Bug 1474107
Summary: | Conflicts between i686 and x86_64 packages | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | srakitnican <samuel.rakitnican> |
Component: | mono | Assignee: | Xavier Lamien <lxtnow> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 28 | CC: | chkr, claudiorodrigo, itamar, lxtnow, paul, pokorra.mailinglists, zboszor |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-05-28 20:05:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
srakitnican
2017-07-23 23:12:05 UTC
I checked how it worked on Fedora 25: rpm -ql mono-core | grep mscorlib /usr/lib/mono/4.5/mscorlib.dll /usr/lib/mono/4.5/mscorlib.dll.mdb /usr/lib/mono/4.5/mscorlib.dll /usr/lib/mono/4.5/mscorlib.dll.mdb rpm -qf /usr/lib/mono/4.5/mscorlib.dll mono-core-4.4.2-1.fc25.x86_64 mono-core-4.4.2-1.fc25.i686 If I remove one package: dnf remove mono-core.i686 the file /usr/lib/mono/4.5/mscorlib.dll is still there. Ok, here is a hint: https://bugzilla.redhat.com/show_bug.cgi?id=1326157#c8 "they contain the same .mo files which is not a problem if you install the same version of x86_64 and i686 package (because the files are identical - have the same chackusum). If versions differ so do files (because they contain at least different timestamps) and it (must) generates file conflict." So it seems, in Mono 4.8 the file mscorlib.dll is compiled differently for 32 and for 64 bit, and therefore cannot be installed in parallel anymore. I don't know if and how that can be solved. Any ideas? Do we need to use /usr/lib64 etc? But that would mean quite a lot of change. Are there any other ways you could workaround this issue? Perhaps using linux containers to install the two packages seperately? (In reply to Timotheus Pokorra from comment #1) > Are there any other ways you could workaround this issue? Perhaps using > linux containers to install the two packages seperately? I am not using it, so I am not having any issues with it personally, thus I am not the right person to answer that. Just reporting the issue. This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. This still occurs on Fedora 28. Error: Transaction check error: file /usr/lib/mono/4.5/mscorlib.dll conflicts between attempted installs of mono-core-4.8.0-12.fc28.x86_64 and mono-core-4.8.0-12.fc28.i686 This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |