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#63701 - mypaint conflicts with libmypaint and gimp
Attached to Project:
Arch Linux
Opened by Jaume Delclòs Coll (cosarara) - Monday, 09 September 2019, 11:37 GMT
Last edited by Levente Polyak (anthraxx) - Monday, 09 September 2019, 11:42 GMT
Opened by Jaume Delclòs Coll (cosarara) - Monday, 09 September 2019, 11:37 GMT
Last edited by Levente Polyak (anthraxx) - Monday, 09 September 2019, 11:42 GMT
|
DetailsDescription:
Since a recent update, mypaint conflicts with libmypaint, a gimp dependency. This means that gimp and mypaint can't be installed side by side on the same system. There is the following comment in the mypaint PKGBUILD before the conflicts line: # requires mypaint 2.0 with libmypaint 2.0 to work dynamically Additional info: * mypaint 1.2.1-9 * libmypaint 1.3.0-6 * gimp 2.10.12-2 Steps to reproduce: pacman -S mypaint gimp |
This task depends upon
Closed by Levente Polyak (anthraxx)
Monday, 09 September 2019, 11:42 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#63663
Monday, 09 September 2019, 11:42 GMT
Reason for closing: Duplicate
Additional comments about closing:
Comment by Levente Polyak (anthraxx) -
Monday, 09 September 2019, 11:42 GMT
Search for existing bugs before opening new ones