| Summary: | gcr4 - unable to update system via urpmi: file /usr/libexec/gcr4-ssh-askpass from install of gcr4-3.90.0-2.mga9.x86_64 conflicts with file from package gcr-3.90.0-1.mga9.x86_64 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Edward <epp> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | lewyssmith |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | gcr-3.41.0-2.mga9.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Edward
2022-07-13 21:41:13 CEST
The gcr Source RPM provided came from the Mageia App Db, even though the version number is different. 'gcr4' was not found in the App Db. I attempted to update my other Cauldron install (different desktop environment) and received the same error as above. You got already some explanations regarding obsoletes/file conflicts on dev ML. Also regarding fast changing package versions which could lead to not completely synced mirrors and some file conflicts because some deps are still building. It's absolutely normal and expected that stuff like this happens on cauldron. As cauldron user you should be able to try some stuff yourself. Did you try to remove gcr-3.90.0-1.mga9.x86_64 yourself? Also our MADB can't keep the speed of our build systems regarding version numbers for cauldron. gcr4 left our build cluster 5 hours ago, so our MADB didn't pick up this new version yet... Upon attempting to remove gcr: Because of their dependencies, the following package(s) also need to be removed: - abiword-3.0.5-3.mga9.x86_64 - evolution-data-server-3.44.3-1.mga9.x86_64 - evolution-data-server-tests-3.44.3-1.mga9.x86_64 - gnome-keyring-42.1-1.mga9.x86_64 - lib64camel1.2_62-3.38.3-2.mga8.x86_64 - lib64camel1.2_63-3.44.3-1.mga9.x86_64 - lib64ebackend1.2_10-3.44.3-1.mga9.x86_64 - lib64ebook-contacts1.2_3-3.44.3-1.mga9.x86_64 - lib64ebook1.2_20-3.44.3-1.mga9.x86_64 - lib64ecal2.0_1-3.44.3-1.mga9.x86_64 - lib64edata-book1.2_26-3.44.3-1.mga9.x86_64 - lib64edata-cal1.2_1-3.44.3-1.mga9.x86_64 - lib64edataserver1.2_25-3.38.3-2.mga8.x86_64 - lib64edataserver1.2_26-3.44.3-1.mga9.x86_64 - lib64edataserverui1.2_2-3.38.3-2.mga8.x86_64 - lib64edataserverui1.2_3-3.44.3-1.mga9.x86_64 - lib64gcr4_0-3.90.0-1.mga9.x86_64 - lib64gnome-keyring-42.1-1.mga9.x86_64 0B of additional disk space will be used. Should I wait until tomorrow and try to update again?? Please do. This SRPM is currently very active in Cauldron. Version 3.90.0 was reverted to 3.41.0. If the conflict remains, this should go to wally, CC ovitters. CC:
(none) =>
lewyssmith There is only a major version change ongoing. We have actual two versions in cauldron: gcr-3.41.0-2.mga9.x86_64.rpm gcr4-3.90.0-2.mga9.x86_64.rpm Per an e-mail in dev, downgrading gcr, then removing gcr4, cleared this up and I was able to fully update again. Thank you. Closing as FIXED then... Status:
NEW =>
RESOLVED |