[Bug 1715719] [NEW] systemd v232+ journals aren't compatible with journalctrl from 229
Ken VanDine
ken.vandine at canonical.com
Thu Sep 7 18:25:51 UTC 2017
Public bug reported:
systemd v232+ journals aren't compatible with journalctrl from 229
This normally isn't a problem, but in trying to create a snap for gnome-
logs I've run into a situation where we need to build the snap for 16.04
which has libsystemd0=229. This snap works fine if the host is running
16.04 as well. But on an artful host, the snap fails to access the
journal. I've tested backporting v232 from zesty to xenial and building
my snap with libsystem0 232. This works fine on 16.04 and 17.10 hosts.
@xnox suggested v232+ journals are built with more features enabled.
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: New
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1715719
Title:
systemd v232+ journals aren't compatible with journalctrl from 229
Status in systemd package in Ubuntu:
New
Bug description:
systemd v232+ journals aren't compatible with journalctrl from 229
This normally isn't a problem, but in trying to create a snap for
gnome-logs I've run into a situation where we need to build the snap
for 16.04 which has libsystemd0=229. This snap works fine if the host
is running 16.04 as well. But on an artful host, the snap fails to
access the journal. I've tested backporting v232 from zesty to xenial
and building my snap with libsystem0 232. This works fine on 16.04
and 17.10 hosts.
@xnox suggested v232+ journals are built with more features enabled.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1715719/+subscriptions
More information about the foundations-bugs
mailing list