[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.

Similar Messages

  • /usr/bin/ld: CANNOT EXECUTE binary file!

    So whenever I try to compile something, I get to the step
    checking for gcc... gcc
    checking for C compiler default output file name...
    configure: error: C compiler cannot create executables
    See `config.log' for more details.
    And looking at the log, my problem is...
    /usr/bin/ld: /usr/bin/ld: cannot execute binary file
    Which... Is bad. Yes, I've tried chmodding it +x. I've also tried logging in as root and trying to run it, no luck.
    What's wrong? =/
    Would asking someone else with an iMac G5 to send me theirs, fix it?

    Running configure on all open source packages brings me to the ld cannot execute error in configure.log. In this case I was attempting to build libssh2 (SSH functions for PHP).
    Thanks for the link Nils, I'll try that.

  • [SOLVED] Pacman fails to refresh/update.

    # pacman -Syy
    :: Synchronizing package databases...
    error: failed to update core (unexpected error)
    error: failed to update extra (unexpected error)
    error: failed to update community (unexpected error)
    error: failed to synchronize any databases
    It doesnt want to connect to anything.yet when i use ping -c 3 www.google.com like the beginners guide said, it connects and does not give me unknown host error.
    Toshiba Satellite L305-S5931
    Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 1)
    subsystem:Askey Computer Corp. Device 7128
    Please, this has plagued me for a while and has left me confused.
    Last edited by 3120 (2009-06-07 21:30:25)

    # /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
    HoldPkg = pacman glibc
    # If upgrades are available for these packages they will be asked for first
    SyncFirst = pacman
    #XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
    #XferCommand = /usr/bin/curl %u > %o
    # Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
    #IgnorePkg =
    #IgnoreGroup =
    #NoUpgrade =
    #NoExtract =
    # Misc options (all disabled by default)
    #NoPassiveFtp
    #UseSyslog
    #ShowSize
    #UseDelta
    #TotalDownload
    # 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
    # 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.
    # Testing is disabled by default. To enable, uncomment the following
    # two 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]
    # Add your preferred servers here, they will be used first
    Include = /etc/pacman.d/mirrorlist
    [extra]
    # Add your preferred servers here, they will be used first
    Include = /etc/pacman.d/mirrorlist
    [community]
    # Add your preferred servers here, they will be used first
    Include = /etc/pacman.d/mirrorlist
    # An example of a custom package repository. See the pacman manpage for
    # tips on creating your own repositories.
    #[custom]
    #Server = file:///home/custompkgs
    that is /etc/pacman.conf
    that is /etc/pacman.d/mirrorlist

  • [Solved] Pacman fails to satisfied java-runtime dependency on upgrade

    Hi. So I haven't been able to upgrade yesterday or today because of this bug. I couldn't figure out how to solve it on my own.
    This is what happens when I try to upgrade:
    jake@levi> sudo pacman -Syyu ~
    :: Synchronizing package databases...
    core 104.8 KiB 76.7K/s 00:01 [##################################################################################################] 100%
    extra 1389.5 KiB 187K/s 00:07 [##################################################################################################] 100%
    community 1549.8 KiB 191K/s 00:08 [##################################################################################################] 100%
    multilib 89.7 KiB 145K/s 00:01 [##################################################################################################] 100%
    :: Starting full system upgrade...
    resolving dependencies...
    looking for inter-conflicts...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: languagetool: requires java-runtime>=6
    :: rhino: requires java-runtime
    I have jre7-openjdk-headless already installed, which provides java-runtime 7, so I don't see why I could be running into any problems.
    [1] jake@levi> pacman -Qi jre7-openjdk-headless ~
    Name : jre7-openjdk-headless
    Version : 7.b147_2.1-1
    URL : http://icedtea.classpath.org
    Licenses : custom
    Groups : None
    Provides : java-runtime=7
    Depends On : libjpeg-turbo lcms2 nss ca-certificates-java rhino
    Optional Deps : libcups: needed for Java Mauve support - libmawt.so
    fontconfig: needed for Java Mauve support - libmawt.so
    Required By : languagetool rhino
    Conflicts With : java-runtime openjdk6
    Replaces : None
    Installed Size : 107421.00 KiB
    Packager : Andreas Radke <[email protected]>
    Architecture : x86_64
    Build Date : Wed Feb 15 06:36:20 2012
    Install Date : Thu Mar 1 14:06:19 2012
    Install Reason : Installed as a dependency for another package
    Install Script : Yes
    Description : Free Java environment based on OpenJDK 7.0 with IcedTea7 replacing binary plugs - Minimal Java runtime - needed for executing non GUI Java programs
    There could be something I don't understand though. Any help is appreciated.
    Last edited by Coward (2012-03-08 00:30:57)

    mira wrote:
    Karol's advice did not worked for me, so I did this:
    pacman -Rdd jre7-openjdk-headless
    and after that this:
    pacman -S jre7-openjdk
    and then the update worked as it should. Hope that helps somebody.
    Not sure what was the issue in your case, but I did say "Try to ignore the conflicts and see if it works out." and by that I meant the '-dd' switch.
    Now I see I should have been explicit about it as my comment doesn't make it clear at all.

  • [Solved] Pacman fails to get packages http 403 or 404 error

    Hi,
    I'm not sure if I should raise this as a bug or not, or indeed if I am doing something fundamentally wrong...
    Pacman tells me there are updates to do, but:
    Using the mirror "mirrors.manchester.m247.com" I get a 404 error
    Using the mirror "http://mirror.bytemark.co.uk/archlinux/$repo/os/$arch" I get a 403 error
    example:
    # pacman -Syu
    :: Synchronizing package databases...
    core is up to date
    extra is up to date 0.0 B 0.00B/s 00:00 [-----------------------------------------------------------------------] 0%
    community is up to date 0.0 B 0.00B/s 00:00 [-----------------------------------------------------------------------] 0%
    multilib is up to date 0.0 B 0.00B/s 00:00 [-----------------------------------------------------------------------] 0%
    :: Starting full system upgrade...
    resolving dependencies...
    looking for conflicting packages...
    Packages (9) ca-certificates-mozilla-3.18-3 dhcpcd-6.8.1-1 gnupg-2.1.2-3 iptables-1.4.21-3 p11-kit-0.23.1-2 procps-ng-3.3.10-2 sudo-1.8.13-1 which-2.21-1 whois-5.2.7-1
    Total Download Size: 0.03 MiB
    Total Installed Size: 21.35 MiB
    Net Upgrade Size: 4.34 MiB
    :: Proceed with installation? [Y/n]
    :: Retrieving packages ...
    error: failed retrieving file 'whois-5.2.7-1-x86_64.pkg.tar.xz' from mirrors.manchester.m247.com : The requested URL returned error: 404
    warning: failed to retrieve some files
    error: failed to commit transaction (unexpected error)
    Errors occurred, no packages were upgraded.
    any ideas?
    [edited to add solved tag to title]
    Last edited by flangemonkey (2015-04-01 15:29:18)

    Hi flangemonkey,
    that mirror was not synced yet when you did the upgrade (the last sync ended today at 10:54 UTC, about 17 mitues after you posted on this borad). It should be ok now, just try to redo the update. Next time, you may want to check first the status of the mirrors https://www.archlinux.org/mirrors/status
    edit: typo
    Last edited by mauritiusdadd (2015-04-01 11:06:10)

  • [SOLVED]Pacman fails to update

    Hi,
    It's been a while, so I hope this issue can be resolved here, and I'll be on my best behaviour. I tried an update (system-wide) with
    pacman -Syu
    it came back with :
    error: failed to commit transaction (conflicting files)
    initscripts: /etc/profile.d/locale.sh exists in filesystem
    Errors occurred, no packages were upgraded.
    What do I do next?
    Thanks for helping out
    Thor
    Last edited by Thor@Flanders (2011-10-26 09:38:53)

    Will do, tnx.
    New-year resolution: read the news on-site more often.
    Marking this as solved
    Last edited by Thor@Flanders (2011-10-26 09:38:33)

  • [SOLVED]pacman fails to install mtpaint

    [me@mypc ~]$ sudo pacman -S mtpaint
    resolving dependencies...
    looking for inter-conflicts...
    Targets (3): giflib-4.1.6-4 openjpeg-1.3-3 mtpaint-3.31-4
    Total Download Size: 0.86 MB
    Total Installed Size: 2.61 MB
    Proceed with installation? [Y/n] y
    :: Retrieving packages from extra...
    giflib-4.1.6-4-x86_64 85.0K 533.6K/s 00:00:00 [###################################################################################################################################################################] 100%
    error: failed retrieving file 'openjpeg-1.3-3-x86_64.pkg.tar.gz' from mirror.lividpenguin.com : File unavailable (e.g., file not found, no access)
    warning: failed to retrieve some files from extra
    error: failed to commit transaction (File unavailable (e.g., file not found, no access))
    Errors occurred, no packages were upgraded.
    [me@mypc ~]$
    I have tried changing mirrors but it doesn't help
    Last edited by dameunmate (2011-09-25 21:56:23)

    You must use pacman -Syy when changing mirrors. openjpeg is at version 1.4-1. You should not expect to find openjpeg 1.3-3 anywhere.

  • [SOLVED] pacman fails on a package that should've been ignored anyway

    Hi all,
    I don't understand why the below upgrade isn't working.  I exclude the kernel from my normal upgrade command as it prevents me from loading any modules until I reboot, so I typically only upgrade the kernel when I'm about to reboot.
    In this case failure to upgrade the kernel is preventing the nVidia driver from being updated also, which is fine, but I don't understand why it then says it can't install 'nvidia' because 'nvidia-utils' is the wrong version - I thought 'nvidia' was going to be skipped?  Why is it trying to install it anyway?
    Is there a way to get around this without having to manually exclude all these packages?
    $ pacman -Su
    :: Starting full system upgrade...
    :: Replace dbus-python with extra/python2-dbus? [Y/n]
    warning: linux: ignoring package upgrade (3.3.8-1 => 3.4.2-2)
    warning: linux-headers: ignoring package upgrade (3.3.8-1 => 3.4.2-2)
    resolving dependencies...
    warning: ignoring package linux-3.4.2-2
    warning: cannot resolve "linux>=3.4", a dependency of "nvidia"
    warning: ignoring package linux-3.4.2-2
    warning: cannot resolve "linux>=3.4", a dependency of "virtualbox-modules"
    :: The following packages cannot be upgraded due to unresolvable dependencies:
    nvidia virtualbox-modules
    Do you want to skip the above packages for this upgrade? [y/N] y
    looking for inter-conflicts...
    error: failed to prepare transaction (could not satisfy dependencies)
    :: nvidia: requires nvidia-utils=295.53
    Last edited by Malvineous (2012-06-17 05:23:21)

    Ohhh, so you're saying it ignored nvidia, but tried to upgrade nvidia-utils.  nvidia-utils requires nvidia, but nvidia needs a specific version of nvidia-utils which would be broken by upgrading nvidia-utils, so it refuses to upgrade nvidia-utils because of the existing dependency.  Right.
    So then the second part of my question - how can I get around this without adding nvidia-utils as an IgnorePkg?  Can I tell pacman to just ignore it if the deps couldn't be satisfied and keep going with whatever's left?

  • [SOLVED] Pacman failed retrieving file 'core.db' after removing KDE

    Hey, I had to remove KDE and foolishly used the -Rsc flag. Now, trying to update yields:
    [root@Gal-PC2 gal]# pacman -Sy
    :: Synchronizing package databases...
    error: failed retrieving file 'core.db' from mirror.isoc.org.il : Resolving timed out after 10524 milliseconds
    error: failed retrieving file 'core.db' from mirror.us.leaseweb.net : Resolving timed out after 10523 milliseconds
    I tryed using the -Sy and -Syy flags to update the database, and made sure I am not using ipv6. I think the -Rsc flag might deleted an importent package. I can connect to the net, and I can acess mirrors using http and I can ping the mirrors. The error persists on a large number of mirrors. Any help will be appriciated.
    Last edited by Greenstuff (2015-02-08 20:49:24)

    Sorry, will do!
    The debug printed a lot of the first errors, so I cut them. This is what pacman --Syu --debug show:
    debug: adding new server URL to database 'multilib': [url]http://ftp.nluug.nl/pub/os/Linux/distr/archlinux/multilib/os/x86_64[/url]
    debug: adding new server URL to database 'multilib': [url]http://ftp.ds.hj.se/pub/os/linux/archlinux/multilib/os/x86_64[/url]
    debug: adding new server URL to database 'multilib': [url]http://ftp.uni-kl.de/pub/linux/archlinux/multilib/os/x86_64[/url]
    debug: adding new server URL to database 'multilib': [url]http://ftp.tu-chemnitz.de/pub/linux/archlinux/multilib/os/x86_64[/url]
    debug: adding new server URL to database 'multilib': [url]http://mirror.lnx.sk/pub/linux/archlinux/multilib/os/x86_64[/url]
    debug: adding new server URL to database 'multilib': [url]http://mirrors.st.uz/archlinux/multilib/os/x86_64[/url]
    debug: adding new server URL to database 'multilib': [url]http://mirrors.mithril.org.ua/linux/archlinux/multilib/os/x86_64[/url]
    debug: adding new server URL to database 'multilib': [url]http://piotrkosoft.net/pub/mirrors/ftp.archlinux.org/multilib/os/x86_64[/url]
    debug: adding new server URL to database 'multilib': [url]http://ftp.uni-bayreuth.de/linux/archlinux/multilib/os/x86_64[/url]
    debug: adding new server URL to database 'multilib': [url]http://artfiles.org/archlinux.org/multilib/os/x86_64[/url]
    debug: adding new server URL to database 'multilib': [url]http://repo.ukdw.ac.id/archlinux/multilib/os/x86_64[/url]
    debug: adding new server URL to database 'multilib': [url]http://linux.cs.nctu.edu.tw/archlinux/multilib/os/x86_64[/url]
    debug: adding new server URL to database 'multilib': [url]http://ftp.kaist.ac.kr/ArchLinux/multilib/os/x86_64[/url]
    debug: config: new section '(null)'
    debug: config: finished parsing /etc/pacman.conf
    :: Synchronizing package databases...
    debug: url: [url]http://mirror.isoc.org.il/pub/archlinux/core/os/x86_64/core.db[/url]
    debug: maxsize: 26214400
    debug: using time condition: 1422991262
    debug: opened tempfile for download: /var/lib/pacman/sync/core.db.part (wb)
    debug: curl returned error 28 from transfer
    error: failed retrieving file 'core.db' from mirror.isoc.org.il : Resolving timed out after 10523 milliseconds
    debug: url: [url]http://mirror.us.leaseweb.net/archlinux/core/os/x86_64/core.db[/url]
    debug: maxsize: 26214400
    debug: using time condition: 1422991262
    debug: opened tempfile for download: /var/lib/pacman/sync/core.db.part (wb)
    EDIT: SOLVED!
    Ok, so I did indeed disable ipv6 as I promised, but turns out I put in the GRUB kernel line "ipv6.disable_ipv6=1". Upon re-reading the wiki, turns out this means ipv6 is disabled but tunnels with ipv6 may be opened by programs. I changed to "ipv6.disable=1" and pacman updates away! I hope others will find this usefull. Be careful!
    Last edited by Greenstuff (2015-02-08 20:52:45)

  • [SOLVED] Pacman refuses to upgrade due to missing key

    Starting today, I get this error messge when trying to upgrade via pacman
    error: key "7A4E76095D8A52E4" could not be looked up remotely
    error: required key missing from keyring
    error: failed to commit transaction (unexpected error)
    Generating a fresh keyring (https://www.archlinux.org/news/gnupg-21 … n-keyring/) doesn't resolve the problem.
    Anyone else getting an error similar to this?
    Any ideas on resolving the issue?
    Last edited by ayr0 (2014-12-19 22:06:18)

    One should follow https://wiki.archlinux.org/index.php/Pa … mport_keys in case reinstalling pacman-keyring wouldn't sufice.
    Using unofficial repos? May have a sig-key, which may need to be re-added. https://wiki.archlinux.org/index.php/Un … positories
    eg for Graysky's repo-ck: https://bbs.archlinux.org/viewtopic.php … 1#p1485841

  • [Solved]Pacman fails on sync

    Hello there Archlinux folks!
    Today, my beloved little home server, running Arch, was a real pain in the ... and I had to realize, the fact: I need the help of ppl who understand this better than I do.
    As a related matter, I just bought a Network Media Player today, so I needed to modify my server a bit, like setup XBMC for upnp sharing, and Pacman showed me a "funny error message". With all due respect, I cannot reproduce the original anymore, - but it looked kinda same - since I tried to sync pacman with the repositories, and that somehow altered the current setup. Also tried to enable another repositories, but it did not helped.
    Now if I try to install something, like # pacman -S xbmc the following error message is triggered:
    [root@hoth estol]# pacman -S xbmc
    függőségek feloldása...
    belső ütközések keresése...
    Célok (79): recode-3.6-6 enca-1.13-1 libmp4v2-1.9.1-1 faac-1.28-2
    faad2-2.7-1 freetype2-2.4.4-2 fontconfig-2.8.0-1
    fribidi-0.19.2-1 xextproto-7.1.2-1 libxext-1.2.0-1
    libice-1.0.7-1 libsm-1.2.0-1 libxt-1.0.9-1 libxmu-1.1.0-1
    inputproto-2.0.1-1 libxi-1.4.1-1 libdrm-2.4.23-2
    xf86vidmodeproto-2.3.1-1 libxxf86vm-1.1.1-1 fixesproto-4.1.2-1
    libxfixes-4.0.5-1 damageproto-1.2.1-1 libxdamage-1.1.3-1
    libgl-7.10.0.git20110215-1 dri2proto-2.3-1 glproto-1.4.12-1
    mesa-7.10.0.git20110215-1 glew-1.5.8-1 freeglut-2.6.0-1
    jasper-1.900.1-6 libcddb-1.3.2-2 libcdio-0.82-1 libmad-0.15.1b-4
    libmms-0.6-1 libmpeg2-0.5.1-1 libvorbis-1.3.2-1
    alsa-lib-1.0.23-2 libsndfile-1.0.23-1 libsamplerate-0.1.7-1
    xineramaproto-1.2.1-1 libxinerama-1.1.1-1 renderproto-0.11.1-1
    libxrender-0.9.6-1 randrproto-1.3.2-1 libxrandr-1.3.1-1
    recordproto-1.14.1-1 libxtst-1.2.0-1 sdl-1.2.14-6
    sdl_image-1.2.10-2 libmikmod-3.1.12-3 smpeg-0.4.4-5
    sdl_mixer-1.2.11-2 wavpack-4.60.1-1 mesa-demos-8.0.1-1
    xf86dgaproto-2.1-1 libxxf86dga-1.1.2-1 compositeproto-0.4.2-1
    libxcomposite-0.4.3-1 dmxproto-2.3.1-1 libdmx-1.1.1-1
    xorg-xdpyinfo-1.2.0-1 xorg-xdriinfo-1.0.4-1 xorg-xev-1.1.0-1
    xorg-xlsatoms-1.1.0-1 xcb-util-0.3.6-1 xorg-xlsclients-1.1.1-1
    xorg-xprop-1.2.0-1 videoproto-2.3.1-1 libxv-1.0.6-1
    xorg-xvinfo-1.1.1-1 xorg-xwininfo-1.1.1-1 xorg-utils-7.6-6
    libmicrohttpd-0.9.7-1 libssh-0.4.8-1 libva-1.0.8-1
    libmodplug-0.8.8.1-1 rtmpdump-2.3-3 lsb-release-1.4-10
    xbmc-10.0-4
    Teljes letöltendő méret: 39,00 MB
    Teljes telepített méret: 133,01 MB
    Kezdődhet a telepítés? [I/n] I
    :: Csomagok letöltése a(z) extra repóból...
    hiba: nem sikerült a(z) 'recode-3.6-6-i686.pkg.tar.xz' fájlt letölteni a ftp.mfa.kfki.hu helyről : No address record
    hiba: nem sikerült a(z) 'enca-1.13-1-i686.pkg.tar.gz' fájlt letölteni a ftp.mfa.kfki.hu helyről : No address record
    ^Chiba: nem sikerült a(z) 'faad2-2.7-1-i686.pkg.tar.gz' fájlt letölteni a ftp.mfa.kfki.hu helyről : No address record
    Interrupt signal received
    Sorry about the language, it is localized for Hungarian.
    hint:
    hiba is for error
    letölteni is for download
    Teljes is for total
    Telepít(telepítés, telepített) is for install(installing, installed)
    Then I interrupt it, since it takes a long time.
    The most confusing part is, that even a simple management command - like # pacman -Syu - is also triggering an error:
    [root@hoth estol]# pacman -Syu
    :: A csomagadatbázisok szinkronizálása...
    hiba: nem sikerült a(z) 'core.db.tar.gz' fájlt letölteni a ftp.mfa.kfki.hu helyről : No address record
    hiba: nem sikerült a(z) core frissítése (No address record)
    ^Chiba: nem sikerült a(z) 'extra.db.tar.gz' fájlt letölteni a ftp.mfa.kfki.hu helyről : No address record
    Interrupt signal received
    Some technical details about the machine:
    [estol@hoth ~]$ uname -a
    Linux hoth 2.6.37-ARCH #1 SMP PREEMPT Fri Feb 18 16:58:42 UTC 2011 i686 Pentium III (Coppermine) GenuineIntel GNU/Linux
    [estol@hoth ~]$ cat /proc/cpuinfo
    processor : 0
    vendor_id : GenuineIntel
    cpu family : 6
    model : 8
    model name : Pentium III (Coppermine)
    stepping : 3
    cpu MHz : 747.685
    cache size : 256 KB
    fdiv_bug : no
    hlt_bug : no
    f00f_bug : no
    coma_bug : no
    fpu : yes
    fpu_exception : yes
    cpuid level : 2
    wp : yes
    flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pse36 mmx fxsr sse up
    bogomips : 1495.67
    clflush size : 32
    cache_alignment : 32
    address sizes : 36 bits physical, 32 bits virtual
    power management:
    Also the recent Pacman log,
    [2011-02-21 00:51] Running 'pacman -Syu'
    [2011-02-21 00:51] synchronizing package lists
    [2011-02-21 00:51] starting full system upgrade
    [2011-02-21 00:52] upgraded tzdata (2010o-1 -> 2011b-1)
    [2011-02-21 00:52] Generating locales...
    [2011-02-21 00:52] en_US.UTF-8... done
    [2011-02-21 00:52] en_US.ISO-8859-1... done
    [2011-02-21 00:52] hu_HU.UTF-8... done
    [2011-02-21 00:52] hu_HU.ISO-8859-2... done
    [2011-02-21 00:52] Generation complete.
    [2011-02-21 00:53] upgraded glibc (2.13-1 -> 2.13-4)
    [2011-02-21 00:53] warning: /etc/bash.bashrc installed as /etc/bash.bashrc.pacnew
    [2011-02-21 00:53] upgraded bash (4.1.009-3 -> 4.1.009-4)
    [2011-02-21 00:53] upgraded binutils (2.21-3 -> 2.21-4)
    [2011-02-21 00:53] upgraded curl (7.21.3-1 -> 7.21.4-2)
    [2011-02-21 00:53] upgraded db (5.1.19-3 -> 5.1.25-1)
    [2011-02-21 00:53] upgraded udev (165-1 -> 166-2)
    [2011-02-21 00:53] upgraded device-mapper (2.02.82-2 -> 2.02.84-1)
    [2011-02-21 00:53] >>> Updating module dependencies. Please wait ...
    [2011-02-21 00:53] >>> MKINITCPIO SETUP
    [2011-02-21 00:53] >>> ----------------
    [2011-02-21 00:53] >>> If you use LVM2, Encrypted root or software RAID,
    [2011-02-21 00:53] >>> Ensure you enable support in /etc/mkinitcpio.conf .
    [2011-02-21 00:53] >>> More information about mkinitcpio setup can be found here:
    [2011-02-21 00:53] >>> http://wiki.archlinux.org/index.php/Mkinitcpio
    [2011-02-21 00:53]
    [2011-02-21 00:53] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
    [2011-02-21 00:53] ==> Building image "default"
    [2011-02-21 00:53] ==> Running command: /sbin/mkinitcpio -k 2.6.37-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26.img
    [2011-02-21 00:53] :: Begin build
    [2011-02-21 00:53] :: Parsing hook [base]
    [2011-02-21 00:53] :: Parsing hook [udev]
    [2011-02-21 00:53] :: Parsing hook [autodetect]
    [2011-02-21 00:53] :: Parsing hook [pata]
    [2011-02-21 00:54] :: Parsing hook [scsi]
    [2011-02-21 00:54] :: Parsing hook [sata]
    [2011-02-21 00:54] :: Parsing hook [filesystems]
    [2011-02-21 00:54] :: Generating module dependencies
    [2011-02-21 00:54] :: Generating image '/boot/kernel26.img'...SUCCESS
    [2011-02-21 00:54] ==> SUCCESS
    [2011-02-21 00:54] ==> Building image "fallback"
    [2011-02-21 00:54] ==> Running command: /sbin/mkinitcpio -k 2.6.37-ARCH -c /etc/mkinitcpio.conf -g /boot/kernel26-fallback.img -S autodetect
    [2011-02-21 00:54] :: Begin build
    [2011-02-21 00:54] :: Parsing hook [base]
    [2011-02-21 00:54] :: Parsing hook [udev]
    [2011-02-21 00:54] :: Parsing hook [pata]
    [2011-02-21 00:54] :: Parsing hook [scsi]
    [2011-02-21 00:56] :: Parsing hook [sata]
    [2011-02-21 00:56] :: Parsing hook [filesystems]
    [2011-02-21 00:57] :: Generating module dependencies
    [2011-02-21 00:57] :: Generating image '/boot/kernel26-fallback.img'...SUCCESS
    [2011-02-21 00:57] ==> SUCCESS
    [2011-02-21 00:57] upgraded kernel26 (2.6.37-5 -> 2.6.37.1-1)
    [2011-02-21 00:57] upgraded libldap (2.4.23-1 -> 2.4.24-1)
    [2011-02-21 00:57] upgraded lvm2 (2.02.82-2 -> 2.02.84-1)
    [2011-02-21 00:57] upgraded mc (4.7.4-1 -> 4.7.5.1-1)
    [2011-02-21 00:57] warning: /etc/ntp.conf installed as /etc/ntp.conf.pacnew
    [2011-02-21 00:57] warning: /etc/conf.d/ntp-client.conf installed as /etc/conf.d/ntp-client.conf.pacnew
    [2011-02-21 00:57] upgraded ntp (4.2.6.p2-1 -> 4.2.6.p3-1)
    [2011-02-21 00:57] upgraded ppp (2.4.5-1 -> 2.4.5-2)
    [2011-02-21 00:57] upgraded syslog-ng (3.2.1-1 -> 3.2.2-1)
    [2011-02-21 00:57] upgraded vi (050325-3 -> 050325-4)
    [2011-02-21 00:57] upgraded wget (1.12-3 -> 1.12-4)
    [2011-02-21 19:57] Running 'pacman -U'
    [2011-03-04 19:42] Running 'pacman -S ushare'
    [2011-03-04 19:44] Running 'pacman -S ushare'
    [2011-03-04 19:44] Running 'pacman -S ushare'
    [2011-03-04 19:46] Running 'pacman -S ushare'
    [2011-03-04 19:46] Running 'pacman -S mediatomb'
    [2011-03-04 19:47] Running 'pacman -S mediatomb'
    [2011-03-04 19:49] Running 'pacman -S ushare'
    [2011-03-04 19:57] Running 'pacman -S ushare'
    [2011-03-04 20:00] Running 'pacman -S ushare'
    [2011-03-04 20:01] Running 'pacman -S ushare'
    [2011-03-04 20:08] Running 'pacman -S ushare'
    [2011-03-04 20:14] Running 'pacman -S ushare'
    [2011-03-04 20:16] Running 'pacman -S ushare'
    [2011-03-04 20:21] Running 'pacman -S ushare'
    [2011-03-04 21:05] Running 'pacman -S ushare'
    [2011-03-04 21:12] Running 'pacman -S ushare'
    [2011-03-04 21:13] Running 'pacman -S mediatomb'
    [2011-03-04 21:17] Running 'pacman -S ushare'
    [2011-03-04 22:51] Running 'pacman -S ushare'
    [2011-03-05 01:42] Running 'pacman -Sy xbmc'
    [2011-03-05 01:42] synchronizing package lists
    [2011-03-05 01:43] Running 'pacman -Syu'
    [2011-03-05 01:43] synchronizing package lists
    [2011-03-05 01:49] Running 'pacman -Syu'
    [2011-03-05 01:49] synchronizing package lists
    [2011-03-05 01:53] Running 'pacman -U'
    [2011-03-05 01:53] Running 'pacman -U'
    [2011-03-05 02:02] Running 'pacman -Syu'
    [2011-03-05 02:02] synchronizing package lists
    [2011-03-05 02:09] Running 'pacman -S xmbc'
    [2011-03-05 02:11] Running 'pacman -S xmbc'
    [2011-03-05 02:11] Running 'pacman -S xmbc'
    [2011-03-05 02:12] Running 'pacman -Syu'
    [2011-03-05 02:12] synchronizing package lists
    [2011-03-05 02:17] Running 'pacman -S xbmc'
    The first entry is the last known use of Pacman, that was successful.
    All help would be highly appreciated.
    estol
    Last edited by estol (2011-03-05 03:51:48)

    @skunktrader: yes, I tried, no it did not helped.
    @karol: mea culpa, mea maxima culpa, a friend of mine hooked me up with this distro, and set it to be hungarian as default, now I know how to change it - to be honest, this language annoys the crap out of me.
    @TigTex: yes, the host is alive, I can even browse the contents.
    Thanks for all the help, as it turned out, the problem was hardware related. Time to put her down.
    Last edited by estol (2011-03-05 03:52:39)

  • [Solved]Pacman fails to connect to server in Arch Virtual Machine

    Hi
    I've just installed arch 2008.06 in VMWare Workstation 6.04 on Vista Business x64. The setup all went fine and i am now logged into my system, but Pacman refuses to connect to anything. i have tried Bridged networking and NAT to no avail. whenever i run 'pacman -Syy' i get the message
    "error: failed retrieving file 'core.db.tar.gz' from ftp.archlinux.org : File unavailable (e.g.,file not found, no access)"
    followed by the same message for each mirror in my mirrorlist, and then again for 'extra.db.tar.gz' and 'community.db.tar.gz', and then 'failed to synchronise any databases' at the end.
    I have tried pinging google, as well as several of the arch mirrors and they all work fine. wget also seems to work fine, it's just pacman that's not working.
    Anyone have any suggestions?
    Last edited by henrypootel (2008-09-12 01:53:56)

    That's what i thought too so i switched off the Vista firewall and still no luck. I am behind a hardware firewall here at work, but it shouldn't be blocking FTP traffic. i use FTP in windows all the time.
    Just tried downloading a file using wget and it worked fine.
    Last edited by henrypootel (2008-09-11 03:45:29)

  • Pacman failing to upgrade

    I've been having some difficulties with my system that are nested many times over.
    I was following the instructions from the wiki here: Using mkinitcpio to put kernel back together
    But it was at the point where I was downloading important files with pacman that I receive the issue:
    package-query: package requires pacman<3.6
    That was fine until I just told pacman to upgrade itself and got the message:
    package-query: package requires pacman<3.6
    So I said to myself, all right, pacman is completely broken on top of things. So fix that. On the same wiki page: How to fix pacman if it is broken
    Following that advice, I download the packages openssl, libarchive and pacman and after consulting the linked script, manually tar -xvpf each file to root, minus the .PKGBUILD and .INSTALL files from each.
    The next line is:
    pacman -Sf openssl libarchive pacman
    And yet again, I receive the message:
    package-query: package requires pacman<3.6
    So I appear to still be at square one. And I still cannot seem to install mkinitcpio.
    Any advice or suggestions would be greatly appreciated, if I've overlooked some important and obvious fix somewhere in my googling, please point me in the right direction.
    Thanks.

    syntaxvorlon wrote:So I said to myself, all right, pacman is completely broken on top of things.
    How did you come to that conclusion? There is no breakage here - you simply have an unofficial package installed that depends on a particular version of pacman, so the error message is displayed when you try to upgrade pacman to a version higher than the one required.
    Also, the wiki link you posted relating to mkinitcpio describes a method of regenerating your initramfs image - it does not "put kernel back together".

  • [Solved] Pacman Failing to do -Syu

    Yesterday for no explicable reason, Pacman -Syu does not work. Installs work fine -S.
    Has anyone else experienced this?
    Log out put below. After entering the command it just sits there, does nothing, even after 5 mins, was thinking it may be the update server was overloaded and slow. Prior to yesterday updates were nearly instantaneous. I have reinstalled pacman, but same results. Once in awhile after 10 or so tries it will get the core files, then stop again, of course the lock file must be  removed after any attempts.
    [2011-06-03 11:29] Running 'pacman -Syu'
    [2011-06-03 11:29] synchronizing package lists
    SinOjos
    Last edited by sinojos (2011-06-05 08:05:38)

    sinojos wrote:
    On subject:
    I have tried switching mirrors as suggested in numerous places, that of course was the first thing I did before consulting anyone, as it seemed that the repository server was not being contacted. Unfortunately there is nothing in the log files, next to impossible to find the problem without errors to point to something.  I could compile the kernel for additional debugging purposes, not going to spend the time to find what is corrupted, a clean install can be faster, though I will have to re-install the packages I need, most of which I did from source because they are not in any repositories, some of my own making, some from other people, and others that are propriety. Going to give it a rest for now, will either reinstall or go to another flavor because it may be a case of corrupted file, difficult to find with no errors.
    I am also considering Slackware and LFS. I am thinking that LFS may be the best, since I always end up fixing what some package maintainer made a mistake on, so I might as well spend my time and money for myself rather than others and get told to sexually assault my mother, not a very good trade off. I am simply looking for a new minimal flavor for my extensive home network and some backup and monitoring servers in my home office. Since I have a business to run, spending hours each day or week fixing what should have not happened in the first place, is not an option. I started out with LFS in the mid 90's, played with Slack, used Suse for a bit in 1999 for business purposes, then Gentoo for the past 10 years for business and pleasure, first computer in 81. Since I need to run some programs that are self generated and or not available via any repository. I have the feeling LFS is going to be my final decision, since the fast easy route is usually not the best route and ends up taking more time in the long run, already spent hours on this error, could of done a LFS install and been running cleanly by now. Only hurdle with LFS is package managing, will have to see what is out their for LFS for which I can customize for my own needs, have not looked at LFS for many years.
    I am not saying that there is something wrong with Arch Linux, just that it may not be the right choice for my needs. My problem may simply be a corrupted file that has nothing to do with Arch Linux in it self, though I do wonder because if it was a corrupted file from the initial install,
    it should have presented itself right off the bat not a week later. Which leads to how did a file get corrupted, or how did it get mis-configured if I did not do it myself, I find nothing wrong with the disk, no bad blocks or any other application affected. Usually a number of applications will start to get affected if the disk starts going bad and starts corrupting files. If other Arch Linux users are not having the same problem, then it must be an isolated case. .
    Thank you to those that replied.
    LMAO Maki, I needed the laugh thanks.  My rant was/is reminiscent of the m$ anti Linux flooding on all forums, at least I kept it in the family kind of sort of. Do not get me started on m$, then you will see my real ugly side!
    Last reply to my rant:
    I apologize if I have offended anyone other than any Gentoo dev who is responsible for immoral actions and including the Gentoo Foundation members who practice, or  tolerate, or perhaps encourage such behavior.
    Yes I know I have not been nice, they pushed me over the edge and I lost it, who would not after being told to sexually assault your mother by some nose wiper who is barely out of their diapers and has no clue, when all you tried to do is help. Any time away from my work costs me money, I am not going to pay to be treated that way any longer, that was the last straw.  I am getting crusty and mean in my old age, you should see what my feet are starting to look like, don't worry it will happen to you to!
    OK thats all over with, subject closed.
    If any Admins feel anything else I have posted is inappropriate, I will be happy to remove it. Everything I have posted has been of my own action, and does not reflect the opinion of any other person alive, dead or fictitious.
    SinOjos
    i guess you meant no harm but try to stay on the topic, switch to a local mirror and try to do -Syu, LFS is not really a good choice for anything except home/hobby use, and you can make packages for any sotware using makepkg.

  • [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.

Maybe you are looking for