Control: retitle -1 sbuild.conf should generate source.changes by default Thank you for your replies, and sorry for my delay replying.
Aurelien Jarno <[email protected]> writes: > On 2025-10-31 06:15, Johannes Schauer Marin Rodrigues wrote: >> Hi, >> >> Quoting Nicholas D Steeves (2025-10-30 22:44:20) >> > I hadn't run sbuild directly in ages, and today I discovered that that it >> > still defaults to binary-only uploads! Of course this results in an >> > auto-reject. Yes, my mistake was carelessness and assuming that >> > sbuild.conf >> > defaults had been updated to keep pace with ftpmasters policy from...what >> > is >> > it now, five or six years? >> > >> > The question is probably: Should sbuild build source+bin, or just source. >> >> if you want to build a source package, this is the tool you should use: >> >> dpkg-source -b . Sorry, I wasn't clear: I meant generate source.changes rather than [re]generating the source package. >> If you want to make sure that the binaries you built and tested are >> connected to the source package you upload, you can use another >> convenience feature: --source-only-changes tells sbuild to create a >> .changes file which includes the source package that it used to build >> just now. >> > I would also note that the current behaviour matches with the package > short description: > > Tool for building Debian binary packages from Debian sources I hope the following is more clear: 1. sbuild is part of the preferred workflow, because it is what is used on buildd. 2. Maintainers should locally test their packages before uploading. 3. The locally tested package must directly correspond to what will be uploaded. 4. The Archive exclusively accepts source.changes, except for NEW uploads. :. sbuild should generate source.changes Regards, Nicholas
signature.asc
Description: PGP signature
