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#56345 - [qcachegrind] conflicts with kcachegrind
Attached to Project:
Community Packages
Opened by Alexander F. Rødseth (xyproto) - Thursday, 16 November 2017, 09:38 GMT
Last edited by Antonio Rojas (arojas) - Friday, 09 March 2018, 08:27 GMT
Opened by Alexander F. Rødseth (xyproto) - Thursday, 16 November 2017, 09:38 GMT
Last edited by Antonio Rojas (arojas) - Friday, 09 March 2018, 08:27 GMT
|
DetailsDescription:
When installing both kcachegrind and qcachegrind: /usr/bin/dprof2calltree exists in both 'kcachegrind' and 'qcachegrind' /usr/bin/hotshot2calltree exists in both 'kcachegrind' and 'qcachegrind' /usr/bin/memprof2calltree exists in both 'kcachegrind' and 'qcachegrind' /usr/bin/op2calltree exists in both 'kcachegrind' and 'qcachegrind' /usr/bin/pprof2calltree exists in both 'kcachegrind' and 'qcachegrind' /usr/share/icons/hicolor/32x32/apps/kcachegrind.png exists in both 'kcachegrind' and 'qcachegrind' /usr/share/icons/hicolor/48x48/apps/kcachegrind.png exists in both 'kcachegrind' and 'qcachegrind' Errors occurred, no packages were upgraded. Steps to reproduce: pacman -S kcachegrind qcachegrind |
This task depends upon
Closed by Antonio Rojas (arojas)
Friday, 09 March 2018, 08:27 GMT
Reason for closing: Fixed
Additional comments about closing: qcachegrind 17.12.3-2
Friday, 09 March 2018, 08:27 GMT
Reason for closing: Fixed
Additional comments about closing: qcachegrind 17.12.3-2