On Wed, Dec 31, 2003 at 09:34:26AM +1100, Daniel Stone wrote:
> On Tue, Dec 30, 2003 at 02:08:41PM -0500, Debian Installer wrote:
> > [nothing of substance, annoyingly]
>
> Hi all,
> OK, so here's what happened:
> * Branden builds pre1v5 (source all powerpc), uploads and has it held
> in queue/new.
> * I build pre1v5 (i386) in my sid chroot, upload and have it held in
> queue/new.
> * pre1v5 (source all powerpc) gets ACCEPTed, and moved into
> experimental.
> * pre1v5 (i386) passes the first basic jennifer checks and gets
> ACCEPTed - but only as far as queue/accepted.
> * kelly realizes pre1v5 (i386) is targeted to unstable (in
> queue/accepted at this stage), but there's no source for pre1v5 in
> unstable. It panics and UNACCEPTs pre1v5 (i386), but this is very
> much a messy, manual operation - doesn't remove anything, doesn't
> reopen any bugs.
> * pre1v5 (i386) thus sits in queue/accepted, getting UNACCEPTed every
> time kelly runs.
> * I manually edit the .changes file and retarget pre1v5 (i386) to
> experimental; I upload.
> * pre1v5 (i386/experimental) gets into queue/unchecked, but every one
> of its files is already in queue/accepted, hence it gets REJECTed.
>
> That's the situation with pre1v5 (i386), unless there's been some
> ftpmaster action very recently. If there hasn't, I'll send them a
> request to purge all xfree86_4.3.0-0pre1v5 (i386) uploads from
> queue/{unchecked,accepted}, and re-upload.
Thanks very much for the exhaustive explanation.
I am missing one piece of information, though -- how did 0pre1v5 (i386)
get targeted at unstable in the first place? The debian/changelog file
in the source package I uploaded certainly was not targeted there.
--
G. Branden Robinson | Don't use nuclear weapons to
Debian GNU/Linux | troubleshoot faults.
branden@debian.org | -- US Air Force Instruction 91-111
http://people.debian.org/~branden/ |
Attachment:
signature.asc
Description: Digital signature