[Pkg-javascript-devel] Bug#977027: Bug#977027: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"
Le jeu. 6 avr. 2023 à 11:24, Paul Gevers a écrit : > > Control: tags -1 pending patch > > On 06-04-2023 12:54, Paul Gevers wrote: > > I'm going to prepare NMU's for rhino and dojo and upload to DELAYED/5 > > Please find the debdiffs attached. Go ahead > > Paul > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#977027: Bug#977027: rhino breaks dojo autopkgtest: Cannot set property "dojo" of null to "[object Object]"
Le dim. 26 mars 2023 à 21:39, Markus Koschany a écrit : > Hi Graham, > > Am Sonntag, dem 26.03.2023 um 19:28 +0200 schrieb Graham Inggs: > > Hi Markus > > > > On Sun, 26 Mar 2023 at 16:34, Markus Koschany wrote: > > > 1. There is no transition needed because only shrinksafe is affected > by the > > > new > > > rhino version. > > > > How did you determine this? > > Rhino 1.7.14 was mostly API compatible meaning I only had to fix an issue > in > closure-compiler. All other packages can be built from source without > modifications. I didn't find any other runtime / ABI issues so far. > > > > > > 2. shrinksafe has no reverse-dependencies > > > > That is true, but src:dojo has ledgersmb and tt-rss as > reverse-dependencies. > > I used codesearch.debian.net and found only documentation or other minor > references of shrinksafe in affected packages. > > https://codesearch.debian.net/search?q=shrinksafe&literal=1 > > Since all Java tests in dojo pass after the rebuild and almost all of the > code > in dojo is Javascript anyway, I don't see how ledgersmb and tt-rss can be > affected by the new rhino version. Wouldn't those packages depend on rhino > in > some way? To me it seems rhino is only required to build shrinksafe which > can > be used for compressing Javascript files. But maybe the dojo maintainers > can > chime in here. > Yes shrinksafe is only used for compression. Bastien > > > Regards, > > Markus > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel > -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#996909: Bug#996909: acorn: Invalid package section for node-debbundle-acorn
Go nmu I will be far from a computer a few days... Do no t forger to apply to salsa or at least do a merge request Thanks Le mer. 20 oct. 2021 à 18:06, Steve Langasek a écrit : > Package: acorn > Version: 8.5.0+ds+~cs24.17.6-2 > Severity: normal > Tags: patch > User: ubuntu-de...@lists.ubuntu.com > Usertags: origin-ubuntu jammy ubuntu-patch > > Hi Bastien, > > The latest version of acorn has node-debbundle-acorn listed in Section: > oldlib. This is invalid; the correct section name is 'oldlibs'. In the > Debian archive, this is not an issue because the Debian archive applies > overrides to all packages (indeed, I see the archive still lists this > package as 'Section: javascript'), but in Ubuntu this blocks the binary > package from being uploaded. So I have applied the attached patch for > Ubuntu, which should also be correct for Debian. > > Cheers, > -- > Steve Langasek Give me a lever long enough and a Free OS > Debian Developer to set it on, and I can move the world. > Ubuntu Developer https://www.debian.org/ > slanga...@ubuntu.com vor...@debian.org > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel > -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#996836: Bug#996836: node-webpack: webpack embeds binary files in es-module-lexer component
Le mar. 19 oct. 2021 à 16:12, Yadd a écrit : > Source: node-webpack > Version: 5.58.2+~cs5.11.7-1 > Severity: serious > Justification: DFSG > > webpack 5.58 uses es-module-lexer. For now, this component is downloaded > including some binary files (WASM,...). This should be fixed before > going to unstable. > I really hate wasm... What is the source language ? Rust ? > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel > -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#994974: Bug#994974: node-define-property: Please deembed and fix vulnereability
Le ven. 24 sept. 2021 à 08:16, Jonas Smedegaard a écrit : > > Hi Bastien, > > Quoting Bastien Roucariès (2021-09-24 09:49:37) > > Package: node-define-property > > Severity: serious > > Tags: security upstream fixed-upstream > > Justification: security bug > > Forwarded: https://github.com/jonschlinkert/define-property/pull/6 > > X-Debbugs-Cc: Debian Security Team > > > > Dear Maintainer, > > > > According to > > https://www.npmjs.com/advisories/1490 > > node-define-property is vulnerable > > > > > > Because it embed small modules that are vulnerable. > > Sorry, I don't see the advisory mentioning define-property anywhere, and > don't see our actual code calling "constructor" anywhere, as seems to be > what the security in the advisory is about. > > Your reference to a PR 6 seems to be tied to an older version of > define-property than in Debian. > > Please elaborate how this vulnerability affects code in Debian. > > > > Embdeding is bad and we have here another proof > > I was puzzled at first, but think I now understand your point: > > Embedding in general is not necessarily bad but is complex to do right - > embedding without proper tracking is bad. Yes it is lack of README.Sources, lack of lintian tag > > What confused me is that at first I thought you were ranting about > Debian practice of embedding, but it seems you are ranting about lack of > tracking of (either upstream or Debian-introduced) embedding. Do I > understand that correctly? Yes it is Fixed nevertheless > > Thanks for reporting, regardless, > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: npm: segfault during extract on i386
Le mar. 21 sept. 2021 à 08:58, Ondrej Zary a écrit : > > On Tuesday 21 September 2021, Bastien ROUCARIES wrote: > > Le mar. 21 sept. 2021 à 07:55, Ondrej Zary a écrit : > > > > > > On Monday 20 September 2021, Bastien Roucariès wrote: > > > > Le lundi 20 septembre 2021, 19:32:52 UTC Bastien ROUCARIES a écrit : > > > > Could you try one by one the following untested patch. Please compile > > > > and run > > > > the testsuite. > > > > > > The first one fails to compile: > > > In file included from ../src/util-inl.h:28, > > > from ../src/aliased_buffer.h:7, > > > from ../src/memory_tracker.h:12, > > > from ../src/memory_tracker-inl.h:6, > > > from ../src/base_object.h:27, > > > from ../src/async_wrap.h:27, > > > from ../src/async_wrap-inl.h:27, > > > from ../src/async_wrap.cc:22: > > > ../src/util.h:210:11: error: ‘Persistent’ does not name a type; did you > > > mean ‘gethostent’? > > > const Persistent& persistent); > > > > Add on the top of the files using v8::Global; > > and replace const Persistent& persistent by const > > Global& persistent > > You probably mean Global& persistent. > > Then ENVIRONMENT_STRONG_PERSISTENT_VALUES is undefined: > In file included from ../src/env-inl.h:28, > from ../src/base_object-inl.h:28, > from ../src/async_wrap-inl.h:28, > from ../src/async_wrap.cc:22: > ../src/env.h:1036:40: error: ‘V’ has not been declared >ENVIRONMENT_STRONG_PERSISTENT_VALUES(V) > ^ > ../src/env.h:1036:41: error: ISO C++ forbids declaration of > ‘ENVIRONMENT_STRONG_PERSISTENT_VALUES’ with no type [-fpermissive] >ENVIRONMENT_STRONG_PERSISTENT_VALUES(V) > ^ > ../src/env.h:1036:41: error: expected ‘;’ at end of member declaration >ENVIRONMENT_STRONG_PERSISTENT_VALUES(V) :S Jeremy backport will be hard. If we use std::shared_ptr we leak memory -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: npm: segfault during extract on i386
Le mar. 21 sept. 2021 à 07:55, Ondrej Zary a écrit : > > On Monday 20 September 2021, Bastien Roucariès wrote: > > Le lundi 20 septembre 2021, 19:32:52 UTC Bastien ROUCARIES a écrit : > > Could you try one by one the following untested patch. Please compile and > > run > > the testsuite. > > The first one fails to compile: > In file included from ../src/util-inl.h:28, > from ../src/aliased_buffer.h:7, > from ../src/memory_tracker.h:12, > from ../src/memory_tracker-inl.h:6, > from ../src/base_object.h:27, > from ../src/async_wrap.h:27, > from ../src/async_wrap-inl.h:27, > from ../src/async_wrap.cc:22: > ../src/util.h:210:11: error: ‘Persistent’ does not name a type; did you mean > ‘gethostent’? > const Persistent& persistent); Add on the top of the files using v8::Global; and replace const Persistent& persistent by const Global& persistent >^~ > > > -- > Ondrej Zary -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Could you try first to apply https://github.com/nodejs/node/commit/c60780ff52 And see if the reject are bad ? Bastien Le lun. 20 sept. 2021 à 19:15, Ondrej Zary a écrit : > > > > On Monday 20 September 2021 19:31:56 Bastien ROUCARIES wrote: > > Le lun. 20 sept. 2021 à 17:28, Jérémy Lal a écrit : > > > > > > > > > > > > Le lun. 20 sept. 2021 à 19:15, Ondrej Zary a écrit : > > > > > > > > On Monday 20 September 2021 16:56:18 Bastien ROUCARIES wrote: > > > > > Le lun. 20 sept. 2021 à 14:24, Ondrej Zary a écrit : > > > > > > > > > > > > On Monday 20 September 2021, Bastien ROUCARIES wrote: > > > > > > > Could you try to apply > > > > > > > > > > > > > > https://github.com/nodejs/node/commit/aa4611cccbcb197df51a9f7056d019005d91acf4 > > > > > > > > > > > > > > I think it describe that you see > > > > > > > > > > > > Does not apply, unfortunately. There's no node_dir.cc file and also > > > > > > no BaseObjectPtr definition. > > > > > > > > > > Ok as band aid could you replace in the patch BaseObjectPtr by > > > > > std:shared_ptr > > > > > > > > Biggest problem is the missing node_dir.cc file. The patched code from > > > > that file is not present at all in nodejs 10. > > > > > > Wild guess, try only that part: > > > > > > - delete wrap_; > > > + wrap_->Detach(); > > > + wrap_.reset(); > > Yes but reset is std:shared_ptr > > > > But I agree it is the main part of the patch > > Detach() is also not defined in src/base_object.h > > > -- > Ondrej Zary > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: npm: segfault during extract on i386
Le lun. 20 sept. 2021 à 17:28, Jérémy Lal a écrit : > > > > Le lun. 20 sept. 2021 à 19:15, Ondrej Zary a écrit : > > > > On Monday 20 September 2021 16:56:18 Bastien ROUCARIES wrote: > > > Le lun. 20 sept. 2021 à 14:24, Ondrej Zary a écrit : > > > > > > > > On Monday 20 September 2021, Bastien ROUCARIES wrote: > > > > > Could you try to apply > > > > > > > > > > https://github.com/nodejs/node/commit/aa4611cccbcb197df51a9f7056d019005d91acf4 > > > > > > > > > > I think it describe that you see > > > > > > > > Does not apply, unfortunately. There's no node_dir.cc file and also no > > > > BaseObjectPtr definition. > > > > > > Ok as band aid could you replace in the patch BaseObjectPtr by > > > std:shared_ptr > > > > Biggest problem is the missing node_dir.cc file. The patched code from that > > file is not present at all in nodejs 10. > > Wild guess, try only that part: > > - delete wrap_; > + wrap_->Detach(); > + wrap_.reset(); Yes but reset is std:shared_ptr But I agree it is the main part of the patch > Jérémy > -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le lun. 20 sept. 2021 à 17:15, Ondrej Zary a écrit : > > On Monday 20 September 2021 16:56:18 Bastien ROUCARIES wrote: > > Le lun. 20 sept. 2021 à 14:24, Ondrej Zary a écrit : > > > > > > On Monday 20 September 2021, Bastien ROUCARIES wrote: > > > > Could you try to apply > > > > > > > > https://github.com/nodejs/node/commit/aa4611cccbcb197df51a9f7056d019005d91acf4 > > > > > > > > I think it describe that you see > > > > > > Does not apply, unfortunately. There's no node_dir.cc file and also no > > > BaseObjectPtr definition. > > > > Ok as band aid could you replace in the patch BaseObjectPtr by > > std:shared_ptr > > Biggest problem is the missing node_dir.cc file. The patched code from that > file is not present at all in nodejs 10. According to https://github.com/nodejs/node/commit/b76a2e502c6f227f7df5f35ac3bbb0dcb2a8372d#diff-12768848757b514f1f042fddf06af34b9ba1d395113539ee98ff4bde165d1d4d it is not needed in old nodejs because dir was not async... Bastien > > -- > Ondrej Zary > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le lun. 20 sept. 2021 à 15:00, Bastien ROUCARIES a écrit : > > Le lun. 20 sept. 2021 à 14:24, Ondrej Zary a écrit : > > > > On Monday 20 September 2021, Bastien ROUCARIES wrote: > > > Could you try to apply > > > > > > https://github.com/nodejs/node/commit/aa4611cccbcb197df51a9f7056d019005d91acf4 [kapouer][jonas] Do you think it could be backported using std::share_ptr ? Superficially it seems semantic equivalent, but I am unease Bastien > > > > > > I think it describe that you see > > > > Does not apply, unfortunately. There's no node_dir.cc file and also no > > BaseObjectPtr definition. > > Ok as band aid could you replace in the patch BaseObjectPtr by > std:shared_ptr > > Bastien > > > > -- > > Ondrej Zary > > > > -- > > Pkg-javascript-devel mailing list > > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le lun. 20 sept. 2021 à 14:24, Ondrej Zary a écrit : > > On Monday 20 September 2021, Bastien ROUCARIES wrote: > > Could you try to apply > > > > https://github.com/nodejs/node/commit/aa4611cccbcb197df51a9f7056d019005d91acf4 > > > > I think it describe that you see > > Does not apply, unfortunately. There's no node_dir.cc file and also no > BaseObjectPtr definition. Ok as band aid could you replace in the patch BaseObjectPtr by std:shared_ptr Bastien > -- > Ondrej Zary > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Could you try to apply https://github.com/nodejs/node/commit/aa4611cccbcb197df51a9f7056d019005d91acf4 I think it describe that you see Bastien Le lun. 20 sept. 2021 à 12:51, Ondrej Zary a écrit : > > > Ok are you on IRC ? I am as rouca on #debian-js channel > > No, I'm not. > > > Install the debug symbols of nodejs and libuv (if available) and try > > to run valgrind with --smc-check=all --read-var-info=yes > > --track-origins=yes > > # runuser -u gitlab -- sh -c 'valgrind --smc-check=all --read-var-info=yes > --trace-children=yes --track-origins=yes yarnpkg install' > ==3423== Memcheck, a memory error detector > ==3423== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. > ==3423== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info > ==3423== Command: /usr/bin/yarnpkg install > ==3423== > ==3423== Memcheck, a memory error detector > ==3423== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. > ==3423== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info > ==3423== Command: /usr/bin/node /usr/bin/yarnpkg install > ==3423== > yarn install v1.13.0 > [1/5] Validating package.json... > [2/5] Resolving packages... > [3/5] Fetching packages... > [---] > 0/520==3423== Invalid read of size 4 > ==3423==at 0x4556B5B: node::fs::FSReqWrap::~FSReqWrap() (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3423==by 0x4547A42: node::fs::FSReqAfterScope::~FSReqAfterScope() (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3423==by 0x45484FD: node::fs::AfterInteger(uv_fs_s*) (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3423==by 0x556170F: uv__work_done (threadpool.c:313) > ==3423==by 0x55657FD: uv__async_io.part.0 (async.c:118) > ==3423==by 0x5575527: uv__io_poll (linux-core.c:378) > ==3423==by 0x55661C5: uv_run (core.c:370) > ==3423==by 0x4515C75: node::Start(v8::Isolate*, node::IsolateData*, > std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > const&, > std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > const&) (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3423==by 0x4513C96: node::Start(int, char**) (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3423==by 0x8049157: main (in /usr/bin/node) > ==3423== Address 0x410 is not stack'd, malloc'd or (recently) free'd > ==3423== > ==3423== > ==3423== Process terminating with default action of signal 11 (SIGSEGV) > ==3423== Access not within mapped region at address 0x410 > ==3423==at 0x4556B5B: node::fs::FSReqWrap::~FSReqWrap() (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3423==by 0x4547A42: node::fs::FSReqAfterScope::~FSReqAfterScope() (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3423==by 0x45484FD: node::fs::AfterInteger(uv_fs_s*) (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3423==by 0x556170F: uv__work_done (threadpool.c:313) > ==3423==by 0x55657FD: uv__async_io.part.0 (async.c:118) > ==3423==by 0x5575527: uv__io_poll (linux-core.c:378) > ==3423==by 0x55661C5: uv_run (core.c:370) > ==3423==by 0x4515C75: node::Start(v8::Isolate*, node::IsolateData*, > std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > const&, > std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > const&) (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3423==by 0x4513C96: node::Start(int, char**) (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3423==by 0x8049157: main (in /usr/bin/node) > ==3423== If you believe this happened as a result of a stack > ==3423== overflow in your program's main thread (unlikely but > ==3423== possible), you can try to increase the size of the > ==3423== main thread stack using the --main-stacksize= flag. > ==3423== The main thread stack size used in this run was 8388608. > ==3423== Invalid read of size 1 > ==3423==at 0x786A6A4: check_free (dlerror.c:189) > ==3423==by 0x786ABD8: free_key_mem (dlerror.c:221) > ==3423==by 0x786ABD8: __dlerror_main_freeres (dlerror.c:239) > ==3423==by 0x7CA4667: __libc_freeres (in > /usr/lib/i386-linux-gnu/libc-2.28.so) > ==3423==by 0x402D1DE: _vgnU_freeres (in > /usr/lib/i386-linux-gnu/valgrind/vgpreload_core-x86-linux.so) > ==3423== Address 0x16b6b3 is not stack'd, malloc'd or (recently) free'd > ==3423== > ==3423== > ==3423== Process terminating with default action of signal 11 (SIGSEGV) > ==3423== Access not within mapped region at address 0x16B6B3 > ==3423==at 0x786A6A4: check_free (dlerror.c:189) > ==3423==by 0x786ABD8: free_key_mem (dlerror.c:221) > ==3423==by 0x786ABD8: __dlerror_main_freeres (dlerror.c:239) > ==3423==by 0x7CA4667: __libc_freeres (in > /usr/lib/i386-linux-gnu/libc-2.28.so) > ==3423==by 0x402D1DE: _vgnU_freeres (in > /us
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Ok are you on IRC ? I am as rouca on #debian-js channel Install the debug symbols of nodejs and libuv (if available) and try to run valgrind with --smc-check=all --read-var-info=yes --track-origins=yes Bastien Le lun. 20 sept. 2021 à 11:57, Ondrej Zary a écrit : > > > And try to rebuild the whole libuv and nodejs with -fstack-protector-all > > Does not print anything other than Segmentation fault. > > -- > Ondrej Zary > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le lun. 20 sept. 2021 à 10:39, Ondrej Zary a écrit : > > > Ok now try to run the whole thing against valgrind... > Seems that valgrind does not work with asan: > > $ LD_PRELOAD=/usr/lib/i386-linux-gnu/libasan.so.5.0.0 valgrind yarnpkg install > ==752== Memcheck, a memory error detector > ==752== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. > ==752== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info > ==752== Command: /usr/bin/yarnpkg install > ==752== > ==752==ASan runtime does not come first in initial library list; you should > either link runtime to your application or manually preload it with > LD_PRELOAD. > ==752== > ==752== HEAP SUMMARY: > ==752== in use at exit: 0 bytes in 0 blocks > ==752== total heap usage: 0 allocs, 0 frees, 0 bytes allocated > ==752== > ==752== All heap blocks were freed -- no leaks are possible > ==752== > ==752== For counts of detected and suppressed errors, rerun with: -v > ==752== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0) > > valgrind with clean libuv1 (no asan): > runuser -u gitlab -- sh -c 'valgrind --trace-children=yes yarnpkg install' > ==3163== Memcheck, a memory error detector > ==3163== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. > ==3163== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info > ==3163== Command: /usr/bin/yarnpkg install > ==3163== > ==3163== Memcheck, a memory error detector > ==3163== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. > ==3163== Using Valgrind-3.14.0 and LibVEX; rerun with -h for copyright info > ==3163== Command: /usr/bin/node /usr/bin/yarnpkg install > ==3163== > yarn install v1.13.0 > [1/5] Validating package.json... > [2/5] Resolving packages... > [3/5] Fetching packages... > [---] > 0/520==3163== Invalid read of size 4 > ==3163==at 0x4556B5B: node::fs::FSReqWrap::~FSReqWrap() (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3163==by 0x4547A42: node::fs::FSReqAfterScope::~FSReqAfterScope() (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3163==by 0x45484FD: node::fs::AfterInteger(uv_fs_s*) (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3163==by 0x556170F: uv__work_done (in > /usr/lib/i386-linux-gnu/libuv.so.1.0.0) > ==3163==by 0x55657FD: ??? (in /usr/lib/i386-linux-gnu/libuv.so.1.0.0) > ==3163==by 0x5575527: uv__io_poll (in > /usr/lib/i386-linux-gnu/libuv.so.1.0.0) > ==3163==by 0x55661C5: uv_run (in /usr/lib/i386-linux-gnu/libuv.so.1.0.0) > ==3163==by 0x4515C75: node::Start(v8::Isolate*, node::IsolateData*, > std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > const&, > std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > const&) (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3163==by 0x4513C96: node::Start(int, char**) (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3163==by 0x8049157: main (in /usr/bin/node) > ==3163== Address 0x1085 is not stack'd, malloc'd or (recently) free'd > ==3163== > ==3163== > ==3163== Process terminating with default action of signal 11 (SIGSEGV) > ==3163== Access not within mapped region at address 0x1085 > ==3163==at 0x4556B5B: node::fs::FSReqWrap::~FSReqWrap() (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3163==by 0x4547A42: node::fs::FSReqAfterScope::~FSReqAfterScope() (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3163==by 0x45484FD: node::fs::AfterInteger(uv_fs_s*) (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3163==by 0x556170F: uv__work_done (in > /usr/lib/i386-linux-gnu/libuv.so.1.0.0) > ==3163==by 0x55657FD: ??? (in /usr/lib/i386-linux-gnu/libuv.so.1.0.0) > ==3163==by 0x5575527: uv__io_poll (in > /usr/lib/i386-linux-gnu/libuv.so.1.0.0) > ==3163==by 0x55661C5: uv_run (in /usr/lib/i386-linux-gnu/libuv.so.1.0.0) > ==3163==by 0x4515C75: node::Start(v8::Isolate*, node::IsolateData*, > std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > const&, > std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > const&) (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3163==by 0x4513C96: node::Start(int, char**) (in > /usr/lib/i386-linux-gnu/libnode.so.64) > ==3163==by 0x8049157: main (in /usr/bin/node) > ==3163== If you believe this happened as a result of a stack > ==3163== overflow in your program's main thread (unlikely but > ==3163== possible), you can try to increase the size of the > ==3163== main thread stack using the --main-stacksize= flag. > ==3163== The main thread stack size used in this run was 8388608. > ==3163== Invalid read of size 1 > ==3163==at 0x786A6A4: check_free (dlerror.c:189) > ==3163==by 0x786ABD8: free_key_mem (dlerror.c:221) > ==3163==by 0x786ABD8: __dlerror_main_
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le lun. 20 sept. 2021 à 10:20, Bastien ROUCARIES a écrit : > > Le lun. 20 sept. 2021 à 10:15, Ondrej Zary a écrit : > > > > libuv libuv1:i386 1.24.1-1+deb10u1 with -fsanitize=address,undefined: > > > > yarn install v1.13.0 > > [1/5] Validating package.json... > > [2/5] Resolving packages... > > [3/5] Fetching packages... > > [---] > > 0/520AddressSanitizer:DEADLYSIGNAL > > = > > ==26662==ERROR: AddressSanitizer: SEGV on unknown address 0x1085 (pc > > 0xf695db5b bp 0xffd3adb8 sp 0xffd3ada4 T0) > > ==26662==The signal is caused by a READ memory access. > > #0 0xf695db5a in node::fs::FSReqWrap::~FSReqWrap() > > (/lib/i386-linux-gnu/libnode.so.64+0x50bb5a) > > #1 0xf694ea42 in node::fs::FSReqAfterScope::~FSReqAfterScope() > > (/lib/i386-linux-gnu/libnode.so.64+0x4fca42) > > #2 0xf694f4fd in node::fs::AfterInteger(uv_fs_s*) > > (/lib/i386-linux-gnu/libnode.so.64+0x4fd4fd) > > #3 0xf629e32d in uv__work_done (/lib/i386-linux-gnu/libuv.so.1+0x5f32d) > > #4 0xf62ad125 (/lib/i386-linux-gnu/libuv.so.1+0x6e125) > > #5 0xf631e0a8 in uv__io_poll (/lib/i386-linux-gnu/libuv.so.1+0xdf0a8) > > #6 0xf62b198c in uv_run (/lib/i386-linux-gnu/libuv.so.1+0x7298c) > > #7 0xf691cc75 in node::Start(v8::Isolate*, node::IsolateData*, > > std::vector, > > std::allocator >, std::allocator > std::char_traits, std::allocator > > > const&, > > std::vector, > > std::allocator >, std::allocator > std::char_traits, std::allocator > > > const&) > > (/lib/i386-linux-gnu/libnode.so.64+0x4cac75) > > #8 0xf691ac96 in node::Start(int, char**) > > (/lib/i386-linux-gnu/libnode.so.64+0x4c8c96) > > #9 0x8049157 in main (/usr/bin/node+0x8049157) > > #10 0xf3ac5b40 in __libc_start_main > > (/lib/i386-linux-gnu/libc.so.6+0x1ab40) > > #11 0x80491c1 in _start (/usr/bin/node+0x80491c1) > > > > AddressSanitizer can not provide additional info. > > SUMMARY: AddressSanitizer: SEGV > > (/lib/i386-linux-gnu/libnode.so.64+0x50bb5a) in > > node::fs::FSReqWrap::~FSReqWrap() > > ==26662==ABORTING > Ok now try to run the whole thing against valgrind... Could you try to build both libuv and node with -fsanitize=null it is likely a null dereference so catch it Bastien > > Bastien > > > > > > > -- > > Ondrej Zary > > > > -- > > Pkg-javascript-devel mailing list > > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le lun. 20 sept. 2021 à 10:15, Ondrej Zary a écrit : > > libuv libuv1:i386 1.24.1-1+deb10u1 with -fsanitize=address,undefined: > > yarn install v1.13.0 > [1/5] Validating package.json... > [2/5] Resolving packages... > [3/5] Fetching packages... > [---] > 0/520AddressSanitizer:DEADLYSIGNAL > = > ==26662==ERROR: AddressSanitizer: SEGV on unknown address 0x1085 (pc > 0xf695db5b bp 0xffd3adb8 sp 0xffd3ada4 T0) > ==26662==The signal is caused by a READ memory access. > #0 0xf695db5a in node::fs::FSReqWrap::~FSReqWrap() > (/lib/i386-linux-gnu/libnode.so.64+0x50bb5a) > #1 0xf694ea42 in node::fs::FSReqAfterScope::~FSReqAfterScope() > (/lib/i386-linux-gnu/libnode.so.64+0x4fca42) > #2 0xf694f4fd in node::fs::AfterInteger(uv_fs_s*) > (/lib/i386-linux-gnu/libnode.so.64+0x4fd4fd) > #3 0xf629e32d in uv__work_done (/lib/i386-linux-gnu/libuv.so.1+0x5f32d) > #4 0xf62ad125 (/lib/i386-linux-gnu/libuv.so.1+0x6e125) > #5 0xf631e0a8 in uv__io_poll (/lib/i386-linux-gnu/libuv.so.1+0xdf0a8) > #6 0xf62b198c in uv_run (/lib/i386-linux-gnu/libuv.so.1+0x7298c) > #7 0xf691cc75 in node::Start(v8::Isolate*, node::IsolateData*, > std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > const&, > std::vector, > std::allocator >, std::allocator std::char_traits, std::allocator > > > const&) > (/lib/i386-linux-gnu/libnode.so.64+0x4cac75) > #8 0xf691ac96 in node::Start(int, char**) > (/lib/i386-linux-gnu/libnode.so.64+0x4c8c96) > #9 0x8049157 in main (/usr/bin/node+0x8049157) > #10 0xf3ac5b40 in __libc_start_main > (/lib/i386-linux-gnu/libc.so.6+0x1ab40) > #11 0x80491c1 in _start (/usr/bin/node+0x80491c1) > > AddressSanitizer can not provide additional info. > SUMMARY: AddressSanitizer: SEGV (/lib/i386-linux-gnu/libnode.so.64+0x50bb5a) > in node::fs::FSReqWrap::~FSReqWrap() > ==26662==ABORTING Ok now try to run the whole thing against valgrind... Bastien > > > -- > Ondrej Zary > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: npm: segfault during extract on i386
Le lun. 20 sept. 2021 à 12:02, Ondrej Zary a écrit : > I'm unable to compile node with -fsanitize=address,undefined. Seems that > compiler hits 32-bit memory space limit: > cc1plus: out of memory allocating 65536 bytes after a total of 3356393472 > bytes > Libuv only will be Nice Node is not crosscompile safe so this is a dead end > > -- > Ondrej Zary > -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: npm: segfault during extract on i386
Le lun. 20 sept. 2021 à 08:02, Ondrej Zary a écrit : > > Rebuilt Debian libuv1 1.24.1 with -fno-stack-protector - still segfaults. > Rebuilt Debian libuv1 1.42.0 (from unstable) in Buster - still segfaults. Please rebuild both nodejs and libuv with asan (adresse sanitizer) After, I think it is time to escalade. Bastien > -- > Ondrej Zary -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#994678: Bug#994678: Bug#994678: pkg-js-tools: MA status
Le lun. 20 sept. 2021 à 06:03, Yadd a écrit : > Le 19/09/2021 à 12:35, Bastien Roucariès a écrit : > > Package: pkg-js-tools > > Version: 0.9.66 > > Severity: important > > > > Dear Maintainer, > > > > According to a few cross build test (see for instance > > https://salsa.debian.org/js-team/node-re2/-/jobs/1960208) > > > > This package is a blocker. > > > > May be MA: same if possible will help here > > pkg-js-tools is arch:all. So this issue seems a duplicate > Sorry i mean ma: foreign > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel > -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le dim. 19 sept. 2021 à 21:57, Bastien ROUCARIES a écrit : > > try to pass > -fstack-protector-strong to the local version as cflags > > If it fail upstream does not take in acount stack protector > > Le dim. 19 sept. 2021 à 21:45, Bastien ROUCARIES > a écrit : > > > > Le dim. 19 sept. 2021 à 21:39, Bastien ROUCARIES > > a écrit : > > > > > > Le dim. 19 sept. 2021 à 21:36, Ondrej Zary a écrit : > > > > > > > > I've reinstalled nodejs and libnode64 back to original Buster > > > > 10.24.0~dfsg-1~deb10u1 and upgraded libuv1 to > > > > libuv1_1.34.2-1~bpo9+1_i386.deb from http://snapshot.debian.org > > > > > > > > It still segfaults! > > > > > > > > So it seems that the problem is not libuv version but its linking > > > > (included in node or external). Or cflags? > > > Or ldflags > > > > > > Could you dump the cflags/ldfalgs of both version? > > Or sanatizer that avoid a free after use... > > > > We harden a lot on debian side > > > > Bastien > > > > > > > > > > > > > > -- > > > > Ondrej Zary If it does work try to build both nodejs and libuv with -fsanitize=address or other sanitizer option Bastien > > > > -- > > > > Pkg-javascript-devel mailing list > > > > Pkg-javascript-devel@alioth-lists.debian.net > > > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel > > > > -- > > Pkg-javascript-devel mailing list > > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
try to pass -fstack-protector-strong to the local version as cflags If it fail upstream does not take in acount stack protector Le dim. 19 sept. 2021 à 21:45, Bastien ROUCARIES a écrit : > > Le dim. 19 sept. 2021 à 21:39, Bastien ROUCARIES > a écrit : > > > > Le dim. 19 sept. 2021 à 21:36, Ondrej Zary a écrit : > > > > > > I've reinstalled nodejs and libnode64 back to original Buster > > > 10.24.0~dfsg-1~deb10u1 and upgraded libuv1 to > > > libuv1_1.34.2-1~bpo9+1_i386.deb from http://snapshot.debian.org > > > > > > It still segfaults! > > > > > > So it seems that the problem is not libuv version but its linking > > > (included in node or external). Or cflags? > > Or ldflags > > > > Could you dump the cflags/ldfalgs of both version? > Or sanatizer that avoid a free after use... > > We harden a lot on debian side > > Bastien > > > > > > > > > > -- > > > Ondrej Zary > > > > > > -- > > > Pkg-javascript-devel mailing list > > > Pkg-javascript-devel@alioth-lists.debian.net > > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le dim. 19 sept. 2021 à 21:39, Bastien ROUCARIES a écrit : > > Le dim. 19 sept. 2021 à 21:36, Ondrej Zary a écrit : > > > > I've reinstalled nodejs and libnode64 back to original Buster > > 10.24.0~dfsg-1~deb10u1 and upgraded libuv1 to > > libuv1_1.34.2-1~bpo9+1_i386.deb from http://snapshot.debian.org > > > > It still segfaults! > > > > So it seems that the problem is not libuv version but its linking (included > > in node or external). Or cflags? > Or ldflags > > Could you dump the cflags/ldfalgs of both version? Or sanatizer that avoid a free after use... We harden a lot on debian side Bastien > > > > > > -- > > Ondrej Zary > > > > -- > > Pkg-javascript-devel mailing list > > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le dim. 19 sept. 2021 à 21:36, Ondrej Zary a écrit : > > I've reinstalled nodejs and libnode64 back to original Buster > 10.24.0~dfsg-1~deb10u1 and upgraded libuv1 to libuv1_1.34.2-1~bpo9+1_i386.deb > from http://snapshot.debian.org > > It still segfaults! > > So it seems that the problem is not libuv version but its linking (included > in node or external). Or cflags? Or ldflags Could you dump the cflags/ldfalgs of both version? > > -- > Ondrej Zary > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le dim. 19 sept. 2021 à 21:25, Bastien ROUCARIES a écrit : > > Le dim. 19 sept. 2021 à 21:15, Ondrej Zary a écrit : > > > > Added back --shared-zlib: works. > > Added back also --shared-cares: works. > > > > So you're right: --shared-libuv is the problem. > > Upstream seems to include libuv 1.34.2. > > Buster has 1.24.1-1. > > Do you have valgrind ? > > If so and if it work (test first on good version), it smell like a use > after free or a RAII violation > > I means, that libuv free a pointer, nodejs fill the buffer with code, > then libuv free it. BOOOM. From libuv changelog - * unix,win: fix `uv_fs_poll_stop()` when active (Anna Henningsen) - * unix: fix race condition in uv_async_send() (Ben Noordhuis) But I suppose it will be quicker to bissect by build/try the different version of libuv... Bastien > > > -- > > Ondrej Zary > > > > -- > > Pkg-javascript-devel mailing list > > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le dim. 19 sept. 2021 à 21:15, Ondrej Zary a écrit : > > Added back --shared-zlib: works. > Added back also --shared-cares: works. > > So you're right: --shared-libuv is the problem. > Upstream seems to include libuv 1.34.2. > Buster has 1.24.1-1. Do you have valgrind ? If so and if it work (test first on good version), it smell like a use after free or a RAII violation I means, that libuv free a pointer, nodejs fill the buffer with code, then libuv free it. BOOOM. > -- > Ondrej Zary > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#994720: Bug#994720: nodejs: Please depends of sse2-support
Le dim. 19 sept. 2021 à 21:03, Jérémy Lal a écrit : > > >> Le dim. 19 sept. 2021 à 22:33, Bastien Roucariès >> a écrit : >> >> Source: nodejs >> Severity: serious >> Tags: patch >> Justification: base arch >> Forwarded: >> https://chromium.googlesource.com/v8/v8.git/+/e825c4318eb2065ffdf9044aa6a5278635c36427 >> >> Dear Maintainer, >> >> libv8 need sse2 on i386 since 2017... >> >> I asked upstream better communication with us, but we must depends on >> sse2-support >> >> Patch because I will fix on git asap I have a bug number. >> > > [i386] sse2-support is already a dependency... but that fact has not made it > to buster. Yes and b-d should also depends > > Jérémy -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le dim. 19 sept. 2021 à 20:21, Ondrej Zary a écrit : > > On Sunday 19 September 2021 20:13:47 Bastien ROUCARIES wrote: > > Hi, > > > > So you work on oldstable. > > > > Could you check for stable/testing/unstable/experimental ? And mark > > the bug with found /not found. > > Unfortunately I can't. I'm trying to get gitlab 11.11.8+dfsg-1+fto10+2 to > work. Then I can upgrade gitlab further to 12 and 13 and only then I can > upgrade Debian to bullseye. > > I've rebuilt Debian nodejs without --shared-zlib, --shared-cares and > --shared-libuv (remove them from debian/rules). It works now! begin whith shared-uv Bastien > > Going to narrow it down. > > -- > Ondrej Zary > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#994703: Bug#994703: Bug#994703: nodejs: please documents deps or avoid it
Le dim. 19 sept. 2021 à 19:33, Jérémy Lal a écrit : > > > > Le dim. 19 sept. 2021 à 18:54, Bastien Roucariès > a écrit : >> >> Package: nodejs >> Version: 12.22.5~dfsg-2 >> Severity: serious >> >> Dear Maintainer, >> >> README.source should document the deps directory. >> >> It will be better to remove some libs from deps. Why libz is needed for node >> ? >> Could we push this plugin stuff to libz and so on. >> >> Acorn embdeded should be fixed by recent version. >> >> openssl one is worry some.. > > > Hi, > > What's in ./deps/ is mostly not used for building node. > It's pretty much obvious if you look at ./debian/rules configure flags. Yes but README.Source is in this case good > > I believe it is not common practice to remove unused files, as long as it's > okay with DFSG. Yes also > That's why > zlib, openssl, nghttp2, http-parser, uv, c-ares, brotli > are kept around in ./deps/ directory. > > This is actually useful, it makes debugging against "upstream-like" builds > easier. Yes but in order to be less worried about something in this huge code base use these files, I will really prefer to move the deps dir before configure or removing the -r bit in order to avoid something strange I was hit ten years ago by some leaking hardcoded path on a project I compiled, and I really prefer to be paraonoiac on this side Bastien > Jérémy > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le dim. 19 sept. 2021 à 19:37, Jérémy Lal a écrit : > > > > Le dim. 19 sept. 2021 à 20:18, Bastien ROUCARIES > a écrit : >> >> Hi, >> >> So you work on oldstable. >> >> Could you check for stable/testing/unstable/experimental ? And mark >> the bug with found /not found. >> > > Interestingly, the copy of zlib in nodejs source has several patches that are > not > in the official zlib release available in debian. > So if what was said is correct (that upstream binary builds do not crash) > this might be a clue. I was more thinking about a cflags like hardening flags or something like this... Bastien > Jérémy -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Hi, So you work on oldstable. Could you check for stable/testing/unstable/experimental ? And mark the bug with found /not found. Thanks Bastien Le dim. 19 sept. 2021 à 18:03, Ondrej Zary a écrit : > > There's no such patch in 10.24.0~dfsg-1~deb10u1 > > -- > Ondrej Zary -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le dim. 19 sept. 2021 à 17:40, Ondrej Zary a écrit : > > Upstream node rebuilt in Debian works. So it's not a compiler or libc problem. Does removing the debian patch large_pages_assembly_gnu_stack.patch Changes something ? Bastien > The Debian (buster) i386 version 10.24.0~dfsg-1~deb10u1 already contains SSE2 > instructions - it does not work on Pentium 3: > $ node > Illegal instruction > > So I doubt that changing -march would help. > > -- > Ondrej Zary -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: Bug#922075: npm: segfault during extract on i386
Le dim. 19 sept. 2021 à 16:33, Ondrej Zary a écrit : > > upstream (strings in bin/node), seems to be statically linked: > gcc 6.3.1 > libc 2.17 according to https://github.com/nodejs/unofficial-builds/ > build log found at > https://unofficial-builds.nodejs.org/logs/202102231620-v10.24.0/x86.log > > Debian binary seems to be split into libnode64. > gcc (Debian 8.3.0-6) 8.3.0 > libc6 2.28-10 > > I'll try to build the upstream version in Debian. Could you try aurel32 tips: rouca: it's not obviously linked to libc [16:34] rouca: about gcc, we have a very low ISA baseline on i386 compared to what is usually used. Might be worth trying to rebuild it with -march=pentium4 or something like that Bastien > > -- > Ondrej Zary > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#922075: Bug#922075: npm: segfault during extract on i386
Le dim. 19 sept. 2021 à 15:48, Ondrej Zary a écrit : > > Seems that only Debian i386 build of nodejs is broken. > > Downloaded > https://unofficial-builds.nodejs.org/download/release/v10.24.0/node-v10.24.0-linux-x86.tar.xz > unpacked somewhere and edited /usr/bin/yarnpkg to point to the new bin/node > added symlinks (dirty hack) so node can find both /usr/lib/nodejs and > /usr/share/nodejs: > /node_modules -> /usr/share/nodejs > /var/lib/gitlab/.node_libraries -> /usr/lib/nodejs > > yarnpkg completed without segfault! Could you investigate: - the libc used both upstream and debian side ? - the gcc or compiler used with flags both side ? Bastien > -- > Ondrej Zary > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Bug#994577: lintian: node-* arch:all package should depends on nodejs:any and b-d on nodejs:native
Le sam. 18 sept. 2021 à 16:57, Mattia Rizzolo a écrit :
> (this reply is not related to lintian directly)
>
> On Fri, Sep 17, 2021 at 09:34:43PM +, Bastien Roucariès wrote:
> > In order to improve cross build of nodejs ecosystem, node-* arch:all
> package
> > should depends on nodejs:any and b-d on nodejs:native
>
> IMHO, you should make your tooling produce this "nodejs:any" binary
> dependency, instead of having each package have it manually listed in
> d/control (see ${perl:Depends} as an example, since, it's actually the
> very same thing, producing perl:any dependencies).
>
Bug already opened. Thanks for thé idea
>
> > Maybe this test should be restricted to ma: foreign package
>
> It shouldn't be IMHO.
>
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
> More about me: https://mapreri.org : :' :
> Launchpad user: https://launchpad.net/~mapreri `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
>
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#994603: errormsg
debian/upstream
To fix the situation please do the following:
1) Examine debian/copyright_* and referenced files
2) Update debian/copyright as needed
3) Replace debian/copyright_hints with debian/copyright_newhints
touch debian/stamp-copyright-check
touch debian/stamp-upstream-cruft
node-gyp configure
gyp info it worked if it ends with ok
gyp info using node-gyp@7.1.2
gyp info using node@12.22.5 | linux | x64
gyp info find Python using Python version 3.9.7 found at "/usr/bin/python3"
gyp info spawn /usr/bin/python3
gyp info spawn args [
gyp info spawn args '/usr/share/nodejs/node-gyp/gyp/gyp_main.py',
gyp info spawn args 'binding.gyp',
gyp info spawn args '-f',
gyp info spawn args 'make',
gyp info spawn args '-I',
gyp info spawn args '/tmp/node-stringprep/build/config.gypi',
gyp info spawn args '-I',
gyp info spawn args '/usr/share/nodejs/node-gyp/addon.gypi',
gyp info spawn args '-I',
gyp info spawn args '/usr/include/nodejs/common.gypi',
gyp info spawn args '-Dlibrary=shared_library',
gyp info spawn args '-Dvisibility=default',
gyp info spawn args '-Dnode_root_dir=/usr/include/nodejs',
gyp info spawn args '-Dnode_gyp_dir=/usr/share/nodejs/node-gyp',
gyp info spawn args
'-Dnode_lib_file=/usr/include/nodejs/<(target_arch)/node.lib',
gyp info spawn args '-Dmodule_root_dir=/tmp/node-stringprep',
gyp info spawn args '-Dnode_engine=v8',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args 'build',
gyp info spawn args '-Goutput_dir=.'
gyp info spawn args ]
gyp info ok
touch debian/stamp-node-gyp-configure
V=1 CC="cc" CXX="g++" CFLAGS="-g -O2
-ffile-prefix-map=/tmp/node-stringprep=. -fstack-protector-strong
-Wformat -Werror=format-security" CXXFLAGS="-g -O2
-ffile-prefix-map=/tmp/node-stringprep=. -fstack-protector-strong
-Wformat -Werror=format-security" CPPFLAGS="-Wdate-time
-D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro -Wl,-z,now" \
node-gyp build
gyp info it worked if it ends with ok
gyp info using node-gyp@7.1.2
gyp info using node@12.22.5 | linux | x64
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make[1] : on entre dans le répertoire « /tmp/node-stringprep/build »
g++ -o Release/obj.target/node_stringprep/node-stringprep.o
../node-stringprep.cc '-DNODE_GYP_MODULE_NAME=node_stringprep'
'-DUSING_UV_SHARED=1' '-DUSING_V8_SHARED=1'
'-DV8_DEPRECATION_WARNINGS=1' '-DV8_DEPRECATION_WARNINGS'
'-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_LARGEFILE_SOURCE'
'-D_FILE_OFFSET_BITS=64' '-D__STDC_FORMAT_MACROS'
'-DBUILDING_NODE_EXTENSION' -I/usr/include/nodejs/include/node
-I/usr/include/nodejs/src -I/usr/include/nodejs/deps/openssl/config
-I/usr/include/nodejs/deps/openssl/openssl/include
-I/usr/include/nodejs/deps/uv/include -I/usr/include/nodejs/deps/zlib
-I/usr/include/nodejs/deps/v8/include -I../../../usr/share/nodejs/nan
-fPIC -pthread -Wall -Wextra -Wno-unused-parameter -m64 -fPIC -O3
-fno-omit-frame-pointer -fno-rtti -std=gnu++1y `pkg-config icu-i18n
--cflags` -MMD -MF
./Release/.deps/Release/obj.target/node_stringprep/node-stringprep.o.d.raw
-Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-ffile-prefix-map=/tmp/node-stringprep=. -fstack-protector-strong
-Wformat -Werror=format-security -c
../node-stringprep.cc:20:26: error: ‘Handle’ has not been declared
20 | static void Initialize(Handle target)
| ^~
../node-stringprep.cc:20:32: error: expected ‘,’ or ‘...’ before ‘<’ token
20 | static void Initialize(Handle target)
|^
../node-stringprep.cc:154:5: warning: dynamic exception specifications
are deprecated in C++11 [-Wdeprecated]
154 | throw(UnknownProfileException)
| ^
../node-stringprep.cc: In static member function ‘static void
StringPrep::Initialize(int)’:
../node-stringprep.cc:28:5: error: ‘target’ was not declared in this scope
28 | target->Set(Nan::New("StringPrep").ToLocalChecked(),
t->GetFunction());
| ^~
../node-stringprep.cc:28:81: error: no matching function for call to
‘v8::FunctionTemplate::GetFunction()’
28 | target->Set(Nan::New("StringPrep").ToLocalChecked(),
t->GetFunction());
|
^
In file included from /usr/include/nodejs/src/node.h:67,
from ../../../usr/share/nodejs/nan/nan.h:56,
from ../node-stringprep.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h:6126:46: note: candidate:
‘v8::MaybeLocal
v8::FunctionTemplate::GetFunction(v8::Local)’
6126 | V8_WARN_UNUSED_RESULT MaybeLocal GetFunction(
| ^~~
/usr/include/nodejs/deps/v8/include/v8.h:6126:46: note: candidate
expects 1 argument, 0 provided
../node-stringprep.cc: In static member function ‘static
Nan::NAN_METHOD_RETURN_TYPE
StringPrep::New(Nan::NAN_METHOD_ARGS_TYPE)’:
../node-stringprep.cc:48:48: error: no matching function for call to
‘v8::
[Pkg-javascript-devel] Bug#994544: Bug#994544: Bug#994544: npm2deb: nodejs:any for arch:all package
Le ven. 17 sept. 2021 à 20:24, Yadd a écrit : > > > > Le 17 septembre 2021 21:30:16 GMT+02:00, Bastien ROUCARIES > a écrit : > >Le ven. 17 sept. 2021 à 16:06, Yadd a écrit : > >> > >> Le 17/09/2021 à 16:36, Bastien Roucariès a écrit : > >> > Package: npm2deb > >> > Version: 0.3.0-6 > >> > Severity: important > >> > > >> > Dear Maintainer, > >> > > >> > > >> > In order to help cross build nodejs depends should be nodejs:any for > >> > purejs > >> > module in depends field. > >> > > >> > In build-depends field we should use nodejs:native in order to help > >> > crossbuilt > >> > > >> > Bastien > >> > >> Hi Bastien, > >> > >> you should clone this and reassign to pkg-js-tools (build depends on > >> nodejs). > >> npm2deb should not set a run dependency to nodejs except if there is a > >> /usr/bin file > >Not sure perl set perl:any on every package. > > > >It is sensible to do so > > > >Bastien > > A Perl file is usable only with Perl, not a JS one. We decided to remove > nodejs dependency some months ago. Ok thanks look sensible nevertheless, nodejs:any is also sensible if needed. Will open a lintian bug also > > Cheers, > Yadd > > -- > Envoyé de mon appareil Android avec Courriel K-9 Mail. Veuillez excuser ma > brièveté. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#994544: Bug#994544: Bug#994544: npm2deb: nodejs:any for arch:all package
control: clone -1 -2 control: reassign -2 pkg-js-tools Le ven. 17 sept. 2021 à 16:06, Yadd a écrit : > > Le 17/09/2021 à 16:36, Bastien Roucariès a écrit : > > Package: npm2deb > > Version: 0.3.0-6 > > Severity: important > > > > Dear Maintainer, > > > > > > In order to help cross build nodejs depends should be nodejs:any for purejs > > module in depends field. > > > > In build-depends field we should use nodejs:native in order to help > > crossbuilt > > > > Bastien > > Hi Bastien, > > you should clone this and reassign to pkg-js-tools (build depends on > nodejs). > npm2deb should not set a run dependency to nodejs except if there is a > /usr/bin file > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#994544: Bug#994544: Bug#994544: npm2deb: nodejs:any for arch:all package
Le ven. 17 sept. 2021 à 16:06, Yadd a écrit : > > Le 17/09/2021 à 16:36, Bastien Roucariès a écrit : > > Package: npm2deb > > Version: 0.3.0-6 > > Severity: important > > > > Dear Maintainer, > > > > > > In order to help cross build nodejs depends should be nodejs:any for purejs > > module in depends field. > > > > In build-depends field we should use nodejs:native in order to help > > crossbuilt > > > > Bastien > > Hi Bastien, > > you should clone this and reassign to pkg-js-tools (build depends on > nodejs). > npm2deb should not set a run dependency to nodejs except if there is a > /usr/bin file Not sure perl set perl:any on every package. It is sensible to do so Bastien > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Issues with node-rollup-plugin-node-resolve
Le lun. 6 sept. 2021 à 16:27, Pirate Praveen a écrit : > > > On തി, സെപ്റ്റം 6, 2021 at 08:42, Julien Puydt > wrote: > > Hi, > > > > I tried to update the above-mentioned package and pushed quite a few > > changes but: > > > > - it looks like the orig tarball generation is quite strange, with a > > succession of "Files-Excluded: *" and "Files-Included: very short > > list" > > which confuses both dpkg-source and lintian -- and there's no +dfsg or > > +ds or +repack suffix... > > > Because upstream uses a mono repo for all plugins and we need to pick > only the required plugin in our orig tar. Since each plugin is released > independantly, we can have a single source package to build all plugins > in one source package. > > uscan will handle this instructions. > +ds is needed here nevertheless > > > - I still have a failing test in the upstream test suite (heavily > > patched to use tape instead of ava... will have to check for a RFP), > > with little clue as to why it is failing. > > > > If you have insight or ideas about those matters, don't hesitate: I > > won't touch the package in the coming days... > > > > Cheers, > > > > J.Puydt > > > > > > -- > > Pkg-javascript-devel mailing list > > Pkg-javascript-devel@alioth-lists.debian.net > > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel > > > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel > -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Improve lintian need a lsit of embeded javascript lib
Hi Xavier, I know where is the actual list here https://salsa.debian.org/lintian/lintian/-/blob/master/lib/Lintian/Check/Languages/Javascript/Embedded.pm In fact I need more file to add to the list in order to improve lintian checking Bastien Le mer. 1 sept. 2021 à 07:01, Yadd a écrit : > > Le 30/08/2021 à 15:47, Bastien Roucariès a écrit : > > Hi, > > > > I plan to improve embedded-javascript-library > > > > Therefore I need a list of javascript embeded file > > > > Could you send me a list ? > > > > Thanks > > > > Bastien > > Hi, > > ask to Felix Lechner. I don't remember where is this list > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#979942: Bug#979942: Bug#979942: Bug#979942: embedding dead code is no fix to bug for removing that same dead code
Le mar. 12 janv. 2021 à 21:02, Jonas Smedegaard a écrit : > > Quoting Bastien ROUCARIES (2021-01-12 21:17:36) > > Fixed it was a little bit hard to test options of compression one by > > one but it work now. Hi, It was harder than I thought. This time I document the requirement for this package under https://salsa.debian.org/js-team/node-browser-pack/-/blob/master/debian/rules#L13 And I think I have suffisantly documented the bandaid method in case of future problems Could you confirm I am clear ? Bastien > > Great! Thanks! > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#979942: Bug#979942: Bug#979942: embedding dead code is no fix to bug for removing that same dead code
Hi, Fixed it was a little bit hard to test options of compression one by one but it work now. Le mar. 12 janv. 2021 à 17:48, Xavier a écrit : > > Control: tags -1 reopen > Control: severity -1 serious > > Le 12/01/2021 à 18:17, Jonas Smedegaard a écrit : > > Quoting Debian FTP Masters (2021-01-12 18:06:40) > >> node-browser-pack (6.1.0+ds-7) unstable; urgency=medium > >> . > >>* Team upload > >>* Bump debhelper compatibility level to 13 > >>* Declare compliance with policy 4.5.1 > >>* Use dh-sequence-nodejs > >>* Remove dependency to node-uglify but embed node-uglify in > >> build_modules > >> else build file is wrong (Closes: #979942) > > > > Do I read the above correctly that node-browser-pack "fixes" node-uglify > > going away by embedding it, hidden? > > > > I disagree that that is a fix. > > OK, but I didn't succeed to fix that, let's reopen, upgrade severity and > wait for someone else to fix it > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] babel7 in a separate package ?
On Tue, Feb 25, 2020 at 12:25 PM Jonas Smedegaard wrote: > > Quoting Pirate Praveen (2020-02-25 10:59:11) > > On 2020, ഫെബ്രുവരി 25 10:59:35 AM IST, Xavier wrote: > > >I think we should publish babel7 in a separate node-babel7: some > > >package require old babel 6 for build. OK? > > > > > > > It will need maintaining two versions of babel which we should try to avoid. > > > > We can have babel 7 in experimental and try to update all packages > > currently using babel 6 to build with babel 7. Basically how we do > > every other major version update. At the least we should evaluate how > > many packages are affected and compare the effort required for both > > approaches. > > I haven't looked at the numbers but just blindly assume that we are > talking about hundreds of packages needing migration here, each > requiring a "real" package upload (binNMUs are not supported for > arch-all packages) and often require patches or changes to patches > (unlike C library bumps only exceptionally needing changes to code). > > I agree that we should not _maintain_ more than a single release of > babel: We should have Debian _release_ with two major versions of babel > concurrently! > > What worries me is that _all_ users of babel must switch _together_ - I > fear that it is too complicates, because of the likelihood of many > unrelated bugs appearing together. > > Please package babel7 as a package independent from babel6, and have > both in unstable concurrently, but also make sure to file a big fat RC > bug against babel7 to ensure that we don't want to maintain it in a > release. > > Then, when enough packages have switched to support babel7, we can move > that RC bugreport to be tied to babel6 instead, so that we instead push > out any packages failing to align with the new World order of babel7. > > I find that a much nice development approach than "let's have the whole > World of babel7 perfected in experimental, and then BOOM! switch over to > unstable - hoping for zero collateral damage in that revolutionary > move". I like this plan, thanks Bastien > > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private-- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] node-typescript-types should die
On Mon, Mar 2, 2020 at 6:24 PM Xavier wrote: > > Le 02/03/2020 à 00:15, Bastien ROUCARIES a écrit : > > On Sun, Mar 1, 2020 at 4:53 PM Jonas Smedegaard wrote: > >> > >> Quoting Bastien ROUCARIES (2020-03-01 16:26:23) > >>> On Tue, Feb 25, 2020 at 5:43 AM Xavier wrote: > >>>> > >>>> Le 24/02/2020 à 23:28, Bastien ROUCARIES a écrit : > >>>>> Hi, > >>>>> > >>>>> This package should die. > >>>>> With newer pkg-js-tools we must embded the types is not supplied by > >>>>> the main package as a compoent of the main package. > >>>>> > >>>>> I was burned because acorn now supply a type. > >>>>> > >>>>> It is better to do the work in the main package than in a meta package > >>>> > >>>> Hi, > >>>> > >>>> I don't agree: many @types/foo files are requires by many packages > >>>> during build (examples with @types/node, @types/mocha,...). So I think > >>>> we should keep a virtual package. > >>> > >>> I means that main package should have a component that create a > >>> @types/node (virtual?) pacakge > >>> > >>> But a meta package is worst because we have an out of sync between > >>> main package and types. > >> > >> Yes, I fully agree with you, Bastien! > >> > >> I think the way to kill that horrible package is to add the types to the > >> respective node-* package. > > > > exactly and pkg-js-tools + components is the best way to do. Could you > > propose a wording for javascript policy ? > > Hi, > > > so let's plan this: > > * @types/backbone => node-backbone > * @types/chai => node-chai > * @types/estree => node-estree > * @types/expect.js => node-expect.js > * @types/fs-extra => node-fs-extra > * @types/glob => node-glob > * @types/handlebars => node-handlebars > * @types/jquery => node-jquery (to be grouped) > * @types/jsdom => to be removed (node-jsdom removed with libjs-jquery) > * @types/lodash => node-lodash > * @types/marked => node-marked > * @types/mathjax => node-mathjax > * @types/micromatch => node-micromatch > * @types/minimist => node-minimist > * @types/mocha => node-mocha > * @types/node => typescript or nodejs ? > * @types/requirejs => node-requirejs > * @types/sax => node-sax > * @types/semver => node-semver > * @types/shelljs => node-shelljs > * @types/sinon => node-sinon > * @types/sizzle => libjs-sizzle ? > * @types/underscore => node-underscore > > * In these packages, add 'Breaks: node-typescript-types (< 20190219)' > > * During a short delay: > * publish these packages in unstable > * update dependencies for package that (build-)depends on > node-typescript and publish them: > - node-base64url > - node-css-what > - node-domhandler > - node-domutils > - node-entities > - node-htmlparser2 > - node-path-to-regexp > - node-rollup > - node-xterm > - node-ytdl-core > - ipywidgets (coordination with Debian Python Modules Team) > > * After full migration to testing, ROM-RM node-typescript-types Yes this is the plan, thanks for doing my homework > > Cheers, > Xavier > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] node-typescript-types should die
On Sun, Mar 1, 2020 at 4:53 PM Jonas Smedegaard wrote: > > Quoting Bastien ROUCARIES (2020-03-01 16:26:23) > > On Tue, Feb 25, 2020 at 5:43 AM Xavier wrote: > > > > > > Le 24/02/2020 à 23:28, Bastien ROUCARIES a écrit : > > > > Hi, > > > > > > > > This package should die. > > > > With newer pkg-js-tools we must embded the types is not supplied by > > > > the main package as a compoent of the main package. > > > > > > > > I was burned because acorn now supply a type. > > > > > > > > It is better to do the work in the main package than in a meta package > > > > > > Hi, > > > > > > I don't agree: many @types/foo files are requires by many packages > > > during build (examples with @types/node, @types/mocha,...). So I think > > > we should keep a virtual package. > > > > I means that main package should have a component that create a > > @types/node (virtual?) pacakge > > > > But a meta package is worst because we have an out of sync between > > main package and types. > > Yes, I fully agree with you, Bastien! > > I think the way to kill that horrible package is to add the types to the > respective node-* package. exactly and pkg-js-tools + components is the best way to do. Could you propose a wording for javascript policy ? Bastien > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] node-typescript-types should die
On Tue, Feb 25, 2020 at 5:43 AM Xavier wrote: > > Le 24/02/2020 à 23:28, Bastien ROUCARIES a écrit : > > Hi, > > > > This package should die. > > With newer pkg-js-tools we must embded the types is not supplied by > > the main package as a compoent of the main package. > > > > I was burned because acorn now supply a type. > > > > It is better to do the work in the main package than in a meta package > > Hi, > > I don't agree: many @types/foo files are requires by many packages > during build (examples with @types/node, @types/mocha,...). So I think > we should keep a virtual package. I means that main package should have a component that create a @types/node (virtual?) pacakge But a meta package is worst because we have an out of sync between main package and types. Thanks Bastien > > See my previous mail: > > - --- forwarded mail --- - > Subject: Typescript fix in node-entities > > Hi all, > > I'd like to share this patch: > https://salsa.debian.org/js-team/node-entities/blob/master/debian/patches/use-global-typescript-files.diff > > I understood what was wrong in node-entities and succeeds to fix RC bug > with it: > * when "typeRoots" is set, typescript loads all files in this >directories unless "types" is set > > I could then remove all embedded @types files > > Cheers, > Xavier > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Rollup in Debian
On Mon, Feb 24, 2020 at 11:26 PM Bastien ROUCARIES wrote: > > On Wed, Jan 15, 2020 at 10:41 AM Pirate Praveen > wrote: > > > > > > > > On ഞാ, Jan 5, 2020 at 22:16, Pirate Praveen > > wrote: > > > It needs acorn 6 and only webpack 4.30 is compatible with acorn 6. To > > > upload webpack 4.30 to unstable we need node-webassemblyjs. > > > node-webassemblyjs needs either nodejs 12 or Array.prototype.flatMap > > > polyfill packaged. > > > > > > I think getting nodejs 12 into unstable is more productive than > > > packaging the polyfill. So help with nodejs 12 transition to get > > > rollup into unstable. > > > > array.prototype.flatmap has the following dependencies, > > "define-properties": "^1.1.3", "es-abstract": "^1.17.0-next.1", > > "function-bind": "^1.1.1" > > > > and es-abstract has the following dependencies, > > "es-to-primitive": "^1.2.1", > > "function-bind": "^1.1.1", > > "has": "^1.0.3", > > "has-symbols": "^1.0.1", > > "is-callable": "^1.1.5", > > "is-regex": "^1.0.5", > > "object-inspect": "^1.7.0", > > "object-keys": "^1.1.1", > > "object.assign": "^4.1.0", > > "string.prototype.trimleft": "^2.1.1", > > "string.prototype.trimright": "^2.1.1" > > es-abstract is waiting on ftpmaster but has dak problem... Stay tuned Get uploaded on unstable > > > So we will need to embed all of these if we don't want to wait for > > nodejs 12. > > > > > > > > -- > > Pkg-javascript-devel mailing list > > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#952312: Bug#952312: Bug#952312: Bug#952312: node-eslint-scope: FTBFS: tests failed
Le mar. 25 févr. 2020 à 19:48, Jonas Smedegaard a écrit : > control: reassign -1 node-espree > control: affects -1 node-eslint-scope > > Quoting Xavier (2020-02-25 18:29:35) > > Le 23/02/2020 à 14:50, Lucas Nussbaum a écrit : > > > During a rebuild of all packages in sid, your package failed to > > > build on amd64. > > > > Some test are incompatible with node-espree-6. The fix could be > > simply: > > Certainly not a fix to disable tests. > > The package node-espree has exactly one reverse dependency which is > node-eslint-scope, so this is a case of bad coordination. > > (yes, another fix would be to upgrade node-eslint-scope, but that is > more complex and less urgent, so let's roll back first and work on going > forward in experimental first Node-espree was upgraded due to not compatible with acorn6... So upgrade is safer > ) > > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private-- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-typescript-types should die
Hi, This package should die. With newer pkg-js-tools we must embded the types is not supplied by the main package as a compoent of the main package. I was burned because acorn now supply a type. It is better to do the work in the main package than in a meta package -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Rollup in Debian
On Wed, Jan 15, 2020 at 10:41 AM Pirate Praveen wrote: > > > > On ഞാ, Jan 5, 2020 at 22:16, Pirate Praveen > wrote: > > It needs acorn 6 and only webpack 4.30 is compatible with acorn 6. To > > upload webpack 4.30 to unstable we need node-webassemblyjs. > > node-webassemblyjs needs either nodejs 12 or Array.prototype.flatMap > > polyfill packaged. > > > > I think getting nodejs 12 into unstable is more productive than > > packaging the polyfill. So help with nodejs 12 transition to get > > rollup into unstable. > > array.prototype.flatmap has the following dependencies, > "define-properties": "^1.1.3", "es-abstract": "^1.17.0-next.1", > "function-bind": "^1.1.1" > > and es-abstract has the following dependencies, > "es-to-primitive": "^1.2.1", > "function-bind": "^1.1.1", > "has": "^1.0.3", > "has-symbols": "^1.0.1", > "is-callable": "^1.1.5", > "is-regex": "^1.0.5", > "object-inspect": "^1.7.0", > "object-keys": "^1.1.1", > "object.assign": "^4.1.0", > "string.prototype.trimleft": "^2.1.1", > "string.prototype.trimright": "^2.1.1" es-abstract is waiting on ftpmaster but has dak problem... Stay tuned > So we will need to embed all of these if we don't want to wait for > nodejs 12. > > > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Another update path to acorn 6: smooth
On Fri, Feb 21, 2020 at 4:38 PM Bastien ROUCARIES wrote: > > Hi, > > I think it is feasible to upgrade smoothly acorn 6 and acorn breaking > the cycle by backporting the patch of acorn6 from 1.0 to 0.68 > > Patch apply smoothly the only problem is that typescript is not > included in acorn > thus I get an error (see debian-0.68-experimental in rollup) > > Thus that I will do is to upload a new acorn 5 (unstable) that will > supply the typescript and drop the typescript for node-typescripts > that package (in unstable) that have this typescripts > > Then I will upload an acorn6 that have the new typescript in experimental. > > Then I will build rollup. I achieved to build a 0.68.1 with acorn6 and self test work... Does it release the upgrade path ? If so I could upload to experimental with a version like 1.0+really0.68.1+acorn6 and try some sanity checking. What do you think ? Bastien > > Bastien -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Another update path to acorn 6: smooth
Hi, I think it is feasible to upgrade smoothly acorn 6 and acorn breaking the cycle by backporting the patch of acorn6 from 1.0 to 0.68 Patch apply smoothly the only problem is that typescript is not included in acorn thus I get an error (see debian-0.68-experimental in rollup) Thus that I will do is to upload a new acorn 5 (unstable) that will supply the typescript and drop the typescript for node-typescripts that package (in unstable) that have this typescripts Then I will upload an acorn6 that have the new typescript in experimental. Then I will build rollup. Bastien -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Babel 7
On Sun, Feb 16, 2020 at 5:28 PM Xavier wrote: > > Hi, > > babel 7 is required by a lot of packages. At least tap=14 for its yaml > dependency (to be packaged separately), mathjax,... > > Upgrading babel needs babel itself. I discussed this with @praveen and > we didn't see a better way than embedding babel-7 in babel to compile it > (there are more steps than for rollup including some beta releases). > > Has anyone a better idea ? Yes I have staged build a la node-rollup-buble https://sources.debian.org/src/node-rollup-plugin-buble/0.19.4-2/debian/rules/ build it by included babel7 in your path, do a binary upload then a source upload Bastien > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Babel 7
On Thu, Feb 20, 2020 at 10:16 PM Xavier wrote: > > Le 20/02/2020 à 22:14, Xavier a écrit : > > Le 20/02/2020 à 22:11, Bastien ROUCARIES a écrit : > >> On Sun, Feb 16, 2020 at 5:28 PM Xavier wrote: > >>> > >>> Hi, > >>> > >>> babel 7 is required by a lot of packages. At least tap=14 for its yaml > >>> dependency (to be packaged separately), mathjax,... > >>> > >>> Upgrading babel needs babel itself. I discussed this with @praveen and > >>> we didn't see a better way than embedding babel-7 in babel to compile it > >>> (there are more steps than for rollup including some beta releases). > >>> > >>> Has anyone a better idea ? > >> > >> Yes I have > >> > >> staged build a la node-rollup-buble > >> > >> https://sources.debian.org/src/node-rollup-plugin-buble/0.19.4-2/debian/rules/ > >> > >> build it by included babel7 in your path, do a binary upload then a > >> source upload > >> > >> Bastien > > > > But in this case, a full archive rebuilt will fail > > Anyway rebuild fails for all compilers... Yes and the trick is to do two upload: - one using $(BABEL7) to already build babel7 for stage1 and a bin upload (or a source upload including the builded babel7 and pointing $(BABEL7) for stage1 to this embdeded one) - Then when on the archive do a source upload only. The staged build is the way to go as you noted for compiler Bastien > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#930268: forwarded
control: forwarded -1 https://github.com/microsoft/TypeScript/issues/33661 -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] rollup circular dependencies
On Thu, Sep 26, 2019 at 11:21 AM Pirate Praveen wrote: > > > > On Thu, Sep 26, 2019 at 10:18, Pirate Praveen > wrote: > > node-immutable is accepted, so we can upload 0.52 now > > > rollup 0.52 is uploaded to unstable, all reverse rebuilds succeeded except > node-mocha (which was already failing). Uploaded 0.53.0 after we will need types package. Prefer to go slow > Next we should get this to buster-backports and in parallel try to move up to > the highest version that this version can build. > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#940648: Do not install bench dir
Package: pkg-js-tools Version: 0.9.10 Severity: wishlist Dear Maintainer, Bench like test should not be installed -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Components quality plan
Acorn was uploaded today with dak rejection... So maybe changes our plan ? On Sun, Sep 1, 2019 at 10:30 PM Xavier wrote: > > Le 01/09/2019 à 12:26, Pirate Praveen a écrit : > > > > > > On Thu, Aug 15, 2019 at 5:44 PM, Xavier wrote: > >> Hi all, To increase embedding quality and security, I plan to do this: > >> * tools for easier embedding (~done in pkg-js-tools >= 0.9.5) + > >> add-node-component + del-node-component + auto_configure: creates > >> component links in node_modules and links between component if needed > >> + auto_test : component are tested if debian/nodejs//test > >> exists + auto_install : component are installed by default in > >> /node_modules/ but it is configurable easily * fix > >> uscan compression [2] * modify uscan DEHS report to display component > >> state [1] * fix component display during ucan download [3] * create a > >> report page somewhere in debian.org website to display which > >> components are embedded, in which version and in which package * > >> create a "checksum" addon in version to avoid having too long versions > >> (see acorn rejection by dak): - target "group": no change > >> (1.2.3+~0.0.1+~2.3.1...) - target "ignore": no change - new target > >> "checksum": last part of version contains the checksum separate sum of > >> version part: if comp1 is 3.4.2 and comp2 is 11.0.3, then version is > >> 1.2.3+~ck14.4.5 Some other improvements: * pkg-js-tools installs > >> automatically in the good place (/usr/share/nodejs or > >> /usr/lib/>/nodejs * lintian will warn for each module that > >> installs something in /usr/lib/nodejs [4] [1]: > >> https://salsa.debian.org/debian/devscripts/merge_requests/147 [2]: > >> https://salsa.debian.org/debian/devscripts/merge_requests/149 [3]: > >> https://salsa.debian.org/debian/devscripts/merge_requests/146 [4]: > >> https://salsa.debian.org/lintian/lintian/merge_requests/214 (merged) > > > > How do we repack components? For example, in node-gulp, tmatch/coverage > > should be removed. If I add Files-Exluded: coverage in debian/copyright, > > don't it get removed from all components? > > No, Files-Excluded is applied only on main. For component1, use > "Files-Excluded-component1" > > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Remove unmaintained package
idem node-shell-quote needed by browserify. On Thu, Aug 8, 2019 at 6:25 PM Xavier wrote: > > Le 08/08/2019 à 09:31, Xavier a écrit : > > Le 08/08/2019 à 08:09, Xavier a écrit : > >> Le 08/08/2019 à 07:24, Xavier a écrit : > >>> Le 08/08/2019 à 07:11, Xavier a écrit : > Hi, > > looking at UDD, we have a some packages that were not in testing for a > long time and could be considered as orphaned. > If nobody disagree, I'll ask their removal: > >>> > >>> Update: > >> > > New update: > > Remove list > >PACKAGETIME IN QUEUE DEPS > * node-yawl1472 days, no dependencies > * jscommunicator 1406 days, no dependencies > * html2canvas 969 days, no dependencies > * libv8-3.14939 days, uwsgi-plugin-v8 > * validator.js 932 days, no dependencies > * node-shell-quote 714 days, buggy, no dependencies > * node-diffie-hellman 586 days, unmaintained upstream, >no dependencies > * node-stream-to-observable 581 days, no dependencies > > Care list: >PACKAGETIME IN QUEUE > * node-carto 2103 days, needed by openstreetmap-carto > * pdf.js 1135 days, buggy, needed by GitLab > * node-jsdom 1016 days > * node-xterm785 days > * node-katex603 days > * node-react282 days > * node-prismjs 260 days > > Going to be updated (updates of error-er and parse-json done in > experimental): > * node-postcss-load-options 536 days > * node-postcss-load-plugins 536 days > * node-postcss-load-config 532 days > > Fixed: > * node-cache-loader > * node-cosmiconfig > * node-worker-loader > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Remove unmaintained package
Hi, Could we keep diffie-helmann until browserify in unstable ? Le jeu. 8 août 2019 à 09:31, Xavier a écrit : > > Le 08/08/2019 à 08:09, Xavier a écrit : > > Le 08/08/2019 à 07:24, Xavier a écrit : > >> Le 08/08/2019 à 07:11, Xavier a écrit : > >>> Hi, > >>> > >>> looking at UDD, we have a some packages that were not in testing for a > >>> long time and could be considered as orphaned. > >>> If nobody disagree, I'll ask their removal: > >> > >> Update: > > > > New update: > > Remove list > >PACKAGETIME IN QUEUE DEPS > * node-yawl1472 days, no dependencies > * jscommunicator 1406 days, no dependencies > * html2canvas 969 days, no dependencies > * libv8-3.14939 days, uwsgi-plugin-v8 > * validator.js 932 days, no dependencies > * node-shell-quote 714 days, buggy, no dependencies > * node-diffie-hellman 586 days, unmaintained upstream, no > dependencies > * node-stream-to-observable 581 days, no dependencies > > Going to be updated (needs to update error-er and node-parse-json at least) > > * node-postcss-load-options 536 days > * node-postcss-load-plugins 536 days > * node-postcss-load-config 532 days > > > Care list: > > > >PACKAGETIME IN QUEUE > > * node-carto 2103 days, needed by openstreetmap-carto > > * pdf.js 1135 days, buggy, needed by GitLab > > * node-jsdom 1016 days > > * node-xterm785 days > > * node-katex603 days > > * node-cosmiconfig 427 days > > * node-react282 days > > * node-prismjs 260 days > > * node-worker-loader245 days > > * node-cache-loader 233 days > > > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Comments regarding acorn_6.1.1+ds+~0.3.1+~4.0.0+~1.0.0+~5.0.1+ds+~1.6.2+ds-1_amd64.changes
On Mon, Aug 5, 2019 at 2:22 PM Pirate Praveen wrote: > > > > On 2019, ഓഗസ്റ്റ് 5 5:42:17 PM IST, roucaries bastien > wrote: > >In > >On Mon, Jul 8, 2019 at 2:26 PM Chris Lamb wrote: > >> > >> Dear Jonas et al., > >> > >> > What would you suggest/expect as more useful alternative - given > >the > >> > constraint set by ftpmasters? > >> > >> If I may be so bold: this seems to be a hot button topic for you or I > >> am somehow entirely incorrectly reading adverserial animosity in the > >> tone of both your messages. This would, if only practically speaking, > >> not feel like a terribly productive mode of discussion so I do hope > >> you that in the event you felt you needed to comment any further you > >> would be able to ally and assuage me on this angle. > >> > >> To be clear, I don't have any suggestions (do note I was quite- > >> literally "musing out loud"), I was merely explicitly noting a slight > >> wart in the current state of affairs that might be taken into account > >> if, completely and entirely hypothethically, any of this revisied or > >> reviewed more generally. I trust this clarifies my position. :) > > > >Going back to debian after a short hiatus (we are expected our 3d > >child in four year in october), I do not see anything offensing in > >your tone. > > > >The next version of acorn will be worst from this point of view: > >6.2.1+ds+~0.4.0+~4.0.0+really4.0.0+~1.0.0+~5.0.1+ds+~1.7.0+ds+~0.1.1+~0.3.1+~0.2.0+~0.1.0+~0.3.0+~0.3.0 > > > >upstream split small package in smaller package, so we try to do our > >best. > > > >I was thinking first to using a sequence number but we lost the uscan > >automatic up to date download. > > > >In fact we exchanged small insane package we insane metadata, against > >a crazy version string, I believe it is a fair engineering decision. > >We push the whole crap only to one place a version string. > > > >Bastien > > I think this is over engineering. We can just embed smaller modules multiple > times instead. If something is not small enough to embed, I think it is worth > tracking it as a separate package. If by embeding you means patching and add the modules n times, it is worst from a security point of view. I prefer a cray version string > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] nodejs_12.7.0~dfsg-1_source.changes ACCEPTED into experimental
On Sat, Aug 3, 2019 at 8:09 PM Debian FTP Masters wrote: > > > > Accepted: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Format: 1.8 > Date: Sat, 03 Aug 2019 19:48:03 +0200 > Source: nodejs > Architecture: source > Version: 12.7.0~dfsg-1 > Distribution: experimental > Urgency: medium > Maintainer: Debian Javascript Maintainers > > Changed-By: Jérémy Lal > Closes: 932991 > Changes: > nodejs (12.7.0~dfsg-1) experimental; urgency=medium > . >* New upstream version 12.7.0~dfsg (Closes: #932991) >* Use shared libuv >= 1.30.1 >* Build-Depends node-debbundle-acorn >= 6.1.0~ node-debbundle-acorn is a virtual package, better to depends to node-acorn and node-acorn-* plugin with version Bastien >* Build-Depends libnghttp2-dev >= 1.39.1 >* Tighten dependency on icu >= 64.0~ >* rules: set nghttp2 lib name - upstream assumes lib prefix >* Upstream patch to fix linking against libnode >* Build with snapshot https://github.com/nodejs/node/issues/28675 > Checksums-Sha1: > 2abe4635a936d4e0570a9ff34488bb9f00890fc5 3062 nodejs_12.7.0~dfsg-1.dsc > 3fa8b255a6da286cd391325fabc5a0eca6dcb667 18209816 > nodejs_12.7.0~dfsg.orig.tar.xz > 46d20b443d6ed21636a3a6d90962453a61a22ed5 95128 > nodejs_12.7.0~dfsg-1.debian.tar.xz > 910fb02b9f9721c0a6bedb77c2bca5759cfa9127 7852 > nodejs_12.7.0~dfsg-1_source.buildinfo > Checksums-Sha256: > f5e6c75ec6e5e9adffeb950961906074f371749bf6ed27e85e2e1dd1e78f2032 3062 > nodejs_12.7.0~dfsg-1.dsc > 0a6946e2be78334311dc1f2783b586aed8ccfeb759c068f31275f663cba6f0f0 18209816 > nodejs_12.7.0~dfsg.orig.tar.xz > e381975e3c44aa7473326d24eee6ed817ee44ea37700dbc06822bc5725a490eb 95128 > nodejs_12.7.0~dfsg-1.debian.tar.xz > 17d6069c15923193836f45db859a103cff17a5d8307d12d8241caf62afa03264 7852 > nodejs_12.7.0~dfsg-1_source.buildinfo > Files: > 5b31ed9d70d2db92fba1b3132d1b00c9 3062 javascript optional > nodejs_12.7.0~dfsg-1.dsc > 64e1890a285e8f5c3068616c5a9a931a 18209816 javascript optional > nodejs_12.7.0~dfsg.orig.tar.xz > 9ccfa8c95db80fb87a3e5593d0c25556 95128 javascript optional > nodejs_12.7.0~dfsg-1.debian.tar.xz > 3f6d7814eb988420e57170d62469c638 7852 javascript optional > nodejs_12.7.0~dfsg-1_source.buildinfo > > -BEGIN PGP SIGNATURE- > > iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAl1FyPkSHGthcG91ZXJA > bWVsaXgub3JnAAoJEGYRwF7dOfN03hgP/AlUkXxvMPpyTNSAtsn5LVtwH2oDlsDW > ydU7sI+PB/YvRnuLjeh36/ZpRGWdrczTYvT8vgNgWrewNWJ4T9yxAvGjAlar46ZQ > 8PDmd8FWjvrnjm2WD2A/SewUv26meTN8K+g+h4arvnQMo5PpDNpOmYrwy8vSeVYQ > OXw7HMGu2uJjUMbLq7/1s2WfdHHkUTrtXrmJjPBbhLboFwllkBT/18PPAWA1cLMZ > KjMz8IabCstm1MkW+TOi7klXOYj9m/hQFiltvPunFNykqJZGZqWct4ni4a5xh8LX > fZUT1ZVJ8kmv4AvPLBCL6r85K5vhPSxvSsYhDPs4wXSFRcqwempY38C9ncii/3gG > Dp/gz20UUO0S8PNlbbNREQEgZp8PWLNHwTetkVYddY53OLHCpDRNqKjueT1imq2M > /toojdU1D8CaVgQfXfl8ZmBbOtU9WaKLBz1ANNG25YfxfJUhFP71ARzW8orcI4wz > whARhtIb26LHvB/6xA4qLbwWk68AoTmsizsGx+4K7cEy8O36ZBGcZxtR65req+UB > j35b9TVbAstjdZtIzOrHFKpHfxnqEoOm/eWqqi4BBb1wRbk7GtNOE7AVhpOEwnoH > uYTj2J0pHhQz4G50fmuudoflzSCgemyTbeqk9+UBCX0p184V/hE16ccn5iMSe3ck > rE/ChN7r4r5q > =eXeh > -END PGP SIGNATURE- > > > Thank you for your contribution to Debian. > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] The way to update rollup
Going back after some time out On Tue, Jul 23, 2019 at 9:03 PM Xavier wrote: > > My first results: > > 0.50.0 can build until 0.53.3 > 0.51.7 can build until 0.56.3 > 0.56.1 can build until 0.65.2 > 0.58.1 can build until 0.67.0 at least We need to go by step. Waiting to go to testing then upload a new version. It seems that I have done a three build pass ? Bastien > > This versions seems not usable (npm install + npm run build failed): > 0.56.0, 0.56.4, 0.56.0, 0.56.4, 0.56.5, 0.57.0, 0.57.1, 0.58.0, 0.59.0, > 0.60.0, 0.60.2, 0.60.3, 0.60.4, 0.60.5, 0.60.6, 0.60.7, 0.61.0, 0.61.2, > 0.64.0, 0.66.0, 0.66.1, 0.66.3, 0.68.0, 1.1.0 > > > Le 23/07/2019 à 16:35, Xavier a écrit : > > Hi all, > > > > following upstream package.json, the way to update rollup follows 35 steps: > > > > Min Max Required version > > Now0.51.7 => 0.48.0 > > 0.51.8 0.55.5 => 0.51.7 > > 0.55.6 0.56.5 => 0.55.3 > > 0.57.0 0.57.1 => 0.56.5 > > 0.57.2 0.58.1 => 0.57.1 > > 0.58.2 0.58.2 => 0.58.1 > > 0.59.0 0.59.1 => 0.58.2 > > 0.59.2 0.61.0 => 0.59.1 > > 0.61.1 0.61.1 => 0.60.7 > > 0.61.2 0.63.5 => 0.61.1 > > 0.64.0 0.65.1 => 0.63.5 > > 0.65.2 0.65.2 => 0.65.1 > > 0.66.0 0.66.0 => 0.65.2 > > 0.66.1 0.66.2 => 0.66.0 > > 0.66.3 0.67.4 => 0.66.2 > > 0.68.0 1.0.2 => 0.67.4 > > 1.1.0 1.1.2 => 1.0.2 > > 1.2.0 1.2.5 => 1.1.2 > > 1.3.0 1.3.1 => 1.2.4 > > 1.3.2 1.7.0 => 1.3.1 > > 1.7.1 1.8.0 => 1.7.0 > > 1.9.0 1.9.1 => 1.8.0 > > 1.9.2 1.9.3 => 1.9.1 > > 1.10.0 1.10.0 => 1.9.3 > > 1.10.1 1.10.1 => 1.10.0 > > 1.11.0 1.11.3 => 1.10.1 > > 1.12.0 1.12.0 => 1.11.3 > > 1.12.1 1.12.4 => 1.12.0 > > 1.12.5 1.14.4 => 1.12.4 > > 1.14.4 1.15.1 => 1.14.4 > > 1.15.2 1.15.5 => 1.15.1 > > 1.15.6 1.15.6 => 1.15.5 > > 1.15.7 1.16.3 => 1.15.6 > > 1.16.4 1.16.7 => 1.16.3 > > 1.17.0 1.17.0 => 1.16.7 > > > > Breaking changes > > (https://github.com/rollup/rollup/blob/master/CHANGELOG.md): > > - 0.57.0 (little) > > - 0.60.0 (little) > > - 0.68.0 (easy to patch) > > - 1.0.0 (big) > > > > The best should to have a rollup up-to-date in bulleyes buildable from > > buster (like does gcc I think). We could perhaps embed some rollup > > intermediate version as component and a debian/rules which detect > > current rollup version and selects needed steps. > > > > But of course this requires to decrease these 35 steps. I'm going to > > test which minimal version is really needed and publish an updated list. > > > > NB: we need at least 0.66 to update node-buble (12 steps !) > > > > Cheers, > > Xavier > > > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] node-acorn-dynamic-import_4.0.0-1_amd64.changes ACCEPTED into unstable
On Wed, Jul 10, 2019 at 11:54 AM Pirate Praveen wrote: > > > > On 2019, ജൂലൈ 10 3:12:37 PM IST, Pirate Praveen > wrote: > >This upload broke node-webpack and node-buble and that means a large > >number of packages now FTBFS. > > > > I think we should revert node-acorn-dynamic-import to 4.0.really.3.0 update, > till we fix node-webpack and node-buble. Acorn will include this module, but it is ftpmaster blocked > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#931179: Bug#931179: acorn 6.1.1 please bundle additional plugins needed by nodejs source
On Thu, Jun 27, 2019 at 5:12 PM Jérémy Lal wrote: > > Source: acorn > Severity: wishlist > > https://github.com/nodejs/node/tree/master/deps/acorn-plugins > shows which ones. > > Thanks for considering - i wonder if some of them would rather be > packaged independently or not. Will do but I need ftpmaster first > > Jérémy > > -- System Information: > Debian Release: 10.0 > APT prefers unstable > APT policy: (500, 'unstable'), (500, 'testing') > Architecture: amd64 (x86_64) > > Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) > Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE > Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8), > LANGUAGE=fr_FR.utf8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] RC bugs
Le lun. 18 févr. 2019 à 19:17, Xavier a écrit : > Le 18/02/2019 à 17:46, Pirate Praveen a écrit : > > > > > > On Thu, Feb 14, 2019 at 10:50 PM, Xavier wrote: > >> - node-mocha: #921798: FTBFS (Module not found: Error: Recursion in > >>resolving) > > > > I tried to use rollup instead of webpack (in rollup branch), it builds > > fine, but will not work in a browser (should be enough for node). If we > > cannot fix thr rc bug, I suggest we drop the browser support for now and > > only target node. > > I fully agree. If no one finds this bad, I'll upload node-mocha this > evening. > I find this bad. Why webpack break ? Do we have an idea ? Bastien > > Cheers, > Xavier > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] nodejs V10: buffer problem
Le mar. 1 janv. 2019 à 19:41, Mattia Rizzolo a écrit :
> On Tue, Jan 01, 2019 at 06:48:00PM +0100, Jérémy Lal wrote:
> > > No the problem is that I have at least 20 package in my ddpo to fix
> >
> > Would there be a way for nodejs to know it's running in a test
> environment
> > and not print deprecation warnings there ?
> > If so we should tell it to nodejs maintainer :)
>
> That sounds like an odd thought to me: one would usually *want*
> deprecation warnings in testing enviroments, exactly so they can
> automatically catch such deprecation before it's too late and need to
> rush on them.
>
>
> I don't know this particular error, but if Jeremy claims it's easy to
> fix, surely fixing 20odds is doable?
> Hiding or ignoring all deprecation warnings sounds not really
> future-proof.
>
Yes it ils preferable but it will block transition to testing.
Better between release will be to revert to behavior of node v8 maybe.
Or mass fix by using Buffer = require('safe-buffer').Buffer
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
> more about me: https://mapreri.org : :' :
> Launchpad user: https://launchpad.net/~mapreri `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
> --
> Pkg-javascript-devel mailing list
> Pkg-javascript-devel@alioth-lists.debian.net
>
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] nodejs V10: buffer problem
On Tue, Jan 1, 2019 at 4:25 PM Jérémy Lal wrote: > > >> Le mar. 1 janv. 2019 à 15:35, Bastien ROUCARIES >> a écrit : >>> >>> Hi, >>> >>> I believe we will have a huge problem >>> >>> https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-bn.js/1624829/log.gz > > > Le mar. 1 janv. 2019 à 16:10, Jérémy Lal a écrit : > > Should that go to a node-bn.js bug report ? It's not that difficult to > > fix... > > Also the test failure is triggered by writing to stderr. > So instead of "fixing" the tests (the module itself does not need fixing) one > can simply add > the correct option to test config. No the problem is that I have at least 20 package in my ddpo to fix > > Jérémy -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] nodejs V10: buffer problem
Hi, I believe we will have a huge problem https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-bn.js/1624829/log.gz -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] browserify last depends : test fail
Hi, Could I get help in order to know why test fail ? Repo is here: g...@salsa.debian.org:js-team/node-insert-module-globals.git https://salsa.debian.org/js-team/node-insert-module-globals This is the last depends of the most needed browserify, so I will like to get this before freeze in order to have it for next stable. Happy new year and thanks Bastien -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Rollup really broken
Hi, Acorn is broken due to rollup, and rollup is broken and could not be fixed due to old acorn. I have just fixed rollup-plugin-commonjs. Could you double check. I do not understand why the test suite fail. For rollup I get now for 0.50 (commonjs plugin) SyntaxError: 'import' and 'export' may appear only with 'sourceType: module' (1:0) in /home/bastien/Documents/Personnel/soft/debian/js/_NMU/node-rollup/node-rollup/src/rollup/index.js I have no idea why I get this Bastien -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#899266: Bug#899266: Bug#899266: [node-backbone] FTBFS documentation
On Sun, Dec 30, 2018 at 3:33 PM Jonas Smedegaard wrote: > > Control: tags -1 -ftbfs > Control: retitle -1 backbone: documentation is pre-generated > Control: severity -1 normal > > Quoting Bastien ROUCARIÈS (2018-05-21 23:37:19) > > docs/*.html are build with docco not packaged for debian > > Correct: The documentation files below docs/ in upstream source was > pre-generated using the tool docco which is not in Debian. > > > > So FTBFS could you please rip it ? > > Please avoid using the term "FTBFS" for anything other than "the package > fails to build from source". > > This Debian source package does not fail to build. > > That said, I will consider improve the reproducibility of source > documentation. I really appreciate your close examination, but do not > consider this a serious issue. Last time ftpmaster consider that I should have to rip the documentation > > > > BTW I could not find copyright information about docs/js/*.js (it is > > lazy load) > > I am unaware that anyone has claimed copyright over the documentation. doc/js file are from other projects so seems safe to document; > > > And favicon.ico is generated from svg file.So you could remove and > > regenerated from svg file (found it on wikipedia uploaded by original > > author). > > Interesting. Do you have a URL for the source SVG? Yes https://commons.wikimedia.org/wiki/File:Backbone.js_logo.svg > > > Thanks again for reporting this, > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] components without major risks
On Tue, Nov 27, 2018 at 3:45 PM Xavier wrote: > > Le 27/11/2018 à 15:33, Jonas Smedegaard a écrit : > > Quoting Xavier (2018-11-27 15:22:10) > >> Le 27/11/2018 à 15:03, Jonas Smedegaard a écrit : > >>> Quoting Xavier (2018-11-27 14:00:42) > Le 27/11/2018 à 11:55, Jonas Smedegaard a écrit : > > Hi Xavier and Paolo, > > > > Please allow me to highlight this security-related detail: > > > > Quoting Xavier (2018-11-26 16:29:32) > >> Embedding components without following them may be a lack of security. > >> I think we should have a policy for embedding: > >> - components without major risks => not used in version > >> - components that must be followed => declared as "group" in > >>debian/watch > >> - components that must be followed and used in many other packages > >>=> packaged separately > > > > Quoting Paolo Greppi (2018-11-27 10:52:37) > >> With yesterday's news about the event-stream node module being pwned: > >> https://github.com/dominictarr/event-stream/issues/116 > >> the importance of these matters should be clear to anyone. > >> Probably there is no component "without major risks", and even if it > >> existed, it would be unfair to lay upon the busy maintainer the task > >> of deciding if it is risky or not. > > > > Thanks to _both_ of you (and others in the thread) for all your work > > tackling these issues. > > > > My point here is *not* to point fingers, but to emphasize an important > > aspect of our task as (re)distributors of code: Ensure code integrity > > towards our users. > > > > > > - Jonas > > Thanks, so I propose this policy update - please review this: > - components used only during build => not used in version > (except if they inject some code) > - if upstream version isn't locked on dependencies (see Jérémy remark) > [or if upstream isn't serious?]: > * very little component => not used in version > * components that must be followed and maybe used in many other > packages => packaged separately > * other components => declared as "group" in debian/watch > >>> > >>> Sorry, I don't understand: Why not track code used during build? > >>> > >>> Seems you propose to systematically ignore potential upstream bugfixes. > >>> > >>> > >>> - Jonas > >> > >> I was thinking to modules used to generate documentation, to test,... So > >> even if there is a security issue in them, risk doesn't exist in > >> published binary > > > > I think it is dangerous to try judge systematically and automated with > > no qualitative input what has security implications and what does not! > > > > - Jonas > > You're right but this has some other cons (version string length,...). > Today, components are allowed without any version following. So this > point should also be inserted in Debian policy, shouldn't it ? Components were created for packaging multiple tar of same project. See cernlib package and cry for instance > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] components without major risks
On Tue, Nov 27, 2018 at 3:33 PM Jonas Smedegaard wrote: > > Quoting Xavier (2018-11-27 15:22:10) > > Le 27/11/2018 à 15:03, Jonas Smedegaard a écrit : > > > Quoting Xavier (2018-11-27 14:00:42) > > >> Le 27/11/2018 à 11:55, Jonas Smedegaard a écrit : > > >>> Hi Xavier and Paolo, > > >>> > > >>> Please allow me to highlight this security-related detail: > > >>> > > >>> Quoting Xavier (2018-11-26 16:29:32) > > Embedding components without following them may be a lack of security. > > I think we should have a policy for embedding: > > - components without major risks => not used in version > > - components that must be followed => declared as "group" in > > debian/watch > > - components that must be followed and used in many other packages > > => packaged separately > > >>> > > >>> Quoting Paolo Greppi (2018-11-27 10:52:37) > > With yesterday's news about the event-stream node module being pwned: > > https://github.com/dominictarr/event-stream/issues/116 > > the importance of these matters should be clear to anyone. > > Probably there is no component "without major risks", and even if it > > existed, it would be unfair to lay upon the busy maintainer the task > > of deciding if it is risky or not. > > >>> > > >>> Thanks to _both_ of you (and others in the thread) for all your work > > >>> tackling these issues. > > >>> > > >>> My point here is *not* to point fingers, but to emphasize an important > > >>> aspect of our task as (re)distributors of code: Ensure code integrity > > >>> towards our users. > > >>> > > >>> > > >>> - Jonas > > >> > > >> Thanks, so I propose this policy update - please review this: > > >> - components used only during build => not used in version > > >>(except if they inject some code) > > >> - if upstream version isn't locked on dependencies (see Jérémy remark) > > >>[or if upstream isn't serious?]: > > >>* very little component => not used in version > > >>* components that must be followed and maybe used in many other > > >> packages => packaged separately > > >>* other components => declared as "group" in debian/watch > > > > > > Sorry, I don't understand: Why not track code used during build? > > > > > > Seems you propose to systematically ignore potential upstream bugfixes. > > > > > > > > > - Jonas > > > > I was thinking to modules used to generate documentation, to test,... So > > even if there is a security issue in them, risk doesn't exist in > > published binary > > I think it is dangerous to try judge systematically and automated with > no qualitative input what has security implications and what does not! I agree here... No more node_modules inside package. At least it will be fixed once > > - Jonas > > -- > * Jonas Smedegaard - idealist & Internet-arkitekt > * Tlf.: +45 40843136 Website: http://dr.jones.dk/ > > [x] quote me freely [ ] ask before reusing [ ] keep private > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] script to generate debian/watch for embedding nodejs modules
On Mon, Nov 26, 2018 at 7:58 PM Jérémy Lal wrote: > > > > Le lun. 26 nov. 2018 à 17:29, Xavier a écrit : >> >> Xavier wrote: >> >> ... >> >> Looks acceptable IMO >> > >> > Policy update: >> > - components used only during build => not used in version >> >(except if they inject some code) >> > - components without major risks=> not used in version >> > - components that must be followed => declared as "group" in >> >debian/watch >> > - components that must be followed and used in many other packages >> >=> packaged separately >> > >> > Note: I wrote this to help js-team and decrease time to wait in NEW >> > queue. If you feel that "crazy", please simply delete >> > https://wiki.debian.org/Javascript/GroupSourcesTutorial and the links to >> > this page. >> > >> > I you don't want to do it by yourself, I can remove the page for you. >> > Just ask me to do it. > > > This is certainly not crazy, and while i'm not myself completely convinced > it's the right approach, > (mostly because i did not took the time to review and practice), it's the > closest thing we have > to a usable solution. > > Please don't stop there, it would be such a waste. > > About the bundled packages and the weird version encoding all the bundled > versions: > most upstreams that are serious about their packaging now use a package-lock > file, > effectively locking down a released version to the needed versions of > dependencies. > When it's the case, it means that any change in versions of dependencies will > be reflected > by a new parent package version. In that case, it's useless to encode > dependencies versions > in the parent debian package version ? No it is not useless because using now sed (and i future a dh helper) you could add automagically a provides: node-foo (=version)... So I think it is a bad idea for a debian/rules point of view > > Jérémy > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] script to generate debian/watch for embedding nodejs modules
On Mon, Nov 26, 2018 at 4:00 PM Pirate Praveen wrote: > > On 11/26/18 8:25 PM, Paolo Greppi wrote: > > The file names are crazy ! is this the way the Debian JavaScript > > Maintainers team wants to go ? > > If you are brave, generate the debian/watch for npm and try running uscan > > on it ... > > I prefer to use this approach which is much cleaner and manageable > https://wiki.debian.org/Javascript/Nodejs/Npm2Deb#Embedding_some_modules As I have already said uscan and pkg-component are orthogonal. Uscan is only for download. We use existing infrastructure and it is better than to use external tooll. > and for npm, upstream itself provides node_modules inside their tar, so > we just need to remove the packaged modules from it (repack with > Files-Excluded). Yes and it is a security problems because we hide depends and it create code copy. I strongly oppose to this. We are a distrib not upstream. > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] New javascript packages for taliesin
On Wed, Nov 14, 2018 at 3:09 PM Pirate Praveen wrote:
>
>
>
> On 2018, നവംബർ 14 7:23:24 PM IST, Nicolas Mora wrote:
> >Le 2018-11-14 05:43, Pirate Praveen a écrit :
> >Also, I just realized that the script jest/bin/jest.js contains this
> >simple code:
> >
> >require('jest-cli/bin/jest');
> >
> >So I think we should remove the file debian/links and add a file
> >debian/node-jest-cli.links instead that will contain the following:
> >
> >usr/lib/nodejs/jest-cli/bin/jest.js usr/bin/jest
> >
> >What do you think?
>
> Test it and see if it is working. Also we may need to move all jest modules
> to a single binary package and add Provides for others.
>
> >>> I'm currently making a package for istanbuljs that is a meta package
> >>> like jest and some of its modules are required for node-jest-cli.
> >>
> >> I think Istanbul is already in NEW.
> >>
> >Yes, I saw that, but that the package node-istanbul in NEW comes from
> >github.com/gotwarlost/istanbul [1], and the one required by jest are
> >node-istanbul-lib-coverage, node-istanbul-lib-instrument and
> >node-istanbul-lib-source-maps, which are in
> >github.com/istanbuljs/istanbul
> >
> >I think they are not the same...
> >
> >I shall call my new package node-istanbuljs to avoid confusion.
No it is nyc. So we need to package nyc
>
> OK.
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
> --
> Pkg-javascript-devel mailing list
> Pkg-javascript-devel@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] New javascript packages for taliesin
On Sun, Nov 11, 2018 at 5:15 PM Pirate Praveen wrote: > > > > On 2018, നവംബർ 11 7:13:47 PM IST, Nicolas Mora wrote: > >Hello, > > > >I'm working on packaging Taliesin, an audio streaming server with a > >front-end written in react [1]. > > Welcome to javascript team. > > >To build the front-end, I need some new node packages. I've already > >starting packaging some of them, but I prefer asking the javascript > >team > >about it first, to make sure I'm making it right. > > That is a good approach. We have some very recent changes in policy which is > yet to be documented clearly. > > >Among the required new packages, there are > >i18next-browser-languagedetector and i18next-xhr-backend that require > >the packages serialize-javascript [2] and jest-worker. > > If a module is simple (no build steps) then it should be embedded. Not embded use group source feature of git uscan please. > >I've already packaged those last 2 and uploaded them to mentors.d.n. > >But > >then I saw that a package node-jest is already in preparation so I can > >offer my help to package node-jest instead. > > Just have a look at the repo in salsa. > > >I also made a new package for node-i18next. There's already a package > >libjs-i18next but the version is quite old (1.7.1) when the current > >version is 12.0.0. > > We should try to update the existing package. > > >Another package in mentors.d.n is react-audio-player [3], a wrapper for > >the html tag binded with react. > > > >Among the other packages I need, there are some that are easy, like > >react-i18next, but some others will probably be difficult to build, > >considering their dependencies. I'm thinking about react-bootstrap and > >redux especially. I've started to package them and their dependencies. > > Embed the simple one. Please use group package > > >I'm also willing to help the javascript with other packages than the > >ones I need if you want. > > Yes, that would be good. Getting jest and ava would be good. > > >Thanks in advance for your help and advises. > > Happy to help. You can come to our irc channel as well for real time help. > > >/Nicolas > > > >[1] - https://salsa.debian.org/babelouest-guest/taliesin > >[2] - https://mentors.debian.net/package/node-serialize-javascript > >[3] - https://mentors.debian.net/package/node-react-audio-player > > > >-- > >Pkg-javascript-devel mailing list > >Pkg-javascript-devel@alioth-lists.debian.net > >https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] RFC: javascript bundle of small packages
On Thu, Nov 1, 2018 at 6:56 PM Chris Lamb wrote: > > Bastien, > > > The WIP acorn package uploaded to experimental is a tentative to group > > small node package. > > > > We are waiting for feedback about viability of this approach. > > For the avoidance of all doubt I note that you have mailed my > la...@debian.org address directly (ie. me in To, CCing others & > teams) but I have no bandwidth to review or comment on this. > > I will therefore not be participating in this thread. (I replied to > your IRC messages to provide low-touch facilitation and to try > and avoid frustration on your part.) Noted with thanks. Understood your bandwith problem > > Regards, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org / chris-lamb.co.uk >`- -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] RFC: javascript bundle of small packages
Hi all, > > Dear ftpmaster could you review before I upload to experimental, > > particularly breaks/replace line. The WIP acorn package uploaded to experimental is a tentative to group small node package. The goal is to use uscan to download a few (<=10 packages) in a debbundle package. Xadd here in copy has created a merge request for uscan and we are waiting from ftpmaster about the technique we used. We acknowledge debian/rules is not pretty, but we plan to improve debhelper in the future. Debian is a docraty, and this your contributation to the small package problems. We are waiting for feedback about viability of this approach. If you want we could post on debian-devel or open a wiki page, but we expect to solve the small packages problem ASAP so please give us some guidance. Bastien On Tue, Oct 30, 2018 at 2:22 PM Chris Lamb wrote: > > Bastien, > > > What's wrong with just uploading to experimental? I'm afraid I > won't have bandwidth to review un-uploaded packages and I doubt > other ftpmasters would too, alas. > > https://salsa.debian.org/js-team/acorn/blob/master/debian/control#L40-42 > > (I don't really understand what is going on here anyway.) > > > Regards, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org / chris-lamb.co.uk >`- -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] RFC: javascript bundle of small packages
On Tue, Oct 30, 2018 at 2:22 PM Chris Lamb wrote: > > Bastien, > > > Dear ftpmaster could you review before I upload to experimental, > > particularly breaks/replace line. > > What's wrong with just uploading to experimental? I'm afraid I > won't have bandwidth to review un-uploaded packages and I doubt > other ftpmasters would too, alas. Ok done > https://salsa.debian.org/js-team/acorn/blob/master/debian/control#L40-42 > > (I don't really understand what is going on here anyway.) this bundle package will replace node-acorn node-acorn-jsx and node-acorn-dynamic-import. I want smooth update > > Regards, > > -- > ,''`. > : :' : Chris Lamb > `. `'` la...@debian.org / chris-lamb.co.uk >`- -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] RFC: javascript bundle of small packages
Hi, I have just pushed a new version of acorn and associated small package to salsa (https://salsa.debian.org/js-team/acorn) It group small package using dpkg module and for now fakeupstream redirector. We plan to modify uscan (yadd?) in order to get this feature upstream. We also plan to improve debhelper in order to get the version parsing of control automatic, and to ease build. But we believe it is a first step in the good direction. Dear ftpmaster could you review before I upload to experimental, particularly breaks/replace line. Package that bundle a few package will be called node-debbundle-foo. I plan to update policy Bastien -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] babel 6 -> 7 transition - call for help
On Tue, Oct 23, 2018 at 3:36 PM Pirate Praveen wrote: > > Hi team, > > Webpack 3 -> 4 update was requested recently which needs babel 7. In > addition to it, esm needs (which will allow us to skip rollup for ES > modules to help fix many circular dependencies) babel 7, gitlab also > needs babel 7. > > I started working on the update and just looked at the devDependencies, > it needs browserify, webpack, rollup and gulp to build! This is new > record even by node's own standard! > > Luckily we have a recent enough nodejs in unstable and we can skip most > of the transpilation steps (tested with acorn) but it requires a manual > conversion of ES modules to CJS. It is sad to see native support for ES > modules remaining experimental for ever in nodejs. > > Let me know if anyone feel brave enough to join this effort. > > Thanks > Praveen Hi, I have achieved to get node-acorn in shape Will upload in experimental > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] acorn status
Hi, I have resolve the problem. Thank for your help On Mon, Oct 22, 2018 at 10:43 PM Xavier wrote: > > Le 22/10/2018 à 21:21, Bastien ROUCARIES a écrit : > > Ok, thanks. > > Last bug fixed, you missed a filenamemangle. > > Now uscan downloads the 3 components + main package > > > The main bug is why test fail > > On Mon, Oct 22, 2018 at 9:08 PM Xavier wrote: > >> > >> Le 22/10/2018 à 15:23, Bastien ROUCARIES a écrit : > >>> On Mon, Oct 22, 2018 at 1:55 PM Xavier wrote: > >>>> > >>>> Le 22/10/2018 à 13:52, Bastien ROUCARIES a écrit : > >>>>> Hi, > >>>>> > >>>>> I have grouped some small package for acorn, see salsa > >>>>> > >>>>> But i could not progress due to dynamic-import failling test > >>>>> > >>>>> Do you have idea ? > >>>>> > >>>>> Bastien > >>>> > >>>> There is a bug with gbp. This works: > >>>> - launch uscan > >>>> - use gbp import-orig ../main-package.orig.tar.gz > >>>> > >>>> gbp --uscan fails > >>> > >>> I use git dpm. It is eassier for patch > >> > >> I fixed your debian/watch: there was 2 "debian". There is still a bug > >> somewhere... > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] acorn status
Ok, thanks. The main bug is why test fail On Mon, Oct 22, 2018 at 9:08 PM Xavier wrote: > > Le 22/10/2018 à 15:23, Bastien ROUCARIES a écrit : > > On Mon, Oct 22, 2018 at 1:55 PM Xavier wrote: > >> > >> Le 22/10/2018 à 13:52, Bastien ROUCARIES a écrit : > >>> Hi, > >>> > >>> I have grouped some small package for acorn, see salsa > >>> > >>> But i could not progress due to dynamic-import failling test > >>> > >>> Do you have idea ? > >>> > >>> Bastien > >> > >> There is a bug with gbp. This works: > >> - launch uscan > >> - use gbp import-orig ../main-package.orig.tar.gz > >> > >> gbp --uscan fails > > > > I use git dpm. It is eassier for patch > > I fixed your debian/watch: there was 2 "debian". There is still a bug > somewhere... -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] acorn status
On Mon, Oct 22, 2018 at 1:55 PM Xavier wrote: > > Le 22/10/2018 à 13:52, Bastien ROUCARIES a écrit : > > Hi, > > > > I have grouped some small package for acorn, see salsa > > > > But i could not progress due to dynamic-import failling test > > > > Do you have idea ? > > > > Bastien > > There is a bug with gbp. This works: > - launch uscan > - use gbp import-orig ../main-package.orig.tar.gz > > gbp --uscan fails I use git dpm. It is eassier for patch -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] acorn status
Hi, I have grouped some small package for acorn, see salsa But i could not progress due to dynamic-import failling test Do you have idea ? Bastien -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#911365: Bug#911365: New upstream is out
On Fri, Oct 19, 2018 at 9:54 AM Julien Puydt wrote: > > Package: node-acorn-dynamic-import > Version: 3.0.0-1 > Severity: wishlist > > Hi, > > I need a more recent version of this package to update the node-buble > package. Need to be merged with node-acorn work on it (avoid a circular ref) Bastien > > Thanks, > > jpuydt on irc.debian.org > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] GroupSourcesTutorial page to review
On Mon, Oct 22, 2018 at 12:34 PM Xavier wrote: > > Le 22/10/2018 à 11:23, Bastien ROUCARIES a écrit : > > I really need it for next ckeditor (40 small packages) and acorn. > > > > For uscan I do not think the alpha sort is worthwhile. Let version be > > in watch file order. > > Do you speak on fakeuptream-like behavior ? If yes, I think a > 1.0.0+~23.4.65 version (sum) will be more efficient for 40 packages. It > guaranties that upstream updates will be detected Sum is not bijective so your are not stateless. I plan to cut in 10 packages each ckeditor. BTW see that I have just pushed on salsa for acorn. We really need it. Bastien > > > Bastien > > On Sat, Oct 20, 2018 at 5:18 PM Xavier wrote: > >> > >> Le 20/10/2018 à 16:47, Bastien ROUCARIES a écrit : > >>> On Thu, Sep 27, 2018 at 3:29 PM Bastien ROUCARIES > >>> wrote: > >>>> > >>>> On Mon, Sep 24, 2018 at 10:03 AM Xavier wrote: > >>>>> > >>>>> Le 13/09/2018 à 11:16, Xavier a écrit : > >>>>>> Le 11/09/2018 à 19:48, Pirate Praveen a écrit : > >>>>>>> > >>>>>>> On 9/11/18 10:45 PM, Jérémy Lal wrote: > >>>>>>>> Hi Xavier, > >>>>>>>> > >>>>>>>> The example in Provides section should be written > >>>>>>>> Provides: node-ta, node-tb > >>>>>>>> ? > >>>>>>> > >>>>>>> I think there should not be Provides as it implies sharing, which will > >>>>>>> negate the reason why we are embedding in the first place. > >>>>>> > >>>>>> Hello, > >>>>>> > >>>>>> I updated https://wiki.debian.org/Javascript/GroupSourcesTutorial to > >>>>>> write a ~policy to choose to embed or not and to export or not. Please > >>>>>> review it > >>>>>> > >>>>>> Cheers, > >>>>>> Xavier > >>>>> > >>>>> Hi all, > >>>>> > >>>>> I rewrote uscan and my work has been accepted by devscripts team (no > >>>>> behavior change for now but OO rewrite will help a lot). If you agree, I > >>>>> can add the same embedding system in uscan than I've done for > >>>>> fakeupstream.cgi > >>>> > >>>> Yes it will really help. > >>> > >>> Any news of uscan ? > >> > >> Hello, > >> > >> I rewrote uscan and fix some bugs. I can embed fakeupstream behavior in > >> uscan but it needs a consensus, here at least. > >> > >> -- > >> Pkg-javascript-devel mailing list > >> Pkg-javascript-devel@alioth-lists.debian.net > >> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel > > -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] GroupSourcesTutorial page to review
I really need it for next ckeditor (40 small packages) and acorn. For uscan I do not think the alpha sort is worthwhile. Let version be in watch file order. Bastien On Sat, Oct 20, 2018 at 5:18 PM Xavier wrote: > > Le 20/10/2018 à 16:47, Bastien ROUCARIES a écrit : > > On Thu, Sep 27, 2018 at 3:29 PM Bastien ROUCARIES > > wrote: > >> > >> On Mon, Sep 24, 2018 at 10:03 AM Xavier wrote: > >>> > >>> Le 13/09/2018 à 11:16, Xavier a écrit : > >>>> Le 11/09/2018 à 19:48, Pirate Praveen a écrit : > >>>>> > >>>>> On 9/11/18 10:45 PM, Jérémy Lal wrote: > >>>>>> Hi Xavier, > >>>>>> > >>>>>> The example in Provides section should be written > >>>>>> Provides: node-ta, node-tb > >>>>>> ? > >>>>> > >>>>> I think there should not be Provides as it implies sharing, which will > >>>>> negate the reason why we are embedding in the first place. > >>>> > >>>> Hello, > >>>> > >>>> I updated https://wiki.debian.org/Javascript/GroupSourcesTutorial to > >>>> write a ~policy to choose to embed or not and to export or not. Please > >>>> review it > >>>> > >>>> Cheers, > >>>> Xavier > >>> > >>> Hi all, > >>> > >>> I rewrote uscan and my work has been accepted by devscripts team (no > >>> behavior change for now but OO rewrite will help a lot). If you agree, I > >>> can add the same embedding system in uscan than I've done for > >>> fakeupstream.cgi > >> > >> Yes it will really help. > > > > Any news of uscan ? > > Hello, > > I rewrote uscan and fix some bugs. I can embed fakeupstream behavior in > uscan but it needs a consensus, here at least. > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#911367: Bug#911367: New upstream is out
Note that it will need a hug testing due to change of API for plugins. On Sat, Oct 20, 2018 at 4:40 PM Bastien ROUCARIES wrote: > > Will take > On Fri, Oct 19, 2018 at 10:21 AM Julien Puydt > wrote: > > > > Package: node-acorn > > Version: 5.5.3+ds3-1 > > Severity: wishlist > > > > Hi, > > > > I need a more recent version of this package to update the node-buble > > package. > > > > Thanks, > > > > jpuydt on irc.debian.org > > > > -- > > Pkg-javascript-devel mailing list > > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] GroupSourcesTutorial page to review
On Thu, Sep 27, 2018 at 3:29 PM Bastien ROUCARIES wrote: > > On Mon, Sep 24, 2018 at 10:03 AM Xavier wrote: > > > > Le 13/09/2018 à 11:16, Xavier a écrit : > > > Le 11/09/2018 à 19:48, Pirate Praveen a écrit : > > >> > > >> On 9/11/18 10:45 PM, Jérémy Lal wrote: > > >>> Hi Xavier, > > >>> > > >>> The example in Provides section should be written > > >>> Provides: node-ta, node-tb > > >>> ? > > >> > > >> I think there should not be Provides as it implies sharing, which will > > >> negate the reason why we are embedding in the first place. > > > > > > Hello, > > > > > > I updated https://wiki.debian.org/Javascript/GroupSourcesTutorial to > > > write a ~policy to choose to embed or not and to export or not. Please > > > review it > > > > > > Cheers, > > > Xavier > > > > Hi all, > > > > I rewrote uscan and my work has been accepted by devscripts team (no > > behavior change for now but OO rewrite will help a lot). If you agree, I > > can add the same embedding system in uscan than I've done for > > fakeupstream.cgi > > Yes it will really help. Any news of uscan ? > > Bastien > > > > > Cheers, > > Xavier > > > > -- > > Pkg-javascript-devel mailing list > > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#911367: Bug#911367: New upstream is out
Will take On Fri, Oct 19, 2018 at 10:21 AM Julien Puydt wrote: > > Package: node-acorn > Version: 5.5.3+ds3-1 > Severity: wishlist > > Hi, > > I need a more recent version of this package to update the node-buble > package. > > Thanks, > > jpuydt on irc.debian.org > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#876618: Bug#876618: science.js build-depends on removed nodejs-legacy
Il Le ven. 28 sept. 2018 à 07:27, Petter Reinholdtsen a écrit : > Control: tags -1 + help upstream confirmed > > [Jérémy Lal] > > Depending on nodejs-legacy was a serious bug in the first place. > > Anyway (nodejs >= 6.11.2~) installs /usr/bin/node now. > > I had a look at this, and do not know how to fix it. Replacing > nodejs-legacy with nodejs in d/control is simple enough, but then the build > fail like this: > > cat science.core.js science.lin.js science.stats.js >> science.v1.js > uglifyjs < science.v1.js > science.v1.min.js > node src/package.js > package.json > (node:7549) [DEP0027] DeprecationWarning: util.puts is deprecated. Use > console.log instead. > rm science.stats.js science.lin.js science.core.js > make[2]: Leaving directory '/home/pere/src/debian/science.js-debian' > make[1]: Leaving directory '/home/pere/src/debian/science.js-debian' >debian/rules override_dh_auto_test > make[1]: Entering directory '/home/pere/src/debian/science.js-debian' > vows test/env-assert.js test/\*/\*-test.js > module.js:549 > throw err; > ^ > Vow need to be updated or your pa ckage néed to dépend to node-glob > > Error: Cannot find module 'glob' > at Function.Module._resolveFilename (module.js:547:15) > at Function.Module._load (module.js:474:25) > at Module.require (module.js:596:17) > at require (internal/module.js:11:18) > at Object. (/usr/lib/nodejs/vows/bin/vows:7:14) > at Module._compile (module.js:652:30) > at Object.Module._extensions..js (module.js:663:10) > at Module.load (module.js:565:32) > at tryModuleLoad (module.js:505:12) > at Function.Module._load (module.js:497:3) > make[1]: *** [debian/rules:17: override_dh_auto_test] Error 1 > make[1]: Leaving directory '/home/pere/src/debian/science.js-debian' > make: *** [debian/rules:8: build] Error 2 > dpkg-buildpackage: error: debian/rules build subprocess returned exit > status 2 > debuild: fatal error at line 1152: > dpkg-buildpackage -rfakeroot -us -uc -ui -ICVS -I.#* -I.cvsignore -I.bzr > -I.svn -I.git failed > > Note, the git repo is at salsa now, > https://salsa.debian.org/js-team/science.js.git >. > > -- > Happy hacking > Petter Reinholdtsen > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] GroupSourcesTutorial page to review
On Mon, Sep 24, 2018 at 10:03 AM Xavier wrote: > > Le 13/09/2018 à 11:16, Xavier a écrit : > > Le 11/09/2018 à 19:48, Pirate Praveen a écrit : > >> > >> On 9/11/18 10:45 PM, Jérémy Lal wrote: > >>> Hi Xavier, > >>> > >>> The example in Provides section should be written > >>> Provides: node-ta, node-tb > >>> ? > >> > >> I think there should not be Provides as it implies sharing, which will > >> negate the reason why we are embedding in the first place. > > > > Hello, > > > > I updated https://wiki.debian.org/Javascript/GroupSourcesTutorial to > > write a ~policy to choose to embed or not and to export or not. Please > > review it > > > > Cheers, > > Xavier > > Hi all, > > I rewrote uscan and my work has been accepted by devscripts team (no > behavior change for now but OO rewrite will help a lot). If you agree, I > can add the same embedding system in uscan than I've done for > fakeupstream.cgi Yes it will really help. Bastien > > Cheers, > Xavier > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] babel-preset-env error that does not allow to test package
Hi,
I am stuck since two days to an error between mocha and babel-preset-error.
I have just pushed an experimental branch to babel-preset-env showing the error.
/usr/lib/nodejs/babel-core/lib/transformation/file/options/option-manager.js:328
throw e;
^
Error: Options {"loose":true} passed
Do you have idea ?
bastien
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] acorn porting to es5
I have just pushed a wip acorn to salsa repo. I block on an acorn module that fail test On Wed, Sep 26, 2018 at 10:34 AM ashutosh singh wrote: > > I have updated the code. The new code can be found at > https://salsa.debian.org/juggernaut451-guest/acorn/tree/cjs > Just an update that code is changed to common js rather than es5. Please > review it and do let me know if more changes to be made > > On Tue, Sep 25, 2018 at 6:48 PM ashutosh singh wrote: >> >> Thanks for the update. Can you please have a look at this >> https://salsa.debian.org/juggernaut451-guest/acorn/tree/es5 >> It's basically the same acorn version only import/export statement have >> changed also added some try/catch. As then we would not need rollup. >> >> On Tue, Sep 25, 2018 at 6:14 PM Bastien ROUCARIES >> wrote: >>> >>> I am working on acorn, it is not easy. >>> >>> Will try to push something today >>> On Tue, Sep 25, 2018 at 1:29 PM ashutosh singh >>> wrote: >>> > >>> > >>> > Hello >>> > >>> > I am porting acorn to es5 as currently it's using rollup to convert from >>> > es6 to es5. As next step would be compiling bluebird with this es5 >>> > version. I am able to build the bluebird with it. Need little help to >>> > verify that i am doing the correct way as i am new to debian family. >>> > >>> > >>> > -- >>> > Cheers! >>> > Ashutosh Kumar Singh >>> > www.ashutoshksingh.com >>> > -- >>> > Pkg-javascript-devel mailing list >>> > Pkg-javascript-devel@alioth-lists.debian.net >>> > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel >> >> >> >> -- >> Cheers! >> Ashutosh Kumar Singh >> www.ashutoshksingh.com > > > > -- > Cheers! > Ashutosh Kumar Singh > www.ashutoshksingh.com -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] acorn porting to es5
I am working on acorn, it is not easy. Will try to push something today On Tue, Sep 25, 2018 at 1:29 PM ashutosh singh wrote: > > > Hello > > I am porting acorn to es5 as currently it's using rollup to convert from es6 > to es5. As next step would be compiling bluebird with this es5 version. I am > able to build the bluebird with it. Need little help to verify that i am > doing the correct way as i am new to debian family. > > > -- > Cheers! > Ashutosh Kumar Singh > www.ashutoshksingh.com > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Re: Shipping DefinitelyTyped definitions : one binary package per definition?
On Mon, Sep 24, 2018 at 12:24 PM Pirate Praveen wrote: > > > > On 2018, സെപ്റ്റംബർ 24 2:28:00 PM IST, Bastien ROUCARIES > wrote: > >On Mon, Sep 24, 2018 at 10:43 AM Pirate Praveen > > wrote: > >> > >> On 9/24/18 2:09 PM, Bastien ROUCARIES wrote: > >> >> I think it is over engineering and making things unnecessarily > >complex. This can be a fallback option if a separate version of type > >definition is required instead of the centrally shipped version. > >> > And how to you keep version in sync ? > >> > >> You always ship the latest in node-typescript-types package and ship > >> separate definitions only in case something don't work. I don't think > >we > >> have to keep it strictly in sync with the node modules. For example, > >we > >> have nodejs 8.11.2 but @types/node only has 8.10.x. > > > >I believe it is quite fragile compared to > >https://wiki.debian.org/Javascript/GroupSourcesTutorial > > I think the type definitions don't change for every js code change so its not > as fragile. If it really change to breaking builds, then only we need to do > the extra work of adding it to corresponding node package. Adding multiple > tarballs is real pain and that has to be the last resort I think. No it is quite easy with newer fakeupstream support. It a joy, Did you try ? Bastien > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > -- > Pkg-javascript-devel mailing list > Pkg-javascript-devel@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
