Bug 20562

Summary:	Installation failed: file /usr/lib/libz.so.1 from install of libzlib1-1.2.11-2.mga6.i586 conflicts with file from package lib64zlib1-1.2.8-7.1.mga5.x86_64
Product:	Mageia	Reporter:	PC LX <mageia>
Component:	RPM Packages	Assignee:	Shlomi Fish <shlomif>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	release_blocker	CC:	cae, mageia, marja11, pkg-bugs
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	zlib-1.2.11-2.mga6.i586	CVE:
Status comment:

Description PC LX 2017-03-23 21:08:12 CET

Description of problem:

When upgrading Mageia 5 to Mageia 6 cauldron I see the following error message:
Installation failed: file /usr/lib/libz.so.1 from install of libzlib1-1.2.11-2.mga6.i586 conflicts with file from package lib64zlib1-1.2.8-7.1.mga5.x86_64



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

libzlib1-1.2.11-2.mga6.i586
lib64zlib1-1.2.8-7.1.mga5.x86_64



How reproducible:

Always.



Steps to Reproduce:
1. Start with a Mageia 5 system.
2. Remove the Mageia 5 repositories.
3. Add the Mageia 6 (cauldron) repositories with the command:
   urpmi.addmedia --urpmi-root "$ROOT_CAULDRON" --distrib 'http://ftp.free.fr/mirrors/mageia.org/distrib/cauldron/x86_64/'
4. Up date the system with "urpmi --auto-update".

Comment 1 Rémi Verschelde 2017-03-23 21:36:56 CET

Sounds like zlib was badly libified in Mageia 5 (lib64 package with stuff in /usr/lib), it should be fixed with proper Conflicts.

Assignee: bugsquad => shlomif

Comment 2 Charles Edwards 2017-03-23 22:24:18 CET

(In reply to Rémi Verschelde from comment #1)
> Sounds like zlib was badly libified in Mageia 5 (lib64 package with stuff in
> /usr/lib), it should be fixed with proper Conflicts.

Up until latest release 1.2.11-2 zlib on x86_64 was built as biarch

%ifarch sparcv9 sparc64 x86_64 ppc64
%define build_biarch 1

and file list

%files -n %{lib_name}
%doc README
%{_libdir}/libz.so.%{lib_major}*
%if %{build_biarch}
%{_prefix}/lib/libz.so.%{lib_major}*
%endif

The spec for the 'new' build was does not consider this and does not contain
any addional|adjusted Obsoletes or Conflicts.

CC: (none) => cae

Comment 3 PC LX 2017-03-28 19:24:48 CEST

Did another Mageia 5 to Mageia 6 cauldron upgrade and this issue seems to be resolved. Both 32 and 64 bit zlib packages installed without any issues. Marking this as resolved.

# rpm -q lib64zlib1 libzlib1
lib64zlib1-1.2.11-2.mga6
libzlib1-1.2.11-2.mga6

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 4 Rémi Verschelde 2017-03-28 23:40:51 CEST

Reopening for now as I saw the issue yesterday, and AFAIK no fix has been done in the zlib packaging, so it might be by chance that it worked properly for PC LX in comment 3. Packagers will need to make sure that conflicts are properly handled.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 5 Marja Van Waes 2017-03-29 06:56:38 CEST

@ Shlomi

If you don't consider yourself to be the zlib maintainer, then please unset yourself as maintainer and reassign this bug report.

However, if you really are the maintainer, then please look into this bug, or, if you can't, set the NEEDHELP keyword.

Thanks,
Marja

Priority: Normal => release_blocker
CC: (none) => marja11, pkg-bugs
Source RPM: libzlib1-1.2.11-2.mga6.i586 => zlib-1.2.11-2.mga6.i586

Comment 6 Nicolas Lécureuil 2017-03-29 09:08:25 CEST

fixed on svn.

Status: REOPENED => RESOLVED
CC: (none) => mageia
Resolution: (none) => FIXED

Comment 7 Rémi Verschelde 2017-03-29 09:23:50 CEST

I don't think the fix is sufficient: http://svnweb.mageia.org/packages/cauldron/zlib/current/SPECS/zlib.spec?r1=1095142&r2=1095141&pathrev=1095142

Here the conflict is:
file /usr/lib/libz.so.1 from install of libzlib1-1.2.11-2.mga6.i586 conflicts with file from package lib64zlib1-1.2.8-7.1.mga5.x86_64

So libzlib1 (32-bit, mga6) should conflict lib64zlib1 < 1.2.9 (64-bit, mga5). The fix you pushed only makes libzlib1 conflict libzlib1, not lib64zlib1.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 8 Nicolas Lécureuil 2017-03-29 10:30:49 CEST

fixed your way then ;)

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED