Your message dated Thu, 10 Jun 2010 22:47:38 +0200
with message-id <[email protected]>
and subject line Re: Bug#433624: apt: please allow release pinning for suite
and codename fields
has caused the Debian Bug report #433624,
regarding apt: please allow release pinning for suite and codename fields
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
433624: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=433624
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: apt
Version: 0.7.3
Severity: wishlist
Please allow pinning for suite and codename fields in Release files.
This is the Release file header for etch
(http://debian.debian.zugschlus.de/debian/dists/etch/Release):
Origin: Debian
Label: Debian
Suite: stable
Version: 4.0r0
Codename: etch
When I want to pin etch, I can pin for Version.
But this does not work for lenny and sid, since their release files
do not have a Version: field. To pin lenny and sid, I would need to
pin for Suite and/or Codename, which does not seem to be possible as
documented in apt_preferences(5).
Please add this possibility.
Greetings
Marc
--- End Message ---
--- Begin Message ---
Version: 0.7.21
2010/6/10 Gerfried Fuchs <[email protected]>:
>> It was more or less the first thing i did in APT and should be working
>> since 0.7.21 (released on 29 Jun 2009). The bug looks like an unmerged
>> duplicate of #97564 which was closed with this upload…
>
> Ah, and lenny has 0.7.20.2+lenny1 - I tested there with the above
> statement. Given my different workflows for my QA work and development I
> can't quickly put in different sources.list entry on my laptop currently
> to test wether this is really fixed in the squeeze version, I have to
> take your word for it.
Trusting me is dangerous in general…
(various reasons, including IANADD, IANADM & IANAL …)
>> Pin: release sid will also work - but a=sid not as a= stands for archive,
>> so make sure to use the right release string.
>> Make also sure that the archive you want to pin actually provides
>> these values - you can find that out with "apt-cache policy"
>> (yes, without a parameter).
>
> Right, stable apt doesn't show n= in its "apt-cache policy" output,
> squeeze's apt does, so I guess this bugreport could get closed with the
> squeeze version latest, 0.7.21 probably also does it.
… but in this specific case it should be safe as the feature is now
nearly a year in unstable without complains - so i guess it works
not only for me in sid and squeeze. :)
Bug is therefore closed with version 0.7.21 now, but as always,
feel free to reopen it if you disagree, it reappears or whatever…
Best regards,
David Kalnischkies
--- End Message ---
