source uploading with a .buildinfo containing hashes for binary is rejected

I am also running into this bug by building with --source-only-changes which is useful to locally build the binary to ensure it works, then upload a _source.changes, all in one command.

Hit this as well. Preventing me from updating Antimicro for folks over at https://github.com/AntiMicro/antimicro/issues/192. Is there any workaround?

Ok I worked around this by just removing the buildinfo from the file list in .changes/source.chanages. Don't bother with any other trickery.

Yep, would be nice to fix this issue. Just ran into it.

Just ran into this myself. Bit of a pain if you want to test build & install in a ppa.

If you're using pbuilder then you can simply skip saving the .buildinfo with this command:
pdebuild -- --source-only-changes --debbuildopts --buildinfo-option="-O"

Using git-buildpackage, this bug can be worked around using the following flag:

--git-pbuilder-opt="--debbuildopts='--buildinfo-option=-O'"

also:
dpkg-buildpackage -i -S -d --buildinfo-option=-O

make sure that debian/files doesn't reference the buildinfo file from previous build attempts.

For `gbp` and `sbuild`, this is what I ended up having to do:

gbp buildpackage --git-builder="sbuild --source-only-changes --debbuildopts='--buildinfo-option=-O'"

```
sbuild --source-only-changes --debbuildopt=--buildinfo-option=-O --dist impish
```

used to produce a `_source.changes` file without the `.buildinfo` lines. However, I find

```
sbuild --source-only-changes --debbuildopt=--buildinfo-option=-O --dist jammy
```

always adds the `.buildinfo` lines to the `_source.changes` file and the upload to Launchpad is rejected with the cryptic:
```
Mismatch in binaryfulness. (arch) False != (files) True
```

Back to doing

```
sed -i '/buildinfo/d' *_source.changes
```

unless anyone has a better workaround?

I can confirm that with jammy, buildinfo is included, even with the debbuildopts flag turning it off.