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
Sorry for replying so late. I'm affraid I can't help much, but if
there's anything else you need, please let me know.
On 3/10/07, Tomas Pospisek [EMAIL PROTECTED] wrote:
From which previous openbsd-inetd versions were you upgrading? What were
the packages that were upgraded along openbsd-inetd?
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
Just had the same problem, this time on a Debian testing system,
instead of unstable as I had before.
As someone mentioned this, I purged netkit-inetd (still had its conf
files, etc.) to see if it helped, but it didn't.
Again, simply stopping openbsd-inetd made it possible to upgrade. This
is
On Sat, 10 Mar 2007, Ludo wrote:
Just had the same problem, this time on a Debian testing system,
instead of unstable as I had before.
As someone mentioned this, I purged netkit-inetd (still had its conf
files, etc.) to see if it helped, but it didn't.
Again, simply stopping openbsd-inetd made
I've just tried this on a Debian Etch system and have not had any
problem, even with xinetd installed.
For reference I performed the following actions:
apt-get install xinetd
apt-get install openbsd-inetd (upgrade -3 to -5)
apt-get install inetutils-inetd (replacing openbsd-inetd)
apt-get
Package: openbsd-inetd
Version: 0.20050402-5
Followup-For: Bug #386469
This bug is not fixed, I just got it on two different machines during
an upgrade:
Setting up openbsd-inetd (0.20050402-5) ...
Installing new version of config file /etc/init.d/openbsd-inetd ...
Starting internet superserver:
10 matches
Mail list logo
