Bug 2060850
Summary: | Move all OCaml packages to CRB | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 9 | Reporter: | Richard W.M. Jones <rjones> |
Component: | distribution | Assignee: | RHEL Program Management <pm-rhel> |
Status: | CLOSED ERRATA | QA Contact: | tingting zheng <tzheng> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 9.1 | CC: | ctwo0002, jbair, jesse.brandeburg, juzhou, jwboyer, mxie, tyan, tzheng, vwu, xiaodwan, ymankad, yoguo |
Target Milestone: | rc | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-11-15 11:23:33 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Richard W.M. Jones
2022-03-04 11:13:31 UTC
tingting, could QA consider ACKing this? I only needs simply checking that the packages end up in CRB. Or should we ask another team for the ACK (release team is current QA owner). (In reply to Richard W.M. Jones from comment #2) > tingting, could QA consider ACKing this? I only needs simply checking > that the packages end up in CRB. Or should we ask another team for > the ACK (release team is current QA owner). Done, I can check it. Couple of questions here: - Is there anything I need to do to this bug (eg. add it to an erratum)? - When will the changes become visible such that we can start building EPEL 9 coccinelle with these packages? Checked latest RHEL9.1 compose:RHEL-9.1.0-20220308.2 These ocaml* packages mentioned in description have not been moved to CRB now, which compose will make the change? Unfortunately - see comment 10 - I will have to rebuild every OCaml package in RHEL 9, which will take quite a lot of effort to do, so I don't know when this will be fixed. It seems as if the results of this won't be available until RHEL 9.1 anyway, so we have no solution for EPEL until that is released at the end of this year. Another reason why RHEL buildroot is a terrible idea as we should try to avoid it as much as possible in future. (In reply to Richard W.M. Jones from comment #12) > Unfortunately - see comment 10 - I will have to rebuild every OCaml package > in RHEL 9, which will take quite a lot of effort to do, so I don't know when > this will be fixed. It seems as if the results of this won't be available > until RHEL 9.1 anyway, so we have no solution for EPEL until that is released > at the end of this year. > > Another reason why RHEL buildroot is a terrible idea as we should try to > avoid it as much as possible in future. Got it,then I will check the bug in late RHEL9.1. I've spent the afternoon building packages. They're currently waiting in OSCI at the moment. Tested by me. The builds are: ocaml-4.11.1-5.el9.2 ocaml-labltk-8.06.5-25.el9 ocaml-ocamlbuild-0.14.0-27.el9 ocaml-csexp-1.3.2-6.el9 ocaml-findlib-1.8.1-28.el9 ocaml-cppo-1.6.6-15.el9 ocaml-curses-1.0.4-24.el9 ocaml-libvirt-0.6.1.5-19.el9 ocaml-calendar-2.04-40.el9 ocaml-camomile-1.0.2-19.el9 ocaml-csv-1.7-29.el9 ocaml-extlib-1.7.8-7.el9 ocaml-xml-light-2.3-0.56.svn234.el9 ocaml-fileutils-0.5.2-29.el9 ocaml-gettext-0.4.2-6.el9 ocaml-dune-2.8.5-6.el9 OSCI created separate advisories for every single one of these builds and I don't have permissions to drop them to combine the advisories into one. So here we are. I have removed the following builds from the following errata: ocaml-curses-1.0.4-24.el9 -> https://errata.devel.redhat.com/advisory/89735 ocaml-dune-2.8.5-6.el9 -> https://errata.devel.redhat.com/advisory/89736 ocaml-gettext-0.4.2-6.el9 -> https://errata.devel.redhat.com/advisory/89737 ocaml-csv-1.7-29.el9 -> https://errata.devel.redhat.com/advisory/89738 ocaml-fileutils-0.5.2-29.el9 -> https://errata.devel.redhat.com/advisory/89739 ocaml-extlib-1.7.8-7.el9 -> https://errata.devel.redhat.com/advisory/89740 ocaml-findlib-1.8.1-28.el9 -> https://errata.devel.redhat.com/advisory/89741 ocaml-csexp-1.3.2-6.el9 -> https://errata.devel.redhat.com/advisory/89742 ocaml-labltk-8.06.5-25.el9 -> https://errata.devel.redhat.com/advisory/89743 ocaml-xml-light-2.3-0.56.svn234.el9 -> https://errata.devel.redhat.com/advisory/89744 ocaml-camomile-1.0.2-19.el9 -> https://errata.devel.redhat.com/advisory/89745 ocaml-calendar-2.04-40.el9 -> https://errata.devel.redhat.com/advisory/89746 ocaml-libvirt-0.6.1.5-19.el9 -> https://errata.devel.redhat.com/advisory/89747 ocaml-cppo-1.6.6-15.el9 -> https://errata.devel.redhat.com/advisory/89748 ocaml-ocamlbuild-0.14.0-27.el9 -> https://errata.devel.redhat.com/advisory/89749 Feel free to re-add these builds to https://errata.devel.redhat.com/advisory/89734 as discussed in IRC and ping me if you run into any surprises. Thanks! I added all the builds to the super-advisory (89734). Checked the latest RHEL9.1 nightly compose: http://download.eng.pek2.redhat.com/rhel-9/nightly/RHEL-9/RHEL-9.1.0-20220329.0/compose/CRB/x86_64/os/Packages/ All ocaml* related packages except ocaml-srpm-macros have been moved to CRB, so move the bug to VERIFIED. This issue is blocking us from using RHEL9.0 as a development environment. (In reply to Jesse Brandeburg from comment #22) > This issue is blocking us from using RHEL9.0 as a development environment. Can you explain exactly what the problem is? I had been looking forward to using the new kernel and features from RHEL9.0 (and contributing feedback if I found problems) by using RHEL9.0 on a test/development platform. The issue is that we extensively use coccinelle in our driver software development (on multiple drivers), and without this coccinelle package, I'm having to roll my own (my first try resulted in a REALLY SLOW coccinelle/spatch) Coccinelle (via EPEL) works fine in fedora, and even in RHEL8.6, so when I upgraded from 8.6 to 9.0 - my development environment broke and now I'm scrambling (maybe I need a container) Unfortunately for reasons outside my control I have to wait until RHEL 9.1 GA before we can build coccinelle for EPEL. Thanks Richard, I appreciate that you've worked on this, and I read the whole series of threads, and wanted to at least mention in an appropriate forum that this particular bug hurts my use case. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (ocaml bug fix and enhancement update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:8408 |