[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#240697: #24697: Sarge installer: change apt-setup to point to sarge instead of testing



Doing further installations and tests I find myself still not (yet) convinced 
just by being told d-i will do the right thing. I have a cuple of questions, 
maybe somone could help a bit.


In order to use and test sarge I did the installations from the prerelease 
(beta) _sarge_-netinst d-i CD. I'd like my (inhouse) systems to be sarge now 
and automaticly stable upon official release. That is the behaviour I would 
have expected from a "Sarge Installer CD". OTOH a  "Testing Installer CD" 
would be fine tracking testing forever.

OK here are my questions:
-- Will the entries in sources.list that are all pointing to testing (exept 
for the cdrom entry) be changed to stable the moment sarge is released? 
( s/testing/stable) So that no further testing updates can be drawn in 
accidentially. (I recognize a stable/update security entry is already there, 
but not sufficient)

-- Will the choose mirror funktion (apt-setup) only generate entries pointing 
to stable upon release date?

-- What would be wrong with having the apt-setup on sarge CDs default to sarge 
now? Making sure that explicit sarge CDs will still install a, then stable, 
sarge system later, and that sarge systems installed now will stay with sarge 
and not update to the ongoing testing after release. (For the sarge+1release 
situation see below.)

-- The default can be changed from sarge to stable just as it needs to be 
changed from testing to stable now, only that it is far less time critical.

1. default apt-setup to point to sarge on sarge CDs etc. now. (I assume this 
is a simple config option)

2. change apt-setup default to stable for release. (As usual, just that it 
used to be a change from testing to stable)

3. provide a security update that changes apt-setup's config to default to 
stable instead of sarge and s/sarge/stable in sources.list This would only 
affect systems that have been previously installed (prerelease sarge), or may 
be installed later from one of the many prerelease d-i sarge CDs that are 
around now. (This update should not time be critical at all, as long as 
sarge+1 is not expected to be released too early.)

Regards,
Christian







Reply to: