Re: Will Sid go nuts?
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 to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
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 package from being integrated into the soon-to-be-released sarge. J. -- Television advertisements are the apothesis of twentieth century culture. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: Will Sid go nuts?
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 do not CC replies directly to me. I'll read them on the list. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
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 settle again. Is that right, Patrick? 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 years now, mostly reliable, with the occasional glitch. I can continue to live with that. In other words, cutting edge is OK, but bleeding edge is a bit too much for me! Thanks for everyone's advice. I think I'll stick with testing for now. Patrick
Re: Will Sid go nuts?
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 testing for a while, until things settle again. Is that right, Patrick? 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 years now, mostly reliable, with the occasional glitch. I can continue to live with that. In other words, cutting edge is OK, but bleeding edge is a bit too much for me! Thanks for everyone's advice. I think I'll stick with testing for now. 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. -- Any technology distinguishable from magic is insufficiently advanced. (*)http://www.spots.ab.ca/~keeling Please don't Cc: me. - - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
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 to stick with woody for the months to come. I just went to my /etc/apt/sources.list file and replaced all 'stable' to 'woody'. Several replacements were made. saved the file, and did apt-get update. No error messages. I seem to recall reading that woody will still be around for a year or so. I'm perfectly happy with woody and reallly don't feel like changing anything yet. -- Regards, dbp
Re: Will Sid go nuts?
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 do not expect this to happens. Newest perl and dpkg for example will go in sid after the release though they have been tested in experimental for more than a month. Though there will obviously will be upgrade issues that should not compare with the woody ones. Regards Alban -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
I think I'll still stick with unstable to be up to date.
Re: Will Sid go nuts?
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 I've had in my sources.list for a couple of years now, mostly reliable, with the occasional glitch. I can continue to live with that. In other words, cutting edge is OK, but bleeding edge is a bit too much for me! Thanks for everyone's advice. I think I'll stick with testing for now. 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? --- 5.6 What does the testing directory contain? Packages are installed into the `testing' directory after they have undergone some degree of testing in unstable. They must be in sync on all architectures where they have been built and mustn't have dependencies that make them uninstallable; they also have to have fewer release-critical bugs than the versions currently in testing [unstable?]. This way, we hope that `testing' is always close to being a release candidate. --- That doesn't sound as if it's about to go haywire. Patrick
Re: Will Sid go nuts?
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 years now, mostly reliable, with the occasional glitch. I can continue to live with that. In other words, cutting edge is OK, but bleeding edge is a bit too much for me! Thanks for everyone's advice. I think I'll stick with testing for now. 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. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
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 release. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
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. Packages will just begin to flow into Testing again after the release. That is slightly inaccurate. There are huge changes on the way (X.org 6.8.2, GNOME 2.10, and others). To say that nothing will go haywire is being very optimistic. Things will likely break for a bit once the flow of packages starts. -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~sanchezr pgpPFCzPogM4L.pgp Description: PGP signature
Re: Will Sid go nuts?
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? --- 5.6 What does the testing directory contain? Packages are installed into the `testing' directory after they have undergone some degree of testing in unstable. They must be in sync on all architectures where they have been built and mustn't have dependencies that make them uninstallable; they also have to have fewer release-critical bugs than the versions currently in testing [unstable?]. This way, we hope that `testing' is always close to being a release candidate. --- That doesn't sound as if it's about to go haywire. OK. Let me explain this better. Right now, sarge is in frozen which means only critical bugs are allowed into it. In a couple of days (hopefully), sarge with become stable and etch will become the new testing. The system will once again allow packages to come into testing (which is now etch) from unstable after 2 to 10 days of no critical bug submissions. The developers will be allowed to submit packages into unstable that they were not allowed to during the freeze. This is usually a *lot* of packages. So, a couple of days after all these packages are submitted, they will eventually find their way into testing. If you can put up with that sudden wave of packages a couple of days after sarge is released (and a steady stream of updates after that), then keep on using testing. If you just want security fixes, use sarge. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
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? --- 5.6 What does the testing directory contain? Packages are installed into the `testing' directory after they have undergone some degree of testing in unstable. They must be in sync on all architectures where they have been built and mustn't have dependencies that make them uninstallable; they also have to have fewer release-critical bugs than the versions currently in testing [unstable?]. This way, we hope that `testing' is always close to being a release candidate. --- That doesn't sound as if it's about to go haywire. OK. Let me explain this better. Right now, sarge is in frozen which means only critical bugs are allowed into it. In a couple of days (hopefully), sarge with become stable and etch will become the new testing. The system will once again allow packages to come into testing (which is now etch) from unstable after 2 to 10 days of no critical bug submissions. The developers will be allowed to submit packages into unstable that they were not allowed to during the freeze. This is usually a *lot* of packages. So, a couple of days after all these packages are submitted, they will eventually find their way into testing. If you can put up with that sudden wave of packages a couple of days after sarge is released (and a steady stream of updates after that), then keep on using testing. If you just want security fixes, use sarge. 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
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 name for unstable. The next testing will be Etch, so once Sarge is stable, we have: Stable = Sarge Testing = Etch Unstable = Sid If you read up on the characters in Toy Story, it makes sense, since Sid is the kid next store who breaks toys. Hal -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
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 available at http://www.people.cornell.edu/pages/kk288/debian_choosing_distribution.html In particular Q 13, 15 might be of interest to you. raju -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
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 clears the situation a bit, Rogério Brito. -- Rogério Brito : [EMAIL PROTECTED] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
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 prevent the packages to hit testing (and filing bug reports with appropriate severity if they are not yet ready for public consumption). 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). -- Rogério Brito : [EMAIL PROTECTED] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Will Sid go nuts?
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 PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
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 there will obviously massive changes (X.org, KDE, Gnome, gcc? etc.). The good thing is that there are already many packages which have been quite well tested either in Ubuntu or in some experimental archive. For example, I don't expect serious breakage when X.org is introduced. But well, there are several thousand packages in Debian... J. -- I wish I could achieve a 'just stepped out of the salon' look more often. Or at least once. [Agree] [Disagree] http://www.slowlydownward.com/NODATA/data_enter2.html signature.asc Description: Digital signature
Re: Will Sid go nuts?
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 _had_ planned on just staying with 'testing' in my sources.list. Is that a bad idea? Patrick
Re: Will Sid go nuts?
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 long time. Will that be the case again? I _had_ planned on just staying with 'testing' in my sources.list. Is that a bad idea? 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). If you want to continue to track the newer stuff and aren't afraid of a breakage here or there, then keep with testing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
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 release occurs. -- John Hasler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Will Sid go nuts?
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 to Woody. It will be switched to point to Sarge when the release occurs. Well, you can, just don't expect to be seeing upgrades until after June 6... -- Paul Johnson Email and Instant Messenger (Jabber): [EMAIL PROTECTED] http://ursine.ca/~baloo/ pgpvBU3nX4tWT.pgp Description: PGP signature
Re: Will Sid go nuts?
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. So, you're not the only one. But if you *do* need a rock-solid desktop, then stable is what you should stick to. -- Rogério Brito : [EMAIL PROTECTED] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
