uefi custom uploads cause backscatter to signer instead of uploader

[Kamal Mostafa]

Why is launchpad notifying *me* about this????

Yes, I did (successfully) upload this package to the archive over a year ago. But I do not care that Joe Random User's PPA build of it (package copy?) failed today.

------------------------------------------------------------------------------

From: Ubuntu Installer <email address hidden>
To: Kamal Mostafa <email address hidden>
Subject: [~cprov/ubuntu/sandbox/saucy] linux_3.11.0-19.33_amd64.tar.gz - (Rejected)
Date: Thu, 28 May 2015 12:28:09 -0000 (05/28/2015 05:28:09 AM)

Rejected:
Rejected by Chris Stratford: Unpublishable UEFI custom uploads.

linux (3.11.0-19.33) saucy; urgency=low

[... full notification message attached ...]

[Adam Conrad (adconrad)]

So, in my mind there are two bugs here:

One is that the uefi custom uploads seem to be somewhat misattributed. I've noticed this for ages on -changes mailing lists where, say, an SRU kernel gets ACCEPTED messages from me for all the copies, but the UEFI tarball gets an ACCEPTED message from the original PPA signer, instead of the uploader.

The second bug (maybe) is that we're generating these mails at all. Custom uploads in other cases don't seem to generate extra mail (see debian-installer), so why are UEFI tarballs a unique snowflake here that generate an extra accept/reject message on top of the linux package that is the parent? I suspect I know the basic reason here (because we hold them in unapproved for review), but it still seems a bit messy and weird from a UI perspective.

Anyhow, the second bit is debatable, but fixing the first bit would make the second less problematic and more just slightly odd.