Your message dated Fri, 31 Jul 2009 21:39:07 +0200 with message-id <c64043e60907311239w4ad7b43ek1686614a5912c67@mail.gmail.com> and subject line Fixed: Support pinning and targeting by codename has caused the Debian Bug report #419188, regarding add support for code name in pinning mechanism 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@bugs.debian.org immediately.) -- 419188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=419188 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: add support for code name in pinning mechanism
- From: Eddy Petrișor <eddy.petrisor@gmail.com>
- Date: Sat, 14 Apr 2007 12:23:20 +0300
- Message-id: <46209D88.6010800@gmail.com>
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Package: apt Version: 0.6.46.4-0.1 Severity: wishlist Hello, Starting with Etch, Debian Installer doesn't put suites anymore in /etc/apt/sources.list. Taking that into account it would be nice if codename based pinning would be possible, since the Release files provide the needed information: head /var/lib/apt/lists/ftp.ro.debian.org_debian_dists_etch_Release Origin: Debian Label: Debian Suite: stable Version: 4.0r0 Codename: etch Date: Sun, 08 Apr 2007 10:41:22 UTC Architectures: alpha amd64 arm hppa i386 ia64 mips mipsel powerpc s390 sparc Components: main contrib non-free Description: Debian 4.0r0 Released 8 April 2007 MD5Sum: Since "c=" is taken already by "component", "c" for codename doesn't work :-/ : ======== for (unsigned J = 0; Fragments[J] != 0; J++) { if (strlen(Fragments[J]) < 3) continue; if (stringcasecmp(Fragments[J],Fragments[J]+2,"v=") == 0) RelVerStr = Fragments[J]+2; else if (stringcasecmp(Fragments[J],Fragments[J]+2,"o=") == 0) RelOrigin = Fragments[J]+2; else if (stringcasecmp(Fragments[J],Fragments[J]+2,"a=") == 0) RelArchive = Fragments[J]+2; else if (stringcasecmp(Fragments[J],Fragments[J]+2,"l=") == 0) RelLabel = Fragments[J]+2; else if (stringcasecmp(Fragments[J],Fragments[J]+2,"c=") == 0) RelComponent = Fragments[J]+2; } ======== - --- System information. --- Architecture: amd64 Kernel: Linux 2.6.18-4-amd64 Debian Release: 4.0 900 stable security.debian.org 900 stable ftp.ro.debian.org 900 stable eddyp.homelinux.net 700 testing snapshot.debian.net - --- Package information. --- Depends (Version) | Installed ==========================================-+-================ libc6 (>= 2.3.5-1) | 2.3.6.ds1-13 libgcc1 (>= 1:4.1.1-12) | 1:4.1.1-21 libstdc++6 (>= 4.1.1-12) | 4.1.1-21 debian-archive-keyring | 2007.02.19 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGIJ2HY8Chqv3NRNoRAhMPAJ9zmXKyUv/b/iJGwh2umWpyd1WLaQCeLvP4 RMq2Fav1c4XgfkE2cqV4MzQ= =RYIX -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
- To: 419188-close@bugs.debian.org
- Subject: Fixed: Support pinning and targeting by codename
- From: David Kalnischkies <kalnischkies+debian@gmail.com>
- Date: Fri, 31 Jul 2009 21:39:07 +0200
- Message-id: <c64043e60907311239w4ad7b43ek1686614a5912c67@mail.gmail.com>
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 ---