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

2022-05-20 Thread Michael Biebl
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 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 n

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

2022-05-20 Thread Pirate Praveen
On വ്യാ, മേയ് 19 2022 at 04:39:23 വൈകു -05:00:00 -05:00:00, Richard Laager 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

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

2022-05-19 Thread Richard Laager
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 frequ

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

2022-05-19 Thread Pirate Praveen
Hi, While embedding @types/markdown-it in node-markdown-it we made a mistake in calculating the resulting upstream version (since uscan was not working for downloading current version it was calculated manually). So current version in the archive is 22.2.3+dfsg+~12.2.3-1 The fixed version we