that won't work...
You can't re-upload the same version number for a given architecture, or the
installer will reject it. The easiest fix in this case is to whack the
changelog, inserting a new entry with a non-maintainer version number, in this
case something like 1.5.4-4.1, with the changelog entry indicating that you're
doing a non-maintainer upload to correct an architecture-specific problem. Do
not upload source, just the binaries... this will cause the installer to do the
right thing, doesn't screw up version numbering elsewhere, and requires no
manual intervention by the team that maintains the install process on master.
------- Forwarded Message
Received: from master.debian.org (firstname.lastname@example.org [220.127.116.11])
by winfree.gag.com (8.8.8/8.8.8/Debian/GNU) with SMTP id MAA14856
for <email@example.com>; Sat, 15 Aug 1998 12:54:37 -0600
Received: (qmail 31095 invoked by uid 878); 15 Aug 1998 18:54:35 -0000
Date: 15 Aug 1998 18:54:35 -0000
From: Debian Installer <firstname.lastname@example.org>
To: Bdale Garbee <email@example.com>
Subject: sudo_1.5.4-4_arm.changes REJECTED
Mapping frozen to unstable
Rejected: sudo_1.5.4-4_arm.deb: Old version `1.5.4-4' >= new version `1.5.4-4'.
If you don't understand why your files were rejected, or if the
override file requires editing, reply to this email.
Your rejected files are in Incoming/REJECT/. (Some may also be in
Incoming/ if your .changes file was unparsable.) If only some of the
files need to repaired, you may move any good files back to Incoming/.
Please remove any bad files from Incoming/REJECT/.
------- End of Forwarded Message