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#46054 - [kdepimlibs(4)]: file conflicts
Attached to Project:
Arch Linux
Opened by Jens Adam (byte) - Friday, 21 August 2015, 10:22 GMT
Last edited by Antonio Rojas (arojas) - Friday, 21 August 2015, 11:58 GMT
Opened by Jens Adam (byte) - Friday, 21 August 2015, 10:22 GMT
Last edited by Antonio Rojas (arojas) - Friday, 21 August 2015, 11:58 GMT
|
Detailsprerequisites:
i686, testing, no external repos, almost complete KDE install, migrated as much as possible to KF5 steps: -Syu, followed by pacman -S kdepim not long after conflicts: /usr/share/mime/packages/kdepimlibs-mime.xml (akonadi-mime vs. kdepimlibs4) /usr/share/mime/packages/x-vnd.akonadi.socialfeeditem.xml (akonadi-socialutils vs. kdepimlibs4) see also: https://bugs.archlinux.org/task/45817 |
This task depends upon
Closed by Antonio Rojas (arojas)
Friday, 21 August 2015, 11:58 GMT
Reason for closing: Fixed
Additional comments about closing: kdepimlibs 15.08.0-2
Friday, 21 August 2015, 11:58 GMT
Reason for closing: Fixed
Additional comments about closing: kdepimlibs 15.08.0-2
Comment by Antonio Rojas (arojas) -
Friday, 21 August 2015, 10:50 GMT
How long is "not long after"? These conflicts have been solved in 15.08, which has been in testing for 2 days already.
Comment by Jens Adam (byte) -
Friday, 21 August 2015, 11:17 GMT
Minutes apart. The mirror is up-to-date and the upgrade was 3h ago, so those are certainly not solved.
Comment by Jens Adam (byte) -
Friday, 21 August 2015, 11:21 GMT
Just compared the filelists, x86_64 and i686 differ.
Comment by Antonio Rojas (arojas) -
Friday, 21 August 2015, 11:58 GMT
ok that explains it, no idea what happened there. Thanks for the report