On Fri, May 3, 2024, 09:34 Florian Weimer <[email protected]> wrote:
> I didn't have a dist-git token for fedpkg, so retiring failed after > doing some work the first time. Is the package actually retired? > It looks like the retirement was successful The dist-git token is only necessary for one API call - disabling the "monitoring" setting. But that was already disabled for this package, so it wouldn't have changed anything. > This command > > koji list-history --package=glibc32 > > does not show any recent activity. I would expect something to untag it > from the buildroot. > This should happen when the retirement is processed during the next rawhide compose. > (Bonus question: can we retire the package from Fedora 40, too?) > No. Retirements can only happen until the start of the final freeze. Fabio > Thanks, > Florian > -- > _______________________________________________ > devel mailing list -- [email protected] > To unsubscribe send an email to [email protected] > 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/[email protected] > Do not reply to spam, report it: > https://pagure.io/fedora-infrastructure/new_issue >
-- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
