Hi Hilko (2024.11.29_22:43:04_+0000) > Unfortunately, this does not work in my case. pybuild installs qto > packages python3-ndiff and python3-zenmap, respectively – with no > obvious way to override the package names.
Turns out it can be overridden, I had to dig about to figure out how all of this works again. I'll push a commit to improve pybuild.1. This works: https://salsa.debian.org/pkg-security-team/nmap/-/merge_requests/8 What's going on is that dh_auto_install always specifies a destdir to buildsystems. So, pybuild's --name mechanism overrides that if it sees --dest-dir=debian/tmp. If it's set to any other value, it isn't overriden. I'll push a git comm to make pybuild.pm cleverer, so it understands if --dest-dir is specified and doesn't stomp on it with --dest-dir=debian/tmp. > In any case, the warning I mentioned in the bug report ought to be > either not come with any change in behavior or be a fatal error. This is harder. It happens a lot, perfectly benignly, in package builds. That's why it isn't currently a hard error. To turn it into a fatal error, we'd need to detect that the content in the scripts directory is different to what we're unpacking. The problem is that we aren't doing the unpack, we're relying on another module to do it, so we can't customize the unpack process. We'd probably need to move the existing directories out of the way, and compare them post-unpack. Building multiple python libraries in one source package is *very* rare. Do you think that's worth the effort? Stefano -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
