On Wed, May 01, 2002 at 02:08:02AM +0200, Josip Rodin wrote: > Even if it doesn't put stuff into pool/, the package is accepted, at that > point it's in the archive[1] I assert that it isn't. It's in a directory called queue because it's queued for further processing. Once that further processing is done, it's in the archive (or rejected, or otherwise not in the archive). However, one of the FTP admins is probably in a position to make an official pronouncement on this matter, if they're so inclined. > as there's no way for it to get automatically thrown out and thus > invalidate the closing of the bug. I thought the issue wasn't whether the closing would be invalidated; after all, I could somehow extract a promise from an FTP admin that he would accept a given package with a given bugfix in it months before I actually upload the package, and thereby be assured that there is no way it will be "automatically thrown out". Under such circumstances should I close the bug months in advance of actually uploading the fix? Obviously not. No, the reason bugs used to be closed when the package hit the archive^Wpool^Wdists/unstable^Wwhatever was because only at that point would the bug fix be available to the general public. > [1] we really know how to overload those terms, don't we? distribution, > section, archive... each of these has a few definitions and whatever else > makes sense even remotely can be a new definition. ;) I don't think there is a problem in this case. The queue is queue, and the archive is the pool and the dists. If the FTP maintainers would care to correct me, I'd appreciate it. -- G. Branden Robinson | The key to being a Southern Debian GNU/Linux | Baptist: It ain't a sin if you branden@debian.org | don't get caught. http://people.debian.org/~branden/ | -- Anthony Davidson
Attachment:
pgpiGnyEBmmgH.pgp
Description: PGP signature