Potato-Woody HOWTO?
Hi! I've just subscribed to the list a few days ago and I'm seeing many messages about people migrating from the Stable to the Testing version of Debian which makes me think that it's not such a painful process as I had thought. Is there a HOWTO or something (perhaps in the archives?) explaining how to do it? (passing from the stable version to the testing version) Can anyone enlighten me? Thanks in advance, Yago
RE: Potato-Woody HOWTO?
I've just subscribed to the list a few days ago and I'm seeing many messages about people migrating from the Stable to the Testing version of Debian which makes me think that it's not such a painful process as I had thought. Is there a HOWTO or something (perhaps in the archives?) explaining how to do it? (passing from the stable version to the testing version) Can anyone enlighten me? Welcome. I just did this yesterday. It was so simple, even *I* couldn't screw it up. In /etc/apt/sources.list, change all occurrences of 'potato' to either 'testing' or 'woody'. The difference is subtle. See Colin's message that he posted a few minutes ago for the distinction. Then, do 'apt-get update', followed by 'apt-get dist-upgrade'. Done. I chose not to upgrade XFree. One problem at a time.
Re: Potato-Woody HOWTO?
On Thursday 20 September 2001 09:05 am, Yago Alvarado wrote: Hi! I've just subscribed to the list a few days ago and I'm seeing many messages about people migrating from the Stable to the Testing version of Debian which makes me think that it's not such a painful process as I had thought. Is there a HOWTO or something (perhaps in the archives?) explaining how to do it? (passing from the stable version to the testing version) It's really very simple. Edit /etc/apt/sources.list s/stable/testing/ all lines in the file. comment out the debian-security lines. Run apt-get update. Run apt-get dist-upgrade. Pay close attention to any errors that appear during the dist-upgrade process. You may need to run it more than once before it gets all the dependencies sorted out. Be prepared for a Very Large Download. I am in the process of upgrading a potato box at work. It wanted to download a bit less than 300 MB. I aborted the dist-upgrade and set up a cron job to download the files last night. Hopefully they will be there when I get to work tomorrow. I upgraded this box from stable to testing and then from testing to unstable using that process. I currently track unstable with an update/upgrade process running from cron every night. So far I have had very few surprises. -- Bud Rogers [EMAIL PROTECTED] They have awakened a sleeping giant and filled him with a terrible resolve.
RE: Potato-Woody HOWTO?
No need for a howto: 1) Edit /etc/apt/sources.list and add these lines so you can see the testing packages: [ ...] If the apt-get dist-upgrade stops due to an error, just run it again. Thanks a lot. That's what I call clear instructions. :-) Regards, Yago
RE: Potato-Woody HOWTO?
I just did this yesterday. It was so simple, even *I* couldn't screw it up. Thanks for the help. :-) I chose not to upgrade XFree. One problem at a time. Can you do that? I mean... can you unselect the packages you don't want to install? :-? Regards, Yago
RE: Potato-Woody HOWTO?
On Thu, 20 Sep 2001, Bob Koss wrote: I've just subscribed to the list a few days ago and I'm seeing many messages about people migrating from the Stable to the Testing version of Debian which makes me think that it's not such a painful process as I had thought. Is there a HOWTO or something (perhaps in the archives?) explaining how to do it? (passing from the stable version to the testing version) Can anyone enlighten me? Welcome. I just did this yesterday. It was so simple, even *I* couldn't screw it up. In /etc/apt/sources.list, change all occurrences of 'potato' to either 'testing' or 'woody'. The difference is subtle. See Colin's message that he posted a few minutes ago for the distinction. Then, do 'apt-get update', followed by 'apt-get dist-upgrade'. I would suggest woody since when woody becomes stable testing will point to something you probably wouldn't want it too. i.e. testing would once again consist a small number of packages so that the next stable release after woody can be 'tested'. At least this is my perception. -walter ps. Older video cards don't seem to be backported to the newer XFree86 but I imagine one can install one of the older X3.3.6 servers... As for newer cards it was a distinct pleasure to note that the latest X11 apt update resulted in my new rage128 card working!
RE: Potato-Woody HOWTO?
I chose not to upgrade XFree. One problem at a time. Can you do that? I mean... can you unselect the packages you don't want to install? :-? The installation / configuration tool asks you questions. I opted to leave anything to do with X the way it was.
Re: Potato-Woody HOWTO?
On Thu, Sep 20, 2001 at 03:57:02PM +0100, Yago Alvarado wrote: I chose not to upgrade XFree. One problem at a time. Can you do that? I mean... can you unselect the packages you don't want to install? :-? No. The reason you can choose to leave X behind is that the packaging has changed. X 3.3.x uses a flock of xserver-card type packages, while X 4.0.x has a single xserver-xfree86 package which handles all video cards. -- With the arrest of Dimitry Sklyarov it has become apparent that it is not safe for non US software engineers to visit the United States. - Alan Cox To prevent unauthorized reading... - Adobe eBook reader license
Re: Potato-Woody HOWTO?
On Thu, Sep 20, 2001 at 11:00:02AM -0400, Walter Tautz wrote: I would suggest woody since when woody becomes stable testing will point to something you probably wouldn't want it too. i.e. testing would once again consist a small number of packages so that the next stable release after woody can be 'tested'. At least this is my perception. I doubt it will contain a small number of packages. Anthony hasn't said anything about it straight out, but I'd imagine that the new testing will start out from woody and be gradually upgraded as normal. That's how the current testing was bootstrapped; it only lost packages sometimes because of the odd bug in the testing scripts. -- Colin Watson [EMAIL PROTECTED]
