Bug 2122159
| Summary: | xmlstarlet missing in CentOS Stream 8 | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Vasishta <vashastr> |
| Component: | xmlstarlet | Assignee: | Johnny Hughes <jhughes> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | CS System Management SST QE <rhel-cs-system-management-subsystem-qe> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | CentOS Stream | CC: | adeza, andreas.harder, bhubbard, bstinson, carl, christian.grundmann, daltonminer, davide, dmarshal, epel-packagers-sig, extras-qa, ghenadii.batalski, guenther.reim, jhughes, jwboyer, kdreyer, michel, ngompa13, olivier.lahaye1, skimeer, stickster, tdawson, thomas.moschny, vcrhonek |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1757000 | Environment: | |
| Last Closed: | 2022-10-26 22:27:10 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
Vasishta
2022-08-29 11:25:14 UTC
Looks like this package is being removed from EPEL because it's getting added to RHEL proper: https://bugzilla.redhat.com/show_bug.cgi?id=2072386 Yikes. What a mess. Most Ceph upstream CI runs are failing because the package was removed prematurely... https://bugzilla.redhat.com/show_bug.cgi?id=2114762 indicates this package is going into RHEL 8.6. Paul, when can we expect this package in CentOS 8 Stream? We build Ceph a lot upstream, and this package retirement has broken our CI. Looks like there was some confusion on the xmlstarlet retirement. It is being added to both RHEL 8.6 (bug 2114762) and RHEL 8.7 (bug 1882020). Our EPEL2RHEL automation opened two corresponding bugs for the EPEL 8 retirement (bug 2118244 and bug 2072386). This is a bit confusing, as there is only one EPEL 8. The maintainer already retired the EPEL 8 package, but xmlstarlet is not yet available in RHEL 8 or CentOS Stream 8 (C8S). We are looking at adjusting the automated bug text to be more clear about waiting until after the package is available in RHEL to retire the EPEL package. I think we'll need to think through a bit how to handle this situation like this where a package is being added to the current RHEL release and the upcoming one. This package was also retired in EPEL 9 (bug 2084488) because it's coming to RHEL 9.1 (bug 2069689). Ideally that also should have waited until it was available in RHEL 9. At least in that case the package is already available in C9S. That's because the RHEL maintainers are in charge of their builds there. We keep getting bit by the fact that C8S is still technically a rebuild, it's just rebuilt from a different branch. xmlstarlet is already available in the RHEL 8.7 nightly composes (not public), and was exported to git.centos.org to be built in C8S. The problem is it is still a manual process to build and ship new packages in C8S. I've built xmlstarlet-1.6.1-20.el8 for C8S, and it should be included in the next C8S compose. If anyone needs the package faster than that, you can download the RPM from the koji build. https://koji.mbox.centos.org/koji/buildinfo?buildID=22657 Thanks Carl. What ticket tracks the work to update that EPEL2RHEL text? Seeing this bug now. Ironically, if I'd just continued in not seeing BZ email this probably would have worked out without me. @carl thanks for finding a solution. Please let me know if I need to take further action to help unmess things. Hi Ken, The EPEL2RHEL program is not part of EPEL, it is part of the RHEL Workflow. Any change, even re-wording of the bug subject and comments, will take between 3 to 6 months. So I want to make sure we get the wording right before starting another ticket for it. We (the EPEL Steering Committee) might even want to change the workflow. Possibly have it only create the bugs on the tracker, and not for the individual packages so things like this do not happen again. I expect the task to update EPEL2RHEL be created next week, but I don't expect change to happen for several months. Again, I'm sorry that the original wording caused this situation. We'll try to make sure this doesn't happen again. That's ok. When should we expect the xmlstarlet-1.6.1-20.el8 c8s build to be on the CentOS 8 Stream mirrors? Looks like it's there now. [root@c8s-container:~]# dnf list --available xmlstarlet Last metadata expiration check: 0:04:09 ago on Fri Sep 2 16:33:00 2022. Available Packages xmlstarlet.x86_64 1.6.1-20.el8 powertools http://mirror.centos.org/centos/8-stream/PowerTools/x86_64/os/Packages/xmlstarlet-1.6.1-20.el8.x86_64.rpm If you aren't seeing you may be hitting a stale mirror. I spot checked a few mirrors and they had synced it already. Sorry, maybe I'm confused now, but what is the solution for people using 8.6 (rhel or rebuilds)? IIUC, the package is in stream now, and will be in 8.7, but that leaves a gap in 8.6. It is also being added to RHEL 8.6, as I stated in comment 4. I don't know when that will be complete, but I expect it will happen before RHEL 8.7 is released. If you can't wait, you can install the CentOS build [0] or the archived EPEL build [1]. These should be functionally identical. [0] http://mirror.centos.org/centos/8-stream/PowerTools/x86_64/os/Packages/xmlstarlet-1.6.1-20.el8.x86_64.rpm [1] https://dl.fedoraproject.org/pub/archive/epel/8.5.2022-05-10/Everything/x86_64/Packages/x/xmlstarlet-1.6.1-11.el8.x86_64.rpm Since this bug is for CentOS Stream 8, and xmlstarlet is available there, I'm closing this bug. It also is available in RHEL 8.6 now, for those following this bug that can't view bug 2114762 because it's private. https://access.redhat.com/errata/RHBA-2022:7118 |