Comment 11 for bug 136593

The main problem with that approach is that dput is asynchronous: it
drops the package into an upload queue, which is processed at some later
point after dput has disconnected. (It's important that it be that way,
because processing could take quite some time for large packages and we
wouldn't want to break just because somebody's connection failed after
they'd completed the upload but before we managed to process it.)

We could do better for SFTP uploads, as alluded to earlier in this bug
log: while we should still require the upload to be signed, SSH
authentication is enough that we could at least trust it for the purpose
of assuring that we can send notification mail. This would only really
be effective if dput's defaults were changed, which is difficult because
it needs to know the user's Launchpad username, but there are ways to
mitigate that (e.g. prompt at first use) and it would still be a good
start.

The other thing I can think of in addition to this would be a
dismissable notification on your Launchpad user page about upload errors
we think might be related to your account, a bit like the system we
already have for package copy failures. If we also arranged for dput to
tell you that upload errors would be notified on your user page, that
would be a good improvement.