Le 25/03/2020 à 09:37, Xavier a écrit :
> Le 04/03/2020 à 18:52, Mattia Rizzolo a écrit :
>> On Wed, Mar 04, 2020 at 11:06:00PM +0530, Pirate Praveen wrote:
>>> That is not correct. Xavier (yadd) proposed 3 solutions already. Hope he 
>>> will share the relevant proposals.
>>
>> Yes, the current one was proposed by him, as well as the one I linked
>> below…
>> I'm actually defending his work here :P
> 
> Hi and thanks ;-)
> 
> In next devscripts MR 178, I'm going to propose a complement to
> "checksum" option to reduce long version:
>  * new line option: ctype which gives the type of component (nodejs for
>    now)
>  * if this ctype exists, uscan reads package.json to find current
>    component version
> 
> Tested with success with node-mongodb (both checksum and ctype), package
> is up to date but a component changed. Current version is
> 3.5.5+~cs11.12.18-1, uscan detects change:
> 
>   $ uscan --report
>   uscan: Newest version of bson on remote site is 1.1.4, local version
>          is 1.1.3
>   uscan.pl:    => Newer package available from
>         https://registry.npmjs.org/bson/-/bson-1.1.4.tgz
> 
> Part of DEHS output (checksum changed well):
> 
>   <package>node-mongodb</package>
>   <debian-uversion>3.5.5+~cs11.12.18</debian-uversion>
>   <debian-mangled-uversion>3.5.5+~cs11.12.18</debian-mangled-uversion>
>   <upstream-version>3.5.5+~cs11.12.19</upstream-version>
> 
> 

And for acorn, last version becomes 7.1.1+~cs12.20.3-1 ;-)

Reply via email to