Re: Epoch for node-markdown-it

["Andrej Shadura" <andrew@shadura.me>]

Hi,

On Fri, 19 Aug 2022, at 16:37, Jonas Smedegaard wrote:
> Quoting Yadd (2022-08-19 10:21:17)
>> some months ago, a bad upstream tag changed node-markdown-it version to 
>> 22.2.3 instead of 10.0.0. So I'd like to change node-markdown-it version 
>> into 1:13.0.1
>
> Since upstream is already at 10, is it unlikely that they will reach 22
> in the foreseeable future?
>
> What I am getting at is that introducing an epoch is a pain *forever*
> (all dependent packages must then *forever* remember to add "1:" prefix)
> wheread converting the accidental too-high major version into
> pseudo-epoch "22.really." will last only until upstream catches up.

I agree, adding an epoch in this package doesn’t seem appropriate or necessary.

-- 
Cheers,
  Andrej