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
On Thu, Mar 15, 2007 at 02:39:16PM -0500, Spencer Butler wrote:
> I just did an apt-get dist-upgrade and the upgrade failed on openbsd-inetd.
> Upon looking at the standard output I noticed the lack of a space between
> inetd and invoke-rc.d.
Which is a symptom, not a cause. If there hadn't been
I just did an apt-get dist-upgrade and the upgrade failed on openbsd-inetd.
Upon looking at the standard output I noticed the lack of a space between
inetd and invoke-rc.d. Once I saw that, I ran the command by hand and reran
apt-get dist-upgrade and dpkg took care of configuring openbsd-inetd an
On Thu, 15 Mar 2007, Spencer Butler wrote:
This bug is nothing more than a typo.
Starting internet superserver: inetdinvoke-rc.d: initscript should read
Starting internet superserver: inetd invoke-rc.d: initscript
^---
Pardon? Where's th
This bug is nothing more than a typo.
Starting internet superserver: inetdinvoke-rc.d: initscript should read
Starting internet superserver: inetd invoke-rc.d: initscript
^---
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, Filipus Klutiero wrote:
Le mardi 6 mars 2007 23:00, Mike Young a écrit :
Package: openbsd-inetd
Version: 0.20050402-5
Followup-For: Bug #386469
I'm seeing this same error on an etch update/upgrade today.
my pid for inetd doesn't change during the attempt at install, which
Le mardi 6 mars 2007 23:00, Mike Young a écrit :
> Package: openbsd-inetd
> Version: 0.20050402-5
> Followup-For: Bug #386469
>
>
> I'm seeing this same error on an etch update/upgrade today.
> my pid for inetd doesn't change during the attempt at install, which
> suggests that the preinstall for o
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
I'm seeing this same error on an etch update/upgrade today.
my pid for inetd doesn't change during the attempt at install, which
suggests that the preinstall for openbsd-inetd doesn't make any attempt
to stop the preexisting
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
On Mar 05, Jirka Novosad <[EMAIL PROTECTED]> wrote:
> I believe the problem is the #!/bin/sh line of /etc/init.d/openbsd-inetd.
> It uses the -e switch and when start-stop-daemon exits with a non-zero
> status, the script exits too.
No shit, Sherlock.
--
ciao,
Marco
signature.asc
Description:
Package: openbsd-inetd
Version: 0.20050402-5
Followup-For: Bug #386469
I believe the problem is the #!/bin/sh line of /etc/init.d/openbsd-inetd.
It uses the -e switch and when start-stop-daemon exits with a non-zero
status, the script exits too.
-- System Information:
Debian Release: 4.0
APT pr
19 matches
Mail list logo
