Re: Changing from stable to testing.....
Hi Whit, last time I tried to dist-upgrade to squeeze, I got stuck in an (for me) unresolvable loop: The system wanted to upgrade the kernel-image and udev in one run - which failed. apt-get always complained, that the kernel-image needs the new udev-package to upgrade - and udev itself needed the new kernel-image... I don't know, if this problem still exists - if yes: you should find a way of not getting into this loop, where no apt-get -f install helped to stop this. I reinstalled lenny after this... ;) Best regards, sigi On Sat, Oct 23, 2010 at 10:35:31PM -0400, Whit Hansell wrote: Just thinking that since Squeeze is coming up to be the new stable and have been running Lenny since March of 2009, I was wondering about how difficult it would be to change from Lenny(stable) to Squeeze(testing) now. [...] -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101025173952.ga4...@cpunk.de
Re: Changing from stable to testing.....
On Mon, Oct 25, 2010 at 07:39:52PM +0200, sigi wrote: last time I tried to dist-upgrade to squeeze, I got stuck in an (for me) unresolvable loop: The system wanted to upgrade the kernel-image and udev in one run - which failed. apt-get always complained, that the kernel-image needs the new udev-package to upgrade - and udev itself needed the new kernel-image... I don't know, if this problem still exists - if yes: you should find a way of not getting into this loop, where no apt-get -f install helped to stop this. I reinstalled lenny after this... ;) This is #571255. udev should be fixed and in testing by now. -- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187 signature.asc Description: Digital signature
Re: Changing from stable to testing.....
On Mon, Oct 25, 2010 at 07:39:52PM +0200, sigi wrote: Hi Whit, last time I tried to dist-upgrade to squeeze, I got stuck in an (for me) unresolvable loop: The system wanted to upgrade the kernel-image and udev in one run - which failed. apt-get always complained, that the kernel-image needs the new udev-package to upgrade - and udev itself needed the new kernel-image... I don't know, if this problem still exists - if yes: you should find a way of not getting into this loop, where no apt-get -f install helped to stop this. I reinstalled lenny after this... ;) Yeah udev needs 2.6.27 or higher, so you have to upgrade the kernel first, then reboot, then do the whole upgrade. I have no idea what the plan for handling the upgrade is officially. Maybe the release notes are supposed to offer some hint. -- Len Sorensen -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101025184254.gr12...@caffeine.csclub.uwaterloo.ca
Re: Changing from stable to testing.....
On Mon, Oct 25, 2010 at 02:42:54PM -0400, Lennart Sorensen wrote: On Mon, Oct 25, 2010 at 07:39:52PM +0200, sigi wrote: Hi Whit, last time I tried to dist-upgrade to squeeze, I got stuck in an (for me) unresolvable loop: The system wanted to upgrade the kernel-image and udev in one run - which failed. apt-get always complained, that the kernel-image needs the new udev-package to upgrade - and udev itself needed the new kernel-image... I don't know, if this problem still exists - if yes: you should find a way of not getting into this loop, where no apt-get -f install helped to stop this. I reinstalled lenny after this... ;) Yeah udev needs 2.6.27 or higher, so you have to upgrade the kernel first, then reboot, then do the whole upgrade. I have no idea what the plan for handling the upgrade is officially. Maybe the release notes are supposed to offer some hint. I've had problems like this several times, in several upgrades from an old stable to a new. Sometimes X, sometimes udev, and once running out of disk space for the upgrade. Usually I end up with an unusable system. Not acceptable for a production system. As a result I always copy the old stable system into separate partition(s), so that when an upgrade fails I can boot into the other copy and have Because of these problems on a production machine, I've gradually learned to copy the old stable system into a separate partition, and then chroot to that to upgrade the copy while the old system is still running. Of course, things go wrong this way, too. Some packages want to fiddle with /proc during upgrade, and it isn't there. I'm not at all sure whether to provide it. Often things can be patched by booting to the incompletely updated new system and resuming the upgrade. This does reduce the amount of time the productin system is in an unusable state. I'd really like it if there were to be viable instructions in the release notes how to upgrade in a chroot, but I've never seen them. -- hendrik -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101026015258.ga4...@topoi.pooq.com
Re: Changing from stable to testing.....
On Mon, Oct 25, 2010 at 09:10:09PM -0500, Karl Schmidt wrote: I did the upgrade from lenny to squeeze without any problems - if you read the wiki, you are supposed to upgrade apt dpkg and aptitude first - then the kernel - then distupgrade. And was your system up and usable during pretty well the entire install? Except during the reboot for the new kernel, of course. I'm talking of network services, such as mail forwarding, NFS service, etc. If so, I'll probably copy the entire system (so I have a fallback just in case) and then upgrade as above. It worked - but - there is always some cruft that accumulates - so if you have time, you might want to bkup your old etc and home - then move to a new install - migrating configs one at a time. Some of my cruft dated back to sarge... On the other hand - with a nvidia card and dual head monitors - kde4 is amazing - I think we just left windoze in the rear view mirror.. Only one monitor, but I have nvidia on the motherboard. Looking forward to it. -- hendrik -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101026022430.gb4...@topoi.pooq.com
Re: Changing from stable to testing.....
I did the upgrade from lenny to squeeze without any problems - if you read the wiki, you are supposed to upgrade apt dpkg and aptitude first - then the kernel - then distupgrade. It worked - but - there is always some cruft that accumulates - so if you have time, you might want to bkup your old etc and home - then move to a new install - migrating configs one at a time. Some of my cruft dated back to sarge... On the other hand - with a nvidia card and dual head monitors - kde4 is amazing - I think we just left windoze in the rear view mirror.. Karl Schmidt EMail k...@xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 Subtle recursive jokes in signatures are funny. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc647aa.3010...@xtronics.com
Re: Changing from stable to testing.....
On 10/25/2010 09:24 PM, Hendrik Boom wrote: On Mon, Oct 25, 2010 at 09:10:09PM -0500, Karl Schmidt wrote: I did the upgrade from lenny to squeeze without any problems - if you read the wiki, you are supposed to upgrade apt dpkg and aptitude first - then the kernel - then distupgrade. And was your system up and usable during pretty well the entire install? Except during the reboot for the new kernel, of course. I'm talking of network services, such as mail forwarding, NFS service, etc. I've done that with two production servers going from sarge to lenny on a Sunday night --- of course you have to restart services - a couple services were down for a few minutes while the con-figs were tweaked. On servers, the right way is to set DNS ttl very low a week ahead of the move. Then set up a new system and move one service at a time. - Draw up a plan and a list ahead of time - save it for next time. Desk top moves get more complicated.. If so, I'll probably copy the entire system (so I have a fallback just in case) and then upgrade as above. It worked - but - there is always some cruft that accumulates - so if you have time, you might want to bkup your old etc and home - then move to a new install - migrating configs one at a time. Some of my cruft dated back to sarge... On the other hand - with a nvidia card and dual head monitors - kde4 is amazing - I think we just left windoze in the rear view mirror.. Only one monitor, but I have nvidia on the motherboard. Looking forward to it. -- hendrik -- !!! INCLUDE ALL TEXT IN TECHNICAL SUPPORT EMAIL REPLIES!!! Please reply in plain-text mode Karl Schmidt EMail k...@xtronics.com Transtronics, Inc. WEB http://xtronics.com 3209 West 9th Street Ph (785) 841-3089 Lawrence, KS 66049 FAX (785) 841-0434 The lawyer was about two bubbles off plumb. -- To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4cc649bb.3060...@xtronics.com