Created attachment 218002 [details]
After dns/knot2-lib is deleted the port dns/knot2 can also be removed.
Is there any possibility that some knot2 config can not run under knot3 ?
Should knot2 be kept at least for a while (mabye with DEPRECATED and EXPIRE) ?
From my own experience I saw an obsolete option just generate a non-blocking warning at validation at startup.
The page https://www.knot-dns.cz/docs/3.0/html/migration.html#upgrade-2-9-x-to-3-0-x states: "Knot DNS version 3.0.x is functionally compatible with 2.9.x.".
So I don't think "cooling down" with DEPRECATED or EXPIRE is needed, but I wouldn't mind having that for a while. But the software will be unmaintained.
What would be nice however, would be something like in Perl5, when you update say perl5-5.26 you automatically get perl5-5.32, but I don't know how and where that's managed.
There is a new 2.X version upstream:
What about update it and mark as deprecated and set an expiry date for two or three months?
Because it seems they will still be maintaining it for a while.
"Since then, it doesn't receive new features or enhancements anymore, but it receives all important fixes. It lacks the latest features, but it's more time-proven."
Like this ?
DEPRECATED= Use knot3, it is functionally compatible with 2.9.x
(In reply to Danilo G. Baio from comment #3)
> Because it seems they will still be maintaining it for a while.
I have to admit that I didn't comprehend that from the announcements, but understood the moment 2.9.7 was released.
I guess I best upgrade the dns/knot2 port AND use these two lines Kurt suggested.
Running knot2 on FreeBSD for an associative ISP here.
AIUI from knot-dns.cz:
> This branch is what used to be Current Stable Branch until it had been replaced by a new Current Stable Branch. Since then, it doesn't receive new features or enhancements anymore, but it receives all important fixes. It lacks the latest features, but it's more time-proven.
Basically: the Previous Stable Branch (2.9.X) is roughly equivalent to FreeBSD STABLE and the Current Stable Branch (3.0.X) is roughly equivalent to FreeBSD RELEASE.
Configuration is supposed to be mostly compatible, except for a change of default in synthrecords and some behaviour change in ACL which likely doesn't affect many users:
Basically: 2.X is supported and, while migration should be easy, there is little reward in forcing such a migration because 3.X has been released.
Created attachment 220573 [details]
meanwhile 2.9.7 is already out since a while.
I made attached patch to update the port, including Kurt's suggestion, adding the grace period.
Tested successful in poudriere (but against 12.1 / amd64 only).
I've been on the knot mailing lists for years. As we
use knot extensively.
Hello Knot DNS users,
CZ.NIC has released Knot DNS 3.0.3 and Knot DNS 2.9.8!
These updates are recommended for users with on-slave DNSSEC signing deployments.
Ubuntu/Debian packages of 3.0.3 version no longer link against jemalloc memory allocator.
Because new versions of Knot DNS behave better with the default memory allocator.
thanks for the patch, will work on it (and updating it to 2.9.8, which is
probably only a minor change).
A commit references this bug:
Date: Tue Dec 15 18:40:19 UTC 2020
New revision: 558171
dns/knot2: upgrade to 2.9.8 and add deprecation advice to use knot3.x
Submitted by: Leo Vandewoestijne <firstname.lastname@example.org> (maintainer)
Reviewed by: Chris Hutchinson <email@example.com>