Steve Langasek <[EMAIL PROTECTED]> writes: > Why not? AFAIK, there's no reason that you can't do an additional upload > that would let both new binary package names through the NEW queue at the > same time.
Because it won't get through any faster that way. It will simply get added to the existing request, which has been languishing. > Also, at this point, any binaries of libofx 1:0.8.0-4 built by autobuilders > after clearing the NEW queue will immediately break packages which depend on > libofx2 (changed ABI without changed package name), so it's not necessarily > a good idea for the ftpmasters to *let* libofx through NEW in its present > state... That's unhelpful. If the ftpmasters want to help out release engineering, they need to do so. It was nice to have them stop processing on ofx when asked, but it's not ok to have them proceed to ignore it after two rounds of NEW processing once asked to consider it once more. Based on past experience, my guess is that it will simply wait, and wait, until it gets whatever special attention it needs. No reupload can change that. Moreover, I have been scolded in the past for making an upload while a previous upload was in the NEW queue. So, all that said, I'll do an extra upload without waiting, if I hear from the ftpmasters that this is what *they* want me to do. Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
