Package: node-http-proxy-agent
Version: 7.0.0~0~2023071921-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' f
Package: node-json-stable-stringify,node-fast-json-stable-stringify
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 1.0.2+~cs5.2.34-1
Control: found -1 2.1.0-1
Hi,
during a test with piuparts I noticed your package failed to install
because
Package: seek-bzip
Version: 1.0.5-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
broken symlinks:
0m22.5s ERROR: FAIL: Broken symlinks:
/usr/bin/seek-bunzip -> ../share/nodejs/@openpgp/seek-bzip/
Control: affects -1 + node-babel-loader
Another set of missing B+R is node-babel-generator (<< 7)
Preparing to unpack .../170-node-babel7_7.20.15+ds1+~cs214.269.168-3_all.deb
...
Unpacking node-babel7 (7.20.15+ds1+~cs214.269.168-3) over
(7.12.12+~cs150.141.84-6) ...
dpkg: error processin
Package: node-babel7
Version: 7.20.15+ds1+~cs214.269.168-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + node-babel-eslint
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'buster' to 'bullseye' to 'bookworm'.
It installed
Package: node-babel7
Version: 7.20.15+ds1+~cs214.269.168-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + node-babel-eslint
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'buster' to 'bullseye' to 'bookworm'.
It installed
Package: node-stylis
Version: 4.1.3~11.10.7+ds1+~cs8.3.3-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files without declaring a
Breaks+Replaces relation
Package: node-mermaid
Version: 8.14.0+~cs11.4.14-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
node-stylis is now available in a separate package. Please stop shipping
a copy of node-stylis and depend on node-stylis instead.
Andreas
--
Pkg-javascript-devel mailing lis
Package: node-isomorphic-fetch
Version: 3.0.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink:
0m15.8s ERROR: FAIL: Broken symlinks:
/usr/share/nodejs/isomorphic-fetch/fetch-npm-b
Package: node-jschardet
Version: 3.0.0+dfsg+~1.4.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink:
0m15.4s ERROR: FAIL: Broken symlinks:
/usr/share/nodejs/jschardet/buffer -> ../
Package: node-shelljs
Version: 0.8.5+~cs0.8.10-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink:
0m22.0s ERROR: WARN: Broken symlinks:
/usr/bin/shjs -> ../lib/nodejs/shelljs/bin/sh
Package: node-is-docker
Version: 3.0.0-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink:
0m15.6s ERROR: FAIL: Broken symlinks:
/usr/bin/is-docker -> ../lib/nodejs/is-docker/cli.js
Control: tag -1 - moreinfo
On 10/05/2023 17.54, Yadd wrote:
node-source-map depends on libjs-source-map, so the link isn't broken in
normal installation.
After a fresh installation in bookworm, the link is
/usr/share/doc/node-source-map -> libjs-source-map
and everything is fine, but after a
Package: node-asn1.js
Version: 5.4.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
0m40.6s ERROR: FAIL: Broken symlinks:
/usr/share/nodejs/asn1.js-rfc2560 -> asn1.js/rfc/2560 (
Package: node-source-map
Version: 0.7.0++dfsg2+really.0.6.1-13
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
a test with piuparts revealed that your package misses the copyright
file after an upgrade, which is a violation of Policy 12.5:
https://www.debian.org/doc/debi
Package: nodejs
Version: 18.13.0+dfsg1-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
0m19.6s ERROR: FAIL: Broken symlinks:
/usr/lib/x86_64-linux-gnu/node_modules -> nodejs (node
Package: node-core-js
Version: 3.26.1-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
0m15.5s ERROR: FAIL: Broken symlinks:
/usr/share/nodejs/core-js/core-js -> ../packages/core-j
Package: node-source-map
Version: 0.7.0++dfsg2+really.0.6.1-12
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
0m14.8s ERROR: FAIL: Broken symlinks:
/usr/share/nodejs/source-map/di
Source: node-readable-stream
Version: 4.2.0+~cs9.0.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
node-readable-stream/experimental recently started to FTBFS:
dh_auto_build --buildsystem=nodejs
Found debian/nodejs/abort-controller/build
cd ./abort-cont
Source: node-readable-stream
Version: 4.1.0+~cs9.0.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
node-readable-stream/experimental recently started to FTBFS, probably
because some build-dependency became more strict. The version in sid is
not affected.
...
dh
Source: node-fetch
Version: 3.2.10+repack1+~cs14.4.14-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
node-fetch/experimental recently started to FTBFS.
A previous rebuild on Aug. 4 was still successful.
The version in sid is not affected by this bug.
+ rollup -c de
Package: node-schema-utils
Version: 3.1.1~ds-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Control: found -1 4.0.0~ds-1
Hi,
node-schema-utils recently started to FTBFS in sid (but not yet in
testing):
dh_auto_test --buildsystem=nodejs
ln -s ../. node_module
Package: node-sockjs
Version: 0.3.24+~0.3.33-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'bullseye'.
It installed fine in 'bullseye', then the upgrade to 'bookworm' fails
because it tries to o
Package: node-fetch
Version: 3.2.9+~cs18.4.14-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' fails
because
Package: node-jest-debbundle
Version: 28.1.2~ds+~cs70.48.26-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'bullseye'.
It installed fine in 'bullseye', then the upgrade to 'bookworm' fails
becaus
Source: node-parse5
Version: 7.0.0+dfsg-4
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite oth
Source: node-react
Version: 18.1.0~18.2.0+dfsg+~cs87.31.26-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fine in 'sid', then the upgrade to 'experimental' f
Source: node-ajv-keywords
Version: 5.1.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
node-ajv-keywords/experimental recently started to FTBFS after
some (transitive) build-dependency got updated:
debian/rules override_dh_auto_build
make[1]: Entering directory
Package: d3-dsv-tools
Version: 1.1.1-6
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other
Package: yarnpkg
Version: 1.22.19+~cs24.27.18-1
Severity: serious
Tags: ftbfs
Control: affects -1 + src:greenbone-security-assistant
Hi,
greenbone-security-assistant fails to built on most (all?) architectures
except amd64. There seems to be a segmentation fault during a yarnpkg call:
debian/ru
On 11/03/2022 20.14, Yadd wrote:
https://salsa.debian.org/js-team/node-cheerio/-/commit/4232ad8c2e2fa65bfb806fbce25e7f06cd509968
Drop component parse5-htmlparser2-tree-adapter
If the conflicting bits are going to be dropped from node-cheerio,
node-jsdom will need
Breaks+Replaces: node-chee
Package: node-jsdom
Version: 19.0.0+~cs153.23.47-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
Followup-For: Bug #1006205
Control: clone -1 -2
Control: found -2 2.19.0~ds-2
Control: retitle -2 node-blueimp-md5: missing Breaks+Replaces: node-md5-hex (<<
3.0.1+~2.19.0-2~)
Control: reassign -1 node-md5-hex 3.0.1+~2.19.0-1
node-blueimp-md5 was only recently uploaded to the archive.
Therefore n
Package: node-md5-hex
Version: 3.0.1+~2.19.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrit
Package: node-tap-parser
Version: 10.1.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
Prepa
Package: node-babel7
Version: 7.16.6+~cs215.259.185-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages filea.
If node-babel-plugin-add-module-exports is to b
Package: node-superagent,node-fast-safe-stringify
Severity: serious
Tags: sid bookworm .
User: trei...@debian.org
Usertags: edos-file-overwrite
Control: found -1 6.1.0+~2.1.1-1
Control: found -1 2.0.7-2
Hi,
automatic installation tests of packages that share a file and at the
same time do not con
Package: node-string-width,node-slice-ansi
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 4.2.3+~3.0.0+~9.2.2-1
Control: found -1 5.0.0+~4.0.0-2
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other pa
Package: node-clipanion
Version: 2.6.2-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
node-clipanion FTBFS in a minimal chroot:
dh_auto_build --buildsystem=nodejs
Found debian/nodejs/./build
cd ./. && sh -ex debian/nodejs/./build
+ rollup -c
./sources/a
Source: node-liftoff
Version: 3.1.0-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
node-liftoff/experimental recently started to FTBFS with
dh_auto_build --buildsystem=nodejs
No build command found, searching known files
No build command found, searching known fi
Package: node-acorn
Version: 8.5.0+ds+~cs24.17.6-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to overwr
Package: node-mermaid
Version: 8.13.2+ds+~cs30.13.21-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'stable'.
It installed fine in 'stable', then the upgrade to 'sid' fails
because it tries to ov
Followup-For: Bug #969611
node-setimmediate has Suggests: libjs-mocha (>= 3), but that package no
longer exists after stretch.
A possible replacement is the virtual, versioned node-mocha (= 8.2.1)
provided by mocha (8.2.1+ds1+~cs29.4.27-3) which ships
/usr/share/nodejs/mocha/lib/mocha.js
/usr
Package: libjs-bootstrap4
Version: 4.5.2+dfsg1-7
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m13.9s ERROR: FAIL: Broken symlin
Package: node-expect.js
Version: 0.3.1+dfsg+~0.3.29-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
1m1.6s ERROR: FAIL: Broken
Package: libjs-pdf
Version: 2.6.347+dfsg-3
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
/usr/share/doc/libjs-pdf/examples/text-
Package: node-es6-shim
Version: 0.35.6+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m37.9s ERROR: FAIL: Broken symlinks:
Package: node-bunyan
Version: 2.0.5+~cs4.4.2-1
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m40.9s ERROR: FAIL: Broken symlinks:
d packages.
cheers,
Andreas
diff -Nru acorn-8.0.5+ds+~cs19.19.27/debian/changelog
acorn-8.0.5+ds+~cs19.19.27/debian/changelog
--- acorn-8.0.5+ds+~cs19.19.27/debian/changelog 2021-01-26 15:04:47.0
+0100
+++ acorn-8.0.5+ds+~cs19.19.27/debian/changelog 2021-03-30 10:10:08.0
+0200
@@
Package: node-sourcemap-codec
Version: 1.4.8-3
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m27.7s ERROR: FAIL: Broken symlin
Package: node-rollup-pluginutils
Version: 4.1.0+~2.8.2-2
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m32.0s ERROR: FAIL: Bro
Package: node-core-js
Version: 3.8.2-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m29.0s ERROR: FAIL: Broken symlinks:
/u
Package: node-d3-dsv
Version: 1.1.1-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m28.5s ERROR: FAIL: Broken symlinks:
/usr/
Package: node-jsesc
Version: 3.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m28.5s ERROR: FAIL: Broken symlinks:
/usr/b
On 15/03/2021 14.00, Yadd wrote:
Le 15/03/2021 à 13:49, Yadd a écrit :
Le 15/03/2021 à 13:30, Andreas Beckmann a écrit :
Package: chai
Version: 4.2.0+ds+~4.2.14-3
there is already a maintscript for this:
$ cat debian/chai.maintscript
dir_to_symlink /usr/share/doc/chai libjs-chai
Package: chai
Version: 4.2.0+ds+~4.2.14-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
an upgrade test with piuparts revealed that your package installs files
over existing symlinks and possibly overwrites files owned by other
packages. This usually means an old versi
Source: node-ws
Version: 7.4.1+~cs18.0.6-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
node-ws/experimental recently started to FTBFS. An earlier build of the
same version has succeeded, so this new failure is likely due some ch
Source: emscripten
Version: 2.0.9~dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
emscripten/experimental FTBFS with
[...]
PATH="/build/emscripten-2.0.9~dfsg:$PATH"
EM_CACHE="/build/emscripten-2.0.9~dfsg/debian/em_cache" em
Source: node-autoprefixer
Version: 10.0.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
node-autoprefixer/experimental recently started to FTBFS:
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=nodej
Package: mocha,node-postcss
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: found -1 8.2.1+ds1+~cs29.4.27-1
Control: found -1 8.2.1+~cs5.3.23-1
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages file
Followup-For: Bug #976819
Control: retitle -1 node-jest-{debbundle,worker}: missing Breaks+Replaces: jest
(<< 26.6.3+repack)
Control: reassign -1 node-jest-debbundle,node-jest-worker
Control: found -1 26.6.3+repack+~cs61.38.31-1
Preparing to unpack .../node-jest-worker_26.6.3+repack+~cs61.38.31
Package: node-jest-debbundle
Version: 26.6.3+repack+~cs61.38.31-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because i
On 12/8/20 9:44 AM, Xavier wrote:
> what is wrong in "Breaks: jest (<< 2.26.3+repack~), node-jest-debbundle
> (<< 2.26.3+repack~)" ? Jest version in unstable is
> "26.6.3+repack+~cs61.38.31-1"
2.26.3+repack~ (Breaks) << 26.6.3+ds+~cs64.28.30-1 (testing)
The package
Package: node-cosmiconfig
Version: 7.0.0+~cs8.3.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to ove
Package: node-snapdragon
Version: 0.12.0+repack-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package has file conflicts
with some newly introduced packages in sid, which seem to package
some components currently in node-sna
Package: node-snapdragon-util
Version: 5.0.1-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrit
Package: node-snapdragon-node
Version: 3.0.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrit
Source: node-trust-jwa
Version: 0.4.6-1~exp1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
node-trust-jwa started to FTBFS after some changes in the node-babel ecosystem:
debian/rules override_dh_auto_build
make[1]: Entering directory '/build/node-trust-jwa-0.4.6
Source: node-solid-jose
Version: 0.4.0+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
node-solid-jose started to FTBFS after some changes in the node-babel ecosystem:
debian/rules override_dh_auto_build
make[1]: Entering directory '/build/node-solid-jose-0.
Source: node-diff
Version: 4.0.1~dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
node-diff/experimental recently started to FTBFS:
debian/rules binary
dh binary
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_build
make[1]: Ente
Package: jest
Version: 24.9.0+ds-3
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite other pack
Source: acorn
Version:
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-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Hi,
acorn/experimental recently started to FTBFS:
debian/rules build
dh build
dh_update_au
Package: node-sinon
Version: 8.1.0+ds-1
Severity: serious
Control: block 945308 with -1
Hi,
node-command-join has been requested to be removed (#945308), but
node-sinon still (build-)depends on it.
Please find a solution.
Andreas
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alio
Package: node-tslib
Version: 1.10.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + node-rollup-plugin-typescript
Hi,
during a test with piuparts I noticed your package installs files over
an existing symlink shipped or created by another package.
Yo
Source: node-file-entry-cache
Version: 5.0.1+~2.0.1+~2.0.0+~1.0.0+~2.0.1-3
Severity: serious
Hi,
node-file-entry-cache/experimental fails to clean after a successful
build:
debian/rules clean
dh clean
dh_clean
rm: cannot remove './debian/node_modules': Is a directory
dh_clean: rm -f -- debia
Source: node-proxyquire
Version: 2.1.3+~1.0.1+~1.0.2-3
Severity: serious
Hi,
node-proxyquire fails to clean after a successful build:
debian/rules clean
dh clean
dh_clean
rm: cannot remove './debian/node_modules': Is a directory
dh_clean: rm -f -- debian/node-proxyquire.substvars ./debian/no
Followup-For: Bug #934228
Control: found -1 12.8.0~dfsg-2
https://buildd.debian.org/status/fetch.php?pkg=nodejs&arch=all&ver=12.8.0%7Edfsg-2&stamp=1565277544&raw=0
[...]
touch debian/stamp-makefile-check
mkdir -p ./tools/node_modules/eslint/node_modules
ln -sf -t ./tools/node_modules/eslint/node_
Control: reopen -1
This is also reproducible with node-acorn-dynamic-import 4.0.0+really3.0.0-1:
Preparing to unpack
.../node-acorn_6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1_all.deb
...
Unpacking node-acorn
(6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4
Package: node-acorn
Version:
6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fin
Hi Xavier,
is this another unneeded broken symlink? Could you take care of it?
On Sat, 22 Sep 2018 10:50:37 +0530
=?UTF-8?B?c2hpcmlzaCDgpLbgpL/gpLDgpYDgpLc=?= wrote:
> $ adequate node-form-data
> node-form-data: broken-symlink /usr/lib/nodejs/form-data/index.js ->
> form_data.js
>
> On further
Package: node-log4js
Version: 4.0.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m23.9s ERROR: FAIL: Broken symlinks:
/usr/
Package: node-xmlhttprequest
Version: 1.8.0-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m23.7s ERROR: FAIL: Broken symlinks:
Package: node-libnpx
Version: 10.2.0+repack-1
Severity: important
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m27.1s ERROR: FAIL: Broken symlink
Package: libjs-markdown-it-html5-embed
Version: 1.0.0+ds-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m17.6s ERROR: FAIL: Brok
Package: node-cacache
Version: 11.3.2-2
Severity: normal
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m22.3s ERROR: FAIL: Broken symlinks:
/usr
Package: libjs-leaflet.markercluster
Version: 1.4.1~dfsg-5
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks
Hi,
during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is cause
Package: node-gyp
Version: 3.8.0-2
Severity: serious
Hi,
nodejs-dev is no longer built. Please check whether you can use
libnode-dev as a replacement.
Andreas
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/list
Source: node-xmpp
Version: 0.3.2-3
Severity: serious
Hi,
the old transitional package nodejs-dev is no longer built, please
update your build-depends to libnode-dev.
Andreas
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-b
Source: node-nodedbi
Version: 1.0.12-2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Hi,
the old transitional package nodejs-dev is no longer built, please
update your build-depends to libnode-dev.
Andreas
--
Pkg-javascript-devel mailing list
Source: node-evp-bytestokey
Version: 1.0.3-4
Severity: serious
Justification: fails to build from source
Hi,
the old transitional package nodejs-dev is no longer built, please
update your build-depends to libnode-dev.
Andreas
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-li
Package: node-istanbul
Version: 0.4.5+ds-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
1m33.0s ERROR: FAIL: Broken symlinks:
Control: found -1 5.8.0+ds-1
Control: found -1 5.8.0+ds6-3
On Sun, 30 Dec 2018 18:57:42 +0100 Ralf Jung wrote:
> In any case it seems like npm updates don't properly upgrade/remove the file
> in
> /etc, because I had an up-to-date npm and still had those lines in there (and
> I
> never locally
Source: leaflet
Version: 1.0.3~dfsg-2
Severity: serious
Hi,
leaflet fails to build twice in a row because cleaning afte rthe first
build errors out:
debian/rules clean
dh clean
dh_clean
rm: cannot remove './debian/js': Is a directory
dh_clean: rm -f -- debian/libjs-leaflet.substvars ./debian
Package: node-acorn
Version:
6.0.2+20181021git007b08d01eff070+ds+~0.3.1+~4.0.0+~0.3.0+~5.0.0+ds+~1.6.1+ds-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'sid' to 'experimental'.
It installed fin
Package: node-combined-stream
Version: 1.0.6-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m35.7s ERROR: FAIL: Broken symlinks
Package: libnode64-dev
Version: 10.4.0~dfsg-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package ships (or creates)
a broken symlink.
>From the attached log (scroll to the bottom...):
0m32.4s ERROR: FAIL: Broken symlinks:
Followup-For: Bug #898024
Control: found -1 10.3.0~dfsg-1
Control: severity -1 serious
The 8 -> 10 upgrade path does not work either:
Selecting previously unselected package libnode64-dev.
Preparing to unpack .../libnode64-dev_10.3.0~dfsg-1_amd64.deb ...
Unpacking libnode64-dev (10.3.0~dfsg
97 matches
Mail list logo
