Package: pkg-js-tools
Version: 0.9.7
Hello,
nodejs buildsystem uses grunt, thus pkg-js-tools should pull in grunt.
Best,
Andrius
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
On 2019-08-22 08:41, Xavier wrote:
> Hi, sorry but I don't understand this issue. pkg-js-tools has already a
> grunt auto_build
Indeed, but this is not the issue. I have a source package with a
Gruntfile, and I want to build it with '--buildsystem nodejs'. As
pkg-js-tools does not depend on
Package: pkg-js-tools
Version: 0.9.6
Hello,
pkg-js-tools should pull in nodejs, just as gradle-debian-helper pulls
in gradle and maven-debian-helper does with maven.
Best,
Andrius
--
Andrius Merkys
Vilnius University Institute of Biotechnology, Saulėtekio al. 7, room V325
LT-10257 Vilnius
Hi,
On 2019-08-22 09:27, Xavier wrote:
> This is not the JS-Team plan: pkg-js-tools will be able to build
> automatically using rollup, grunt, gulp, babel, nyc, tsc,... It could
> not depend on all of these JS builders.
I see the point here. No more reports from me for now, pkg-js-tools can
be
On 2019-08-21 15:50, Xavier wrote:
> thanks for your reports! A a workaround, you can set "grunt" in
> debian/nodejs/build. If you are doing more test, I can wait to push next
> pkg-js-tools with your patches
Thanks a lot for prompt response! Would you mind postponing next release
of pkg-js-tools
Source: pkg-js-tools
Severity: wishlist
control: tag -1 + patch
control: forwarded -1
https://salsa.debian.org/js-team/pkg-js-tools/merge_requests/2
Hello,
I propose the addition of dh-make-node tool which, as the other
dh-make-* tools, generates debian/ directory by reading package.json.
The
Package: node-requirejs-text
Version: 2.3.6-1
Affects: node-requirejs node-grunt-contrib-requirejs
Hello,
node-requirejs-text installs its package.json to
/usr/share/nodejs/requirejs, where the package.json of node-requirejs is
expected to be. This results in the failing test (grunt test -v
Hi Sean,
Many thanks for the review.
On 2020-04-16 02:00, Sean Whitton wrote:
> src/scss/mixins/_gradients.scss has code from another project with
> different copyright holders.
Thanks for noticing this – I will add an entry in debian/copyright
regarding this file.
> It looks like
Hi Andreas,
On 2020-04-07 22:49, Andreas Tille wrote:
> Aaaargh. Could we include Debian JS team into our sprint? I think we'd
> definitely need help here? Any volunteer to help us fighting Covid-19?
I have some experience in packaging JS, and I would be willing to help.
However, this is a
Hi Sean,
Many thanks for your comments.
On 2020-04-08 17:31, Sean Whitton wrote:
> d/copyright is a bit confusing -- dist/css has been removed but "we
> are installing it directly" ...?
Indeed, dist/ directory had been excluded via Files-Exclude, but the
comments in d/copyright has not been
Hi Thorsten,
On 2020-04-23 00:00, Thorsten Alteholz wrote:
> according to LICENSE, the copyright holder is Eloqua. Please clarify with
> Seth Carney who really owns the copyright.
Thanks for the review. I have posted a request to clarify the copyright
on the GitHub [1].
Best,
Andrius
[1]
Hello,
On 2020-04-26 20:15, Sean Whitton wrote:
> It depends on the answer to my original question, which I do not believe
> you have answered: can the tests be run successfully without this file?
Sorry for not answering properly earlier.
No, some of the tests cannot be run without
Hi Jonas,
On 2020-04-28 10:43, Jonas Smedegaard wrote:
> Please file bugreports, to make the issue actionable, and to help track
> progress.
Thanks for the advice. I will try to keep up with it.
Best wishes,
Andrius
signature.asc
Description: OpenPGP digital signature
--
Hello Sean,
On 2020-05-13 06:17, Sean Whitton wrote:
> In that case I think the files need to be filtered out, as otherwise we
> would be including code in Debian main without also including all its
> dependencies.
OK, I think I understand the issue. Could you please reject the package
so as I
Hello,
On 2020-05-13 07:00, Sean Whitton wrote:
> +--+
> | REJECT reasoning |
> +--+
>
> Per existing e-mail discussion, tests/unit-*.html need filtering out
> of the source tarball as their dependencies are not in Debian main.
Thanks! Repacked and
Hello,
On 2020-05-14 01:02, Sean Whitton wrote:
> It seems you have already reuploaded it?
Yes, I have reuploaded 4.0.13+dfsg1-1 right after receiving the REJECT
notice.
Best,
Andrius
signature.asc
Description: OpenPGP digital signature
--
Pkg-javascript-devel mailing list
Source: select2.js
Severity: wishlist
Control: block -1 by 959411
Upstream uses grunt-contrib-qunit to run automated tests in headless Web
browser. These tests should be used in build time and autopkgtest to
ensure the integrity of the package.
Andrius
--
Pkg-javascript-devel mailing list
On 2020-07-12 13:52, Jonas Smedegaard wrote:
> I think that when we declare only¹ lower bounds, we do avoid the biggest
> headache of nodejs failing to transition - and reduce the problem to
> each package requiring a binNMU being flagged as such.
[snip]
> ¹ ...and obviously declare upper
Hello,
I am trying to package git HEAD for node-node-sass [1]. However, I
cannot get the MUT update right [2]. I have tried 'gbp import-orig
--pristine-tar --uscan', but when I use gbp to build the package, I get:
dpkg-source: error: aborting due to unexpected upstream changes, see
Hi,
On 2020-07-09 13:12, Nilesh Patra wrote:
> For me, it was failing to even gbp import - I noticed that the
> compression=xz parameter is missing in the watch file.
> After fixing this, the build starts and w/o the unexpected changes thingy.
> I've pushed to salsa, please $gbp pull :-)
Thanks
Hi,
On 2020-07-09 14:14, Nilesh Patra wrote:
> Oops:
> tar cvfJ
> node-node-sass_4.14.1+git20200512.e1fc158+dfsg.orig-sass-spec.tar.xz
> sass-spec
>
>
> mv sass-spec.xz
> ../node-node-sass_4.14.1+git20200512.e1fc158+dfsg.orig-sass-spec.tar.xz
> ../
>
>
> mv
) UNRELEASED;
urgency=medium
+
+ * Fetching git HEAD, excluding src/libsass.
+ * New upstream version 4.14.1+git20200512.e1fc158+dfsg
+
+ -- Andrius Merkys Wed, 08 Jul 2020 09:00:53 -0400
+
node-node-sass (4.14.1-2) unstable; urgency=medium
* Team upload
diff --git a/debian/copyright b/debian
On 2020-07-10 10:27, Jonas Smedegaard wrote:
> How is that a different situation from node-iconv or node-expat?
I stand corrected, the situation is the same as in node-iconv and
node-expat. Sorry for the noise. However, I still think that long term
solution would be to specify both lower and
On 2020-07-09 22:29, Jonas Smedegaard wrote:
> Please, Andrius, think twice before repeating the discussion already had
> about node-iconv and node-expat.
>
> I urge you to read through that previous thread (if you haven't
> already), and I recommend that you consider if it is really worth it
On 2020-07-11 11:00, Jonas Smedegaard wrote:
> Reason I suspect upstream-only tracking is wrong is that also Debian
> changes can change ABI - either deliberately or accidentally. Most
> notibly by adding/changing patches, but possibly also through changes to
> build-dependencies.
Agree.
> I
Hello,
Could someone with appropriate rights delete repositories
js-team/node-http-proxy{,-old} from salsa? They have been created incorrectly
and have to be redone anew.
Thanks,
Andrius
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Hello,
On 2020-07-08 18:46, Jonas Smedegaard wrote:
> I don't want packages removed either - and for this one specifically, I
> very much look forward to having mermaid in Debian - cool stuff!)
I also would be unhappy to see node-node-sass removed from Debian, but I
subscribe to Jonas's opinion
On 2020-07-09 09:38, Jonas Smedegaard wrote:
> You are now owner in the team and can do it yourself.
Many thanks!
Andrius
signature.asc
Description: OpenPGP digital signature
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Hello,
On 2020-07-09 23:03, Jonas Smedegaard wrote:
> If sass-spec as packaged for Debian is unsuitable for node-node-sass,
> then please file bugreport(s) against that other package
> clarifying what is needed/broken.
nodejs package node-sass-spec is not built from sass-spec source
currently. I
Hi Xavier,
On 2020-09-03 15:54, Xavier wrote:
> buffer-equal:
> - node-buffer-equal (1.0.0)
> - node-vinyl-fs (1.0.0)
Does this (and the like) mean that is now packaged as
node-? If so, such embedded modules might be removed.
Best,
Andrius
--
Pkg-javascript-devel mailing list
On 2020-09-03 16:23, Jonas Smedegaard wrote:
> Quoting Andrius Merkys (2020-09-03 14:59:38)
>> On 2020-09-03 15:54, Xavier wrote:
>>> buffer-equal:
>>> - node-buffer-equal (1.0.0)
>>> - node-vinyl-fs (1.0.0)
>> Does this (and the like) mea
Source: node-ws
Version: 7.3.1+~cs24.0.5-1
Dear Maintainer(s),
node-ws embeds nodejs module agent-base which has recently entered
Debian as package node-agent-base. Please remove the embedded module and
depend on node-agent-base instead.
Best wishes,
Andrius
--
Pkg-javascript-devel mailing
On 2020-07-10 12:38, Jonas Smedegaard wrote:
> I suspect you are wrong about relaxing lower bounds to only upstream
> part.
I got this idea from the way the issue was fixed in node-expat [1].
Could you explain why you think this is a bad idea?
[1]
Hello,
It seems #975794 (node-ws) and #975819 (node-agent-base) are related as
they concern the same piece of code of agent-base, which is packaged in
node-agent-base and embedded in node-ws. Removing agent-base source from
node-ws is underway (#972541).
Best,
Andrius
--
Pkg-javascript-devel
Hello,
On 2020-12-07 20:46, Pirate Praveen wrote:
> I have fixed node-request to work with node-uuid 8 API and it also fixed
> yarnpkg/gitlab.
Does this mean node-request is going to be part of bullseye? There was a
mass bug filling (see #974064 for example) suggesting otherwise.
Best,
Andrius
On 2020-12-08 08:45, Pirate Praveen wrote:
> On 2020, ഡിസംബർ 8 10:53:26 AM IST, Andrius Merkys wrote:
>> Hello,
>>
>> On 2020-12-07 20:46, Pirate Praveen wrote:
>>> I have fixed node-request to work with node-uuid 8 API and it also fixed
>>> yarnpkg/gi
Source: node-original
Hello,
'node-original' embeds a copy of source code of 'assume' node module,
which has recently entered Debian as 'node-assume'. Please switch from
embedded code copy to Debian-packaged module.
Best,
Andrius
--
Pkg-javascript-devel mailing list
Source: node-url-parse
Hello,
'node-url-parse' embeds a copy of source code of 'assume' node module,
which has recently entered Debian as 'node-assume'. Please switch from
embedded code copy to Debian-packaged module.
Best,
Andrius
--
Pkg-javascript-devel mailing list
Hi Paul,
On 2020-11-05 01:27, Paul Wise wrote:
> Based on the GitHub descriptions, node-fn.name and node-fn-name have
> identical functionality. Should one of them be removed from Debian and
> should one of the upstream projects be replaced by the other within the
> NodeJS ecosystem? It seems
Hello,
On 2020-11-05 11:37, Paul Wise wrote:
> Based solely on the usage information in the README, their APIs are
> compatible, so just changing from fn.name to fn-name or vice versa in
> the require() call will be enough to switch between them.
Thanks, I will try it.
> I'm not sure which one
Source: node-yarnpkg
Version: 1.22.10+~cs22.25.14-2
node-yarnpkg embeds tar-fs, which has been recently packaged as
node-tar-fs. Please consider using the Debian package instead the
embedded source.
Andrius
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Hello,
mkdirp-classic can also be removed, as it has been packaged as
node-mkdirp-classic. I assume it is embedded here only because of tar-fs.
Andrius
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Package: pkg-js-autopkgtest
Version: 0.9.63
There is a couple of outdated/incorrect bits in the description (in
debian/control) of pkg-js-autopkgtest:
> Description: collection of autopktest scripts for Perl packages
s/autopktest/autopkgtest/
> Packages using the tests with autopkgtests in
On 2021-01-20 15:00, Andrius Merkys wrote:
>> Description: collection of autopktest scripts for Perl packages
Sorry, this line should have been:
> Description: collection of autopktest scripts for Nodejs packages
Nevertheless, 'autopktest' spelling remains.
Best,
Andrius
--
Pkg-j
On 2021-03-15 13:51, Pirate Praveen wrote:
> On 2021, മാർച്ച് 15 11:55:19 AM IST, Andrius Merkys wrote:
>> On 2021-03-14 14:49, VIVEK K J wrote:
>>> I've been modified node-agent-base package for including
>>> typescript definitions.. The modified rep
Hi,
On 2021-03-14 14:49, VIVEK K J wrote:
> I've been modified node-agent-base package for including
> typescript definitions.. The modified repo is available at
> https://salsa.debian.org/vivekkj/node-agent-base .
> Requesting for Sponsorship..
I am getting lintian warnings:
W:
Hello,
On 2021-03-14 14:49, VIVEK K J wrote:
> I've been modified node-agent-base package for including
> typescript definitions.. The modified repo is available at
> https://salsa.debian.org/vivekkj/node-agent-base .
> Requesting for Sponsorship..
Could you please open a merge request
On 2021-03-15 09:24, Pirate Praveen wrote:
> On 2021, മാർച്ച് 15 11:55:19 AM IST, Andrius Merkys wrote:
>> On 2021-03-14 14:49, VIVEK K J wrote:
>>> I've been modified node-agent-base package for including
>>> typescript definitions.. The modified rep
Hi Nilesh,
On 2021-03-15 12:29, Nilesh Patra wrote:
> On 15 March 2021 2:13:10 pm IST, Andrius Merkys wrote:
>> On 2021-03-15 09:24, Pirate Praveen wrote:
>>> We can upload to experimental so work depending on it does not have
>> to wait.
>>
>> Ma
Hello,
On 2021-03-15 13:45, Pirate Praveen wrote:
> On 2021, മാർച്ച് 15 4:21:37 PM IST, Nilesh Patra wrote:
>>> $ node-sass
>>> /usr/share/nodejs/normalize-package-data/lib/fixer.js:138
>>> if (!(deps in data)) return
>>> ^
>>
>> Since node-node-sass is supposed to be used as a library, probably
On 2021-03-17 06:50, Yadd wrote:
> Le 16/03/2021 à 12:22, Andrius Merkys a écrit :
>> I am getting lintian warnings:
>>
>> W: node-agent-base: nodejs-module-not-declared node-async-listen
>> usr/share/nodejs/async-listen/package.json
>> W: node-agent-base: node
Hi,
On 2021-03-18 18:55, Nilesh Patra wrote:
> On 18 March 2021 8:22:54 pm IST, Andrius Merkys wrote:
>
> On 2021-03-15 13:45, Pirate Praveen wrote:
>>> If no one steps in to fix this, then we can consider removing it.
>> Codesearch does not list any uses of node-s
On 2021-03-19 07:55, Pirate Praveen wrote:
> On 2021, മാർച്ച് 18 8:22:54 PM IST, Andrius Merkys wrote:
>> Codesearch does not list any uses of node-sass binary. Thus I think it
>> is safe to remove it.
>
> How? A command line interface can be used directly by users.
&
Hi,
On 2021-10-08 11:43, Yadd wrote:
> Take a look at
> https://github.com/sindresorhus/got/blob/main/documentation/migration-guides/request.md
Thanks for the link. I recall trying to follow these guidelines, but I
dropped the ball on it.
However, the package seems abandoned upstream and is
Hi Yadd,
First and foremost, thank you very much for taking care of my packages!
And sorry for the low quality. I will take your notice into consideration.
On 2021-11-21 09:46, Yadd wrote:
> I don't think it's normal to push package with npm2deb default template
> without looking at debian/*
Hi Yadd,
On 2021-11-21 15:18, Yadd wrote:
> I just updated npm2deb, however it is a good practice to launch
> `lintian-brush`. In addition, npm2deb's agorithm is very questionable,
> in particular for the search for reverse dependencies.
Thanks for the recommendation. I was not using
Hi Thorsten,
On 2021-12-10 21:00, Thorsten Alteholz wrote:
> please mention "Paul Vorbach and contributors" in your debian/copyright.
Thanks for spotting this! Yadd has fixed the issue, I have uploaded the
fixed version.
Best,
Andrius
--
Pkg-javascript-devel mailing list
Hi Yadd,
Thanks a lot for your help!
I see you have updated puppeteer to v13.0.1. Martina and I have
attempted to stick to earlier versions, but if you had luck building
v13.0.1, IMO this is even better.
On 2022-01-14 10:41, Yadd wrote:
> I started to modify your package. The problem for tests
Hello,
Martina and I have been working on packaging puppeteer, an API to
control Chrome over the DevTools Protocol. Martina got the package
building on sbuild, but we are stuck with tests. Most likely the blocker
is incorrect combination of extcopies/extlinks, but we are not able to
sort it out
Hi Daniel,
You said you were interested in updating libjs-modernizr. I need
libjs-modernizr >= 3.5.0 to package node-puppeteer. Could you prepare an
update on a fork/branch in salsa?
Best,
Andrius
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Hi,
On 2022-03-18 16:13, Yadd wrote:
> Maybe this can help:
> https://salsa.debian.org/js-team/node-terser/-/blob/debian/latest/debian/patches/1001_commander.patch
Thanks for pointer. I think I managed to go this far myself by patching:
-const program = require('commander')
+const program =
Source: node-wikibase-cli
Version: 15.15.4
Severity: serious
Tags: help
While node-wikibase-cli was in NEW, node-commander was updated from
6.2.1 to 9.0.0. node-wikibase-cli is compatible with node-commander 6.x
only and simple patching does not seem to help. I will try patching it a
bit more,
On Thu, 24 Feb 2022, 22:21 Andreas Tille, wrote:
> Am Wed, Feb 23, 2022 at 06:10:24PM +0200 schrieb Andrius Merkys:
> > >
> https://github.com/sockjs/sockjs-client/commit/d9584abe2c7c913ce95a1aea29e5744dd85e1af4
> > > <
> https://github.c
On 2022-02-28 08:58, Andrius Merkys wrote:
> If I get a second opinion that
> node-devtools-protocol is not worthy as a package on its own, I will RM it.
Here I meant second opinion besides mine. So if anyone would say
node-devtools-protocol is not worth staying in Debian on its own, I w
Hi Eric,
On 2022-02-27 22:36, Eric Brown wrote:
> Likewise, thank you very much! It’s exciting that the dependencies for
> shiny-server are coming together. Please note the upstream for
> sockjs-client responded to me and released 1.6.0 which also updates some
> other dependency versions.
You
Hello,
On 2022-02-28 06:09, Martina Ferrari wrote:
>> node-puppeteer embeds a copy of devtools-protocol while Debian has
>> node-devtools-protocol. Please drop this and use node-devtools-protocol
>> dependency
>
> This was done on purpose, as it is not really workable to keep them
> separate due
On 2022-02-22 13:20, Andreas Tille wrote:
> Unfortunately we have a new problem as
> autopkgtest shows[4]
>
>sockjs-client : Depends: node-json3 (>= 3.3.2) but it is not installable
>
> while we had this package before it was removed[5] from Debian.
>
> I need to admit that I have no idea
Hi Eric,
On 2022-02-22 14:52, Eric Brown wrote:
> If I’m understanding the below correctly, it appears that the node-json3
> may already have been removed from the dependency socksjs-client, but
> the updated version is not released yet.
>
>
Hi Eric,
On 2022-02-22 14:52, Eric Brown wrote:
> If I’m understanding the below correctly, it appears that the node-json3
> may already have been removed from the dependency socksjs-client, but
> the updated version is not released yet.
>
>
Hello,
Replying to Nilesh and Andreas in the same mail.
On 2022-02-25 07:49, Andreas Tille wrote:
> Am Fri, Feb 25, 2022 at 03:09:36AM +0530 schrieb Nilesh Patra:
>>> Sure. It would be nice to get ACK from Pirate, though, as he owns the ITP.
>> I am a bit confused, why would you need ack from
Hello,
On 2022-03-24 11:39, Nilesh Patra wrote:
> node-send is patched[1] to use node-mime-types instead of node-mime.
The patch should be dropped altogether, since node-ms is now a package
on its own.
> [1]:
>
On 2022-03-30 07:50, Yadd wrote:
> /usr/bin/* links were wrong. I fixed all these issues
Thanks a lot!
Best,
Andrius
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Hi Yadd,
On 2022-03-29 19:17, Yadd wrote:
> On 29/03/2022 17:44, Yadd wrote:
>> Hi Andrius,
>>
>> you fix is enough for commander 8, I'm currently writing commander 9
>> patch
>
> Fixed and pushed. However package looks unusable because all bin/*
> commands are not in $PATH. You could either:
>
Hi Nilesh,
On 2022-01-27 17:00, Nilesh Patra wrote:
> It is because of:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004272
Thanks for the pointer. However, it is not evident to me how this bug
could cause false-positive freeze blocks, but maybe there is a whole
story behind that.
Hi Nilesh,
On 2022-01-28 09:48, Nilesh Patra wrote:
> On 1/28/22 12:55 PM, Andrius Merkys wrote:
>> Thanks for the pointer. However, it is not evident to me how this bug
>> could cause false-positive freeze blocks, but maybe there is a whole
>> story behind t
Hi,
On 2022-01-27 16:09, Nicolas Mora wrote:
> It seems that the last javascript packages uploaded to unstable can't
> migrate to testing due to a blocking request, for example:
>
> https://tracker.debian.org/pkg/node-pbkdf2
> https://tracker.debian.org/pkg/node-jose
>
Hi,
On 2022-01-27 16:49, Yadd wrote:
> tracker.d.o shows reasons. Fixed for node-pbkdf2
I still see "Not touching package due to block request by elbrus (Follow
the freeze policy when applying for an unblock)" in [1], which seems
misleading to me. We are not in freeze, AFAIK.
[1]
Hi Daniel,
Thanks for sharing your insight into libjs-modernizr.
On 2022-01-21 11:04, Daniel Ring wrote:
On 1/11/2022 1:43 AM, Andrius Merkys wrote:
You said you were interested in updating libjs-modernizr. I need
libjs-modernizr >= 3.5.0 to package node-puppeteer. Could you prepare an
upd
Hi all,
Back in a day I packaged/sponsored a bunch of node packages needed by
node-shiny-server. I ended up never using shiny-server and/or
node-shiny-server, but with the responsibility for its dependencies. I
would be happy if someone from Med or JS teams could step up and replace
me as
Hi,
On 2023-10-23 22:04, Bastien Roucariès wrote:
Source: node-katex
Source package names in Subject and Source do not match. Please retitle
if this is not intentional.
Best,
Andrius
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
Hi Yadd,
On 2022-06-24 17:10, Yadd wrote:
> I prepared a fix, pushed to salsa. Could you take a look ?
Thanks a lot, reviewed and uploaded.
Best wishes,
Andrius
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
control: tags -1 + moreinfo
Hi Steve,
On Sat, 20 Aug 2022 15:05:03 -0700 Steve Langasek
wrote:
> In Ubuntu, node-wikibase-cli fails to build from source because dh_auto_test
> runs a test suite at build time which requires Internet access, and the
> Ubuntu build environment does not allow
Hello,
On Thu, 18 Aug 2022 12:12:09 +0200 Yadd wrote:
node-fetch 3 is ready in experimental. It is an hybrid package:
* ES part is node-fetch-3
* CJS part reproduces node-fetch-2 behavior
This changes are OK for all packages except node-wikibase-cli and
node-wikibase-edit. Sadly I didn't
Package: node-should
Version: 13.2.3~dfsg-6
Severity: wishlist
Hello,
I am working to update node-wikibase-sdk to 9.0.5 (newest release ATM).
The new release has tests depending on @types/should which does not seem
to be packaged.
Andrius
--
Pkg-javascript-devel mailing list
Hi,
On 2023-03-23 17:05, Yadd wrote:
should.js already provides its typescript definitions, @types/should is
an empty package. Maybe the issue is just to rename "typings" field into
"types"
Thanks for the prompt fix. It may have been my mistake to forget to
include 'should' into
Source: node-eventemitter3
Severity: wishlist
Version: 4.0.7-3
Hello,
node-eventemitter3 contains a debian/todo file with the following content:
Tests depend on node-assume, which is not yet packaged (#962635):
mocha spec --timeout 1 test/test.js
node-assume is now packaged and it
Source: node-agent-base
Severity: normal
Hello,
The upstream of node-agent-base has merged several repositories into
one, thus debian/watch should be updated to see more recent versions of
this package. Upstream message could be found here [1].
[1]
Hello,
I have commented out a pair of test cases which attempted network access
in the upload of node-wikibase-cli 15.15.4-5. Could you please check
whether FTBFS continues?
On Wed, 14 Dec 2022 12:16:39 +0100 Sven Mueller wrote:
Interestingly, in our build environment which has some
Source: node-pause
Severity: wishlist
Hello,
Back in a day I packaged/sponsored a bunch of node packages needed by
node-shiny-server. I ended up never using shiny-server and/or
node-shiny-server, but with the responsibility for its dependencies.
Thus I would like to be removed from the
Source: node-stable
Severity: wishlist
Hello,
Back in a day I packaged/sponsored a bunch of node packages needed by
node-shiny-server. I ended up never using shiny-server and/or
node-shiny-server, but with the responsibility for its dependencies.
Thus I would like to be removed from the
Source: node-ip-address
Severity: wishlist
Hello,
Back in a day I packaged/sponsored a bunch of node packages needed by
node-shiny-server. I ended up never using shiny-server and/or
node-shiny-server, but with the responsibility for its dependencies.
Thus I would like to be removed from the
Source: node-morgan
Severity: wishlist
Hello,
Back in a day I packaged/sponsored a bunch of node packages needed by
node-shiny-server. I ended up never using shiny-server and/or
node-shiny-server, but with the responsibility for its dependencies.
Thus I would like to be removed from the
Source: node-client-sessions
Severity: wishlist
Hello,
Back in a day I packaged/sponsored a bunch of node packages needed by
node-shiny-server. I ended up never using shiny-server and/or
node-shiny-server, but with the responsibility for its dependencies.
Thus I would like to be removed from
93 matches
Mail list logo
