FS#56241 - [pyalpm] versioned dependencies are wrong
Attached to Project:
Arch Linux
Opened by Eli Schwartz (eschwartz) - Sunday, 05 November 2017, 03:20 GMT
Last edited by Jelle van der Waa (jelly) - Monday, 06 November 2017, 09:05 GMT
Opened by Eli Schwartz (eschwartz) - Sunday, 05 November 2017, 03:20 GMT
Last edited by Jelle van der Waa (jelly) - Monday, 06 November 2017, 09:05 GMT
|
Details
The latest update of pyalpm has a versioned dependency on
pacman>=5.0.2
The latest documentation for pyalpm states that it requires libalpm 10 which means any version of pacman>=5 should work, and there do not seem to be any changes in the 5.0.2 maintenance release which would break pyalpm. Not that there should be, because it is a maintenance release! Also due to the fact that *not* having libalpm 10 is called "error while loading shared libraries". Versioned dependencies suck on general principle, and it is reasonable to expect that no Arch Linux systems on which pyalpm will be installed, have pacman<5.0 installed. This also means that due to pacman 5.0.2 being a separate-branch maintenance release, using pacman-git tracking the current commits on git master still fails this overly restrictive check with pacman-git 5.0.1.r182.gbcc9c417, causing pacman to forcibly replace pacman-git with pacman. |
This task depends upon
Closed by Jelle van der Waa (jelly)
Monday, 06 November 2017, 09:05 GMT
Reason for closing: Works for me
Additional comments about closing: Versioned dependencies do work, but actually pacman should provide libalpm=10, so pyalpm can depend on it.
Monday, 06 November 2017, 09:05 GMT
Reason for closing: Works for me
Additional comments about closing: Versioned dependencies do work, but actually pacman should provide libalpm=10, so pyalpm can depend on it.