Dne 14. 12. 21 v 17:12 Matthew Miller napsal(a):
But it seems like "request an EPEL branch" should generally be either "Okay!
Doing that automatically now" or "Oh, this is in EL, sorry"*. What are the
other cases?
As far as I know this isn't about requesting EPEL branches, as much as
requesting any branches by hand. If I add something to Fedora rawhide
and then ask for a F34 branch, the same issues can happen. Remember
our build infrastructure is a pile of band-aids on top of duct tape on
top of bungee cords. Lots of tools are written for a toolchain which
existed years ago and have been hacked to make it work with whatever
new initiative that comes into play. 'Unexpected' side effects and
corner cases happen all the time and the fixing of them tends to add
new ones.
Sure. But also, asking people to spend a lot of their time running
grunt-work tasks means that they have less time to fix when things break,
let alone re-engineer away some of that tech debt. It seems like we should
be able to automate the simple cases (adding F34 and F35 branches should be
even easier, since we don't have the "is it in EL?" question even).
*nod*
So ... the question is how can I help? Can you document the check-list? I
volunteer to start writing the script.
Miroslav
_______________________________________________
epel-devel mailing list -- epel-devel@lists.fedoraproject.org
To unsubscribe send an email to epel-devel-le...@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/epel-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
