Re: not later than in testing
On 11014 March 1977, Keith Edmunds wrote:
>> also decided to allow versions from lenny into sarge-bpo, otherwise it
>> would be pretty useless.
> I disagree that it would be 'useless'.
> Could someone who supports the idea of post-Etch packages being present in
> sarge-backports please explain how to upgrade a system (that contains such
> packages) to etch?
If I need a >etch version I continue to need it when I switch to
etch. Otherwise I wouldnt need to run a lenny version in the first
place. So *I* would expect that >etch backports for sarge get a >etch
version into etch backports too.
That could also be a discussion item - have it so that you *can* upload
newer sarge backports, but only if it is << of one in etch-backports.
Would be enough if that << is just the debian rev to trigger an upgrade
when one goes sarge+bpo to etch+bpo.
Of course that destroys the upgradepath sarge+po to etch (without
backports). I dont think that would be a too big problem. You used
backports once and so seem to havent had too much trouble - why stop.
Hm.
Now - what do others here think? I described a different possibility in
another mail.
So, what do people here on the list think?
a.) have a second suite for the backports >> etch version and keep a
frozen sarge.
Advantage: Keeps an upgrade path of sarge+bpo -> clean etch.
Disadvantage: Much work on the ftpadmin side. And yet another suite,
add to confusion.
b.) the above, ie. make it a technical requirement that versions have to
be etch >> sarge. Where a new hidden setting would be added to the
bpo archive that contains the etch version numbers. (Plain etch +
security).
Advantage: Technically enforced that people who upload package
foobar to sarge-bpo have to take the steps to get foobar backported
to etch, if they want to upload a version that is not in etch.
Disadvantage: Upgrading means to continue to use backports.
People have to backport twice if they want it in sarge. Once for
etch, once for sarge.
I personally like option b more, as thats not as much work for me. :)
--
bye Joerg
[...]
While Debian is certainly about beer, and in some cases may even be
about free beer, Debian is mainly about free speech.
Reply to: