-
Notifications
You must be signed in to change notification settings - Fork 123
Ubuntu Focal (20.04) Python Bindings #3522
Comments
The original issue regarding this incompatibility is #3379. It was resolved by adding the version check. If ubuntu backported the fix, which I do not think, there is no guarantee that other distris did the same. |
They didn't backport the commit. See https://bugs.launchpad.net/ubuntu/+source/swig/+bug/1876764 |
While further looking: |
Thank you so much for looking into this! If
So we can make this check less strict? Are we talking about this |
Add
3.9 will remove |
So it will not help for Ubuntu Focal as 3.8 still has tp_print? But this means that we can make the check less strict (allow 4.0.1 with >=3.9). Did someone try SWIG 4.0.2 on Ubuntu Focal? |
Afair the error was related to |
Yes, I will also create the docker image for 20.04. |
Any update here? Did someone manage to build the Ubuntu Focal (20.04) packages with Python Bindings? |
The python bindings are building on Ubuntu Focal with SWIG 4.0.2. For building of the deb packages I changed the swig dependencies in ...
dpkg-checkbuilddeps: error: Unmet build dependencies: swig
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting Removing swig from the Build-Depends section in |
What exactly is the change? Can you create a PR or point me to the repo?
Please run Is there another error earlier (from cmake)? Does CMakeFiles/CMakeError.log say something about why the swig executable is unsuitable? (It is possible cmake did not even run as dpkg found a dependency problem earlier.) |
I will soon add the changes to the pipeline and the new Ubuntu Focal Dockerfile to my last PR.
Will do.
I did. I just wanted to mention that building of the package would require changes to debian/control and debian/rules
Yes but i don't think it has something to do with swig. All tests pass as well.
|
Yes, but probably these changes will stay compatible so that also Debian Buster can build with it. (As you already noticed about the swig binary. And removing a dep will not break the Debian builds.) Long term we probably need a better solution as it will probably not always be possible to cover all Debian derivatives from a single source.
Some tests in CMakeFiles/CMakeError.log are supposed to fail, e.g. when CMake checks some linker flags a test might fail but CMake knows about an alternative, as in this case: CMAKE_HAVE_LIBC_PTHREAD checks if libc has pthread but on this system, pthread is a separate library. So no need to worry here, nothing seems to be related to swig. |
Ubuntu Focal (20.04) needs swig 4.0.2 to build the Python Bindings. Since swig 4.0.2 is currently installed manually in the docker images (without package manager), it can not be found by dpkg. Therfore it needs to be removed. Discussed in ElektraInitiative#3522
Ubuntu Focal (20.04) needs swig 4.0.2 to build the Python Bindings. Since swig 4.0.2 is currently installed manually in the docker image (without package manager), it can not be found by dpkg. Therefore it needs to be removed. Discussed in ElektraInitiative#3522
I now tested https://build.libelektra.org/job/libelektra-release/70/artifact/artifacts/ubuntu-focal/ubuntu-focal-release.tar.gz |
It looks like Ubuntu Focal (20.04) has incompatible SWIG/Python versions according to:
libelektra/src/bindings/swig/python/CMakeLists.txt
Lines 28 to 30 in cbb0909
which gets exactly triggered by:
https://packages.ubuntu.com/focal/swig 4.0.1-5build1
https://packages.ubuntu.com/focal/python3 3.8.2-0ubuntu2
@manuelm do you remember which incompatibility is addressed there?
The first question is, if our check is correct. Maybe 4.0.1-5build1 already contains a patch that fixes this incompatibility.
If they really are incompatible, then we could try to upgrade swig, which hopefully still will lead to functioning Ubuntu Focal (20.04) packages, as swig should not show up as run-time dependency.
@robaerd Can you already build Ubuntu Focal (20.04) packages for the upcoming release? (At the moment we also do not even have a Docker image for 20.04, so it is probably quite a bit of work.) There were already several requests to have it, e.g. #3412
@mpranj It would be great if this issue can be fixed for 0.9.3. (If the swig upgrade is necessary and works, nothing is to be changed in the source of Elektra.)
@dev2718 Thank you for reporting this problem!
The text was updated successfully, but these errors were encountered: