Bug#927698: udev dependencies broken on stretch

2019-04-23 Thread Marko von Oppen



Am 23.04.19 um 14:48 schrieb Michael Biebl:

Am 23.04.19 um 21:11 schrieb Marko von Oppen:

On Sun, 21 Apr 2019 20:23:26 +0200 Michael Biebl  wrote:


This is by design. The init script requires a start-stop-daemon with
support for --notify-await.
This is only necessary for sysvinit users. If you don't want to use
systemd then backports is not available to you.
You can ask the dpkg maintainer for a backport of dpkg though.

Hi Michael,

there seems to be a misunderstanding at your side.

Not really, it seems you are misunderstanding the issue. The udev
package is not for sysvinit only.

I did not write that udev is for sysvinit only. And of course I know 
that because I've used udev more than 10 years before it became part of 
systemd (unfortunately).




Bug#927698: udev dependencies broken on stretch

2019-04-23 Thread Michael Biebl
Am 23.04.19 um 21:11 schrieb Marko von Oppen:
> On Sun, 21 Apr 2019 20:23:26 +0200 Michael Biebl  wrote:
> 
>> This is by design. The init script requires a start-stop-daemon with
>> support for --notify-await.
>> This is only necessary for sysvinit users. If you don't want to use
>> systemd then backports is not available to you.
>> You can ask the dpkg maintainer for a backport of dpkg though.
> 
> Hi Michael,
> 
> there seems to be a misunderstanding at your side.

Not really, it seems you are misunderstanding the issue. The udev
package is not for sysvinit only.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature


Bug#927698: udev dependencies broken on stretch

2019-04-23 Thread Marko von Oppen

On Sun, 21 Apr 2019 20:23:26 +0200 Michael Biebl  wrote:

> This is by design. The init script requires a start-stop-daemon with
> support for --notify-await.
> This is only necessary for sysvinit users. If you don't want to use
> systemd then backports is not available to you.
> You can ask the dpkg maintainer for a backport of dpkg though.

Hi Michael,

there seems to be a misunderstanding at your side.

You write that 'this is only necessary only for sysvinit users'. But 
exactly sysvinit users cannot install that package because the package 
depends from 'systemd-sysv' what in turn is a 'systemd' package. 
'systemd-sysv' cannot be installed by sysvinit users.


So finally if the package is only for sysvinit users but sysvinit users 
cannot install it, the best for all sides would be to delete the package.


Marko