Package: node-babel-types
Version: 6.26.0+repack-4
Severity: normal
Dear Maintainer,
Got this while trying to upgrade node-babel -
Unpacking node-babel7 (7.17.8+~cs214.260.191-2) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-cLw40Y/12-node-babel7_7.17.8+~cs214.260.191-2_all.deb
(--unpa
Package: node-babel7
Version: 7.17.6+~cs214.260.190-1
Severity: normal
Dear Maintainer,
Got the following while upgrading today -
Unpacking node-babel7 (7.17.8+~cs214.260.191-2) over
(7.17.6+~cs214.260.190-1) ...
dpkg: error processing archive
/tmp/apt-dpkg-install-dogkWA/60-node-babel7_7.17.8+~c
Package: node-core-js
Version: 3.8.1-1
Severity: normal
User : debian...@lists.debian.org
Usertags : broken-symlink adequate
Dear Maintainer,
While upgrading I was hit by a broken symlink of node-core-js. On
further investigation got the following, please fix it -
$ adequate node-core-js
nod
Reply at bottom :-
On 09/04/2020, Jérémy Lal wrote:
> Le ven. 10 avr. 2020 à 01:13, shirish शिरीष a
> écrit :
>
>> Hi all,
>>
>> Please CC me if somebody replies, thank you :)
>>
>> For a long time webpack and rollup were supposed to be problems. They
Hi all,
Please CC me if somebody replies, thank you :)
For a long time webpack and rollup were supposed to be problems. They
are now in testing, so what else is remaining ?
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://crea
Package: libjs-sprintf-js
Version: 1.1.2+ds1-1
Severity: normal
User : debian...@lists.debian.org
Usertags : broken-symlink adequate
Dear Maintainer,
I was installing some binaries when I came across the following -
libjs-sprintf-js: broken-symlink
/usr/share/doc/libjs-sprintf-js/examples/an
Dear all,
Please CC me if somebody responds.
Would it be possible to package corona-cli for Debian.
The package lives at https://registry.npmjs.org/corona-cli
I could have installed it via instructions given at [1] . It would be
a handy tool to have stats, about the disease on the CLI itself.
Package: gulp
Version: 4.0.2-6
Severity: normal
User: debian...@lists.debian.org
Usertags : broken-symlink adequate
Dear Maintainer,
Adequate informed me that gulp has a broken-symlink. Please fix it.
$ adequate gulp
gulp: broken-symlink /usr/share/bash-completion/completions/gulp ->
..
Hi all,
Please cc me if somebody responds.
Can anybody comment on Xavier's call or ideas about npm migration to
sid/unstable [1] ?
1.
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2020-January/038122.html
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quo
at bottom :-
On 13/12/2019, Pirate Praveen wrote:
>
>
> Current webpack 4.7 need acorn 5, and webpack 4.30 only works with acorn 6.
> So if we upload acorn 6 to unstable, it will break webpack 4.7.
>
The numbering seems to be all over the place how is it that webpack
4.7 = acorn 5 and webpack
at bottom :-
On 26/11/2019, Jérémy Lal wrote:
>
> Not precisely.
> Upstream v8 currently supports mipsel, however upstream node doesn't,
> so mipsel issues are not investigated. Patches are accepted, though.
> However it's usually tricky to find out what's wrong. And it takes an
> eternity
> t
Reply in-line :-
On 26/11/2019, Jérémy Lal wrote:
>
> Nodejs 12 will eventually go into sid... it is in good shape in
> experimental right now.
> However it fails to build on mips(64)el (surely a v8 issue, with a bit of
> luck upstream will
> solve it).
Is there a ticket/issue somewhere upstre
Hi all,
I had been having a long running issue with riot-web as shared in [1]
One of the causes seems to be the old nodejs that we have while
upstream uses the latest nodejs as shared in the picture attached.
Chromium seems to be a bit behind but not much, electron is not
packaged to Debian so no
Package: node-semver
Version: 6.3.0-2
Severity: normal
Usertags: broken-symlink adequate
User: debian...@lists.debian.org
Adequate reported broken-symlink in node-semver while upgrading one of
my machines today -
$ adequate node-semver
node-semver: broken-symlink /usr/bin/semver -> ../share/node
at bottom :-
> That's the reason why it's not going to testing.
> I started investigating... up to the point non-debian work took over my
> time.
> Feel free to give some help !
>
>
>> Additional info:
>> Piuparts tested OK -
>> https://piuparts.debian.org/sid/source/n/nodejs.html
>>
ing to cause
> troubles (even if not that much) so will be announced.
>
> Does this answer your question?
>
> Le ven. 18 oct. 2019 à 20:57, shirish शिरीष a
> écrit :
>
>> Hi all,
>>
>> I have been observing nodejs for quite sometime and also seeing th
Hi all,
I have been observing nodejs for quite sometime and also seeing the
archives, but the archives do not tell what is happening.
While as Utkarsh shared in at
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2019-October/036552.html
From an outsider one is unable to know what
Package: node-form-data
Version: 2.3.2-2
Severity: normal
Usertags: broken-symlink adequate
User: debian...@lists.debian.org
Dear Maintainer,
Thank you for maintaining node-form-data package.
I was updating my system when I saw the following -
$ adequate node-form-data
node-form-data: broken-s
Dear all,
I just cloned the repo. from
https://anonscm.debian.org/git/pkg-javascript/npm.git/
I saw that in /npm/debian/patches$ cat 2011_node-gyp-path.patch
you see -
if [ "x$npm_config_node_gyp" = "x" ]; then
- node "`dirname "$0"`/../../node_modules/node-gyp/bin/node-gyp.js" "$@"
this is
Package: npm
Version: 5.8.0+ds4-1
Severity: normal
Dear Maintainer,
Thank you for maintaining npm. While trying the new version got the
following via adequate -
adequate found packaging bugs
-
npm: broken-symlink
/usr/share/npm/node_modules/npm-lifecycle/node_modules
Package: npm
Version: 5.8.0+ds3-1
Severity: normal
Usertags: broken-symlink adequate
User: debian...@lists.debian.org
Dear Maintainer,
While updating my system came across the following -
$ adequate npm
npm: broken-symlink /usr/share/npm/node_modules/.bin/mkdirp ->
../mkdirp/bin/cmd.js
npm: bro
Package: npm
Version: 5.8.0+ds-2
Severity: normal
Dear Maintainer,
I was trying to build an upstream version of requestpolicy and got the
following warnings -
~/games/requestpolicy$ make
npm install
npm ERR! write after end
npm ERR! write after end
npm ERR! write after end
npm ERR! write after e
22 matches
Mail list logo
