[arch-dev-public] systemd 209 in [testing]
Hi all, I'm working on packaging the systemd 209 release, and I expect to have pkgrel=1 into [testing] in a few hours, barring any unforseen problems. It's a huge release (nearly 2000 commits since 208), and I don't anticipate that this will make it into [core]. *************** Because of the number of substantial internal changes, the post_upgrade will NOT reexec systemd. I strongly advise you to, instead, reboot after upgrading. If you *do* reexec systemd, you'll see all of the applets (machined, logind, journald, etc) killed once when they don't respond to an expected watchdog ping. There may be other breakages of varying verbosity. *************** The full list of changes is here: http://cgit.freedesktop.org/systemd/systemd/tree/NEWS Packaging changes of varying importance: - The network interface naming mechanism has been changed. The post_upgrade() has a fairly naive heuristic to try and preserve the existing behavior. - systemd's in-house seccomp filtering has been replaced by linkage to libseccomp (now that the API doesn't suck). I'd really like to keep support for this in our package, so it means moving libseccomp from [extra] to [core]. If it means I need to adopt libseccomp, I'm willing to do this. - libsystemd-{login,journal,daemon,etc}.so are deprecated, and the symbols have been merged into a singular libsystemd.so. You'll still see the legacy library names, but they're now just a bunch of IFUNC symbols. Please raise up any build problems and try to nudge respective upstreams to move to the new library name. - No, I will not ever be building v209 with --enable-kdbus. Happy testing, Dave
Am 20.02.2014 17:33, schrieb Dave Reisner:
- libsystemd-{login,journal,daemon,etc}.so are deprecated, and the symbols have been merged into a singular libsystemd.so. You'll still see the legacy library names, but they're now just a bunch of IFUNC symbols. Please raise up any build problems and try to nudge respective upstreams to move to the new library name.
Do you expect any build problems? And why do projects explicitly need to move? Can't we simply do a rebuild (if needed), disable the compat libraries but keep providing the compat .pc files for a while?
On Thu, Feb 20, 2014 at 05:52:14PM +0100, Thomas Bächler wrote:
Am 20.02.2014 17:33, schrieb Dave Reisner:
- libsystemd-{login,journal,daemon,etc}.so are deprecated, and the symbols have been merged into a singular libsystemd.so. You'll still see the legacy library names, but they're now just a bunch of IFUNC symbols. Please raise up any build problems and try to nudge respective upstreams to move to the new library name.
Do you expect any build problems? And why do projects explicitly need to move?
No, I don't. Projects need to move because the compat libs won't be around forever. We're probably talking a timeline of O(years) before they go away, though.
Can't we simply do a rebuild (if needed), disable the compat libraries but keep providing the compat .pc files for a while?
We would need to hack up the .pc files to use -lsystemd instead of whatever they provide, and then rebuild. What do we stand to gain from this instead of passing off the work to upstream?
Am 20.02.2014 18:13, schrieb Dave Reisner:
Can't we simply do a rebuild (if needed), disable the compat libraries but keep providing the compat .pc files for a while?
We would need to hack up the .pc files to use -lsystemd instead of whatever they provide, and then rebuild.
They do that. $ grep ^Libs ./src/compat-libs/*.pc.in ./src/compat-libs/libsystemd-daemon.pc.in:Libs: -L${libdir} -lsystemd ./src/compat-libs/libsystemd-id128.pc.in:Libs: -L${libdir} -lsystemd ./src/compat-libs/libsystemd-journal.pc.in:Libs: -L${libdir} -lsystemd ./src/compat-libs/libsystemd-login.pc.in:Libs: -L${libdir} -lsystemd
What do we stand to gain from this instead of passing off the work to upstream?
Just saying, that short-term, we could get rid of the compat libraries this way.
Am 20.02.2014 17:33, schrieb Dave Reisner:
Hi all,
I'm working on packaging the systemd 209 release, and I expect to have pkgrel=1 into [testing] in a few hours, barring any unforseen problems. It's a huge release (nearly 2000 commits since 208), and I don't anticipate that this will make it into [core].
This version works fine on my desktop, but fails on my laptop. The initramfs works fine. While booting up the system, systemd hangs and this appears in the journal: systemd[1]: Assertion '(x->type == SOURCE_MONOTONIC && y->type == SOURCE_MONOTONIC) || (x->type == SOURCE_REALTIME && y->type == SOURCE_REALTIME)' failed at src/libsystemd/sd-event/sd-event.c:264, function latest_time_prioq_compare(). Aborting. systemd[1]: Caught <ABRT>, dumped core as pid 317.
participants (2)
-
Dave Reisner
-
Thomas Bächler