>https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773924
Wow! Thanks, Oli.
That’s very informative and much appreciated. It looks like we could simply
rebuild the package without the dependency, if I am reading this correctly.
T.J.___
Dng mail
>I looked it up in packages.debian.org.
>systemd-login0 is in both wheezy and wheezy-backports, with different
>version numbers.
>It is deprecated in jessie and sid, and rc-buggy in experimental.
>Is there any way to track the history of a package and its adoption
>into different releases?
>On my wheezy pulseaudio wants:
>libsystemd-daemon0 (>= 31), libsystemd-login0 (>= 31)
>If i had some time i would change to jack...
>Possibly it would be a boost for the jack development if we make it
>standard in Devuan?
Well, before we overreact- if the package has been depreciated, we
Thank you, Hendrik.
That is what I assumed you would find. I’m not overreacting per se. I freely
admit, I’ve not looked at the code to see how well it functions independently.
I also do not know for certain that it is a recent addition. I do not recall
seeing it in previous Wheezy releases a
>I think it is not so much a problem of the kernel, which as you > point out
>can be compiled to suit and by its nature is >backwards compatible in most
>things other than size, but rather >other pieces, a cascade of "what next?"
>dependencies and the >horror of horrors proprietary bi
Hi, Clarke!
>It was a bit of a wake up call for me as it made me realize that for
>more recent hardware continued use of Wheezy to avoid systemd may not be
>as simple as it first seems.
You can get around that. Systemd is not a kernel requirement. You can easily
get around said problems b
>Then I have no idea about default installation (you can probably look at
>package dependencies to figure it out). But from Debian's current POV, it is
>probably considered an improvement to add systemd components and more
>recent versios of __ that use them, even if PID1 is still sysvinit. Af
> My concern is that Debian is backporting code to the Wheezy release that
> they shouldn’t be installing by default
I should say “might be” as I am not sure and have not looked at the code
personally. I am merely concerned.
From: t.j.duch...@gmail.com
Sent: Monday, January 5,
>IIRC, Wheezy is known to have systemd packages but they aren't (or shouldn't
>be?) installed by default, probably as an early preparation for full systemd in
>Jessie.
Yes, I know.
As I’ve said before I have no problem with systemd, except on mission critical
servers. My concern is tha
I just wanted to post this for consideration. I’m not looking to rehash old
posts, but Devuan is at the moment finding its legs. I feel that this is a
valid concern that may arise in Devuan’s future. I think it should be
discussed openly.
http://threatpost.com/debian-announces-end-of-secur
The reasons for a dynamic device manger were simple:
a) Actually makes sure that the device really exists, and is connected rather
than having a static /dev entry that is essentially worthless.
b) A dynamic manager provides a consistent way for naming device nodes, rather
than having administ
From: frank ernest
Sent: Tuesday, December 30, 2014 11:18 AM
To: dng@lists.dyne.org
https://www.mail-archive.com/dng%40lists.dyne.org/msg00051.html
>And later messages suggested to me that this was the case.
>Perhaps I misunderstood.
Maybe there is. I’m hardly a source of
12 matches
Mail list logo
