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 call
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
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
u
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 begin
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
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 ine
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
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 open
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 instal
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: i
Package: openbsd-inetd
Version: 0.20050402-4
Followup-For: Bug #386469
I just experience apparently the same problem as descibed by Kent West
(Mon, 19 Feb 2007 21:20:51 -0600). Manually stopping openbsd-inetd
before upgrading worked for me:
$ sudo apt-get upgrade
...
Setting up openbsd-inetd (0.
Package: openbsd-inetd
Version: 0.20050402-4
Followup-For: Bug #386469
[EMAIL PROTECTED]:/etc/init.d> sudo aptitude install openbsd-inetd
Reading package lists... Done
Building dependency tree... Done
Reading extended state information
Initializing package states... Done
Building tag database...
Package: openbsd-inetd
Version: 0.20050402-3
Followup-For: Bug #386469
I think I can shed some light on this, since I saw this problem while
upgrading a machine from sarge to etch. If netkit-inetd isn't purged,
its init script will start /usr/sbin/inetd. openbsd-inetd's init
script then can't s
On Friday 08 September 2006 08:39, Marco d'Itri wrote:
> On Sep 08, Bill Carini <[EMAIL PROTECTED]> wrote:
> > I can start and stop from the command line. After I stopped it, I did
> > apt-get dist-upgrade and the setting up and starting were then
> > successful.
>
> Again, check the log file.
The
On Sep 08, Bill Carini <[EMAIL PROTECTED]> wrote:
> I can start and stop from the command line. After I stopped it, I did
> apt-get dist-upgrade and the setting up and starting were then successful.
Again, check the log file.
--
ciao,
Marco
signature.asc
Description: Digital signature
On Thursday 07 September 2006 21:56, Marco d'Itri wrote:
> On Sep 07, Bill Carini <[EMAIL PROTECTED]> wrote:
> > While doing apt-get dist-upgrade the following occurs:
> >
> > Setting up openbsd-inetd (0.20050402-2) ...
> > Starting internet superserver:invoke-rc.d: initscript openbsd-inetd,
> > ac
On Sep 07, Bill Carini <[EMAIL PROTECTED]> wrote:
> While doing apt-get dist-upgrade the following occurs:
>
> Setting up openbsd-inetd (0.20050402-2) ...
> Starting internet superserver:invoke-rc.d: initscript openbsd-inetd, action
> "start" failed.
It would be useful to know why.
Is there anyt
Package: openbsd-inetd
Version: 0.20050402-2
Severity: important
While doing apt-get dist-upgrade the following occurs:
Setting up openbsd-inetd (0.20050402-2) ...
Starting internet superserver:invoke-rc.d: initscript openbsd-inetd, action
"start" failed.
dpkg: error processing openbsd-inetd (--
18 matches
Mail list logo
