<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le mer. 25 mars 2020 à 10:39, Xavier <<a href="mailto:yadd@debian.org">yadd@debian.org</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Le 25/03/2020 à 10:32, Xavier a écrit :<br>
> Le 25/03/2020 à 10:26, Xavier a écrit :<br>
>> Le 25/03/2020 à 09:37, Xavier a écrit :<br>
>>> Le 04/03/2020 à 18:52, Mattia Rizzolo a écrit :<br>
>>>> On Wed, Mar 04, 2020 at 11:06:00PM +0530, Pirate Praveen wrote:<br>
>>>>> That is not correct. Xavier (yadd) proposed 3 solutions already. Hope he will share the relevant proposals.<br>
>>>><br>
>>>> Yes, the current one was proposed by him, as well as the one I linked<br>
>>>> below…<br>
>>>> I'm actually defending his work here :P<br>
>>><br>
>>> Hi and thanks ;-)<br>
>>><br>
>>> In next devscripts MR 178, I'm going to propose a complement to<br>
>>> "checksum" option to reduce long version:<br>
>>> * new line option: ctype which gives the type of component (nodejs for<br>
>>> now)<br>
>>> * if this ctype exists, uscan reads package.json to find current<br>
>>> component version<br>
>>><br>
>>> Tested with success with node-mongodb (both checksum and ctype), package<br>
>>> is up to date but a component changed. Current version is<br>
>>> 3.5.5+~cs11.12.18-1, uscan detects change:<br>
>>><br>
>>> $ uscan --report<br>
>>> uscan: Newest version of bson on remote site is 1.1.4, local version<br>
>>> is 1.1.3<br>
>>> <a href="http://uscan.pl" rel="noreferrer" target="_blank">uscan.pl</a>: => Newer package available from<br>
>>> <a href="https://registry.npmjs.org/bson/-/bson-1.1.4.tgz" rel="noreferrer" target="_blank">https://registry.npmjs.org/bson/-/bson-1.1.4.tgz</a><br>
>>><br>
>>> Part of DEHS output (checksum changed well):<br>
>>><br>
>>> <package>node-mongodb</package><br>
>>> <debian-uversion>3.5.5+~cs11.12.18</debian-uversion><br>
>>> <debian-mangled-uversion>3.5.5+~cs11.12.18</debian-mangled-uversion><br>
>>> <upstream-version>3.5.5+~cs11.12.19</upstream-version><br>
>>><br>
>>><br>
>><br>
>> And for acorn, last version becomes 7.1.1+~cs12.20.3+ds-1 ;-)<br>
> <br>
> ctype permits to download current version as well (not "ignore" without<br>
> ctype):<br>
> <br>
> ~/acorn $ uscan --report --download-current-version --dehs<br>
> [...]<br>
> <debian-uversion>6.2.1+ds</debian-uversion><br>
> <debian-mangled-uversion>6.2.1</debian-mangled-uversion><br>
> <upstream-version>6.2.1+~cs11.24.3</upstream-version><br>
> <upstream-url><a href="https://github.com/acornjs/acorn/archive/6.2.1.tar.gz" rel="noreferrer" target="_blank">https://github.com/acornjs/acorn/archive/6.2.1.tar.gz</a></upstream-url><br>
> <decoded-checksum><br>
> 0.4.0+~4.0.0+~1.0.0+~5.0.1+~1.7.0+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0<br>
> </decoded-checksum><br>
> [...]<br>
<br>
and a download works (and fix +ds) and then debian version is<br>
6.2.1+ds+~cs11.24.3 which is > to current version, this permits migration:<br>
<br>
~/acorn $ uscan --download-current-version<br>
mv ../acorn_6.2.1+ds.orig.tar.xz to ../acorn_6.2.1+ds+~cs11.24.3.orig.tar.xz<br>
mv ../acorn_0.4.0+ds.orig-node-acorn-bigint.tar.xz to<br>
../acorn_6.2.1+ds+~cs11.24.3.orig-node-acorn-bigint.tar.xz<br>
mv ../acorn_4.0.0+really4.0.0+ds.orig-node-acorn-dynamic-import.tar.xz<br>
to ../acorn_6.2.1+ds+~cs11.24.3.orig-node-acorn-dynamic-import.tar.xz<br>
mv ../acorn_1.0.0+ds.orig-node-acorn-import-meta.tar.xz to<br>
../acorn_6.2.1+ds+~cs11.24.3.orig-node-acorn-import-meta.tar.xz<br>
mv ../acorn_5.0.1+ds.orig-node-acorn-jsx.tar.xz to<br>
../acorn_6.2.1+ds+~cs11.24.3.orig-node-acorn-jsx.tar.xz<br>
mv ../acorn_1.7.0+ds.orig-node-acorn-node.tar.xz to<br>
../acorn_6.2.1+ds+~cs11.24.3.orig-node-acorn-node.tar.xz<br>
mv ../acorn_0.1.1+ds.orig-node-acorn-private-class-elements.tar.xz to<br>
../acorn_6.2.1+ds+~cs11.24.3.orig-node-acorn-private-class-elements.tar.xz<br>
mv ../acorn_0.3.1+ds.orig-node-acorn-class-fields.tar.xz to<br>
../acorn_6.2.1+ds+~cs11.24.3.orig-node-acorn-class-fields.tar.xz<br>
mv ../acorn_0.2.0+ds.orig-node-acorn-static-class-features.tar.xz to<br>
../acorn_6.2.1+ds+~cs11.24.3.orig-node-acorn-static-class-features.tar.xz<br>
mv ../acorn_0.1.0+ds.orig-node-acorn-export-ns-from.tar.xz to<br>
../acorn_6.2.1+ds+~cs11.24.3.orig-node-acorn-export-ns-from.tar.xz<br>
mv ../acorn_0.3.0+ds.orig-node-acorn-numeric-separator.tar.xz to<br>
../acorn_6.2.1+ds+~cs11.24.3.orig-node-acorn-numeric-separator.tar.xz<br>
mv ../acorn_0.3.0+ds.orig-node-acorn-private-methods.tar.xz to<br>
../acorn_6.2.1+ds+~cs11.24.3.orig-node-acorn-private-methods.tar.xz<br>
<br></blockquote><div><br></div><div>👍<br></div><div>Could you tell how acorn 6.2.1+ds+0.4.0+~4.0.0+~1.0.0+~5.0.1+~1.7.0+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0</div><div>becomes 6.2.1+ds+~cs11.24.3 : how 11.24.3 is built ?</div><div><br></div><div>Thanks,</div><div>Jérémy</div></div></div>