Hi everybody, It's that time of the semi-year again, and I again found multiple instances of packages that have updates for rawhide and f31/f30, but no bodhi update for fedora 32. In most cases, the updated package was built on fedora 32 (a koji build was successful), but no bodhi update was created. In some cases, f32 was "forgotten" entirely. So, assuming the best, those packagers simply forgot that bodhi updates are necessary for branched releases after the beta freeze. What is the best couse of action for such forgotten updates? Some are bugfixes, others are new versions, and some could be security fixes, that are then missing from f32 entirely. I *could* file bodhi updates for everything that's missing from f32, but I do not want to interfere with others' work here. Filing bodhi comments on the updates that break the upgrade path (f31/f30, in this case) is not productive either, since those comments are often ignored in my experience. A few examples that popped up on my systems (I'm sure there are more): 1) dnsmasq-2.80-12.fc31 is going to f31 stable: https://bodhi.fedoraproject.org/updates/FEDORA-2020-aab29ac03c The corresponding f32 build (dnsmasq-2.80-13.fc32) succeeded in koji, but then an internal koji error broke it. It wasn't resubmitted, and there's no bodhi update for it: https://koji.fedoraproject.org/koji/taskinfo?taskID=42386221 2) libinput-1.15.3-2.fc31 is going to f31 stable: https://bodhi.fedoraproject.org/updates/FEDORA-2020-d66ed9f32e The corresponding f32 build in koji was successful, but no bodhi update is associated with it: https://koji.fedoraproject.org/koji/buildinfo?buildID=1475404 3) python-matplotlib-3.1.3-1.fc31 is going to f31 stable: https://bodhi.fedoraproject.org/updates/FEDORA-2020-188dd2b161 The update to 3.1.3 has been built for f33 and f31, but not for f32. The 3.1.3 changes aren't even merged from master into the f32 branch in dist-git. Any suggestions what we could do to make sure f32 updates aren't forgotten after the beta freeze? Fabio _______________________________________________ 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
