[EPEL-devel] Re: EPEL 10 status update

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

 



On Tue, Aug 13, 2024 at 9:12 AM Stephen Smoogen <ssmoogen@xxxxxxxxxx> wrote:

> This is something I wanted to do in previous EPEL splits, but it has usually gotten too many complaints from packagers to consider. Many packagers don't want their packages in EPEL at all but will do so if there are requests from someone or that there is going to be a branch packager for EPEL packages. Many EPEL branch packagers really only want to support one release because that is what they are using versus multiple ones.

There is also the case (I had one), where a package
(in epel8) was later incorporated by RH into EL9, for
which automatic branch requests might have been an
issue (unless the automatic approval processes already
checks for that and rejects the branch request).

> That said, I think it is something to revisit like we did for EL7, EL8 and EL9 :).

Personally, automatic branching would work fine
for me, but often my bigger issue is opening the
bugzilla tickets for the often large dependency
chain for some scripting languages asking for
each package to be actually built, and then
waiting for the packager to have the resources
to build them.  If one starts with the premise that
the packagers should control the creation of all
branches then auto-creating all those dependency
branch/build bugzillas (and *their* dependency
branch/build bugzillas, and so on) might be a
better step forward to reduce the process delays.
-- 
_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue




[Index of Archives]     [Fedora Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Announce]     [SSH]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Linux Apps]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux