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#60806 - [gtk-sharp-2] illegal conflict gtk#
Attached to Project:
Arch Linux
Opened by Andreas Baumann (andreas_baumann) - Wednesday, 14 November 2018, 16:32 GMT
Last edited by Jan de Groot (JGC) - Sunday, 03 February 2019, 22:42 GMT
Opened by Andreas Baumann (andreas_baumann) - Wednesday, 14 November 2018, 16:32 GMT
Last edited by Jan de Groot (JGC) - Sunday, 03 February 2019, 22:42 GMT
|
DetailsDescription:
:: Synchronizing package databases... staging is up to date testing is up to date core is up to date extra is up to date community-staging is up to date community-testing is up to date downloading community.db... :: Starting full system upgrade... there is nothing to do ==> Building in chroot for [staging] (x86_64)... ==> Synchronizing chroot copy [/data/archbuild/staging-x86_64/root] -> [arch32]...done ==> ERROR: conflicts contains invalid characters: '#' Additional info: * package version(s): 2.12.45-1 Steps to reproduce: asp export gtk-sharp-2 cd gtk-sharp-2 staging-x86_64-build |
This task depends upon
Comment by Jan de Groot (JGC) -
Sunday, 03 February 2019, 22:42 GMT
There used to be a gtk# package, so the conflicts is correct. However, it's very unlikely someone will upgrade a system containing that package, the conflict was added years ago, so I decided to remove it now.