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#33517 - [kadu] don't store plugins in /usr/lib64, this makes [testing]/filesystem angry
Attached to Project:
Community Packages
Opened by Aurora (LadyAurora) - Tuesday, 22 January 2013, 15:57 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Wednesday, 23 January 2013, 20:25 GMT
Opened by Aurora (LadyAurora) - Tuesday, 22 January 2013, 15:57 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Wednesday, 23 January 2013, 20:25 GMT
|
DetailsDescription:
kadu 0.12.3-1 stores plugin DSOs in /usr/lib64/kadu/plugins. filesystem 2013.01-1 (the one currently in [testing]) wants to make /usr/lib64 a symlink. This results in a file conflict. Possible solution: Move the kadu plugins to /usr/lib/kadu/plugins. |
This task depends upon
Closed by Bartłomiej Piotrowski (Barthalion)
Wednesday, 23 January 2013, 20:25 GMT
Reason for closing: Fixed
Additional comments about closing: kadu 0.12.3-2
Wednesday, 23 January 2013, 20:25 GMT
Reason for closing: Fixed
Additional comments about closing: kadu 0.12.3-2
Comment by Dave Reisner (falconindy) -
Wednesday, 23 January 2013, 14:59 GMT
This blocks moving glibc/filesystem to [core].