Bug 19595 - package conflict 32/64 bit libopenssl when updating to version 1.0.2j-1.mga6
Summary: package conflict 32/64 bit libopenssl when updating to version 1.0.2j-1.mga6
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-16 09:58 CEST by Jan Smout
Modified: 2016-10-16 19:11 CEST (History)
7 users (show)

See Also:
Source RPM: openssl-1.0.2j-1.mga6
CVE:
Status comment:


Attachments
Conflict 32 - 64 bit openssl (3.55 KB, text/plain)
2016-10-16 09:58 CEST, Jan Smout
Details

Description Jan Smout 2016-10-16 09:58:50 CEST
Created attachment 8546 [details]
Conflict 32 - 64 bit openssl

64-bit install with 32-bit libraries.

libopenssl won't upgrade because of conflicting files


Details are given in attachment
Comment 1 Marja Van Waes 2016-10-16 12:06:01 CEST
I see you have both arches installed:

libopenssl-devel-1.0.2h-1.mga5.i586
lib64openssl-devel-1.0.2h-1.mga5.x86_64

AFAIK, upgrading in such cases is not supported.

Assigning to all packagers collectively (openssl has no registered maintainer), to decide what to do with this report.

CC: (none) => fundawang, guillomovitch, luigiwalser, mageia, marja11, pterjan, tmb
Assignee: bugsquad => pkg-bugs
Summary: package conflict 32/64 bit libopenssl => package conflict 32/64 bit libopenssl when updating to version 1.0.2j-1.mga6
Source RPM: (none) => openssl-1.0.2j-1.mga6

Comment 2 Jan Smout 2016-10-16 12:49:44 CEST
*upgrading* --> that gave me a clue

Strange bug:

Removing libopenssl-devel-1.0.2h-1.mga5 + upgrading + re-adding libopenssl-devel-1.0.2j-1.mga5 works. But direct upgrade does not...


Seems like an issue with urpmi?
Comment 3 Guillaume Rousse 2016-10-16 16:10:34 CEST
That's a file conflict between packages. Given enough metadata (ie, explicit conflict declared in packages), urpmi could foresee it, and either abort the operation, either handle it differently, as you did manually. However, this would require a lot of work to first identify those conflict between packages of different architectures and different versions, then to declare them, for very few benefit. Documenting the issue seems an easier workaround.
Comment 4 Jan Smout 2016-10-16 17:42:35 CEST
I guess not too many people will encounter this. Documenting is good enough for me
Comment 5 David Walser 2016-10-16 19:11:25 CEST
Indeed, not supported.  Just uninstall libopenssl-devel.

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


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