Thank you for the question/comment, Ian. On pondělí 1. prosince 2025 22:33:44, středoevropský standardní čas Ian Pilcher via copr-devel wrote: > On 12/1/25 9:27 AM, Jakub Kadlcik via copr-devel wrote: > > Everything is explained in this blog post: > > https://fedora-copr.github.io/posts/migrating-copr-results-to-pulp > > > > Please let us know if you have any questions or concerns, > > From the blog post: > > > While your projects are being migrated, all your builds and actions > > will be stuck in the “pending” state until the migration is finished. > > ... and ... > > > For technical reasons, we won’t notify users directly that their > > projects are about to be migrated. Please see the Pulp Migration > > Schedule to get a rough estimate of when you could be affected. > > That's certainly not ideal.
For owners who have a standard number of projects and a reasonable size of generated content, the update should be very quick. Note that you won't wait for the entire group of users to be migrated, just the single owner. Most users won't even notice (we could send emails, but it's not worth triggering spam filters, we have thousands of owners). > My question, though, is whether there will be any user-visible > indication during a migration that this is the reason that everything is > stuck. Otherwise, I can foresee a flood of tickets, emails, etc. when > (months from now) things appear broken. We can technically keep the banner updated declaring which users are being migrated right now, that sounds like a good idea. Pavel -- _______________________________________________ copr-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.fedorahosted.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
