Re: Will Sid go nuts?

2005-06-04 Thread Alban Browaeys
Le Thu, 02 Jun 2005 23:57:48 +0300, Andres Järv a écrit : I think I'll still stick with unstable to be up to date. I think I'll still stick with unstable to be up to date.br I think i ll install sid to test bugs and fix them ... be etch released in a few monthes :) -- To UNSUBSCRIBE, email

Re: Will Sid go nuts?

2005-06-03 Thread Jochen Schulz
Rogério Brito: This has been done in the past and I would expect that things would not change so soon (see the many dummy bugs reported like this package is not suitable for testing). Exactly these packages *will* get into etch after sarge is stable! The dummy bugs are there to prevent the

Re: Will Sid go nuts?

2005-06-02 Thread Lee Braiden
On Thursday 02 Jun 2005 01:34, Patrick Wiseman wrote: I _had_ planned on just staying with 'testing' in my sources.list. Is that a bad idea? I think Patrick might be referring to switching from sid to testing for a while, until things settle again. Is that right, Patrick? -- Lee. Please

Re: Will Sid go nuts?

2005-06-02 Thread Patrick Wiseman
On 6/2/05, Lee Braiden [EMAIL PROTECTED] wrote: On Thursday 02 Jun 2005 01:34, Patrick Wiseman wrote: I _had_ planned on just staying with 'testing' in my sources.list. Is that a bad idea? I think Patrick might be referring to switching from sid to testing for a while, until things

Re: Will Sid go nuts?

2005-06-02 Thread s. keeling
Incoming from Patrick Wiseman: On 6/2/05, Lee Braiden [EMAIL PROTECTED] wrote: On Thursday 02 Jun 2005 01:34, Patrick Wiseman wrote: I _had_ planned on just staying with 'testing' in my sources.list. Is that a bad idea? I think Patrick might be referring to switching from sid to

Re: Will Sid go nuts?

2005-06-02 Thread dbp lists
On 6/2/05, s. keeling [EMAIL PROTECTED] wrote: So edit sources.list to say sarge instead of testing, and watch what others are encountering. Once you see how stable sarge is and how others are doing with the new testing, change sarge to testing and track the new testing. FYI I'm wanting

Re: Will Sid go nuts?

2005-06-02 Thread Alban Browaeys
Joe Potter jpotter1034 at cfl.rr.com writes: Hello all, When we get a Sarge release in a few days, we will get crazy behavior out of Sid for a while? I seem to remember that when Woody was released, updating in testing or Sid was a problem for a long time. Will that be the case again? I

Re: Will Sid go nuts?

2005-06-02 Thread =?ISO-8859-1?Q?Andres_J=E4rv?=
I think I'll still stick with unstable to be up to date.

Re: Will Sid go nuts?

2005-06-02 Thread Patrick Wiseman
On 6/2/05, Colin [EMAIL PROTECTED] wrote: Patrick Wiseman wrote: No - the original poster suggested that both testing and unstable were problematic after the last stable release. So I was concerned that the new 'testing' would be flaky for a while. I've found the current testing, which

Re: Will Sid go nuts?

2005-06-02 Thread Colin
Patrick Wiseman wrote: No - the original poster suggested that both testing and unstable were problematic after the last stable release. So I was concerned that the new 'testing' would be flaky for a while. I've found the current testing, which I've had in my sources.list for a couple of

Re: Will Sid go nuts?

2005-06-02 Thread John Hasler
Colin writes: You'll want to change testing to sarge if you want a stable system. If you leave it at testing, the system will go haywire a couple of weeks from now when etch becomes the new testing. Nothing will go haywire. Packages will just begin to flow into Testing again after the

Re: Will Sid go nuts?

2005-06-02 Thread Roberto C. Sanchez
On Thu, Jun 02, 2005 at 07:16:32PM -0500, John Hasler wrote: Colin writes: You'll want to change testing to sarge if you want a stable system. If you leave it at testing, the system will go haywire a couple of weeks from now when etch becomes the new testing. Nothing will go haywire.

Re: Will Sid go nuts?

2005-06-02 Thread Colin
Patrick Wiseman wrote: On 6/2/05, Colin [EMAIL PROTECTED] wrote: You'll want to change testing to sarge if you want a stable system. If you leave it at testing, the system will go haywire a couple of weeks from now when etch becomes the new testing. So this answer to a FAQ is false? ---

Re: Will Sid go nuts?

2005-06-02 Thread James Ronald
Patrick Wiseman wrote: On 6/2/05, Colin [EMAIL PROTECTED] wrote: You'll want to change testing to sarge if you want a stable system. If you leave it at testing, the system will go haywire a couple of weeks from now when etch becomes the new testing. So this answer to a FAQ is false? ---

Re: Will Sid go nuts?

2005-06-02 Thread Hal Vaughan
On Thursday 02 June 2005 10:54 pm, James Ronald wrote: snip I'm a Debian noob and don't understand... Won't , Sarge become Stable, Sid become Testing, whatever (etch??) become unstable? Also, this thread is in regard to Sid.. What happens to Sid if not become testing? JR Sid is always the

Re: Will Sid go nuts?

2005-06-02 Thread kamaraju kusumanchi
I'm a Debian noob and don't understand... Won't , Sarge become Stable, Sid become Testing, whatever (etch??) become unstable? Also, this thread is in regard to Sid.. What happens to Sid if not become testing? JR A more detailed explanation of what happens when a release is made is

Re: Will Sid go nuts?

2005-06-02 Thread =?iso-8859-1?Q?Rog=E9rio?= Brito
On Jun 02 2005, Colin wrote: So, a couple of days after all these packages are submitted, they will eventually find their way into testing. *IF* no bug with high severity is found/reported during the time between the upload of the package and the period necessary to hit testing. Hope this

Re: Will Sid go nuts?

2005-06-02 Thread =?iso-8859-1?Q?Rog=E9rio?= Brito
On Jun 02 2005, Roberto C. Sanchez wrote: That is slightly inaccurate. There are huge changes on the way (X.org 6.8.2, GNOME 2.10, and others). Yes, the main problems would be the partial migration of huge systems like Gnome. OTOH, the dependencies on basic packages may be a solution to

Will Sid go nuts?

2005-06-01 Thread Joe Potter
Hello all, When we get a Sarge release in a few days, we will get crazy behavior out of Sid for a while? I seem to remember that when Woody was released, updating in testing or Sid was a problem for a long time. Will that be the case again? Regards, Joe -- To UNSUBSCRIBE, email to [EMAIL

Re: Will Sid go nuts?

2005-06-01 Thread Jochen Schulz
Joe Potter: When we get a Sarge release in a few days, we will get crazy behavior out of Sid for a while? I seem to remember that when Woody was released, updating in testing or Sid was a problem for a long time. Will that be the case again? Nobody can say how seriously sid will break, but

Re: Will Sid go nuts?

2005-06-01 Thread Patrick Wiseman
On 6/1/05, Joe Potter [EMAIL PROTECTED] wrote: Hello all, When we get a Sarge release in a few days, we will get crazy behavior out of Sid for a while? I seem to remember that when Woody was released, updating in testing or Sid was a problem for a long time. Will that be the case again? I

Re: Will Sid go nuts?

2005-06-01 Thread Steve Witt
On Wed, 1 Jun 2005, Patrick Wiseman wrote: On 6/1/05, Joe Potter [EMAIL PROTECTED] wrote: Hello all, When we get a Sarge release in a few days, we will get crazy behavior out of Sid for a while? I seem to remember that when Woody was released, updating in testing or Sid was a problem for a

Re: Will Sid go nuts?

2005-06-01 Thread John Hasler
Steve Witt writes: It really depends upon you and how stable you need the machine(s) to be. If you need them to be pretty stable, then change that to 'sarge' (or stable). Don't change it to Stable now, though. Stable presently points to Woody. It will be switched to point to Sarge when the

Re: Will Sid go nuts?

2005-06-01 Thread Paul Johnson
On Wednesday June 1 2005 6:22 pm, John Hasler wrote: Steve Witt writes: It really depends upon you and how stable you need the machine(s) to be. If you need them to be pretty stable, then change that to 'sarge' (or stable). Don't change it to Stable now, though. Stable presently points

Re: Will Sid go nuts?

2005-06-01 Thread =?iso-8859-1?Q?Rog=E9rio?= Brito
On Jun 01 2005, Patrick Wiseman wrote: I _had_ planned on just staying with 'testing' in my sources.list. Is that a bad idea? I *will* stay with testing in my sources.list. It is a way to be always testing the distribution and reporting problems that you see, giving feedback to the developers.