Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
1. Proposed title of this feature request
Add ability to yum-groups-manager to identify packages with version and/or architecture specified in package name
2. What is the nature and description of the request?
Prior to RHEL 8, yum-groups-manager was able to identify packages with version and/or architecture specified in package name and add them in comps.xml file, But from RHEL 8 it appears that yum-groups-manager i.e. dnf groups-manager only allow packages having package name without version and architecture. And for packages with version and/or architecture specified in name yum-groups-manager gives No match for argument error.
# dnf groups-manager -n test --print bash-4.4.20-1.el8_4.x86_64
No match for argument: bash-4.4.20-1.el8_4.x86_64
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE comps PUBLIC "-//Red Hat, Inc.//DTD Comps info//EN" "comps.dtd">
<comps>
<group>
<id>test</id>
<name>test</name>
<default>false</default>
<uservisible>true</uservisible>
</group>
</comps>
3. Why does the customer need this? (List the business requirements here)
We need this ability for yum-groups-manager (dnf groups-manager) to be able to identify packages with version and/or architecture specified in name
4. How would the customer like to achieve this? (List the functional requirements here)
Like in RHEL 7, same command should give exactly the same result on RHEL 8 i.e. creation of comps.xml file with all packages given as argument to command even though some packages might have version and/or architecture specified in name.
5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
To test, you can take any packages with version and/or architecture specified in name. For example even with the version/arch attached, we see that "bash" is now in the group file.
# dnf groups-manager -n test --print bash-4.4.20-1.el8_4.x86_64
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE comps PUBLIC "-//Red Hat, Inc.//DTD Comps info//EN" "comps.dtd">
<comps>
<group>
<id>test</id>
<name>test</name>
<default>false</default>
<uservisible>true</uservisible>
<packagelist>
<packagereq type="default" requires="">bash</packagereq> <<<<<<<<<
</packagelist>
</group>
</comps>
6. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?
RHEL 8
7. List any affected packages or components.
dnf groups-manager
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 (dnf-plugins-core 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:2052
1. Proposed title of this feature request Add ability to yum-groups-manager to identify packages with version and/or architecture specified in package name 2. What is the nature and description of the request? Prior to RHEL 8, yum-groups-manager was able to identify packages with version and/or architecture specified in package name and add them in comps.xml file, But from RHEL 8 it appears that yum-groups-manager i.e. dnf groups-manager only allow packages having package name without version and architecture. And for packages with version and/or architecture specified in name yum-groups-manager gives No match for argument error. # dnf groups-manager -n test --print bash-4.4.20-1.el8_4.x86_64 No match for argument: bash-4.4.20-1.el8_4.x86_64 <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE comps PUBLIC "-//Red Hat, Inc.//DTD Comps info//EN" "comps.dtd"> <comps> <group> <id>test</id> <name>test</name> <default>false</default> <uservisible>true</uservisible> </group> </comps> 3. Why does the customer need this? (List the business requirements here) We need this ability for yum-groups-manager (dnf groups-manager) to be able to identify packages with version and/or architecture specified in name 4. How would the customer like to achieve this? (List the functional requirements here) Like in RHEL 7, same command should give exactly the same result on RHEL 8 i.e. creation of comps.xml file with all packages given as argument to command even though some packages might have version and/or architecture specified in name. 5. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented. To test, you can take any packages with version and/or architecture specified in name. For example even with the version/arch attached, we see that "bash" is now in the group file. # dnf groups-manager -n test --print bash-4.4.20-1.el8_4.x86_64 <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE comps PUBLIC "-//Red Hat, Inc.//DTD Comps info//EN" "comps.dtd"> <comps> <group> <id>test</id> <name>test</name> <default>false</default> <uservisible>true</uservisible> <packagelist> <packagereq type="default" requires="">bash</packagereq> <<<<<<<<< </packagelist> </group> </comps> 6. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)? RHEL 8 7. List any affected packages or components. dnf groups-manager