| Summary: | package conflict 32/64 bit libopenssl when updating to version 1.0.2j-1.mga6 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jan Smout <smout.jan> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | fundawang, guillomovitch, luigiwalser, mageia, marja11, pterjan, tmb |
| Version: | 5 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | openssl-1.0.2j-1.mga6 | CVE: | |
| Status comment: | |||
| Attachments: | Conflict 32 - 64 bit openssl | ||
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 *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? 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. I guess not too many people will encounter this. Documenting is good enough for me Indeed, not supported. Just uninstall libopenssl-devel. Status:
NEW =>
RESOLVED |
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