Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak

[Tobias Frost <tobi@debian.org>]

Am Sat, Dec 09, 2023 at 12:15:29PM +0300 schrieb Igor B. Poretsky:
> Hello Tobias,
> 
> >>>>> "Tobias" == Tobias Frost <tobi@debian.org> writes:
> 
>     Tobias> The "-1" is the Debian revision; it is orthogonal to the
>     Tobias> upstream version, (except the rules where it resets to
>     Tobias> usually -1, of course)
> 
> So, what should I do if my package has not been yet sponsored, but a new
> upstream release actually has some sensible fixes? As I understand, I
> may update my upload on mentors.debian.net. But what should I do in
> debian/changelog? Should I add a new entry with a new upstream version
> or amend the one that closes the ITP bug? I think that the latter option
> is better. Am I right?

You amend it. To avoid ambigiouness:

Until the first upload is sponsored, you just keep a single changelog entry.
In the case of a new upstream version, you just change the version accordingly.

For example a fictional package foobar, updating from 1.0.0 to 1.0.1:

foobar (1.0.0-1) unstable; urgency=medium

 * Initial Package (Closes: #…)

would become:

foobar (1.0.1-1) unstable; urgency=medium

 * Initial Package (Closes: #…)

Version 1.0.0-1 will NOT be mentioned in d/changelog, as there are no changes
to the Debian package if there was no prior upload.


-- 
Cheers,
tobi