Recreating this on canonistack arm64 host with armhf LXD container. Building chrony locally and running the test reproduces the test.
It is good that I can re-create this already at build-time. That makes it less complex to switch glibc between 2.32 and 2.33 and doing a rebuild to check. I wondered why this didn't block/break on build already. But on https://launchpad.net/ubuntu/+source/chrony/4.0-5ubuntu1/+build/21010562 you see that at build time this was skipped: 005-scfilter SKIP (not root) Maybe running that as root might catch things earlier ? ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1915006 Title: Consider merging 4.0-5 for Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1915006/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
