Bug#932753: tag2upload should record git tag signer info in .dsc
Package: dgit-infrastructure
Version: 9.4
Raphael Hertzog writes ("Re: git & Debian packaging sprint report"):
> On Sun, 21 Jul 2019, Ian Jackson wrote:
> > IME as a sponsor I get (AFAICT) no mails as a result of my sponsorship
> > signatures so I think there are few automatic processes.
>
> That's actualy not true, dak is sending mails to the person who signs the
> upload when it has to send mails like NEW notifications, etc.
>
> > Hrm, I think tracker may become confused. It seems to be looking at the
> > .dsc signatur. So maybe the .dsc field is indeed needed.
>
> Yes, definitely.
Thanks to all for the info. I thought I would capture this here in
a bug, which I can mention in my commit messages, giving a link back
to this -devel thread.
The signing robot's key email address will be a mailing list, so any
stray emails will go there. That's clearly far from perfect but I
don't think it's a blocker for deployment. (Which is good because
fixing it will involve patching dak and the other things which use
that signing identity.)
Ian.
--
Ian Jackson <ijackson@chiark.greenend.org.uk> These opinions are my own.
If I emailed you from an address @fyvzl.net or @evade.org.uk, that is
a private address which bypasses my fierce spamfilter.
Reply to: