On Mon, Jan 27, 2025 at 3:32 AM Ian McInerney via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > Were the FTBFS bugs filed differently this time? It appears that there were actually two FTBFS bugs filed against Audacity (https://bugzilla.redhat.com/show_bug.cgi?id=2339522 and https://bugzilla.redhat.com/show_bug.cgi?id=2339913) that both reference the same Koji task, but then the first bug was marked as a duplicate of the later one by releng shortly after its creation? > > Also, it appears that the FTBFS bugs for the mass rebuild have been linked to the FTBFS tracker from F41 (https://bugzilla.redhat.com/show_bug.cgi?id=2260875), can this be fixed so there is a FTBFS tracker for F42 separate from F41? It was done "differently" in the sense that it was first done "wrong" :D To my knowledge, the script that files the FTBFS bugs was first - launched with settings to block the wrong bug (F41FTBFS), - when this was noticed, stopped, and re-run blocking the correct F42FTBFS, - duplicate bugs were manually closed, and had Blocks: F41FTBFS removed from them. So the F42FTBFS blocker bug already exists (https://bugzilla.redhat.com/show_bug.cgi?id=F42FTBFS). It's possible that one of your package was affected by the double-run and wasn't "cleaned up" properly. 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 Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
