Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1179344
| From | Tobias Frost <tobi@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak |
| Date | 2023-12-19 19:30 +0100 |
| Message-ID | <HMN0S-eGNm-3@gated-at.bofh.it> (permalink) |
| References | (7 earlier) <HHxpL-bjv5-1@gated-at.bofh.it> <HA4Vz-5qzF-9@gated-at.bofh.it> <HJ1F7-cm55-3@gated-at.bofh.it> <HA4Vz-5qzF-9@gated-at.bofh.it> <HJ1F7-cm55-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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
Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak "Igor B. Poretsky" <poretsky@mlbox.ru> - 2023-11-14 18:00 +0100
Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak Tobias Frost <tobi@debian.org> - 2023-11-26 10:50 +0100
Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak "Igor B. Poretsky" <poretsky@mlbox.ru> - 2023-11-26 13:40 +0100
Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak Tobias Frost <tobi@debian.org> - 2023-11-26 15:50 +0100
Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak "Igor B. Poretsky" <poretsky@mlbox.ru> - 2023-12-01 06:50 +0100
Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak Tobias Frost <tobi@debian.org> - 2023-12-05 07:50 +0100
Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak "Igor B. Poretsky" <poretsky@mlbox.ru> - 2023-12-09 10:20 +0100
Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak Tobias Frost <tobi@debian.org> - 2023-12-19 19:30 +0100
Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak "Igor B. Poretsky" <poretsky@mlbox.ru> - 2023-12-20 02:10 +0100
Bug#1055951: RFS: multispeech/4.6.0-1 [ITP] -- Multilingual speech server for Emacspeak Samuel Thibault <sthibault@debian.org> - 2023-12-05 00:00 +0100
csiph-web