Hi Marco,
I've prepared an NMU for this issue with the following patch. I think the
'which invoke-rc.d' check is probably unnecessary altogether, because
invoke-rc.d has been part of essential since sarge, but it doesn't hurt
overly much; anyway, if invoke-rc.d is missing, I haven't bothered
So far, none of the people reporting this bug have provided information that
can be used to track it down. Most users are quoting the failure to set up
openbsd-inetd -- that's not news, what we need is output from the *unpack*
stage of the upgrade showing why the attempt to *stop* the previous
Very strange, but i cannot reproduce this bug again on my machine.
Upgrade from:
-3 to -4: no problems
-4 to -5: no problems
-3 to -5: no problems
-5 plain install: no problems.
Every time purged the package.
Downgrade from:
-5 to -4: no problems
All on the same machine i've reported some
On Sun, Mar 11, 2007 at 05:42:38PM +0100, Norman Messtorff wrote:
Attached you will find a logfile with my trials and the snipplet of my
dpkg.log from upgrade on 2007-03-05.
Ok, but this dpkg.log only shows the status of openbsd-inetd *after* the
upgrade has been started. Context at the
clone 386469 -1
tags -1 =patch
reassign -1 update-inetd
retitle -1 update-inetd: no reason to restart inetd on service removal
severity -1 important
thanks
Discussing with Marco on IRC, it seems he's reluctant to have inetd running
when no services are configured, but it's clear in any case that
5 matches
Mail list logo
