Latest upstream release: 9.16.20 Current version/release in rawhide: 9.16.19-4.fc35 URL: https://www.isc.org/bind/ Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/ More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream. Based on the information from anitya: https://release-monitoring.org/project/77661/
Created attachment 1815325 [details] [patch] Update to 9.16.20 (#1995289)
the-new-hotness/release-monitoring.org's scratch build of bind-9.16.20-1.fc32.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=74091389
Found new issue when trying new build, there seems to be incompatible change in map fileformat zone.
Built in rawhide
FEDORA-2021-fbb258debf has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-fbb258debf
FEDORA-2021-fbb258debf has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-fbb258debf` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-fbb258debf See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-fbb258debf has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FTR recommened way to patch out this issue is https://ftp.isc.org/isc/bind9/9.16.20/patches/bind-9.16.20-map-format-fix.patch
Recommended way rebuilt with reference to bug #1997504, which was created to gather links about the issue. Solution is still unmerged upstream AFAIK, is there agreement it is the best approach?
(In reply to Petr Menšík from comment #9) > Recommended way rebuilt with reference to bug #1997504, which was created to > gather links about the issue. Solution is still unmerged upstream AFAIK, is > there agreement it is the best approach? Yes it is, barring unforeseen complications. The only thing which is holding the merge is missing documentation and release notes.