Bug 1869037
| Summary: | Conflict between chromium from Fedora and a later chromium-freeworld from rpmfusion | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | stan <gryt2> |
| Component: | chromium | Assignee: | Tom "spot" Callaway <spotrh> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 31 | CC: | gryt2, joukj, kwizart, mszpak, spotrh, tpopela, yaneti |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | chromium-85.0.4183.83-1.fc32 chromium-85.0.4183.83-1.fc31 chromium-85.0.4183.83-1.fc33 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-09-11 15:14:26 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
stan
2020-08-15 17:51:13 UTC
The conflict should go away when the .125 update lands, however, you should not need both chromium and chromium-freeworld installed, the latter is sufficient. Thanks! FEDORA-2020-a1f140614b has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-a1f140614b FEDORA-2020-6da740d38c has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-6da740d38c FEDORA-2020-88bf0a76d1 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-88bf0a76d1 FEDORA-2020-88bf0a76d1 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-88bf0a76d1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-88bf0a76d1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-a1f140614b has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-a1f140614b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-a1f140614b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-6da740d38c has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-6da740d38c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6da740d38c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2020-a1f140614b has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report. (In reply to Tom "spot" Callaway from comment #1) > The conflict should go away when the .125 update lands, however, you should > not need both chromium and chromium-freeworld installed, the latter is > sufficient. Maybe adding Conflicts: chhromium-freeworld would solve it Error: Transaction test error: file /usr/lib/.build-id/7f/190bb3947b233b057b0dc95646a47b4c4cd200 from install of chromium-85.0.4183.83-1.fc33.x86_64 conflicts with file from package chromium-freeworld-85.0.4183.83-2.fc33.x86_64 file /usr/lib/.build-id/bd/a9f265da028283bc497eab9de14e0341d7afaa from install of chromium-85.0.4183.83-1.fc33.x86_64 conflicts with file from package chromium-freeworld-85.0.4183.83-2.fc33.x86_64 file /usr/lib/.build-id/d2/6977040b38ba3575294e56f49819d848cb60b6 from install of chromium-85.0.4183.83-1.fc33.x86_64 conflicts with file from package chromium-freeworld-85.0.4183.83-2.fc33.x86_64 I'm not sure about the reason of such a conflict ? I expect that something is not built from source whereas propagated to end-users in both build processes. Specially I don't expect buildId hash collision here... FEDORA-2020-88bf0a76d1 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report. Unfortunately, it still doesn't work for me with chromium-85.0.4183.83-1.fc32.x86_64 and chromium-freeworld-85.0.4183.83-2.fc32.
> Error: Transaction test error:
> file /usr/lib/.build-id/61/91aba223f60784c4a2fb95cdedcedc97217e5b from install of chromium-freeworld-85.0.4183.83-2.fc32.x86_64 conflicts with file from package chromium-85.0.4183.83-1.fc32.x86_64
> file /usr/lib/.build-id/82/5827dc3adff19282b7b337b044b381e2f226ee from install of chromium-freeworld-85.0.4183.83-2.fc32.x86_64 conflicts with file from package chromium-85.0.4183.83-1.fc32.x86_64
> file /usr/lib/.build-id/cc/2a382a1ab1ec74354adf012ad958a17f880f88 from install of chromium-freeworld-85.0.4183.83-2.fc32.x86_64 conflicts with file from package chromium-85.0.4183.83-1.fc32.x86_64
I don't know why there is a build-id collision, but it seems to me that the most correct solution is for chromium-freeworld to Obsolete: chromium. I'd suggest opening a ticket in the rpmfusion bugzilla to this effect. Alternately, if there is a use-case for them to live simultaneously, I would accept a PR to make that possible. > but it seems to me that the most correct solution is for chromium-freeworld to Obsolete: chromium Due to that error I've switched recently to chromium-freeworld, but due to https://bugzilla.rpmfusion.org/show_bug.cgi?id=5758 (from Google Meet screen sharing) there are cases when it would be good to have them both installed simultaneously. Maybe there will be some idea on the rpmfusion side: https://bugzilla.rpmfusion.org/show_bug.cgi?id=5743 FEDORA-2020-6da740d38c has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report. |