Your message dated Mon, 13 Feb 2017 20:52:58 +
with message-id
and subject line Bug#855050: fixed in systemd 232-18
has caused the Debian Bug report #855050,
regarding systemd: systemctl regressions, assertion failure with "--user
enable" without HOME, and more
to be marked as done.
This mea
Your message dated Mon, 13 Feb 2017 20:52:57 +
with message-id
and subject line Bug#854814: fixed in systemd 232-18
has caused the Debian Bug report #854814,
regarding Fails to start systemd-resolved
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Mon, 13 Feb 2017 17:36:12 +0100
Source: systemd
Binary: systemd systemd-sysv systemd-container systemd-journal-remote
systemd-coredump libpam-systemd libnss-myhostname libnss-mymachines
libnss-resolve libnss-systemd l
systemd_232-18_amd64.changes uploaded successfully to localhost
along with the files:
systemd_232-18.dsc
systemd_232-18.debian.tar.xz
libnss-myhostname-dbgsym_232-18_amd64.deb
libnss-myhostname_232-18_amd64.deb
libnss-mymachines-dbgsym_232-18_amd64.deb
libnss-mymachines_232-18_amd64.deb
Processing control commands:
> tag -1 pending
Bug #855050 [systemd] systemd: systemctl regressions, assertion failure with
"--user enable" without HOME, and more
Added tag(s) pending.
> severity -1 important
Bug #855050 [systemd] systemd: systemctl regressions, assertion failure with
"--user ena
Control: tag -1 pending
Control: severity -1 important
Raphaël Hertzog [2017-02-13 16:39 +0100]:
> Severity: serious
That seems grossly inflated, adjusting.
> Any invocation of "systemctl --user enable/disable" will fail if
> XDG_RUNTIME_DIR is not set while it's strictly not required to do
> it
Package: systemd
Version: 232-15
Severity: serious
User: de...@kali.org
Usertags: origin-kali
I opened this upstream: https://github.com/systemd/systemd/issues/5260
and I would like to get this fixed in Debian stretch. This is a regression
compared to former versions.
Any invocation of "systemct
On 13/02/17 09:52, Felipe Sateler wrote:
> Hi Dererk,
>
> On 10 February 2017 at 14:06, Dererk wrote:
>> Dear pkg-systemd Maintainers,
>>
>> I've been trying to deliver a package that has a mix of enabled/disable
>> and started/not started service units.
>>
>> The situation I encounter seems to be
Hi Dererk,
On 10 February 2017 at 14:06, Dererk wrote:
> Dear pkg-systemd Maintainers,
>
> I've been trying to deliver a package that has a mix of enabled/disable
> and started/not started service units.
>
> The situation I encounter seems to be reflected at the manpage, when
> calling dh_systemd