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.
Bug 1693212 - Reinstall with --replacepkgs fails on packages with self-conflicts
Summary: Reinstall with --replacepkgs fails on packages with self-conflicts
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: rpm
Version: 8.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 8.0
Assignee: Packaging Maintenance Team
QA Contact: Luca Berton
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-27 11:16 UTC by Panu Matilainen
Modified: 2020-06-18 10:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-18 10:33:21 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Reproducer spec (222 bytes, text/plain)
2019-03-27 11:16 UTC, Panu Matilainen
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1564747 0 high CLOSED freeipa-client-common conflicts with ipa-client-common-4.5.0-22.el7.centos.noarch 2024-03-25 15:03:43 UTC

Internal Links: 1564747

Description Panu Matilainen 2019-03-27 11:16:18 UTC
Created attachment 1548507 [details]
Reproducer spec

Description of problem:

Rpm has permitted self-conflicts in packages since version 4.9, but attempting to reinstall such packages with -i --replacepkgs (which yum 3.x uses for the purpose) fails with dependency errors.

Version-Release number of selected component (if applicable):

All current rpm versions (4.9 - 4.14/upstream)

How reproducible:
Always

Steps to Reproduce:
1. rpmbuild -bb self-conflict.spec (see attachment)
2. rpm -i self-conflict-2.0-1.noarch.rpm
3. rpm -i --replacepkgs self-conflict-2.0-1.noarch.rpm

Actual results:
error: Failed dependencies:
	blech conflicts with self-conflict-2.0-1.noarch
	blech conflicts with (installed) self-conflict-2.0-1.noarch

Expected results:
Step 3. succeeds silently

Additional info:
This is is a relatively rare issue, it took eight years for anybody to discover and would be low priority/severity but as this is getting fixed in rhel-7 (via workaround in yum, see bug 1564747) we need it fixed in rhel-8 to avoid creating a regression.

Comment 1 Panu Matilainen 2019-08-30 08:16:10 UTC
For the record, there's now a partial fix for this case now at upstream - it doesn't help with -i --replacepkgs but it does fix the more "common" -U --replacepkgs: https://github.com/rpm-software-management/rpm/pull/770

Comment 5 Panu Matilainen 2020-06-18 10:33:21 UTC
As there's no real pressure to get this fixed, lets just defer it to some possible future date.

The case of installing/upgrading with -U is fixed upstream and Fedora, but backport is on the scary side, and for -i there is no solution which would not involve breaking longstanding rpm principles.


Note You need to log in before you can comment on or make changes to this bug.