Hello 68k porters and FTP masters, I tried to upload a package to etch-m68k but I got a REJECT.
My guess: python2.4_2.4.4-3_m68k was actually build in the past, but did not go to etch-m68k and have been removed since. I suspect I am supposed to do a binary-only NMU? But that means even if I had kept a copy of the first python2.4_2.4.4-3_m68k, it would get rejected. The issue is that it will not be obvious to know which packages need a binNMU instead of binary-upload, since there are no trace of the old packages. Cheers, -- Bill. <[EMAIL PROTECTED]> Imagine a large red swirl here. ----- Forwarded message from Debian Installer <[EMAIL PROTECTED]> ----- Envelope-to: [EMAIL PROTECTED] Delivery-date: Wed, 20 Jun 2007 00:53:58 +0200 X-Virus-Scanned: amavisd-new at math.u-bordeaux1.fr X-Sieve: CMU Sieve 2.3 X-Virus-Scanned: amavisd-new at math.u-bordeaux1.fr From: Debian Installer <[EMAIL PROTECTED]> To: Bill Allombert <[EMAIL PROTECTED]> X-DAK: dak process-unchecked X-Katie: $Revision: 1.65 $ X-DAK-Rejection: automatic (moo) X-Katie-Rejection: automatic (moo) Subject: python2.4_2.4.4-3_m68k.changes REJECTED Rejected: python2.4_2.4.4-3_m68k.changes: a file with this name already exists in the Done directory. === If you don't understand why your files were rejected, or if the override file requires editing, reply to this email. ----- End forwarded message -----
signature.asc
Description: Digital signature
