Red Hat Bugzilla – Bug 1301884
libevent2-devel conflicts with libevent-devel
Last modified: 2017-02-19 19:13:19 EST
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):
Steps to Reproduce:
1. yum install libevent-devel
2. yum install libevent2-devel
[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
--> 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
there is no conflict
it was the same issue like in the extras channel, but now there is libevent2 in the 'normal' channel
yes. they are conflicting because both devel packages cannot be installed at the same time.
Why is that a bug?
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.
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
> 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.