Re: nasty slink - potato upgrade problem
At 10:57 +1100 2000-03-12, Hamish Moffatt wrote: Also, libc6 tries to restart some NSS-using services, but never seems to succeed in restarting sshd. I end up with it refusing connections, although sshd still appears to be running (the original process and not a new one). I guess that means that ssh has a buggy init script then, because I merely call it with an argument of restart. I've also heard that some versions of ssh have an init script that kills all sshd processes on the system, so maybe I should not do it at all. -- Joel Klecker (aka Espy)Debian GNU/Linux Developer URL:mailto:[EMAIL PROTECTED] URL:mailto:[EMAIL PROTECTED] URL:http://web.espy.org/ URL:http://www.debian.org/
Re: nasty slink - potato upgrade problem
On Sat, Mar 11, 2000 at 08:10:07PM -0500, Daniel Burrows wrote: On Sat, Mar 11, 2000 at 08:32:07PM -0400, Nicolás Lichtmaier was heard to say: Trouble ahead? Please run apt-get install apt before doing the dist-upgrade. Old apt don't manage well the perl transition. This will be documented in the Release Notes. Why don't we make the new perls conflict the old apt? I know I suggested something similar earlier, but would this really work? You'd have to restart the apt frontend in order to get the needed effect, even if it correctly upgraded itself. Not sure, but wouldn't it be possible somehow to fork exec (and exit the parent program - not to forget)?
Re: nasty slink - potato upgrade problem
Trouble ahead? Please run apt-get install apt before doing the dist-upgrade. Old apt don't manage well the perl transition. This will be documented in the Release Notes. Why don't we make the new perls conflict the old apt?
Re: nasty slink - potato upgrade problem
And/or make the new Perl pre-depend on the new apt, so the apt update will happen before anything else? On Sat, 11 Mar 2000, Nicolás Lichtmaier wrote: Trouble ahead? Please run apt-get install apt before doing the dist-upgrade. Old apt don't manage well the perl transition. This will be documented in the Release Notes. Why don't we make the new perls conflict the old apt? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Do not meddle in the affairs of dragons, for you are crunchy and taste good with ketchup.
Re: nasty slink - potato upgrade problem
On Sat, Mar 11, 2000 at 08:32:07PM -0400, Nicolás Lichtmaier was heard to say: Trouble ahead? Please run apt-get install apt before doing the dist-upgrade. Old apt don't manage well the perl transition. This will be documented in the Release Notes. Why don't we make the new perls conflict the old apt? I know I suggested something similar earlier, but would this really work? You'd have to restart the apt frontend in order to get the needed effect, even if it correctly upgraded itself. Or am I missing something? (eg..would it just hold back the perl upgrade and require two runs instead of doing something really nasty like it does now? :) ) Daniel
Re: nasty slink - potato upgrade problem
On Sat, 11 Mar 2000, [iso-8859-1] Nicolás Lichtmaier wrote: Trouble ahead? Please run apt-get install apt before doing the dist-upgrade. Old apt don't manage well the perl transition. This will be documented in the Release Notes. Why don't we make the new perls conflict the old apt? Augh, no don't do that! Upgrading APT will have to be in the release notes, you *HAVE* to run 'apt-get install apt' For alot of reasons, more than just perl, and you have to be running the new APT before you start going and installing other things for it to be of any value (ie depends are pointless) Jason
Re: nasty slink - potato upgrade problem
Trouble ahead? Please run apt-get install apt before doing the dist-upgrade. Old apt don't manage well the perl transition. This will be documented in the Release Notes. Why don't we make the new perls conflict the old apt? Augh, no don't do that! Upgrading APT will have to be in the release notes, you *HAVE* to run 'apt-get install apt' For alot of reasons, more than just perl, and you have to be running the new APT before you start going and installing other things for it to be of any value (ie depends are pointless) Besides, it wouldn't work.. as somebody pointed out... =/
Re: nasty slink - potato upgrade problem
Le Sat, Mar 11, 2000 at 07:06:24PM +1100, Hamish Moffatt écrivait: Trouble ahead? Please run apt-get install apt before doing the dist-upgrade. Old apt don't manage well the perl transition. This will be documented in the Release Notes. Cheers, -- Raphaël Hertzog -=- http://tux.u-strasbg.fr/~raphael/ pub CDs Debian : http://tux.u-strasbg.fr/~raphael/debian/#cd Formations Linux et logiciels libres : http://www.logidee.com /pub
Re: nasty slink - potato upgrade problem
On Sat, Mar 11, 2000 at 04:37:11PM +0100, Raphael Hertzog was heard to say: Le Sat, Mar 11, 2000 at 07:06:24PM +1100, Hamish Moffatt écrivait: Trouble ahead? Please run apt-get install apt before doing the dist-upgrade. Old apt don't manage well the perl transition. This will be documented in the Release Notes. This is just a thought: would it be a good idea for apt to always upgrade itself before attempting to upgrade anything else? Or would this be better done (if at all) in the frontends? Daniel -- There are many of us in this old world of ours who hold that things break about even for all of us. I have observed, for example, that we all get about the same amount of ice. The rich get it in the summer and the poor get it in the winter. -- Bat Masterson
Re: nasty slink - potato upgrade problem
On Sat, Mar 11, 2000 at 04:37:11PM +0100, Raphael Hertzog wrote: Le Sat, Mar 11, 2000 at 07:06:24PM +1100, Hamish Moffatt écrivait: Trouble ahead? Please run apt-get install apt before doing the dist-upgrade. Old apt don't manage well the perl transition. This will be documented in the Release Notes. Yuck. Can we add a conflicts somewhere to automate this? Also, libc6 tries to restart some NSS-using services, but never seems to succeed in restarting sshd. I end up with it refusing connections, although sshd still appears to be running (the original process and not a new one). That could be very very nasty! If you logout then you can't login again... fortunately I have telnet from selected hosts and also dialup, but for others it could be bad. Hamish -- Hamish Moffatt VK3SB. CCs of replies on mailing lists are welcome.
