On Tue, Apr 6, 2021 at 12:42 PM Fabio Valentini <decathorpe@xxxxxxxxx> wrote: > --- A quick update: I have created the missing bodhi updates where the packagers obviously just forgot to file one, or missed the announcement of the updates-testing activation point (i.e. builds for f35 and f34 (and sometimes f33 or even f32) exist, but no bodhi update for f34 was created). As far as I can see, this leaves 21 packages with issues, those being various combinations of: - a missing commit in f34 dist-git branch, - a missing koji build for f34, - mistagged packages, possibly related to a build that happened right during mass branching (looking at you, gecode). Question regarding further actions: - Would it be OK if I fix a few packages where there are missing *builds* for f34 as well? (Of course, only where it is obvious that the packager just forgot to merge the same changes that already happened on rawhide and f33 branches.) - Would it be OK if I file freeze exceptions for the bodhi updates that fix upgrade path, or is it fine if they are just 0day-updates? (Freeze-excepting packages that land on any images would probably be a good idea, but I don't know how to check that for individual packages.) Fabio --- > - YafaRay-0:3.5.1-8.fc33 > YafaRay-0:3.5.1-7.fc34 > - YafaRay-blender-0:3.5.1-8.fc33 > YafaRay-blender-0:3.5.1-7.fc34 > - YafaRay-devel-0:3.5.1-8.fc33 > YafaRay-devel-0:3.5.1-7.fc34 > - YafaRay-lib-0:3.5.1-8.fc33 > YafaRay-lib-0:3.5.1-7.fc34 > > YafaRay seems to have been updated on f33 but not on f34, or the > release bump was done to the "main" integer instead of appending .1 > after dist if it was a stable-release-branch-only change. I have unpushed the update that broke the upgrade path for YafaRay. It had collected -2 negative karma already, and it bumped a SONAME in F33 / stable. > - conky-0:1.12.1-1.fc33 > conky-0:1.11.6-2.fc34 > > Was successfully built for f34, but no bodhi update was submitted. Created a bodhi update: https://bodhi.fedoraproject.org/updates/FEDORA-2021-90f942916f > - container-selinux-2:2.160.0-1.fc33 > > container-selinux-2:2.158.0-1.gite78ac4f.fc34 > > Bad rhcontainerbot (built for f34, but no update created). Created a bodhi update: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ac9daea36e > - cppad-devel-0:20210000.3-3.fc33 > cppad-devel-0:20210000.3-2.fc34 > - cppad-doc-0:20210000.3-3.fc33 > cppad-doc-0:20210000.3-2.fc34 > > Update was built for f34, but no bodhi update was created. Created a bodhi update: https://bodhi.fedoraproject.org/updates/FEDORA-2021-5f179fa2c6 > - python-scrapy-doc-0:2.4.1-1.fc33 > python-scrapy-doc-0:1.5.1-10.fc34 > - python3-scrapy-0:2.4.1-1.fc33 > python3-scrapy-0:1.5.1-10.fc34 > > The 2.4.1 update had been built for f34, but no bodhi updates has been > submitted. Created a bodhi update: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ee5190cbb0 > - yoshimi-0:2.0-1.fc33 > yoshimi-0:1.7.4-2.fc34 > > yoshimi 2.0 was built for f34, but no bodhi update was created. Created a bodhi update: https://bodhi.fedoraproject.org/updates/FEDORA-2021-4b3d6a519d _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
