On 2015-12-24 00:04, Johannes Schauer wrote:
why this high severity? This rather sounds like a feature request so
should be
severity wishlist, no?
buildd should check if date(.upload) < date(.changes) &&
signed(.changes) and
delete the .upload file if this is the case. Otherwise uploads of
given-back
packages will not happen if a stale .upload file still lays around in
the
upload queue, despite it being signed properly.
Since this bug has been unfixed for more than five years I guess the
problem
has been dealt with in a different way now?
Can this bug thus be closed?
Should it be marked wishlist?
We still need to login manually into buildds whenever this happens and
nuke away the .upload file.
(Luckily it does not happen too often that builds are rejected or
reuploaded. And the security team for instance knows that they have to
contact us for exactly this manual action whenever this happens.)
Kind regards
Philipp Kern
