Control: tag -1 pending
Hello,
Bug #1071382 in nodejs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: node-babel7
Version: 7.20.15+ds1+~cs214.269.168-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source
This package FTBFS When rebuilding it in bookworm, against
nodejs 18.19.0+dfsg-6~deb12u1
node-undici 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4
(not yet uploaded)
The way
Source: node-zx
Version: 7.1.1+~cs6.7.23-3
Followup-For: Bug #1068918
Control: tags -1 ftbfs
Failure:
make[1]: Leaving directory '/<>'
dh_auto_test --buildsystem=nodejs
ln -s ../. node_modules/zx
/bin/sh -ex debian/tests/pkg-js/test
+ uvu -b -i extra.test.js|package.test.js test
Package: node-v8-compile-cache
Version: 2.4.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Even when built with node-undici 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u4,
this package fails to build with:
not ok 2 - test/NativeCompileCache-test.js # time=149.066ms
---
env:
Source: node-zx
Version: 7.1.1+~cs6.7.23-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source
This package FTBFS in bookworm, even when using node-undici with fixed types.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500,
Source: tpm2-tss
Followup-For: Bug #1067418
Upstream will just skip those tests on 32-bit:
https://github.com/tpm2-software/tpm2-tss/commit/932b1e78047ed0ddc09fcb06bff2e7cf96406976
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Le mer. 20 mars 2024 à 22:14, Lucas Nussbaum a écrit :
> Source: node-ajv
> Version: 8.12.0~ds+~2.1.1-4
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20240319 ftbfs-trixie
>
> Hi,
>
> During a rebuild of all packages in sid, your
Emmanuel,
Le dim. 17 mars 2024 à 04:39, Peter Michael Green a
écrit :
> Package: python-cryptography
> Version: 41.0.7-5
> Severity: serious
> x-debbugs-cc: eam...@debian.org, kapo...@melix.org
>
>
> python-cryptography build-depends on python3-cryptography-vectors (<<
> 41.0.8~)
> but
Le ven. 15 mars 2024 à 11:17, Jérémy Lal a écrit :
>
>
> Le ven. 15 mars 2024 à 08:46, Jochen Sprickerhof a
> écrit :
>
>> Hi Andreas,
>>
>> * Andreas Tille [2024-03-15 07:31]:
>> >Hi,
>> >
>> >thanks to the next round of Lucas' FT
Le ven. 15 mars 2024 à 08:46, Jochen Sprickerhof a
écrit :
> Hi Andreas,
>
> * Andreas Tille [2024-03-15 07:31]:
> >Hi,
> >
> >thanks to the next round of Lucas' FTBFS QA rebuilds (at least) one
> >package of the R pkg team is affected by some strange linker issue
> >
> >#1066409 r-cran-v8:
Source: ipywidgets
Version: 8.1.1-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Rebuilding
https://deb.debian.org/debian/pool/main/i/ipywidgets/ipywidgets_8.1.1-4.dsc
in a clean sid chroot fails with
error: aborting due to unexpected upstream changes
-- System
Control: tag -1 pending
Hello,
Bug #1065510 in nodejs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Le dim. 3 mars 2024 à 07:57, Yadd a écrit :
> On 2/24/24 13:10, Sebastian Ramacher wrote:
> > Source: node-leveldown
> > Version: 5.6.0+dfsg-4
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source (but built successfully in the
> past)
> > X-Debbugs-Cc:
Le ven. 9 févr. 2024 à 14:33, Dylan Aïssi a écrit :
> Source: node-undici
> Version: 5.15.0+dfsg1+~cs20.10.9.3-1+deb12u3
> Severity: serious
> Tags: bookworm
> Usertags: apertis-ftbfs
> Justification: FTBFS
>
> Hello,
>
> While doing a rebuild of some node packages in Bookworm, it appears
Source: azure-cosmos-table-python
Followup-For: Bug #1061440
This package is deprecated, in favor of the python3-azure debian package.
Please don't fix this bug, and let's get this eventually autoremoved.
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy:
Control: tag -1 pending
Hello,
Bug #1063365 in python-cryptography reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Source: celery
Followup-For: Bug #1058317
Note the segmentation fault at the end of python 3.12 pytest run.
Using export PYTHONFAULTHANDLER=1 before running the tests, I only got
an error in garbage-collector, no trace.
It is a bit like #1055717, which was closed by
I've reassigned it to solo1-cli,
because I thought it wasn't a library (and the start of the docs lead me to
it), but actually it is a library.
My mistake, re-reassigning to django_solo, the newcomer has to go elsewhere.
Package: vitrage
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Version 11 of vitrage depends on a package that I just uploaded to debian,
which is great !
But vitrage still needs to depend on it :)
Jérémy
-- System Information:
Le sam. 23 déc. 2023 à 20:15, Jonas Smedegaard a écrit :
> Quoting Pirate Praveen (2023-12-22 20:53:46)
> > On Sun, 29 Oct 2023 21:37:08 +0100 Jonas Smedegaard wrote:
> > > Yes, I still want to work on node-jsonld - I will make time to look at
> > > this soon...
> >
> > yarnpkg 4.0.2 was
Le jeu. 21 déc. 2023 à 08:59, Paul Gevers a écrit :
> Hi,
>
> On 20-12-2023 23:08, Jérémy Lal wrote:
> > I did the one for burp.
>
> Thanks for that.
>
> > Dolfin has active maintainers, though.
>
> I think I need to file a "flaky autopkgtest" bu
Le mer. 20 déc. 2023 à 22:33, Mark Brown a écrit :
> On Wed, Dec 20, 2023 at 10:14:44PM +0100, Jérémy Lal wrote:
>
> > BURP wrong zlib version check in the failing test - this could be NMUed
>
> > DOLFIN has a single test failure, that is odd and unrelated as well -
>
Le mer. 20 déc. 2023 à 21:18, Mark Brown a écrit :
> clone 1059165 -1
> reassign -1 nodejs
> retitle -1 autopkgtest failures on i386
> found -1 18.19.0+dfsg-6
> block 1059165 by -1
> kthxbye
>
> On Wed, Dec 20, 2023 at 08:15:31PM +0100, Paul Gevers wrote:
>
> > The Release Team considers
Le mer. 30 août 2023 à 12:18, Jan Mojzis a écrit :
> Hi,
> I've uploaded experimental version with the PCRE2 patch included
> 1:0.10.25-2~exp1 to the experimental.
Cool !
It seems three modules need to be patched:
https://github.com/swananan/lua-resty-core/tree/support_pcre2
Le mar. 29 août 2023 à 15:43, Thomas Ward a écrit :
> I apoligize I was thinking Lua deps not PCRE.
>
> However, I did more digging. OpenResty has been on NGINX cofe version
> 1.21.4 for the longest time. They do not have PCRE2 support in their
> system. As this is an OpenResty-originating
Le lun. 21 août 2023 à 19:09, Thomas Ward a écrit :
> Bastian:
>
> As I understand the module, for over a year now the latest Lua module
> from OpenResty requires LuaJIT to actually compile. See
>
> https://salsa.debian.org/nginx-team/libnginx-mod-http-lua/-/blob/main/debian/control#L8
> where
Le jeu. 9 mars 2023 à 15:00, Piotr Jurkiewicz <
piotr.jerzy.jurkiew...@gmail.com> a écrit :
> On Wed, 8 Mar 2023 19:05:39 +0100 Jan Mojzis wrote:
> > Hello,
> > can You please send me the steps how i can reproduce it
> > - packages list/versions before the upgrade
> > - exact apt/apt-get command
Le mer. 1 mars 2023 à 14:39, James Addison a écrit :
> If reproducible: would this bug be a good candidate for upload of a
> fix to 'experimental' so that it can be alpha-tested by others?
>
Sure.
For now I'm unlucky with the porterbox, because /var/run/schroot
disappeared yesterday.
Notified
Le mer. 1 mars 2023 à 02:30, Thorsten Glaser a écrit :
> Jérémy Lal dixit:
>
> >I can build nodejs on amhdal.debian.org if you're not comfortable with
> that.
>
> The problem with the DSA porterboxen is that you cannot install your own
> built packages in the chroot t
Le mar. 28 févr. 2023 à 19:06, James Addison a écrit :
> On Tue, Feb 28, 2023, 17:55 Thorsten Glaser wrote:
>
>> Can you test it? I don’t have the bandwidth for that right now…
>
>
> Should be able to, yep - I seem to remember seeing some repro instructions
> from you on the GitHub thread and
Le mar. 28 févr. 2023 à 00:33, James Addison a écrit :
> Package: nodejs
> Followup-For: Bug #1030284
> X-Debbugs-Cc: t...@debian.org,
> reply+aagshfqluldiwi3obwdg6lgb7if7fevbnhheauz...@reply.github.com
>
> mirabilos gesagt:
>
> > We know the default ulimits for users in Debian, and they are
Le mer. 15 févr. 2023 à 14:39, Thorsten Glaser a écrit :
> Hi James,
>
> (you might wish to Cc <${bugnumber}-submit...@bugs.debian.org> so they
> actually get the reply…)
>
> >Are you able to determine whether
> https://github.com/nodejs/node/issues/41163
> >(and/or any of the guidance within
Control: tag -1 pending
Hello,
Bug #1023039 in python-xmlsec reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Source: python-xmlsec
Version: 1.3.12-1
Followup-For: Bug #1023039
The test failure in dynamic signature actually comes from libxmlsec1.
It is expected: there's even a patch in libxmlsec1 that skips those tests.
I suggest to just do the same in python-xmlsec (skip those two failing tests).
Package: pdfarranger
Followup-For: Bug #1020639
Hi,
i've prepared and pushed an update to salsa.
I can upload it, if no one is planning to do it.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'testing')
Architecture: amd64
Control: tag -1 pending
Hello,
Bug #1020980 in nodejs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Le ven. 23 sept. 2022 à 23:21, Jérémy Lal a écrit :
>
>
> Le ven. 23 sept. 2022 à 23:03, Sebastian Andrzej Siewior <
> sebast...@breakpoint.cc> a écrit :
>
>> control: found -1 odejs/18.7.0+dfsg-5
>>
>> On 2022-09-23 22:55:23 [+0200], Jérémy Lal wrote:
>
Le ven. 23 sept. 2022 à 23:03, Sebastian Andrzej Siewior <
sebast...@breakpoint.cc> a écrit :
> control: found -1 odejs/18.7.0+dfsg-5
>
> On 2022-09-23 22:55:23 [+0200], Jérémy Lal wrote:
> > Thanks, I'm already aware of the need to run nodejs testsuite using
> > the
Le ven. 23 sept. 2022 à 22:51, Sebastian Andrzej Siewior <
sebast...@breakpoint.cc> a écrit :
> Package: nodejs
> Version: 8.7.0+dfsg-5
> Severity: serious
> control: tags -1 patch
>
> The last OpenSSL upload moved the default security level from the
> openssl.cnf file to build-time default so I
Package: dwz
Version: 0.14-1
Followup-For: Bug #1016936
It also fails for nodejs (gcc 11 on mips64el):
https://buildd.debian.org/status/fetch.php?pkg=nodejs=mips64el=18.8.0%2Bdfsg-1=1662286086=0
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500,
Le sam. 20 août 2022 à 08:18, Paul Gevers a écrit :
> Hi Jérémy,
>
> On 19-08-2022 23:15, Jérémy Lal wrote:
> > Some recent small changes in libuv had unexpected outcomes,
> > I suppose upstream siridb should be made aware of it.
>
> Which is what this bug is abou
Hi folks,
Some recent small changes in libuv had unexpected outcomes,
I suppose upstream siridb should be made aware of it.
Le ven. 19 août 2022 à 22:42, Paul Gevers a écrit :
> Hi Jeroen,
>
> On 19-08-2022 21:39, Paul Gevers wrote:
> > With a recent upload of libuv1 the autopkgtest of
Source: postgresql-set-user
Version: 3.0.0-2
Severity: serious
Justification: Policy 5.6.13
Hi,
your package is missing a description.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'testing')
Architecture: amd64 (x86_64)
Le dim. 31 juil. 2022 à 16:27, Dominique Dumont a
écrit :
> On Saturday, 30 July 2022 19:36:26 CEST you wrote:
> > libuv1 is a library, you're supposed to manage the transition:
> > https://wiki.debian.org/Teams/ReleaseTeam/Transitions
>
> This page applies when the new version breaks the ABI or
Le sam. 30 juil. 2022 à 19:24, Dominique Dumont a
écrit :
> On Saturday, 30 July 2022 17:25:29 CEST you wrote:
> > libuv1 maintainer: please avoid uploading new versions when nodejs is
> > in transition...
>
> I package libuv1 because it's a dependency of moarvm.
>
> I don't follow nodejs
Source: nodejs
Version: 18.6.0+dfsg-3
Followup-For: Bug #1016305
X-Debbugs-Cc: lib...@packages.debian.org
The two actually failing tests are:
parallel/test-socket-write-after-fin-error
parallel/test-tls-streamwrap-buffersize
Those failures are regressions caused by recent upload of libuv1
Le ven. 29 juil. 2022 à 20:27, Lucas Nussbaum a écrit :
> Source: nodejs
> Version: 18.6.0+dfsg-3
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220728 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your
Source: olm
Version: 3.2.11~dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
nodejs 18 exposes `global.fetch` API which makes some code
believe it is sitting in a real browser.
olm test fails because of that.
A workaround is
Source: node-canvas-confetti
Version: 1.5.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
In debian/unstable,
Here's the log
dh binary
dh_update_autotools_config
dh_autoreconf
dh_auto_configure --buildsystem=nodejs
dh_auto_build --buildsystem=nodejs
Found
close 1015051 0.1+20220404git9ecf45e-2
thanks
python3-six was missing from Depends
Control: tag -1 pending
Hello,
Bug #1014214 in nodejs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Source: node-react-highlighter
Version: 0.4.3+repack1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Seen while rebuilding with node 18.4.0.
However it is probably caused by recent changes in webpack.
-- System Information:
Debian Release: bookworm/sid
APT prefers
Source: node-blob
Version: 0.0.4-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source
node >= 18 exports Blob already,
making node-blob fail.
I suggest node-blob should be removed,
it is a leaf package without reverse build-deps.
-- System Information:
Debian Release:
Source: golang-github-evanw-esbuild
Version: 0.14.43-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Happened when doing a nodejs 18.4.0 migration check.
However it doesn't look like it is related to node at all.
See attached log.
Source: r-cran-v8
Version: 4.2.0+dfsg-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
When building r-cran-v8 against nodejs 18.4.0 in experimental,
this happened:
# Fatal error in , line 0
# Embedder-vs-V8 build configuration
Control: tag -1 pending
Hello,
Bug #1011784 in node-cacache reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Le mar. 17 mai 2022 à 12:00, Adam Borowski a écrit :
> Source: iotjs
> Version: 1.0+715-1
> Severity: serious
> Justification: In the opinion of a QA person the package is unsuitable for
> release.
>
> Hi!
> This package appears to be unmaintained, and:
> * has a large set of CVEs reported.
Package: nodejs
Version: 16.14.2+dfsg1-1+b1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Last time so many openssl-related test failures happened,
OPENSSL_CONF env was set to a relative path, and nodejs/openssl3
expected an absolute
Le lun. 16 mai 2022 à 22:09, Adrian Bunk a écrit :
> Package: webpack
> Version: 4.43.0-7
> Severity: serious
> Tags: ftbfs
> Control: affects -1 src:macaulay2
>
> https://buildd.debian.org/status/logs.php?pkg=macaulay2=all
>
> ...
> > build
> > webpack
>
> node:internal/crypto/hash:67
>
Forwarded: https://github.com/Keruspe/GPaste/issues/398
(but probably the bts will ignore this, I happen to never find the right
doc about it)
Le jeu. 12 mai 2022 à 19:33, Thorsten Alteholz a
écrit :
> Package: gpaste
> Severity: serious
> User: alteh...@debian.org
> Usertags: ftp
> thanks
>
>
Hi,
Le jeu. 5 mai 2022 à 11:12, Bo YU a écrit :
>
> ```
>
> Error: Unrecognized type: 'string\[]'.
> Please, edit the type or update
'file:///<>/debian/doc-generator/type-parser.mjs'.
> at file:///<>/debian/doc-generator/type-parser.mjs:297:15
> ```
That's the documentation generator,
Control: tag -1 pending
Hello,
Bug #1010509 in nodejs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: nodejs
Version: 16.14.2+dfsg-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
I'll disable the test for now.
The failure:
not ok 2933 sequential/test-cpu-prof-worker-argv
---
duration_ms: 2.317
severity: fail
Control: tag -1 pending
Hello,
Bug #1010069 in nodejs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Le sam. 23 avr. 2022 à 17:18, Jérémy Lal a écrit :
> Package: nodejs
> Version: 16.13.2+really14.19.1~dfsg-6
> Severity: serious
> Tags: ftbfs
> Justification: fails to build from source (but built successfully in the
> past)
>
>
> https://buildd.debian.org/status/
Source: golang-github-evanw-esbuild
Version: 0.14.25-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
your package FTBFS, however a trivial upstream update fixes it (took me a
minute to rebuild it).
Jérémy.
-- System
Package: nodejs
Version: 16.13.2+really14.19.1~dfsg-6
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
https://buildd.debian.org/status/fetch.php?pkg=nodejs=mipsel=16.13.2%2Breally14.19.1~dfsg-6%2Bb1=1650719824=log
...
not ok 185
Control: tag -1 pending
Hello,
Bug #1007858 in node-lodash reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
On Wed, Apr 6, 2022 at 6:30 PM Jonas Smedegaard wrote:
> Quoting Yadd (2022-04-06 18:12:30)
> > On 19/03/2022 08:38, Yadd wrote:
> > > On 19/03/2022 08:11, Yadd wrote:
> > >> On 17/03/2022 19:21, Jérémy Lal wrote:
> > >>> Source: node-lodash
> &g
Control: tag -1 pending
Hello,
Bug #1007858 in node-lodash reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1007858 in node-lodash reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #1007858 in node-lodash reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Package: node-p-locate
Version: 6.0.0-8
Severity: serious
Justification: autopkgtest regressions
Hi,
this is the cause of several regressions.
-- System Information:
Debian Release: bookworm/sid
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'unstable'), (101,
On Fri, Apr 1, 2022 at 10:42 AM Jérémy Lal wrote:
> Source: node-expat
> Version: 2.4.0+ds-1
> Severity: normal
>
> Hi,
>
> while your package's autopkgtests pass, there is an odd failure:
>
> https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-expa
Control: tag -1 pending
Hello,
Bug #1007248 in nodejs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
On Thu, Mar 24, 2022 at 11:15 PM Daniel Leidert wrote:
> reopen 1007248
> thanks
>
> I just got hit by this bug as well:
>
> Entpacken von nodejs (16.13.2+really14.19.1~dfsg-5) über (12.22.9~dfsg-1)
> ...
> dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-DvPfq0/442-
>
On Tue, Mar 22, 2022 at 5:42 PM Yadd wrote:
> Package: nodejs
> Version: 16.13.2+really14.19.1~dfsg-4
> Severity: serious
> Tags: ftbfs
> Justification: FTBFS
>
> nodejs 14 installs @types/node files except package.json. This render
> typescript declaration unusable and blocks typescript builds.
Source: node-modern-syslog
Version: 1.2.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
The test run during build is failing.
Since node-tap 15, test coverage is on by default, and fails when < 100%.
-- System Information:
Debian
On Mon, Mar 21, 2022 at 4:27 PM PaulLiu wrote:
> > Question: is this package useful ? No reverse dependencies in Debian, no
> > new version for 2 years even if there are 116 open bugs, low and
> > decreasing weekly downloads
>
> Hi Yadd,
>
> This package is used by me for a personal project.
On Mon, Mar 21, 2022 at 10:54 AM Yadd wrote:
> Control: tags -1 + moreinfo
>
> On 21/03/2022 09:02, Jérémy Lal wrote:
> > Source: sax.js
> > Version: 1.2.4+~1.2.4-1
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from sour
Source: sax.js
Version: 1.2.4+~1.2.4-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
This happened during rebuild of this package:
dh_nodejs_substvars
No such file or directory at /usr/bin/dh_nodejs_substvars line 21.
make: *** [debian/rules:8: binary] Error 2
On Sat, Mar 19, 2022 at 10:37 PM Rebecca N. Palmer
wrote:
>
> Control: reassign -1 python3-nbclient, src:theano
> Control: tags -1 patch
>
> This looks like a missing dependency on python3-ipython-genutils, though
> I haven't actually tested adding that. (That package was installed when
>
On Fri, Mar 18, 2022 at 1:21 PM Yadd wrote:
> On 18/03/2022 09:38, Jérémy Lal wrote:
> > Package: node-inquirer
> > Version: 8.2.0+~cs26.5.5-1
> > Severity: serious
> > Tags: ftbfs
> > Justification: fails to build from source
> >
> > Found d
On Fri, Mar 18, 2022 at 7:09 AM Yadd wrote:
> On 17/03/2022 19:02, Jérémy Lal wrote:
> > Source: node-nodedbi
> > Version: 1.0.14-2
> > Severity: important
> > Tags: ftbfs
> >
> > This package fails to rebuild. Build log is attached.
>
> There was a
Source: node-jest
Version: 27.5.1~ds+~cs69.51.22-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
No build command found, searching known files
Found debian/nodejs/bcoe-v8-coverage/build
cd ./bcoe-v8-coverage && sh -ex
Package: node-inquirer
Version: 8.2.0+~cs26.5.5-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
Found debian/nodejs/additional_components
Adding component(s): packages/checkbox, packages/confirm, packages/core,
packages/editor, packages/expand, packages/input,
Package: node-got
Version: 11.8.3+~cs58.7.37-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
No build command found, searching known files
Found debian/nodejs/normalize-url/build
cd ./normalize-url && sh -ex ../debian/nodejs/normalize-url/build
+ babeljs
Source: theano
Version: 1.0.5+dfsg-4
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
cp
/var/lib/nspawn-runner/.build/js-team/nodejs/debian/output/theano-1.0.5+dfsg/doc/library/d3viz/index.ipynb
jupyter_tmp && jupyter-nbconvert --to
Source: python-xarray
Version: 2022.03.0-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
It fails in a clean sid chroot with:
Could not import extension nbsphinx (exception: No module named
'ipython_genutils')
Jérémy
Control: tag -1 pending
Hello,
Bug #1007248 in nodejs reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Le lun. 18 oct. 2021 à 22:12, Jérémy Lal a écrit :
> Le lun. 18 oct. 2021 à 16:48, Oliver Schode a
> écrit :
>
> > Package: luarocks
> > Version: 3.7.0+dfsg1-1
> > Severity: grave
> > Justification: renders package unusable
> >
> > Hi,
> >
&
Le lun. 18 oct. 2021 à 16:48, Oliver Schode a
écrit :
> Package: luarocks
> Version: 3.7.0+dfsg1-1
> Severity: grave
> Justification: renders package unusable
>
> Hi,
>
> thanks for reviving the package. Now I'm getting this when attempting to
> install however:
>
> Error: Cannot access
Le dim. 17 oct. 2021 à 15:39, Simon McVittie a écrit :
> Package: gpaste
> Version: 3.42.0-2
> Severity: grave
> Justification: renders package unusable
> Control: found -1 3.42.0-1
> Control: block 996607 by -1
>
> gpaste/3.42.0-1 and gpaste/3.42.0-2 have:
>
> > Depends: ..., gnome-shell (>=
Le dim. 19 sept. 2021 à 22:33, Bastien Roucariès <
roucaries.bast...@gmail.com> a écrit :
> Source: nodejs
> Severity: serious
> Tags: patch
> Justification: base arch
> Forwarded:
> https://chromium.googlesource.com/v8/v8.git/+/e825c4318eb2065ffdf9044aa6a5278635c36427
>
> Dear Maintainer,
>
>
Le dim. 19 sept. 2021 à 22:27, Bastien ROUCARIES <
roucaries.bast...@gmail.com> a écrit :
> Le dim. 19 sept. 2021 à 19:33, Jérémy Lal a écrit :
> >
> >
> >
> > Le dim. 19 sept. 2021 à 18:54, Bastien Roucariès <
> roucaries.bast...@gmail.com> a écri
Le dim. 19 sept. 2021 à 18:54, Bastien Roucariès <
roucaries.bast...@gmail.com> 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
node-stringprep is totally abandoned. It would be so great to drop that
package.
Le ven. 27 août 2021 à 12:27, Jeremy Bicha a écrit :
> Package: gnome-shell-extension-gpaste
> Version: 3.40.2-1
> Severity: serious
> Control: block -1 by 992870
>
> Sorry, I don't think I was clear with https://bugs.debian.org/993064
>
> I believe gnome-shell-extension-gpaste 3.40 is not
Package: node-websocket-driver
Version: 0.3.5-1.1
Severity: serious
Justification: Policy 2.2.1
This package does have a test suite, however its test runner
is not available in debian (jstest).
However, i installed jstest manually, patched it to avoid trivial
errors in jstest itself, and was
Le ven. 9 juil. 2021 à 22:57, Yadd a écrit :
>
>
> Le 9 juillet 2021 19:32:21 GMT+02:00, "Jérémy Lal" a
> écrit :
> >Le ven. 9 juil. 2021 à 15:39, Gianfranco Costamagna <
> >locutusofb...@debian.org> a écrit :
> >
> >> Source: node-
1 - 100 of 377 matches
Mail list logo