Hi Soren, Quoting Soren Stoutner (2025-11-18 02:51:10) > I just needed to do a library transition, involving a binary upload to NEW. > Without the $build_source entry in my .sbuildrc, it did not produce the > necessary files. When uploading the amd64.changes file, this is what was > sent:
this is what the --source-only-changes option is for. I have it in my ~/.config/sbuild/config.pl so that I always get a *_source.changes. In cases where I also need to upload the source, I can do: mergechanges xxx_arm64.changes xxx_source.changes > xxx_both.changes And then I can dput xxx_both.changes. If you want to automate this, you might want to look into a tool which is aware of what is getting uploaded. For example dgit is able to drive sbuild and merge the .changes files in whatever way required for an upload. I'm not sure whether sbuild is the right location for even more convenience options than what --source-only-changes already provides. I think you are looking for a --both-changes option but that would just further pollute the list of command line arguments with a feature which I think is better put into tools which know how to upload to the archive (like dgit). What do you think? Thanks! cheers, josch
signature.asc
Description: signature
