[SOLVED]pacman: libusb-compat: /usr/bin/libusb-config exists ...

Hi,
I just installed the arch base system and did a 'pacman -S kernel26' and got some errors
error: failed to commit transaction (conflicting files)
libusb-compat: /usr/bin/libusb-config exists in filesystem
libusb-compat: /usr/include/usb.h exists in filesystem
libusb-compat: /usr/lib/libusb-0.1.so.4 exists in filesystem
libusb-compat: /usr/lib/libusb-0.1.so.4.4.4 exists in filesystem
libusb-compat: /usr/lib/libusb.a exists in filesystem
libusb-compat: /usr/lib/libusb.so exists in filesystem
libusb-compat: /usr/lib/pkgconfig/libusb.pc exists in filesystem
Errors occurred, no packages were upgraded.
this page I found on google contains error messages very similar to mine: http://pastebin.com/twGU7Yy3
any ideas?
Last edited by tgoossens (2011-08-11 17:12:32)

[SOLVED] I believe this is a related topic: https://bbs.archlinux.org/viewtopic.php?id=23774
Last edited by tgoossens (2011-08-11 17:11:52)

Similar Messages

  • [SOLVED] .. error: coreutils: /usr/bin/install exists in filesystem

    Hi All,
    Getting the following error:
    (85/85) checking for file conflicts [###########################] 100%
    error: failed to commit transaction (conflicting files)
    coreutils: /usr/bin/install exists in filesystem
    I am reluctant to delete/move /usr/bin/install for fear of breaking the system ..
    Anyone help here?
    Last edited by bmentink (2012-04-05 02:26:42)

    I just ran into this same issue today while performing a full system upgrade. After some investigation, I came to agree with the OP that manually removing "/usr/bin/install" is the correct action to take.
    Prior to successfully executing the full system upgrade, I found that /usr/bin/install was a symlink to /bin/install. Using "pacman -Qo /bin/install", I found that the file /bin/install was owned by the coreutils 8.15-1 package. The symlink /usr/bin/install, however, was not owned by any package. The conflict arises because coreutils 8.16-2 wants to put the new install program in /usr/bin instead of its previous location under /bin.
    My memory is a bit fuzzy, but I seem to recall running into a problem installing some third party library that had /usr/bin/install hard-coded into its build script and claimed the file didn't exist. I may have manually created the symlink /usr/bin/install to /bin/install as a quick-fix, then forgot to remove it. In retrospect, I could have confirmed/refuted this hypothesis by comparing the time stamp on the symlink /usr/bin/install to /bin/install. If the symlink was created well after /bin/install, then I'm probably to blaim; on the other hand, if the symlink was created essentially at the time /bin/install was created, then most likely the creators of the coreutils package forgot to claim ownership of the symlink.

  • [SOLVED] Freezing while executing /usr/bin/openbox from Openbox menu

    I'm following the instructions in this webpage to create a dynamic menu. I have successfully achieved this on my laptop by installing the openbox-menu package and typing the following lines in menu.xml:
    <menu id="desktop-app-menu" label="Applications" execute="/usr/bin/openbox-menu lxde-applications.menu" />
    For some reason, the same doesn't work on my desktop PC. After editing and saving the menu.xml file, I restart Openbox and when I right click the desktop and hover the "Applications" menu item the desktop freezes. However, I can still move the mouse and switch to other ttys with Ctrl+Alt+Fx, therefore I believe it's reasonable to suggest that the problem lies in the permissions.
    What should I do about it?
    Last edited by Martificiam (2013-02-03 11:29:21)

    Umm, that's not "some random" webpage at all... It worked on all of my Arch Linux installations. The "lxde-applications.menu" is just an argument. But thanks for the link, I'll look into it.
    It's just that it's more of a workaround, not a solution, really... since it has ALWAYS worked for me.
    Furthermore, while setting up Arch on my laptop I remember experiencing similar problems (running a particular program from the openbox menu and resulting in a desktop freeze). This must have something to do with permissions.
    Edit: the xdg_menu worked perfectly, but I would still prefer to use the openbox-menu. I'm marking this as solved anyway.
    Last edited by Martificiam (2013-02-03 11:29:06)

  • Need pacman files for /usr/bin

    Hello, in a freak accident as root, I've deleted my /bin folder. I still have all the rest intact. All I need is pacman's files in that folder in order to recover the others. Can anyone zip their /usr/bin or just their /usr/bin with the pacman files?
    And yes, I have learned my lesson about double checking commands before execution as root.
    Last edited by deadlylife (2010-06-19 21:52:58)

    http://wiki.archlinux.org/index.php/Ins … ting_Linux
    specifically the "Install the required files onto the host system" section.

  • [Solved] Virtualbox-source missing /usr/bin/vboxbuild

    New virtualbox source missing /usr/bin/vboxbuild
    i cant load my vboxdrv module & i also cant build vboxdrv module
    new vbox-source 4.1.18-3 (2012-07-24) dont have vboxbuild script
    anyone also have problem with this issue?
    btw i use ck-kernel
    Last edited by dhiika (2012-07-25 01:19:27)

    xzy3186 wrote:
    gbc921 wrote:
    I'm also using the linux-ck from AUR and I could not load vboxdrv even after the "# dkms setup vboxhost/4.1.18"
    It has compiled fine, but when I do "$ sudo rc.d start dkms" it gives me this:
    :: Starting Dynamic Kernel Module System [BUSY] Error! Could not locate dkms.conf file.
    File: does not exist.
    ERROR: could not insert 'vboxdrv': Exec format error
    ERROR: could not insert 'vboxnetadp': Exec format error
    ERROR: could not insert 'vboxnetflt': Exec format error
    ERROR: could not insert 'vboxpci': Exec format error
    If I try to compile it again then:
    $ sudo dkms install vboxhost/4.1.18
    Module vboxhost/4.1.18 already installed on kernel 3.4.6-2-ck/x86_64
    I have installed these packages:
          community/virtualbox 4.1.18-4
          community/virtualbox-additions 4.1.18-1
          community/virtualbox-modules 4.1.18-4
          community/virtualbox-source 4.1.18-4
          aur/virtualbox-hook 1.0-3
    Sincerely,
    The same problem here. I compiled virtualbox-source 4.1.18-4 with "dkms install" under linux-ck-3.4.6-2 but had "ERROR: could not insert 'vboxdrv': Exec format error" whilie trying to modprobe.
    Solved：According to https://bbs.archlinux.org/viewtopic.php?id=145925, I should delete "old" vboxdrv generated by vboxbuild.
    Yeah! Removing the modules from /usr/lib/extramodules... and doing a depmod worked fine!
    Thanks!

  • [SOLVED] Binaries move to /usr/bin - Few Questions

    Hi All-
    I just learned about this recent change to the filesystem. Wondering if this page outlines the correct steps for moving binaries to /usr/bin:
    https://www.archlinux.org/news/binaries … ervention/
    When I ran the second command (paclist...) on that page, I got a syntax error:
    bash: syntax error near unexpected token `|'
    Other than that, none of the commands listed on the page give me any results, so I'm assuming that means there are no conflicts and it's safe to run the final three commands to upgrade the system. Any advice appreciated.
    Thanks!
    Last edited by w201 (2013-06-09 22:35:32)

    cfr wrote:
    What do you mean when you say that every file in there is linked?
    /bin, /sbin and /usr/sbin should themselves be links. They should not contain links.
    lrwxrwxrwx 1 root root 7 Mai 31 19:40 /bin -> usr/bin/
    lrwxrwxrwx 1 root root 7 Mai 31 19:40 /sbin -> usr/bin/
    lrwxrwxrwx 1 root root 3 Mai 31 19:40 /usr/sbin -> bin/
    Hi- Hmmm, I think this requires an explanation... I see that /bin /sbin/ and /usr/sbin directories are symbolic links, but what I meant is that if you cd into /bin for example, and do "file filename" on any file in there, it'll show that it's "dynamically linked"... I mistook this for meaning a symbolic link.
    Example:
    └──╼ file mev
    mev: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, BuildID[sha1]=24cd2c473bdaa7d951bbf9e14b2792646b6b4932, stripped
    Last edited by w201 (2013-06-10 00:37:18)

  • [SOLVED] Binaries move to /usr/bin requiring update intervention

    Hi!
    I'm trying to follow the instructions from the first page to upgrade but I get this:
    pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm -
    sysvinit 2.88-9
    consolekit 0.4.6-4
    gadmin-samba 0.3.4-1
    initscripts 2012.10.1-1
    And I cannot fix these packages. What should I do?
    Last edited by eherranzr (2013-08-06 23:48:26)

    [548][emilio:/home/emilio]$ pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm -
    Clean output
    [549][emilio:/home/emilio]$ sudo cat /etc/pacman.conf
    # Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
    #IgnorePkg =
    #IgnoreGroup =
    #[testing]
    #Include = /etc/pacman.d/mirrorlist
    [core]
    Include = /etc/pacman.d/mirrorlist
    [extra]
    Include = /etc/pacman.d/mirrorlist
    #[community-testing]
    #Include = /etc/pacman.d/mirrorlist
    [community]
    Include = /etc/pacman.d/mirrorlist
    #[kde-unstable]
    #Include = /etc/pacman.d/mirrorlist
    # If you want to run 32 bit applications on your x86_64 system,
    # enable the multilib repositories as required here.
    #[multilib-testing]
    #Include = /etc/pacman.d/mirrorlist
    [multilib]
    Include = /etc/pacman.d/mirrorlist
    # An example of a custom package repository. See the pacman manpage for
    # tips on creating your own repositories.
    #[custom]
    #SigLevel = Optional TrustAll
    #Server = file:///home/custompkgs
    [archlinuxfr]
    SigLevel = Never
    Server=http://repo.archlinux.fr/x86_64
    No packages ignores or non-official repos
    [550][emilio:/home/emilio]$ find /bin /sbin /usr/sbin -exec pacman -Qo -- {} + >/dev/null
    Clean output
    Not using autofs (it's not installed)
    So everything looks okay I think, I can proceed with step 5 can't I?
    Last edited by eherranzr (2013-08-06 15:35:11)

  • [SOLVED]Pacman error: samba: /lib/libnss_winbind.so.2 exists in filesy

    Hi,
    Went to upgrade and have fixed the problems most are having with pacman 4 etc but now I am getting the below error anyone got any ideas as to how to fix this ?
    Proceed with installation? [Y/n] y
    (406/406) checking package integrity                                                                       [###############################################################] 100%
    (406/406) loading package files                                                                            [###############################################################] 100%
    (406/406) checking for file conflicts                                                                      [###############################################################] 100%
    error: failed to commit transaction (conflicting files)
    samba: /lib/libnss_winbind.so.2 exists in filesystem
    Errors occurred, no packages were upgraded.
    Cheers
    Quazza
    Last edited by quazza (2012-01-20 10:22:37)

    karol wrote:Please read https://bbs.archlinux.org/viewtopic.php?id=130138
    Why thankyou, I am now completing the upgrade, I will mark this as **SOLVED**
    Cheers
    Quazza

  • [SOLVED] Pacman: cant install, remove, update packages

    I'm new to Arch, and yes I've read the Wiki and the sticky post "pacman error: FILENAME exists in filesystem".
    I can't install or update packages. Just synced the local database. I want to install the package "mc", so I ran:
    pacman -S mc
    All required packages were downloaded but then I got lots of:
    [package-name]: /path/to/file exists in file system
    I tried to remove that package but it says:
    loading package data...
    error: '[package-name]': could not find or read package
    I'm totally confused!
    Last edited by presario (2009-02-13 05:08:06)

    here's the output from "pacman -S mc"
    resolving dependencies...
    looking for inter-conflicts...
    Targets: kernel-headers-2.6.27.6-2 tzdata-2009a-1 glibc-2.9-4 ncurses-5.7-2
    Total Download Size: 0.00 MB
    Total Installed Size: 51.91 MB
    checking package integrity...
    checking for file conflicts...
    error: could not prepare transaction
    kernel-headers: /usr/include/asm-generic/errno-base.h exists in filesystem
    kernel-headers: /usr/include/asm-generic/errno.h exists in filesystem
    kernel-headers: /usr/include/asm-generic/fcntl.h exists in filesystem
    kernel-headers: /usr/include/asm-generic/ioctl.h exists in filesystem
    kernel-headers: /usr/include/asm-generic/mman.h exists in filesystem
    kernel-headers: /usr/include/asm-generic/poll.h exists in filesystem
    kernel-headers: /usr/include/asm-generic/resource.h exists in filesystem
    kernel-headers: /usr/include/asm-generic/siginfo.h exists in filesystem
    kernel-headers: /usr/include/asm-generic/signal.h exists in filesystem
    kernel-headers: /usr/include/asm-generic/statfs.h exists in filesystem
    kernel-headers: /usr/include/asm/a.out.h exists in filesystem
    kernel-headers: /usr/include/asm/auxvec.h exists in filesystem
    kernel-headers: /usr/include/asm/boot.h exists in filesystem
    kernel-headers: /usr/include/asm/bootparam.h exists in filesystem
    tzdata: /usr/bin/tzselect exists in filesystem
    tzdata: /usr/sbin/zdump exists in filesystem
    tzdata: /usr/sbin/zic exists in filesystem
    tzdata: /usr/share/man/man3/newctime.3.gz exists in filesystem
    tzdata: /usr/share/man/man3/newtzset.3.gz exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Abidjan exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Accra exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Addis_Ababa exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Algiers exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Asmara exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Asmera exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Bamako exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Bangui exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Banjul exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Bissau exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Blantyre exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Brazzaville exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Bujumbura exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Cairo exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Casablanca exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Ceuta exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Conakry exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Dakar exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Dar_es_Salaam exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Djibouti exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Douala exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/El_Aaiun exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Freetown exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Gaborone exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Harare exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Johannesburg exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Kampala exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Khartoum exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Kigali exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Kinshasa exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Lagos exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Libreville exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Lome exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Luanda exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Lubumbashi exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Lusaka exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Malabo exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Maputo exists in filesystem
    tzdata: /usr/share/zoneinfo/Africa/Maseru exists in filesystem
    glibc: /etc/locale.gen exists in filesystem
    glibc: /etc/nscd.conf exists in filesystem
    glibc: /etc/rc.d/nscd exists in filesystem
    glibc: /etc/rpc exists in filesystem
    glibc: /lib/ld-linux.so.2 exists in filesystem
    glibc: /lib/libBrokenLocale.so.1 exists in filesystem
    glibc: /lib/libSegFault.so exists in filesystem
    glibc: /lib/libanl.so.1 exists in filesystem
    glibc: /lib/libc.so.6 exists in filesystem
    glibc: /lib/libcidn.so.1 exists in filesystem
    glibc: /lib/libcrypt.so.1 exists in filesystem
    glibc: /lib/libdl.so.2 exists in filesystem
    glibc: /lib/libm.so.6 exists in filesystem
    glibc: /lib/libmemusage.so exists in filesystem
    glibc: /lib/libnsl.so.1 exists in filesystem
    glibc: /lib/libnss_compat.so.2 exists in filesystem
    glibc: /lib/libnss_dns.so.2 exists in filesystem
    glibc: /lib/libnss_files.so.2 exists in filesystem
    glibc: /lib/libnss_hesiod.so.2 exists in filesystem
    glibc: /lib/libnss_nis.so.2 exists in filesystem
    glibc: /lib/libnss_nisplus.so.2 exists in filesystem
    glibc: /lib/libpcprofile.so exists in filesystem
    glibc: /lib/libpthread.so.0 exists in filesystem
    glibc: /lib/libresolv.so.2 exists in filesystem
    glibc: /lib/librt.so.1 exists in filesystem
    glibc: /lib/libthread_db-1.0.so exists in filesystem
    glibc: /lib/libthread_db.so.1 exists in filesystem
    glibc: /lib/libutil.so.1 exists in filesystem
    glibc: /sbin/ldconfig exists in filesystem
    glibc: /sbin/sln exists in filesystem
    glibc: /usr/bin/catchsegv exists in filesystem
    glibc: /usr/bin/gencat exists in filesystem
    glibc: /usr/bin/getconf exists in filesystem
    glibc: /usr/bin/getent exists in filesystem
    glibc: /usr/bin/iconv exists in filesystem
    glibc: /usr/bin/ldd exists in filesystem
    glibc: /usr/bin/lddlibc4 exists in filesystem
    glibc: /usr/bin/locale exists in filesystem
    glibc: /usr/bin/localedef exists in filesystem
    glibc: /usr/bin/mtrace exists in filesystem
    glibc: /usr/bin/pcprofiledump exists in filesystem
    glibc: /usr/bin/rpcgen exists in filesystem
    glibc: /usr/bin/sprof exists in filesystem
    glibc: /usr/bin/xtrace exists in filesystem
    glibc: /usr/include/_G_config.h exists in filesystem
    glibc: /usr/include/a.out.h exists in filesystem
    glibc: /usr/include/aio.h exists in filesystem
    glibc: /usr/include/aliases.h exists in filesystem
    glibc: /usr/include/alloca.h exists in filesystem
    glibc: /usr/include/ar.h exists in filesystem
    glibc: /usr/include/argp.h exists in filesystem
    glibc: /usr/include/argz.h exists in filesystem
    glibc: /usr/include/arpa/ftp.h exists in filesystem
    glibc: /usr/include/arpa/inet.h exists in filesystem
    glibc: /usr/include/arpa/nameser.h exists in filesystem
    glibc: /usr/include/arpa/nameser_compat.h exists in filesystem
    glibc: /usr/include/arpa/telnet.h exists in filesystem
    glibc: /usr/include/arpa/tftp.h exists in filesystem
    glibc: /usr/include/assert.h exists in filesystem
    glibc: /usr/include/bits/a.out.h exists in filesystem
    glibc: /usr/include/bits/byteswap.h exists in filesystem
    glibc: /usr/include/bits/cmathcalls.h exists in filesystem
    glibc: /usr/include/bits/confname.h exists in filesystem
    glibc: /usr/include/bits/dirent.h exists in filesystem
    glibc: /usr/include/bits/dlfcn.h exists in filesystem
    glibc: /usr/include/bits/elfclass.h exists in filesystem
    glibc: /usr/include/bits/endian.h exists in filesystem
    glibc: /usr/include/bits/environments.h exists in filesystem
    glibc: /usr/include/bits/errno.h exists in filesystem
    glibc: /usr/include/bits/error.h exists in filesystem
    glibc: /usr/include/bits/fcntl.h exists in filesystem
    glibc: /usr/include/bits/fcntl2.h exists in filesystem
    glibc: /usr/include/bits/fenv.h exists in filesystem
    glibc: /usr/include/bits/fenvinline.h exists in filesystem
    glibc: /usr/include/bits/huge_val.h exists in filesystem
    glibc: /usr/include/bits/huge_valf.h exists in filesystem
    glibc: /usr/include/bits/huge_vall.h exists in filesystem
    glibc: /usr/include/bits/in.h exists in filesystem
    glibc: /usr/include/bits/inf.h exists in filesystem
    glibc: /usr/include/bits/initspin.h exists in filesystem
    glibc: /usr/include/bits/ioctl-types.h exists in filesystem
    glibc: /usr/include/bits/ioctls.h exists in filesystem
    glibc: /usr/include/bits/ipc.h exists in filesystem
    glibc: /usr/include/bits/ipctypes.h exists in filesystem
    glibc: /usr/include/bits/libc-lock.h exists in filesystem
    glibc: /usr/include/bits/libio-ldbl.h exists in filesystem
    glibc: /usr/include/bits/link.h exists in filesystem
    glibc: /usr/include/bits/local_lim.h exists in filesystem
    glibc: /usr/include/bits/locale.h exists in filesystem
    glibc: /usr/include/bits/mathcalls.h exists in filesystem
    glibc: /usr/include/bits/mathdef.h exists in filesystem
    glibc: /usr/include/bits/mathinline.h exists in filesystem
    glibc: /usr/include/bits/mman.h exists in filesystem
    glibc: /usr/include/bits/monetary-ldbl.h exists in filesystem
    glibc: /usr/include/bits/mqueue.h exists in filesystem
    glibc: /usr/include/bits/mqueue2.h exists in filesystem
    glibc: /usr/include/bits/msq.h exists in filesystem
    glibc: /usr/include/bits/nan.h exists in filesystem
    glibc: /usr/include/bits/netdb.h exists in filesystem
    glibc: /usr/include/bits/poll.h exists in filesystem
    glibc: /usr/include/bits/posix1_lim.h exists in filesystem
    glibc: /usr/include/bits/posix2_lim.h exists in filesystem
    glibc: /usr/include/bits/posix_opt.h exists in filesystem
    glibc: /usr/include/bits/printf-ldbl.h exists in filesystem
    glibc: /usr/include/bits/pthreadtypes.h exists in filesystem
    glibc: /usr/include/bits/resource.h exists in filesystem
    glibc: /usr/include/bits/sched.h exists in filesystem
    glibc: /usr/include/bits/select.h exists in filesystem
    glibc: /usr/include/bits/sem.h exists in filesystem
    glibc: /usr/include/bits/semaphore.h exists in filesystem
    glibc: /usr/include/bits/setjmp.h exists in filesystem
    ncurses: /bin/tput exists in filesystem
    ncurses: /lib/libncursesw.so.5 exists in filesystem
    ncurses: /usr/bin/captoinfo exists in filesystem
    ncurses: /usr/bin/clear exists in filesystem
    ncurses: /usr/bin/infocmp exists in filesystem
    ncurses: /usr/bin/infotocap exists in filesystem
    ncurses: /usr/bin/ncursesw5-config exists in filesystem
    ncurses: /usr/bin/reset exists in filesystem
    ncurses: /usr/bin/tic exists in filesystem
    ncurses: /usr/bin/toe exists in filesystem
    ncurses: /usr/bin/tset exists in filesystem
    ncurses: /usr/include/curses.h exists in filesystem
    ncurses: /usr/include/cursesapp.h exists in filesystem
    ncurses: /usr/include/cursesf.h exists in filesystem
    ncurses: /usr/include/cursesm.h exists in filesystem
    ncurses: /usr/include/cursesp.h exists in filesystem
    ncurses: /usr/include/cursesw.h exists in filesystem
    ncurses: /usr/include/cursslk.h exists in filesystem
    ncurses: /usr/include/eti.h exists in filesystem
    ncurses: /usr/include/etip.h exists in filesystem
    ncurses: /usr/include/form.h exists in filesystem
    ncurses: /usr/include/menu.h exists in filesystem
    ncurses: /usr/include/ncurses.h exists in filesystem
    ncurses: /usr/include/ncurses_dll.h exists in filesystem
    ncurses: /usr/include/panel.h exists in filesystem
    ncurses: /usr/include/term.h exists in filesystem
    ncurses: /usr/include/termcap.h exists in filesystem
    ncurses: /usr/include/unctrl.h exists in filesystem
    ncurses: /usr/lib/libcurses.a exists in filesystem
    ncurses: /usr/lib/libcurses.so exists in filesystem
    ncurses: /usr/lib/libcursesw.so exists in filesystem
    ncurses: /usr/lib/libform.a exists in filesystem
    ncurses: /usr/lib/libform.so exists in filesystem
    ncurses: /usr/lib/libformw.a exists in filesystem
    ncurses: /usr/lib/libformw.so exists in filesystem
    ncurses: /usr/lib/libformw.so.5 exists in filesystem
    ncurses: /usr/lib/libmenu.a exists in filesystem
    i can't post the everything since it's too long (about 6000 lines), the forum is not letting me to post everything

  • [Solved]Pacman can't find steam(and yes I read the other topics)

    To make it short, pacman really can't find steam.
    Options I tried:
    pacman -S steam
    pacman -Sy steam
    pacman -Syyu steam
    pacman -Ss steam
    And still got nothing.
    Here's my last attempt at it:
    $ sudo pacman -Syyu steam
    :: Synchronizing package databases...
    core                     112.7 KiB  49.9K/s 00:02 [######################] 100%
    extra                   1763.0 KiB  30.5K/s 00:58 [######################] 100%
    community                  2.3 MiB  74.2K/s 00:31 [######################] 100%
    error: target not found: steam
    Notes: I'm running arch on a VBox. Sorry if I sound cocky or anything but maybe it's my lack of sleep over this particular problem. Yes, I uncommented the multilib repo in pacman.conf.
    Anyone got any ideas?
    Last edited by Jackoz530 (2014-08-11 14:20:02)

    lucke wrote:Maybe you have failed to uncomment the multilib repo properly, as your output doesn't show its synchronizing.
    This worked for me. Found steam in the multilib repo when I properly uncommented the repo.
    Though it's weird that steam can't be found in the community repo, only in the multilib repo.
    $ pacman -Ss steam
    multilib/steam 1.0.0.48-1
    Digital distribution client bootstrap package
    Pacman.conf is as follows:
    # /etc/pacman.conf
    # See the pacman.conf(5) manpage for option and repository directives
    # GENERAL OPTIONS
    [options]
    # The following paths are commented out with their default values listed.
    # If you wish to use different paths, uncomment and update the paths.
    #RootDir = /
    #DBPath = /var/lib/pacman/
    #CacheDir = /var/cache/pacman/pkg/
    #LogFile = /var/log/pacman.log
    #GPGDir = /etc/pacman.d/gnupg/
    HoldPkg = pacman glibc
    #XferCommand = /usr/bin/curl -C - -f %u > %o
    #XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
    #CleanMethod = KeepInstalled
    #UseDelta = 0.7
    Architecture = auto
    # Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
    #IgnorePkg =
    #IgnoreGroup =
    #NoUpgrade =
    #NoExtract =
    # Misc options
    #UseSyslog
    #Color
    #TotalDownload
    CheckSpace
    #VerbosePkgLists
    # By default, pacman accepts packages signed by keys that its local keyring
    # trusts (see pacman-key and its man page), as well as unsigned packages.
    SigLevel = Required DatabaseOptional
    LocalFileSigLevel = Optional
    #RemoteFileSigLevel = Required
    # NOTE: You must run `pacman-key --init` before first using pacman; the local
    # keyring can then be populated with the keys of all official Arch Linux
    # packagers with `pacman-key --populate archlinux`.
    # REPOSITORIES
    # - can be defined here or included from another file
    # - pacman will search repositories in the order defined here
    # - local/custom mirrors can be added here or in separate files
    # - repositories listed first will take precedence when packages
    # have identical names, regardless of version number
    # - URLs will have $repo replaced by the name of the current repo
    # - URLs will have $arch replaced by the name of the architecture
    # Repository entries are of the format:
    # [repo-name]
    # Server = ServerName
    # Include = IncludePath
    # The header [repo-name] is crucial - it must be present and
    # uncommented to enable the repo.
    # The testing repositories are disabled by default. To enable, uncomment the
    # repo name header and Include lines. You can add preferred servers immediately
    # after the header, and they will be used before the default mirrors.
    #[testing]
    #Include = /etc/pacman.d/mirrorlist
    [core]
    Include = /etc/pacman.d/mirrorlist
    [extra]
    Include = /etc/pacman.d/mirrorlist
    #[community-testing]
    #Include = /etc/pacman.d/mirrorlist
    [community]
    Include = /etc/pacman.d/mirrorlist
    # If you want to run 32 bit applications on your x86_64 system,
    # enable the multilib repositories as required here.
    #[multilib-testing]
    #Include = /etc/pacman.d/mirrorlist
    [multilib]
    Include = /etc/pacman.d/mirrorlist
    # An example of a custom package repository. See the pacman manpage for
    # tips on creating your own repositories.
    #[custom]
    #SigLevel = Optional TrustAll
    #Server = file:///home/custompkgs
    I'm currently grabbing the steam in the multilib repo and gonna test it once I finished grabbing it.

  • [SOLVED] pacman replies - No such file

    i cant install amarok right now.
    pacman -S amarok
    No such file “amarok-2.4.1-1-x86_64.pkg.tar.xz”.
    warning: failed to retrieve some files from extra
    error: failed to commit transaction (error invoking external downloader)
    Errors occurred, no packages were upgraded.
    i have tried various transfer commands as well in the pacman.conf
    #XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
    #MY EDIT
    #XferCommand = /usr/bin/wget -c --passive-ftp -c %u
    #XferCommand = /usr/bin/curl %u > %o
    i tried about 15 different mirrors as well. 
    what am i doing wrong?
    Last edited by wolfdogg (2011-07-05 23:04:17)

    thank you for the replies.
    falconindy wrote:If you switch mirrors, you need to forcefully update your sync DBs with 'pacman -Syy'. Failing to do this will lead to attempts to download the same missing files.
    your right, thanks its working now! i forgot about this, (to re sync pacman -Syy after switching mirrors)
    first i received a message that the file doesnt exist, thats understandable if its using the old pacman database before the -Syy resync
    Connecting to mirror.rit.edu|129.21.171.98|:21... connected.
    Logging in as anonymous ... Logged in!
    ==> SYST ... done.    ==> PWD ... done.
    ==> TYPE I ... done.  ==> CWD (1) /archlinux/extra/os/x86_64 ... done.
    ==> SIZE amarok-2.4.1-1-x86_64.pkg.tar.xz ... done.
    ==> PASV ... done.    ==> RETR amarok-2.4.1-1-x86_64.pkg.tar.xz ...
    No such file “amarok-2.4.1-1-x86_64.pkg.tar.xz”.
    why is it if i switch mirrors, even though i can see the machine its connecting to is the new mirror, the file isnt found, it must be because the old database list from the old mirror tells it that it doesnt exist, so it doesnt even bother looking right? 
    but for some reason the next time i tried i got a 404 error, which is confusing to me because when you see a 404, that means that the server responded that the file doesnt exist.  i think this is the one i was going off off to make my assumption.  i didnt notice the first one until i detailed this out.  i only noticed the 404.
    Connecting to mirrors.kernel.org|149.20.20.135|:80... connected.
    HTTP request sent, awaiting response... 404 Not Found
    2011-07-02 13:20:52 ERROR 404: Not Found.
    Last edited by wolfdogg (2011-07-02 20:51:23)

  • [solved] Pacman Signatures not trusted

    ben@arch-desktop:~$ sudo pacman -S archlinux-keyring
    warning: archlinux-keyring-20131027-1 is up to date -- reinstalling
    resolving dependencies...
    looking for inter-conflicts...
    Packages (1): archlinux-keyring-20131027-1
    Total Installed Size: 0.55 MiB
    Net Upgrade Size: 0.00 MiB
    :: Proceed with installation? [Y/n]
    (1/1) checking keys in keyring [#########################] 100%
    (1/1) checking package integrity [#########################] 100%
    error: archlinux-keyring: signature from "Pierre Schmitz <[email protected]>" is unknown trust
    :: File /var/cache/pacman/pkg/archlinux-keyring-20131027-1-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
    Do you want to delete it? [Y/n] n
    error: failed to commit transaction (invalid or corrupted package (PGP signature))
    Errors occurred, no packages were upgraded.
    Tried deleting the /etc/pacman.d/gpupg and refreshing keys, no luck
    ben@arch-desktop:~$ sudo pacman-key --refresh-keys
    gpg: refreshing 4 keys from hkp://pool.sks-keyservers.net
    gpg: requesting key 1DBDE5EE from hkp server pool.sks-keyservers.net
    gpg: requesting key 653C3094 from hkp server pool.sks-keyservers.net
    gpg: requesting key 06361833 from hkp server pool.sks-keyservers.net
    gpg: requesting key 9741E8AC from hkp server pool.sks-keyservers.net
    gpgkeys: key 2DD280C54478C0000E232A734D090A9F1DBDE5EE not found on keyserver
    gpg: key 653C3094: "Vi0L0 <[email protected]>" not changed
    gpg: key 06361833: "Tom Gundersen <[email protected]>" not changed
    gpg: key 9741E8AC: "Pierre Schmitz <[email protected]>" not changed
    gpg: Total number processed: 3
    gpg: unchanged: 3
    ben@arch-desktop:~$ cat /etc/pacman.conf
    # /etc/pacman.conf
    # See the pacman.conf(5) manpage for option and repository directives
    # GENERAL OPTIONS
    [options]
    # The following paths are commented out with their default values listed.
    # If you wish to use different paths, uncomment and update the paths.
    #RootDir = /
    #DBPath = /var/lib/pacman/
    #CacheDir = /var/cache/pacman/pkg/
    #LogFile = /var/log/pacman.log
    #GPGDir = /etc/pacman.d/gnupg/
    HoldPkg = pacman glibc
    #XferCommand = /usr/bin/curl -C - -f %u > %o
    #XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
    #CleanMethod = KeepInstalled
    #UseDelta = 0.7
    Architecture = auto
    # Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
    IgnorePkg = linux linux-headers
    IgnoreGroup = xorg
    #NoUpgrade =
    #NoExtract =
    # Misc options
    #UseSyslog
    #Color
    #TotalDownload
    CheckSpace
    #VerbosePkgLists
    # By default, pacman accepts packages signed by keys that its local keyring
    # trusts (see pacman-key and its man page), as well as unsigned packages.
    SigLevel = Required DatabaseOptional
    LocalFileSigLevel = Optional
    #RemoteFileSigLevel = Required
    # NOTE: You must run `pacman-key --init` before first using pacman; the local
    # keyring can then be populated with the keys of all official Arch Linux
    # packagers with `pacman-key --populate archlinux`.
    # REPOSITORIES
    # - can be defined here or included from another file
    # - pacman will search repositories in the order defined here
    # - local/custom mirrors can be added here or in separate files
    # - repositories listed first will take precedence when packages
    # have identical names, regardless of version number
    # - URLs will have $repo replaced by the name of the current repo
    # - URLs will have $arch replaced by the name of the architecture
    # Repository entries are of the format:
    # [repo-name]
    # Server = ServerName
    # Include = IncludePath
    # The header [repo-name] is crucial - it must be present and
    # uncommented to enable the repo.
    # The testing repositories are disabled by default. To enable, uncomment the
    # repo name header and Include lines. You can add preferred servers immediately
    # after the header, and they will be used before the default mirrors.
    [catalyst]
    SigLevel = Optional TrustAll
    #Server = http://catalyst.wirephire.com/repo/catalyst/$arch
    Server = http://mirror.rts-informatique.fr/archlinux-catalyst/repo/catalyst/$arch
    #[testing]
    #Include = /etc/pacman.d/mirrorlist
    [core]
    Include = /etc/pacman.d/mirrorlist
    [extra]
    Include = /etc/pacman.d/mirrorlist
    #[community-testing]
    #Include = /etc/pacman.d/mirrorlist
    [community]
    Include = /etc/pacman.d/mirrorlist
    # If you want to run 32 bit applications on your x86_64 system,
    # enable the multilib repositories as required here.
    #[multilib-testing]
    #Include = /etc/pacman.d/mirrorlist
    [multilib]
    Include = /etc/pacman.d/mirrorlist
    # An example of a custom package repository. See the pacman manpage for
    # tips on creating your own repositories.
    #[custom]
    #SigLevel = Optional TrustAll
    #Server = file:///home/custompkgs
    I'm at a loss, nothing on the wiki or forums or google seem to be a solution, any thoughts?  Thanks.
    EDIT: this is weird, ran pacman-key --populate archlinux and now it seems to work?  That was also on the list of things I had tried with no positive results... perhaps it was the order in which I did it?
    Last edited by hippieben (2014-01-05 01:40:04)

    Allan wrote:Try "pacman-key --populate archlinux"
    that's what did it.

  • [Solved] pacman upgrade fail

    When I try to upgrade pacman I get the following:
    gordiegii@Ion-Arch ~]$ sudo pacman -S pacman
    Password:
    resolving dependencies...
    looking for inter-conflicts...
    Targets (1): pacman-4.0.3-1
    Total Installed Size: 3.54 MiB
    Proceed with installation? [Y/n]
    (1/1) checking package integrity [###################################################] 100%
    (1/1) loading package files [###################################################] 100%
    (1/1) checking for file conflicts [###################################################] 100%
    error: failed to commit transaction (conflicting files)
    pacman: /usr/bin/cleanupdelta exists in filesystem
    pacman: /usr/bin/makepkg exists in filesystem
    pacman: /usr/bin/pacman exists in filesystem
    pacman: /usr/bin/pacman-db-upgrade exists in filesystem
    pacman: /usr/bin/pacman-key exists in filesystem
    pacman: /usr/bin/pacman-optimize exists in filesystem
    pacman: /usr/bin/pacsort exists in filesystem
    pacman: /usr/bin/pactree exists in filesystem
    pacman: /usr/bin/pkgdelta exists in filesystem
    pacman: /usr/bin/rankmirrors exists in filesystem
    pacman: /usr/bin/repo-add exists in filesystem
    pacman: /usr/bin/repo-elephant exists in filesystem
    pacman: /usr/bin/repo-remove exists in filesystem
    pacman: /usr/bin/testdb exists in filesystem
    pacman: /usr/bin/testpkg exists in filesystem
    pacman: /usr/bin/vercmp exists in filesystem
    pacman: /usr/include/alpm.h exists in filesystem
    pacman: /usr/include/alpm_list.h exists in filesystem
    pacman: /usr/lib/libalpm.a exists in filesystem
    pacman: /usr/lib/libalpm.so exists in filesystem
    pacman: /usr/lib/libalpm.so.7 exists in filesystem
    pacman: /usr/share/locale/ca/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/ca/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/ca/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/cs/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/cs/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/cs/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/da/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/da/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/da/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/de/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/de/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/de/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/el/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/el/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/el/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/en_GB/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/en_GB/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/en_GB/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/es/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/es/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/es/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/fi/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/fi/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/fi/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/fr/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/fr/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/fr/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/hu/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/hu/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/hu/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/it/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/it/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/it/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/kk/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/kk/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/kk/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/lt/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/lt/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/lt/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/nb/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/nb/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/nb/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/pl/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/pl/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/pl/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/pt/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/pt/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/pt/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/pt_BR/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/pt_BR/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/pt_BR/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/ro/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/ro/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/ro/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/ru/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/ru/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/ru/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/sk/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/sk/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/sk/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/sr/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/sr/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/sr/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/sr@latin/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/sr@latin/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/sr@latin/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/sv/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/sv/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/sv/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/tr/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/tr/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/tr/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/uk/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/uk/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/uk/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/zh_CN/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/zh_CN/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/zh_CN/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/locale/zh_TW/LC_MESSAGES/libalpm.mo exists in filesystem
    pacman: /usr/share/locale/zh_TW/LC_MESSAGES/pacman-scripts.mo exists in filesystem
    pacman: /usr/share/locale/zh_TW/LC_MESSAGES/pacman.mo exists in filesystem
    pacman: /usr/share/man/man3/libalpm.3.gz exists in filesystem
    pacman: /usr/share/man/man5/PKGBUILD.5.gz exists in filesystem
    pacman: /usr/share/man/man5/makepkg.conf.5.gz exists in filesystem
    pacman: /usr/share/man/man5/pacman.conf.5.gz exists in filesystem
    pacman: /usr/share/man/man8/makepkg.8.gz exists in filesystem
    pacman: /usr/share/man/man8/pacman-key.8.gz exists in filesystem
    pacman: /usr/share/man/man8/pacman.8.gz exists in filesystem
    pacman: /usr/share/man/man8/pkgdelta.8.gz exists in filesystem
    pacman: /usr/share/man/man8/repo-add.8.gz exists in filesystem
    pacman: /usr/share/man/man8/repo-remove.8.gz exists in filesystem
    pacman: /usr/share/man/man8/vercmp.8.gz exists in filesystem
    pacman: /usr/share/pacman/ChangeLog.proto exists in filesystem
    pacman: /usr/share/pacman/PKGBUILD-split.proto exists in filesystem
    pacman: /usr/share/pacman/PKGBUILD.proto exists in filesystem
    pacman: /usr/share/pacman/proto.install exists in filesystem
    pacman: /usr/share/zsh/site-functions/_pacman exists in filesystem
    Errors occurred, no packages were upgraded.
    [gordiegii@Ion-Arch ~]$
    Has anybody seen this or have any idea how to fix it?
    Should I just delete all these files?
    I was getting a gcc / gcc-libs error before but reinstalling gcc as per other forum help fixed that.
    Last edited by GordieGii (2012-04-29 15:29:26)

    @Gcool: I did a quick search and could not find anything that matched my symptoms. The only things I found that seemed to apply were the gcc / gcc-libs issue which I resolved and merging my pacman.conf.pacnew file into pacman.conf file (only two non-comments were new and they didn't seem related).
    Perhaps I can't assess the applicability of a post to my symptoms.
    @karol: I did -Syu, as I always do, but this time I got this:
    :: The following packages should be upgraded first :
    pacman
    :: Do you want to cancel the current operation
    :: and upgrade these packages now? [Y/n]
    I tried both 'Yes' and 'no' and both failed. 'No' took much longer because it had to download a couple hundred packages (I have been trying to resolve this myself for over a week and the list keeps getting longer) before failing so I switched to just pacman.
    Pacman was in the list of packages and I couldn't figure out how to exclude it to see if the others would update. Reinstalling gcc worked.
    [gordiegii@Ion-Arch man]$ stat -c %s $(find /var/lib/pacman/local -name "pacman-4*")/files
    0
    [gordiegii@Ion-Arch man]$
    Please pardon my newbieness, I came from Ubuntu when GnomeBloat became too much for my Intel ATOM and am still learning the Arch way.

  • Circular: can't install libusb-compat for `pacman-key --init` [SOLVED]

    So like a lot of people on here have upgraded to pacman 4.
    I can't run `pacman-key --init` to update the keyring:
    [stuart@myhost ~]$ sudo pacman-key --init
    Password:
    gpg: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
    chmod: cannot access `/etc/pacman.d/gnupg/trustdb.gpg': No such file or directory
    gpg: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
    gpg: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
    ==> Updating trust database...
    gpg: error while loading shared libraries: libusb-0.1.so.4: cannot open shared object file: No such file or directory
    And because of signature issues can't install libusb-compat:
    [stuart@myhost ~]$ sudo pacman -S libusb-compat
    Password:
    resolving dependencies...
    looking for inter-conflicts...
    Targets (1): libusb-compat-0.1.3-2
    Total Installed Size: 0.06 MiB
    Net Upgrade Size: -0.02 MiB
    Proceed with installation? [Y/n] y
    (1/1) checking package integrity [######################] 100%
    warning: Public keyring not found; have you run 'pacman-key --init'?
    error: GPGME error: Invalid crypto engine
    error: failed to commit transaction (invalid or corrupted package (PGP signature))
    Errors occurred, no packages were upgraded.
    Last edited by Skipper_the_eye_child (2012-01-26 19:24:00)

    That worked - thanks. It'd have helped had I remembered to write over pacman.conf of course! I've not done any mainentance for while, got a little rusty i'm afraid.
    Last edited by Skipper_the_eye_child (2012-04-11 14:02:52)

  • [SOLVED]pacman fails to upgrade... /usr/bin/vercmp: cannot execute bin

    Proceed with installation? [Y/n] y
    :: Retrieving packages from core...
    pacman-3.2.1-1-x86_64 491.3K 1850.7K/s 00:00:00 [########################################################################################################] 100%
    checking package integrity...
    (1/1) checking for file conflicts [########################################################################################################] 100%
    (1/1) upgrading pacman [########################################################################################################] 100%
    warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
    /tmp/alpm_eT02H1/.INSTALL: line 5: /usr/bin/vercmp: cannot execute binary file
    /tmp/alpm_eT02H1/.INSTALL: line 5: [: : integer expression expected
    Here is more info on my system and the file vermcp is installed and permissions seem correct.
    http://rafb.net/p/MYk3pO21.html
    HELP?
    Last edited by rooloo (2008-09-09 00:07:09)

    Ok, this was my dumb mistake again. I was testing out powerpill on my server which is a 32 bit machine. I tried copying my 64 bit mirrorlist to my 32 bit server because I have it ranked and slimmed down to only the essential servers.

Maybe you are looking for