incompatible with the compat lib.
Mon Jun 14 2010 Stephen Gallagher firstname.lastname@example.org - 2.0.1-7
This update has been submitted for testing.
This update has been pushed to testing
Conflicting with samba3x is NOT the correct solution. Because now, a "yum
install samba3x" fails with "libtalloc-2.0.1-3.el5.x86_64 from epel-testing has
depsolving problems: libtalloc conflicts with samba3x-common" - because of
"Processing Dependency: libtalloc.so.1()(64bit) for package: samba3x"
From my point of view you are simply not allowed to provide a library having the
same soname and same soversion as RHEL 5 does - this violates the EPEL policy
right now, because we conflict with RHEL as our upstream.
There are no correct solutions at the moment for this issue. It's being resolved
for RHEL 5.6 with the samba packaging team. This is an attempt to minimize the
exposure of this conflict until that time.
The problem is that EPEL had libtalloc 2 during the RHEL 5.4 days, but RHEL 5.5
shipped with an incompatible library. Because some users already had libtalloc 2
(mostly for SSSD) we can't just drop it from EPEL. So we need to resolve this as
best we can.
Waiting until RHEL 5.6 is not a solution. EPEL is not allowed to break RHEL.
As I stated above. EPEL did not break RHEL. RHEL broke EPEL, and the higher
priority for EPEL is to not terminate support arbitrarily. The real problem here
is that RHEL5.5 shipped AFTER libtalloc 2.0 was available in EPEL, and they
shipped with an unsupported, forked version of the library, with the same
soname. RHEL is being the bad citizen here.
The update seems to work - at least no failures during the whole day here.
Works for me.
This update has been submitted for stable.
This update has been pushed to stable
Please login to add feedback.
Confirm request to re-trigger tests.
Copyright © 2007-2022 Red Hat, Inc. and
bodhi-server 6.0.1 on
bodhi is Free Software.
if you have any problems. Read the documentation.