On Tue, Mar 03, 08:21, Helmut Grohne wrote > On Mon, Mar 02, 2026 at 09:29:58PM +0100, Andre Noll wrote: > > Yes, please upload the version I've just tagged as v1.0.6-1. The > > ID of the git commit is cd596839f6d8147ac7464fddad88d0987c728e02. > > Signing a the git commit id in the mail is fine to me. > > Unfortunately, the commit does not seem very well tested. The format of > debian/changelog is rejected by dpkg-source. A space is missing.
Sorry about that. I've now added a fixup commit that adds the space. The
tip of the updated branch is
11f06a85b699251b6ef9ecdd87c85503e007fcd4
> Beyond that, this is uploading a new upstream release. I attempted
> fetching it via uscan and uscan failed verifying the expected upstream
> signature.
Hm, works for me. Does the signature of this email verify?
> This is not in a state that I can sponsor, sorry.
>
> How about uploading a targeted .debdiff fixing just the rc bug for now
> and deferring the upstream release and its signature verification?
I was unable to produce a .debdiff that consisted only of the change introduced
by commit c0cf8e24b72effbe53c7dd840ead5130b87151d9 that fixed the RC bug. What
would be a suitable debdiff command to achieve that?
Thanks
Andre
--
Max Planck Institute for Biology
Tel: (+49) 7071 601 829
Max-Planck-Ring 5, 72076 Tübingen, Germany
https://people.tuebingen.mpg.de/maan/
signature.asc
Description: PGP signature
