Bug#312321: marked as done (Both woody and sarge have Archive: stable in Release file)

Your message dated Fri, 31 Jul 2009 21:39:07 +0200
with message-id <c64043e60907311239w4ad7b43ek1686614a5912c67@xxxxxxxxxxxxxx>
and subject line Fixed: Support pinning and targeting by codename
has caused the Debian Bug report #419188,
regarding Both woody and sarge have Archive: stable in Release file
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 owner@xxxxxxxxxxxxxxx
immediately.)


-- 
419188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419188
Debian Bug Tracking System
Contact owner@xxxxxxxxxxxxxxx with problems

--- Begin Message ---

Subject:	Both woody and sarge have Archive: stable in Release file

Package: ftp.debian.org

Both woody and sarge have Archive: stable in the Release file. That
affects package pinning, release a=stable does no longer differentiate
between them.

--
DanB


--- End Message ---

--- Begin Message ---

Subject:	Fixed: Support pinning and targeting by codename

Version: 0.7.22

Thanks for your reports and especially thanks for the patch Ryan Murray!
The patch was a good base but is now a bit more general
to not only support codenames in pin-files.

The issue should be fixed in 0.7.22:
extracted from the changelog:

[ David Kalnischkies ]
* [ABI break] Allow pinning by codename (closes: #97564)

Note: The char chosen to represent the codeName is n=
a= is as before for archive. Without a a= or n= both are checked.

So the line:
Pin: release n=squeeze
is equal to
Pin: release squeeze

See also apt_preference (5) for details on pinning to a codename.

This commit also made it possible to use codenames in
--target-release and in pkg/codename

So the commands
apt-get install awesome/unstable
and
apt-get install awesome/sid
are equal and work now as expected.



Best regards / Mit freundlichen Grüßen,

David "DonKult" Kalnischkies


--- End Message ---