[SOLVED] Pacman complains ... (no, it was clyde)
After the update to pacman 3.4 and reading http://www.archlinux.org/news/503/, I updated my pacman.conf from the pacman.conf.pacnew and added the line
Architecture = i686
(tried "= auto" as well).
Pacman worked fine, but I had forgotten to update my mirrorlist as well -- until now.
With the new mirrorlist doing "pacman -Syu" I get:
error: The mirror 'ftp://mirror.aarnet.edu.au/pub/archlinux/$repo/os/$arch' contains the $arch variable, but no Architecture is defined.
error: The mirror 'ftp://mirror.aarnet.edu.au/pub/archlinux/$repo/os/$arch' contains the $arch variable, but no Architecture is defined.
error: The mirror 'ftp://mirror.aarnet.edu.au/pub/archlinux/$repo/os/$arch' contains the $arch variable, but no Architecture is defined.
:: Synchronizing package databases...
error: failed to update core (no servers configured for repository)
error: failed to update extra (no servers configured for repository)
error: failed to update community (no servers configured for repository)
(same for other mirrors).
Am I missing soemthing?
Last edited by JackH79 (2010-07-04 04:58:37)
As I said: I tried "auto" as well. Same result.
EDIT:
Oh the shame of it!!!!!!
Completely forgot that I had installed clyde to try it out (and I had an alias called 'pacman', which is why I didn't notice ). D'oh.
Sorry for the confusion.
Last edited by JackH79 (2010-07-04 04:57:26)
Similar Messages
-
[SOLVED]Pacman complains when trying to upgrade
Hello all.
Trying to run "pacman -Syu" I get the following errors:
error: failed to commit transaction (conflicting files)
kernel26-firmware: /lib/firmware/bnx2x-e1-4.8.53.0.fw exists in filesystem
kernel26-firmware: /lib/firmware/bnx2x-e1h-4.8.53.0.fw exists in filesystem
kernel26-firmware: /lib/firmware/cis/3CCFEM556.cis exists in filesystem
kernel26-firmware: /lib/firmware/cis/3CXEM556.cis exists in filesystem
kernel26-firmware: /lib/firmware/cxgb3/t3fw-7.4.0.bin exists in filesystem
Errors occurred, no packages were upgraded.
I suspected that it had something to do with an old custom kernel I'm not really using anymore, but not sure. Running "pacman -Qo" just gives:
error: No package owns /lib/firmware/bnx2x-e1-4.8.53.0.fw
Anyone had any ideas? Help much appreciated.
Last edited by rune0077 (2009-10-11 17:15:45)Yup, I just ran it with the force option and everything installed and upgraded fine.
Thanks. -
[SOLVED] Pacman unable to install packages due to invalid or corrup...
Hullo,
I know this is a common error judging by the results google lists for that subject. But all sollutions I found don't work for my specific case.
My battery died on my laptop and when I rebooted and tried to install a package pacman complained the database was locked (can't remember if I was installing something or else while my battery died, happend while I was away).
So since I've just rebooted I deleted the lock-file by hand. Now when ever I tried to install something it would complain:
error: xyz: signature from "xyz @ zyx" is unknown trust
:: File /var/cache/pacman/pkg/packagexyz.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package (PGP signature))
So I removed /etc/pacman.d/gnupg, cleared the package-cache and ran pacman-key --init:
gpg: /etc/pacman.d/gnupg/trustdb.gpg: trustdb created
gpg: no ultimately trusted keys found
gpg: Generating pacman keyring master key...
gpg: key B99666F8 marked as ultimately trusted
gpg: Done
==> Updating trust database...
gpg: 3 marginal(s) needed, 1 complete(s) needed, PGP trust model
gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u
followed by pacman-key --populate archlinux:
==> Appending keys from archlinux.gpg...
gpg: no valid OpenPGP data found.
==> Updating trust database...
gpg: no need for a trustdb check
and pacman-key --refresh-keys:
gpg: refreshing 1 key from hkp://pool.sks-keyservers.net
gpg: requesting key B99666F8 from hkp server pool.sks-keyservers.net
gpgkeys: key AA3E1E751B31AB9C2E6CDA64F2A911E7B99666F8 can't be retrieved
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
==> ERROR: A specified local key could not be updated from a keyserver.
It looks like it's not doing much. Anyway, trying to install packages or upgrading the system results in me having to import a bunch of keys and then failing with the before mentioned error.
Anything I can do?
Thanks
Last edited by hachel (2014-02-24 11:50:56)Rexilion wrote:Reinstall archlinux-keyring maybe? And then perform the commands you listed earlier.
Worked, thank you! -
Pacman complains after Gummiboot upgrade
Hi,
just updated to gummiboot 24-1 which replaced gummiboot-efi. After installation pacman complained:
File system /boot is not a FAT EFI System Partition (ESP) file system.
Fehler: Befehl konnte nicht korrekt ausgeführt werden (Error: Command not executed)
I just wonder why gummiboot assumes /boot to be a FAT ESP? I mount my ESP at /boot/efi, because I thought this is common practice. Furthermore which command was not executed? Anyhow system is booting normal, so not a big deal.
Last edited by tobsen (2013-03-05 19:00:27)65kid wrote:
srs5694 wrote:Imagine, for instance, one distribution setting up gummiboot on the ESP; then another one comes along and its installer decides that the ESP is too crowded, so it sets up gummiboot on a separate Freedesktop partition.
This is something that I would consider a buggy installer.
Perhaps -- but the Freedesktop spec creates more room for such bugs to be created than would other alternatives. All other things being equal (which I realize they aren't), it's better to have a spec that gives fewer opportunities for bugs in implementations than a spec that gives more opportunities for such bugs to breed.
Even if creating a separate ESP was a good idea, how would the installer even do that? It would have to shrink another partition first which is way too risky.
No, it wouldn't. An OS installer is presumably creating partition(s) for the OS, so that means that either the disk already has free space or an existing partition must be shrunk to make free space to install the OS. The second ESP or Freedesktop partition would just go in that free space. There's no rule that says that either the ESP or the Freedesktop partition must go before other partitions on the disk, although doing so is advisable because putting an ESP in the middle of the disk increases the odds that it will have to be moved in the future. Also, note that one of my points is that having two ESPs on a disk is inadvisable because Windows doesn't like such configurations; thus, I'd say that it's better to create a Freedesktop boot partition than a second ESP.
srs5694 wrote:Thus, the safest choice -- the one that's most likely to work with the greatest number of computers -- is to put the Linux boot loader (or a boot manager, at least) on the ESP, even if it's small, and put the kernel elsewhere.
But putting the kernel elsewhere is crazy for a simple reason: what if my root including the kernel is on an encrypted drive, RAID, LVM etc.?
I said "elsewhere," not "the Linux root (/) partition." In this context, "elsewhere" could easily be a separate Linux /boot partition, which can reside outside of the LVM or RAID, be unencrypted, be FAT, etc.
That's exactly what gummiboot is about - do only what the boot loader needs to do, let the kernel deal with the rest.
I would argue that "what the boot loader needs to do" should include "read partitions other than the one from which it was loaded." In the BIOS world, this pretty much goes without saying. In the EFI world, it's easier to create a boot loader that can read only from its own partition, but that will inevitably lead to problems on some systems and configurations.
And "the greatest number of computers" won't even care if their ESP is only 100MB, because they only use one OS. And whoever needs more should simply make the ESP big enough in the first place.
By "greatest number of computers" I meant the largest possible number, not the majority. Yes, the majority can probably make do with a 100MiB ESP, but to maximize usability, other configurations are more flexible and therefore preferable.
WonderWoofy wrote:I don understand why srs5694 includes the filesystem drivers in his rEFInd, but also understand your point about having the boot manager be as simple as possible like gummiboot.
Clearly there's a typo; I'm not sure if you mean you do understand or that you don't understand. In case it's the latter, it's because (a) they were available with the rEFIt source code and so could be (relatively) easily included with rEFInd; and (b) because including them in rEFInd greatly simplifies installing and using rEFInd on typical Fedora, Ubuntu, SUSE, and other distributions. These distributions typically either don't use LVM or use a separate ext2/3/4fs /boot partition. It's currently possible to download a Debian package or RPM of rEFInd, install it on one of these distributions, and have it all work without further tweaking, at least in most cases. (If the user uses XFS, JFS, Btrfs, or something else unusual to hold the kernel, this won't work without additional reconfiguration; but the default settings for these distributions put the kernel outside of LVM/RAID setups in ext4fs partitions.) In the end, this is partially labor saving for me, too; users tend to want things to Just Work, and when they don't, they e-mail me for help. Without those drivers, rEFInd does not Just Work on the more popular distributions, but with them, it does, so I spend less time answering e-mail.
It seems that the filesystem driver is optional and is only available if the necessary drivers are placed on the ESP.
rEFInd's filesystem drivers are implemented as separate binaries from rEFInd itself, so you can run rEFInd without using the drivers at all. Currently, the install.sh script (which I believe the Arch package omits) attempts to determine what filesystem is used on /boot and installs it, if necessary. If it's not necessary (say, if the filesystem is FAT), no filesystem driver gets installed unless the --alldrivers option is passed to install.sh. It's possible to use rEFInd's filesystem drivers without using rEFInd, but most EFIs lack support for loading filesystem drivers automatically, so the trick is to get them loaded.
65kid wrote:Modularity may be a good thing, duplicating logic still isn't, even if it's "just" a filesystem driver. The kernel already knows how to do it and it knows how to do it best, why waste effort duplicating the same logic into the bootloader?
Rudictio ad absurdum: The kernel already knows how to accept keyboard input, so why duplicate that functionality in a boot loader?
The answer is the same in both cases: Because it's necessary, or at least helpful, before the kernel loads.
I'm more than happy to admit that it's not necessary for the EFI or a boot loader to read Linux-specific filesystems if the user/installer sets up the computer with the kernel on a FAT filesystem. The problem is that in the real world, that conditional clause is often false. Note my earlier comments about Ubuntu, Fedora, etc. -- they all place their kernels on ext2/3/4 filesystems by default. Even many Arch users today have scripts and whatnot to copy their kernels to the ESP from /boot on some other filesystem. Yes, this becomes simpler if the ESP is mounted at /boot -- but as I've pointed out in this thread, doing this has its drawbacks, too, particularly when the user is a novice who hasn't thought things through or when using software (including third-party OSes) that set things up in a way that's not optimal for this type of configuration. I chose to fork rEFIt to rEFInd in order to glue together all the pieces I saw lying around that could almost handle the real-world situation. Now (as rEFInd) it can.
65kid wrote:I admit that I don't have a good understanding of how these EFI filesystem drivers work, but wouldn't you have also have to keep the EFI driver up-to-date separately?
Yes, but read-only filesystem drivers need little maintenance once they're stabilized. All of rEFInd's filesystem drivers are read-only, so they pose no real threats to your data.
WonderWoofy wrote:As far as updating the driver, I would imagine that this would be inclusive in the rEFInd updates. But moving the necessary files to the proper places might indeed be manual (rEFInd is not my primary boot manager, so I am not sure if there is automagic function to be included here).
The install.sh script included with rEFInd will update the driver(s) along with the rEFInd binary and icons. Unfortunately, the Arch packagers have chosen to omit this script from the Arch packages (or they had the last time I checked).
65kid wrote:I didn't mean to say that these EFI drivers are complete non-sense, whoever thinks this is the better approach or has a special usecase for it has the option and may use it. I personally just don't see the usecase
Given the relative market shares of Arch vs. Fedora or Arch vs. Ubuntu, it's really the Arch way of doing things that qualifies as the "special usecase." The drivers -- and especially the ext4fs driver -- help a lot with installing rEFInd on these distributions and getting it working painlessly.
progandy wrote:Simply support kernel on ESP, if Windows cannot deal with more than one ESP that is not our problem to solve. The user will have to resize the partition in this case.
Philosophically, you're right -- Windows' bugs and limitations belong to Microsoft. Practically, I'm afraid it's not that simple -- if John Doe installs Linux and then tries to re-install Windows and discovers that it flakes out because of something that Linux put on the hard disk, who will John blame? Maybe Microsoft, but maybe Linux. Furthermore, if a Linux developer knows that the Windows bug exists, is the developer justified in ignoring that bug, knowing that doing so will cause John Doe problems in the future? IMHO, the answer is "no" -- although with the caveat that the difficulty of finding a solution is a factor, too.
As to resizing the ESP, as I wrote in post #12 in this thread, you shouldn't do that unnecessarily, since it will almost certainly require deleting or resizing the first partition that follows the ESP, and in some cases a partition or two after that, as well. Resizing partitions from their start points is inherently dangerous, so any policy that requires doing this will damage somebody's filesystem. This is an even clearer case where developers' decisions can have negative consequences, and developers have a moral obligation to avoid causing such problems (such as data loss), even indirectly.
I'd just like to take a step back from all this to clarify my main point: The Freedesktop proposed loader spec is a worthwhile attempt to address certain problems with boot loaders as they're currently implemented in Linux. I agree with most of their goals and some of the details of that proposal. If it were implemented universally tomorrow, though, it would cause problems. The main reason is because of gummiboot's limitations, which seem to have motivated many of the proposal's details. (Let me say that I'm not trying to trash gummiboot here; I do respect it, but it also has limitations that have important implications when it's used as the core of a proposal like this one.) Consider:
An existing installation has Windows and an ESP that's too small. Under the Freedesktop guidelines, a new Freedesktop partition will be created and used to hold kernels. I don't believe the proposal is specific about where the boot loader must reside, but there are two choices: Put gummiboot on the ESP, in which case it can launch Windows but not Linux; or put gummiboot on the Freedesktop boot partition, where it can launch Linux but not Windows. In either case it's not very useful by itself. In the latter case, the EFI might not even launch it, since the Freedesktop partition isn't an ESP, and IIRC, the EFI spec doesn't require the EFI to be able to launch boot programs on a non-ESP.
Now, consider if gummiboot were modified to support booting from other partitions. The six Freedesktop rules could be cut by two (removing #4 and #6) and slightly amended (to make $BOOT always be a Freedesktop partition and never an ESP, and to permit multiple Freedesktop partitions per disk should the need arise). This will eliminate the problem I've just identified and simplify the rules that OS installers or administrators should follow, thus reducing the odds of bugs or different interpretations causing problems. Yes, it means that the Freedesktop developers will need to add some code to their boot loader. OTOH, this also means there will be:
Less ambiguity about what /boot is (the ESP vs. the Freedesktop boot partition) on any given system; this will lead to simpler code in support scripts and less chance of user error because of confusion or help from others based on false assumptions
Less chance of another OS altering or damaging the Linux boot loader files, thus improving overall system reliability
Less chance of creating a configuration in which gummiboot is incapable of booting some OSes that are legally installed
A need for fewer rules in the proposal, thereby reducing the odds of differing interpretations causing compatibility problems
Overall, I'd say these benefits are worth a few extra lines of code. -
[SOLVED] pacman libgl dependecy thing
Hello,
I have a weird problem. I recently tried to remove orphant packages using the following ocmmand:
pacman -Rsn $(pacman -Qdtq)
Maybe this was not to smart, anyway my system still works fine, but when I try to make a full system update I get:
root@crimson:~ # pacman -Suy
:: Starting full system upgrade...
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: cairo: requires libgl
:: dosbox: requires libgl
:: freeglut: requires libgl
:: glu: requires libgl
:: libva: requires libgl
:: mplayer: requires libgl
:: qt4: requires libgl
:: wxgtk: requires libgl
:: xorg-xdriinfo: requires libgl
It seems to be missing, since:
root@crimson:~ # pacman -Q libgl
error: package 'libgl' was not found
which stuns me, for this means the command I used to remove unused packages actually removed a package which was in use.
Anyway I tried to install the libgl package, but I have 4 options to choose:
root@crimson:~ # pacman -S libgl
:: There are 4 providers available for libgl:
:: Repository extra
1) mesa-libgl 2) nvidia-304xx-utils 3) nvidia-libgl
:: Repository community
4) catalyst-utils
Unfortunately each of them is in conflict with nvidia-utils. How can that be? libgl must have existed in my system before, doesn't it?
I don't really know how to fix this. If somebody has a clue or could help understand whats going on here I'd be really thankfull!
Regards,
Keen
Last edited by keen90 (2013-04-04 15:51:41)phil wrote:
# pacman -Syu nvidia-libgl
Should help!
This is already solved, and at the time the OP states that "# pacman -Suy" was used.
-- edit --
I stand corrected, ignore this noise.
Last edited by opt1mus (2013-04-04 16:57:18) -
[SOLVED] Pacman strange behavior from last system upgrade
Hi,
From last august, pacman complains when I try a system update.
He says that a lot of local packages are more recent than proposed:
# pacman -Syu
:: Synchronisation des bases de données de paquets...
core est à jour;
extra est à jour;
community est à jour;
:: Début de la mise à jour complète du système...
Avertissement: a52dec: la version locale (0.7.4-5) est plus récente que extra (0.7.4-4)
... #the full stdout is @ the end
Avertissement: usbutils: la version locale (004-1) est plus récente que core (0.87-1)
:: Remplacer util-linux par core/util-linux-ng ? [O/n] o
A depency error occurs if I answere 'O':
Avertissement: vde2: la version locale (2.3.1-1) est plus récente que extra (2.3-1)
... #the full stdout is @ the end
Avertissement: zlib: la version locale (1.2.5-4) est plus récente que core (1.2.5-2)
résolution des dépendances...
recherche des conflits entre paquets...
Erreur: la préparation de la transaction a échoué (la satisfaction des dépendances a échoué)
:: mkinitcpio: requiert util-linux>=2.19
The last good upgrade is on 2011.08.30:
[2011-08-18 22:32] Running '/usr/bin/pacman -Syu'
[2011-08-18 22:32] synchronizing package lists
[2011-08-18 22:32] starting full system upgrade
... #the full stdout is @ the end
[2011-08-30 23:43] Running '/usr/bin/pacman -Syu'
[2011-08-30 23:43] synchronizing package lists
[2011-08-30 23:44] starting full system upgrade
[2011-08-30 23:44] upgraded imagemagick (6.7.1.6-1 -> 6.7.2.1-1)
[2011-08-30 23:44] upgraded lzo2 (2.05-1 -> 2.06-1)
[2011-08-30 23:44] Running '/usr/bin/pacman -Scc'
Here is the full stdouts:
# pacman -Syu
:: Synchronisation des bases de données de paquets...
core est à jour;
extra est à jour;
community est à jour;
:: Début de la mise à jour complète du système...
Avertissement: a52dec: la version locale (0.7.4-5) est plus récente que extra (0.7.4-4)
Avertissement: aalib: la version locale (1.4rc5-8) est plus récente que extra (1.4rc5-6)
Avertissement: acl: la version locale (2.2.51-1) est plus récente que core (2.2.49-1)
Avertissement: acpi: la version locale (1.5-1) est plus récente que extra (1.4-2)
Avertissement: acpid: la version locale (2.0.10-2) est plus récente que extra (1.0.10-3)
Avertissement: acpitool: la version locale (0.5.1-3) est plus récente que community (0.5.1-1)
Avertissement: alsa-lib: la version locale (1.0.24.1-1) est plus récente que extra (1.0.23-1)
Avertissement: alsa-utils: la version locale (1.0.24.2-3) est plus récente que extra (1.0.23-2)
Avertissement: apr: la version locale (1.4.5-1) est plus récente que extra (1.4.2-1)
Avertissement: apr-util: la version locale (1.3.12-2) est plus récente que extra (1.3.9-4)
Avertissement: artwiz-fonts: la version locale (1.3-6) est plus récente que extra (1.3-5)
Avertissement: aspell: la version locale (0.60.6.1-1) est plus récente que extra (0.60.6-4)
Avertissement: atk: la version locale (2.0.1-1) est plus récente que extra (1.30.0-1)
Avertissement: attr: la version locale (2.4.46-1) est plus récente que core (2.4.44-1)
Avertissement: audacity: la version locale (1.3.13-1) est plus récente que extra (1.3.12-3)
Avertissement: aufs2-util: la version locale (20110314-1) est plus récente que extra (20100517-1)
Avertissement: autoconf: la version locale (2.68-1) est plus récente que core (2.66-2)
Avertissement: automake: la version locale (1.11.1-2) est plus récente que core (1.11.1-1)
Avertissement: avahi: la version locale (0.6.30-5) est plus récente que extra (0.6.25-3)
Avertissement: babl: la version locale (0.1.4-1) est plus récente que extra (0.1.2-1)
Avertissement: bash: la version locale (4.2.010-1) est plus récente que core (4.1.007-1)
Avertissement: bash-completion: la version locale (1.3-2) est plus récente que extra (1.2-1)
Avertissement: bin86: la version locale (0.16.18-1) est plus récente que core (0.16.17-4)
Avertissement: binutils: la version locale (2.21.1-2) est plus récente que core (2.20.1-3)
Avertissement: bison: la version locale (2.5-1) est plus récente que core (2.4.2-1)
Avertissement: bluez: la version locale (4.96-1) est plus récente que extra (4.69-1)
Avertissement: boost-libs: la version locale (1.47.0-1) est plus récente que extra (1.43.0-1)
Avertissement: bzip2: la version locale (1.0.6-1) est plus récente que core (1.0.5-5)
Avertissement: cabextract: la version locale (1.4-1) est plus récente que extra (1.2-2)
Avertissement: ca-certificates: la version locale (20110502-1) est plus récente que core (20090814-3)
Avertissement: cairo: la version locale (1.10.2-2) est plus récente que extra (1.8.10-1)
Avertissement: cairomm: la version locale (1.10.0-1) est plus récente que extra (1.8.4-1)
Avertissement: cdparanoia: la version locale (10.2-3) est plus récente que extra (10.2-2)
Avertissement: cdrkit: la version locale (1.1.11-1) est plus récente que extra (1.1.10-1)
Avertissement: chromium: la version locale (13.0.782.215-1) est plus récente que extra (5.0.375.99-1)
Avertissement: clamav: la version locale (0.97.2-1) est plus récente que extra (0.96.1-1)
Avertissement: compositeproto: la version locale (0.4.2-1) est plus récente que extra (0.4.1-1)
Avertissement: coreutils: la version locale (8.12-3) est plus récente que core (8.5-2)
Avertissement: cracklib: la version locale (2.8.18-1) est plus récente que core (2.8.16-1)
Avertissement: cryptsetup: la version locale (1.3.1-2) est plus récente que core (1.1.3-1)
Avertissement: ctags: la version locale (5.8-2) est plus récente que extra (5.8-1)
Avertissement: curl: la version locale (7.21.7-1) est plus récente que extra (7.21.0-1)
Avertissement: damageproto: la version locale (1.2.1-1) est plus récente que extra (1.2.0-1)
Avertissement: dash: la version locale (0.5.7-2) est plus récente que core (0.5.6.1-1)
Avertissement: db: la version locale (5.2.28-1) est plus récente que core (4.8.26-2)
Avertissement: dbus: la version locale (1.4.14-1) est plus récente que extra (1.2.24-1)
Avertissement: dbus-core: la version locale (1.4.14-1) est plus récente que core (1.2.24-1)
Avertissement: dbus-glib: la version locale (0.94-2) est plus récente que extra (0.86-1)
Avertissement: dcron: la version locale (4.5-2) est plus récente que core (4.4-2)
Avertissement: ddrescue: la version locale (1.14-1) est plus récente que extra (1.11-1)
Avertissement: desktop-file-utils: la version locale (0.18-1) est plus récente que extra (0.16-1)
Avertissement: device-mapper: la version locale (2.02.88-1) est plus récente que core (2.02.70-1)
Avertissement: dhcpcd: la version locale (5.2.12-1) est plus récente que core (5.2.5-1)
Avertissement: dia: la version locale (0.97.1-4) est plus récente que extra (0.97.1-1)
Avertissement: dialog: la version locale (1.1_20110707-1) est plus récente que core (1.1_20100428-1)
Avertissement: diffutils: la version locale (3.1-1) est plus récente que core (3.0-1)
Avertissement: django: la version locale (1.3-1) est plus récente que extra (1.2.1-1)
Avertissement: dmxproto: la version locale (2.3.1-1) est plus récente que extra (2.3-1)
Avertissement: dnsutils: la version locale (9.8.0.P4-1) est plus récente que core (9.6.1-3)
Avertissement: dosfstools: la version locale (3.0.11-1) est plus récente que extra (3.0.9-1)
Avertissement: dvdauthor: la version locale (0.7.0-1) est plus récente que extra (0.6.14-7)
Avertissement: e2fsprogs: la version locale (1.41.14-1) est plus récente que core (1.41.12-1)
Avertissement: ed: la version locale (1.5-2) est plus récente que core (1.4-2)
Avertissement: eject: la version locale (2.1.5-7) est plus récente que extra (2.1.5-4)
Avertissement: encfs: la version locale (1.7.4-5) est plus récente que community (1.6-1)
Avertissement: enchant: la version locale (1.6.0-3) est plus récente que extra (1.6.0-1)
Avertissement: epdfview: la version locale (0.1.8-1) est plus récente que extra (0.1.7-5)
Avertissement: eventlog: la version locale (0.2.12-2) est plus récente que core (0.2.12-1)
Avertissement: exiv2: la version locale (0.21.1-2) est plus récente que extra (0.19-1)
Avertissement: exo: la version locale (0.6.2-1) est plus récente que extra (0.3.107-1)
Avertissement: expat: la version locale (2.0.1-6) est plus récente que core (2.0.1-5)
Avertissement: faad2: la version locale (2.7-2) est plus récente que extra (2.7-1)
Avertissement: fakeroot: la version locale (1.17-1) est plus récente que core (1.14.4-2)
Avertissement: ffmpeg: la version locale (20110724-1) est plus récente que extra (24460-1)
Avertissement: ffmpegthumbnailer: la version locale (2.0.6-1) est plus récente que community (2.0.2-2)
Avertissement: file: la version locale (5.08-1) est plus récente que core (5.04-2)
Avertissement: filesystem: la version locale (2011.08-1) est plus récente que core (2010.02-4)
Avertissement: findutils: la version locale (4.4.2-3) est plus récente que core (4.4.2-2)
Avertissement: firefox: la version locale (6.0-1) est plus récente que extra (3.6.8-1)
Avertissement: firefox-i18n: la version locale (6.0-2) est plus récente que extra (3.6.8-1)
Avertissement: fixesproto: la version locale (5.0-1) est plus récente que extra (4.1.1-1)
Avertissement: flac: la version locale (1.2.1-3) est plus récente que extra (1.2.1-2)
Avertissement: flashplugin: la version locale (10.3.183.7-1) est plus récente que extra (10.1.53.64-1)
Avertissement: flex: la version locale (2.5.35-4) est plus récente que core (2.5.35-3)
Avertissement: fontsproto: la version locale (2.1.1-1) est plus récente que extra (2.1.0-1)
Avertissement: freerdp: la version locale (0.8.2-3) est plus récente que community (0.7.2-1)
Avertissement: freetype2: la version locale (2.4.6-1) est plus récente que extra (2.4.1-1)
Avertissement: fuse: la version locale (2.8.5-1) est plus récente que extra (2.8.4-2)
Avertissement: gamin: la version locale (0.1.10-5) est plus récente que community (0.1.10-2)
Avertissement: gawk: la version locale (4.0.0-1) est plus récente que core (3.1.8-1)
Avertissement: gc: la version locale (7.1-3) est plus récente que extra (7.1-1)
Avertissement: gcc: la version locale (4.6.1-4) est plus récente que core (4.5.0-6)
Avertissement: gcc-libs: la version locale (4.6.1-4) est plus récente que core (4.5.0-6)
Avertissement: gdbm: la version locale (1.8.3-8) est plus récente que core (1.8.3-7)
Avertissement: geany: la version locale (0.20-1) est plus récente que community (0.19-1)
Avertissement: gegl: la version locale (0.1.6-1) est plus récente que extra (0.1.2-1)
Avertissement: gen-init-cpio: la version locale (2.6.36-1) est plus récente que core (2.6.32-1)
Avertissement: gettext: la version locale (0.18.1.1-3) est plus récente que core (0.18.1.1-1)
Avertissement: ghostscript: la version locale (9.04-5) est plus récente que extra (8.71-3)
Avertissement: giflib: la version locale (4.1.6-4) est plus récente que extra (4.1.6-3)
Avertissement: gimp: la version locale (2.6.11-6) est plus récente que extra (2.6.9-1)
Avertissement: git: la version locale (1.7.6.1-1) est plus récente que extra (1.7.2-1)
Avertissement: glade: la version locale (3.10.0-2) est plus récente que extra (3.6.7-1)
Avertissement: glib2: la version locale (2.28.8-1) est plus récente que core (2.24.1-1)
Avertissement: glibc: la version locale (2.14-5) est plus récente que core (2.12-4)
Avertissement: glibmm: la version locale (2.28.2-1) est plus récente que extra (2.24.2-1)
Avertissement: gmp: la version locale (5.0.2-3) est plus récente que core (5.0.1-1)
Avertissement: gnome-disk-utility: la version locale (3.0.2-1) est plus récente que extra (2.30.1-1)
Avertissement: gnome-icon-theme: la version locale (3.0.0-2) est plus récente que extra (2.30.3-1)
Avertissement: gnupg: la version locale (1.4.11-3) est plus récente que extra (1.4.10-2)
Avertissement: gnutls: la version locale (3.0.1-1) est plus récente que extra (2.8.6-1)
Avertissement: gobject-introspection: la version locale (0.10.8-1) est plus récente que extra (0.6.14-1)
Avertissement: gpicview: la version locale (0.2.2-1) est plus récente que community (0.2.1-3)
Avertissement: gpm: la version locale (1.20.6-6) est plus récente que core (1.20.6-5)
Avertissement: grep: la version locale (2.9-1) est plus récente que core (2.6.3-1)
Avertissement: groff: la version locale (1.21-1) est plus récente que core (1.20.1-4)
Avertissement: grub: la version locale (0.97-20) est plus récente que core (0.97-17)
Avertissement: gsl: la version locale (1.15-1) est plus récente que extra (1.14-1)
Avertissement: gstreamer0.10: la version locale (0.10.35-1) est plus récente que extra (0.10.29-1)
Avertissement: gstreamer0.10-base: la version locale (0.10.35-1) est plus récente que extra (0.10.29-1)
Avertissement: gtk2: la version locale (2.24.5-3) est plus récente que extra (2.20.1-2)
Avertissement: gtk-engines: la version locale (2.20.2-1) est plus récente que extra (2.20.1-1)
Avertissement: gtkmm: la version locale (2.24.2-1) est plus récente que extra (2.20.3-1)
Avertissement: gtksourceview2: la version locale (2.10.5-1) est plus récente que extra (2.10.4-1)
Avertissement: gtk-vnc: la version locale (0.4.3-2) est plus récente que extra (0.3.10-1)
Avertissement: gv: la version locale (3.7.2-1) est plus récente que extra (3.7.1-1)
Avertissement: gvfs: la version locale (1.8.2-1) est plus récente que extra (1.6.3-1)
Avertissement: gvfs-smb: la version locale (1.8.2-1) est plus récente que extra (1.6.3-1)
Avertissement: gvim: la version locale (7.3.266-1) est plus récente que extra (7.2-1)
Avertissement: gzip: la version locale (1.4-2) est plus récente que core (1.4-1)
Avertissement: hdparm: la version locale (9.37-1) est plus récente que core (9.28-1)
Avertissement: hexedit: la version locale (1.2.12-4) est plus récente que extra (1.2.12-2)
Avertissement: hgsvn: la version locale (0.1.8-3) est plus récente que community (0.1.8-1)
Avertissement: hunspell: la version locale (1.3.2-1) est plus récente que extra (1.2.12-1)
Avertissement: hyphen: la version locale (2.7.1-2) est plus récente que extra (2.5-1)
Avertissement: icon-naming-utils: la version locale (0.8.90-2) est plus récente que extra (0.8.90-1)
Avertissement: icu: la version locale (4.8.1-1) est plus récente que extra (4.4.1-1)
Avertissement: imagemagick: la version locale (6.7.2.1-1) est plus récente que extra (6.6.2.10-1)
Avertissement: initscripts: la version locale (2011.07.3-1) est plus récente que core (2010.07-1)
Avertissement: inkscape: la version locale (0.48.2-1) est plus récente que extra (0.47-4)
Avertissement: inputproto: la version locale (2.0.2-1) est plus récente que extra (2.0-1)
Avertissement: intel-dri: la version locale (7.11-1) est plus récente que extra (7.8.2-1)
Avertissement: iproute2: la version locale (2.6.39-1) est plus récente que core (2.6.34-2)
Avertissement: iptables: la version locale (1.4.12-2) est plus récente que core (1.4.8-1)
Avertissement: iputils: la version locale (20101006-1) est plus récente que core (20100214-2)
Avertissement: ipython: la version locale (0.11-1) est plus récente que community (0.10-4)
Avertissement: jack: la version locale (0.121.2-2) est plus récente que extra (0.118.0-3)
Avertissement: jasper: la version locale (1.900.1-6) est plus récente que extra (1.900.1-5)
Avertissement: jdk: la version locale (7-3) est plus récente que community (6u20-1)
Avertissement: jre: la version locale (7-3) est plus récente que community (6u20-1)
Avertissement: kbd: la version locale (1.15.3-1) est plus récente que core (1.15.2-1)
Avertissement: kbproto: la version locale (1.0.5-1) est plus récente que extra (1.0.4-1)
Avertissement: lcms: la version locale (1.19-1) est plus récente que extra (1.18-3)
Avertissement: less: la version locale (444-1) est plus récente que core (436-1)
Avertissement: libao: la version locale (1.1.0-1) est plus récente que extra (1.0.0-2)
Avertissement: libarchive: la version locale (2.8.4-2) est plus récente que core (2.8.4-1)
Avertissement: libass: la version locale (0.9.13-1) est plus récente que extra (0.9.9-1)
Avertissement: libasyncns: la version locale (0.8-3) est plus récente que community (0.8-2)
Avertissement: libcanberra: la version locale (0.28-1) est plus récente que extra (0.23-1)
Avertissement: libcap: la version locale (2.22-1) est plus récente que core (2.19-1)
Avertissement: libcups: la version locale (1.4.8-2) est plus récente que extra (1.4.4-1)
Avertissement: libdatrie: la version locale (0.2.4-1) est plus récente que extra (0.2.3-1)
Avertissement: libdmx: la version locale (1.1.1-1) est plus récente que extra (1.1.0-1)
Avertissement: libdrm: la version locale (2.4.26-1) est plus récente que extra (2.4.21-1)
Avertissement: libdvdcss: la version locale (1.2.10-2) est plus récente que extra (1.2.10-1.1)
Avertissement: libedit: la version locale (20110802_3.0-1) est plus récente que extra (20090923_3.0-1)
Avertissement: libevent: la version locale (2.0.12-1) est plus récente que core (1.4.14b-1)
Avertissement: libexif: la version locale (0.6.20-1) est plus récente que extra (0.6.19-1)
Avertissement: libfetch: la version locale (2.33-3) est plus récente que core (2.32-1)
Avertissement: libffi: la version locale (3.0.10-1) est plus récente que extra (3.0.9-1)
Avertissement: libfontenc: la version locale (1.1.0-1) est plus récente que extra (1.0.5-1)
Avertissement: libftdi: la version locale (0.19-1) est plus récente que extra (0.18-1)
Avertissement: libgcrypt: la version locale (1.5.0-1) est plus récente que core (1.4.6-1)
Avertissement: libgl: la version locale (7.11-1) est plus récente que extra (7.8.2-1)
Avertissement: libglade: la version locale (2.6.4-2) est plus récente que extra (2.6.4-1)
Avertissement: libgnome-keyring: la version locale (3.0.3-1) est plus récente que extra (2.30.1-1)
Avertissement: libgpg-error: la version locale (1.10-1) est plus récente que core (1.7-3)
Avertissement: libgssglue: la version locale (0.3-1) est plus récente que core (0.1-2)
Avertissement: libice: la version locale (1.0.7-1) est plus récente que extra (1.0.6-1)
Avertissement: libid3tag: la version locale (0.15.1b-6) est plus récente que extra (0.15.1b-5)
Avertissement: libldap: la version locale (2.4.26-3) est plus récente que core (2.4.22-1)
Avertissement: libmad: la version locale (0.15.1b-5) est plus récente que extra (0.15.1b-4)
Avertissement: libmpc: la version locale (0.9-2) est plus récente que core (0.8.2-2)
Avertissement: libmpeg2: la version locale (0.5.1-3) est plus récente que extra (0.5.1-1)
Avertissement: libnotify: la version locale (0.7.4-1) est plus récente que extra (0.4.5-1.1)
Avertissement: libogg: la version locale (1.3.0-1) est plus récente que extra (1.2.0-1)
Avertissement: libpcap: la version locale (1.1.1-2) est plus récente que core (1.1.1-1)
Avertissement: libpciaccess: la version locale (0.12.1-1) est plus récente que extra (0.11.0-1)
Avertissement: libpng: la version locale (1.4.8-1) est plus récente que extra (1.4.3-1)
Avertissement: libproxy: la version locale (0.4.7-1) est plus récente que extra (0.3.1-1)
Avertissement: librsvg: la version locale (2.34.0-1) est plus récente que extra (2.26.3-1)
Avertissement: libsamplerate: la version locale (0.1.8-1) est plus récente que extra (0.1.7-1)
Avertissement: libsasl: la version locale (2.1.23-7) est plus récente que core (2.1.23-4)
Avertissement: libsigc++: la version locale (2.2.10-1) est plus récente que extra (2.2.8-1)
Avertissement: libsm: la version locale (1.2.0-1) est plus récente que extra (1.1.1-1)
Avertissement: libsndfile: la version locale (1.0.25-1) est plus récente que extra (1.0.21-1)
Avertissement: libsoup: la version locale (2.34.3-1) est plus récente que extra (2.30.2-1)
Avertissement: libsoup-gnome: la version locale (2.34.3-1) est plus récente que extra (2.30.2-1)
Avertissement: libtasn1: la version locale (2.9-1) est plus récente que extra (2.6-1)
Avertissement: libtextcat: la version locale (2.2-8) est plus récente que community (2.2-6)
Avertissement: libthai: la version locale (0.1.15-1) est plus récente que extra (0.1.14-1)
Avertissement: libtiff: la version locale (3.9.5-1) est plus récente que extra (3.9.4-1)
Avertissement: libtirpc: la version locale (0.2.2-2) est plus récente que core (0.2.1-1)
Avertissement: libtool: la version locale (2.4-4) est plus récente que core (2.2.10-1)
Avertissement: libusb: la version locale (1.0.8-1) est plus récente que core (0.1.12-4)
Avertissement: libva: la version locale (1.0.14-1) est plus récente que extra (0.31.0_p13-2)
Avertissement: libvdpau: la version locale (0.4.1-1) est plus récente que extra (0.4-1)
Avertissement: libvorbis: la version locale (1.3.2-1) est plus récente que extra (1.3.1-1)
Avertissement: libvpx: la version locale (0.9.7.p1-1) est plus récente que extra (0.9.1-1)
Avertissement: libwmf: la version locale (0.2.8.4-8) est plus récente que extra (0.2.8.4-7)
Avertissement: libwpd: la version locale (0.9.2-1) est plus récente que extra (0.8.14-1)
Avertissement: libx11: la version locale (1.4.4-1) est plus récente que extra (1.3.4-1)
Avertissement: libxau: la version locale (1.0.6-1) est plus récente que extra (1.0.5-1)
Avertissement: libxaw: la version locale (1.0.9-1) est plus récente que extra (1.0.7-1)
Avertissement: libxcb: la version locale (1.7-2) est plus récente que extra (1.6-1)
Avertissement: libxcomposite: la version locale (0.4.3-1) est plus récente que extra (0.4.2-1)
Avertissement: libxcursor: la version locale (1.1.12-1) est plus récente que extra (1.1.10-1)
Avertissement: libxdmcp: la version locale (1.1.0-1) est plus récente que extra (1.0.3-1)
Avertissement: libxext: la version locale (1.3.0-1) est plus récente que extra (1.1.2-1)
Avertissement: libxfce4util: la version locale (4.8.1-2) est plus récente que extra (4.6.2-1)
Avertissement: libxfixes: la version locale (5.0-1) est plus récente que extra (4.0.5-1)
Avertissement: libxfont: la version locale (1.4.4-1) est plus récente que extra (1.4.2-1)
Avertissement: libxft: la version locale (2.2.0-1) est plus récente que extra (2.1.14-1)
Avertissement: libxi: la version locale (1.4.3-1) est plus récente que extra (1.3-2)
Avertissement: libxinerama: la version locale (1.1.1-1) est plus récente que extra (1.1-1)
Avertissement: libxkbfile: la version locale (1.0.7-1) est plus récente que extra (1.0.6-1)
Avertissement: libxml2: la version locale (2.7.8-1) est plus récente que extra (2.7.7-1)
Avertissement: libxmu: la version locale (1.1.0-1) est plus récente que extra (1.0.5-1)
Avertissement: libxpm: la version locale (3.5.9-1) est plus récente que extra (3.5.8-1)
Avertissement: libxrandr: la version locale (1.3.2-1) est plus récente que extra (1.3.0-1)
Avertissement: libxslt: la version locale (1.1.26-2) est plus récente que extra (1.1.26-1)
Avertissement: libxss: la version locale (1.2.1-1) est plus récente que extra (1.2.0-1)
Avertissement: libxt: la version locale (1.1.1-1) est plus récente que extra (1.0.8-1)
Avertissement: libxtst: la version locale (1.2.0-1) est plus récente que extra (1.1.0-1)
Avertissement: libxv: la version locale (1.0.6-1) est plus récente que extra (1.0.5-1)
Avertissement: libxvmc: la version locale (1.0.6-1) est plus récente que extra (1.0.5-1)
Avertissement: libxxf86dga: la version locale (1.1.2-1) est plus récente que extra (1.1.1-1)
Avertissement: libxxf86vm: la version locale (1.1.1-1) est plus récente que extra (1.1.0-1)
Avertissement: licenses: la version locale (2.8-1) est plus récente que core (2.6-1)
Avertissement: linux-api-headers: la version locale (3.0.1-1) est plus récente que core (2.6.34-1)
Avertissement: linux-firmware: la version locale (20110727-1) est plus récente que core (20100623-2)
Avertissement: lirc-utils: la version locale (1:0.9.0-6) est plus récente que extra (0.8.6-3)
Avertissement: logrotate: la version locale (3.8.0-2) est plus récente que core (3.7.8-1)
Avertissement: lpsolve: la version locale (5.5.2.0-1) est plus récente que extra (5.5.0.15-1)
Avertissement: lshw: la version locale (B.02.15-1) est plus récente que community (B.02.14-2)
Avertissement: lsof: la version locale (4.84-3) est plus récente que extra (4.83-1)
Avertissement: lua: la version locale (5.1.4-6) est plus récente que extra (5.1.4-5)
Avertissement: lvm2: la version locale (2.02.88-1) est plus récente que core (2.02.70-1)
Avertissement: lzo2: la version locale (2.06-1) est plus récente que core (2.03-1)
Avertissement: lzop: la version locale (1.03-1) est plus récente que extra (1.02rc1-4)
Avertissement: m4: la version locale (1.4.16-1) est plus récente que core (1.4.14-2)
Avertissement: make: la version locale (3.82-3) est plus récente que core (3.81-5)
Avertissement: man-db: la version locale (2.6.0.2-2) est plus récente que core (2.5.7-1)
Avertissement: man-pages: la version locale (3.32-1) est plus récente que core (3.25-1)
Avertissement: mdadm: la version locale (3.2.2-3) est plus récente que core (3.1.2-2)
Avertissement: meld: la version locale (1.5.2-1) est plus récente que extra (1.3.1-2)
Avertissement: mercurial: la version locale (1.9.2-1) est plus récente que extra (1.6-1)
Avertissement: mesa: la version locale (7.11-1) est plus récente que extra (7.8.2-1)
Avertissement: mime-types: la version locale (8-1) est plus récente que extra (1.0-3)
Avertissement: mkinitcpio: la version locale (0.7.2-1) est plus récente que core (0.6.7-1)
Avertissement: mkinitcpio-busybox: la version locale (1.18.5-1) est plus récente que core (1.16.2-1)
Avertissement: mlocate: la version locale (0.24-1) est plus récente que core (0.22.4-1)
Avertissement: moc: la version locale (20110528-3) est plus récente que extra (2.4.4-2)
Avertissement: module-init-tools: la version locale (3.16-1) est plus récente que core (3.11.1-2)
Avertissement: mpfr: la version locale (3.0.1.p4-2) est plus récente que core (3.0.0-1)
Avertissement: mpg123: la version locale (1.13.3-2) est plus récente que extra (1.12.3-1)
Avertissement: mplayer: la version locale (34007-1) est plus récente que extra (31774-1)
Avertissement: namcap: la version locale (3.1-1) est plus récente que extra (2.6-1)
Avertissement: nano: la version locale (2.2.6-1) est plus récente que core (2.2.4-1)
Avertissement: nbd: la version locale (2.9.23-1) est plus récente que community (2.9.15-1)
Avertissement: ncurses: la version locale (5.9-1) est plus récente que core (5.7-3)
Avertissement: neon: la version locale (0.29.6-2) est plus récente que extra (0.29.3-2)
Avertissement: netpbm: la version locale (10.47.24-1) est plus récente que extra (10.47.16-1)
Avertissement: net-tools: la version locale (1.60-18) est plus récente que core (1.60-14)
Avertissement: nmap: la version locale (5.51-1) est plus récente que extra (5.21-2)
Avertissement: nspr: la version locale (4.8.9-1) est plus récente que extra (4.8.4-1)
Avertissement: nss: la version locale (3.12.11-1) est plus récente que extra (3.12.6-3)
Avertissement: ntfs-3g: la version locale (2011.4.12-1) est plus récente que extra (2010.5.22-1)
Avertissement: obconf: la version locale (2.0.3.git20100309-2) est plus récente que extra (2.0.3-3)
Avertissement: openbox: la version locale (3.5.0-4) est plus récente que extra (3.4.11.2-1)
Avertissement: openssh: la version locale (5.8p2-9) est plus récente que core (5.5p1-1)
Avertissement: openssl: la version locale (1.0.0.d-1) est plus récente que core (1.0.0.a-2)
Avertissement: orc: la version locale (0.4.14-1) est plus récente que extra (0.4.6-1)
Avertissement: p7zip: la version locale (9.20.1-4) est plus récente que extra (9.13-2)
Avertissement: pacman: la version locale (3.5.4-4) est plus récente que core (3.4.0-2)
Avertissement: pacman-mirrorlist: la version locale (20110816-1) est plus récente que core (20100621-1)
Avertissement: pam: la version locale (1.1.4-1) est plus récente que core (1.1.1-1)
Avertissement: pango: la version locale (1.28.4-3) est plus récente que extra (1.28.1-1)
Avertissement: pangomm: la version locale (2.28.1-1) est plus récente que extra (2.26.2-1)
Avertissement: parted: la version locale (3.0-3) est plus récente que extra (2.3-1)
Avertissement: patch: la version locale (2.6.1-2) est plus récente que core (2.6.1-1)
Avertissement: pciutils: la version locale (3.1.7-4) est plus récente que core (3.1.7-1)
Avertissement: pcmciautils: la version locale (018-1) est plus récente que core (017-1)
Avertissement: pcre: la version locale (8.13-2) est plus récente que core (8.10-1)
Avertissement: perl: la version locale (5.14.1-3) est plus récente que core (5.10.1-5)
Avertissement: perl-error: la version locale (0.17016-2) est plus récente que extra (0.17016-1)
Avertissement: perl-xml-parser: la version locale (2.41-1) est plus récente que extra (2.36-6)
Avertissement: perl-xml-simple: la version locale (2.18-3) est plus récente que extra (2.18-2)
Avertissement: pixman: la version locale (0.22.2-1) est plus récente que extra (0.18.2-1)
Avertissement: pkg-config: la version locale (0.26-1) est plus récente que core (0.25-2)
Avertissement: polkit: la version locale (0.101-2) est plus récente que extra (0.96-2)
Avertissement: poppler: la version locale (0.16.7-1) est plus récente que extra (0.14.0-1)
Avertissement: poppler-data: la version locale (0.4.4-1) est plus récente que extra (0.4.2-1)
Avertissement: poppler-glib: la version locale (0.16.7-1) est plus récente que extra (0.14.0-1)
Avertissement: popt: la version locale (1.16-3) est plus récente que core (1.16-2)
Avertissement: powertop: la version locale (1.13-2) est plus récente que community (1.11-2)
Avertissement: ppl: la version locale (0.11.2-2) est plus récente que core (0.10.2-3)
Avertissement: procinfo-ng: la version locale (2.0.304-2) est plus récente que core (2.0.304-1)
Avertissement: procps: la version locale (3.2.8-4) est plus récente que core (3.2.8-1)
Avertissement: psmisc: la version locale (22.14-1) est plus récente que core (22.11-1)
Avertissement: pv: la version locale (1.2.0-1) est plus récente que community (1.1.4-4)
Avertissement: pygobject: la version locale (2.28.6-1) est plus récente que extra (2.21.3-1)
Avertissement: pygtk: la version locale (2.24.0-2) est plus récente que extra (2.17.0-1)
Avertissement: pygtksourceview2: la version locale (2.10.1-3) est plus récente que extra (2.10.1-1)
Avertissement: python: la version locale (3.2.1-1) est plus récente que extra (2.6.5-3)
Avertissement: python-lxml: la version locale (2.3-1) est plus récente que extra (2.2.6-1)
Avertissement: python-pexpect: la version locale (2.3-4) est plus récente que community (2.3-3)
Avertissement: python-pychart: la version locale (1.39-5) est plus récente que community (1.39-4)
Avertissement: python-pypdf: la version locale (1.13-1) est plus récente que community (1.12-4)
Avertissement: python-reportlab: la version locale (2.5-1) est plus récente que community (2.4-1)
Avertissement: python-virtualenv: la version locale (1.6.4-1) est plus récente que extra (1.4.9-1)
Avertissement: pyxml: la version locale (0.8.4-8) est plus récente que extra (0.8.4-6)
Avertissement: qemu-kvm: la version locale (0.15.0-2) est plus récente que extra (0.12.4-2)
Avertissement: randrproto: la version locale (1.3.2-1) est plus récente que extra (1.3.1-1)
Avertissement: raptor: la version locale (2.0.4-1) est plus récente que extra (1.4.21-1)
Avertissement: rasqal: la version locale (1:0.9.27-1) est plus récente que extra (0.9.19-2)
Avertissement: rdesktop: la version locale (1.7.0-2) est plus récente que extra (1.6.0-5)
Avertissement: readline: la version locale (6.2.001-2) est plus récente que core (6.1.002-1)
Avertissement: recode: la version locale (3.6-6) est plus récente que extra (3.6-5)
Avertissement: recordproto: la version locale (1.14.1-1) est plus récente que extra (1.14-1)
Avertissement: redland: la version locale (1:1.0.14-1) est plus récente que extra (1.0.10-2)
Avertissement: renderproto: la version locale (0.11.1-1) est plus récente que extra (0.11-1)
Avertissement: rsync: la version locale (3.0.8-2) est plus récente que extra (3.0.7-1)
Avertissement: ruby: la version locale (1.9.2_p290-1) est plus récente que extra (1.9.1_p429-1)
Avertissement: run-parts: la version locale (4.0.2-1) est plus récente que core (3.2.3-1)
Avertissement: sakura: la version locale (2.4.2-1) est plus récente que community (2.3.8-1)
Avertissement: schroedinger: la version locale (1.0.10-1) est plus récente que extra (1.0.9-1)
Avertissement: scrnsaverproto: la version locale (1.2.1-1) est plus récente que extra (1.2.0-1)
Avertissement: sdl: la version locale (1.2.14-7) est plus récente que extra (1.2.14-5)
Avertissement: sdparm: la version locale (1.06-1) est plus récente que core (1.05-1)
Avertissement: sed: la version locale (4.2.1-3) est plus récente que core (4.2.1-2)
Avertissement: sg3_utils: la version locale (1.30-1) est plus récente que extra (1.29-1)
Avertissement: shadow: la version locale (4.1.4.3-2) est plus récente que core (4.1.4.2-3)
Avertissement: shared-mime-info: la version locale (0.90-1) est plus récente que extra (0.71-1)
Avertissement: slim: la version locale (1.3.2-5) est plus récente que extra (1.3.1-7)
Avertissement: slock: la version locale (0.9-6) est plus récente que community (0.9-3)
Avertissement: smbclient: la version locale (3.6.0-8) est plus récente que extra (3.5.4-1)
Avertissement: soundtouch: la version locale (1.6.0-1) est plus récente que extra (1.5.0-1)
Avertissement: sox: la version locale (14.3.2-3) est plus récente que extra (14.3.1-2)
Avertissement: sqlite3: la version locale (3.7.7.1-1) est plus récente que core (3.6.23.1-1)
Avertissement: squashfs-tools: la version locale (4.2-1) est plus récente que extra (4.0-3)
Avertissement: sshfs: la version locale (2.3-1) est plus récente que extra (2.2-3)
Avertissement: startup-notification: la version locale (0.12-1) est plus récente que extra (0.10-1)
Avertissement: stunnel: la version locale (4.39-1) est plus récente que community (4.33-1)
Avertissement: subversion: la version locale (1.6.17-6) est plus récente que extra (1.6.9-5)
Avertissement: sudo: la version locale (1.8.2-1) est plus récente que core (1.7.3-1)
Avertissement: sysfsutils: la version locale (2.1.0-6) est plus récente que core (2.1.0-5)
Avertissement: syslinux: la version locale (4.04-2) est plus récente que extra (4.02-1)
Avertissement: syslog-ng: la version locale (3.2.4-3) est plus récente que core (3.1.1-1)
Avertissement: sysvinit: la version locale (2.88-2) est plus récente que core (2.86-5)
Avertissement: talloc: la version locale (2.0.5-1) est plus récente que extra (2.0.1-1)
Avertissement: tar: la version locale (1.26-1) est plus récente que core (1.23-3)
Avertissement: tcpdump: la version locale (4.1.1-2) est plus récente que extra (4.1.1-1)
Avertissement: tcp_wrappers: la version locale (7.6-12) est plus récente que core (7.6-11)
Avertissement: tdb: la version locale (1.2.9-1) est plus récente que extra (1.2.1-1)
Avertissement: texinfo: la version locale (4.13a-5) est plus récente que core (4.13a-4)
Avertissement: thunar: la version locale (1.2.2-3) est plus récente que extra (1.0.2-1)
Avertissement: thunar-archive-plugin: la version locale (0.3.0-1) est plus récente que extra (0.2.4-6)
Avertissement: thunar-volman: la version locale (0.6.0-2) est plus récente que extra (0.3.80-1)
Avertissement: transcode: la version locale (1.1.5-5) est plus récente que extra (1.1.5-4)
Avertissement: transmission-gtk: la version locale (2.33-1) est plus récente que extra (2.03-1)
Avertissement: tree: la version locale (1.6.0-1) est plus récente que extra (1.5.3-1)
Avertissement: ttf-dejavu: la version locale (2.33-1) est plus récente que extra (2.30-2)
Avertissement: ttf-freefont: la version locale (20100919-1) est plus récente que extra (20090104-2)
Avertissement: tzdata: la version locale (2011h-1) est plus récente que core (2010j-1)
Avertissement: udev: la version locale (173-3) est plus récente que core (160-1)
Avertissement: udisks: la version locale (1.0.4-1) est plus récente que extra (1.0.1-4)
Avertissement: uml_utilities: la version locale (20070815-4) est plus récente que extra (20070815-3)
Avertissement: unrar: la version locale (4.0.7-1) est plus récente que extra (3.9.10-1)
Avertissement: usbutils: la version locale (004-1) est plus récente que core (0.87-1)
:: Remplacer util-linux par core/util-linux-ng ? [O/n] o
Avertissement: vde2: la version locale (2.3.1-1) est plus récente que extra (2.3-1)
Avertissement: videoproto: la version locale (2.3.1-1) est plus récente que extra (2.3.0-1)
Avertissement: vim-runtime: la version locale (7.3.266-1) est plus récente que extra (7.2-1)
Avertissement: vpnc: la version locale (0.5.3.svn457-1) est plus récente que core (0.5.3-2)
Avertissement: vte: la version locale (0.28.2-1) est plus récente que extra (0.24.3-1)
Avertissement: wget: la version locale (1.13.1-1) est plus récente que core (1.12-2)
Avertissement: which: la version locale (2.20-4) est plus récente que core (2.20-3)
Avertissement: wine: la version locale (1.3.27-1) est plus récente que community (1.2-1)
Avertissement: wireless-regdb: la version locale (2010.11.24-1) est plus récente que core (2009.11.25-1)
Avertissement: wireless_tools: la version locale (29-4) est plus récente que core (29-3)
Avertissement: wpa_supplicant: la version locale (0.7.3-3) est plus récente que core (0.6.10-2)
Avertissement: wxgtk: la version locale (2.8.12.1-1) est plus récente que extra (2.8.11-1)
Avertissement: x11vnc: la version locale (0.9.12-1) est plus récente que extra (0.9.10-1)
Avertissement: x264: la version locale (20110617-1) est plus récente que extra (20100722-1)
Avertissement: xarchiver: la version locale (0.5.2-4) est plus récente que extra (0.5.2-1)
Avertissement: xaw3d: la version locale (1.5E-3) est plus récente que extra (1.5E-2)
Avertissement: xbitmaps: la version locale (1.1.1-1) est plus récente que extra (1.1.0-1)
Avertissement: xcb-proto: la version locale (1.6-2) est plus récente que extra (1.6-1)
Avertissement: xdg-utils: la version locale (1.1.0rc1-3) est plus récente que extra (1.0.2.20100618-1)
Avertissement: xextproto: la version locale (7.2.0-1) est plus récente que extra (7.1.1-1)
Avertissement: xf86-input-evdev: la version locale (2.6.0-3) est plus récente que extra (2.4.0-1)
Avertissement: xf86-input-keyboard: la version locale (1.6.0-2) est plus récente que extra (1.4.0-2)
Avertissement: xf86-input-mouse: la version locale (1.7.1-1) est plus récente que extra (1.5.0-2)
Avertissement: xf86-input-synaptics: la version locale (1.4.1-1) est plus récente que extra (1.2.2-2)
Avertissement: xf86-video-fbdev: la version locale (0.4.2-4) est plus récente que extra (0.4.2-1)
Avertissement: xf86-video-intel: la version locale (2.15.0-2) est plus récente que extra (2.12.0-1)
Avertissement: xf86-video-vesa: la version locale (2.3.0-5) est plus récente que extra (2.3.0-2)
Avertissement: xf86vidmodeproto: la version locale (2.3.1-1) est plus récente que extra (2.3-1)
Avertissement: xfconf: la version locale (4.8.0-2) est plus récente que extra (4.6.2-1)
Avertissement: xineramaproto: la version locale (1.2.1-1) est plus récente que extra (1.2-1)
Avertissement: xkeyboard-config: la version locale (2.2.1-1) est plus récente que extra (1.8-1)
Avertissement: xorg-docs: la version locale (1.6-1) est plus récente que extra (1.5-1)
Avertissement: xorg-fonts-encodings: la version locale (1.0.4-1) est plus récente que extra (1.0.3-1)
Avertissement: xorg-font-utils: la version locale (7.6-2) est plus récente que extra (7.5-2)
Avertissement: xorg-server: la version locale (1.10.3.901-1) est plus récente que extra (1.8.1.902-1)
Avertissement: xorg-server-utils: la version locale (7.6-2) est plus récente que extra (7.5-4)
Avertissement: xorg-twm: la version locale (1.0.7-1) est plus récente que extra (1.0.4-3)
Avertissement: xorg-utils: la version locale (7.6-7) est plus récente que extra (7.6-2)
Avertissement: xorg-xauth: la version locale (1.0.6-1) est plus récente que extra (1.0.4-1)
Avertissement: xorg-xinit: la version locale (1.3.0-3) est plus récente que extra (1.2.1-1)
Avertissement: xproto: la version locale (7.0.22-1) est plus récente que extra (7.0.17-1)
Avertissement: xterm: la version locale (271-1) est plus récente que extra (259-1)
Avertissement: xvidcore: la version locale (1.3.2-1) est plus récente que extra (1.2.2-1)
Avertissement: xz: la version locale (5.0.3-1) est plus récente que core (4.999.9beta-5)
Avertissement: zenity: la version locale (3.0.0-2) est plus récente que extra (2.30.0-1)
Avertissement: zip: la version locale (3.0-2) est plus récente que extra (3.0-1.1)
Avertissement: zlib: la version locale (1.2.5-4) est plus récente que core (1.2.5-2)
résolution des dépendances...
recherche des conflits entre paquets...
Erreur: la préparation de la transaction a échoué (la satisfaction des dépendances a échoué)
:: mkinitcpio: requiert util-linux>=2.19
# cat pacman.log
[2009-11-24 23:34] installed filesystem (2009.07-1)
[2011-08-18 22:32] Running '/usr/bin/pacman -Syu'
[2011-08-18 22:32] synchronizing package lists
[2011-08-18 22:32] starting full system upgrade
[2011-08-18 22:36] upgraded nettle (2.1-1 -> 2.2-1)
[2011-08-18 22:36] upgraded gnutls (2.12.7-2 -> 3.0.0-2)
[2011-08-18 22:36] upgraded libcups (1.4.8-1 -> 1.4.8-2)
[2011-08-18 22:36] upgraded freerdp (0.8.2-2 -> 0.8.2-3)
[2011-08-18 22:36] upgraded glib-networking (2.28.7-1 -> 2.28.7-4)
[2011-08-18 22:36] upgraded gtk-vnc (0.4.3-1 -> 0.4.3-2)
[2011-08-18 22:36] >>>
[2011-08-18 22:36] >>> If you use the LILO bootloader, you should run 'lilo' before rebooting.
[2011-08-18 22:36] >>>
[2011-08-18 22:36] >>> Updating module dependencies. Please wait ...
[2011-08-18 22:36] >>> Generating initial ramdisk, using mkinitcpio. Please wait...
[2011-08-18 22:36] ==> Building image from preset: 'default'
[2011-08-18 22:36] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2011-08-18 22:36] ==> Starting build: 3.0-ARCH
[2011-08-18 22:36] -> Parsing hook: [base]
[2011-08-18 22:36] -> Parsing hook: [udev]
[2011-08-18 22:36] -> Parsing hook: [sata]
[2011-08-18 22:36] -> Parsing hook: [encrypt]
[2011-08-18 22:36] ==> Generating module dependencies
[2011-08-18 22:36] ==> Creating gzip initcpio image: /boot/initramfs-linux.img
[2011-08-18 22:36] 10623 blocks
[2011-08-18 22:36] ==> Image generation successful
[2011-08-18 22:36] ==> Building image from preset: 'fallback'
[2011-08-18 22:36] -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2011-08-18 22:36] ==> Starting build: 3.0-ARCH
[2011-08-18 22:36] -> Parsing hook: [base]
[2011-08-18 22:36] -> Parsing hook: [udev]
[2011-08-18 22:36] -> Parsing hook: [sata]
[2011-08-18 22:36] -> Parsing hook: [encrypt]
[2011-08-18 22:36] ==> Generating module dependencies
[2011-08-18 22:36] ==> Creating gzip initcpio image: /boot/initramfs-linux-fallback.img
[2011-08-18 22:36] 10623 blocks
[2011-08-18 22:36] ==> Image generation successful
[2011-08-18 22:36] upgraded linux (3.0.2-1 -> 3.0.3-1)
[2011-08-18 22:36] upgraded linux-headers (3.0.2-1 -> 3.0.3-1)
[2011-08-18 22:36] >>> PLEASE READ FOR KVM USAGE!
[2011-08-18 22:36] >>> Load the correct KVM module, you will need a KVM capable CPU!
[2011-08-18 22:36] >>> Add yourself to the group 'kvm'.
[2011-08-18 22:36] >>> Use 'qemu-kvm -enable-kvm' to use KVM.
[2011-08-18 22:36]
[2011-08-18 22:36] upgraded qemu-kvm (0.15.0-1 -> 0.15.0-2)
[2011-08-18 22:36] upgraded wireshark-cli (1.6.1-1 -> 1.6.1-2)
[2011-08-18 22:36] upgraded wireshark-gtk (1.6.1-1 -> 1.6.1-2)
[2011-08-18 22:37] Running '/usr/bin/pacman -Scc'
[2011-08-18 22:37] Running '/usr/bin/pacman -Syu'
[2011-08-18 22:37] synchronizing package lists
[2011-08-18 22:37] starting full system upgrade
[2011-08-19 23:24] Running '/usr/bin/pacman -Syu'
[2011-08-19 23:24] synchronizing package lists
[2011-08-19 23:24] starting full system upgrade
[2011-08-19 23:24] upgraded thunar (1.2.2-1 -> 1.2.2-2)
[2011-08-19 23:40] Running '/usr/bin/pacman -Scc'
[2011-08-20 23:41] Running '/usr/bin/pacman -Syu'
[2011-08-20 23:41] synchronizing package lists
[2011-08-20 23:41] upgraded pacman (3.5.4-3 -> 3.5.4-4)
[2011-08-20 23:41] Running '/usr/bin/pacman -Syu'
[2011-08-20 23:41] synchronizing package lists
[2011-08-20 23:41] starting full system upgrade
[2011-08-20 23:44] upgraded linux-api-headers (2.6.39.1-1 -> 3.0.1-1)
[2011-08-20 23:44] Generating locales...
[2011-08-20 23:44] fr_FR.UTF-8... done
[2011-08-20 23:44] fr_FR.ISO-8859-15@euro... done
[2011-08-20 23:44] fr_FR.ISO-8859-1... done
[2011-08-20 23:44] Generation complete.
[2011-08-20 23:44] upgraded glibc (2.14-4 -> 2.14-5)
[2011-08-20 23:44] upgraded zlib (1.2.5-3 -> 1.2.5-4)
[2011-08-20 23:44] upgraded binutils (2.21.1-1 -> 2.21.1-2)
[2011-08-20 23:44] upgraded isl (0.06-1 -> 0.06-2)
[2011-08-20 23:44] upgraded gcc-libs (4.6.1-2 -> 4.6.1-3)
[2011-08-20 23:44] upgraded gmp (5.0.2-2 -> 5.0.2-3)
[2011-08-20 23:44] upgraded cloog (0.16.2-1 -> 0.16.2-2)
[2011-08-20 23:44] upgraded eject (2.1.5-5 -> 2.1.5-7)
[2011-08-20 23:44] upgraded mpfr (3.0.1.p4-1 -> 3.0.1.p4-2)
[2011-08-20 23:44] upgraded libmpc (0.9-1 -> 0.9-2)
[2011-08-20 23:44] upgraded ppl (0.11.2-1 -> 0.11.2-2)
[2011-08-20 23:44] upgraded gcc (4.6.1-2 -> 4.6.1-3)
[2011-08-20 23:44] upgraded sudo (1.8.1.p2-1 -> 1.8.2-1)
[2011-08-21 20:20] Running '/usr/bin/pacman -Syu'
[2011-08-21 20:20] synchronizing package lists
[2011-08-21 20:21] starting full system upgrade
[2011-08-21 20:21] upgraded gnutls (3.0.0-2 -> 3.0.1-1)
[2011-08-21 20:21] Running '/usr/bin/pacman -Scc'
[2011-08-21 23:32] Running '/usr/bin/pacman -U wit-svn-2941-1-i686.pkg.tar.xz'
[2011-08-21 23:32] installed wit-svn (2941-1)
[2011-08-21 23:35] Running '/usr/bin/pacman -Rsn wit-svn-2941-1'
[2011-08-21 23:35] Running '/usr/bin/pacman -Rsn wit-svn-2941'
[2011-08-21 23:35] Running '/usr/bin/pacman -Rsn wit-svn'
[2011-08-21 23:35] removed wit-svn (2941-1)
[2011-08-22 01:05] Running '/usr/bin/pacman -Rsn john'
[2011-08-22 01:05] removed john (1.7.8-3)
[2011-08-22 22:39] Running '/usr/bin/pacman -Syu'
[2011-08-22 22:39] synchronizing package lists
[2011-08-22 22:40] starting full system upgrade
[2011-08-22 22:41] upgraded ghostscript (9.04-3 -> 9.04-4)
[2011-08-22 22:41] upgraded mplayer (33805-2 -> 34007-1)
[2011-08-22 22:41] upgraded soundtouch (1.5.0-1 -> 1.6.0-1)
[2011-08-22 22:41] upgraded usbutils (003-1 -> 004-1)
[2011-08-25 00:57] Running '/usr/bin/pacman -Syu'
[2011-08-25 00:57] synchronizing package lists
[2011-08-25 00:57] starting full system upgrade
[2011-08-25 01:02] upgraded nspr (4.8.8-1 -> 4.8.9-1)
[2011-08-25 01:02] upgraded nss (3.12.10-1 -> 3.12.11-1)
[2011-08-25 01:02] upgraded chromium (13.0.782.112-2 -> 13.0.782.215-1)
[2011-08-25 01:02] upgraded device-mapper (2.02.87-1 -> 2.02.88-1)
[2011-08-25 01:02] upgraded fakeroot (1.16-1 -> 1.17-1)
[2011-08-25 01:02] upgraded gamin (0.1.10-4 -> 0.1.10-5)
[2011-08-25 01:02] upgraded ghostscript (9.04-4 -> 9.04-5)
[2011-08-25 01:02] upgraded libsamplerate (0.1.7-2 -> 0.1.8-1)
[2011-08-25 01:02] upgraded libssh2 (1.2.7-2 -> 1.2.9-1)
[2011-08-25 01:02] upgraded lvm2 (2.02.87-1 -> 2.02.88-1)
[2011-08-25 01:02] upgraded pcre (8.13-1 -> 8.13-2)
[2011-08-25 01:02] upgraded xulrunner (6.0-1 -> 6.0-2)
[2011-08-25 01:03] Running '/usr/bin/pacman -Scc'
[2011-08-25 01:03] Running '/usr/bin/pacman -Syu'
[2011-08-25 01:03] synchronizing package lists
[2011-08-25 01:03] starting full system upgrade
[2011-08-26 22:59] Running '/usr/bin/pacman -Syu'
[2011-08-26 22:59] synchronizing package lists
[2011-08-26 22:59] starting full system upgrade
[2011-08-26 23:01] upgraded devtools (0.9.23-1 -> 0.9.27-1)
[2011-08-26 23:01] upgraded flashplugin (10.3.183.5-1 -> 10.3.183.7-1)
[2011-08-26 23:01] upgraded git (1.7.6-1 -> 1.7.6.1-1)
[2011-08-26 23:01] upgraded libffi (3.0.9-1 -> 3.0.10-1)
[2011-08-26 23:01] upgraded obconf (2.0.3.git20100309-1 -> 2.0.3.git20100309-2)
[2011-08-26 23:01] upgraded rasqal (1:0.9.26-1 -> 1:0.9.27-1)
[2011-08-26 23:01] upgraded smbclient (3.6.0-1 -> 3.6.0-4)
[2011-08-26 23:01] upgraded thunar (1.2.2-2 -> 1.2.2-3)
[2011-08-26 23:01] upgraded udisks (1.0.3-6 -> 1.0.4-1)
[2011-08-26 23:01] upgraded xarchiver (0.5.2-2 -> 0.5.2-4)
[2011-08-26 23:03] Running '/usr/bin/pacman -Scc'
[2011-08-26 23:03] Running '/usr/bin/pacman -Syu'
[2011-08-26 23:03] synchronizing package lists
[2011-08-26 23:03] starting full system upgrade
[2011-08-27 14:38] Running '/usr/bin/pacman -Syu'
[2011-08-27 14:38] synchronizing package lists
[2011-08-27 14:40] Running '/usr/bin/pacman -Syu'
[2011-08-27 14:40] synchronizing package lists
[2011-08-27 14:40] starting full system upgrade
[2011-08-27 14:44] upgraded avahi (0.6.30-4 -> 0.6.30-5)
[2011-08-27 14:44] upgraded isl (0.06-2 -> 0.07-1)
[2011-08-27 14:44] upgraded cloog (0.16.2-2 -> 0.16.3-1)
[2011-08-27 14:44] upgraded gcc-libs (4.6.1-3 -> 4.6.1-4)
[2011-08-27 14:44] upgraded gcc (4.6.1-3 -> 4.6.1-4)
[2011-08-27 14:44] upgraded gdk-pixbuf2 (2.23.5-1 -> 2.24.0-1)
[2011-08-27 14:44] upgraded logrotate (3.8.0-1 -> 3.8.0-2)
[2011-08-27 14:44] upgraded wine (1.3.26-1 -> 1.3.27-1)
[2011-08-27 14:44] upgraded wireshark-cli (1.6.1-2 -> 1.6.1-3)
[2011-08-27 14:44] upgraded wireshark-gtk (1.6.1-2 -> 1.6.1-3)
[2011-08-28 11:55] Running '/usr/bin/pacman -Syu'
[2011-08-28 11:55] synchronizing package lists
[2011-08-28 11:55] starting full system upgrade
[2011-08-28 11:55] upgraded mercurial (1.9.1-1 -> 1.9.2-1)
[2011-08-28 11:55] upgraded smbclient (3.6.0-4 -> 3.6.0-6)
[2011-08-28 11:55] Running '/usr/bin/pacman -Scc'
[2011-08-29 01:49] Running '/usr/bin/pacman -Syu'
[2011-08-29 01:49] synchronizing package lists
[2011-08-29 01:49] starting full system upgrade
[2011-08-29 01:50] upgraded libnotify (0.7.3-1 -> 0.7.4-1)
[2011-08-29 01:50] upgraded smbclient (3.6.0-6 -> 3.6.0-7)
[2011-08-29 23:59] Running '/usr/bin/pacman -Syu'
[2011-08-29 23:59] synchronizing package lists
[2011-08-29 23:59] starting full system upgrade
[2011-08-30 00:00] upgraded run-parts (3.4.4-1 -> 4.0.2-1)
[2011-08-30 00:00] upgraded ca-certificates (20110421-3 -> 20110502-1)
[2011-08-30 00:00] upgraded openbox (3.5.0-3 -> 3.5.0-4)
[2011-08-30 00:00] upgraded smbclient (3.6.0-7 -> 3.6.0-8)
[2011-08-30 00:00] upgraded vte-common (0.28.1-1 -> 0.28.2-1)
[2011-08-30 00:00] upgraded vte (0.28.1-1 -> 0.28.2-1)
[2011-08-30 00:16] Running '/usr/bin/pacman -Scc'
[2011-08-30 23:43] Running '/usr/bin/pacman -Syu'
[2011-08-30 23:43] synchronizing package lists
[2011-08-30 23:44] starting full system upgrade
[2011-08-30 23:44] upgraded imagemagick (6.7.1.6-1 -> 6.7.2.1-1)
[2011-08-30 23:44] upgraded lzo2 (2.05-1 -> 2.06-1)
[2011-08-30 23:44] Running '/usr/bin/pacman -Scc'
[2011-10-05 12:20] Running '/usr/bin/pacman -Syu'
[2011-10-05 12:20] synchronizing package lists
[2011-10-05 12:20] starting full system upgrade
Last edited by Lacsap (2011-10-05 21:40:13)Ok, I used https://www.archlinux.org/mirrorlist/ to generate a mirror list and retained the best score:
## Arch Linux repository mirrorlist
## Sorted by mirror score from mirror status page
## Generated on 2011-10-05
## Score: 1.8, France
#Server = http://distrib-coffee.ipsl.jussieu.fr/pub/linux/archlinux/$repo/os/$arch
## Score: 1.8, France
#Server = http://miroir.ezvan.fr/archlinux/$repo/os/$arch
## Score: 1.9, France
#Server = http://mir1.archlinux.fr/archlinux/$repo/os/$arch
## Score: 1.9, France
#Server = http://mir.archlinux.fr/$repo/os/$arch
## Score: 1.9, France
#Server = http://archlinux.polymorf.fr/$repo/os/$arch
## Score: 2.0, Switzerland
#Server = http://archlinux.puzzle.ch/$repo/os/$arch
## Score: 5.6, France
Server = http://archlinux.mirrors.ovh.net/archlinux/$repo/os/$arch
I ran the command:
# pacman -Syyu
:: Synchronisation des bases de données de paquets...
core 59,5K 158,3K/s 00:00:00 [######################] 100%
extra 886,5K 28,4K/s 00:00:31 [######################] 100%
community 454,4K 24,0K/s 00:00:19 [######################] 100%
:: Début de la mise à jour complète du système...
:: Remplacer pygobject par extra/python2-gobject2 ? [O/n] O
résolution des dépendances...
recherche des conflits entre paquets...
Suppression (1): pygobject-2.28.6-1
Taille totale des paquets (suppression): 1,83 Mo
Cibles (167): glib2-2.30.0-1 atk-2.2.0-1 glibmm-2.30.0-1 atkmm-2.22.5-1
xorg-server-common-1.10.4-1 xorg-server-1.10.4-1 zenity-3.2.0-1
Taille totale des paquets (téléchargement): 321,72 Mo
Taille totale des paquets (installation): 1371,45 Mo
Procéder à l'installation ? [O/n]
I will update tonight but my problem seems to be set ...
See you tonight. -
[SOLVED] Pacman 3.5.1 and install script problem.
Hi, i'm currently maintaining dkms-nvidia package in AUR. After upgrading to pacman 3.5.1 install script doesn't work anymore. I have searched forum and some googled but i haven't got a clue. It was working with pacman 3.4.3 (i have skipped 3.5.0 release). Does something changed with 3.5.x release about install script handling? Here is the install script:
http://pastebin.com/Lpehuabk
Last edited by tarakbumba (2011-04-06 07:18:16)I have found the problem, i think. When i extracted my compiled dkms-nvidia package i get :
02:35 atilla@tarakbumba:~/DEPOM/Archlinux/Paketler/dkms-nvidia-270.30-3-x86_64.pkg$ ls -lah
toplam 24K
drwxr-xr-x 4 atilla users 4,0K Mar 30 02:35 .
drwxr-xr-x 3 atilla users 4,0K Mar 30 02:35 ..
drwxr-xr-x 3 atilla users 4,0K Mar 30 02:34 etc
-rw-r--r-- 1 atilla users 1,2K Mar 30 02:34 .iNSTALL
-rw-r--r-- 1 atilla users 1,7K Mar 30 02:34 .PKGINFO
drwxr-xr-x 3 atilla users 4,0K Mar 30 02:34 usr
See the ".iNSTALL"? But when it comes to pacman package file is ".INSTALL". Also namcap throws a warning:
02:41 atilla@tarakbumba:~/DEPOM/Archlinux/Paketler$ namcap dkms-nvidia-270.30-3-x86_64.pkg.tar.xz
dkms-nvidia W: Dependency included and not needed ('dkms')
dkms-nvidia E: Missing custom license directory (usr/share/licenses/dkms-nvidia)
dkms-nvidia W: File (.iNSTALL) exists in a non-standard directory.
dkms-nvidia W: File (usr/src) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/xapi-sdk.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nv.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/cpuopsys.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nvtypes.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nv-i2c.c) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/README.template) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/os-registry.c) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nv-memdbg.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nv_gvi.c) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/os-agp.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/os-agp.c) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nvacpi.c) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/rmretval.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/conftest.sh) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nv-cray.c) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/gcc-version-check.c) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nv-reg.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/os-interface.c) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/dkms.conf) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nv.c) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/g_nvreadme.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nv-linux.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nv-vm.c) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/rmil.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nv-misc.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/makefile) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/Makefile.kbuild) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/os-interface.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nv-vm.h) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/Makefile.nvidia) exists in a non-standard directory.
dkms-nvidia W: File (usr/src/nvidia-270.30/nv-kernel.o) exists in a non-standard directory.
dkms-nvidia E: ELF file ('usr/src/nvidia-270.30/nv-kernel.o') outside of a valid path.
See "dkms-nvidia W: File (.iNSTALL) exists in a non-standard directory." ?
My older packges also have ".iNSTALL" but pacman-3.4.3 was taking care of it. Now it ignores install scriplets like these. It is either a makepkg bug or pacman bug. Any help or should i open a bug report?
Last edited by tarakbumba (2011-03-29 23:45:26) -
(SOLVED)pacman loses liblzma.so.0 after conflict-fix using pacman
The latest version of pacman -S package needed to fix a conflict and I replied 'Y' or it wouldn't have installed what I wanted.
Once the install had finished, pacman complained about a missing 'liblzma.so.0'.
No big deal, I set a symbolic link yourself and it worked as before. I've linked
it to the target, not another link that in turn pointed at the target (thus avoiding the 'link that points to
a link that points to a target' situation).
Just thought that you wanted to know.
Tom.
Last edited by archthomas.butz (2011-03-30 04:44:19)For when you run into the "every package is corrupt" issue you just caused yourself:
pacman -S libarchive xz
then remove that link... -
[SOLVED] Pacman leaving system in inconsistent state
Today I made an update to my system and wanted to reboot. Since then I am having issues to no end.
To begin with, I had a custom kernel but it became hard to maintain it so I wanted to drop it in favor of a much newer default kernel. So I removed my kernel with pacman and updated the default one. Then I made sure that all traces of the custom kernel were removed and re-ran mkinitcpio and grub-mkconfig.
Afterwards, I rebooted but gut stuck entering by LUKS passphrase, because it would not accept any input. Here you have to know I was using Plymouth which already fell back to its text-mode (so I assume, the nice lock and GUI were gone). I booted from a CD, chrooted and removed plymouth and its hooks and re-installed the encrypt hook. Upon regenerating the image, it complained libgcrypt.20.so or something was missing. I checked and while pacman -Ql libgcrypt said there should be such a file, there actually wasn't (only in lib32 there was this file, and in lib there was an older version).
So I reinstalled the package and the file was there. Then I wanted to start vim and it complained some libraries were missing. I checked and again same behavior. So reinstalled all packages. This did not help. Again, manual install of those packages. Now I rebooted.
The system started, I could enter my passphrase and was automatically logged in. However, my window manager displayed several errors (among others, ACPI problems) and the screen froze. Reboot, start X as root, screen freezes as well (no WM set up here). I checked /var/log/Xorg.0.log and it is empty as is my .xlog which logs the stdout in case of my user.
I then reinstalled my graphics- and input-drivers. I also removed some packages where pacman claimed they were no longer needed (I know, risky). Now I couldn't even log in to a shell, even as root, login just said something about an Incorrect Login oder something?
So I booted from CD again, chrooted and reinstalled those packages I removed. And here comes the major suprise: My stdout gets overwhelmed with "exists in filesystem". It literally took several seconds to run through. So it seems pacman never removed those files properly.
I checked pacman.log, dmesg, journalctl and anything else I could think of but I only found possible symptoms (like VBox not finding modules), no cause.
Some additional info:
The system is a laptop with an SSD that is encrypted and uses LVM with an ext4 filesystem on all partitions (root, home, usr, var). I know usr is not such a good idea, but I learned that too late...
The installed graphics card is a generic intel card with an additional nVidia card accessible via Optimus (if that's relevant).
I have no idea what could possibly have gone wrong and would love if anyone could provide any suggestion on how to fix it or find the cause of it.
Last note: The initial problem was that it always took multiple seconds to connect to something via network. However I assumed that is because of my outdated kernel but updated libraries that require a newer kernel. Seems I was wrong...
Regards,
javex
Last edited by javex (2014-03-17 16:52:54)Sorry for my late reply. Since the problem had to be fixed fast, I just reinstalled arch. I created a backup and so it was much quicker to reinstall than to unwrap this issue.
Still, concerning the kernel version: It was just some patches to add real multi-threading to luks/dm-crypt.
And during installation, I found that my usr directory had a lot of packages directories (possibly w/ content) even when the actual usr partition was not mounted. I found that I did not have the usr hook in mkinitcpio and must say, I possibly broke it myself by mounting it for my chroot environ. So this may be the cause of the extended issues.
So what likely happened here was that I broke my system by sometimes exeuting pacman with separately mounted /usr and sometimes without. This still doesn't explain the original issue but maybe a simple live CD boot & update/upgrade would have solved that. Thank you all for your responses and your effort and sorry this thread wasn't of much use to anyone. -
Pacman complains with `"gcc-libs" is not in the package set` message
Hi,
today I wanted to do full system upgrade, but this happened:
# pacman -Syu
:: Synchronizing package databases...
current 69,7K 84,9K/s 00:00:01 [#################################################] 100%
extra 323,1K 17,5K/s 00:00:18 [#################################################] 100%
community 312,4K 219,0K/s 00:00:01 [#################################################] 100%
:: Starting full system upgrade...
:: Replace scrollkeeper with extra/rarian? [Y/n]
warning: apr: forcing upgrade to version 1.2.9-1
warning: dnsutils: forcing upgrade to version 9.4.1_P1-2
warning: ruby: forcing upgrade to version 1.8.6_p36-3
warning: sudo: forcing upgrade to version 1.6.9p4-1
warning: xpdf: forcing upgrade to version 3.02_pl1-1
resolving dependencies...
error: cannot resolve dependencies for "rarian" ("gcc-libs" is not in the package set)
error: failed to prepare transaction (could not satisfy dependencies)
:: rarian requires gcc-libs
It's obvious that gcc-libs package is missing in current package. I've found one similar problem here http://bbs.archlinux.org/viewtopic.php?pid=283439. But I cannot solve it like that. I have current file included in /etc/pacman.conf already. I've also tried to change current to core and make the /etc/pacman.d/core file and it complained too:
# pacman -Su
:: Starting full system upgrade...
:: Replace util-linux with current/util-linux-ng? [Y/n]
:: Replace scrollkeeper with extra/rarian? [Y/n]
warning: apr: forcing upgrade to version 1.2.11-1
warning: apr-util: forcing upgrade to version 1.2.10-1
warning: dnsutils: forcing upgrade to version 9.4.1_P1-2
warning: ntp: forcing upgrade to version 4.2.4p4-2
warning: ruby: forcing upgrade to version 1.8.6_p111-2
warning: sudo: forcing upgrade to version 1.6.9p5-1
warning: xpdf: forcing upgrade to version 3.02_pl1-1
:: pacman has detected a newer version of the "pacman" package.
:: It is recommended that you allow pacman to upgrade itself
:: first, then you can re-run the operation with the newer version.
:: Upgrade pacman first? [Y/n]
resolving dependencies... done.
looking for inter-conflicts... done.
Targets: pacman-3.0.6-1
Total Package Size: 0,80 MB
Proceed with installation? [Y/n]
checking package integrity... done.
cleaning up... done.
(1/1) checking for file conflicts [#################################################] 100%
error: could not prepare transaction
error: failed to commit transaction (conflicting files)
pacman: /etc/pacman.d/core exists in filesystem
errors occurred, no packages were upgraded.
The last upgrade was almost perfect but now strange things happens. :^(
Can anyone help me to solve this, please??kishd wrote:Did you replace current with core in your pacman.conf file?
yes, the second output is related to pacman.conf with `current` replaced with `core` .... and good to say, that I did NOT forgot to update repositories with `pacman -Sy` before upgrade ;-) -
[SOLVED] Pacman "config file could not be read" error during Arch ins
I've been attempting to get Arch setup for a while now, and after having some trouble with partitions, my wireless connecting, and setting up repos and mirrors, which the Wiki helped me solve, I've hit a bigger bump. While updating the system using pacman as the Beginners Guide says to do, I get errors when I try to continue the update process as follows :
btw: I'm typing this on a laptop next to my computer
[root@McArch~]# pacman -Syu
error: config file /etc/pacman.d/core could not be read
error: config file /etc/pacman.d/extra could not be read
error: config file /etc/pacman.d/community could not be read
:: Synchronizing package databases . . .
error: failed to updated core (unexpected error)
error: failed to updated extra (unexpected error)
error: failed to updated community (unexpected error)
error: failed to synchronize any databases
Any tips as to whats going on? I've tried to created said files, and even insert mirrors into the file, like in the /etc/pacman.d/mirrorlist file but this doesn't seem to help
Last edited by Windfinder (2008-09-29 20:43:29)Glad you got it working.
I'm not sure what happened in your install but I just finished using an old 2007.08 iso and pacman first starts out with /etc/pacman.d/core, etc/pacman.d/extra, /etc/pacman.d/community ... etc., but I never had your problem when I did the #pacman -Syu after initial install reboot. The pacman update removes the above mentioned repos and replaces them with a single /etc/pacman.d/mirrorlist. You must have messed up an initial config file somehow as I couldn't get the same errors you got. It looks like you had your /etc/pacman.conf file messed up somehow and when you pointed it to the mirrorlist it could finally work properly. I'll just include my /etc/pacman.conf file and /etc/pacman.d/mirrorlist so you can compare. NB* these are from my x86_64 so for 32 bit machines i686 would replace x86_64 in the files.
# /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
/etc/pacman.d/mirrorlist
# Arch Linux repository mirrorlist
# North America
# - United States
Server = http://mirror.neotuli.net/arch/$repo/os/x86_64
Server = http://holmes.umflint.edu/archlinux/$repo/os/x86_64
Server = http://archlinux.unixheads.org/$repo/os/x86_64
Server = ftp://ftp.archlinux.org/$repo/os/x86_64
Server = ftp://locke.suu.edu/linux/dist/archlinux/$repo/os/x86_64
Server = ftp://ftp.gtlib.gatech.edu/pub/linux/distributions/archlinux/$repo/os/x86_64
Server = ftp://mirror.cs.vt.edu/pub/ArchLinux/$repo/os/x86_64
Server = http://mirrors.easynews.com/linux/archlinux/$repo/os/x86_64
Server = ftp://ftp.ibiblio.org/pub/linux/distributions/archlinux/$repo/os/x86_64
Server = http://mirror.rit.edu/archlinux/$repo/os/x86_64
Server = http://mirror.umoss.org/archlinux/$repo/os/x86_64
# - Canada
Server = ftp://mirror.csclub.uwaterloo.ca/archlinux/$repo/os/@carch
Well it was an interesting way to kill 30+ minutes. -
[solved] pacman broken after "pacman -Syyu" excluding pacman
Hi forums,
I use arch x86_64, yaourt and the testing and multilib repositories.
A full system upgrade doing "yaourt -Syyu" didn't work, because pacman had an unfulfilled dependancy which I don't recall, but it was about a normal and a multilib version: I probably have the multilib version of a library installed, which has not been updated to the version required by pacman yet.
So I thought it would be perfectly fine to exclude pacman from this system upgrade by choosing "manually" from the options given by "yaourt -Syyu" and commented pacman.
The upgrade then went fine except for the two final lines:
package-query: error while loading shared libraries: libarchive.so.2: cannot open shared object file: No such file or directory
testdb: error while loading shared libraries: libarchive.so.2: cannot open shared object file: No such file or directory
Now everytime I try to use pacman, I get this error:
pacman: error while loading shared libraries: libarchive.so.2: cannot open shared object file: No such file or directory
Do you know how to solve this?
Thanks in advance
xiliyi
Last edited by xiliyi (2012-01-05 09:49:23)ngoonee wrote:Actually (even without cower), makepkg will tell you what dependencies are missing when you try and compile an AUR package. In fact, -s will install them for you (unless they're from the AUR, in which case you have to download/makepkg that package first).
Actually, I was more concerned about updates for packages from AUR. yaourt would handle AUR packages as if they were in a repository, and update them, solving dependency problems.
Now what I fear is, that if some regular library gets an update, it may not updated on my system in the first place, because pacman only sees that the older version is needed for the AUR software, but is not capable of updating the AUR package (which works with the new library version) automatically. So updates will break some software unless I remove it first and install the latest version manually. -
[Solved] Pacman message after interrupted installation... persists
As you can see I'm still a bit of a newbie. Yesterday I was installing TeX live, but while installing someone unplugged a USB stick and all went stuck... it all just freeze the system, I guess it was a hardware problem. Anyway, I restarted and when I came back to resume the installation (downloading of packages was already finished), pacman sent me a lot of error messages, but apparently TeX live installed fine. Well, I checked my TeX system and works fine. The problem is every time I try to install something, I always get this error message:
error: could not open file /var/lib/pacman/local/texlive-bin-2010.1-4/depends: No such file or directory
error: could not open file /var/lib/pacman/local/texlive-bin-2010.1-4/depends: No such file or directory
How do I repair this? I didn't want to clean the cache, but... would this do fine? what else do I have to do?
Thanx in advance.
Last edited by joe74 (2010-10-23 22:33:20)Well, solved by myself.
What I had to do after a lot of mess was
1. uninstall everything that was causing errors
sudo pacman -Rs texmaker texlive-most texlive-core texlive-bin
2. and clear the cache of files not installed
sudo pacman -Sc texmaker texlive-most texlive-core texlive-bin
This solved the entire problem. Dialectical theory still functioning in my brains -
Hello,
I've been trying to install fluxbox on my freshly installed arch linux (with updates) and I've been following a guide on how to do so. The problem is that I can't really install anything but 'pacman -S xorg', like for example if I try 'pacman -S hwd' I get this error:
http://rs51gc.rapidshare.com/files/1985 … G_1785.JPG
and this happens to pretty much every package that I've tried.
I've googled a lot and I've found some suggestions but none have worked =/
Please help.
Thanks.
Last edited by loxaXcracker (2009-02-16 11:44:20)loxaXcracker wrote:
Nvm guys, I've figured out what the problem was.
(edit in rc.conf (change to eth0="dhcp") and then simply restart the network.)
Thanks for the help anyway guys!
Glad to hear that Add [SOLVED] in the topic. -
[Solved] Pacman errors: "call to execv failed", system not booting
Recent upgrade (yesterday) - problems went like this:
1) pacman -Syu attempted "filesystem" upgrade and threw errors about some directories in /usr/local being 775 not 755.
2) that was because I had a non-standard package in there. I changed just those relevant directories to 755.
3) reattempted pacman -Syu but got a bunch of errors: "call to execv failed"
4) system was immediately borked. Reboot now throws me into a shell.
This is a 32 bit system.
Any ideas and help would be greatly appreciated.
Last edited by lagagnon (2013-01-30 19:10:24)Solved my problem with the following method:
1) used Arch LiveCD. Mounted boot and / partitions
2) pacman -r /path/to/root -Syyu glibc filesystem
3) reboot gave "Unable to find root device error"
4) ran LiveCD again following these instructions: https://wiki.archlinux.org/index.php/Pa … onger_boot
Maybe you are looking for
-
Hi, I want to create a delivery from sales order using 'Submit'. Is this a correct program? What needs to be populated in the table rspar_tab? Please provide your input. data: rspar_tab TYPE TABLE OF rsparams. SUBMIT SAPMV50A USING SELECTION-SCREEN
-
Will Bootcamp run on a Macbook Air?
I'm planning to buy a Mac laptop for my wife. She needs to use Windows (yuk). I'm considering a Macbook Air. Will I be able to run Bootcamp?
-
I have the main movie with a button on it with the following command: on (release) { loadMovie("loadCentralCommandSGUnload.swf", "_root.loadCentralCommand"); That works great - it loads the movie into the loadCentralCommand clip The problem if I load
-
Am I entitled to download CS2 products when I own an older Photoshop version?
I just installed my owned Photoshop CS (1), and can no longer activate it on my machine, meaning I can't use it after a 30-day trial period. According to this page (http://helpx.adobe.com/x-productkb/policy-pricing/creative-suite-2-activation-end-lif
-
Annoying progress bar doesn't let me do anything!! Help I'm stuck!!
I turned off my mac with Pages and other documents open but now when I click on Pages the blue and gray progress bar appears and doesn't let me do anything: copy, paste, change colors or font, save or open other documents...Does anyone know what I ha