On Fri, Aug 19, 2022 at 04:43:17PM +0200, Andrej Shadura wrote: > 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. JTFR - Upstream released 12.0.4 in 2020, and they have reached 13.0.1 _now_ (after two years) Going by previous releases, the delta between one major release is atleast an year. And so reaching to 22.2.3 will take a very long time as well, if not _forever_ and that would mean keeping up with +really for several years. I do not think tagging this along with really is much better than adding in an epoch. (I personally find the former a bit more ugly for my taste) The only reverse-dependency of this package is "node-prosemirror-markdown" and so it would not be too much work if an epoch is introduced. -- Best, Nilesh
Attachment:
signature.asc
Description: PGP signature