Re: Rejig apt Config Now That Woody = stable ?
On Wed, 31 Jul 2002, Nick wrote:
> I've been running Woody-testing for a while, so now that Woody is
> released do I need to amend my apt config files to take account of the
> fact that Woody = stable and Sarge = testing ?
>
> I've been using the "pinning" method to ensure I get updates from
> testing unless I specify unstable, so I currently have :
>
> =========================< cut >===========================
> MYBOX:/etc/apt# cat sources.list
> [...]
> deb http://ftp.uk.debian.org/debian/ testing main
> deb http://ftp.uk.debian.org/debian/ unstable main
> deb http://ftp.uk.debian.org/debian-non-US/ testing/non-US main
> non-free
> deb http://ftp.uk.debian.org/debian-non-US/ unstable/non-US main
> non-free
>
> deb http://security.debian.org/ stable/updates main contrib non-free
>
> MYBOX:/etc/apt# cat preferences
> Package: *
> Pin: release a=testing
> Pin-Priority: 900
>
> Package: *
> Pin: release a=unstable
> Pin-Priority: 50
> =========================< cut >===========================
Cool. I've been looking to do something like this.
>
> Presumably, with these config settings a straight apt-get will now get
> me packages from Sarge ..
>
> I've seen a post from Vineet Kumar on 3.Jul.2002 at
> http://lists.debian.org/debian-user/2002/debian-user-200207/msg00346.html
> which suggests you can use the release codenames instead of
> descriptive names in the config files - i.e.
>
> use "woody" instead of "stable"
> use "sarge" instead of "testing"
> use "sid" instead of "unstable"
>
> So, e.g. in "sources.list" :
> deb http://ftp.uk.debian.org/debian/ woody main
> instead of
> deb http://ftp.uk.debian.org/debian/ testing main
>
> Is this true ?
> Is it the Right Thing To Do ?
I believe the only reason you might want to do this is if you
don't want to suddenly have your system updated if sarge suddenly became
stable and the next release after was made the new testing. Note that
sid is alway going to be referred to as unstable so there is no
difference.
If you want to run testing by default then leave your current setting in place.
That way testing will always have new package coming into while at times it
will be frozen after which a new stable will be born from the frozen
testing. Once that is done testing will then be unfrozen and continue
to progress to the next stable release which is what is occuring now with
sarge = testing.
Reply to: