Re: Missing RHEL 9 buildroot packages in EPEL 9 buildroot

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

 



On Fri, Mar 11, 2022 at 09:36:08AM +0000, Richard W.M. Jones wrote:
> On Fri, Mar 04, 2022 at 11:14:31AM +0000, Richard W.M. Jones wrote:
> > On Fri, Mar 04, 2022 at 11:01:20AM +0000, Richard W.M. Jones wrote:
> > > On Fri, Mar 04, 2022 at 10:51:48AM +0000, Richard W.M. Jones wrote:
> > > > I'll see if we can move the OCaml packages to CRB.  It seems to be the
> > > > easiest way to fix the original coccinelle build problem.
> > > 
> > > This gets odder.  I see from our internal spreadsheet and downloads
> > > that some of the ocaml packages are in fact already in CRB for RHEL
> > > 9.0, and others are not.  We previously requested that all ocaml-*
> > > packages be added to CRB.
> > > 
> > > Binary packages which are not in CRB but should be:
> > > 
> > > ocaml-calendar*
> > > ocaml-camomile*
> > > ocaml-csexp*
> > > ocaml-csv*
> > > ocaml-curses*
> > > ocaml-dune*
> > > ocaml-fileutils*
> > > ocaml-gettext*
> > > ocaml-libvirt*
> > > ocaml-source
> > > ocaml-xml-light*
> > > 
> > > Do you need a BZ opened to move these packages to CRB?
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=2060850
> 
> Currently even with this bug fixed we won't be able to build
> Coccinelle until RHEL 9.1 is released, which is like 9+ months away.
> This (if true) is ridiculous.  Is there some other solution?

I have now rebuilt all the packages and they're in a RHEL 9.1 erratum
(RHBA-2022:89734-01 for those who have access).

Is there anything we can do to get these packages into the EPEL
buildroot so we don't have to wait forever to build coccinelle for
EPEL?

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
libguestfs lets you edit virtual machines.  Supports shell scripting,
bindings from many languages.  http://libguestfs.org
_______________________________________________
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