The bodhi update for the 3.0.0 update on f33 was unpushed for ... reasons, which leads to the awkward situation of the package having been updated to 3.0.0 in f31, f32, and rawhide/f34, but f33 still being at 2.9.6. This leads to package downgrades when upgrading fedora from fedora 32 to fedora 33: - knot is newer in 32 than in 33: 0:3.0.0-1.fc32 > 0:2.9.6-1.fc33 - knot-devel is newer in 32 than in 33: 0:3.0.0-1.fc32 > 0:2.9.6-1.fc33 - knot-doc is newer in 32 than in 33: 0:3.0.0-1.fc32 > 0:2.9.6-1.fc33 - knot-libs is newer in 32 than in 33: 0:3.0.0-1.fc32 > 0:2.9.6-1.fc33 - knot-utils is newer in 32 than in 33: 0:3.0.0-1.fc32 > 0:2.9.6-1.fc33 Can you push the 3.0.0 update to fedora 33 again to fix the downgrade issue? https://bodhi.fedoraproject.org/updates/FEDORA-2020-fd0435566d Maybe also do the accompanying rebuild of knot-resolver that was mentioned in the update alongside the negative karma.
Hello, I wanted to enable Fedora CI [1] before re-trying this update to prevent further breakages like the one that lead to unpushing it (incompatible `.so` version) before rebuilding but there are issues with the underlying Jenkins instance preventing it to work at this time so I'm gonna build and test the update manually ASAP in the light of upgrade issues you mentioned. I'm sorry for the inconvenience, stay tuned for the update fixing this. [1] https://src.fedoraproject.org/rpms/knot-resolver/pull-request/4#
Oh, I reminded myself why this actually wasn't done with the rest of the batch: remote: Unspecified ref refs/heads/f33 is blocked remote: Denied push for ref 'refs/heads/f33' for user 'jruzicka' I assumed this is due to Fedora 33 freeze as I was able to push/build other branches: https://fedorapeople.org/groups/schedule/f-33/f-33-key-tasks.html I'm going to eagerly rebuild and push fixing update as soon as possible.
No, this is caused by an outage of pdc.fedoraproject.org
(In reply to Fabio Valentini from comment #3) > No, this is caused by an outage of pdc.fedoraproject.org I see. I hit the same (or similar-looking) issue before on `f33` branch so I assumed this is intended change to release process. Do you think this update is worth a freeze exception once I'm able to rebuild both `knot` and `knot-resolver`?
Update: `knot` build is currently failing on `f33`/`rawhide` due to failing tests: $> ./test_semantic_check | grep 'not ok' not ok 42 - different_signer_name.signed - check errors not ok 148 - rrsig_ttl.signed - correct zone, without error not ok 149 - no_error_delegaton_bitmap.signed - correct zone, without error not ok 150 - no_error_nsec3_delegation.signed - correct zone, without error not ok 151 - no_error_nsec3_optout.signed - correct zone, without error The "good" thing is these fails are consistent - I was able to reproduce them both in a f33 docker container and in an improvised f33 VM. Also the very same package built successfully in f33/master about 3 weeks ago so it's likely something caused by a new version of a dependency introduced since then. I wasn't able to debug the test myself during my brief look so I'll work on this with upstream and aim at having builds and the update ready before f33 release. Here's a convenience link to koschei for inspecting new deps: https://koschei.fedoraproject.org/package/knot?collection=f33
Upstream 3.0.1 release fixes test issues introduced by new stricter gnutls policies introduced in Fedora 33. knot-3.0.1-1.fc33 build is ready [1] but I'm still waiting for my build override [2] to take effect which is needed to build depending package knot-resolver. [1] https://koji.fedoraproject.org/koji/buildinfo?buildID=1623847 [2] https://bodhi.fedoraproject.org/overrides/knot-3.0.1-1.fc33
FEDORA-2020-6f500ea4ff has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-6f500ea4ff
FEDORA-2020-6f500ea4ff has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-6f500ea4ff` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6f500ea4ff See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-6f500ea4ff has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.