Dne 13. 07. 25 v 7:16 Gary Buhrmaster napsal(a):
I have a (somewhat?) strange situation (or at least strange for me, maybe others have this on a regular basis), that I wish to understand how to proceed.I have a library (libcbor, if it matters) which has a new version with a soname bump. It will require rebuilding of three packages in a side tag, libfido2 (which I can do myself), and fwupd and qemu. However, qemu is currently FTBFS due to (I think) the python 3.14 bump ( https://bugzilla.redhat.com/show_bug.cgi?id=2375004 ). libfido2 is in the critical path (which means indirectly libcbor is too). I have sort of waited for a bit to see if the qemu team would update the package for python 3.14 compatibility, but I have not seen a recent update to the package.
I think that you have forgotten to announce the soname bump this time (or maybe it is part of the "sort of" waiting ;) ). If you do that, you'll still need to wait for a week (which gives QEMU folks additional time to react):
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#_rawhide
I would *like* to do the soname bump before the mass rebuilds to avoid the expected fallouts (and, of course, to be a blamee), but I don't wish to break qemu. What are my best (or less worst?) options here?
While the policy says "Feel free to push out the newest version of packages as long as they do not cause breakage.", I would not be that strict and would not read it as "You must not push packages if they do cause breakage". If you e.g. tried with QEMU in F42 and you are confident the ABI change in your library won't be issue after the QEMU compatibility is fixed, I'd say feel free to make the judgement call and push the change.
And as a Rawhide use, I think we are in better position then we used to be and I am not going crazy to see some broken dependencies (especially if this was communicated). I just don't update some packages and keep going. Hopefully they'll be fixed next time.
Vít
OpenPGP_signature.asc
Description: OpenPGP digital signature
-- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
