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 1349281 - Fix `Conflicts` with ipa-python
Summary: Fix `Conflicts` with ipa-python
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: IPA Maintainers
QA Contact: Kaleem
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-23 06:57 UTC by Jan Cholasta
Modified: 2016-11-04 05:55 UTC (History)
5 users (show)

Fixed In Version: ipa-4.4.0-1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-04 05:55:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2404 0 normal SHIPPED_LIVE ipa bug fix and enhancement update 2016-11-03 13:56:18 UTC

Description Jan Cholasta 2016-06-23 06:57:44 UTC
Description of problem:

Currently, we have the following Conflicts line in ipa-common and python-ipalib:

  Conflicts: %{name}-python < %{version}-%{release}

But rpmdiff does not like it:

  changed from Conflicts: ipa-python < 4.4.0-0.el7.1.alpha1 to Conflicts: ipa-python < 4.4.0-0.el7.2.alpha1 on noarch

To fix this, the conflicting version should be changed to < 4.2.91, i.e. to before ipa-python was split into ipa-common and python-ipalib.


Version-Release number of selected component (if applicable):
ipa-4.4.0-0.el7.2.alpha1

How reproducible:
Always.

Steps to Reproduce:
1.
2.
3.

Actual results:
rpmdiff complains

Expected results:
rpmdiff does not complain

Additional info:

Comment 1 Petr Vobornik 2016-06-28 07:38:22 UTC
Upstream ticket:
https://fedorahosted.org/freeipa/ticket/6004

Comment 2 Martin Bašti 2016-06-30 13:46:15 UTC
Fixed upstream
master:
https://fedorahosted.org/freeipa/changeset/669da991837267435a6e6563794f93c2f207c80b

Comment 6 Abhijeet Kasurde 2016-09-15 05:57:16 UTC
Verified using IPA server version::
ipa-server-4.4.0-11.el7.x86_64

[root@ipamaster1 /]# rpm -q --conflicts ipa-common 
ipa-python < 4.2.91
freeipa-common
freeipa-python < 4.4.0
[root@ipamaster1 /]# rpm -q --conflicts python2-ipalib 
ipa-python < 4.2.91
freeipa-python < 4.4.0
[root@ipamaster1 /]# rpm -q ipa-server
ipa-server-4.4.0-11.el7.x86_64

Comment 8 errata-xmlrpc 2016-11-04 05:55:27 UTC
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://rhn.redhat.com/errata/RHBA-2016-2404.html


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