Is there a process for EPEL 7/8 FTBFS issues?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi everybody,

Over time, I've encountered some packages that fail to build on EPEL7
/ EPEL8, in some cases, like since forever. Is there an equivalent to
the FTBFS cleanup in rawhide / fedora N+1 for EPEL branches? Or are
those packages just left to rot?

Two examples:
- assertj-core (seems to be a leaf package), broken epel7 branch
- replacer (required by a total of 4 other packages, recursively),
broken epel7 branch

Those two are maintained by the Stewardship SIG right now, and we have
no interest in EPEL branches whatsoever. I guess we could retire the
one without dependent packages, but what about packages that are still
needed by something else?

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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux