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.
The issue is a limitation of yum-4 and it cannot be resolved during RHEL8 life-cycle, because it would introduce incompatibility changes in API (It requires new workfows).
To resolve the issue I would recommend to use all local files as a arguments in the first line:
1. install /root/nano-2.9.8-1.el8.x86_64.rpm /root/mc-4.8.19-9.el8.x86_64.rpm
2. run
Is my suggested work-around suitable for the customer?
I am really sorry, but there is a misunderstanding. You can still do multiple requests with yum shell in any order that you wish, but with one exception. Install or upgrade of local packages is limited. You can do:
1. install /root/nano-2.9.8-1.el8.x86_64.rpm /root/mc-4.8.19-9.el8.x86_64.rpm
2. remove <pkg>
3. install <another_package>
4. run
I can enhance the documentation to describe the limitation. Also I can add a warning when local packages will be added after other transaction item is already in place.
I know that this is not nice, but that nearly all what I can do without a huge redesign of DNF. In long term plan we would like to resolve the issue completely, but redesign will be accompanied with API changes that will be difficult to delivery into RHEL8.
What do you think?
I create a patch (https://github.com/rpm-software-management/dnf/pull/1546) that enhance documentation and add an error visible in `yum shell`:
sudo dnf shell
Last metadata expiration check: 2:10:58 ago on Wed 04 Dec 2019 11:41:44 AM CET.
> install /home/jmracek/acpi-1.7-11.fc30.x86_64.rpm
> install /home/jmracek/acpi-1.7-11.fc30.x86_64.rpm
Error: Cannot add local packages, because transaction job already exists
> run # only the first request is performed
Is it OK?
Comment 6Parikshit Khedekar
2019-12-04 14:20:54 UTC
Perfect! Customer agreed on these facts as well.
Can be closed, thank you.
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, 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-2020:1823