Bug#433624: apt: please allow release pinning for suite and codename fields

2010-06-10 Thread David Kalnischkies
Hi,

2010/6/10 Gerfried Fuchs rho...@deb.at:
  The manpage apt_preferences(5) claims for a long while now already that
 pinning for codename is expected to work with n= - unfortunately that
 has no effect at all. So this isn't a wishlist but rather a quite
 unfortunate bug. :/

Could you provide a non-working example please?

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…

At least the following works:
Package: *
Pin: release n=sid
Pin-Priority: 300

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).


Best regards,

David Kalnischkies



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#433624: apt: please allow release pinning for suite and codename fields

2010-06-10 Thread Gerfried Fuchs
severity 433624 normal
thanks

Hi!

* Marc Haber mh+debian-b...@zugschlus.de [2007-07-18 12:03:11 CEST]:
 Please allow pinning for suite and codename fields in Release files.
 
 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).

 The manpage apt_preferences(5) claims for a long while now already that
pinning for codename is expected to work with n= - unfortunately that
has no effect at all. So this isn't a wishlist but rather a quite
unfortunate bug. :/

 Thanks,
Rhonda



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#433624: apt: please allow release pinning for suite and codename fields

2010-06-10 Thread Gerfried Fuchs
Hi!

* David Kalnischkies kalnischkies+deb...@gmail.com [2010-06-10 21:47:49 CEST]:
 2010/6/10 Gerfried Fuchs rho...@deb.at:
   The manpage apt_preferences(5) claims for a long while now already that
  pinning for codename is expected to work with n= - unfortunately that
  has no effect at all. So this isn't a wishlist but rather a quite
  unfortunate bug. :/
 
 Could you provide a non-working example please?

Package: *
Pin: release n=squeeze
Pin-Priority: 300

 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.

 At least the following works:
 Package: *
 Pin: release n=sid
 Pin-Priority: 300
 
 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.

 Thanks,
Rhonda
-- 
most users choose convenience over security, and that's reflected in the
 choice of the current default
   Hin-Tak Leung -- http://bugs.ghostscript.com/show_bug.cgi?id=691339#c7



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#433624: apt: please allow release pinning for suite and codename fields

2008-12-22 Thread Michael Goetze
I second this request. It would be very useful for early adopters of 
an almost-finished release.


Regards,
Michael



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#433624: apt: please allow release pinning for suite and codename fields

2008-12-22 Thread Loïc Minier
On Wed, Jul 18, 2007, Marc Haber wrote:
 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
 
   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).

 I think you can at least pin suite with a=:
a=testing

Last time I looked:
v= to match the Version header
o= to match the Origin header
a= to match the Archive / Suite header
l= to match the Label header
c= to match the Component header

-- 
Loïc Minier



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#433624: apt: please allow release pinning for suite and codename fields

2008-12-22 Thread Michael Goetze

Loïc Minier wrote:

 I think you can at least pin suite with a=:
a=testing


But that's not what we want since then we will suddenly be tracking 
squeeze when lenny is released (or squeeze+1 when squeeze is released or 
whatever). That might be fine on a single desktop machine but it doesn't 
scale well.




--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#433624: apt: please allow release pinning for suite and codename fields

2008-12-22 Thread Loïc Minier
On Tue, Dec 23, 2008, Michael Goetze wrote:
  I think you can at least pin suite with a=:
 a=testing
 But that's not what we want since then we will suddenly be tracking  
 squeeze when lenny is released (or squeeze+1 when squeeze is released or  
 whatever). That might be fine on a single desktop machine but it doesn't  
 scale well.

 The request was about pinning suite and codename; I replied to the
 suite part.

-- 
Loïc Minier



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#433624: apt: please allow release pinning for suite and codename fields

2007-07-18 Thread Marc Haber
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


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]