Hi Johannes, Johannes Schauer Marin Rodrigues <josch@debian.org> writes: > Hi Xiyue Deng, > > On Sun, 09 Nov 2025 23:03:55 -0800 Xiyue Deng <manphiz@gmail.com> wrote: >> Sorry I missed your previous email. I also got confused that even if I >> tried to build using `sbuild --source-only-change' it still generates a >> *_amd64.changes, and by default it doesn't provide a *_source.buildinfo >> and so debsign fails to sign *_source.changes. So I signed the other >> *_amd64.changes and uploaded that, which apparently had the same effect. >> >> So it turns out I can make *_source.buildinfo a symlink to >> *_amd64.buildinfo and it will let debsign pass. I have now reuploaded >> the *_source.changes which hopefully should be intended. Sorry for the >> double failure. >> >> (Also, if there is a way to generate *_source.buildinfo please let me >> know :) > > please do not symlink *_source.buildinfo to *_amd64.buildinfo. > > I would be very interested in how you made sbuild create a *_source.buildinfo. > This is out-of-scope for this bug but I'd like to see a reproducer of this > problem and I'd be happy to receive a bug against sbuild for this problem. > > None of the 303 *_source.changes files that I have locally as leftovers from previous builds with sbuild --source-only-changes point to a *_source.buildinfo.They should not. > Exactly, it didn't! Sorry if my previous email was not clear: `sbuild --source-only-changes' only produces *_amd64.buildinfo. The issue is that in this case, `debsign'ing *_source.changes fails because it's looking for *_source.buildinfo but only *_amd64.buildinfo is available. So I wonder, how to invoke sbuild so that `debsign'ing *_source.changes can succeed OOTB? > Thanks! > > cheers, josch -- Regards, Xiyue Deng
Attachment:
signature.asc
Description: PGP signature