Bug#594461: apt-setup: Should propose using t-p-u when testing is installed
On Thu, Aug 26, 2010 at 10:03:40AM +0200, Petter Reinholdtsen wrote:
> [Christian PERRIER]
> > After a (short) discussion in -devel, I came up with the proposal of
> > activating "testing-proposed-updates" when users install testing, in
> > a similar way that we currently propose activating volatile when
> > they install stable.
> One challenge that should be considered, is what should happen when
> testing become stable, and the meaning of testing-proposed-updates
> changes.
> For example now, testing-proposed-updates is packages intended for
> squeeze, and after the release, it will no longer have packages
> intended for squeeze.
> Should those installing testing today keep using testing, or should
> they get squeeze? If they should get squeeze, the
> testing-proposed-update source will give them the wrong set of
> packages after squeeze is released.
There is a 'squeeze-proposed-updates' alias for 'testing-proposed-updates',
which will continue to work after release (when it becomes
'stable-proposed-updates' instead). So whatever method is used for
configuring sources.list currently (and I think it's always right to use the
codename here rather than the suite name, to avoid accidental dist-upgrades
down the line) should apply equally well to testing-proposed-updates in that
sense.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
slangasek@ubuntu.com vorlon@debian.org
Reply to: