Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#46098 - Conflict between files owned by marble-data and subsurface-marble
Attached to Project:
Arch Linux
Opened by Samuel Gilbert (Prozzaks) - Monday, 24 August 2015, 22:03 GMT
Last edited by Gaetan Bisson (vesath) - Tuesday, 25 August 2015, 01:37 GMT
Opened by Samuel Gilbert (Prozzaks) - Monday, 24 August 2015, 22:03 GMT
Last edited by Gaetan Bisson (vesath) - Tuesday, 25 August 2015, 01:37 GMT
|
DetailsDescription:
When updating my system (sudo pacman -Suy), the operation got interrupted with the message "error: failed to commit transaction (conflicting files)" fallowed with a very long list of files and folders under /usr/share/marble/ Running "pacman -Qo" on some of the conflicting files reveals that they are currently owned by : subsurface-marble 4.4.1-1 It looks like extra/marble-data 15.08.0-2 also owns those files. For the time being, I worked around the problem by issuing the following commands : sudo pacman -Sdd --force extra/marble-data sudo pacman -Su I'm assuming that the resources files are similar enough to work for both packages. |
This task depends upon
Closed by Gaetan Bisson (vesath)
Tuesday, 25 August 2015, 01:37 GMT
Reason for closing: Fixed
Additional comments about closing: subsurface-marble-4.4.1-2 in [community]
Tuesday, 25 August 2015, 01:37 GMT
Reason for closing: Fixed
Additional comments about closing: subsurface-marble-4.4.1-2 in [community]
1) Make subsurface-marble provide and conflict with marble-data
2) Strip the data files from subsurface-marble and make it depend on marble-data
The second one seems cleaner to me