python-systemd 234-1 MIGRATED to testing

FYI: The status of the python-systemd source package in Debian's testing distribution has changed. Previous version: 233-1 Current version: 234-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

Bug#869531: casync autopkgtest is broken in 1+65-2

Source: casync Version: 1+65-2 Severity: important As seen at , the casync autopkgtest is broken in 1+65-2: adt-run [04:02:12]: test upstream: [--- [...] + mesontest --num-processes 1 Only ninja backend is supported to

Bug#869422: closed by Michael Biebl <bi...@debian.org> (Re: Bug#869422: systemd-logind lacks an init script)

That might answer that question about those instruments pointing away from Earth. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#869422: closed by Michael Biebl <bi...@debian.org> (Re: Bug#869422: systemd-logind lacks an init script)

Am 23.07.2017 um 19:02 schrieb sm-bugs...@gmx-topmail.de: > Don't know if that's reliable enough but a naive init script approach > could be: > > stop: killall systemd-logind > start: loginctl list-sessions As said, we are not going to add a SysV init script. -- Why is it that all of the

Bug#869144: systemd: Setting PATH with environment.d does not work

> Not sure. Maybe raise this question upstream. https://github.com/systemd/systemd/issues/6414 ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org

Bug#869422: closed by Michael Biebl <bi...@debian.org> (Re: Bug#869422: systemd-logind lacks an init script)

Don't know if that's reliable enough but a naive init script approach could be: stop: killall systemd-logind start: loginctl list-sessions ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org

Bug#869422: closed by Michael Biebl <bi...@debian.org> (Re: Bug#869422: systemd-logind lacks an init script)

Am 23.07.2017 um 17:46 schrieb sm-bugs...@gmx-topmail.de: > Well, saying systemd-logind is started by dbus but after that no one > cares about it doesn't sound like a resonable solution. If you have > systemd you can say "service systemd-logind restart", but if you have > SysV init you can't?

Bug#869422: closed by Michael Biebl <bi...@debian.org> (Re: Bug#869422: systemd-logind lacks an init script)

Well, saying systemd-logind is started by dbus but after that no one cares about it doesn't sound like a resonable solution. If you have systemd you can say "service systemd-logind restart", but if you have SysV init you can't? Bizarre. ___

Bug#869422: marked as done (systemd-logind lacks an init script)

Your message dated Sun, 23 Jul 2017 15:57:32 +0200 with message-id <65ed8af4-6bc6-32e5-007b-fb87a061b...@debian.org> and subject line Re: Bug#869422: systemd-logind lacks an init script has caused the Debian Bug report #869422, regarding systemd-logind lacks an init script to be marked as done.