Parag Nemade venit, vidit, dixit 2025-06-17 04:39:32: > On Tue, Jun 17, 2025 at 1:27 AM <c...@luigifab.fr> wrote: > > > loool, ok... > > > > I can update my SPECs from aspell to hunspell, but I see hunspell-fr > > isn't in EPEL. > > Maybe I can ask to branch them (hunspell + hunspell-fr)? > > > > > Both packages are already part of the RHEL 10 release. No need to request > for the EPEL branch. > Maybe you want to read https://docs.fedoraproject.org/en-US/epel/epel-faq/ > to understand EPEL and RHEL package relationship. > > Regards, > Parag
This shows (again) some rough edges which are there for Fedora packagers willing to contribute to the *EL ecosystem via EPEL packaging. The scenario is: - package y is in EPEL n - you decide to package x for EPEL n, which depends on y - your package x fails to build for EPEL n+1 - dist-git shows there is no package y in EPEL n+1 (only in EPEL n) Several causes are possible: A) package y has not neen built yet for EPEL n+1 B) package y has been "promoted" to be in RHEL n+1 but without y-devel C) package y has been "promoted" to be in RHEL n+1 but there is an unrelated problem In case A), you can request a build of y in EPEL n+1, but frankly I've often had a really hard time getting even the answer "not interested" which is the prerequisite for me taking over y in EPEL n+1. In case B), you can request a build (ship) of y-devel in CRB, but frankly ... Case C) is hard to discover unless you've ruled out or solved A) and B) or built y (with y-devel) locally or in COPR, and in both cases you may face subtle differences between a RHEL-like mock chroot and a "real" RHEL/EPEL build environment. We should really make this easier, because right now, you have to discover https://docs.fedoraproject.org/en-US/epel/epel-faq/#how_can_i_know_which_packages_are_part_of_rhel and then decide whether you'd rather grep a webpage or go by COS info which does *not* tell the whole story, in particular with regard to the y/y-devel problem. Michael -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to 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/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
