** Description changed: - systemd v232+ journals aren't compatible with journalctrl from 229 + In my attempt to snap gnome-logs, I've run into an issue where gnome- + logs fails to get the journal when run on an artful host. The snap is + built in a xenial chroot against xenial + gnome-3-24 backports PPA. The + same snap does work when run on a 16.04 host. - 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. + artful has libsystemd0 234 and xenial has libsystemd0 229. I took a + stab at building libsystemd0 232 on xenial then build the snap with + libsystemd0 232. The resulting snap works fine on 16.04 and 17.10 + hosts. + + To summarize, we need a libsystemd0 built for xenial bundled in the + gnome-logs snap that is compatible with the running systemd on the host. + The basic rebuild of 232 for xenial is compatible with systemd from + xenial through artful. But we want to be sure backporting that in a + supported PPA is not a bad idea. Ideally we would just cherry pick + whatever 229 is lacking in our PPA. @xnox suggested v232+ journals are built with more features enabled.
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1715719 Title: systemd v232+ journals aren't compatible with journalctrl from 229 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1715719/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
