[Bug 274907] net/krill Update to version 0.14.1
Date: Sat, 04 Nov 2023 14:29:55 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274907 Bug ID: 274907 Summary: net/krill Update to version 0.14.1 Product: Ports & Packages Version: Latest Hardware: Any URL: https://github.com/NLnetLabs/krill/releases/tag/v0.14. 1 OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: jaap@NLnetLabs.nl Attachment #246109 maintainer-approval+ Flags: Created attachment 246109 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=246109&action=edit Patch to upgrade This update includes 0.14.0 'ASPA' Extra, Extra! Latest This release fixes a bug in the migration code where 'surplus' directories for archived events should be skipped (#1147). Release 0.14.0 'ASPA' adds support for the updated ASPA v1 profile (issue #1080). Any existing ASPA objects will be re-issued automatically. Updated documentation can be found here. In addition, the following small features and fixes were done: Show delete ROA button when no BGP preview is available #1139 o Add traditional and simplified Chinese translations #1075 o Let the testbed automatically renew the TA manifest and CRL #1095 (see below) o Show the delete icon for AS0 ROA when there is another existing announcement #1109 o The main effort in this release was spent on less user-visible improvements in how Krill stores its data. This will help improve robustness today and pave the way for introducing support for Krill clustering using a database back-end in a future release. For now, these issues have been done: o Improve transactionality of changes (e.g. #1076-1078, #1085, #1108, #1090) o Remove no longer needed 'always_recover_data' function #1086 o Improve upgrade failed error: tell users to downgrade #1042 o Crash Krill if the task scheduler encounters a fatal error. #1132 You can find the full list of issues here: https://github.com/NLnetLabs/krill/projects/25 Finally, regarding issue #1095. If you were running 0.13.1 as a testbed, you might have symlinked the "signer" directory to "ta_signer" to support a manual workaround for re-signing the trust anchor CRL and manifest. If you did, you may need to delete any surplus files and directories under "data/ta_signer" other than the " ta " directory. -- You are receiving this mail because: You are the assignee for the bug.