On Fri, 16 Dec 2016 00:40:10 +0100 Michael Biebl wrote:
This was fixed upstream by
https://github.com/systemd/systemd/commit/ad2706db7cceba69203f3ac2b6ef65d7490c5f29
Attached is a backport of that patch for v215
Confirmed. That fix works here too.
The 'deb http://apt.osso.nl/debian jessie sy
Control: forwarded -1 https://github.com/systemd/systemd/issues/4810
This was fixed upstream by
https://github.com/systemd/systemd/commit/ad2706db7cceba69203f3ac2b6ef65d7490c5f29
Attached is a backport of that patch for v215
It seems to fix the issue seen on jessie.
--
Why is it that all of the
So shortly after writing that, the jessie systemd got bumped to
215-17+deb8u5.
I added my proposed patches from comment #52 and recompiled. If anyone
wants to try them, they're here as 215-17+deb8u5osso1:
deb http://apt.osso.nl/debian jessie systemd
deb-src http://apt.osso.nl/debian jessi
I could unfortunately reproduce the "Assertion 'sd_id128_randomize(&id)
>= 0'" issue on my Debian/Jessie with systemd 215-17+deb8u4.
I added the attached two patches and then things started working.
Cheers,
Walter Doekes
OSSO B.V.
>From 874d3404cbf2363604106c8f86683db4082691ea Mon Sep 17 00:00
Michael Biebl [2016-07-18 18:34 +0200]:
> Thanks, I'm able to reproduce the problem now on a jessie system with
> lxc v2 from backports.
> Interestingly, this happens for both a jessie *and* a stretch container.
> So it looks like either the combination "v215 host + v230 container" is
> interfering
Am 14.07.2016 um 19:31 schrieb 0x2a:
> you will see this in the log:
>
> Jul 14 17:11:40 systemd-test systemd[1]: Starting Halt...
> Jul 14 17:11:40 systemd-test systemd[1]: Assertion
> 'sd_id128_randomize(&id) >= 0' failed at ../src/core/dbus.c:688,
> function bus_on_connection(). Aborting.
> Ju
On Tue, 22 Mar 2016 14:54:22 +0100 Stefan Schlesinger wrote:
> Package: systemd
> Version: 215-17+deb8u3
> Tags: patch fixed-upstream
> User: pkg-systemd-maintainers@lists.alioth.debian.org
> Usertags: jessie-backport
>
> We are currently testing LXC 2.0 beta with unprivileged containers on Ubunt
On Thu, 07 Apr 2016 16:45:14 +0200 0...@correcthorsebatterystaple.xyz wrote:
> Hi,
>
> backporting the upstream fix [0] from systemd 219 doesn't seem to
> resolve the issue,
Does that mean, systemd upstream (current version v230) is still affected?
If not, was this fixed by a followup commit u
Hi,
backporting the upstream fix [0] from systemd 219 doesn't seem to
resolve the issue, but Stéphane Grabers patches [1] do so.
All patches have been tested with current LXC/LXD/lxcfs 2.0.0 RCs with
debian jessie as host/guest system.
[0]
https://github.com/systemd/systemd/commit/874d3404
Package: systemd
Version: 215-17+deb8u3
Tags: patch fixed-upstream
User: pkg-systemd-maintainers@lists.alioth.debian.org
Usertags: jessie-backport
We are currently testing LXC 2.0 beta with unprivileged containers on Ubuntu
16.04/testing and hit a already fixed systemd bug when testing with
Debian
10 matches
Mail list logo