Your message dated Thu, 14 Nov 2019 21:00:23 +0000
with message-id <20191114210022.gb3...@hindley.org.uk>
and subject line Re: elogind: elogind 239 in bullseye FTBFS with gcc-9
has caused the Debian Bug report #939101,
regarding elogind: elogind 239 in bullseye FTBFS with gcc-9
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
939101: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939101
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: elogind
Version: 239.3+20190131-1+debian1
Severity: serious
Control: fixed -1 241.3-1+debian1
Control: block -1 by 934132
Reproducible builds of src:elogind 239.3+20190131-1+debian1 in bullseye
have FTBFS for the last few days. This seems to be related to the
migration of gcc-9 to bullseye.
The issue appears to be the STRING_FOREACH macro and was fixed in
systemd in v241:
https://github.com/systemd/systemd/issues/11394
https://bugzilla.opensuse.org/show_bug.cgi?id=1121387#c0
This fix is already included in elogind 241.3-1+debian1 which is in
unstable. However, migration of elogind 241.3-1+debian1 to bullseye is
currently blocked (see #934132). When it is unblocked it should resolve
this issue.
Mark
--- End Message ---
--- Begin Message ---
elogind/241.3-1+debian1 is now in bullseye so this is no longer an issue.
Closing.
Mark
--- End Message ---
