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#16071 - system-config-printer-common not backwards compatible
Attached to Project:
Arch Linux
Opened by Christoper Daley (luciferin) - Monday, 07 September 2009, 05:13 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 07 September 2009, 07:20 GMT
Opened by Christoper Daley (luciferin) - Monday, 07 September 2009, 05:13 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 07 September 2009, 07:20 GMT
|
DetailsDescription:
pacman gives a dependency error when upgrading certain components due to the name change/upgrade of system-config-printer The package could be change to provide system-config-printer until all packages which depended upon it are rebuild with the new name. Affects system-config-printer-common version 1.1.12-5 Steps to reproduce: run a 'pacman -Syu' or try to install kdeadmin-system-config-printer-kde package resolving dependencies... warning: cannot resolve "system-config-printer>=1.1.7-3", a dependency of "kdeadmin-system-config-printer-kde" warning: cannot resolve "system-config-printer>=1.1.7-3", a dependency of "kdeutils-printer-applet" :: the following package(s) cannot be upgraded due to unresolvable dependencies: kdeadmin-system-config-printer-kde kdeutils-printer-applet Do you want to skip the above package(s) for this upgrade? [Y/n] |
This task depends upon
Comment by Christoper Daley (luciferin) -
Monday, 07 September 2009, 05:20 GMT
I'm sorry, with further investigation this doesn't appear to be a bug... I couldn't reach SVN to check the PKGBUILD before I filed the report, but after the latest upgrade the errors seem to have resolved.