Skip to content

How to pin lenny?

Dear lazyweb, how do I pin lenny now and have that pin hold after lenny's release?

  • Codename lenny doesn't work, apt cannot do this (#433624, 18 months old, without any reaction yet)
  • Version 5.0 doesn't work, lenny's Release file doesn't have a Version field yet
  • Suite testing will match lenny now and then track squeeze once squeeze is testing
Is there any method that will get me testing lenny now and stable lenny later and not testing squeeze?


No Trackbacks


Display comments as Linear | Threaded

Loïc Minier on :

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

Marc 'Zugschlus' Haber on :

Yes, I can pin suite, as I wrote in the original article, but that'll give me squeeze once somebody inadvertently updates sources.list.

Chris Lawrence on :

Pin v=5.0 and a=testing (two separate pins) at the same priority level and use codenames, not releases, in /etc/apt/sources.list. That way you'll never see lenny+1; apt will only know about lenny (testing -> v5.0) and sid (unstable -> unstable).

Marc 'Zugschlus' Haber on :

That might work, but one needs to be careful updating sources.list since preferences needs to be updated as well. This kind of defeats preferences' purpose of taking care of accidental sources.list updates.

markrian on :

What's wrong with just making sure sources.list is correctly pointing to lenny? The end result is identical. Is there a special set of circumstances where it's not?

Add Comment

Markdown format allowed
Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.
Form options