#60 Update Knot to new API version
Closed: Fixed 3 years ago by tdawson. Opened 4 years ago by smooge.

https://lists.fedoraproject.org/archives/list/epel-devel@lists.fedoraproject.org/message/7D7NCLNKH3YMNDBPQQJES6JY6YC64I42/

Tomas Krizek tomas.krizek@nic.cz via lists.fedoraproject.org
Attachments
Wed, 26 Jun, 04:26 (6 days ago)
to epel-devel

Hi,

I'd like to rebase knot and knot-resolver packages to their latest
upstream versions (Knot DNS 2.8.2, Knot Resolver 4.0.0) in EPEL 7.

Reasons

  • upstream of Knot DNS supports only 2.7 and 2.8; the knot version in
    EPEL 7 (2.6.9) is unsupported and will not receive any more security or
    other bugfixes
  • upstream of Knot Resolver supports only the latest version which is
    binary-compatible only with Knot DNS 2.8+; the version of knot-resolver
    in EPEL7 will not receive any more security or other bugfixes

Potential Issues

  • in case the user has made changes to default configuration of Knot
    Resolver, manual update of the config file may be required [1]
  • in case the user has written custom module for Knot Resolver, a manual
    update may be required [1]

Additional info

  • upstream has documented the update process [1], [2] and it should be
    seamless for Knot DNS (and default configurations of Knot Resolver)

[1] - https://knot-resolver.readthedocs.io/en/stable/upgrading.html
[2] -
https://www.knot-dns.cz/docs/2.8/html/migration.html#upgrade-2-7-x-to-2-8-x


+1 here as long as announcements are made, etc...

+1
As Kevin said, as long as they follow the protocal's of announcements and stuff. And since this ticket is here, it looks like they are.

I would like to edit this to +1 if the karma is set higher and/or testing is 3 weeks. OR this happens after 7.7 is released This would have been a great candidate to have done in a 'staging' environment, but we did not get that done in time.

It appears that both knot and knot-resolver were updated in EPEL7 several months ago.
Can we close this issue?

Metadata Update from @tdawson:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata