Hi,
Le 2022-10-26 à 11 h 09, Yadd a écrit :
Le Mercredi, Octobre 26, 2022 16:46 CEST, Nicolas Mora
a écrit:
Hi,
mass-bug but manual fixes (even if I built some ephemeral tools here ;-))
Indeed,
but still, why are the patches marked as "Forwarded: not-needed"?
--
Pkg-javasc
Hello,
Thanks for the mass fix Yadd,
Le 2022-10-26 à 08 h 50, Debian FTP Masters a écrit :
Accepted:
Format: 1.8
Date: Wed, 26 Oct 2022 14:28:39 +0200
Source: node-i18next-browser-languagedetector
Built-For-Profiles: nocheck
Architecture: source
Version: 6.1.8-2
Distribution: unstable
Le 2022-10-16 à 00 h 19, Yadd a écrit :
If I build using ollup --bundleConfigAsCjs -c, build fails with the
following error:
[!] TypeError: nodeResolve is not a function
Hi, replace
const nodeResolve = require('@rollup/plugin-node-resolve')
by
const {nodeResolve} =
Hello,
Le 2022-10-12 à 06 h 22, Yadd a écrit :
Hi all,
one of the main changes with rollup 3 is that it doesn't accept ES in
rollup.config.js except if "type=module". Those package should rename
their rollup.config.js into rollup.config.mjs.
I encounter several problems while migrating to
Package: node-react-audio-player
Version: 0.17.0-2
Severity: normal
X-Debbugs-Cc: pkg-javascript-de...@lists.alioth.debian.org
I intent to remove node-react-audio-player from the Debian archive, it has
originally been added to Debian to help build a bigger package.
But considering the amount of
Hello,
A few years ago, I packaged and uploaded node-react-audio-player because
I needed it and some others to build another expected big package.
Then, after a long time of tries and failures, I realized the big
package will most likely not be uploaded in Debian as is, there are too
many
Hello,
Le 2022-01-27 à 09 h 29, Andrius Merkys a écrit :
This is not limited to javascript packages. All my migrations seem to be
blocked as well no matter the team/language.
My bad, this makes it more even weird though...
--
Pkg-javascript-devel mailing list
Hello,
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
https://tracker.debian.org/pkg/node-i18next
I don't see any information
Hello Ayoyimika,
I've updated the webpack patch for webpack 5. Now the build goes
further, but it fails anyway:
make[1]: Entering directory '/<>'
webpack -p
internal/modules/cjs/loader.js:818
throw err;
^
Error: Cannot find module 'import-local'
Require stack:
-
Hello,
Le 2021-12-30 à 06 h 22, Ayoyimika Ajibade a écrit :
We are starting to build against webpack5 in experimental and the
package needed for local build is webpack and node-webpack-source from
experimental.
During a test rebuild, node-react-audio-player was found to fail to
build in
Hello again,
Le 2021-10-26 à 09 h 33, Nicolas Mora a écrit :
So if there's no objection, I would like to send a patched
node-i18next-http-backend which uses node-fetch instead of cross-fetch
like before. When cross-fetch will be packaged, I'll reupload
node-i18next-http-backend without
Hello team,
I updated the node-i18next* in unstable, but node-i18next-http-backend
added cross-fetch [1] as a dependency, which isn't packaged in Debian
yet. Which leads to ftbfs for Glewlwyd [2]
I'm working on packaging node-cross-fetch to definitely fix that, but
it's not easy-peasy for
Hello,
Le 2021-09-23 à 10 h 06, Yadd a écrit :
"pkg-js-autopkgtest-require" tries to use "require(foo)". If your
package isn't a node module, you can:
echo "require" >debian/tests/pkg-js/SKIP
Be careful to upstream changes. Some updates declares "type: module" in
package.json which isn't
Hello,
I have 2 js packages blocked in unstable because of autopkgtests fail:
- https://tracker.debian.org/pkg/node-i18next-http-backend
- https://tracker.debian.org/pkg/node-redux
For both of them, autopkgtest result says:
autopkgtest [19:12:52]: test pkg-js-autopkgtest:
Hello,
Le 2021-01-26 à 06 h 32, Xavier a écrit :
But node-i18next-xhr-backend has popcon = 1 and according to upstream:
https://github.com/i18next/i18next-xhr-backend
it is "[deprecated] can be replaced with i18next-http-backend"
The latter we already have in Debian:
Le 2020-12-31 à 09 h 53, Pirate Praveen a écrit :
Can someone from the team grant me admin for this repo? then I'll
reapply or cleanup my changes.
You have maintainer access now.
Thanks!
OpenPGP_0xFE82139440BD22B9.asc
Description: application/pgp-keys
OpenPGP_signature
Description:
Hello,
Thanks for the upload, although I remember I'm having problems with this
package salsa repo, I don't have admin access to it, therefore I can't
push to master branch. I made some changes I pushed in the branch
merge-master a few days ago [1].
Can someone from the team grant me admin
Le 2020-11-04 à 07 h 57, Xavier a écrit :
Let's try this in experimental!
Please JS Team, install npm from experimental and test it!
It took me 2 packages build to realize this is about npm and not nodejs :p
So no impact for my packages...
If someone needs a hand to test packages with npm
Hello,
I've completed my node-fetch test in experimental and saw no issues on
my side, nor the package node-isomorphic-fetch which is a reverse dep.
Unless someone has an objection, I'll move node-fetch 2.6.1 to unstable
in the next days.
/Nicolas
--
Pkg-javascript-devel mailing list
Le 20-09-03 à 10 h 33, Xavier a écrit :
>> A second step would be to report all embedded code to the security team
>> - see https://wiki.debian.org/EmbeddedCopies
>
> Partially done
>
Awesome!
>> A third step would be to ask the security team how we might better help
>> them handle this¹
Hello,
Concerning embedded modules, this raises me another question.
Le 20-09-03 à 08 h 54, Xavier a écrit :
> serialize-javascript:
> - node-compression-webpack-plugin (1.9.1)
> - node-copy-webpack-plugin (1.4.0)
> - node-uglifyjs-webpack-plugin (1.7.0)
A CVE was recently
Package: wnpp
Severity: wishlist
Owner: Nicolas Mora
X-Debbugs-CC: pkg-javascript-de...@lists.alioth.debian.org
* Package name : node-i18next-http-backend
Version : 1.0.18
Upstream Author : i18next
* URL : https://github.com/i18next/i18next-http-backend
* License : Expat
Programming Lang
Hello,
In order to package node-i18next-http-backend which replaces
node-i18next-xhr-backend, I need to upgrade package node-fetch to 2.6.0.
According to "build-rdeps node-fetch", this package has the following
build dependencies:
node-isomorphic-fetch
node-formidable
node-jsdom
node-solid-rest
Le 20-07-26 à 18 h 01, Pirate Praveen a écrit :
>
>>
>> File in node-lodash unstable package:
>> 4.17.19+dfsg-1 _baseOrderBy.js https://paste.debian.net/1157886/
>>
I made a dirty hack to check my theory and it looks like if I patch this
file by replacing 'isArray' with 'Array.IsArray' or if I
I'm not sure yet if this would fix the bug but in all the build log
errors, I see that the file /usr/share/nodejs/lodash/_baseOrderBy.js is
always the source of the error.
The file _baseOrderBy.js in the package seems buggy for an unresolved reson.
File in node-lodash unstable package:
, 6 Jun 2020 19:47:42 -0400
De : Nicolas Mora
Pour : Debian Javascript Maintainers
Hello tram,
I'm looking for a DD to upload the new package "node-react" in unstable
with my fix.
* Package name: node-react
Version : 16.13.1+dfsg+~cs16.9.34-2
Upstream Author : Fac
Sujet : RFS - node-react - d/nodejs/additional_components: install all
modules
Date : Sat, 6 Jun 2020 19:47:42 -0400
De : Nicolas Mora
Pour : Debian Javascript Maintainers
Hello tram,
I'm looking for a DD to upload the new package "node-react" in unstable
with my fix.
* Pa
Hello tram,
I'm looking for a DD to upload the new package "node-react" in unstable
with my fix.
* Package name: node-react
Version : 16.13.1+dfsg+~cs16.9.34-2
Upstream Author : Facebook, Inc.
* URL : https://github.com/facebook/react/
* License : Expat
Hello team,
The package node-redux has been updated thanks to yadd's feedbacks, I
also added a few updates and fixes to it.
Since the package node-symbol-observable 1.2 is now in testing,
node-redux is ready.
Can a DD push the package node-redux [1] to the NEW queue if my package
fits Debian's
Le 20-05-13 à 03 h 33, Xavier a écrit :
>
> Push a few minutes ago
>
Thanks all for your help!
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Hello,
Le 20-05-12 à 01 h 21, Nilesh Patra a écrit :
>
> Can I upgrade the salsa package node-symbol-observable to 1.2.0? [2]
>
> Yes, I guess.
>
> [~]$ reverse-depends node-symbol-observable
> No reverse dependencies found
>
> [~]$ reverse-depends -b node-symbol-observable
> No reverse
Le 20-05-11 à 17 h 01, Nilesh Patra a écrit :
>
>
> It's still in NEW[3]. I _think_ if you really want to enable tests now,
My very bad, I forgot to check the NEW queue
> you can do the needful. Since when the packages are accepted, jest would
> (hopefully) be accepted before redux, and hence
Thanks Nilesh for the help
>
> Node-jest has been packaged for Debian, you can go ahead with running
> tests needing jest.
>
Not yet, the package is in salsa [1] but the package isn't in unstable [2]
>
> Skip tests if they don't look compatible due to version constraints.
> Or try upgrading
Hello,
Le 20-05-11 à 01 h 14, Xavier a écrit :
>
> at least you should:
> * remove dependency to node-babel-preset-env
> * update homepage to https://redux.js.org/ (reported by `duck`)
> * Add "Testsuite: autopkgtest-pkg-nodejs" and remove
>debian/tests/control & debian/tests/require
>
Hello,
I've complete packaging node-redux thanks to node-babel7 [1], this
package has been asked to me because I've started to package it a while
ago and it's required for the Covid biohackathon by the Debian Med team.
Can a DD review the package and, if it's clean, upload it to the NEW queue?
Hello,
Le 20-04-26 à 21 h 22, Nilesh Patra a écrit :
>
> It has been packaged. Please check node-babel7[1]
>
> [1]: https://tracker.debian.org/pkg/node-babel7
My bad, thanks for the tip, I'll try it with node-babel7 then, thanks a
lot Nilesh!
/Nicolas
--
Pkg-javascript-devel mailing list
As I'm used to, right after sending an email to the list, I found a
beginning o an answer
Le 20-04-26 à 20 h 27, Nicolas Mora a écrit :
> SyntaxError: /opt/redux-4.0.1/src/applyMiddleware.js: Unexpected token
> (37:6)
> 35 |
> 36 | return {
>> 3
Hello,
I'm helping the Covid biohackathon by the Debian Med team with the
package node-redux [1], but I have a problem in the package builder. The
command 'rollup -c' exits with the following error.
root@docker-sid:/opt/redux-4.0.1 # rollup -c
src/index.js → lib/redux.js...
[!] (babel plugin)
Le 19-12-01 à 11 h 32, Xavier a écrit :
> Le 01/12/2019 à 16:02, Nicolas Mora a écrit :
>> I'm looking for a DD to review my 2 i18next* packages, and upload them
>> to NEW if they meet Debian quality level:
>>
>
> Not good:
> * remove *.min.js from import (o
Hello Team,
I'm looking for a DD to review my 2 i18next* packages, and upload them
to NEW if they meet Debian quality level:
- node-i18next-xhr-backend: simple i18next backend to be used in the
browser - https://salsa.debian.org/js-team/node-i18next-xhr-backend
-
Hello,
Le 19-11-17 à 16 h 20, Xavier a écrit :
>
> Take a look at my changes. I think you should provide a browserified
> file in /usr/share/javascript (in a separate package).
>
I added a separate package called libjs-i18next, but for some reason, if
I add a file
Le 19-11-17 à 08 h 09, Xavier a écrit :
>
> I fixed copyright years
>
Thanks!
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Hello team,
Le 19-11-16 à 18 h 00, Thorsten Alteholz a écrit :
>
> please also mention at least
> i18next-17.0.18/test/backward/v1.11.1.compat.js
> in your debian/copyright.
>
I've updated the file d/copyright in the salsa repository [1].
I've looked for other source files with a copyright
Le 19-10-27 à 15 h 37, Jonas Smedegaard a écrit :
Initial uploads to Debian, and a later upload that introduces a new
binary package, needs to visit the NEW queue, and that requires a full
upload with both source and binary.
Of course!
I didn't understand it wasn't uploaded to NEW at first
Le 19-10-27 à 15 h 18, Debian FTP Masters a écrit :
Source-only uploads to NEW are not allowed.
binary:node-qrcode-generator is NEW.
source:node-qrcode-generator is NEW.
I'm not sure I understand this rejection...
Can someone enlighten me?
/Nicolas
--
Pkg-javascript-devel mailing list
Hi,
Le 19-10-26 à 14 h 24, Xavier a écrit :
* debian-compat => 12
No problem, done
You use npm generated file (using fakeupstram instead of uscan
"searchmode=plain). This is bad here: qrcode_*.js are generated files.
Your lintian-overrides is not acceptable (it hides real problems).
In
Hello js team,
I need a sponsor to review the package node-qrcode-generator [1] and
push it to NEW if possible.
node-qrcode-generator is a javascript library which generates QR codes
as svg, images or tables to be inserted in the html DOM.
Thanks in advance
/Nicolas
[1] -
Le 19-10-25 à 08 h 21, Pirate Praveen a écrit :
The repositories I have problem with are:
https://salsa.debian.org/js-team/node-qrcode-generator
https://salsa.debian.org/js-team/node-i18next-xhr-backend
https://salsa.debian.org/js-team/node-i18next-browser-languagedetector
You have
Hello,
Le 19-10-16 à 20 h 10, Nicolas Mora a écrit :
The problem is I don't have the settings menu in the new repositories,
yet I have maintainer credentials in the team. So I can't create a
default branch for the repositories...
For some reason, the left sidebar doesn't have all the entries
I have a web application written in react built with weback during the
packaging.
If I build the package with the command "debuild -b -uc -us", the
packaging works.
But if I use sbuild to build the package, I have this weird error [1]:
Module parse failed: Unexpected token (38:22)
You may
Hello,
I have 3 new javascript packages almost ready to be uploaded to NEW so
later today I created the repositories in salsa.d.o/js-team/ since I
have the maintainer role.
Lately, when I tried to push the code to salsa, I got the following
error message:
remote: A default branch (e.g. master)
Hello,
As far as I can say, the package node-i18next [1] is ready to be pushed
in NEW but I'm not a DD yet so if I want to upload a new package I must
use mentors.d.n.
Except from the err below which seems not to be related to the package,
the rest of the QA tests are good: lintian and
Le 19-10-12 à 14 h 12, Pirate Praveen a écrit :
>
>
> Now autopkgtest is failing,
>
> autopkgtest [23:40:13]: test require: [---
> /usr/share/nodejs/i18next/i18next.js:124 _export(_export.S + _export.F *
> !_descriptors, 'Object', { defineProperty: _objectDp.f }); ^
Package: node-sourcemap-codec
Version: 1.4.5
Severity: normal
Tags: patch
The link usr/lib/nodejs/sourcemap-codec/index.js included in the package
points to the file usr/lib/nodejs/sourcemap-codec/sourcemap-codec.js
where it should link to
Package: node-rollup-plugin-commonjs
Version: 10.0.1
Severity: normal
Tags: patch
The link usr/lib/nodejs/rollup-plugin-commonjs/index.js included in the package
points to the file
usr/lib/nodejs/rollup-plugin-commonjs/rollup-plugin-commonjs.cjs.js
where it should link to
Hello,
In the package node-i18next-xhr-backend [1] I'm working on, I have this
error during the dh_test phase:
dh_auto_test --buildsystem=nodejs
/usr/bin/node -e require\(\"./.\"\)
internal/modules/cjs/loader.js:638
throw err;
^
Error: Cannot find module './_an-object'
at
Le 2019-10-09 13:02, Xavier a écrit :
No but it's a git-buildpackage bug. Commit the good file using:
$ pristine-tar commit ../node-i18next-17.0.18.tar.gz upstream/17.0.18
Then push to salsa (using `salsa push` which pushes all what is needed)
Got it, thanks.
Also, I could push force in
Le 2019-10-09 09:36, Pirate Praveen a écrit :
I guess one of the gitlab acl bugs/features as you have maintainer
access there, if you wish you can make master branch as unprotected
and force push. But I think lets leave it as it is.
I tried to find out how to change it but so far no luck,
Le 19-10-09 à 02 h 47, Pirate Praveen a écrit :
>
>
> Well, if you had not pushed to js-team, squashing makes sense as it require
> force push. It is not recommended to force push to team repo after it is
> published. In this case since we have not uploaded it, you can squash and
> force push
Hello,
Le 19-10-08 à 03 h 57, Pirate Praveen a écrit :
>
> * You can change pkg-js-tools dependency to (>= 0.8.13~) and then remove
> debian/install file.
>
done
> * You remove unnecessary comments like #override.. #export... in rules.
>
done
> * It is better to remove
Le 19-10-07 à 11 h 41, Pirate Praveen a écrit :
>> If I apply this change, I got a lot of errors like this:
>>
>> (!) Circular dependency:
>> ../../../usr/lib/nodejs/core-js/library/modules/_export.js ->
>> ../../../usr/lib/nodejs/core-js/library/modules/_hide.js ->
>>
Hi,
Le 19-10-07 à 04 h 02, Pirate Praveen a écrit :
>
> See
> https://salsa.debian.org/ruby-team/rails/blob/master/debian/patches/0002-disable-uglify-in-activestorage-rollup-config-js.patch
> to pass system paths to rollup-plugin-node-resolve instead of copying
> whole /usr/lib/nodejs.
>
> Pass
Hello JS team,
I was able to make a package for i18next here:
https://salsa.debian.org/babelouest-guest/node-i18next
Thanks to Pirate's feedback, I now build the bundle with rollup, but the
minified bundle is created with uglifyjs.terser
For some reason, lintian seems to be failing right now, I
Hello,
Le 19-10-06 à 09 h 21, Pirate Praveen a écrit :
>
>
> You can just patch out rollup-plugin-terser usage and use
> uglifyjs.terser command line.
>
Thanks for the tip, I'm trying to use rollup to build the package but so
far no luck: I removed rollup-plugin-terser from the
Hello,
I'm trying to package i18next for Debian [1]. The upstream dev use
rollup to build the i18next.js file with rollup-plugin-terser.
Unfortunately, rollup-plugin-terser isn't in Debian yet and requires a
lot of unpackaged dependencies.
I can build i18next.js with webpack, all the required
Hello,
Le 2018-11-26 03:01, Pirate Praveen a écrit :
You can try using node-neo-async instead for your package. It is
supposed to be a drop in replacement for node-async.
https://tracker.debian.org/pkg/node-neo-async
Thanks for pointing out node-neo-async!
I ran a manual test of the
Hello,
Le 18-11-25 à 13 h 56, Jonas Smedegaard a écrit :
> Did you check that none of the 6 reverse dependencies and none of the 67
> reverse build-dependencies break when doing such a major upgrade?
> Beware of packages with no or inferior or skipped testsuites: Quite
> likely manual
Hello Jonas,
In order to package node-istanbuljs, I made a new package for node-async
based on the original node-async package. The new features for the
package are:
* New upstream version
* Add node-babel-plugin-add-module-exports as dependency
* Bump Standards-Version to 4.2.1, no changes
Hello,
Wow, thanks a lot for the very detailed review!
Most of the feedbacks are fixed or are going to be, but I have a couple
of questions regarding some of them, and answers for your questions.
Le 2018-11-21 04:47, Per Andersson a écrit :
node-async:
* In the commit
Hello again,
Le 2018-11-19 13:14, Nicolas Mora a écrit :
In order to create the Debian package redux, I need the following
unresolved dependencies:
redux
├─ loose-envify (^1.4.0) node-loose-envify
(1.3.1+dfsg1-1)
└─ js-tokens (^3.0.0 || ^4.0.0) node
Hello,
Sorry if I ask a question that was already discussed before, I'm kinda
new in Debian javascript team.
In order to create the Debian package redux, I need the following
unresolved dependencies:
redux
├─ loose-envify (^1.4.0) node-loose-envify
(1.3.1+dfsg1-1)
Le 2018-11-14 05:43, Pirate Praveen a écrit :
You can chmod +x it in override_dh_fixperms target in rules.
Yes, fixed it.
Also, I just realized that the script jest/bin/jest.js contains this
simple code:
require('jest-cli/bin/jest');
So I think we should remove the file debian/links and
Hello,
Le 2018-11-11 22:08, Pirate Praveen a écrit :
I don't think grouping unrelated packages is a good idea. If there is
a circular dependency or related projects, then its OK. It is making
things unnecessarily complex.
I don't think either that making a group package for such small
Hello,
I'm working on packaging Taliesin, an audio streaming server with a
front-end written in react [1].
To build the front-end, I need some new node packages. I've already
starting packaging some of them, but I prefer asking the javascript team
about it first, to make sure I'm making it
74 matches
Mail list logo
