You are not logged in.
Hi,
Yesterday everything was working great but today it isn't anymore.
The problem
-----------------
I did
pacman -Syu
Output:
sudo pacman -Syu
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
archlinuxfr is up to date
:: The following packages should be upgraded first :
pacman
:: Do you want to cancel the current operation
:: and upgrade these packages now? [Y/n]
So i choose Y and i get this:
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: package-query: requires pacman<3.5
:: pacman-color: requires pacman=3.4.3
What does this mean and how can I solve this?
As described here: https://bbs.archlinux.org/viewtopic.php?pid=907659
I removed yaourt but this didn't solve the problem
Thanks in advance!
Last edited by tgoossens (2011-03-24 12:11:46)
Share and enjoy!
Offline
pacman -Rsn package-query pacman-color
pacman -Syyu
pacman-db-upgrade
install yaourt and pacman-color-testing (until pacman-color 3.5.1 is out).
Arch64/DWM || My Dropbox referral link
Offline
Thanks that worked.
Share and enjoy!
Offline
I had this same problem, and I went through the instructions as posted, but it must have removed pacman in the process. Now, I cannot update anything. I went through the stickied topic on pacman but it didn't work. I found some instructions on downloading pacman and installing it manually, but now every time I run the pacman command I get:
pacman: error while loading shared libraries: libalpm.so.6: cannot open shared object file: No such file or directory
I googled that and none of those instructions work for me. Is there a way I can save my system?
Edit: And now my laptop has the same error preventing me from updating Pacman, what should I do to resolve that one? I would think that something in the repositories needs to be fixed and this is probably a bug, considering the home page doesn't say anything about it.
Edit 2: I did the following
sudo mv /usr/lib/liblzma.so /usr/lib/liblzma.so.0
And now pacman works, but it cannot find a single mirror that I have set up, it says "error retrieving file" on everything.
Edit 3: Nevermind, I give up. I'm going to wipe and reformat my computer. This is RIDICULOUS. I hope the same problem doesn't happen to my laptop, what is the *official* way to fix the "package-query: requires pacman<3.5" problem?
Last edited by jlacroix (2011-03-24 14:23:20)
Offline
sudo mv /usr/lib/liblzma.so /usr/lib/liblzma.so.0
dont ever do something like this.
did you tried installing pacman using the arch livecd?
pacman -r /mnt -U /path/to/pacman.pkg.tar.xz ?
what is the *official* way to fix the "package-query: requires pacman<3.5" problem?
remove it, update all packages including pacman, install it again.
Last edited by JokerBoy (2011-03-24 14:49:42)
Arch64/DWM || My Dropbox referral link
Offline
jlacroix wrote:sudo mv /usr/lib/liblzma.so /usr/lib/liblzma.so.0
dont ever do something like this.
did you tried installing pacman using the arch livecd?
pacman -r /mnt -U /path/to/pacman.pkg.tar.xz ?
jlacroix wrote:what is the *official* way to fix the "package-query: requires pacman<3.5" problem?
remove it, update all packages including pacman, install it again.
Will the livecd method still work? The current status is that when I run pacman, I get:
pacman: error while loading shared libraries: libalpm.so.6: cannot open shared object file: No such file or directory
In regards to removing and then updating packages, that smells like a packaging bug to me. Does this mean that everyone running Arch is going to have to do this? On a stable branch of a distribution, that doesn't seem right. Is there going to be an updated package that will make it so I don't have to do that? If so, I'll just wait a bit before I mess with my laptop.
Thanks!
Offline
No it doesn't. I upgraded pacman yesterday without any glitches.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
No it doesn't. I upgraded pacman yesterday without any glitches.
That's good to know. I wonder what made the difference in both of my machines is that makes me have to do it this way?
Offline
probably because you have other pacman like apps eg. pacman-color or aur wrappers that depend on a particular pacman version.
I have nothing of the sort. I only have pacman and aurget
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
probably because you have other pacman like apps eg. pacman-color or aur wrappers that depend on a particular pacman version.
I have nothing of the sort. I only have pacman and aurget
I don't have pacman-color or aur wrappers, other than Yoaurt if that's what you mean.
Edit: You're right, I removed yaourt and its dependency and had no problem updating. So now I just have to figure out how to get my desktop working again.
Last edited by jlacroix (2011-03-24 15:26:45)
Offline
Will the livecd method still work?
why not? you'll run pacman exec from livecd, not the one installed on your HDD. chroot not needed also. i use this "pacman -r /mnt -Syy syslinux" to install syslinux every time i make an installation.
Last edited by JokerBoy (2011-03-24 15:29:30)
Arch64/DWM || My Dropbox referral link
Offline
jlacroix wrote:Will the livecd method still work?
why not? you'll run pacman exec from livecd, not the one installed on your HDD. chroot not needed also. i use this "pacman -r /mnt -Syy syslinux" to install syslinux every time i make an installation.
But Pacman is installed, it's complaining that it can't find libalpm.so.6, will that fix that problem as well?
Offline
im having the same issue as posted above. If i want to keep yaourt should i just wait till the update works?
Offline
all aur helpers need to be updated to use the latest pacman and the new db structure. So yeah you will have to wait until those helpers get updated. But since we are talking about pacman, you will not be able to upgrade any packages if you don't update pacman because everytime you try, it will ask you if you want to upgrade pacman first and if you say no, then pacman 3.4 will not be able to understand the new db structure.
There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !
Offline
probably because you have other pacman like apps eg. pacman-color or aur wrappers that depend on a particular pacman version.
I have two systems and the one without pacman-color upgraded smoothly. The one with it failed like the original poster.
JokerBoy's process basically worked for me but I couldn't do anything after the "pacman-db-upgrade" without getting a bunch of database errors. A "pacman -Syu" fixed it.
pacman -Rsn package-query pacman-color
pacman -Syyu
pacman-db-upgrade
pacman -Syu
install yaourt and pacman-color-testing (until pacman-color 3.5.1 is out).
Thank you for this thread. I was struggling to sort this issue out before arriving here.
Last edited by TomB17 (2011-03-24 19:49:03)
Offline
Future note: This will happen almost every time a pacman upgrade comes through. Just remove your wrappers and reinstall after upgrade; simple as that.
Offline
I'll keep that in mind. I'll be reinstalling my entire system this evening, so lesson learned.
Offline
I finally got Pacman reinstalled, but now it says that _every_ package is corrupted even after cleaning the cache. Pressing on...
Offline
I finally got Pacman reinstalled, but now it says that _every_ package is corrupted even after cleaning the cache. Pressing on...
Did you remember to merge pacman.conf with the pacnew?
Offline
jlacroix wrote:I finally got Pacman reinstalled, but now it says that _every_ package is corrupted even after cleaning the cache. Pressing on...
Did you remember to merge pacman.conf with the pacnew?
My pacman.conf was completely overwritten with the new one during my day of troubleshooting hell. It seems that every time I try something to troubleshoot it, I just make it worse. I forcefully installed the latest pacman and xz by untaring, and now it thinks everything is corrupt.
Edit: I also tried:
sudo ln -s /usr/lib/liblzma.so /usr/lib/liblzma.so.0
per some instructions I found on Google. It still thinks every package is corrupt.
Last edited by jlacroix (2011-03-24 23:55:56)
Offline
Future note: This will happen almost every time a pacman upgrade comes through. Just remove your wrappers and reinstall after upgrade; simple as that.
Do helpers like powerpill, bauerbill, packer fall in the same category? And would it be a viable procedure to then say no to the pacman upgrade, wait for helpers to be updated, upgrade the helpers first, and then upgrade pacman?
Offline
ANOKNUSA wrote:Future note: This will happen almost every time a pacman upgrade comes through. Just remove your wrappers and reinstall after upgrade; simple as that.
Do helpers like powerpill, bauerbill, packer fall in the same category? And would it be a viable procedure to then say no to the pacman upgrade, wait for helpers to be updated, upgrade the helpers first, and then upgrade pacman?
Generally yes, since they're all wrappers--they simply call pacman, makepkg, text editors, etc. in a single command instead of the user doing so separately and manually. They're a decadent bourgeois conveniance and aren't stand-alone tools. Exceptions I can think of might be cower and packer, which are just AUR scripts, and clyde, which (if I remember correctly) is basically a clone of pacman with extended features intended to match the capabilities of yaourt. Also, see this.
Offline
Also, see this.
Dang! Thanks for the clarification and the heads-up re: xyne. Dang! Hopefully the new pacman is worth it... I like bourgeois conveniences.
Last edited by stryder (2011-03-25 03:38:45)
Offline
Before I continue to wipe and restore my desktop, does anyone have any last minute ideas to solve my issue (post #20)?
Offline
Before I continue to wipe and restore my desktop, does anyone have any last minute ideas to solve my issue (post #20)?
Is your pacman database upgraded, i.e. did you run "pacman-db-upgrade" as root?
To know or not to know ...
... the questions remain forever.
Offline