On 17819 March 1977, Ian Jackson wrote:
- queued is for anything *before* it actually reaches the archive.
So
upload queues and their various steps.
Is the time a package can spend in there bounded? If so then it would
be possible to assume that things that were uploaded, but haven't
appeared in the later stages, got lost or overwritten somehow.
Not especially bound. It can stay minutes, it can stay hours. Queued
processes files, puts them in a dir for the unchecked process from
ftp-master to fetch. When that doesn't happen (archive off for whatever
reason, busy with other things, ....) then it can take time before files
move on.
(And then there is DELAYED, of course)
(Quite what to do about that is another question. AFAICT with
multiple rapidly successive uploads with increasing version numbers,
only one of them will get past queued? The DELAYED queues are a
wrinkle here too, I think.)
Queued doesnt care about any versioning, superseding or whatever. It
only deletes when the signature is broken or a command file tells it to
do so.
The archive does. I did merge something recently that should enable more
of such quickly obsoleted binaries to get published at least once (to
reach snapshot).
The latter can (and does) modify projectb, so adding more status info
at
that point is easy. Queued case needs more work and thought.
Are REJECTed uploads recorded in projectb then? (Or could they be?)
If they are then ...
No, not currently, except for their .changes signature.
--
bye, Joerg
