FS#7820 - Pacman failed to upgrade pacman package during distribution upgrade

Attached to Project: Pacman
Opened by Petr Slansky (psl) - Tuesday, 14 August 2007, 21:51 GMT
Last edited by Dan McGee (toofishes) - Friday, 09 November 2007, 04:27 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To Aaron Griffin (phrakture)
Dan McGee (toofishes)
Architecture i686
Severity Low
Priority Normal
Reported Version 3.0.5
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:

pacman failed to resolve dependencies during distribution upgrade (Archlinux 0.8 to 2007.08). Maybe that this problem was already fixed in pacman 3.0.5...

Steps to Reproduce:

"pacman -Syu" failed on pacman update as it failed to update libarchive. I updated pacman manualy "pacman -S pacman" and after that "pacman -Syu" worked great.

Details:

# pacman -Syu
:: Synchronizing package databases...
:: current is up to date
:: extra is up to date
:: Replace traceroute with iputils from "current"? [Y/n]
:: Replace gaim with pidgin from "extra"? [Y/n]

:: 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]
error: unresolvable dependencies:
pacman: requires libarchive>=2.2.3 but it is not in the sync db


# pacman -S pacman

Targets: libarchive-2.2.5-1 pacman-3.0.5-2

Total Package Size: 1.1 MB

Proceed with upgrade? [Y/n]

:: Retrieving packages from current...
libarchive-2.2.5-1 [################] 100% 291K 23.6K/s 00:00:12
pacman-3.0.5-2 [################] 100% 821K 38.6K/s 00:00:21

checking package integrity... done.
loading package data... done.
checking for file conflicts... done.
This task depends upon

This task blocks these from closing
 FS#8109 - Pacman 3.1 Release Roadmap 
Closed by  Dan McGee (toofishes)
Friday, 09 November 2007, 04:27 GMT
Reason for closing:  Fixed
Additional comments about closing:  This shouldn't be an issue as long as we set the deps right in the PKGBUILD.
Comment by Xavier (shining) - Tuesday, 14 August 2007, 23:05 GMT
Yep, that problem only happened with pacman 2. It should work fine now with pacman 3.
Comment by Xavier (shining) - Saturday, 18 August 2007, 10:48 GMT
With recent pacman and libdownload upgrade, I noticed something that may be an issue :
since pacman only depends on libdownload (no particular version), that dependency is already satisfied
by the older version of libdownload, and so pacman doesn't upgrade it the first time.

However, for libarchive, pacman depends on libarchive>=2.2.3 , so libarchive got upgraded in the same time than pacman.
Comment by Dan McGee (toofishes) - Thursday, 23 August 2007, 18:02 GMT
We should try to explicitly specify the libarchive and libdownload versions with the pacman PKGBUILD from now on. This will ensure you have the same pacman 'toolchain' that the developer had when compiling.

EDIT: or make dependency resolving for pacman smarter- make it always grab the most recent version of its deps or something.

Loading...