FS#63288 - [mypaint] building against swig 4 produces a broken package
Attached to Project:
Community Packages
Opened by Antonio Rojas (arojas) - Saturday, 27 July 2019, 08:24 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 12 September 2019, 00:50 GMT
Opened by Antonio Rojas (arojas) - Saturday, 27 July 2019, 08:24 GMT
Last edited by Eli Schwartz (eschwartz) - Thursday, 12 September 2019, 00:50 GMT
|
Details
Description:
After rebuilding the package with current swig: Traceback (most recent call last): File "/usr/bin/mypaint", line 464, in <module> main.main(datapath, iconspath, old_confpath, version=version) File "/usr/share/mypaint/gui/main.py", line 95, in main from gui import application File "/usr/share/mypaint/gui/application.py", line 48, in <module> import lib.document File "/usr/share/mypaint/lib/document.py", line 37, in <module> import lib.helpers as helpers File "/usr/share/mypaint/lib/helpers.py", line 26, in <module> import mypaintlib File "/usr/share/mypaint/lib/mypaintlib.py", line 13, in <module> from . import _mypaintlib ImportError: cannot import name _mypaintlib |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Thursday, 12 September 2019, 00:50 GMT
Reason for closing: Fixed
Additional comments about closing: mypaint 1.2.1-10
Thursday, 12 September 2019, 00:50 GMT
Reason for closing: Fixed
Additional comments about closing: mypaint 1.2.1-10
Discussion: https://github.com/mypaint/mypaint/issues/929
It drops the use of scons and adds support for depending on the system libmypaint package. Generally alphas of software would be avoided if possible, but given mypaint doesn't build at the moment, it might be better than dropping it to the AUR.