Re: call for epoch (was Re: Bug#915553: ITP: pd-csound -- Csound external for Pure Data)
- Date: Tue, 4 Dec 2018 23:22:19 +0100
- From: Adam Borowski <kilobyte@xxxxxxxxxx>
- Subject: Re: call for epoch (was Re: Bug#915553: ITP: pd-csound -- Csound external for Pure Data)
On Tue, Dec 04, 2018 at 10:49:44PM +0100, IOhannes m zmölnig (Debian/GNU) wrote:
> On 12/4/18 9:34 PM, Simon McVittie wrote:
> > If they agree that this is confusing, they might be willing to re-version
> > to 7.01.0 or something, so that version numbers keep going up.
> > If they are unwilling to change the version number, then bumping the
> > epoch seems like a correct Debian-level workaround for the version
> > numbering scheme having been reset.
> i asked upstream, and their answer is:
> > The version was always 1.00 even when it was inside Csound. Minor
> > changes made it go to 1.01 when we moved it out. It is not the same as
> > the Csound version. So I am not really keen on changing this.
> so it seems that the Debian *binary* package should have used a
> different version than the source package in the first place.
> it also gives me confidence, that the upstream version number will not
> increment much in the next time, which should keep us safe from re-using
> the same version (without epoch)
There already is an epoch, you can't remove it. On the other hand, with the
damage already done, there's little reason not to bump it.
⣾⠁⢠⠒⠀⣿⡁ Ivan was a worldly man: born in St. Petersburg, raised in
⢿⡄⠘⠷⠚⠋⠀ Petrograd, lived most of his life in Leningrad, then returned
⠈⠳⣄⠀⠀⠀⠀ to the city of his birth to die.