On 03/17/2018 09:12 AM, Patrick Matthäi wrote:
> Hi,
>
> Then the dependency still needs to get fixed in VMware Tools.
which won't help you as that systemd version is not in jessie and stretch.
(just fyi: bug reports to backports versions have to go on the backports
user list, not into the
Am 17.03.2018 um 18:37 schrieb Michael Grant:
> Package: systemd
> Version: 238-2
> Severity: normal
>
> I noticed the following in the log file:
> Mar 17 07:12:41 example systemd[1]:
> /lib/systemd/system/system-update-cleanup.service:35: Unknown lvalue
> 'SuccessAction' in section 'Service'
>
Processing commands for cont...@bugs.debian.org:
> forwarded 893282 https://github.com/systemd/systemd/issues/8477
Bug #893282 [systemd] systemd: SuccessAction=reboot in wrong stanza in
/lib/systemd/system/system-update-cleanup.service
Set Bug forwarded-to-address to
On Sat, Mar 17, 2018 at 03:30:06AM +0100, Michael Biebl wrote:
> On Thu, 11 Jan 2018 11:01:03 +0200 "Plamen K. Kosseff"
> wrote:
> > Package: systemd
> > Version: 236-2
> > Severity: normal
> >
> > Dear Maintainer,
> >
> >
> > This is new debian buster install on HP z600
On Sat, Mar 17, 2018 at 3:20 AM, Michael Biebl wrote:
> On Tue, 19 Dec 2017 19:50:49 +0200 =?utf-8?q?R=C3=A9mi_Denis-Courmont?=
>> systemd-networkd from version 236-1 systematically segfaults at start-up.
>
> Could you test with v238 please and report back with your results.
Your message dated Sat, 17 Mar 2018 14:59:30 +0100
with message-id <3ce1c79f-2816-d46b-9867-2bdc66d84...@debian.org>
and subject line Re: Bug#852461: systemd: Creating scopes with systemd-run
unreliable
has caused the Debian Bug report #852461,
regarding systemd: Creating scopes with systemd-run