Do I understand the code correctly, that the python derivation depends on the binary library derivation and also executes the configure script in the sources again but does not build the binary library again?

Yes. The configure script at least sets the version, i.e. replaces @version@, while turning setup.py.in into setup.py. I could do that manually instead but I don't think there's a lot of harm in running the script.

The question is: Is this acceptable for staging-next? Otherwise it won't land in 24.11.
I tried only applying the second commit but ran into the same problem as #354166, even after adding distutils to build-system.
cc @NixOS/nixos-release-managers

The question is: Is this acceptable for staging-next?

I'm not sure, lemme ask the staging folks. I would say yes.

Otherwise it won't land in 24.11.

Yeah, we should fix this before 24.11's release.

Well it looks like this won't make it to 24.11, should go back to staging and it can land in there once approved enough.

I don't understand why python313.pkgs.gpgme fails to build with

checking for swig... /nix/store/8w5lfkjysan93sv31rmjxbpw1g1iv115-swig-4.2.1/bin/swig
checking for a Python interpreter with version >= 2.7... none
checking for a Python interpreter with version >= 3.6... none
checking for a Python interpreter with version >= 3.8... none
checking for a Python interpreter with version >= 3.9... none
checking for a Python interpreter with version >= 3.10... none
checking for a Python interpreter with version >= 3.11... none
checking for a Python interpreter with version >= 3.12... none
checking for a Python interpreter with version >= all... none
configure: error: 
***
*** Please install the python development packages.
***

@mweinelt Any idea?

@dotlambda I think that is the configure script of gpgme which tries to find a suitable python version and they have hardcoded a list :/

Maybe there is an option to tell configure to just use one specific python executable and not search for it, but I did not find that option at first glance.

@lucc Did you even look at this PR's diff? There's a patch that changes said list.

Should we merge this anyway and fix Python 3.13 later?

@ofborg build gpgme.passthru.tests python313.pkgs.gpgme

Backport failed for staging-24.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin staging-24.11
git worktree add -d .worktree/backport-354635-to-staging-24.11 origin/staging-24.11
cd .worktree/backport-354635-to-staging-24.11
git switch --create backport-354635-to-staging-24.11
git cherry-pick -x b3797b6d48b59ca5d8e1c991278d33ad48bde9bd 29c88a0ce64fed33d93d02605c8420ff42d570ee

Fix for python313Packages.gpgme: #371188