broken hamm upgrade
Hello, I've been having a heck of a time upgrading a 1.3.1 bo (originally 1.2) system to hamm using autoup. Everything is installed up to libreadlineg2 in the autoup script, then libreadlineg2's post install script bombs out and leaves the system in an essentially unusable state (nearly everything dumps core) until the package is removed. The screen output from the autoup.sh: Unpacking replacement libreadlineg2 ... Setting up libreadlineg2 (2.1-7) ... dpkg: error processing libreadlineg2 (--install): subprocess post-installation script killed by signal (Segmentation fault) -- I've looked through the documentation and not found any reference to a problem like this. Any clues as to what I should be doing here? Thanks, -Don -- E-mail the word unsubscribe to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED] .
Re: broken hamm upgrade
Don Erickson [EMAIL PROTECTED] writes: I've been having a heck of a time upgrading a 1.3.1 bo (originally 1.2) system to hamm using autoup. Everything is installed up to libreadlineg2 in the autoup script, then libreadlineg2's post install script bombs out and leaves the system in an essentially unusable state (nearly everything dumps core) until the package is removed. The screen output from the autoup.sh: Unpacking replacement libreadlineg2 ... Setting up libreadlineg2 (2.1-7) ... dpkg: error processing libreadlineg2 (--install): subprocess post-installation script killed by signal (Segmentation fault) -- The only thing the libreadlineg2 postinst does is ldconfig. I suggest you run ldconfig and see what error it complains about. This is most likely a dangling symlink. Removing the dangling symlink often cures the problem. If the ldconfig error is eliminated, then you can run atuoup.sh again. -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- E-mail the word unsubscribe to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED] .
Re: broken hamm upgrade
I got A LOT of problems when trying to upgrade, my lack of response the past few days is because I was fixing my box. :) Well, this is the 'best' way to upgrade to glibc2, unfortunately, it is a very undesirable solution. Install 1.3.R6 fresh, THEN as dselect comes up, cancel, and immediately run the autoup.sh. It would be better if you predownloaded the first hamm packages first, but the script will prompt you. Ok.. run the script, then install everything. This will give you a VERY clean install of Debian 2.0 (unstable). I moronically did a few critical errors while doing this. I installed NIS or something that I never heard of which broke my shadow passwords. And.. Accelerated X4.1 would NOT run with glibc2! Very very frustrating. I reinstalled back to Debian 1.3R6... and I feel great about it. To be honest, I really do not know of the big advantages of glibc2, and until support is stabilize 100%, I do not think it is worthwhile unless you have some spare time and it is not a production box. (glibc2 is supposed to be faster... linux already runs quick enough?!?) On Sun, 8 Mar 1998, Don Erickson wrote: Hello, I've been having a heck of a time upgrading a 1.3.1 bo (originally 1.2) system to hamm using autoup. Everything is installed up to libreadlineg2 in the autoup script, then libreadlineg2's post install script bombs out and leaves the system in an essentially unusable state (nearly everything dumps core) until the package is removed. The screen output from the autoup.sh: Unpacking replacement libreadlineg2 ... Setting up libreadlineg2 (2.1-7) ... dpkg: error processing libreadlineg2 (--install): subprocess post-installation script killed by signal (Segmentation fault) -- I've looked through the documentation and not found any reference to a problem like this. Any clues as to what I should be doing here? Thanks, -Don -- E-mail the word unsubscribe to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED] .
Re: broken hamm upgrade
I got A LOT of problems when trying to upgrade, my lack of response the past few days is because I was fixing my box. :) Well, this is the 'best' way to upgrade to glibc2, unfortunately, it is a very undesirable solution. Install 1.3.R6 fresh, THEN as dselect comes up, cancel, and immediately run the autoup.sh. It would be better if you predownloaded the first hamm packages first, but the script will prompt you. Ok.. run the script, then install everything. This will give you a VERY clean install of Debian 2.0 (unstable). Actually, the best way to install 2.0, AFAICT and IMHO, is to use the brand-new 2.0 install disks. You can find them in the usual archives in the disks-i386 distribution. -- E-mail the word unsubscribe to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED] .
Re: broken hamm upgrade
Ben Pfaff [EMAIL PROTECTED] write: Actually, the best way to install 2.0, AFAICT and IMHO, is to use the brand-new 2.0 install disks. You can find them in the usual archives in the disks-i386 distribution. That is unquestionably the best way, if the disks work on your machine, however they aren't yet stable. I was able to make a satisfactory (but not bug-free) installation using the 3.5 disks from the 1988-02-20 set with my Micron Pentium 166 machine, but the 5.25 disks failed on my old 486-33 machine. Quite a few people have reported failures to the testing list with various configurations of the test machine. The last time I checked, debian/hamm/hamm/disks-i386/1998-02-20 was the current set, but I haven't checked Incoming. -- _ |_) _ |_ Robert D. Hilliard[EMAIL PROTECTED] |_) (_) |_) Palm City, FL USAPGP Key ID: A8E40EB9 -- E-mail the word unsubscribe to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED] .
Re: broken hamm upgrade
Ben Pfaff [EMAIL PROTECTED] said: Actually, the best way to install 2.0, AFAICT and IMHO, is to use the brand-new 2.0 install disks. You can find them in the usual archives in the disks-i386 distribution. Would that be: ftp://ftp.debian.org/pub/debian/hamm/hamm/disks-i386/current/ And the needed disks for most folks usually be: base14-1.bin 1440 KbSat Feb 21 base14-2.bin 1440 KbSat Feb 21 base14-3.bin 1440 KbSat Feb 21 base14-4.bin 1440 KbSat Feb 21 base14-5.bin 1440 KbSat Feb 21 base14-6.bin drv1440.bin1440 KbSat Feb 21 resc1440.bin If they have a running linux system and know how to dd the images onto floppys. not sure what this one is for: root.bin So your saying if your goal is to have a hamm/2.0 system and you are installing a fresh system, not an upgrade is to start straight out with 2.0. There is no advantage to starting with your 1.3.1 CDROMs. (Well at least I got the book that came with them :-)). Henry Hollenberg [EMAIL PROTECTED] -- E-mail the word unsubscribe to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED] .
Re: broken hamm upgrade
In article [EMAIL PROTECTED] you write: The only thing the libreadlineg2 postinst does is ldconfig. I suggest you run ldconfig and see what error it complains about. This is most likely a dangling symlink. Removing the dangling symlink often cures the problem. If the ldconfig error is eliminated, then you can run atuoup.sh again. Thanks, you were correct, a symlink I had dropped in to patch the box from an earlier upgrade attempt was the culprit. libreadlineg2 is installed, but I'm having a similar adventure upgrading bash, as the install script and any attempt to call bash gives a [ba]sh: error in loading shared libraries : undefined symbol: history_get_string_value_hook and then exits. *sigh* Perhaps I really should do a fresh 2.0 install, as this box has had a number of fairly ugly things done to it over the past year and a half or so. I figured it would catch up to me eventually. Thanks to everyone who responded. Regards, -Don -- .sig lite -- E-mail the word unsubscribe to [EMAIL PROTECTED] TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to [EMAIL PROTECTED] .
