Re: Missing RHEL 9 buildroot packages in EPEL 9 buildroot

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

 



On Tue, Mar 1, 2022 at 8:45 AM Stephen John Smoogen <smooge@xxxxxxxxx> wrote:
>
>
>
> On Tue, 1 Mar 2022 at 08:19, Richard W.M. Jones <rjones@xxxxxxxxxx> wrote:
>>
>> On Tue, Mar 01, 2022 at 04:21:56AM -0500, Neal Gompa wrote:
>> > On Tue, Mar 1, 2022 at 3:07 AM Richard W.M. Jones <rjones@xxxxxxxxxx> wrote:
>> > >
>> > >
>> > >   https://bugzilla.redhat.com/show_bug.cgi?id=2058274
>> > >
>> > > fails to build with:
>> > >
>> > >   DEBUG util.py:444:  No matching package to install: 'ocaml-dune >= 1.0'
>> > >
>> > > This package is in RHEL 9 buildroot (ocaml-dune-2.8.5-5.el9.x86_64).
>> > >
>> > > I read an earlier thread ("Subject: [EPEL-devel] Re: Packages
>> > > disappearing from the EPEL 9 buildroot") and it seems to indicate that
>> > > RHEL 9 buildroot packages aren't going to be available in EPEL 9.
>> > > This seems crazy, is it really correct?
>> > >
>> >
>> > It's not crazy. EPEL is intended to build on RHEL content, which means
>> > we can't depend on something RHEL doesn't publish. If Red Hat wants to
>> > publish their buildroot repo, then sure, we could use it.
>>
>> I wasn't very clear, but I was addressing my remark at Red Hat.
>> There's really no reason why we (Red Hat) don't publish buildroot, in
>> fact my personal view is we ought to for open source reasons.
>>
>
> I do not think you will find much disagreement here.. but after 3+ years of saying it and nothing changing, many of us have made our peace.

To be a bit more fair, we have not blindly added all buildroot content
to RHEL.  However, we have made progress on coming up with a way to
request these packages be added and worked to help teams internally
understand the implications of this.  We continue to add content to
every RHEL minor release.

That's not nothing.  It's just not everything.

josh
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure




[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