Re: experimental codename: scud?

2003-12-17 Thread Matthew A. Nicholson
On Wed, 17 Dec 2003 22:56:21 +0100, GCS <[EMAIL PROTECTED]> wrote: On Wed, Dec 17, 2003 at 11:56:30AM +0100, Toens Bueker <[EMAIL PROTECTED]> wrote: Hamish Harvey <[EMAIL PROTECTED]> wrote: > I'm not on the list, just follow DWN. Just a thought, > but naming something after a missile seems odd. Qu

Re: experimental codename: scud?

2003-12-17 Thread GCS
On Wed, Dec 17, 2003 at 11:56:30AM +0100, Toens Bueker <[EMAIL PROTECTED]> wrote: > Hamish Harvey <[EMAIL PROTECTED]> wrote: > > > I'm not on the list, just follow DWN. Just a thought, > > but naming something after a missile seems odd. > > Question is, after what the missile was named ... If I

Re: experimental codename: scud?

2003-12-17 Thread Toens Bueker
Vincent Renardias <[EMAIL PROTECTED]> wrote: > > > I'm not on the list, just follow DWN. Just a thought, > > > but naming something after a missile seems odd. > > > > Question is, after what the missile was named ... > > Extract from http://en.wikipedia.org/wiki/Scud: > > "Scud is the NATO repo

Re: experimental codename: scud?

2003-12-17 Thread Vincent Renardias
On Wed, 2003-12-17 at 11:56, Toens Bueker wrote: > Hamish Harvey <[EMAIL PROTECTED]> wrote: > > > I'm not on the list, just follow DWN. Just a thought, > > but naming something after a missile seems odd. > > Question is, after what the missile was named ... Extract from http://en.wikipedia.org/w

Re: experimental codename: scud?

2003-12-17 Thread Toens Bueker
Hamish Harvey <[EMAIL PROTECTED]> wrote: > I'm not on the list, just follow DWN. Just a thought, > but naming something after a missile seems odd. Question is, after what the missile was named ... by Töns -- There is no safe distance.

experimental codename: scud?

2003-12-17 Thread Hamish Harvey
I'm not on the list, just follow DWN. Just a thought, but naming something after a missile seems odd. Hamish

Re: experimental codename

2003-12-16 Thread Andreas Metzler
Graham Wilson <[EMAIL PROTECTED]> wrote: [...] > I think maybe many problems with using experimental as a playground for > development packages could be remedied by creating a central document > about it. Things to include might be: > * sources.lists lines > * using APT's preferences to pin pack

Re: experimental codename

2003-12-16 Thread Graham Wilson
On Tue, Dec 16, 2003 at 01:03:57AM +0100, Arnaud Vandyck wrote: > Graham Wilson <[EMAIL PROTECTED]> writes: > > On Mon, Dec 15, 2003 at 08:44:42PM +0100, Arnaud Vandyck wrote: > >> it's a bit different and for different arches. What about the arches > >> `all'? Well, I'm maybe a particular case: po

Re: experimental codename

2003-12-15 Thread Henning Makholm
Scripsit Graham Wilson <[EMAIL PROTECTED]> > However, I am not (nor do I believe a majority might be) that > experimental should duplicate unstable, with only a few packages (the > experimental ones) being newer. However, with the pool structure > archive, this might not actually mean a duplicatio

Re: experimental codename

2003-12-15 Thread Arnaud Vandyck
Graham Wilson <[EMAIL PROTECTED]> writes: > On Mon, Dec 15, 2003 at 08:44:42PM +0100, Arnaud Vandyck wrote: [...] >> it's a bit different and for different arches. What about the arches >> `all'? Well, I'm maybe a particular case: powerpc + java ;) but it >> could be the same with sparc + perl o

Re: experimental codename

2003-12-15 Thread Graham Wilson
On Mon, Dec 15, 2003 at 08:44:42PM +0100, Arnaud Vandyck wrote: > Graham Wilson <[EMAIL PROTECTED]> writes: > > If this would lead to more developers and beta-testers being able to > > use experimental, then I think this would be a good idea. People might > > upload there newer more in-development

Re: experimental codename

2003-12-15 Thread Arnaud Vandyck
Michael Poole <[EMAIL PROTECTED]> writes: > John Hasler writes: > >> gram writes: >>> Every new package, or every new upload? >> >> Perhaps every upload to Unstable should go to Experimental as well unless >> Experimental already has a newer package (or the same one), but uploads to >> Experimenta

Re: experimental codename

2003-12-15 Thread Arnaud Vandyck
Graham Wilson <[EMAIL PROTECTED]> writes: > On Mon, Dec 15, 2003 at 02:10:22PM +0100, Arnaud Vandyck wrote: [...] >> What I'm trying to explain is that I like the idea of an extra pool >> with the buildd and bts but no automatic move to another pool. I >> think, DD and people with chroot can poi

Re: experimental codename

2003-12-15 Thread Michael Poole
John Hasler writes: > gram writes: >> Every new package, or every new upload? > > Perhaps every upload to Unstable should go to Experimental as well unless > Experimental already has a newer package (or the same one), but uploads to > Experimental should go to Experimental only. Nothing would eve

Re: experimental codename

2003-12-15 Thread John Hasler
gram writes: > Every new package, or every new upload? Perhaps every upload to Unstable should go to Experimental as well unless Experimental already has a newer package (or the same one), but uploads to Experimental should go to Experimental only. Nothing would ever move from Experimental to any

Re: experimental codename

2003-12-15 Thread Graham Wilson
On Mon, Dec 15, 2003 at 02:10:22PM +0100, Arnaud Vandyck wrote: > Colin Watson <[EMAIL PROTECTED]> writes: > > I think that's the way it should be. Experimental isn't a complete > > distribution in the sense that the others are, so it doesn't really > > deserve a codename. > > Isn't it possible th

Re: experimental codename

2003-12-15 Thread Joel Baker
On Mon, Dec 15, 2003 at 01:38:37PM +0100, Christoph Berg wrote: > Re: Neil McGovern in <[EMAIL PROTECTED]> > > I like it too :) > > Thanks :) > > > Prehaps it could be used as a codename for the new unstable when Sarge > > is released as stable? > > That's not the way it works; "Sid" is not "Sar

Re: experimental codename

2003-12-15 Thread Arnaud Vandyck
Colin Watson <[EMAIL PROTECTED]> writes: > On Mon, Dec 15, 2003 at 01:50:00AM +0100, Christoph Berg wrote: >> since we are discussing codenames for the Debian/*BSD OSs, I noticed >> that the "experimental" distribution doesn't have a codename yet, as >> unstable has with "Sid". > > I think that's

Re: experimental codename

2003-12-15 Thread Christoph Berg
Re: Neil McGovern in <[EMAIL PROTECTED]> > I like it too :) Thanks :) > Prehaps it could be used as a codename for the new unstable when Sarge > is released as stable? That's not the way it works; "Sid" is not "Sarge+1" but the never-to-be- released development version. Think of it as "version i

Re: experimental codename

2003-12-15 Thread Neil McGovern
On Mon, Dec 15, 2003 at 02:46:27AM +0100, Rene Engelhard wrote: > Christoph Berg wrote: > > since we are discussing codenames for the Debian/*BSD OSs, I noticed > > that the "experimental" distribution doesn't have a codename yet, as > > unstable has with "Sid". I'd propose to call it "Scud", which

Re: experimental codename

2003-12-15 Thread Colin Watson
On Mon, Dec 15, 2003 at 01:50:00AM +0100, Christoph Berg wrote: > since we are discussing codenames for the Debian/*BSD OSs, I noticed > that the "experimental" distribution doesn't have a codename yet, as > unstable has with "Sid". I think that's the way it should be. Experimental isn't a complet

Re: experimental codename

2003-12-14 Thread Rene Engelhard
Hi, Christoph Berg wrote: > since we are discussing codenames for the Debian/*BSD OSs, I noticed > that the "experimental" distribution doesn't have a codename yet, as > unstable has with "Sid". I'd propose to call it "Scud", which is the > Name of Sid's dog (which broke toys even worse than Sid d

experimental codename

2003-12-14 Thread Christoph Berg
Hello, since we are discussing codenames for the Debian/*BSD OSs, I noticed that the "experimental" distribution doesn't have a codename yet, as unstable has with "Sid". I'd propose to call it "Scud", which is the Name of Sid's dog (which broke toys even worse than Sid did ;-). Christoph [1] htt