This bug was fixed in the package kronosnet - 1.32-1ubuntu1
---------------
kronosnet (1.32-1ubuntu1) resolute; urgency=medium
* Merge with Debian unstable (LP: #2131648). Remaining changes:
- d/rules: don't disable fortify feature. It adds
-D_FORTIFY_SOURCE=0 in Ubuntu and conflicts with the upstream
-D_FORTIFY_SOURCE=3 option.
- d/p/gnu-date-check.patch: change GNU date check to also allow for
the rust-coreutils variant (LP #2125058)
- d/t/control: add the build-needed restriction, since the test calls
./configure
kronosnet (1.32-1) unstable; urgency=medium
* [14ea589] New upstream release (1.32)
* [48e21b1] Acknowledge new symbol
* [9b3094b] Lintian 2.117.1+ knows about the t64 transition
* [6594e01] Finish transitioning our autopkgtests to pkgconf
* [dee7c17] Simplify Salsa CI configuration
* [80181a2] Domain_host variation does not break nozzle tests anymore
* [24cc88a] We've been using external doxygen2man since release 1.20-2.
And the current syntax was broken by Salsa CI commit
891bc54894db47f58c963964ec795c33ddc5f853 anyway.
-- Renan Rodrigo <[email protected]> Mon, 17 Nov 2025 05:15:44 -0300
** Changed in: kronosnet (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2131648
Title:
Merge kronosnet from Debian Unstable for resolute
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kronosnet/+bug/2131648/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
