You are not logged in.
Pages: 1
I have a strange problem. I haven't updated Arch since sometimes in January, and today when I tried to it asked me to update pacman first. I said yes, and got this:
sudo pacman -Syu
Password:
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
repo-ck 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] y
resolving dependencies...
looking for inter-conflicts...
error: failed to prepare transaction (could not satisfy dependencies)
:: pyalpm: requires pacman<3.6What do I do now?
EDIT:
pacman -Qi pacman
Name : pacman
Version : 3.5.4-4
URL : http://www.archlinux.org/pacman/
Licenses : GPL
Groups : base
Provides : None
Depends On : bash glibc>=2.14 libarchive>=2.8.4 libfetch>=2.28
pacman-mirrorlist
Optional Deps : fakeroot: for makepkg usage as normal user
curl: for rankmirrors usage
Required By : cower-git pyalpm
Conflicts With : None
Replaces : None
Installed Size : 2956.00 K
Packager : Allan McRae <allan@archlinux.org>
Architecture : x86_64
Build Date : Sun 14 Aug 2011 01:37:32 SAST
Install Date : Mon 05 Sep 2011 23:08:03 SAST
Install Reason : Explicitly installed
Install Script : Yes
Description : A library-based package manager with dependency supportLast edited by biltong (2012-02-09 15:06:03)
Offline
pacman -S pacman pyalpmshould work
Running arch is like raising a puppy - if you spend a bit of time with it each day and do just a bit of training you'll end up with the most loyal partner you could want; if you lock it in a room and don't check on if for several days, it'll tear apart your stuff and poop everywhere.
Offline
pacman -S pacman pyalpmshould work
Shouldn't he remove pyalpm, update pacman, then reinstall pyalpm?
Offline
meph wrote:pacman -S pacman pyalpmshould work
Shouldn't he remove pyalpm, update pacman, then reinstall pyalpm?
It's a known bug, manually and explicitly updating pyalpm solves the problem. Doesn't mean your solution wouldn't work ![]()
Running arch is like raising a puppy - if you spend a bit of time with it each day and do just a bit of training you'll end up with the most loyal partner you could want; if you lock it in a room and don't check on if for several days, it'll tear apart your stuff and poop everywhere.
Offline
Rerun the command, but say no.
It will still update pacman, it just will not do it *first* which is what is causing the problem.
Responding NO will allow the full update to proceed, then make sure to merge your pacnew's and check the wiki to set up package signing.
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
I have encountered this case for several times, I usually remove other packages and update pacman first, then install the packages again.
Hello&Thanks
Offline
Pages: 1