Control: tag -1 - newcomer Hi,
Quoting Mathias Behrle (2021-01-25 08:55:34) > Probably I shall try this next time resp. I will try with an old version of > sbuild. > > IIRC this bug is a regression introduced (probably between August and > September > 2020). Before the signing process used to work for changes as well as for > source-only-changes. From my unexperienced view the following commit comes to > my > attention > https://salsa.debian.org/debian/sbuild/-/commit/bafc5362e0bbf29c5604fcaa73454e0fd6d0e3fc > that could have caused the impact. that this is maybe a regression piqued my interest. I tried to reproduce the problem you are seeing by running sbuild with --keyid, --source-only-changes and --source. This is probably the combination that causes your problem. Unfortunately, I was not able to reproduce your problem. How did you verify that the checksums indeed are wrong? Did you try running dscverify on the amd64 and source changes files? I tried with a test package and it all checks out: tmp/test-pkg_1.0_source.changes: validating test-pkg_1.0.dsc validating test-pkg_1.0.tar.xz validating test-pkg_1.0_amd64.buildinfo All files validated successfully. tmp/test-pkg_1.0_amd64.changes: validating test-pkg_1.0.dsc validating test-pkg_1.0.tar.xz validating test-pkg_1.0_all.deb validating test-pkg_1.0_amd64.buildinfo All files validated successfully. Also, maybe unrelated, why are you running sbuild with --source? Did you read the part in the sbuild man page about the --source option? Thanks! cheers, josch
signature.asc
Description: signature
