Bug no longer evident, without updating jackd or webmin.
If no further comment or report, bug can be closed.
(Is a re-boot nessessary so that an sysv-rc update gets functional?)
actual version 2.87dsf-4
--
Bernhard Kleine
signature.asc
Description: Dies ist ein digital signierter Nachrichten
[Bernhard Kleine]
> package jackd left obsolete init.d script behind package timidity
> left obsolete init.d script behind
I checked, and these issues are already reported to BTS as #538963 and
#538967.
Happy hacking,
--
Petter Reinholdtsen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ..
[Bernhard Kleine]
> Hopefully the output may help!
It does, and as far as I know, the fix provided in 2.87dsf-4 solved
the upgrade problem, and you are left with the migration issues
reported in the debconf note.
Here is a summary of the problems with the init.d scripts and how to
solve it to mig
Am Sonntag, den 06.09.2009, 11:26 +0200 schrieb Petter Reinholdtsen:
> [Bernhard Kleine]
>
> DEBCONF_DEBUG=developer dpkg-reconfigure sysv-rc
>
> I suspect the problem is debconf related. It would also be nice to
> see the output from reconfiguring after adding 'set -x' to the top of
> /var/l
[Bernhard Kleine]
> Hallo, I am still left with an update failure:
Hm, strange. Must be some new issue. Can you rerun the reconfigure
like this to get some idea why this fail?
DEBCONF_DEBUG=developer dpkg-reconfigure sysv-rc
I suspect the problem is debconf related. It would also be nice to
Hallo, I am still left with an update failure:
the debconf window shows the following messages:
Tests have determined that problems in the boot system exist which
prevent migration to dependency based boot sequencing. It is recommended
to migrate for the following reasons:
* the order of boot a
On Sat, Sep 05, 2009 at 09:57:20PM +0200, Petter Reinholdtsen wrote:
> I am able to reproduce this now, by starting in squeeze, adding a
> dummy init.d script with no header using 'update-rc.d dummy defaults'
> and then upgrade to unstable using 'DEBCONF_DEBUG=developer aptitude
Hmm, I upgraded fr
[Mario 'BitKoenig' Holbe]
> Nope, `db_stop || true' doesn't help.
> As you can see in the previous log, there is still action after
> db_stop.
I am able to reproduce this now, by starting in squeeze, adding a
dummy init.d script with no header using 'update-rc.d dummy defaults'
and then upgrade to
On Sat, Sep 05, 2009 at 08:51:46PM +0200, Petter Reinholdtsen wrote:
> Thank you for testing. This is rather strange, I believe. The only
> failing thing I can imagine is db_stop, which I believed until now
> could not fail. Anyway, does it help to change db_stop to 'db_stop ||
> true' in the po
[Mario 'BitKoenig' Holbe]
> Logfile attached.
Thank you for testing. This is rather strange, I believe. The only
failing thing I can imagine is db_stop, which I believed until now
could not fail. Anyway, does it help to change db_stop to 'db_stop ||
true' in the postinst?
Happy hacking,
--
Pe
On Sat, Sep 05, 2009 at 08:19:09PM +0200, Petter Reinholdtsen wrote:
> There is nothing there exiting with an error code.
> Can you try to add 'set -x' at the start of
> /var/lib/dpkg/info/sysv-rc.postinst and let me know what is printed
> when you try to configure the sysv-rc package again?
Logfi
[Mario 'BitKoenig' Holbe]
> when sysv-rc's check if it is safe to convert to dependency based boot
> fails, package upgrade fails:
Strange.
> Preparing to replace sysv-rc 2.87dsf-2 (using .../sysv-rc_2.87dsf-3_all.deb)
> ...
> Unpacking replacement sysv-rc ...
> Processing triggers for man-db ..
Package: sysv-rc
Version: 2.87dsf-3
Severity: important
Hello,
when sysv-rc's check if it is safe to convert to dependency based boot
fails, package upgrade fails:
Preparing to replace sysv-rc 2.87dsf-2 (using .../sysv-rc_2.87dsf-3_all.deb) ...
Unpacking replacement sysv-rc ...
Processing trigge
13 matches
Mail list logo
