Hi. I had a discussion about AlmaLinux Beta on root.cz. Some person complained CentOS Stream is unusable, because it is breaking ABI of packages. He got libpoppler as an example. I just thought, we have all public code changes on GitLab. Could we mark MR containing ABI breaks in a special way? It might help catching those changes sooner by maintainers of dependent packages. If EPEL package depends on rebased CentOS package, is there a good way how to handle synchronization to EPEL rebuilds or even rpmfusion depending builds? Would some automation helping with this make sense? Is it rare enough that it does not need any automatic processing? I thought if MR were marked with special tag, maybe on its merge some bot could open bugzillas or even open PR on depending packages with just bumpspec to rebuild. Do you think it would be worth the effort? Does it have better alternative? Cheers, Petr -- Petr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemensik@xxxxxxxxxx PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB _______________________________________________ epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to epel-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/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
