Thanks for that info, I actually did not know about that particular feature of the changelog. I’ll try to use that from now on. On 26 Aug 2022, at 9:02, Vít Ondruch wrote: > If you included `Resolves: rhbz#2114563` in the changelog, the automatically created bodhi update would resolve the ticket. Since you have not done this, then you have to close the ticket yourself and possibly include the NVR in 'Fixed In Versoin' field. > > > Vít > > > > Dne 26. 08. 22 v 15:48 Ron Olson napsal(a): >> Hey all, >> >> https://bugzilla.redhat.com/show_bug.cgi?id=2114563 was reported against Swift on Rawhide. I fixed the issue and responded on 8/4 that the Koji build was successful, but I got two additional, presumably automated, notes from Ben Cotton and Miro that suggest something else needs to be done. Since this is/was a rawhide build there’s nothing to “fedpkg update” as I recall, so I guess what I’m asking is what should I do to make it clear that Swift is working for Rawhide/F37? I admit I’ve always been kind-of unsure how Rawhide works insofar as I’ve never submitted a “formal update” to it (i.e. the aforementioned “fedpkg update” command). >> >> Thanks, >> >> Ron >> _______________________________________________ >> devel mailing list -- devel(a)lists.fedoraproject.org >> To unsubscribe send an email to devel-leave(a)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 > _______________________________________________ > devel mailing list -- devel(a)lists.fedoraproject.org > To unsubscribe send an email to devel-leave(a)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

On 26/08/2022 14:48, Ron Olson wrote: Well it was reported before branching and you fixed it but didn't actually close it so it looks like it is still an active bug and hence got automatically moved to F37 and added as a blocker to the FTBFS bug. If it was fixed before branching, as appears to be the case then the fix is in F37 now so you can just close it NEXTRELEASE. Tom -- Tom Hughes (tom(a)compton.nu) http://compton.nu/

Hi, Usually for Rawhide updates CLOSED RAWHIDE + add NVR into `fixed in version` if only Rawhide fixes that bug (e.g., a new software version), that should be enough. But it seems auto updates can take care of the tickets if you specify the bugs via the `Resolves: rhbz#1234` references as noted by Vít. A webpage… Depends what you plan on doing, I use this if I am unsure in the bug status workflow: https://docs.fedoraproject.org/en-US/package-maintainers/bug_status/ Regards, Jarek On 8/26/22 16:28, Ron Olson wrote: