Andrey Rakhmatullin <w...@debian.org> writes: > On Thu, Dec 26, 2024 at 12:03:51PM +0100, Simon Josefsson wrote: >> Andrey Rakhmatullin <w...@debian.org> writes: >> >> > Wasn't the proposed fix "export PYBUILD_NAME as the docs say"? I see you >> > are not doing this. >> >> Thanks for reply! I added that but commented out since adding it did >> not change the pybuild behaviour. The extra genson/schema/ files are >> not built and installed, only the top-level genson/ directory which is >> the case even without PYBUILD_NAME. > > I've rechecked and the proposed fix also included "also, note the big fat > warnings about upstream not configuring setuptools correctly". > As I've just checked, running `python3 -m build` in the upstream repo also > produces a wheel without the schema subpackage.
Thanks for testing. Yes so maybe the best is if upstream make genson/schema/ installed by default, and maybe that will solve the autopkgtest failure too. Or we can look into reverting back something based on my 'hack' approach, which is pretty much the same as the PYBUILD_BEFORE_TEST command, that made autopkgtest happy. I didn't understand which big fat warning this was? I looked in the build logs. /Simon
signature.asc
Description: PGP signature
