Processing of warzone2100_2.0.4-2_i386.changes

[Linas Žvirblis]

> warzone2100_2.0.4-2_i386.changes uploaded successfully to localhost

Umm... Why -2? I thought that the whole point was to avoid uploading
another revision of a package that is not yet in Debian.

> warzone2100 (2.0.4-3) UNRELEASED; urgency=low
> 
>   * NOT RELEASED YET
> 
>  -- Alexander Schmehl <alex at schmehl.info>  Mon,  4 Sep 2006 23:19:50 +0200

So... why is it here then?

> warzone2100 (2.0.4-2) unstable; urgency=low
> 
>   [Linas Žvirblis]
>   * fixing manpage
> 
>   [Alexander Schmehl]
>   * adding myself to uploads, so this won't be an NMU
> 
>  -- Alexander Schmehl <tolimar at debian.org>  Mon,  4 Sep 2006 17:55:58 +0200

What NMU? How is this upload different from a normal sponsored upload?

> warzone2100 (2.0.4-1) unstable; urgency=low
> 
>   * Initial release (Closes: #325935).
> 
>  -- Linas Žvirblis <0x0007 at gmail.com>  Sat, 26 Aug 2006 23:10:40 +0300

This one never entered 'unstable', as far as I know...

I do not want to sound paranoid, but this just feels wrong. Is it not
possible to reupload a normal -1 revision with a clean changelog? Or
does being in NEW count as being in Debian already?

It may be that I am simply thinking too much, but I suggest requesting
FTP masters to reject the package. I am more concerned about doing it
right than about pushing the package into Debian as soon as possible.