This bug was fixed in the package strace - 5.19-0ubuntu1
---------------
strace (5.19-0ubuntu1) lunar; urgency=medium
* New upstream release (LP: #1990964)
* Update d/copyright to reflect upstream relicensing to LGPL >= 2.1 from
2018 and its switch from sourceforge to github.
* Drop merged patch 0006-s390-Check-infmname-with-IS_ARRAY_ZERO-too.patch
-- Adrien Nader <adrien.na...@canonical.com> Mon, 21 Nov 2022 16:05:44
+0100
** Changed in: strace (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990964
Title:
FTBFS on kinetic
Status in linux package in Ubuntu:
Fix Released
Status in strace package in Ubuntu:
Fix Released
Status in linux source package in Kinetic:
New
Status in strace source package in Kinetic:
New
Bug description:
As can be seen in [1], strace FTBFS in kinetic: this is caused by the
kernel headers (linux-libc-dev) which do not define F_GETLK64 and
other on 64b builds because the kernel contains a bogus commit
(306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in
fcntl.h"). This commit actually did the opposite of what it was
supposed to do, namely defining those macros even on 64b builds. There
is an attempt here to fix this which was not merged yet:
https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/
[1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic-
amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
