#2129 knot / knot-resolver package rebase exception request
Closed: Accepted 4 years ago by zbyszek. Opened 4 years ago by tkrizek.

I'd like to rebase knot and knot-resolver packages to their latest upstream versions (Knot DNS 2.8.1, Knot Resolver 4.0.0) in Fedora 29, Fedora 30 and 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 F29, F30 and EPEL7 will not receive any more security or other bugfixes
  • rebase to latest upstream versions will allow bugfixes and other updates to both Knot DNS and Knot Resolver, most likely for the entire lifetime of F29 and F30 (although EPEL 7 is expected to eventually have the same issue again in the future)

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

  • this is a one-time request, not a permanent exception
  • together, Knot DNS and Knot Resolver can be considered as leaf packages, as no other package depends on them
  • 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 for Fedora. Should EPSCo decide EPEL?

+1 for Fedora too. +1 for EPEL7 if we decide EPSCo should not handle this.

Based on the policy, this is now approved for Fedora but not yet for EPEL.

Metadata Update from @churchyard:
- Issue tagged with: pending announcement

4 years ago

You could send a note to fedora-devel for additional testing. If bodhi feedback indicates no issues, there should be no need to notify users.

Metadata Update from @zbyszek:
- Issue untagged with: pending announcement
- Issue close_status updated to: Accepted
- Issue status updated to: Closed (was: Open)

4 years ago

@churchyard I'm not sure what is the outcome for EPEL - should I raise this issue with EPSCo?

Yeah, please file a ticket with EPSCo.

Login to comment on this ticket.

Metadata