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#51868 - [mypaint] broken pacman dependency 'protobuf-python' due to testing/python2-protobuf package changes
Attached to Project:
Community Packages
Opened by Adric (promarbler14) - Thursday, 17 November 2016, 23:47 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 18 November 2016, 10:53 GMT
Opened by Adric (promarbler14) - Thursday, 17 November 2016, 23:47 GMT
Last edited by Sergej Pupykin (sergej) - Friday, 18 November 2016, 10:53 GMT
|
DetailsDescription:
Pacman refuses to upgrade because of a broken dependency for mypaint, caused by a new change in the package info for testing/python2-protobuf, between the package releases 2.6.1-2 and 3.0.2-2 . Assuming that testing is following the correct lead, mypaint should be repackaged. In particular, python2-protobuf in testing no longer provides "protobuf-python", which mypaint depends on. Additional info: * community/mypaint 1.2.0-3 (local version is up-to-date.) * no relevant config files, though see attached. Steps to reproduce: Execute any pacman -Su operation with dependency processing. |
This task depends upon
Comment by Sergej Pupykin (sergej) -
Friday, 18 November 2016, 10:53 GMT
I've replaced protobuf-python with python2-protobuf. Should work for both community and community-testing.
repo_pkg_info.txt