Re: Adding epoch to node-markdown-it to correct a wrong upstream version

[Michael Biebl <biebl@debian.org>]

Am 20.05.22 um 11:23 schrieb Pirate Praveen:
> On വ്യാ, മേയ് 19 2022 at 04:39:23 വൈകു -05:00:00 -05:00:00, Richard Laager 
> <rlaager@debian.org> wrote:
> > On 5/19/22 05:42, Pirate Praveen wrote:
> > > So current version in the archive is 22.2.3+dfsg+~12.2.3-1
> > >
> > > The fixed version we want is 10.0.0+dfsg+~cs16.6.17-1
> >
> > I have no dog in this fight as they say, but...
> >
> > How fast does upstream bump versions? With a 10.x, I wonder if it 
> > might be relatively frequently. Would they likely exceed 22 in the 
> > near future? If so, you might just do 
> > 22.3+really10.0.0+dfsg+~cs16.6.17-1 and when they get to 23, it goes 
> > back to normal, without the epoch.
>
> You can see the release history here 
> https://www.npmjs.com/package/markdown-it?activeTab=versions
>
> 13.0.0 - a month ago
> 12.0.0 - 2 years ago
> 11.0.0 - 2 years ago
> 10.0.0 - 3 years ago
>
> So I don't think waiting ~10 years (or even 5 years) is a reasonable 
> option here.

You could ask your upstream to bump the version number to 23.
But I can understand if you don't want to bother your upstream with this 
Debian specific problem.

Regards,
Michael

Attachment: OpenPGP_signature
Description: OpenPGP digital signature