Re: No different package pins for volatile and volatile-sloppy anymore
Hi,
I guess I have found the reason for this old problem:
> for debian sarge the volatile archive used to have different package
> pins for volatile and volatile-sloppy:
> release o=volatile.debian.org,a=sarge,l=debian-volatile
> release o=volatile.debian.org,a=sarge-sloppy,l=debian-volatile
> For etch both archives use the same pin:
> release o=volatile.debian.org,a=stable,l=debian-volatile
The pins are still the same for lenny. You can easily check it
with 'apt-cache policy' (without any further argument) when you
have the volatile archive in your sources list.
> Unfortunately I don't see any possibility to give volatile and
> volatile-sloppy different priorities in apt/preferences now (I know
> the default priorities are set different, but that doesn't help if
> you use your own priority scheme).
> This forces me to assign both volatile and volatile-sloppy a low
> priority (below 100 to avoid the auto update of packages from
> volatile-sloppy) and to update the packages from volatile by
> hand, which is not what I want.
[...]
The reason seems to be an (undocumented?) change in apts
behaviour between version 0.5 and 0.6. The 'a=<name>' attribute
in the apt preferences file seems not to match against the
'Archive:' attribute in the Release files anymore. See debian
bug #308445.
So maybe you could use the 'Suite:' line in the Release files
or maybe even better the 'Label:' line ('Label: debian-volatile'
resp. 'Label: debian-volatile-sloppy') to make it possible to set
different priorities for 'volatile' and 'volatile-sloppy' again.
Please Cc: to my address if you answer this mail, I'm not
subscribed to this mailing list.
Thanks,
Uwe
Reply to: