Upgrading to Testing (was: Re: Ive been getting scanned...)
What are the proper lines to put in /etc/apt/sources.list to upgrade from stable to testing? I seem to recal someone on the list saying to replace the lines for stable with: deb http://http.us.debian.org/debian testing main contrib non-free deb http://http.us.debian.org/debian unstable main contrib non-free but this will also get packages from unstable, which I would prefer not to do at this time. If I do make these changes and do an 'apt-get update/upgrade' then apt wants to upgrade 188 packages on my box, add 40 some packages and delete 11 packages. If I only have the line for testing in my sources.list then 'upgrade' only wants to change 7 packages and 'dist-upgrade' also updates only 7 packages and wants to delete 3 others. There is much that simply does not exist in testing that is in stable and unstable. I thought that testing was a complete set of packages, but this does not seem to be the case. Can anyone explain exactly the way packages flow through the system, including when a new release becomes stable? If you don't want to be running year-old software (with the latest security fixes backported), switch over to testing instead. It's both pretty solid and pretty recent. But if you want/need the absolute reliability of stable, that takes time. If it takes a year to produce that stability, then the code will be a year old when it's released and, short of spending lots of money to buy testing and bugfixing time, there's nothing anyone can do about it. -- Marc Shapiro If you drink melomel every day, [EMAIL PROTECTED]you will live to be 150 years old, Please visit The Meadery at: unless your wife shoots you. http://www.bigfoot.com/~m_shapiro/ -- Dr. Ferenc Androczi, winemaker, Little Hungary Farm Winery
Re: Upgrading to Testing (was: Re: Ive been getting scanned...)
On Sun, May 27, 2001 at 06:07:24AM -0400, Marc Shapiro wrote: What are the proper lines to put in /etc/apt/sources.list to upgrade from stable to testing? I seem to recal someone on the list saying to replace the lines for stable with: deb http://http.us.debian.org/debian testing main contrib non-free deb http://http.us.debian.org/debian unstable main contrib non-free but this will also get packages from unstable, which I would prefer not to do at this time. If I do make these changes and do an 'apt-get update/upgrade' then apt wants to upgrade 188 packages on my box, add 40 some packages and delete 11 packages. If I only have the line for testing in my sources.list then 'upgrade' only wants to change 7 packages and 'dist-upgrade' also updates only 7 packages and wants to delete 3 others. There is much that simply does not exist in testing that is in stable and unstable. I thought that testing was a complete set of packages, but this does not seem to be the case. Can anyone explain exactly the way packages flow through the system, including when a new release becomes stable? You really could have started another string here. Anyway your questions are answered at - http://www.debian.org/releases/ kent -- From seeing and seeing the seeing has become so exhausted First line of The Panther - R. M. Rilke
Re: Upgrading to Testing (was: Re: Ive been getting scanned...)
On Sun, 27 May 2001 06:07:24 EDT, Marc wrote: What are the proper lines to put in /etc/apt/sources.list to upgrade from stable to testing? I seem to recal someone on the list saying to replace the lines for stable with: deb http://http.us.debian.org/debian testing main contrib non-free That line is correct, leave unstable out of it, unless you want sid. but this will also get packages from unstable, which I would prefer not to do at this time. If I do make these changes and do an 'apt-get update/upgrade' then apt wants to upgrade 188 packages on my box, add 40 some packages and delete 11 packages. If I only have the line for testing in my sources.list then 'upgrade' only wants to change 7 packages and 'dist-upgrade' also updates only 7 packages and wants to delete 3 others. There is much that simply does not exist in testing that is in stable and unstable. I thought that testing was a complete set of packages, but this does not seem to be the case. Can anyone explain exactly the way packages flow through the system, including when a new release becomes stable? Testing is a bit screwy right now, but word is it should be fixed sometime soon. AFAIK, there's something wrong with the Packages file, but I could be wrong. I'd wait a day or so so they can get everything repaired. Anyone know more or more accurate info? -- Paul T. Wright [EMAIL PROTECTED] -currently seeking employment-
Re: Upgrading to Testing (was: Re: Ive been getting scanned...)
Marc Shapiro [EMAIL PROTECTED] wrote: What are the proper lines to put in /etc/apt/sources.list to upgrade from stable to testing? I seem to recal someone on the list saying to replace the lines for stable with: deb http://http.us.debian.org/debian testing main contrib non-free deb http://http.us.debian.org/debian unstable main contrib non-free but this will also get packages from unstable, which I would prefer not to do at this time. If I do make these changes and do an 'apt-get update/upgrade' then apt wants to upgrade 188 packages on my box, add 40 some packages and delete 11 packages. If I only have the line for testing in my sources.list then 'upgrade' only wants to change 7 packages and 'dist-upgrade' also updates only 7 packages and wants to delete 3 others. There is much that simply does not exist in testing that is in stable and unstable. I thought that testing was a complete set of packages, but this does not seem to be the case. Can anyone explain exactly the way packages flow through the system, including when a new release becomes stable? Somebody's replied already to say that testing was broken yesterday; normally you'd see a lot more change than that. Discounting that ... 'testing' is a fairly new invention to try to help speed up release cycles. The idea, roughly, is that it's normally not too far behind unstable but doesn't suffer from some of the worse problems in unstable. Developers upload new versions of packages to unstable, and, after a period of time there, individual versions of packages migrate into testing according to various rules: they can't have any high-severity bugs filed against them, and putting them into testing can't make more packages uninstallable than was already the case. testing started off as a copy of stable, but at various times I think things have got out of kilter in such a way as to leave certain packages in stable and unstable but not testing (but I may be misremembering there). That should mostly get fixed before release. Sooner or later, after testing has been largely frozen for a while so that we can, er, test it, the release manager decides that today is a good day to release. At that point, testing becomes stable, a new testing branch is created, and we go round again. Since woody will be our first release with testing, I'm not sure if anybody knows yet quite how it'll go. Cheers, -- Colin Watson [EMAIL PROTECTED]
