[Pkg-javascript-devel] Bug#973741: gitlab: Yarn hasn't been able to find a cache folder it can use

Pirate Praveen praveen at onenetbeyond.org
Thu Nov 19 18:02:20 GMT 2020



On 2020, നവംബർ 19 11:01:11 PM IST, Michael Prokop <mika at debian.org> wrote:
>Hi,
>
>* Pirate Praveen [Thu Nov 19, 2020 at 03:05:13PM +0530]:
>
>> As you already found out, the problem is in node-yarnpkg. The fix is
>> a bit hard though as node-yarnpkg currently ftbfs due to babel 7
>> transition.
>
>> A work around could be to install yarnpkg via npm. npm install -g
>> yarn and replace the yarnpkg command.
>
>I noticed that yarnpkg currently isn't part of Debian/testing
>(according to https://tracker.debian.org/pkg/node-yarnpkg due to
>"Updating node-yarnpkg introduces new bugs: #960120, #972952, #973741").
>
>It would be rather unfortunate if it wouldn't make it into bullseye.
>Sadly I can't really help with the mentioned bugreports myself, but is
>there a chance, to see yarnpkg back in Debian/testing (given that
>latest interaction in e.g. #960120 dates back to August) so it could
>make it into bullseye? :)

I can see 2 possibilities,

1. Someone make yarn 1.x build with babel 7
2. Yarn 2.x gets a stable release and it is updated

I'm not sure if either of it will happen in time for bullseye. I tried my best with option 1, but I'm not a js programmer to unblock it. I asked a few people for help, but was not successful in that attempt.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.



More information about the Pkg-javascript-devel mailing list