Eugene V. Lyubimkin a écrit : > package cupt apt > reassign 554773 apt > thanks > > Hi Jean, > > Jean-Christophe Dubacq wrote: >> Package: cupt >> Version: 1.2.1 >> Severity: normal >> >> While in the process of comparing apt-get and cupt, I found this >> discrepancy between apt-get and cupt computations of pinnings: >> >> LANG=C apt-cache policy xml-core >> xml-core: >> Installed: 0.12 >> Candidate: 0.13 >> Version table: >> 0.13 0 >> 500 http://ftp.fr.debian.org testing/main Packages >> 100 http://ftp.fr.debian.org unstable/main Packages >> *** 0.12 0 >> 500 http://ftp.fr.debian.org lenny/main Packages >> 100 /var/lib/dpkg/status >> >> LANG=C cupt policy xml-core >> xml-core: >> Installed: 0.12 >> Candidate: 0.12 >> Version table: >> *** 0.12 501 >> /var/lib/dpkg/status installed/ (unsigned) >> http://ftp.fr.debian.org/debian stable/main (signed) >> 0.13 101 >> http://ftp.fr.debian.org/debian testing/main (signed) >> http://ftp.fr.debian.org/debian unstable/main (signed) >> >> >> My pinnings are as follow : >> Package: * >> Pin: release a=unstable >> Pin-Priority: 100 >> > > I believe cupt is doing right here. From 'man apt_preferences': "If any > specific-form records match an available package version then the first such > record determines the priority of the package version. Failing that, if any > general-form records match an available package version then the first such > record determines the priority of the package version." > > So, you have '100' for unstable versions, and then 100 (+1) is strictly > assigned to that version of xml-core, not looking more at any other settings, > including 'apt::default-release'. > > And no, cupt has not 'stable' in its 'apt::default-release' setting by > default, but undefined value like APT does. All option inconsistencies are > listed in 'man cupt_vs_apt', and 'apt::default-release' is not there. > Should I file a bug against apt-get or the manual ? The solution for me is obviously to to pin stable and testing to 500. However, either apt-cache is at fault, or the manual is (I read the excerpts you quoted the same as you). The only ambiguity resides in the definition of a "package version" : possibly apt-get tries for each origin of a package version and gives the higher score possible, whereas cupt matches globally a package version (which seems to be the documented way of proceeding). -- Jean-Christophe Dubacq
Attachment:
signature.asc
Description: OpenPGP digital signature