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.
Description of problem:
there is fileconfict libevent-devel with libevent2-devel
Both package are in the 'normal' channels
Version-Release number of selected component (if applicable):
libevent-devel-1.4.13-4.el6.x86_64
libevent2-devel-2.0.21-2.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. yum install libevent-devel
2. yum install libevent2-devel
Actual results:
[0 root@qeos-24 test]# yum install libevent-devel
Loaded plugins: product-id, refresh-packagekit, search-disabled-repos, security, subscription-manager
This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package libevent-devel.x86_64 0:1.4.13-4.el6 will be installed
--> Processing Dependency: libevent-doc = 1.4.13-4.el6 for package: libevent-devel-1.4.13-4.el6.x86_64
--> Processing Dependency: libevent-headers = 1.4.13-4.el6 for package: libevent-devel-1.4.13-4.el6.x86_64
--> Running transaction check
---> Package libevent-doc.noarch 0:1.4.13-4.el6 will be installed
---> Package libevent-headers.noarch 0:1.4.13-4.el6 will be installed
--> Processing Conflict: libevent2-devel-2.0.21-2.el6.x86_64 conflicts libevent-devel
--> Finished Dependency Resolution
Error: libevent2-devel conflicts with libevent-devel-1.4.13-4.el6.x86_64
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Expected results:
there is no conflict
Additional info:
it was the same issue like in the extras channel, but now there is libevent2 in the 'normal' channel
https://bugzilla.redhat.com/show_bug.cgi?id=1261401#c6
Quick check revealed that this package is available just in optional repo/channel (please correct me if I'm wrong). There's some special handling of conflicting packages in 'standard' repo in certain cases (however covered by release engineering & conflicting packages are not prohibited by any means).
From distribution point of view this does not seem to violate anything.
Hi folks, what's the expected behavior when it comes to installing libevent / libevent2 at the same host. Shouldn't libevent2 obsolete libevent?
Shouldn't be a conflict ... and if so ... we need to put them into conflict groups in comps.
Lubos
libevent2 should not obsolete libevent. The choice was made not to cause potential problems in applications that would get switched from libevent1 to libevent2.
Since they do have same named header files, these devek packages cannot be both installed. This is similar to openssl vs openssl099 or bind vs bind9xxx.
That's why I think this is not a problem.
(In reply to Paul Wouters from comment #6)
> libevent2 should not obsolete libevent. The choice was made not to cause
> potential problems in applications that would get switched from libevent1 to
> libevent2.
>
> Since they do have same named header files, these devek packages cannot be
> both installed. This is similar to openssl vs openssl099 or bind vs bind9xxx.
>
> That's why I think this is not a problem.
+1