* Johannes Schauer Marin Rodrigues: " Re: Bug#977674: Corrupt changes file when built with --source-only-changes" (Sun, 24 Jan 2021 22:53:56 +0100):
Hi Josh, > Quoting Mathias Behrle (2020-12-18 16:39:44) > I'm not surprised that this bug exists. The codepath you are using doesn't get > any testing. The official buildds are not using source-only-changes and those > who do, do not sign the build result with sbuild. > > I'm tagging this with "help" and "newcomer". The fix is is likely to modify > the function close_build_log() in lib/Sbuild/Build.pm. There is a part that > calls debsign differently if SOURCE_ONLY_CHANGES is active and that part is > probably broken somehow. A merge request against > https://salsa.debian.org/debian/sbuild is greatly appreciated. Thanks for your analysis. As I am not familiar with perl at all I am not able to do this merge request. > Since you are using sbuild in a buildd context I think you can work around > this bug for now by either manually signing or manually mangling your changes > files? 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. Cheers Mathias -- Mathias Behrle PGP/GnuPG key availabable from any keyserver, ID: 0xD6D09BE48405BBF6 AC29 7E5C 46B9 D0B6 1C71 7681 D6D0 9BE4 8405 BBF6
