On 2016-02-26 14:56, Mark Brown wrote:
> On Fri, Feb 26, 2016 at 02:17:46PM +0100, Jeroen Massar wrote:
>> On 2016-02-26 13:55, Mark Brown wrote:
>>> On Wed, Feb 17, 2016 at 11:03:41PM +0100, Jeroen Massar wrote:
>
No VPN-alike tool does such a thing. OpenVPN for instance also nicely
On Fri, Feb 26, 2016 at 02:17:46PM +0100, Jeroen Massar wrote:
> On 2016-02-26 13:55, Mark Brown wrote:
> > On Wed, Feb 17, 2016 at 11:03:41PM +0100, Jeroen Massar wrote:
> >> No VPN-alike tool does such a thing. OpenVPN for instance also nicely
> >> aborts as it can't do anything with that
On 2016-02-26 13:55, Mark Brown wrote:
> On Wed, Feb 17, 2016 at 11:03:41PM +0100, Jeroen Massar wrote:
>
>> No VPN-alike tool does such a thing. OpenVPN for instance also nicely
>> aborts as it can't do anything with that situation. SSH tunnels also
>> nicely state "no network".
>
> This is
On Wed, Feb 17, 2016 at 11:03:41PM +0100, Jeroen Massar wrote:
> No VPN-alike tool does such a thing. OpenVPN for instance also nicely
> aborts as it can't do anything with that situation. SSH tunnels also
> nicely state "no network".
This is true for things intended to be used interactively
On 2016-02-17 19:26, Mark Brown wrote:
> On Wed, Feb 17, 2016 at 05:46:53PM +0100, Jeroen Massar wrote:
>> On 2016-02-17 17:00, Mark Brown wrote:
>
>>> Right, but I do think AICCU can deal better with this situation. Not
>>> dealing with it makes system integration much harder as there are a
>>>
On Wed, Feb 17, 2016 at 05:46:53PM +0100, Jeroen Massar wrote:
> On 2016-02-17 17:00, Mark Brown wrote:
> > Right, but I do think AICCU can deal better with this situation. Not
> > dealing with it makes system integration much harder as there are a
> > range of options that users have for
On 2016-02-17 17:00, Mark Brown wrote:
> On Wed, Feb 17, 2016 at 04:03:22PM +0100, Jeroen Massar wrote:
>> On 2016-02-17 13:47, Mark Brown wrote:
>
>>> Let me try to provide that... We now no longer have the problems in the
>>> original report with the boot hanging but we still don't have AICCU
On Wed, Feb 17, 2016 at 04:03:22PM +0100, Jeroen Massar wrote:
> On 2016-02-17 13:47, Mark Brown wrote:
> > Let me try to provide that... We now no longer have the problems in the
> > original report with the boot hanging but we still don't have AICCU
> > coming up reliably at boot.
> You
On 2016-02-17 13:47, Mark Brown wrote:
> Hi,
>
> There's a bug open in Debian about AICCU not starting when used with
> systemd (though it's most likely not that specifically). One of the
> last things in the bug log is:
>
> | Actually, a concise problem statement would be a good thing to have,
Hi,
There's a bug open in Debian about AICCU not starting when used with
systemd (though it's most likely not that specifically). One of the
last things in the bug log is:
| Actually, a concise problem statement would be a good thing to have, as
| it seems completely lost in the bug report.
in Debian's testing distribution has changed.
Previous version: 20070115-15.2
Current version: (not in testing)
Hint: http://release.debian.org/britney/hints/auto-removals
Bug #754121: aiccu fails to start with systemd
The script that generates this mail tries to extract removal
reassign: -1 aiccu
Am 06.05.2015 um 04:43 schrieb Daniel Albers:
This is a critical bug of either aiccu or systemd as explained by
Pascal.
Assigning also to systemd as the aiccu maintainer considers this a
systemd bug, although I think message #26
On 2015-05-06 12:29, Michael Biebl wrote:
reassign: -1 aiccu
Am 06.05.2015 um 04:43 schrieb Daniel Albers:
This is a critical bug of either aiccu or systemd as explained by
Pascal.
Assigning also to systemd as the aiccu maintainer considers this a
systemd bug, although I think message #26
Hi Jeroen,
Am 06.05.2015 um 13:06 schrieb Jeroen Massar:
On 2015-05-06 12:29, Michael Biebl wrote:
reassign: -1 aiccu
Am 06.05.2015 um 04:43 schrieb Daniel Albers:
This is a critical bug of either aiccu or systemd as explained by
Pascal.
Assigning also to systemd as the aiccu maintainer
On 2015-05-06 13:26, Michael Biebl wrote:
Hi Jeroen,
Am 06.05.2015 um 13:06 schrieb Jeroen Massar:
On 2015-05-06 12:29, Michael Biebl wrote:
reassign: -1 aiccu
Am 06.05.2015 um 04:43 schrieb Daniel Albers:
This is a critical bug of either aiccu or systemd as explained by
Pascal.
On 2015-05-06 13:47, Michael Biebl wrote:
Am 06.05.2015 um 13:44 schrieb Jeroen Massar:
On 2015-05-06 13:26, Michael Biebl wrote:
See above, if you feel like taking over maintainership of the package,
this would be appreciated.
Attempted that before. Failed.
Please note that the fun part
Am 06.05.2015 um 13:44 schrieb Jeroen Massar:
On 2015-05-06 13:26, Michael Biebl wrote:
See above, if you feel like taking over maintainership of the package,
this would be appreciated.
Attempted that before. Failed.
Please note that the fun part of this all is that we originally
This is a critical bug of either aiccu or systemd as explained by
Pascal.
Assigning also to systemd as the aiccu maintainer considers this a
systemd bug, although I think message #26
546673f0.1040...@localhost.localdomain.org already points to the
proper fix for aiccu.
Cheers, Daniel
--
To
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
23 matches
Mail list logo
