Source: remmina
Version: 1.2.31.2+dfsg-1~bpo9+1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The remmina backport package fails because of a libssh-4 dependency problem,
even if the backport version of this library is installed.
$ sudo apt install -t stretch-backport
Thanks!
Hi all,
looking at CPAN reports [1], no bug found by CPAN testers even on Gregor
machine [2] ;-) (except on Windows, which is a known problem).
I'll take a look to recent SSL problems (and Net::SMTP dependencies) to
try to understand.
Cheers,
Xavier
[1] http://matrix.cpantesters.org/?dis
Le 15/09/2018 à 17:42, Damyan Ivanov a écrit :
> -=| gregor herrmann, 14.09.2018 16:08:50 +0200 |=-
>> Control: tag -1 + unreproducible
>>
>> On Fri, 14 Sep 2018 16:52:38 +0300, Adrian Bunk wrote:
>>
>>> Source: libnet-server-mail-perl
>>> Version: 0.25-1
>>> Severity: serious
>>> Tags: ftbfs
>>>
>
After some tests on Santiago VM, it looks like feersum build well in
stretch but fails randomly (>90%) with testing/unstable
I'll take a look at Plack::App::Cascade and EV changes.
Le 29/09/2018 à 14:56, Xavier a écrit :
> After some tests on Santiago VM, it looks like feersum build well in
> stretch but fails randomly (>90%) with testing/unstable
>
> I'll take a look at Plack::App::Cascade and EV changes.
Bug is around HTTP::Request, either it doesn&
Le 29/09/2018 à 16:41, Xavier a écrit :
> Le 29/09/2018 à 14:56, Xavier a écrit :
>> After some tests on Santiago VM, it looks like feersum build well in
>> stretch but fails randomly (>90%) with testing/unstable
>>
>> I'll take a look at Plack::App::Cascade and
Le 29/09/2018 à 17:59, Santiago Vila a écrit :
> On Sat, Sep 29, 2018 at 05:40:54PM +0200, Xavier wrote:
>
>> The error is 'Connection reset by peer', so LWP can't follow
>> redirection. Is there a special network configuration in your VMs ?
>
> Well, t
Hi,
even on a very slow machine with some parallel schroot builds, I'm
unable to reproduce this FTBFS failure. Maybe related to LXC
infrastructure. I'll test later.
Cheers,
Xavier
Control: forwarded -1 https://github.com/andrewrk/node-yawl/issues/5
Control: tags -1 + upstream confirmed
Upstream tests fail even using a fresh "npm install".
https://salsa.debian.org/js-team/node-lodash/blob/master/.travis.yml
shows the way to build lodash-packages from lodash :
$ yarn
$ git clone --depth=10 --branch=master
git://github.com/lodash/lodash-cli ./node_modules/lodash-cli
$ mkdir -p ./node_modules/lodash-cli/node_modules/lodash
$ cd $_
$ cp
#894962 was probably partially due to #909151.
Thanks to Mauricio Oliveira to have fixed #909151.
https://bugs.debian.org/894962
FTBFS and Debci failure with node-process-nextick-args 2.0.0-1
https://bugs.debian.org/909151
'Uncaught TypeError: nextTick is not a function' with
node-process-ne
#894962 was probably partially due to #909151.
Thanks to Mauricio Oliveira to have fixed #909151.
https://bugs.debian.org/894962
FTBFS and Debci failure with node-process-nextick-args 2.0.0-1
https://bugs.debian.org/909151
'Uncaught TypeError: nextTick is not a function' with
node-process-ne
Le 27/02/2019 à 13:40, Xavier a écrit :
> Le 27/02/2019 à 08:47, Andreas Tille a écrit :
>> Hi Utkarsh,
>>
>> I realised that you intend to take over this package but for a reason I
>> do not understand myself it does not migrate to testing (see testing
>
ocked). There is no reverse dependency to ejs.js (the
only one requires node-ejs >= 2.5.2 while ejs.js is 1.0.0 due to old
GitHub repo, so points to src:node-ejs). libjs-ejs isn't used by any
package.
Cheers,
Xavier
Le 27/02/2019 à 15:35, Gianfranco Costamagna a écrit :
> reopen 923223
> affects 923223 src:xmltv
> severity 923223 serious
> thanks
>
> Hello, the latest update of libxml-parser-perl seems to have broken xmltv
> testsuite, and now it is failing to build from source.
>
> I suspect the testsuite
r providing a better patch for XML::Parser.)
Patch is ready in salsa repo:
if (ref $file or $file eq '-') {
open(FILE, $file) or croak "Couldn't open $file:\n$!";
} else {
open(FILE, '<', $file) or croak "Couldn't open $file:\n$!";
}
Successfully tested with xmltv. I propose to push as this for now to
close bug before freeze. This patch fixes security bug since strange
filename are no more interpreted and autopkgtest regression is fixed.
Cheers,
Xavier
On 16/02/2017 23:52, gregor herrmann wrote:
> On Mon, 13 Feb 2017 20:23:55 +0100, Xavier wrote:
>
>>> Pushed to git, waiting with an upload for a test/sanity check of you
>>> guys.
>> Oups, thank you very much ! Works fine now
>
> Thanks for checking, and s
calhost' );
http://matrix.cpantesters.org/?dist=Net-Server-Mail+0.26 also shows that
this rarely happens since the release of 5.28.0 (1/22), never before.
I added a workaround for now in libnet-server-mail-perl tests (warn and
return when $s is undefined).
Cheers,
Xavier
Control: reassign -1 node-send
Build error is in node-send (index.js line 693)
Problem found: node-send depends on node-mime 1.6 while unstable has
node-mime 2.3.1-1 (with breaking changes)
Probably same issue for #902507
Le 10/01/2019 à 19:41, Xavier a écrit :
>> ...
>> That does actually look like a bug in the new uglifyfs.
>>
>> cu
>> Adrian
>
> I tried to reproduce but have different errors related to debian/examples* :
debian/control should require node-pend (>= 1.2.0)
Le 10/01/2019 à 19:34, Adrian Bunk a écrit :
> Control: reassign -1 uglifyjs 3.4.9-2
> Control: retitle -1 uglifyjs: Error: Cannot find module '../tools/exit'
> Control: affects -1 src:node-browserify-lite
>
> On Thu, Jan 10, 2019 at 08:04:46PM +0200, Adrian Bunk wrote:
>> Source: node-browserify-
Control: tags -1 + moreinfo
Hello,
I'm unable to reproduce this bug and
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/node-livescript.html
seems clean at least since 2019-01-07
Cheers,
Xavier
Update to 11.3.2 fixes partially failing build. Last problem is in
node-readable-stream
Control: reopen -1
Control: severity -1 important
Control: tags -1 - ftbfs
Control: retitle -1 node-duplexer3: incompatible with Node >=10 stream
Even using `npm install` files, the failing test shows that duplexer3
isn't compatible with Node.js stream.
Tagged as "important" instead of "serious"
Le 19/01/2019 à 14:44, Adrian Bunk a écrit :
> Source: libdbd-sqlite3-perl
> Version: 1.62-1
> Severity: serious
> Tags: ftbfs
>
> https://buildd.debian.org/status/fetch.php?pkg=libdbd-sqlite3-perl&arch=mips&ver=1.62-1&stamp=1546291045&raw=0
>
> ...
> t/65_db_config.t
Le 19/01/2019 à 20:16, gregor herrmann a écrit :
> On Sat, 19 Jan 2019 15:03:24 +0100, Xavier wrote:
>
>>> https://buildd.debian.org/status/fetch.php?pkg=libdbd-sqlite3-perl&arch=mips&ver=1.62-1&stamp=1546291045&raw=0
>>>
>>> ...
>>> t/65
Control: severity -1 important
According to debci reports, this FTBFS seems fixed. I'm going to upload
a new version since license is wrong (upstream has changed to ISC, not
reported in debian/changelog)
An update of node-union-value fixes the problem. Let's do it
Hello,
Debian bug is tagged as "patch", but I didn't find any patch in the
related documents. Can you give me the link to patch ?
Cheers,
Xavier
Le 22/01/2019 à 21:18, Salvatore Bonaccorso a écrit :
> Source: apache2
> Version: 2.4.37-1
> Severity: grave
> Tags: patc
node-temporary seems orphaned upstream, looking at apt-cache depends, it
seems that no package needs it, so I think it can be safely removed from
testing.
Le 23/01/2019 à 09:33, Xavier a écrit :
> node-temporary seems orphaned upstream, looking at apt-cache depends, it
> seems that no package needs it, so I think it can be safely removed from
> testing.
However I fixed this package.
node-temporary in memoriam...
Anyway, keeping this package in buster seems not a security problem:
very simple wrapper around node.fs()
Message transféré
Subject : Re: [vesln/temporary] Tests fail (#28)
Date : Wed, 23 Jan 2019 08:57:32 -0800
>From : Will
To :
Le 23/01/2019 à 20:57, Salvatore Bonaccorso a écrit :
> Control: tags -1 + fixed-upstream
> Control: tags -1 - patch
>
> Hi Xavier,
>
> On Wed, Jan 23, 2019 at 09:18:36AM +0100, Xavier wrote:
>> Hello,
>>
>> Debian bug is tagged as "patch", but I did
Le 23/01/2019 à 21:50, Salvatore Bonaccorso a écrit :
> Hi Xavier,
>
> On Wed, Jan 23, 2019 at 09:46:44PM +0100, Xavier wrote:
>> Le 23/01/2019 à 20:57, Salvatore Bonaccorso a écrit :
>>> Control: tags -1 + fixed-upstream
>>> Control: tags -1 - patch
>>
Hi all,
to fix missing popper.js, I propose to embed it for now in
twitter-bootstrap4 (done in salsa repo but not pushed). After buster
release, we could split it in a separate package.
Please review this.
Cheers,
Xavier
Le 25/01/2019 à 17:39, Santiago Vila a écrit :
> found 886664 1.0.7-4
> thanks
>
>>[ Xavier Guimard ]
>>* Remove timeout based tests (Closes: #886664)
>
> Hi. Sorry for the reopening but this does not seem fixed:
>
> https://tests.reproducible-builds
moved from buster with
all its reverse dependencies
- package many new modules (I've no time to do this)
- decrease this severity issue
NB: upstream build can be reproduce only using yarnpkg, failed with npm:
$ yarnpkg install
$ yarnpkg build
Cheers,
Xavier
Le 29/01/2019 à 07:41, Xavier a écrit :
> Le 28/01/2019 à 18:45, Jonas Smedegaard a écrit :
>> Source: popper.js
>> Version: 1.14.6+ds-1
>> Severity: serious
>> Justification: Policy 2.1
>>
>> Source package contains several files (seemingly all of them) bel
Le 29/01/2019 à 15:23, Jonas Smedegaard a écrit :
> Quoting Xavier (2019-01-29 07:41:40)
>> Le 28/01/2019 à 18:45, Jonas Smedegaard a écrit :
>>> Source: popper.js
>>> Version: 1.14.6+ds-1
>>> Severity: serious
>>> Justification: Policy 2.1
>>>
Hello Dominik,
did you check if it works now after libpcap-ng release ?
Cheers,
Xavier
thout source included.
>
> Thanks to Xavier for noticing (although only as comment in copyright
> file).
>
>
> - Jonas
I succeed to build source, but this needs:
- to upgrade: rollup-plugin-babel, browserslist
- to package or upgrade at least (I reduced this list to the minimum
possib
Le 30/01/2019 à 22:34, Jonas Smedegaard a écrit :
> Quoting Xavier (2019-01-30 22:26:57)
>> Le 29/01/2019 à 22:17, Jonas Smedegaard a écrit :
>>> Source: twitter-bootstrap4
>>> Version: 4.2.1+dfsg1-1
>>> Severity: serious
>>> Justification: Policy 2.1
&
Le 30/01/2019 à 23:47, Jonas Smedegaard a écrit :
> Quoting Xavier (2019-01-30 22:54:53)
>> Le 30/01/2019 à 22:34, Jonas Smedegaard a écrit :
>>> Quoting Xavier (2019-01-30 22:26:57)
>>>> Le 29/01/2019 à 22:17, Jonas Smedegaard a écrit :
>>>>> Source pa
Control: reassign -1 node-cssstyle
node-jsdom debian/control has a node-cssstyle dependency. However a
simple test shows that cssstyle is unusable:
$ node -e 'require("cssstyle")'
internal/modules/cjs/loader.js:583
throw err;
^
Error: Cannot find module 'cssom'
at Function.Module._re
Bug isn't related to node-process-nextick-args (same in
testing/unstable). For now it succeeds to build in testing but not in
unstable locally.
Hello,
there is something wrong with your patch:
W: node-terser source: binaries-have-file-conflict node-terser
uglifyjs.terser usr/lib/nodejs/terser/dist/bundle.js
Your link overrides a regular file
Le 21/06/2019 à 06:04, Pirate Praveen a écrit :
>
>
> On 2019, ജൂൺ 20 5:08:24 PM IST, Xavier wrote:
>> Hello,
>>
>> there is something wrong with your patch:
>> W: node-terser source: binaries-have-file-conflict node-terser
>> uglifyjs.terser usr/lib/nodej
Hi all,
libsass has been updated in testing. I think it is time to close (or at
least decrease) this RC bug.
Cheers,
Xavier
e';
> a.href = url;
> // the filename you want
> a.download = 'z.html';
> document.body.appendChild(a);
> a.click();
> window.URL.revokeObjectURL(url);
> alert('your file has downloaded!');
> }).
> catch(() = >alert('oh no!'
After more search, the problem is that if /usr/lib/nodejs/duplexer2
isn't cleaned by dpkg, the link isn't created and the
/usr/lib/nodejs/duplexer2 stays empty.
Le 10/07/2019 à 14:40, Pirate Praveen a écrit :
> Package: pkg-js-autopkgtest
> version: 0.8
> severity: serious
>
> autopkgtest_rollup_src.js → autopkgtest_rollup_dest.js...
> (!) Generated an empty bundle
> (!) Unresolved dependencies
> https://github.com/rollup/rollup/wiki/Troubleshooting#treat
Le 28/07/2019 à 10:01, Pirate Praveen a écrit :
> Package: pkg-js-tools
> Version: 0.8.2
> Severity: grave
>
> Reproducible in node-webpack master.
>
> dh_auto_configure --buildsystem=nodejs
> mkdir node_modules mkdir webpack-cli/node_modules
> ln -s ../eslint-scope node_modules/eslint-scope
> ln
Le 31/07/2019 à 10:02, Pirate Praveen a écrit :
> $ apt-file list node-uglifyjs-webpack-plugin
> node-uglifyjs-webpack-plugin:
> /usr/lib/nodejs/uglifyjs-webpack-plugin/dist/index.js
> node-uglifyjs-webpack-plugin:
> /usr/lib/nodejs/uglifyjs-webpack-plugin/lib/post_install.js
> node-uglifyjs-webpac
Control: reopen -1
Adding node-request in recommended dependencies is not enough: package
is unusable without it
source package node-retry
>> dpkg-buildpackage: info: source version 0.12.0-1
>> dpkg-buildpackage: info: source distribution unstable
>> dpkg-buildpackage: info: source changed by Xavier Guimard
>> dpkg-source --before-build .
>> dpkg-buildpackage: info: host architect
mp;stamp=1588581432&raw=0
> for examples.
Hi,
Could someone help us here ? I forwarded this bug to upstream ([1]) but
didn't receive any response for now.
(Cc to RFH bug)
Cheers,
Xavier
[1]: https://github.com/cyrusimap/cyrus-imapd/issues/3040
Le 12/05/2020 à 01:04, John Paul Adrian Glaubitz a écrit :
> On 5/12/20 1:01 AM, John Paul Adrian Glaubitz wrote:
>> On 5/11/20 11:56 PM, Xavier wrote:
>>> Could someone help us here ? I forwarded this bug to upstream ([1]) but
>>> didn't receive any response
Le 12/05/2020 à 10:34, John Paul Adrian Glaubitz a écrit :
> Hi Xavier!
>
> On 5/12/20 10:09 AM, Xavier wrote:
>>>> The problem here is va_list. On some architectures, the calling convention
>>>> doesn't seem to allow comparing va_list against NULL due to th
Control: tags -1 + moreinfo
Le 15/05/2020 à 22:10, Paul Gevers a écrit :
> Source: node-co
> Version: 4.6.0-2
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
>
> Dear maintainer(s),
>
> With a recent upload of node-co the a
Hi,
with upstream help; I just built cyrus-imapd_3.2.0-4 which may fix this
issue.
@Adrian, could you test this on your armv8 ?
Cheers,
Xavier
Le 20/05/2020 à 11:26, Xavier a écrit :
> Hi,
>
> with upstream help; I just built cyrus-imapd_3.2.0-4 which may fix this
> issue.
> @Adrian, could you test this on your armv8 ?
>
> Cheers,
> Xavier
Note that there are still 4 tests that fail [1] (failed already at least
Control: severity -1 important
This bug is partially fixed in version 3.2.0-5. Keeping it opened due to:
* some unimportant tests still fail (disabled in 3.2.0-5)
* build still fail for hppa and sparc64 [1]
[1]: https://buildd.debian.org/status/logs.php?pkg=cyrus-imapd&ver=3.2.0-5
ing backports, purging and reinstalling (the older one).
Hi,
I pushed node-dot-prop in backports. Since this package is new in
backports, wait 2-3 days to get it
Cheers,
Xavier
Forwarder mail
From: Debian FTP Masters
Subject: node-dot-prop_5.2.0-1~bpo10+1_amd64.changes is NEW
b
Le 23/05/2020 à 08:49, Felix Zielcke a écrit :
> Package: npm
> Version: 6.14.3+ds-1~bpo10+1
> Severity: grave
>
> npm installed from backports fails with:
>
> $ npm
> npm ERR! pathArray is not defined
>
> Installing node-dot-prop from testing fixes this.
node-dot-prop is in backports NEW queue
Le 22/12/2020 à 06:03, Xavier Guimard a écrit :
> Package: libjs-bootstrap4
> Version: 4.5.2+dfsg1-3
> Severity: serious
>
> Version 4.5.2+dfsg1-2 transform /usr/share/javascript/bootstrap4 from
> symlink to dir without any maintscript. This break updates.
I enabled CI for t
Le 22/12/2020 à 06:30, Jonas Smedegaard a écrit :
> Quoting Xavier Guimard (2020-12-22 06:03:43)
>> Package: libjs-bootstrap4
>> Version: 4.5.2+dfsg1-3
>> Severity: serious
>>
>> Version 4.5.2+dfsg1-2 transform /usr/share/javascript/bootstrap4 from
>> symli
Control: fixed -1 4.5.2+dfsg1-4
Hi Peter,
it is normal to find this issue in version 4.5.2+dfsg1-3 since it has
been fixed in 4.5.2+dfsg1-4!
y/jquery.js
libjs-jquery: /usr/share/javascript/jquery/jquery.js
$ ls -l /usr/share/javascript/jquery/jquery.js
lrwxrwxrwx 1 root root 34 22 déc. 08:27
/usr/share/javascript/jquery/jquery.js -> ../../nodejs/jquery/dist/jquery.js
$ ls -lL /usr/share/javascript/jquery/jquery.js
-rw-r--r-- 1 root root 287600 22 déc. 08:27
/usr/share/javascript/jquery/jquery.js
Cheers,
Xavier
memfs adds hooks to simulate a filesystem and overrides
webpack/mkdirp calls, simulating mkdirp 0.53.
You can fix this in memfs to return a promise instead of waiting for a
callback
Cheers,
Xavier
Le 23/12/2020 à 12:34, Matthias Klose a écrit :
> On 12/23/20 12:19 PM, Xavier wrote:
>> Control: tags -1 + moreinfo
>>
>> Le 23/12/2020 à 12:06, Matthias Klose a écrit :
>>> Package: libjs-jquery
>>> Version: 3.5.1+dfsg+~3.5.5-1
>>> Severity: s
Control: tags -1 help
Le 25/12/2020 à 10:34, Matthias Klose a écrit :
> Control: reopen -1
> Control: found -1 3.5.1+dfsg+~3.5.5-3
>
> the changelog reads:
>
> * Team upload
> * libjs-jquery must require node-jquery with the same version
> (Closes: #977960)
>
> and after the upgrade:
>
Le 25/12/2020 à 09:55, Xavier Guimard a écrit :
> Package: node-consolidate
> Version: 0.15.1+repack-1
> Severity: serious
>
> Enabling test proves that node-consolidate depends on node-babel-core 6:
>
> ```
> function requireReact(module, filename) {
>
Le 26/12/2020 à 22:54, Lucas Nussbaum a écrit :
> Source: node-cross-spawn-async
> Version: 2.2.5-4
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201226 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to
Le 26/12/2020 à 23:05, Lucas Nussbaum a écrit :
> Source: node-recast
> Version: 0.20.4-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201226 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on
Control: reassign -1 node-babel7
Control: reassign 978384 node-babel
Control: forcemerge -1 978384
Control: retitle -1 @babel/types: missing lib/index.d.ts
Control: affects -1 node-recast
Control: affects -1 node-ast-typpes
Le 27/12/2020 à 12:07, Xavier a écrit :
> Le 26/12/2020 à 23:05, Lu
Le 27/12/2020 à 19:04, Thorsten Glaser a écrit :
> Package: node-jquery
> Version: 3.5.1+dfsg+~3.5.5-3
> Followup-For: Bug #977960
> X-Debbugs-Cc: t...@mirbsd.de
>
> Even for the latest versions of these packages, adequate reports:
>
> node-jquery: broken-symlink /usr/share/nodejs/jquery/dist/jqu
Le 10/01/2021 à 11:05, Jonas Smedegaard a écrit :
> Quoting Debian FTP Masters (2021-01-10 10:49:04)
>> Changes:
>> typescript-types (20210110-1) unstable; urgency=medium
>> .
>>* Team upload
>>* Remove @types/node, provided by node 12.20.1~dfsg-1 (Closes: #979693)
>
> I am not convinced
Hi all,
Bullseye freeze is coming and we still have problems with node-request
removal. In particular, node-jsdom is not easy to patch. I tried a patch
(not approved by upstream) but it needs a lot of unavailable Node.js
modules.
Looking at the following list, it seems that only node-jsdom is
imp
Control: reassign -1 pkg-js-autopkgtest
Control: affects -1 ts-node
Le 15/01/2021 à 22:14, Paul Gevers a écrit :
> Source: ts-node
> Version: 9.1.1-4
> X-Debbugs-CC: debian...@lists.debian.org
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: regression
>
> Dear maintainer(s),
>
Le 18/01/2021 à 18:47, Pirate Praveen a écrit :
>
> On Mon, Jan 18, 2021 at 2:28 pm, Antonio Terceiro
> wrote:
>> But the fact is that all the other reverse dependencies that used any
>> plugin now need to be changed accordingly. Otherwise we can just wait
>> for their chart features to break in
Le 19/01/2021 à 11:11, Jonas Smedegaard a écrit :
> Quoting Xavier (2021-01-18 22:16:30)
>> Le 18/01/2021 à 18:47, Pirate Praveen a écrit :
>>>
>>> On Mon, Jan 18, 2021 at 2:28 pm, Antonio Terceiro
>>> wrote:
>>>> But the fact is that all the other
Le 19/01/2021 à 15:04, Pirate Praveen a écrit :
>
>
> On Tue, Jan 19, 2021 at 2:24 pm, Pirate Praveen
> wrote:
>> Control: severity -1 serious
>>
>> I was able to use xterm 3.8.1 from nmpjs.com with gitlab without any
>> issues. So this is a bug in node-xterm debian build.
>
> Trying to switch
Le 20/01/2021 à 21:46, Lucas Nussbaum a écrit :
> Source: node-d3-transition
> Version: 1.3.2-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20210120 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to buil
Le 24/01/2021 à 15:52, Jan Kiszka a écrit :
> Package: npm
> Version: 7.4.0+ds-1~bpo10+2
> Severity: grave
> Justification: renders package unusable
>
> Tried out via, e.g., "npm install serialport" inside a debian:buster-slim
> container. Happens with both "npm node-*" as well only the required
>
Control: tags -1 + pending
Le 25/01/2021 à 10:35, Xavier a écrit :
> Le 24/01/2021 à 15:52, Jan Kiszka a écrit :
>> Package: npm
>> Version: 7.4.0+ds-1~bpo10+2
>> Severity: grave
>> Justification: renders package unusable
>>
>> Tried out via, e.g., "np
Hi Jonas,
could you take a look at this issue? Seems not a big bug, all tests
passed except this one:
> not ok 438 formatter:html when passing a single message with illegal
characters should return a string in HTML format with 1 issue in 1 file
> Check that message is correct: expected 'Unexpec
Hi,
looking at upstream patch [1], it seems that iotjs 1.0-1 isn't affected
by this security issue: there is no `(*(++stack_top_p))` anywhere.
Cheers,
Xavier
[1]: https://github.com/jerryscript-project/jerryscript/pull/3867/files
fresh packages...
> success Saved lockfile.
> Done in 0.07s.
Hi JS Team,
yarnpkg is not in testing due to babel problems. Do you agree to
dicrease severity of this bug to allow mkdirp transition (or reassign
this bug to node-yarnpkg) ?
Cheers,
Xavier
Le 26/10/2020 à 20:50, Paolo Greppi a écrit :
> Hi Xavier,
>
> Il 26/10/20 20:24, Xavier ha scritto:
>> Le 26/10/2020 à 15:28, ano...@users.sourceforge.net a écrit :
>>> ...
>>
>> Hi JS Team,
>>
>> yarnpkg is not in testing due to babel proble
Control: reassign -1 webpack
Control: affects -1 src:pdf.js
Le 27/10/2020 à 18:09, Lucas Nussbaum a écrit :
> Source: pdf.js
> Version: 2.6.347+dfsg-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 ftbfs-bullseye
>
> Hi,
>
> During a reb
Control: reassign -1 node-fetch
Control: affects -1 node-formidable
Le 27/10/2020 à 18:07, Lucas Nussbaum a écrit :
> Source: node-formidable
> Version: 1.2.1+20200129git8231ea6-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201027 ftbfs-bullse
Control: reassign -1 src:pdf.js
Control: found -1 2.6.347+dfsg-1
Le 27/10/2020 à 23:29, Xavier a écrit :
> Control: reassign -1 webpack
> Control: affects -1 src:pdf.js
>
> Le 27/10/2020 à 18:09, Lucas Nussbaum a écrit :
>> Source: pdf.js
>> Version: 2.6.347+dfs
Control: retitle -1 node-fetch has no default export
Le 27/10/2020 à 21:47, Xavier a écrit :
> Control: reassign -1 node-fetch
> Control: affects -1 node-formidable
>
> Le 27/10/2020 à 18:07, Lucas Nussbaum a écrit :
>> Source: node-formidable
>> Version: 1.2.1+20200129
Le 29/10/2020 à 14:07, Moritz Schlarb a écrit :
> Hi Xavier,
>
> thanks for the rapid fix!
> Would you consider requesting to include this on the next point release?
>
> Thanks a lot,
> Moritz
Done ;-)
Hi,
Sadly, there is no easy example, API differs...
Le 9 novembre 2020 15:55:21 GMT+01:00, Andrius Merkys a
écrit :
>Hello,
>
>On 2020-11-09 16:37, Xavier Guimard wrote:
>> node-request won't be part of bullseye, please patch
>> node-client-sessions to replace node-
Control: tags -1 + moreinfo
Le 28/01/2021 à 21:12, Andreas Beckmann a écrit :
> 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 FTB
Control: tags -1 - moreinfo
Control: tags -1 + experimental
Control: reassign -1 nodejs
Control: found -1 14.13.0~dfsg-1
Control: retitle -1 nodejs: missing ts definitions
Control: notfound -1 12.20.1~dfsg-3
Le 29/01/2021 à 05:53, Xavier a écrit :
> Control: tags -1 + moreinfo
>
>
Control: tags -1 + moreinfo
Hi,
debci autopkgtest still reports "Cannot find module 'iconv'" with arm64,
armhf i386 and ppc64el but I'm unable to reproduce this in a porterbox
(and node-iconv is listed in test dependencies). Could someone take a look ?
1 - 100 of 724 matches
Mail list logo
