[Pkg-javascript-devel] Testing migrations

Pirate Praveen praveen at onenetbeyond.org
Fri Aug 23 18:37:44 BST 2019



On Fri, 23 Aug, 2019 at 12:05 PM, Utkarsh Gupta 
<guptautkarsh2102 at gmail.com> wrote:
> Hey,
> 
> On Fri 23 Aug, 2019, 12:00 Pirate Praveen, <praveen at onenetbeyond.org> 
> wrote:
>> 
>> 
>>  On 2019, ഓഗസ്റ്റ് 21 2:29:46 AM IST, Utkarsh Gupta 
>> <guptautkarsh2102 at gmail.com> wrote:
>>  >I can't seem to build. There are so many problems. Changed 
>> binaries,
>>  >then
>>  >local changes.
>>  >Not sure what's happening :P
>> 
>>  I have fixed node-d3 locally, will push soon.
>> 
>>  I had to add /usr/share/nodejs to node-resolve plugin in 
>> rollup.config.js, update debian/links and also create links during 
>> build for pkg-js-tools require test.
> 
> Geez.
> As far as I remember, some binary contents changed after each build. 
> Perhaps we need to add them to d/source/include-binaries?
> 

Now transpiling is correct but still autopktest fails. I think it is a 
bug in pkg-js-autopkgtest.

ln: failed to create symbolic link './node_modules': File exists

> 
> Best,
> Utkarsh
>> 





More information about the Pkg-javascript-devel mailing list