On Mon, Jan 10, 2022 at 9:32 AM Petr Pisar <ppi...@redhat.com> wrote:
> Hello, > > I happened to hit a request for adding web-assets-devel binary package of > web-assets component to EPEL 9 (bug #2036086) while web-assets-filesystem > binary package is shipped in RHEL. I recall it is allowed, but ones need to > follow some rules which I cannot find now. > > Current Packaging guide lines > <https://docs.fedoraproject.org/en-US/epel/epel-packaging/> do not > document > this particular case. The closest one is adding missing architectures > (Limited > Arch Packages section). > > Do you know the rules for adding the missing subpackages? > > I remember that release number needs to be kept lower. > What about component (source package) name. Can I use reuse it, or do we > need > to rename it to keep Koji happy in case it has imported CentOS builds? > I guess I should disable subpackages already shipped by RHEL. > > -- Petr > This currently is in the FAQ.[1] We recently discussed this in the EPEL Steering Committee Meeting, because some clarification was requested.[2] I am in the middle of writing a new page with the outcome of the meeting [3]. I'll write a separate page, because this gets asked enough, that it deserves it's own page. Because I haven't gotten the new page written yet, follow the instructions in the FAQ, and ask if things are not clear. Two things to note. 1 - Name it web-assets-epel That has changed from a recommended to a Must for packages that are just supplying a missing -devel sub-package. 2 - Most -devel packages have a Requires: %{name}-%{version}-%{release} It is suggested that you drop the -%{release} to save headache if you need to redo the package. If you do need it tied that closely to the release, let us know. We've come up with ways to do that, so just ask. Troy [1] - https://docs.fedoraproject.org/en-US/epel/epel-faq/#rhel_8_has_binaries_in_the_release_but_is_missing_some_corresponding__devel_package._how_do_i_build_a_package_that_needs_that_missing__devel_package [2] - https://pagure.io/epel/issue/134#comment-767745 [3] - https://pagure.io/epel/issue/134#comment-772905
_______________________________________________ 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
