[Pkg-javascript-devel] Bug#977781: Bug#977781: Bug#977781: real issue is, it does not pull not-yet-cached modules

Paolo Greppi paolo.greppi at libpf.com
Tue Dec 22 06:16:54 GMT 2020


Hi Akshay, many thanks for the debugging ! see below

Il 22/12/20 06:06, Akshay S Dinesh ha scritto:
> 
>> There are some 4 pipes before the finish event. I'm looking through each one of them to see if there's a mismatch.
>>
> 
> It seems to be tar-fs
> 
> Please see https://salsa.debian.org/js-team/node-yarnpkg/-/merge_requests/4
> 
> I've just downloaded the latest version from the github of tar-fs and replace in the directory. Not sure if this is the way to do it.

It's a pity the salsa Continuous Integration has failed on your fork.

I noticed this message in the extract-source job log:

   gbp:error: upstream/1.22.10+_cs18.39.16 is not a valid treeish

indeed your fork only has 33 tags, whereas js-team/node-yarnpkg has 37.
Please pull those tags and push them to your fork, then force restart the CI pipeline.
This would help us to see if your proposed fix works.

As to upgrading tar-fs, it is possible that some other dependency we updated here and there requires it.
Upstream are currently using 1.16.3:
https://github.com/yarnpkg/yarn/blob/master/yarn.lock#L7137
whereas we were already using version 2

If we want to upgrade tar-fs we need to upgrade its sources and then import them in upstream and master branches:
https://wiki.debian.org/Javascript/GroupSourcesTutorial

Paolo



More information about the Pkg-javascript-devel mailing list