Bug#310489: Uploading a binNMU
On Tue, May 24, 2005 at 04:09:54PM -0600, dann frazier wrote:
> I'm going to go ahead and binNMU ssh using the 3.8.1p1-8.sarge.5
> version string. Please skip this version in your next MU.
Sorry, I hadn't noticed this bug yet (note I've done all the openssh
uploads of late, although I'm Uploader: not Maintainer:, so your earlier
Cc didn't reach me).
The versioning scheme in use on the sarge branch was certainly a
mistake, given how the archive reacts to it ...
The next upload of openssh on that branch is more likely to be a
security upload; I don't have any more maintainer uploads planned for
sarge at the moment. I guess the security team will just have to cope
with that when the time comes.
Have you audited the rest of the archive to ensure that nothing else
relies on the piece of OpenSSL's ABI that changed on ia64? It seems
surprising to me that this could be the only occurrence. However, if the
ia64 port team thinks changing applications is the way to go then that's
their call.
Cheers,
--
Colin Watson [cjwatson@debian.org]
Reply to: