Summary: | app-emulation/lxd-4.0.7 - ./.../syscall_wrappers.h: error: conflicting types for close_range; have int(unsigned int, unsigned int, | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
Component: | Current packages | Assignee: | Joonas Niilola <juippis> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | flow, sam, toolchain, virtualization |
Priority: | Normal | Keywords: | PATCH, PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://github.com/gentoo/gentoo/pull/22383 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 803482 | ||
Attachments: |
emerge-info.txt
app-emulation:lxd-4.0.7:20210808-221327.log emerge-history.txt environment etc.portage.tar.bz2 temp.tar.bz2 |
Description
Toralf Förster
2021-08-09 10:52:40 UTC
Created attachment 731671 [details]
emerge-info.txt
Created attachment 731674 [details]
app-emulation:lxd-4.0.7:20210808-221327.log
Created attachment 731677 [details]
emerge-history.txt
Created attachment 731680 [details]
environment
Created attachment 731683 [details]
etc.portage.tar.bz2
Created attachment 731686 [details]
temp.tar.bz2
Patch from upstream master: https://github.com/lxc/lxd/commit/9a128f32fc277dd0c07bc85c71dc25d123f8a831. Not clear if anybody has backported it but it should be simple from a glance. Let me know if you need help/turns out not to be! Thanks, I do have few questions: 1. How close we are to unmasking glibc-2.34? lxd-4.0.7 was just released so I expect a next one will be months away. Then again they usually make a quicker release for big fixes like this. I do see the tracker bug is about ~20 done. 2: Will there be some runtime issues if you compile lxd-4.0.7 with glibc-2.33, then update to glibc-2.34 without recompiling? I.e., does this require a revbump? (In reply to Joonas Niilola from comment #8) > Thanks, I do have few questions: > 1. How close we are to unmasking glibc-2.34? lxd-4.0.7 was just released so > I expect a next one will be months away. Then again they usually make a > quicker release for big fixes like this. I do see the tracker bug is about > ~20 done. > Not very close, although trying to get stuff w/ patches done so we can focus on the ones where upstream is quiet / bugs need reporting. It'll be a good while. > 2: Will there be some runtime issues if you compile lxd-4.0.7 with > glibc-2.33, then update to glibc-2.34 without recompiling? I.e., does this > require a revbump? No, all good there! The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=4d7295038ed9e84cc131b3003b1d103f35fcea50 commit 4d7295038ed9e84cc131b3003b1d103f35fcea50 Author: Florian Schmaus <flow@gentoo.org> AuthorDate: 2021-09-24 07:49:57 +0000 Commit: Florian Schmaus <flow@gentoo.org> CommitDate: 2021-09-24 08:06:15 +0000 app-emulation/lxd: backport syscall_wrappers patch, use --syslog This backports the lxd patch to avoid conflicts with glibc's close_range(). Also use --syslog instead of --logfile=/var/log/lxd/lxd.log in lxd's systemd service, so that lxd's log messages are not logged to a file, but instead to the service's journal. The ebuild also no longer uses a dedicated apparmor service file (files/lxd-4.0.0_apparmor.service), but instead patches the existing service file if apparmor is used. This avoids maintaining two systemd service files. Also drop the unused autotools eclass. Closes: https://bugs.gentoo.org/807268 Closes: https://github.com/gentoo/gentoo/pull/22383 Signed-off-by: Florian Schmaus <flow@gentoo.org> app-emulation/lxd/files/lxd-4.0.7-r1.service | 20 +++ ...appers-don-t-conflict-with-glibc-provided.patch | 58 +++++++ app-emulation/lxd/lxd-4.0.7-r1.ebuild | 170 +++++++++++++++++++++ 3 files changed, 248 insertions(+) |