Severity: important
Lowering severity to important. Causing a package for removal because
somebody decided on a new init system that is not backwards compatible
is not a critical thing.
Also, you can always start AICCU simply by typing 'aiccu start' which is
what the init script does.
I'll
On 11/14/2014 09:44 AM, Jeroen Massar wrote:
Severity: important
Lowering severity to important. Causing a package for removal because
somebody decided on a new init system that is not backwards compatible
is not a critical thing.
,--[ https://www.debian.org/Bugs/Developer#severities ]--
On 2014-11-14 22:28, Pascal Volk wrote:
On 11/14/2014 09:44 AM, Jeroen Massar wrote:
[..]
As mentioned in my message from yesterday, the system is unable to
finish the boot process. The message `A start job is running for LSB: …'
can't be interrupted.
You are using a 'testing' branch of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Version: 20070115-15.2
Severity: critical
Dear aiccu package maintainers,
out of curiosity I've enabled aiccu again (`update-rc.d aiccu defaults`).
Since that time systemd can't finish booting! Systemd shows the following
message - forever:
[ *
Package: aiccu
Version: 20070115-15.1
Severity: normal
Tags: ipv6
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear aiccu package maintainers,
since switching from sysvinit-core to systemd-sysv aiccu is no longer
started on system boot. journalctl shows some entries about aiccu (see
attached
5 matches
Mail list logo