Bug#554773: cupt: Wrong computation of preferences/pinning

[David Kalnischkies <kalnischkies+debian@gmail.com>]

>>> My pinnings are as follow :
>>> Package: *
>>> Pin: release a=unstable
>>> Pin-Priority: 100
>>>
>> I believe cupt is doing right here. From 'man apt_preferences':
And i believe apt-get is right here. ;) From 'man apt_preferences':
> If there is no preferences file or if there is no entry in the file that
> applies to a particular version then the priority assigned to that
> version is the priority of the distribution to which that version belongs.
( First sentence in "APT´s Default Priority Assignments" )
In "The Effect of APT Preferences" it is said:
> The general form assigns a priority to all of the package versions
> in a given distribution [...]

Or in short: A package version has multiply pin-settings:
- a version specific one (e.g. 5.8*)
- one for each origin/release/distribution (e.g. sid or "")
And this is btw what i expect with the given pin-file,
but your mileage may vary, of course.
(Or to rephrase it: how to get the same behavior in cupt?)

I would therefore reassign the bug (again) to cupt and proceed
with improving the manpage in #557637 instead, but i don't want to
play bug-ping-pong. So what do you think Eugene V. Lyubimkin?


Best regards / Mit freundlichen Grüßen,

David "DonKult" Kalnischkies