Samba/libtalloc/libtdb/libtevent/libldb fails to build with Python 3.8. Checking for pyembed fails because it is not really supported by the python3-config anymore, see https://bugs.python.org/issue36721
Ok, this is a python3 change. We need to fix waf to look up pyembed correctly as libpytalloc-util requires it!
waf bug: https://gitlab.com/ita1024/waf/issues/2239
Created attachment 15252 [details] patch for 4.10
Comment on attachment 15252 [details] patch for 4.10 LGTM. Please create a CI run on gitlab too.
(In reply to Alexander Bokovoy from comment #4) Pushed to autobuild-v4-10-test. Patch adds trailing whitespaces.
Yes, that's from waf upstream repo. Andrew didn't want to remove them :-)
Pushed to v4-10-test. Closing out bug report. Thanks!
David pointed out to me in a private mail that the version numbers of the sub-projects need to be bumped to keep the common code (eg the build system) in sync between released tarballs and the published samba tarball. Lets sort that out in bug 13846.
(In reply to Andrew Bartlett from comment #8) Trying to put the last comment in other words that make more sense to me, pls correct me if I'm wrong: In order to actually "fix" this bug for libraries (as the bug is for both Samba and libraries) we need to make a new release of those libraries. And in order to make a new release, we need to bump the version numbers because, well, different releases must have different version numbers. It's not about ABI stuff and such. Hence the bumping, where applicable should be in the patchlevel number.
(In reply to Uri Simchoni from comment #9) Correct. This isn't really an ABI change, we just need new packages. However our current process requires it. See https://gitlab.com/samba-team/samba/merge_requests/374 for an attempt to make the ldb package version be the Samba version, which would have made this process automatic for ldb but it got lost in the weeds.
In master we have: git log --oneline origin/master third_party/waf/ lib/tdb/wscript lib/tevent/wscript lib/talloc/wscript 123267138e99 tevent: Release tevent 0.10.1 60cba7b3a171 tdb: Release tdb 1.4.2 cd20e3876c36 talloc: Release talloc 2.3.0 aabdcc91513e third_party: Update waf to version 2.0.17 For 4.10 we have: git log --oneline origin/v4-10-stable third_party/waf/ lib/ldb/wscript fe99db5c3492 ldb: Release ldb 1.5.6 c51d810ee99f third_party: Update waf to version 2.0.17 For 4.11 we have: git log --oneline origin/v4-11-stable third_party/waf/ lib/ldb/wscript bc0d16c9d8ea ldb: Release ldb 2.0.7 9c677a274d49 ldb: Correct Pigeonhole principle validation in ldb_filter_attrs() 80bd467affbd ldb: Release ldb 2.0.6 86d480ade259 ldb: Release ldb 2.0.5 f58324570655 ldb: Fix dependency on ldb_key_value_sub_txn_{mdb_}test e46d5bb669d1 ldb: Release ldb 2.0.4 201684e59fd4 lib ldb ldb_key_value tests: Add tests for wrapped operations b78597e1cd0b lib ldb: csbuild add lib/util/attr.h to dist aabdcc91513e third_party: Update waf to version 2.0.17 So this seems to be no problem at all. All current releases have at least waf 2.0.17