The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Whether Revisions should be required

Carl V Streeter <streeter@cae.wisc.edu>

> Now, consider this:
> I make a packages callex modules-1.xxx-1.deb.  In upload, this gets corrupted.
> I re-upload this as odules-1.xxx-1.deb, or new-modules, or whatever.

Call me standards-happy, but I think this can be easily addressed
by having an agreed standard procedure for dealing with this situation.
It's the "or whatever" part of the procedure which causes it to
be difficult to cope with.

I have a noticeable number of failed or corrupted uploads.  Sometimes,
I find the upload site in a state which allows me to delete the
bad file, and I do that and re-upload with the same name if I'm
able.  More usually, I'm not allowed to do this.  In this case,
I append a ".retryN" (n=[1-9], in sequence per retry) to the
target fillename and try again.

Given this as a standard procedures, scripts on the upload site could
simply mv any *.retry[0-9] files over the filenames with the .retry[0-9]
suffix removed prior to processing uploaded files.