On Mon, Aug 25, 2025, at 4:14 AM, xiao sheng wen wrote: > Package: cargo > Version: 0.66.0+ds1-1 > Severity: normal > X-Debbugs-Cc: [email protected], [email protected] > > Hi, > > When I build the libimagequant package, I meet a FTBFS[1]: > > debian/rules execute_before_dh_auto_configure > make[1]: Entering directory > '/build/reproducible-path/libimagequant-4.4.0' > /usr/share/cargo/bin/cargo prepare-debian debian/cargo_registry > --link-from-system > make[1]: /usr/share/cargo/bin/cargo: No such file or directory > make[1]: *** [debian/rules:28: execute_before_dh_auto_configure] Error > 127 > make[1]: Leaving directory > '/build/reproducible-path/libimagequant-4.4.0' > make: *** [debian/rules:8: binary-arch] Error 2 > dpkg-buildpackage: error: debian/rules binary-arch subprocess returned > exit status 2 > > /usr/share/cargo/bin/cargo is a python3 script, after I add python3 to > Build-Depends, > the libimagequant package build success. > > The cargo package is set Suggests: python3 now, but it's enough for > build package, > so I hope set cargo Depends python3.
cargo itself doesn't require python at all, just this build wrapper for packaging purposes does. I am wary of upgrading the dependency for this reason. in particular, dh-cargo (the main user of the cargo wrapper) already has this dependency, so for the vast majority of package builds python3 is already pulled in correctly.. splitting out the cargo wrapper into its own package also seems a bit overkill, although it might make sense if we pull out the whole collection of package build helper scripts?
