Hi Corey (2023.02.24_20:48:54_+0000) > Would you object to generating cpython3_fallback on the fly during the package > build? If so I'm happy to submit a patch.
I had a chat about this with people in #debian-devel, and people didn't really like the idea of pulling apt-file data during a build. (There was some misunderstanding about exactly how dh-python does this, of course...) I'd say the main concerns are: 1. Guarantees of Contents.gz availability. 2. Guarantees of reproducibility. I guess we'd have to merge between all configured apt suites. But there is no guarantee that a build chroot will have a correctly configured apt. Some other options we could consider: 1. Including Ubuntu data when we build pydist. Assuming there are only additions, not different packages providing the same python module... 2. Building a separate Ubuntu pydist, and selecting the appropriate one to install, at build time. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272
