[Pkg-javascript-devel] node-assert 2.0.0+~cs2.4.2-1 MIGRATED to testing
FYI: The status of the node-assert source package in Debian's testing distribution has changed. Previous version: 2.0.0-1 Current version: 2.0.0+~cs2.4.2-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-morgan 1.10.0-3 MIGRATED to testing
FYI: The status of the node-morgan source package in Debian's testing distribution has changed. Previous version: 1.10.0-2 Current version: 1.10.0-3 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-browserslist 4.20.2+~cs5.1.3-1 MIGRATED to testing
FYI: The status of the node-browserslist source package in Debian's testing distribution has changed. Previous version: 4.20.0+~cs5.1.3-1 Current version: 4.20.2+~cs5.1.3-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-caniuse-lite 1.0.30001319+dfsg+~1.0.1-1 MIGRATED to testing
FYI: The status of the node-caniuse-lite source package in Debian's testing distribution has changed. Previous version: 1.0.30001314+dfsg+~1.0.1-1 Current version: 1.0.30001319+dfsg+~1.0.1-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-caniuse-db 1.0.30001319-1 MIGRATED to testing
FYI: The status of the node-caniuse-db source package in Debian's testing distribution has changed. Previous version: 1.0.30001314-1 Current version: 1.0.30001319-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1008290: Unable to install node-babel7 because the same file is present in another binary.
Package: node-babel7 Version: 7.17.6+~cs214.260.190-1 Severity: normal Dear Maintainer, Got the following while upgrading today - Unpacking node-babel7 (7.17.8+~cs214.260.191-2) over (7.17.6+~cs214.260.190-1) ... dpkg: error processing archive /tmp/apt-dpkg-install-dogkWA/60-node-babel7_7.17.8+~cs214.260.191-2_all.deb (--unpack): trying to overwrite '/usr/share/doc/node-babel-types/copyright', which is also in package node-babel-types 6.26.0+repack-4 $ aptitude search node-babel7 Bu node-babel7 - Babel command line i A node-babel7-runtime - Babel modular runtime helpers p node-babel7-standalone - Standalone build of Babel for use in browsers and other non-No Please fix the same, thank you. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing'), (500, 'testing-debug'), (100, 'unstable-debug'), (100, 'experimental'), (100, 'unstable'), (50, 'experimental-debug') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages node-babel7 depends on: ii node-ampproject-remapping 2.1.2+~cs4.7.20-1 ii node-babel-plugin-add-module-exports 1.0.4+dfsg1~cs5.8.0-3 ii node-babel7-runtime 7.17.8+~cs214.260.191-2 ii node-browserslist 4.20.0+~cs5.1.3-1 ii node-chalk4.1.2-1 ii node-clone-deep 4.0.1-3 ii node-commander9.1.0-1 ii node-convert-source-map 1.8.0+~1.5.2-1 ii node-core-js 3.8.2-3 ii node-debug4.3.3+~cs4.1.7-1 ii node-esutils 2.0.3-3 ii node-find-cache-dir 3.3.2+~3.2.1-1 ii node-fs-readdir-recursive 1.1.0-2 ii node-glob 7.2.1+~cs7.6.15-1 ii node-globals 13.12.1-1 ii node-js-tokens7.0.0-1 ii node-jsesc3.0.2+~3.0.1-1 ii node-json52.2.0+dfsg-1 ii node-lodash 4.17.21+dfsg+~cs8.31.198.20210220-5 ii node-lodash-packages 4.17.21+dfsg+~cs8.31.198.20210220-5 ii node-make-dir 3.1.0-2 ii node-quick-lru5.1.1-1 ii node-regenerator-transform0.14.5-4 ii node-regexpu-core 4.8.0-4 ii node-resolve 1.20.0+~cs5.27.9-1 ii node-semver 7.3.5+~7.3.8-1 ii node-slash3.0.0-2 ii node-source-map 0.7.0++dfsg2+really.0.6.1-9 ii node-source-map-support 0.5.21+ds+~0.5.4-1 ii node-to-fast-properties 3.0.1-2 ii node-v8flags 3.2.0-3 ii nodejs12.22.10~dfsg-2 node-babel7 recommends no packages. node-babel7 suggests no packages. -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 https://creativecommons.org/licenses/by-nc/3.0/ https://flossexperiences.wordpress.com E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1008287: Failed install of npm backports package
Package: npm Version: 8.3.1~ds-1~bpo11+1 When I install the npm backports package, I get an error: root@pad:/etc/apt# apt install -t bullseye-backports npm Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: npm : Depends: nodejs:any (>= 10) but it is not installable Recommends: node-tap but it is not going to be installed E: Unable to correct problems, you have held broken packages. Yet the nodejs package is installed with good version: root@pad:/etc/apt# dpkg -l nodejs apt ii apt2.2.4 amd64commandline package manager ii nodejs 12.22.5~dfsg-2~11u1 amd64evented I/O for V8 javascript - runtime executable root@pad:/etc/apt# grep "^deb" sources.list deb http://deb.debian.org/debian/ bullseye main deb-src http://deb.debian.org/debian/ bullseye main deb http://security.debian.org/debian-security bullseye-security main deb-src http://security.debian.org/debian-security bullseye-security main deb http://deb.debian.org/debian/ bullseye-updates main deb-src http://deb.debian.org/debian/ bullseye-updates main deb http://deb.debian.org/debian bullseye-backports main I am using Debian Stable up to date: root@pad:/etc/apt# cat /etc/debian_version 11.2 root@pad:/etc/apt# uname -a Linux pad 5.10.0-12-amd64 #1 SMP Debian 5.10.103-1 (2022-03-07) x86_64 GNU/Linux With all my encouragement, Cpm. -- Christian Pierre MOMON Tél. +33 (0)6 26 72 40 04 OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] New JS team mailing list?
Quoting Nilesh Patra (2022-03-25 21:54:13) > On 3/26/22 12:56 AM, Jonas Smedegaard wrote: > > Ok. I am then still in the dark about your point of suggesting me > > in particular for moving this forward. > > I was (a few mails earlier), hoping that you might administer the new > list, if we happen to get it. > (And no, this does not mean that you'd engage in filtering spam, > although it only takes a couple of clicks usually) Makes sense. Thanks for clarifying. > > Not sure why you cc'ed me that followup to the bugreport, > > Well, since we just had 'a thread of conversation' about it, and you > pointed me to a HOWTO, I thought I'd keep you in loop(?). No motive > here other than that. Makes sense as well now. Thanks! > I think at this point all discussion is done. So let's end the > conversation here, shall we. Agreed. :-) - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] New JS team mailing list?
On 3/26/22 12:56 AM, Jonas Smedegaard wrote: No, not SPF, I mean DKIM[1] it is not a policy framework, but rather a signature (not GPG) on your mail validating it to be sent from your domain. Unlike SPF, it is more robust by design. You need not sell DKIM to me. I believe issue for SPF and DKIM is same: Debian administrators administrate only services tied to the debian.org domain (and _delegation_ of services tied to debian.net). Looks like I misunderstood you earlier. Fair enough. If you want to debunk that point of mine as well, [...] I do not want to debunk your point. Sure, that wasn't the point of my mail either :) Ok. I am then still in the dark about your point of suggesting me in particular for moving this forward. I was (a few mails earlier), hoping that you might administer the new list, if we happen to get it. (And no, this does not mean that you'd engage in filtering spam, although it only takes a couple of clicks usually) I just replied to the bug with the information that listmasters need, with you in CC. Will see if it gets processed. Not sure why you cc'ed me that followup to the bugreport, Well, since we just had 'a thread of conversation' about it, and you pointed me to a HOWTO, I thought I'd keep you in loop(?). No motive here other than that. but am not in the mood for guessing as to your motives, so just informing you that again I am clueless. I think at this point all discussion is done. So let's end the conversation here, shall we. OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] New JS team mailing list?
Quoting Nilesh Patra (2022-03-25 19:11:32) > On 3/25/22 10:58 PM, Jonas Smedegaard wrote: > >>> I recommend that you report that issue to the mailinglist admins: > >>> The footer of https://alioth-lists.debian.net/ lists > >>> https://salsa.debian.org/alioth-lists-team/support as their > >>> preferred place to report issues. > >> > >> I think it is already known for quite sometime. IIRC bugs.d.o and > >> alioth lists use similar mechanisms for mails. > > > > Ah, you mean the SPF issue, affecting domains outside debian.org. > > > > Yes, I am aware of that issue, and there is no need to report it, as > > there is nothing really to be done about it: It works as intended by > > design (and design of SPF is limited). > > No, not SPF, I mean DKIM[1] > it is not a policy framework, but rather a signature (not GPG) on your > mail validating it to be sent from your domain. > Unlike SPF, it is more robust by design. You need not sell DKIM to me. I believe issue for SPF and DKIM is same: Debian administrators administrate only services tied to the debian.org domain (and _delegation_ of services tied to debian.net). If you want to debunk that point of mine as well, then I recommend you do it at the bugreport you referenced earlier, because I am not a postmaster nor a listmaster in Debian and convincing me that some mechanism will work great is not gonna change anything. > >> Since you moderate this list, I thought it would be nice if you > >> would be nice if you could also moderate lists.d.o, as current > >> maintainer it would be easier to collaborate with list admins (just > >> a thought, not a strong opinion) > > > > I don't think I will engage in screening for spam at lists.d.o. > > Sure, that wasn't the point of my mail either :) Ok. I am then still in the dark about your point of suggesting me in particular for moving this forward. Maybe you have noticed by now that I have a hard time understanding what it is you are trying to point out. In some cases I only point out my failure but at other times I try guess. Possibly that is me being daft, but regardless it is helpful if you try clarify, and it certainly isn't helpful to simply inform me that I got it wrong. > > I don't see at https://www.debian.org/MailingLists/HOWTO_start_list > > that my status as DD should have any special relevancy for creating > > a new list for our team. > > What is needed is clear and accurate facts passed to listmasters > > when requesting - as documented very detailed. > > I am a DD myself. > So should there be such reqs, I possibly should be able to handle > that. > I just replied to the bug with the information that listmasters need, > with you in CC. > > Will see if it gets processed. Not sure why you cc'ed me that followup to the bugreport, but am not in the mood for guessing as to your motives, so just informing you that again I am clueless. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] nodejs_16.14.2+dfsg-1_ppc64el.changes ACCEPTED into experimental, experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 23 Mar 2022 15:34:41 +0100 Source: nodejs Binary: libnode-dev libnode93 libnode93-dbgsym nodejs nodejs-dbgsym nodejs-doc Architecture: source ppc64el all Version: 16.14.2+dfsg-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Jérémy Lal Description: libnode-dev - evented I/O for V8 javascript (development files) libnode93 - evented I/O for V8 javascript - runtime library nodejs - evented I/O for V8 javascript - runtime executable nodejs-doc - API documentation for Node.js, the javascript platform Changes: nodejs (16.14.2+dfsg-1) experimental; urgency=medium . * New upstream version 16.14.2+dfsg * Change ~dfsg to +dfsg * copyright: + dfsg-exclude corepack - missing source + remove tools/lint-md.mjs * rules: do not install corepack * B-D libuv >= 1.43 Checksums-Sha1: 112933b7b984650ffbd4df738c0271f1b8177ab8 4145 nodejs_16.14.2+dfsg-1.dsc 1562de95f380e5b89f80bcb54331a6d63b0abe84 897488 nodejs_16.14.2+dfsg.orig-node-acorn.tar.xz d35550578589e5a0ee976cd571db0c9b3608c50c 235200 nodejs_16.14.2+dfsg.orig-types-node.tar.xz e99439faecbb7b9ca55fa72c20c955f4fec2837f 21772776 nodejs_16.14.2+dfsg.orig.tar.xz aee246d94d7c1295589804bb1b79b21b680a181e 155256 nodejs_16.14.2+dfsg-1.debian.tar.xz a89eb24157d808211b2646e5b045dd0b914d5575 460028 libnode-dev_16.14.2+dfsg-1_ppc64el.deb c47925ea39e0ac4bffd9991a62b43c0697e2e2f9 809702672 libnode93-dbgsym_16.14.2+dfsg-1_ppc64el.deb bb217064b1c33522a749a6a3f50fb33476c9f3cc 10146148 libnode93_16.14.2+dfsg-1_ppc64el.deb 809b86ea61091e0b39cc11e3bce119bc467c6bad 143580 nodejs-dbgsym_16.14.2+dfsg-1_ppc64el.deb 48dc9527579cc38dc439bd69d559fb75483e04f4 2984040 nodejs-doc_16.14.2+dfsg-1_all.deb 62126e3d52bb34b192448e4d6811fb5860b7cd23 11049 nodejs_16.14.2+dfsg-1_ppc64el.buildinfo 48e2b70543d23988352dc5c4e372c3345dbc65af 298108 nodejs_16.14.2+dfsg-1_ppc64el.deb Checksums-Sha256: 4afc5f7d6b5f6fe8c1f2bf48bea7b5facb8cd60aaf2f38f498f32d2fe9900262 4145 nodejs_16.14.2+dfsg-1.dsc 7ed9981927513a2ccac1787405dcd05d844aa7c2c8d9d32ad2ff85322376 897488 nodejs_16.14.2+dfsg.orig-node-acorn.tar.xz 8bf4fdc5807720e4c610a90bbad4140e5adaac4fff762d2836c93706d790c159 235200 nodejs_16.14.2+dfsg.orig-types-node.tar.xz 0909d56b80d408f7a9a02d4c8f30356ba5cd1202533b48c5a4644c909e9b050e 21772776 nodejs_16.14.2+dfsg.orig.tar.xz 8dfe46635c6ef653ca357284659cfa9e5594a01954b6281298a75bd3d49eb40b 155256 nodejs_16.14.2+dfsg-1.debian.tar.xz 8bb4f3ce35e25fc0595af7aab00e03682342d29a175ca00f8fd7c539f2b20c3b 460028 libnode-dev_16.14.2+dfsg-1_ppc64el.deb 46472e4b2fed358c76f63a1f8a38fa37a2e9de9698e030dbed49e014b114f1a5 809702672 libnode93-dbgsym_16.14.2+dfsg-1_ppc64el.deb cdd572e5ec4c1e34a837dcbce00f541707128154ddc35fed4b096d39d98a36cd 10146148 libnode93_16.14.2+dfsg-1_ppc64el.deb 31477bc71de241bc3f411b8454dfe8da81a534b4253665377497c65f54099b2c 143580 nodejs-dbgsym_16.14.2+dfsg-1_ppc64el.deb 2241e6030c57f173a54a07d3eb361f4cb0f4e3638083174a85a2b979c2490a6f 2984040 nodejs-doc_16.14.2+dfsg-1_all.deb 9b00ab6016eedd6062f19b23d03767c315d73a1a03b3f8905676429219ddf08f 11049 nodejs_16.14.2+dfsg-1_ppc64el.buildinfo 8d398a7428013c90da5e96dc6cb60c6002266bd9a236103ec0552ea586065e2f 298108 nodejs_16.14.2+dfsg-1_ppc64el.deb Files: 78a7f3905a5c88144fa34019003172b3 4145 javascript optional nodejs_16.14.2+dfsg-1.dsc 4a6332f8a9839cf1ca1bb5bfa4b9f6e5 897488 javascript optional nodejs_16.14.2+dfsg.orig-node-acorn.tar.xz d3a41936133f0dbc2200fab43cfc604c 235200 javascript optional nodejs_16.14.2+dfsg.orig-types-node.tar.xz 8b1c2bfaafc7e08ea5d954103d75aaa7 21772776 javascript optional nodejs_16.14.2+dfsg.orig.tar.xz 47f04d6b1b65a8cf5921b50f72d72e76 155256 javascript optional nodejs_16.14.2+dfsg-1.debian.tar.xz 2a8f83797b80627a24dd591b618601d2 460028 libdevel optional libnode-dev_16.14.2+dfsg-1_ppc64el.deb 2433965455927a3ca624ed076185ff08 809702672 debug optional libnode93-dbgsym_16.14.2+dfsg-1_ppc64el.deb 1319d6f8fd29a2a73d3b352541b31625 10146148 libs optional libnode93_16.14.2+dfsg-1_ppc64el.deb bc02f7bb585c434f9a8ceac9f82ea32f 143580 debug optional nodejs-dbgsym_16.14.2+dfsg-1_ppc64el.deb 8ecf926425abc4538723713211d6 2984040 doc optional nodejs-doc_16.14.2+dfsg-1_all.deb 1ca9cfd8eeffad8a68a12bb3c778db62 11049 javascript optional nodejs_16.14.2+dfsg-1_ppc64el.buildinfo 5703ec3846a4223089a2e6f43b9686aa 298108 javascript optional nodejs_16.14.2+dfsg-1_ppc64el.deb -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEA8Tnq7iA9SQwbkgVZhHAXt0583QFAmI7fMISHGthcG91ZXJA bWVsaXgub3JnAAoJEGYRwF7dOfN0wWYP/1qo2nWa1a8PvVM8HbPNe3eXjKLyaYpo h1C/llFHSRwbPb8m+f5TW6z/SbnI2UWNAcdbcvGt9RsF7lHR4F2bH1Z2/4Ipx5ZP PNmivV15IRRx4wHfBKgtHqNxdAWWplvG0/Os2HV/gMekrFea5ZwDUdGlGyGZs11P 3J8LxNkbx6RI9tMeIJ7lpaLhzZqawxEo9E2ZlOHPSjFcbkTgDHSfdY6ivuWD7FsE AjkdtvC9ZH/byp42RIcA4LFfJem//pHCYDmwULtxnUxJMmpV1w2vt6s5QQl5ffka
Re: [Pkg-javascript-devel] New JS team mailing list?
On 3/25/22 10:58 PM, Jonas Smedegaard wrote: I recommend that you report that issue to the mailinglist admins: The footer of https://alioth-lists.debian.net/ lists https://salsa.debian.org/alioth-lists-team/support as their preferred place to report issues. I think it is already known for quite sometime. IIRC bugs.d.o and alioth lists use similar mechanisms for mails. Ah, you mean the SPF issue, affecting domains outside debian.org. Yes, I am aware of that issue, and there is no need to report it, as there is nothing really to be done about it: It works as intended by design (and design of SPF is limited). No, not SPF, I mean DKIM[1] it is not a policy framework, but rather a signature (not GPG) on your mail validating it to be sent from your domain. Unlike SPF, it is more robust by design. [1]: https://en.wikipedia.org/wiki/DomainKeys_Identified_Mail Since you moderate this list, I thought it would be nice if you would be nice if you could also moderate lists.d.o, as current maintainer it would be easier to collaborate with list admins (just a thought, not a strong opinion) I don't think I will engage in screening for spam at lists.d.o. Sure, that wasn't the point of my mail either :) I don't see at https://www.debian.org/MailingLists/HOWTO_start_list that my status as DD should have any special relevancy for creating a new list for our team. What is needed is clear and accurate facts passed to listmasters when requesting - as documented very detailed. I am a DD myself. So should there be such reqs, I possibly should be able to handle that. I just replied to the bug with the information that listmasters need, with you in CC. Will see if it gets processed. Regards, Nilesh OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] New JS team mailing list?
Quoting Nilesh Patra (2022-03-25 17:55:33) > On 3/25/22 9:09 PM, Jonas Smedegaard wrote: > >> I actively want us to change. As the signal to noise ratio is > >> lowered due to tons of processing emails (and it is not only -my- > >> opinion) > > > > I guess that by "processing emails" you mean those emails sent from > > Debian infrastructure to the Maintainer email address. > > yes, things like "Processing of xxx_sourceonly.changes" Or bug > processing mails from BTS (like processing tags) > > > Do you mean that you want an _additional_ mailinglist which is > > _separate_ from the address used in package Maintainer field? > > > E.g. a -discuss list? > > Yes, as an example we have > "debian-med-packag...@alioth-lists.debian.net" as maintainer address, > and "debian-...@lists.debian.org" for discussions. > > Several teams have similar schemes. > Those without a alioth list use tracker+@debian.org as maint > address so as to reduce noise. Hope that helps clarify what I meant to > say. Yes, understand you now. Thanks for your patience. > >> Also, alioth lists (like the current one) break DKIM signatures and > >> is a sort of a bummer since I see valid mails get to my spam folder > >> sometimes. > > > > I was unaware that the Alioth list was broken. > > > > I recommend that you report that issue to the mailinglist admins: > > The footer of https://alioth-lists.debian.net/ lists > > https://salsa.debian.org/alioth-lists-team/support as their > > preferred place to report issues. > > I think it is already known for quite sometime. IIRC bugs.d.o and > alioth lists use similar mechanisms for mails. Ah, you mean the SPF issue, affecting domains outside debian.org. Yes, I am aware of that issue, and there is no need to report it, as there is nothing really to be done about it: It works as intended by design (and design of SPF is limited). > >> But please note that there is already a bug for lists.d.o for a JS > >> team mailing list here[1] it has been a long time since, though. > > > > Ah, right. I vaguely rmember us discussing mailinglist structure in the > > past, but I do not remember what was the conclusion of that discussion, > > and it is not clear to me from that bugreport either. > > Thread starts from here[3] > Conclusion was to start with it if no-one objected; and IIRC, no-one raised > any objections. > > [3]: > https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2019-December/037619.html Thanks! > >> Since you moderate this list, it would make a lot of sense if you > >> could follow up there and do the needful with respect to the > >> procedure. > >> > >> [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946979 > > > > Sorry, I fail to see how my role as moderator for the current Alioth > > list makes me any special regarding setup of additional lists - at > > alioth-lists.d.n or at lists.d.o. > > Since you moderate this list, I thought it would be nice if you would > be nice if you could also moderate lists.d.o, as current maintainer it > would be easier to collaborate with list admins (just a thought, not a > strong opinion) I am not listmaster anywhere related to Debian (only on systems I host myself). I am moderator for 13 lists at alioth-lists.d.n which is efficient for me since they all use mailman where I can comfortably do screening with the command-line tool listadmin. Spam processing for lists.d.o is radically different, as documented at https://wiki.debian.org/Teams/ListMaster/ListArchiveSpam and (more brief but official) at https://lists.debian.org/archive-spam-removals/review/ I don't think I will engage in screening for spam at lists.d.o. I don't see at https://www.debian.org/MailingLists/HOWTO_start_list that my status as DD should have any special relevancy for creating a new list for our team. What is needed is clear and accurate facts passed to listmasters when requesting - as documented very detailed. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] New JS team mailing list?
On 3/25/22 9:09 PM, Jonas Smedegaard wrote: I actively want us to change. As the signal to noise ratio is lowered due to tons of processing emails (and it is not only -my- opinion) I guess that by "processing emails" you mean those emails sent from Debian infrastructure to the Maintainer email address. yes, things like "Processing of xxx_sourceonly.changes" Or bug processing mails from BTS (like processing tags) Do you mean that you want an _additional_ mailinglist which is _separate_ from the address used in package Maintainer field? > E.g. a -discuss list? Yes, as an example we have "debian-med-packag...@alioth-lists.debian.net" as maintainer address, and "debian-...@lists.debian.org" for discussions. Several teams have similar schemes. Those without a alioth list use tracker+@debian.org as maint address so as to reduce noise. Hope that helps clarify what I meant to say. Also, alioth lists (like the current one) break DKIM signatures and is a sort of a bummer since I see valid mails get to my spam folder sometimes. I was unaware that the Alioth list was broken. I recommend that you report that issue to the mailinglist admins: The footer of https://alioth-lists.debian.net/ lists https://salsa.debian.org/alioth-lists-team/support as their preferred place to report issues. I think it is already known for quite sometime. IIRC bugs.d.o and alioth lists use similar mechanisms for mails. bugs.d.o breaking DKIM is well known. Don't exactly remember where alioth lists thingy was, but a quick search led me to these[1,2] Do consider taking a look. [1]: https://lists.debian.org/debian-devel/2022/03/msg00057.html [2]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830865#40 But please note that there is already a bug for lists.d.o for a JS team mailing list here[1] it has been a long time since, though. Ah, right. I vaguely rmember us discussing mailinglist structure in the past, but I do not remember what was the conclusion of that discussion, and it is not clear to me from that bugreport either. Thread starts from here[3] Conclusion was to start with it if no-one objected; and IIRC, no-one raised any objections. [3]: https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2019-December/037619.html Since you moderate this list, it would make a lot of sense if you could follow up there and do the needful with respect to the procedure. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946979 Sorry, I fail to see how my role as moderator for the current Alioth list makes me any special regarding setup of additional lists - at alioth-lists.d.n or at lists.d.o. Since you moderate this list, I thought it would be nice if you would be nice if you could also moderate lists.d.o, as current maintainer it would be easier to collaborate with list admins (just a thought, not a strong opinion) I am open to changes to mailinglists, for the record. - Thumbs up - Regards, Nilesh OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] New JS team mailing list?
On Fri, Mar 25, 2022 at 4:39 PM Jonas Smedegaard wrote: > Quoting Nilesh Patra (2022-03-25 15:59:51) > > On 3/25/22 8:09 PM, Jonas Smedegaard wrote: > > > Everyone *are* allowed to post, we actively *chose* sensoring, and I > > > *volunteer* to screen it to avoid spam on the list. > > > > ACK. > > > > > If you disagree and think that we should permit spam on our lists, > > > then that is a different topic than that of my post, and it is not > > > entirely clear to me if you simply misunderstood me or you actively > > > want us to change. > > > > I actively want us to change. As the signal to noise ratio is lowered > > due to tons of processing emails (and it is not only -my- opinion) > > Reduction of "processing emails" is unrelated to sensoring (if I > understand you correctly). > > I guess that by "processing emails" you mean those emails sent from > Debian infrastructure to the Maintainer email address. > > Do you mean that you want an _additional_ mailinglist which is > _separate_ from the address used in package Maintainer field? > > E.g. a -discuss list? > Truely #946979 does show some sort of confusion between the current pkg-javascript-devel@alioth-lists.debian.net which is our Maintainer Team list, and which doesn't need to be imported into the new debian...@lists.debian.org which would be used only for discussion. The last reply from Alexander (while vaguely not friendly, but whatever), shows that you need to clearly express this: - nothing to do with pkg-javascript-devel@alioth-lists.debian.net - create debian...@lists.debian.org, and give him the info he asked Jérémy -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Updating node-typescript to 4.6.3
Le vendredi 25 mars 2022 à 17:34 +0100, Yadd a écrit : > On 25/03/2022 17:33, Yadd wrote: > > > > We're far enough away from Bookworm's release to allow us some > > build-only FTBFS ;-) > > But please wait for nodejs 14 migration before uploading this to > unstable Good point! J.Puydt -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-arr-exclude_2.0.0-1_sourceonly.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 17:08:23 +0100 Source: node-arr-exclude Architecture: source Version: 2.0.0-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Changes: node-arr-exclude (2.0.0-1) experimental; urgency=medium . * Team upload * New upstream version 2.0.0 * Update test Checksums-Sha1: fbebd06a034a3a523a7b8396696f8328e44fd8e8 2086 node-arr-exclude_2.0.0-1.dsc 341e0d69f12fd927f1927996dfe71ffad6cd6679 2214 node-arr-exclude_2.0.0.orig.tar.gz 8bb8ee143e4b6f991b94c95439adcc3c378497b4 2868 node-arr-exclude_2.0.0-1.debian.tar.xz Checksums-Sha256: 48f2a662e04492858b6dcdfb5d50e71a74fb6c3ff045252e8b83be68bafc4946 2086 node-arr-exclude_2.0.0-1.dsc 2b12dc73b682b5c5b10336a4129b9090b3a2b948c6130a35124d45f2c1d86c0e 2214 node-arr-exclude_2.0.0.orig.tar.gz d80b258481d763736a44f65ba4a8a97c9be6f86b8fd550bab29525fd8ca99ef6 2868 node-arr-exclude_2.0.0-1.debian.tar.xz Files: e1757f5a2ffd6a4e2d20ea964dd29fbd 2086 javascript optional node-arr-exclude_2.0.0-1.dsc a6284048a8c74f45020d7e77708eb01c 2214 javascript optional node-arr-exclude_2.0.0.orig.tar.gz 0b937dbe7e3c4b0d135c131ce15c24b4 2868 javascript optional node-arr-exclude_2.0.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI96U0ACgkQ9tdMp8mZ 7umA0w//ZBJzonsRcYu+BM/2P2Iy3gJW3aehLT8pFHTH9SJxNKdjPHtmzI+XqOxi erZpQCnldoEdSYkP0w4gpjRR7tGHweINKbrXFhjgnPnDNv8ODH1LN/1Ysdly1v3Y f7WgFxFcKAUZWUxdpXxHjzgeQt5BhEpQ0bZnz5WZuwjrGAnmX9GVr5VgAVRHQe91 MHyq7870jmYAdAxhiMTukhENX5Q83o3q1qFu75xh0ATSUItMx0So/JRbdSqv1GQR pHsr0XBlkcq+YLbgth/2rVaZIDGJuQQ17ud2yVF7cS60TwQyr6Wib2Uy1P1Hgn1v GZZXNWvtyx4hJc937trDk0JdfFgM3gmxXTJIfutypkL+SuG4vsOztpGfvORkXaFe 5ss8IqgyxjcS5z5wKq2OZDSSsumRIAV/fq+jem0FrVWPwsUfBFHM/X982uY3zhwL hVU6dimoOp0IEJ183Y8RXG2GhWePgPHF+r6S3L1TgzeIDFGhgF5gtgV1HpteN2YP kSMyAqiW7xahZ/zmqnIbfkXT8IasJHAClS5DowlsN4eVDQDC+Kmi2SJbVE/wB4E5 +PU6M/EXtY1GvG/IFBs2aS8f0zU8mHnh8ne1Q24P0aNy3sydkpuevpnSorG2wSed csJwvITa6Bmcf/OTuGoJv7AN6T+VeDafny/coIvcYEFTvNkZvDk= =HZ0V -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Updating node-typescript to 4.6.3
On 25/03/2022 17:33, Yadd wrote: On 25/03/2022 16:51, julien.pu...@gmail.com wrote: Hi, I prepared the package and uploaded it to experimental: I know by experience that an update from 4.5.4 to 4.6.3 has a very high chance to break things. If I'm mistaken and it doesn't bring pain all around, I'll upload to unstable in two weeks. If I'm right, well, here's a nice thread start to notify and discuss. Cheers, J.Puydt Hi Julien, We're far enough away from Bookworm's release to allow us some build-only FTBFS ;-) Cheers, Yadd But please wait for nodejs 14 migration before uploading this to unstable -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Updating node-typescript to 4.6.3
On 25/03/2022 16:51, julien.pu...@gmail.com wrote: Hi, I prepared the package and uploaded it to experimental: I know by experience that an update from 4.5.4 to 4.6.3 has a very high chance to break things. If I'm mistaken and it doesn't bring pain all around, I'll upload to unstable in two weeks. If I'm right, well, here's a nice thread start to notify and discuss. Cheers, J.Puydt Hi Julien, We're far enough away from Bookworm's release to allow us some build-only FTBFS ;-) Cheers, Yadd -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-arr-exclude_2.0.0-1_sourceonly.changes
node-arr-exclude_2.0.0-1_sourceonly.changes uploaded successfully to localhost along with the files: node-arr-exclude_2.0.0-1.dsc node-arr-exclude_2.0.0.orig.tar.gz node-arr-exclude_2.0.0-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Updating node-typescript to 4.6.3
Hi, I prepared the package and uploaded it to experimental: I know by experience that an update from 4.5.4 to 4.6.3 has a very high chance to break things. If I'm mistaken and it doesn't bring pain all around, I'll upload to unstable in two weeks. If I'm right, well, here's a nice thread start to notify and discuss. Cheers, J.Puydt -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1006862: marked as done (the tsserver binary is missing)
Your message dated Fri, 25 Mar 2022 15:49:48 + with message-id and subject line Bug#1006862: fixed in node-typescript 4.6.3+ds1-1 has caused the Debian Bug report #1006862, regarding the tsserver binary is missing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1006862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-typescript Version: 4.5.4+ds1-1 Hi, according to the source code: https://salsa.debian.org/js-team/node-typescript/-/blob/master/bin/ this package should include two binaries when it gets installed on any Debian system, however it only brings the tsc program to the system $PATH and not the tsserver. Here is the relevant output: $ dpkg -L node-typescript . . . /usr/share/nodejs/typescript/bin /usr/share/nodejs/typescript/bin/tsc /usr/share/nodejs/typescript/lib/tsc.js /usr/share/nodejs/typescript/lib/tsserver.js /usr/bin/tsc . . . This program is necessary for IDEs and plugins that provide autocompletion for javascript files such as the Dense Analysis (also known as ALE) for Vim and Vscode. For more details see the contents of: /usr/share/vim-ale/ale_linters/javascript/tsserver.vim from the package "vim-ale" This kind of plugin always look for the executables in the $PATH by default and then in the project's local directory. If one binary is missing (like tsserver in this case) then the LSP functionality might not work as expected. Please include the tsserver binary in the final .deb package. Cheers. --- End Message --- --- Begin Message --- Source: node-typescript Source-Version: 4.6.3+ds1-1 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of node-typescript, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1006...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated node-typescript package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 16:09:37 +0100 Source: node-typescript Architecture: source Version: 4.6.3+ds1-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Julien Puydt Closes: 1006862 Changes: node-typescript (4.6.3+ds1-1) experimental; urgency=medium . [ lintian-brush ] * Use secure URI in Homepage field. * Set upstream metadata fields: Security-Contact. . [ Yadd ] * Update nodejs dependency to nodejs:any * Add patch to ignore debian and quilt directories * Use dh-sequence-nodejs auto install . [ Julien Puydt ] * New upstream release. * Ship the tsserver binary (Closes: #1006862). * Refresh patch. Checksums-Sha1: 076b3620f70a332845ef8d87a734f6ba1d0c0f82 2112 node-typescript_4.6.3+ds1-1.dsc 2f2381c089f86cf4a7ee1c8668c2e62f61a2dc1a 21363980 node-typescript_4.6.3+ds1.orig.tar.xz ea67dbab1083bc5da0eca5639af03f39fadd649a 6944 node-typescript_4.6.3+ds1-1.debian.tar.xz 2c4480e893b10ae456c402163e823b0fdb1e3363 7550 node-typescript_4.6.3+ds1-1_source.buildinfo Checksums-Sha256: a534b6e1042cac68e87eef773701295f4f45b72dd6bd92ebdec48f793e2b9a8e 2112 node-typescript_4.6.3+ds1-1.dsc df4f993391afee31d826f296caf3db6faa70795b06aab26c7cb2c0e6f892fa9a 21363980 node-typescript_4.6.3+ds1.orig.tar.xz aa1264807b1913392f6504d29d368a384fd4e63178fbe296f116f2f3fc18488e 6944 node-typescript_4.6.3+ds1-1.debian.tar.xz a2c5b55e9998b081f8f9d17b7c13a4db0505ce325bb00f7b998fef720706be31 7550 node-typescript_4.6.3+ds1-1_source.buildinfo Files: 8a6c6c3f92aae7ea6c36fc7f9f8bae50 2112 javascript optional node-typescript_4.6.3+ds1-1.dsc 9158f037c5291820bb21875886a43474 21363980 javascript optional node-typescript_4.6.3+ds1.orig.tar.xz 1cfbc963572843cde3aeca55bb6489ad 6944 javascript optional node-typescript_4.6.3+ds1-1.debian.tar.xz bfd6bc443809c6afcd047a4d1936916f 7550 javascript optional node-typescript_4.6.3+ds1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmI93m4SHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRsNsP/Atw9wOpa7BFH+diOYRutjOlK57P0fXz
[Pkg-javascript-devel] node-typescript_4.6.3+ds1-1_source.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 16:09:37 +0100 Source: node-typescript Architecture: source Version: 4.6.3+ds1-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Julien Puydt Closes: 1006862 Changes: node-typescript (4.6.3+ds1-1) experimental; urgency=medium . [ lintian-brush ] * Use secure URI in Homepage field. * Set upstream metadata fields: Security-Contact. . [ Yadd ] * Update nodejs dependency to nodejs:any * Add patch to ignore debian and quilt directories * Use dh-sequence-nodejs auto install . [ Julien Puydt ] * New upstream release. * Ship the tsserver binary (Closes: #1006862). * Refresh patch. Checksums-Sha1: 076b3620f70a332845ef8d87a734f6ba1d0c0f82 2112 node-typescript_4.6.3+ds1-1.dsc 2f2381c089f86cf4a7ee1c8668c2e62f61a2dc1a 21363980 node-typescript_4.6.3+ds1.orig.tar.xz ea67dbab1083bc5da0eca5639af03f39fadd649a 6944 node-typescript_4.6.3+ds1-1.debian.tar.xz 2c4480e893b10ae456c402163e823b0fdb1e3363 7550 node-typescript_4.6.3+ds1-1_source.buildinfo Checksums-Sha256: a534b6e1042cac68e87eef773701295f4f45b72dd6bd92ebdec48f793e2b9a8e 2112 node-typescript_4.6.3+ds1-1.dsc df4f993391afee31d826f296caf3db6faa70795b06aab26c7cb2c0e6f892fa9a 21363980 node-typescript_4.6.3+ds1.orig.tar.xz aa1264807b1913392f6504d29d368a384fd4e63178fbe296f116f2f3fc18488e 6944 node-typescript_4.6.3+ds1-1.debian.tar.xz a2c5b55e9998b081f8f9d17b7c13a4db0505ce325bb00f7b998fef720706be31 7550 node-typescript_4.6.3+ds1-1_source.buildinfo Files: 8a6c6c3f92aae7ea6c36fc7f9f8bae50 2112 javascript optional node-typescript_4.6.3+ds1-1.dsc 9158f037c5291820bb21875886a43474 21363980 javascript optional node-typescript_4.6.3+ds1.orig.tar.xz 1cfbc963572843cde3aeca55bb6489ad 6944 javascript optional node-typescript_4.6.3+ds1-1.debian.tar.xz bfd6bc443809c6afcd047a4d1936916f 7550 javascript optional node-typescript_4.6.3+ds1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmI93m4SHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRsNsP/Atw9wOpa7BFH+diOYRutjOlK57P0fXz +9EDHT5LB9MzagOUDWYA6eBnM7B86J+32SZk0DDEDRWyvFB0Omi7xup0SnlmjEdr naxPetcxFlPT/ZEQ6vQ9UlFlvrIAaUC5ByAdKhn79mvydhjL3B4q971vdGyvVB3S Dl6GkQ7JKxCMFmd/e1XvAfGswMEh3x36PwzFjoETiC6FCClwLteMfn4sp6PquIld 30l7bhjvBEKJqxE1beG58wQOPWr8qyH2bVD+Xt6mOsXTZaZwZ1gZTunlpHzQ2x3l abQjnbjejrJf2uX4C4tYY+u7DFGuKX/4dGs61GJxTK8wb0lc/56C5Y/03lDfNhF3 grhW8K/Jdino1wmicLvmV2XPlSqGGfNHHbXhC97IIdmancIy6aBAOA9nZLAcAsAb GKDSyoLQM3UpZqAB/CYJUpszSdHc3I9yo7aEGiIrbfYO67VFswB96nI0c/YHGUBo Ak+XMNSUC2MWM3Y8r3VV+zpiE0OtwwYluJCPvz825CNeBRML6bhACBjIi2Zu8ZWJ Vd3r3GkokZynQ9BGNcN9i4sKDLdmPS/Xj0sucH1Kg3HHQMHfb0t0OvCVymXwLb5u msdOT+XdunOT/oAQiHzvQSBL3e5mS7QYwIo1xYIMclSmemDretoRZx+VWMMVHxD6 9Gl2wkKdH5th =bKAY -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-find-up_6.3.0-2_sourceonly.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 16:25:22 +0100 Source: node-find-up Architecture: source Version: 6.3.0-2 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Changes: node-find-up (6.3.0-2) experimental; urgency=medium . * Team upload * Add dependency to node-path-exists (>= 5) * Fix autopkgtest using pkg-js-autopkgtest 0.14.11 Checksums-Sha1: ea3e64e6a8a9b274b290ab11956c2b121ccd0d8c 2187 node-find-up_6.3.0-2.dsc c739023dc509403f27c4069ce242d8d56ccb6711 4736 node-find-up_6.3.0-2.debian.tar.xz Checksums-Sha256: 9d741f3a53df2cb5075b93972796453b4b960a49295e24a8d06db46393095a0c 2187 node-find-up_6.3.0-2.dsc 7cc3b58ef39db5d1ffa6e16eb1857ec5fb7e01539e1292a2ae29f073f7588445 4736 node-find-up_6.3.0-2.debian.tar.xz Files: 45806539a2f1a52c14c031c3a8e1a562 2187 javascript optional node-find-up_6.3.0-2.dsc f01e9a77b3d7a4ee35ac5a2c84b12101 4736 javascript optional node-find-up_6.3.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI93zoACgkQ9tdMp8mZ 7uk+Fw/9HGznUgW1A5UOs4rG92+vCt5k8FgQVHWt/9zZ3dmIIxxRPqHm7CGRxTKZ uXZ4+QKOvkS5AKIIinQsBfouW0iM20s4uwpdBDOsv8UalzoTt2qvphD190QU9Ptw i+ZZjtNRfHoz9+ion1qhPxS3Q5WRHzC3ZLTEesYT99ZT9BAdDcX1bkK6fwV3n6fX OLJU5vkDOVloCx5l298ZkQSr/3eqUv5s3pXBsR7D55babk81GHSwQKL7bj4PMZJH 9uZvhsv7WJkfOUuo8tcaP3a/5bE1ay+T2HRt6xZLk6ovTxTA2wJpkQ+5jlqtpknN 8EeAJhyigti2zWqSLH+fkGuQRynEgm3mSVXzCsn8hZsDSwTAnFlcFYqWnjU28yIg JDOVPtQCFSRLx8xH+fKGOerlk6PcmPqU/VUEtvHUMgEOIvfrhUqBWtB9qv9nFQQw NjYU7g63scj4vwCwEHC/IgPCoTO/Oe68eQlCxaF8a1e8KLP+HaabToBd8NxLlHlb KuO6AlSGsI9G0ajQ3KPnHANDZREGOfXTRak32ciY1EdhBe1goB8zH3aDouusML8s 8PnQRytHmFCOzuowqXIEnVkGwG4cb9KY9OHvhkeSMPya8nxxPfnF6mOuPDySspsE 8XwJISc9WIUhDGjOw/4D8LD5qWo1qHMWQ6kMpy13/pP+9kuYBs8= =hfkq -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-typescript_4.6.3+ds1-1_source.changes
node-typescript_4.6.3+ds1-1_source.changes uploaded successfully to localhost along with the files: node-typescript_4.6.3+ds1-1.dsc node-typescript_4.6.3+ds1.orig.tar.xz node-typescript_4.6.3+ds1-1.debian.tar.xz node-typescript_4.6.3+ds1-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] New JS team mailing list?
Quoting Nilesh Patra (2022-03-25 15:59:51) > On 3/25/22 8:09 PM, Jonas Smedegaard wrote: > > Everyone *are* allowed to post, we actively *chose* sensoring, and I > > *volunteer* to screen it to avoid spam on the list. > > ACK. > > > If you disagree and think that we should permit spam on our lists, > > then that is a different topic than that of my post, and it is not > > entirely clear to me if you simply misunderstood me or you actively > > want us to change. > > I actively want us to change. As the signal to noise ratio is lowered > due to tons of processing emails (and it is not only -my- opinion) Reduction of "processing emails" is unrelated to sensoring (if I understand you correctly). I guess that by "processing emails" you mean those emails sent from Debian infrastructure to the Maintainer email address. Do you mean that you want an _additional_ mailinglist which is _separate_ from the address used in package Maintainer field? E.g. a -discuss list? > Also, alioth lists (like the current one) break DKIM signatures and is > a sort of a bummer since I see valid mails get to my spam folder > sometimes. I was unaware that the Alioth list was broken. I recommend that you report that issue to the mailinglist admins: The footer of https://alioth-lists.debian.net/ lists https://salsa.debian.org/alioth-lists-team/support as their preferred place to report issues. > > Please if you want to change our mailinglist handling then > > (preferably as a new separate thread) state your proposal > > explicitly, and let's discuss that. > > Hope this serves the purpose. Yes. Thanks :-) > But please note that there is already a bug for lists.d.o for a JS > team mailing list here[1] it has been a long time since, though. Ah, right. I vaguely rmember us discussing mailinglist structure in the past, but I do not remember what was the conclusion of that discussion, and it is not clear to me from that bugreport either. > Since you moderate this list, it would make a lot of sense if you > could follow up there and do the needful with respect to the > procedure. > > [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946979 Sorry, I fail to see how my role as moderator for the current Alioth list makes me any special regarding setup of additional lists - at alioth-lists.d.n or at lists.d.o. Given my lack of understanding of both what exactly you want here and what was requested in the bugreport, I don't think I am the best to follow up. I am open to changes to mailinglists, for the record. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1007983: marked as done (node-puppeteer: broken autopkgtest keeping chromium from migrating to testing)
Your message dated Fri, 25 Mar 2022 15:29:58 +
with message-id <9e2043f1-0ffc-bb34-ba25-5cfba374b...@debian.org>
and subject line Re: node-puppeteer: broken autopkgtest keeping chromium from
migrating to testing
has caused the Debian Bug report #1007983,
regarding node-puppeteer: broken autopkgtest keeping chromium from migrating to
testing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1007983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007983
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: node-puppeteer
Control: found -1 node-puppeteer/13.1.0+dfsg-6
Control: affects -1 chromium
Severity: serious
Tags: sid bookworm
node-puppeteer is keeping chromium from migrating; as
https://tracker.debian.org/pkg/chromium describes,
"Issues preventing migration:
∙ ∙ autopkgtest for node-puppeteer/13.1.0+dfsg-6: amd64: Regression ♻
(reference ♻), arm64: Regression ♻ (reference ♻), armhf: Regression ♻
(reference ♻), i386: Regression ♻ (reference ♻), ppc64el: Not a
regression"
One of the failure logs is here:
https://ci.debian.net/data/autopkgtest/testing/amd64/n/node-puppeteer/20095690/log.gz
1 failing
1) AriaQueryHandler
queryOne (Chromium web test)
should find by role "button":
Error: expect(received).toEqual(expected) // deep equality
- Expected - 0
+ Received + 1
Array [
"node5",
"node6",
+ "node7",
"node8",
"node10",
"node21",
]
I'm not entirely sure why it's failing, as the test in
node-puppeteer-13.1.0+dfsg/test/ariaqueryhandler.spec.ts seems to be
searching for button nodes and finds an extra (hidden) button:
it('should find by role "button"', async () => {
const { page } = getTestState();
const found = await
page.$$('aria/[role="button"]'); const ids =
await getIds(found); expect(ids).toEqual(['node5', 'node6',
'node8', 'node10', 'node21']); });
Please fix the test; or if this is an actual bug in chromium, please
reassign and let me know.
Thanks,
Andres
--- End Message ---
--- Begin Message ---
Package: node-puppeteer
Version: 13.4.1+dfsg-1
I had forgotten to close this bug with my last upload, which fixes those
issues.
--
Martina Ferrari (Tina)--- End Message ---
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-find-up_6.3.0-2_sourceonly.changes
node-find-up_6.3.0-2_sourceonly.changes uploaded successfully to localhost along with the files: node-find-up_6.3.0-2.dsc node-find-up_6.3.0-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-path-exists_5.0.0-1_sourceonly.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 16:22:06 +0100 Source: node-path-exists Architecture: source Version: 5.0.0-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Changes: node-path-exists (5.0.0-1) experimental; urgency=medium . * Team upload * New upstream version 5.0.0 * Breaks: node-find-up < 6 * Update test Checksums-Sha1: ff4242ce4268c9dd8feaafffb5c999d1b7b74940 2092 node-path-exists_5.0.0-1.dsc 40d80b2292f79fc3fd5ed3de90ec08be61c0750a 3108 node-path-exists_5.0.0.orig.tar.gz 8e6f27e5fa29634f477d2f65582c590de691f534 2952 node-path-exists_5.0.0-1.debian.tar.xz Checksums-Sha256: 3115612e38f26e44b83c8fa89c1cb01ca485f2339156f86713e6eb2f00188437 2092 node-path-exists_5.0.0-1.dsc df9dcb047331fd993940d095b9d3ec010cbb66d831a4dfca7a9046a94d6d303e 3108 node-path-exists_5.0.0.orig.tar.gz 489a1d0c1404d87094588619a29147cc10e0d33a271bcbff1ea87ebadcf62f8c 2952 node-path-exists_5.0.0-1.debian.tar.xz Files: db3f39131224b5b238a6ee0a1bbf3d55 2092 javascript optional node-path-exists_5.0.0-1.dsc 8b831234bb55e5bd4ea6d005097e2c7d 3108 javascript optional node-path-exists_5.0.0.orig.tar.gz e9c3d169b66de8a94d70258abf1cb8bf 2952 javascript optional node-path-exists_5.0.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI93nUACgkQ9tdMp8mZ 7uky9g/+PW65nqRV5gUS1ER100sx0/9ztTKIp87jwbzXcoVIGlZWw8jPl5HEJCaz EslsDXEfXiqEth0HoVWpEY2eCkHSbCxIAakGa74D0jbxv+GXeoTDJksMfBYO0M7o Nry9ttqZSRrtbWZI257S+chCpkYJ6TBEFF2L/QS5OxU13nxjs5wXZ4ybwgPSUU/n 2fGhLQ0IpnItr3iNAXj1NC1ihrxxvS+nRNlzFE0zEE8JhwFfHKWEa8LDCkLRlH2U I+1KT1k+tQgd0JyNoSvAhQkE2n5WW2Kt+WPfXxFA+7RPipTq6WLxQeYXqHaUdSMv kzQsmHSKydo9lTycM8SAa4pZTv+vVFBI4gWE1aClOJltD66G+1UHGWHj6oqj+0rP /qKVXtsSVDxFQ5/d+okb0nBnT1mD51b7WyuK0+Z63qAPwKSo2ji9BQls3o03tWY+ fMRLII0qCfptGcXz1GMzFPCHjOUGNnGI2yTFOtLRMdO86dOdqcyNFKgVwpPDMuGC GmiaGFOEyRYkUwu4WNmQwkdcDeJ1WuaVLaz6VrzNNYuW26xCpud79RWCC8lbLdXD BvYE0Cz40WAgcN2pRdOt7nSAJfQ2r3dTOlW5vYviquIwbZ28pReoIvEFHIpg/2jF 3MQOsv7UmHK0X9o2dsqnQBFdH/8Hv0byZV19RAV2QgRSED3xmfA= =3XdS -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processed: Bug#1006862 marked as pending in node-typescript
Processing control commands: > tag -1 pending Bug #1006862 [node-typescript] the tsserver binary is missing Added tag(s) pending. -- 1006862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-path-exists_5.0.0-1_sourceonly.changes
node-path-exists_5.0.0-1_sourceonly.changes uploaded successfully to localhost along with the files: node-path-exists_5.0.0-1.dsc node-path-exists_5.0.0.orig.tar.gz node-path-exists_5.0.0-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] pkg-js-tools_0.14.11_sourceonly.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 16:07:05 +0100 Source: pkg-js-tools Architecture: source Version: 0.14.11 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Changes: pkg-js-tools (0.14.11) unstable; urgency=medium . * Add no_lerna tests * autopkgtest: improve "require" test for modules when /usr/share/node_modules links exists (given by nodejs 14 in unstable) Checksums-Sha1: 508bd6aa9e408058be1794ee7236ffe5c92f3c1e 2628 pkg-js-tools_0.14.11.dsc ea2e3a7d103239d78f20064312e375cc071dbd3d 75872 pkg-js-tools_0.14.11.tar.xz Checksums-Sha256: 8f5a4966f1f7a4b3d4faa22a96eb84637cf1bd3f5968d678530261452767d7ca 2628 pkg-js-tools_0.14.11.dsc 08e7bb544c375b64a966909d7bcadfcf01453ab5bc0be0dacba0de6c3c35fb54 75872 pkg-js-tools_0.14.11.tar.xz Files: 2dcfefc20636634b37cf84d1242dabb6 2628 devel optional pkg-js-tools_0.14.11.dsc ae036d3588d67bc0a2127242e8ac78de 75872 devel optional pkg-js-tools_0.14.11.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI92xwACgkQ9tdMp8mZ 7uke7Q//fm6jQ1h8uMDm219MM03jayh44alpdbQT6+CvmYXHFTF2RMzGp/AqxljJ Od1q6Hb1pTCRbAnEu/75wjnfUDaflJGU/Jxs+G7t6q/sqO02hbPjXxhOP7xKt4Uy lTJqQyo0XRQmfjaBzs/3xqaBhY2aDZf2aq7SRTZuFo1a7iB5Va/NrpqfbcMMqMH1 JEfboQHTZ447/YqIpAdZMG7n0nLvqAEiV4Ks5V66a3y1j1JDW70VxTbCovWl1HSg Sw3QUWqQPvR2C8fBo/vJ10GddPFIDgfEviuIsmEC94+v+xSoOfo+RV0B7CFbcrku gxetvfU4T/Is3MZ8mFL4KkGPexxHytJBvuCZKneZeuuXbSYdmahdwtHWfeobwVRO xug9NxY+sX9tP6ahZC9QS5/jUzGe+DCUNrC448atqVgR0jyZNQ3vqad/tVtQ+hcQ LezRGovz0i7tyxWSSisfjykb4RApQyAwwgZ9QkkwMsS5rrXzwUQYcK20qRaKjuSI djD99S75EHhpSHXdc/zHquEeoh1iAE9NvyKwj7eHuQhfuQ3GzuJyzrCe0KbP9N/d PU93tXbabnHoNGwLx/+CnZ8gZG/uJ8lHmQv4l1OyIJuTbW2YQRXWGez4KX9qVamb lu2g489fUxyd1acLbFc5wXWrBaKIn4+RU1c5JqBXyWMptnc5LH8= =6YVf -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-locate-path_7.1.0-2_sourceonly.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 16:05:52 +0100 Source: node-locate-path Architecture: source Version: 7.1.0-2 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Changes: node-locate-path (7.1.0-2) experimental; urgency=medium . * Team upload * Breaks: node-find-up < 6 * Fix autopkgtest using pkg-js-autopkgtest >= 0.14.11 Checksums-Sha1: cbe5f85de8e96aa91a55614583eb5d224311bed4 2157 node-locate-path_7.1.0-2.dsc 15de3481ce3c7e78cb1840eb42123ce98ae09ccd 3856 node-locate-path_7.1.0-2.debian.tar.xz Checksums-Sha256: 829c73475ef5f8818fb2a493536366da2ab36fcab5f0aabf1d985dc73c812ab7 2157 node-locate-path_7.1.0-2.dsc bd8e620a856b2b42bd6ad5443eddb2cf3663998740af414f33da8fff33b21d69 3856 node-locate-path_7.1.0-2.debian.tar.xz Files: 1ecaa798b8022857bc50772b507ba610 2157 javascript optional node-locate-path_7.1.0-2.dsc 694ca1a36b730fb6d13fdf6caeff459f 3856 javascript optional node-locate-path_7.1.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI92sEACgkQ9tdMp8mZ 7ukT/g//TKAZeiMxS0xroFACHZHiV1HqASEoX880iivt0W/a66yBdX9HyX6jE/2y 0ZMmR6Rw9btAcfCo+yUNGjTH5KUCR7RCFgLGBf8vGG3d/+EcAMqjsotsfK7OokpU 9UBK5CmECsPCOO0JJi41arIWkuRgvMYmX7K9s7RTL/NOOZo9w10OGAf0lvAGV+iL QtEdvXvnRtLfPEduzijBkv6Jv3jgnVI4aDGZ5EiOv/L3Krwbs5Z0ryomSj9BvDSw L+WiYe4B3mM3JdcuE87vQZtLMlzAPyPqJOaUWgEZcAhkkV8p0j9pDS/mk6CPsyrP EtHgMd65hm2MvbDs8Cz19bHnKXfjy5ZDfcf79G7V5TqbyaBmDCfZ1aN+ub0oNlKo 2bYdVUmo+OYO8JXgt3ZUW7s6vawhOah5hbIo7LEXOANNj6hz2Q1BviuzXOIYUENn gHTbYBfeNEU3j8aZXcEVEMs2qujjMllnXeFZYyVkRt21PcZXZ7K5GHSiv4xOeEv5 WTJ/aBiay9gafl82HQ/JZprS0lwP5AdUogIaleSikgi0iW4zmqPIyC5dQS9F1mSu vm3/iIGN8HYsmVHeAcYB0hh78ivq+l64ehZLLqe/9XCXM7+IYoYOWFjef32xLxGD gopopk8mKfNwZulExcDqRn11fp9UGOXJIHRo6pgna7LfiRzsZUM= =gzsi -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-locate-path_7.1.0-2_sourceonly.changes
node-locate-path_7.1.0-2_sourceonly.changes uploaded successfully to localhost along with the files: node-locate-path_7.1.0-2.dsc node-locate-path_7.1.0-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of pkg-js-tools_0.14.11_sourceonly.changes
pkg-js-tools_0.14.11_sourceonly.changes uploaded successfully to localhost along with the files: pkg-js-tools_0.14.11.dsc pkg-js-tools_0.14.11.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1008230: marked as done (pkg-js-tools: dh-sequence-nodejs-no-lerna not functional)
Your message dated Fri, 25 Mar 2022 15:05:50 + with message-id and subject line Bug#1008230: fixed in pkg-js-tools 0.14.10 has caused the Debian Bug report #1008230, regarding pkg-js-tools: dh-sequence-nodejs-no-lerna not functional to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1008230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: pkg-js-tools Version: 0.14.9 Severity: normal Tags: patch Due to a couple of bugs, you currently cannot disable the usage of workspaces (from lerna.json or packages.json), and if you try to use the nodejs-no-lerna sequence, the build fails completely. I have provided a patch in https://salsa.debian.org/js-team/pkg-js-tools/-/merge_requests/16 -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-11-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8), LANGUAGE=en_IE:en Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages pkg-js-tools depends on: ii dh-nodejs 0.14.9 Versions of packages pkg-js-tools recommends: ii apt-file 3.2.2 ii devscripts2.22.1 pn libcache-cache-perl pn libprogress-any-output-termprogressbarcolor-perl ii node-semver 7.3.5+~7.3.8-1 ii npm 8.5.5~ds1-1 Versions of packages pkg-js-tools suggests: pn autodep8 ii git-buildpackage 0.9.25 ii lintian 2.114.0 -- no debconf information --- End Message --- --- Begin Message --- Source: pkg-js-tools Source-Version: 0.14.10 Done: Yadd We believe that the bug you reported is fixed in the latest version of pkg-js-tools, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated pkg-js-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 15:26:47 +0100 Source: pkg-js-tools Architecture: source Version: 0.14.10 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1008229 1008230 Changes: pkg-js-tools (0.14.10) unstable; urgency=medium . [ Yadd ] * autopkgtest: able to skip main module using debian/tests/pkg-js/require-SKIP . [ Martina Ferrari ] * Fix dh-sequence-nodejs-no-lerna (Closes: #1008230) * Add missing EOL in error messages. . [ Yadd ] * Fix doc: a "main" component is always required (Closes: #1008229). Thanks to Martina Ferrari Checksums-Sha1: b785ccc0904391cc64d62c6d2c0b7229c0d4cb7c 2628 pkg-js-tools_0.14.10.dsc 18169d6860d6e493a2ae8f985ff4d1df618c5a15 75228 pkg-js-tools_0.14.10.tar.xz Checksums-Sha256: 5bd0f20aa80e8b47412ff8deebd0f99d7167e8f4e818712e978b5baee0ff4dc4 2628 pkg-js-tools_0.14.10.dsc c9ba3f47bb328dd3bad89fa1f60f0bf9fa88931cd7a6e525124a62d47a366b87 75228 pkg-js-tools_0.14.10.tar.xz Files: 2b2bc973c972ffe4b42700e14dd6758c 2628 devel optional pkg-js-tools_0.14.10.dsc 3fb4e363256d5262401a738183feb618 75228 devel optional pkg-js-tools_0.14.10.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI90Y4ACgkQ9tdMp8mZ 7uns+Q//dyzpfbRE8wJN63Vtn89qdCkGEJ8sthJw9C6HvDDsSI5fQfqsZkMHKlMV Wls/diodvJoivUghyNHoIuffWdQ7oic5EJ9I+aoIfJpoC2I/7/Phfo1iAX785yOI hdRQ/r6eUqgIGmV1kVDqUO3JDo2wvx6GzIE2tF0E6MRdkhaomzu/kWBZvVy+6moc Bq1t9inYRKaSKpklQxtMYh1CAeah739LROw7DyULNg/Kh/iusR8tRFE2WD6uQvdQ 2004Fk3C7H9SM3kayoxpyKninRRGez/DCELL4+Ppoj0iBLBLsYlbLKir9S3aIUue FFgsOY7JgtgV0te1DqJtHUKqbIJ/1sAOkXOb/qtj+kcXXuqhgKo4W/zrWkQytL5k UVg6FJ8q0nk1+Buy0rgHC+KMNuwrztH3gGF58wxIf5Cbzz8qY6ck+eyY5PM6q9hv rYxDwX6jY7M3BFmIzgeFkJJjshSQQLn1vEsx4E9Jm7AnVPychbM41oVquKEFqWC8
[Pkg-javascript-devel] Bug#1008229: marked as done (pkg-js-tools: Issues with bundle packages with no main package)
Your message dated Fri, 25 Mar 2022 15:05:50 +
with message-id
and subject line Bug#1008229: fixed in pkg-js-tools 0.14.10
has caused the Debian Bug report #1008229,
regarding pkg-js-tools: Issues with bundle packages with no main package
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1008229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: pkg-js-tools
Version: 0.14.9
Severity: normal
Despite what the documentation says, placing an empty debian/nodejs/main file
does not properly work. There are many parts of the code that still try to use
the main package, and the ${nodejs:Provides} substvar contains an invalid
"node-" line.
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-11-amd64 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8),
LANGUAGE=en_IE:en
Shell: /bin/sh linked to /bin/dash
Init: unable to detect
Versions of packages pkg-js-tools depends on:
ii dh-nodejs 0.14.9
Versions of packages pkg-js-tools recommends:
ii apt-file 3.2.2
ii devscripts2.22.1
pn libcache-cache-perl
pn libprogress-any-output-termprogressbarcolor-perl
ii node-semver 7.3.5+~7.3.8-1
ii npm 8.5.5~ds1-1
Versions of packages pkg-js-tools suggests:
pn autodep8
ii git-buildpackage 0.9.25
ii lintian 2.114.0
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: pkg-js-tools
Source-Version: 0.14.10
Done: Yadd
We believe that the bug you reported is fixed in the latest version of
pkg-js-tools, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1008...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Yadd (supplier of updated pkg-js-tools package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 25 Mar 2022 15:26:47 +0100
Source: pkg-js-tools
Architecture: source
Version: 0.14.10
Distribution: unstable
Urgency: medium
Maintainer: Debian Javascript Maintainers
Changed-By: Yadd
Closes: 1008229 1008230
Changes:
pkg-js-tools (0.14.10) unstable; urgency=medium
.
[ Yadd ]
* autopkgtest: able to skip main module using
debian/tests/pkg-js/require-SKIP
.
[ Martina Ferrari ]
* Fix dh-sequence-nodejs-no-lerna (Closes: #1008230)
* Add missing EOL in error messages.
.
[ Yadd ]
* Fix doc: a "main" component is always required (Closes: #1008229). Thanks
to Martina Ferrari
Checksums-Sha1:
b785ccc0904391cc64d62c6d2c0b7229c0d4cb7c 2628 pkg-js-tools_0.14.10.dsc
18169d6860d6e493a2ae8f985ff4d1df618c5a15 75228 pkg-js-tools_0.14.10.tar.xz
Checksums-Sha256:
5bd0f20aa80e8b47412ff8deebd0f99d7167e8f4e818712e978b5baee0ff4dc4 2628
pkg-js-tools_0.14.10.dsc
c9ba3f47bb328dd3bad89fa1f60f0bf9fa88931cd7a6e525124a62d47a366b87 75228
pkg-js-tools_0.14.10.tar.xz
Files:
2b2bc973c972ffe4b42700e14dd6758c 2628 devel optional pkg-js-tools_0.14.10.dsc
3fb4e363256d5262401a738183feb618 75228 devel optional
pkg-js-tools_0.14.10.tar.xz
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI90Y4ACgkQ9tdMp8mZ
7uns+Q//dyzpfbRE8wJN63Vtn89qdCkGEJ8sthJw9C6HvDDsSI5fQfqsZkMHKlMV
Wls/diodvJoivUghyNHoIuffWdQ7oic5EJ9I+aoIfJpoC2I/7/Phfo1iAX785yOI
hdRQ/r6eUqgIGmV1kVDqUO3JDo2wvx6GzIE2tF0E6MRdkhaomzu/kWBZvVy+6moc
Bq1t9inYRKaSKpklQxtMYh1CAeah739LROw7DyULNg/Kh/iusR8tRFE2WD6uQvdQ
2004Fk3C7H9SM3kayoxpyKninRRGez/DCELL4+Ppoj0iBLBLsYlbLKir9S3aIUue
FFgsOY7JgtgV0te1DqJtHUKqbIJ/1sAOkXOb/qtj+kcXXuqhgKo4W/zrWkQytL5k
UVg6FJ8q0nk1+Buy0rgHC+KMNuwrztH3gGF58wxIf5Cbzz8qY6ck+eyY5PM6q9hv
rYxDwX6jY7M3BFmIzgeFkJJjshSQQLn1vEsx4E9Jm7AnVPychbM41oVquKEFqWC8
TSqvQFH7HO44mdlKhVQAEZVYIwwG4I4yOvvdPEdnD7DEtXebOEej6k1TtFlLHm3S
[Pkg-javascript-devel] Bug#1008200: Bug#1008200: marked as done (node-send: patched node-mime-types cause problems for other reverse-dependencies)
On 3/25/22 8:15 PM, Debian Bug Tracking System wrote: node-send (0.18.0+~cs1.19.1-1) unstable; urgency=medium . * Embed typescript declarations * New upstream version 0.18.0+~cs1.19.1 * Add dependency to node-ms and node-statuses and drop old patches (Closes: #1008200) * Add patch for mime >= 2 and statuses < 2 Thank you, Yadd for quick processing. Much appreciated! We can now proceed with shiny-server. Regards, Nilesh OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] pkg-js-tools_0.14.10_sourceonly.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 15:26:47 +0100 Source: pkg-js-tools Architecture: source Version: 0.14.10 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1008229 1008230 Changes: pkg-js-tools (0.14.10) unstable; urgency=medium . [ Yadd ] * autopkgtest: able to skip main module using debian/tests/pkg-js/require-SKIP . [ Martina Ferrari ] * Fix dh-sequence-nodejs-no-lerna (Closes: #1008230) * Add missing EOL in error messages. . [ Yadd ] * Fix doc: a "main" component is always required (Closes: #1008229). Thanks to Martina Ferrari Checksums-Sha1: b785ccc0904391cc64d62c6d2c0b7229c0d4cb7c 2628 pkg-js-tools_0.14.10.dsc 18169d6860d6e493a2ae8f985ff4d1df618c5a15 75228 pkg-js-tools_0.14.10.tar.xz Checksums-Sha256: 5bd0f20aa80e8b47412ff8deebd0f99d7167e8f4e818712e978b5baee0ff4dc4 2628 pkg-js-tools_0.14.10.dsc c9ba3f47bb328dd3bad89fa1f60f0bf9fa88931cd7a6e525124a62d47a366b87 75228 pkg-js-tools_0.14.10.tar.xz Files: 2b2bc973c972ffe4b42700e14dd6758c 2628 devel optional pkg-js-tools_0.14.10.dsc 3fb4e363256d5262401a738183feb618 75228 devel optional pkg-js-tools_0.14.10.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI90Y4ACgkQ9tdMp8mZ 7uns+Q//dyzpfbRE8wJN63Vtn89qdCkGEJ8sthJw9C6HvDDsSI5fQfqsZkMHKlMV Wls/diodvJoivUghyNHoIuffWdQ7oic5EJ9I+aoIfJpoC2I/7/Phfo1iAX785yOI hdRQ/r6eUqgIGmV1kVDqUO3JDo2wvx6GzIE2tF0E6MRdkhaomzu/kWBZvVy+6moc Bq1t9inYRKaSKpklQxtMYh1CAeah739LROw7DyULNg/Kh/iusR8tRFE2WD6uQvdQ 2004Fk3C7H9SM3kayoxpyKninRRGez/DCELL4+Ppoj0iBLBLsYlbLKir9S3aIUue FFgsOY7JgtgV0te1DqJtHUKqbIJ/1sAOkXOb/qtj+kcXXuqhgKo4W/zrWkQytL5k UVg6FJ8q0nk1+Buy0rgHC+KMNuwrztH3gGF58wxIf5Cbzz8qY6ck+eyY5PM6q9hv rYxDwX6jY7M3BFmIzgeFkJJjshSQQLn1vEsx4E9Jm7AnVPychbM41oVquKEFqWC8 TSqvQFH7HO44mdlKhVQAEZVYIwwG4I4yOvvdPEdnD7DEtXebOEej6k1TtFlLHm3S d5x7P5PnWhRGoAV0nUn/alZzHXQmFmRE4iiXUbs96CWwwdjHisbBLVDFcdCN6K1f nFg70siKW0yOkTC88tXytGki+5VPqaW2l1p07J+30V74HV2Y15c= =B3eW -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-p-locate_6.0.0-2_sourceonly.changes ACCEPTED into experimental
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 15:52:23 +0100 Source: node-p-locate Architecture: source Version: 6.0.0-2 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Changes: node-p-locate (6.0.0-2) experimental; urgency=medium . * Team upload * Indicate that p-locate 6 breaks node-locate-path < 7 Checksums-Sha1: 491d0d83a3944d2591807a2d305dbfefd9c9bf7d 2078 node-p-locate_6.0.0-2.dsc e7411af8b4673577ce606acb452ea0a2fc64873f 81116 node-p-locate_6.0.0-2.debian.tar.xz Checksums-Sha256: bca4c7e7a94af770556a575141ae8c004bafbb286992a9cfb4f5dd0e52756709 2078 node-p-locate_6.0.0-2.dsc 3d48cd2861e030c2f187a91bc070c1e3f3741d8fef7492f0ffbd00ab13e8885d 81116 node-p-locate_6.0.0-2.debian.tar.xz Files: 75b54dd5d649e7ccd8af036614702618 2078 javascript optional node-p-locate_6.0.0-2.dsc d5ed675a694932f8247d5fdb53a11db1 81116 javascript optional node-p-locate_6.0.0-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI914cACgkQ9tdMp8mZ 7unMrw//bHCVFkfeIcgX91Boh3J0XqYBdCA3WhEaECL+KRj88IlT1PrrXK/Ppah3 4kulnY8k2qFMzQP5ca5mngDDx7KzMlaUZF5cUGHMhIam1eKbaye9yc0RI+ZjQgJ4 LWH4x2jqbhZzfSoGq83BUwMH71NBHE2zOWuPKye4LuScxhBPH6ZaM6LNSqduZtG6 15SwBYrdbT9InpteVaP9MymWxs4pSVnBzXI0xoqDctOVOI45BAklF26q7vytukFt AEg9m+LiV8mMGGqdQA3Kk/nhaH2DA26LFdDkg/Bwkuo5EZEOBhp+GRjWwVu7717k uQJQkAO0YLSYEiZeBMmLgpH8wf0QQT462AdacdHErSG3RHQ3AORqbsNJPevsIAjT MqGDC18Jj9/ntpq0TPrD/MYmQTQkqJHiIXLaGDoPW+34mGI1DD+h0hG27/4vbpaW 9wD4w+s05j1eIOhfUpezVTfHOAAwxm9MN88TaX1pgEa15ghAYGG07p6w8AacfYCY lK15fny0tFgGJQlyeaFHJMaL255QLaKjiSzKV+o1luMA24k044HvMOI4PeAvBecs Ycd2RLsgBqG0k/kF2itJUssAxcJv2QSknVAhcAPV+usyWetIMbXzg0h2K+XSeJBt OZOEmiGcTI5xGAxAVvpRKJtQT90whyhSIeIfGbhOMT70J14TGio= =b4eD -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-micromatch_4.0.5+~4.0.2-1_sourceonly.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 15:47:30 +0100 Source: node-micromatch Architecture: source Version: 4.0.5+~4.0.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Changes: node-micromatch (4.0.5+~4.0.2-1) unstable; urgency=medium . * Team upload * New upstream version 4.0.5+~4.0.2 * Drop old & useless patch Checksums-Sha1: 365a8c0dff0aedf005861a500a2ccc2ed1a8cb0b 2532 node-micromatch_4.0.5+~4.0.2-1.dsc ce29c8b166a73bf980a5727b1e4a4d099965151d 5932 node-micromatch_4.0.5+~4.0.2.orig-types-micromatch.tar.gz e0400069b89a7594a4b3789e56b07acc413868c7 88213 node-micromatch_4.0.5+~4.0.2.orig.tar.gz 9431c99b2998f96459f6a53baa531c0cbd0ec984 4056 node-micromatch_4.0.5+~4.0.2-1.debian.tar.xz Checksums-Sha256: 47f73274195e15919010d3835f02fc3f5bb7560ecce2f0266327e4fa010e937a 2532 node-micromatch_4.0.5+~4.0.2-1.dsc a868f7470d8d8897cf76a0c3da1be9c0145b16d7737f523cfe8a5731eb474ecb 5932 node-micromatch_4.0.5+~4.0.2.orig-types-micromatch.tar.gz bf99f621436c00abbd60c1f071df6eb94576d7616b6a2e594b3374ae6469a224 88213 node-micromatch_4.0.5+~4.0.2.orig.tar.gz b36316d6e341264fda8b5287ceefec14c7f5974b82f4ca5c2c82b62515435bd8 4056 node-micromatch_4.0.5+~4.0.2-1.debian.tar.xz Files: 2ca43bb757c8706a084fb924b8b88825 2532 javascript optional node-micromatch_4.0.5+~4.0.2-1.dsc 18ef2e9e8298a8cff569187e7ec48638 5932 javascript optional node-micromatch_4.0.5+~4.0.2.orig-types-micromatch.tar.gz ce1e89fcb0b659708f618b5ffd184acf 88213 javascript optional node-micromatch_4.0.5+~4.0.2.orig.tar.gz cec21c29c8d566e8333b33b007d0ae44 4056 javascript optional node-micromatch_4.0.5+~4.0.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI91sgACgkQ9tdMp8mZ 7umVzg//Ubq58q6x/kx0uBwBdwh9ppjJFyE68InMyejwQuJhFMH3oDQW1yKH6LCp /rsngAQ+KXz4vq8LZ9pw8LDJRy6nBZqAkA83IbR/Rr98qVjaFGlyfSNMD+vr3U1B wDiQJutlxfGKVvgTtPBUlxBFuCF0jkoMwaiGEvULW1ae6pY19uz7tE/9LjiIYB0s 36O+nEwegyfH0jpP6CS5kCTXdURlQmahctERNfz6iOzK1riVc8GPbLtk9KIYio8n jgna7AWdvkpPb4nphGaGgdODSkQ5sD90gbf6yxiz0wnh1Dn4csYuqVL+9VuIKPPF jFnK6bAylg5I8skna7vu4V4Nw4vIOXrOq57BlTaWx+yijBiXJ8lTCWjp9lV02vet 0biQ8v4RAc1qAki3sgXhQD28bVQKKpW6P4gd0m3dYJS7YTNHjPn+kEZh25kxWuYK 1ckQcumhPhtN+77wyG5e4F5+H/lT0miK4Il7CyjL/msTWW7hJCOnOQqkpbmCWPjX hhRl1ivQ/x9KZIlLn7/1olj+1FsMLI8hExidSG7CqNXiXa3xGBorh269F1wv46u0 mPYbGMeivgAOXVGFBw7kex8NKCQmTx85pZB/fm1xzsukcNgWnRrTBlhFLcHvy5U9 rU+45hdUWC74xUP9E0GSxwfjsHRGclJWeNLkAlSlwq++9I7bamc= =1lyz -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-mdn-browser-compat-data_4.1.13+~3.4.0-1_sourceonly.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 15:50:11 +0100 Source: node-mdn-browser-compat-data Architecture: source Version: 4.1.13+~3.4.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Changes: node-mdn-browser-compat-data (4.1.13+~3.4.0-1) unstable; urgency=medium . * New upstream version 4.1.13+~3.4.0 Checksums-Sha1: 5a472fdbabd7ed7229ee1bfcfeb3f3d6af9efbbe 2649 node-mdn-browser-compat-data_4.1.13+~3.4.0-1.dsc 2f378f8892c194592e6a7def293b01696beaf25a 44039 node-mdn-browser-compat-data_4.1.13+~3.4.0.orig-browser-specs.tar.gz 32ed258007bc5f8761088ad127f8701da9d3f314 996295 node-mdn-browser-compat-data_4.1.13+~3.4.0.orig.tar.gz 130cb72fd08a8c766aac4a39009f048554da9530 6308 node-mdn-browser-compat-data_4.1.13+~3.4.0-1.debian.tar.xz Checksums-Sha256: 66577be270ec5e2c3fb559e987a27ea0c78394b4ef0581eb48bdd12139830fb3 2649 node-mdn-browser-compat-data_4.1.13+~3.4.0-1.dsc aac2283c6bf899cc9bb81f88eaee951051c8cede4e9ab297c8f7c0dcf321e830 44039 node-mdn-browser-compat-data_4.1.13+~3.4.0.orig-browser-specs.tar.gz f3db23fd327a972b10a4c67c8bf7e992851bf1ebfc993d619a61b61289fcee2f 996295 node-mdn-browser-compat-data_4.1.13+~3.4.0.orig.tar.gz 702629f655159f128b81386eb9277ca9ce19c980651691ad97d49499c9127080 6308 node-mdn-browser-compat-data_4.1.13+~3.4.0-1.debian.tar.xz Files: fc815155e4fb05d0f97822623ecdbf0f 2649 javascript optional node-mdn-browser-compat-data_4.1.13+~3.4.0-1.dsc 67d0658d988e626f573c6f83ccf2e050 44039 javascript optional node-mdn-browser-compat-data_4.1.13+~3.4.0.orig-browser-specs.tar.gz 56f6fa9c4100148ac802c99a6c1cc6c0 996295 javascript optional node-mdn-browser-compat-data_4.1.13+~3.4.0.orig.tar.gz 061975ce21a08a6b416cbdb92053e14f 6308 javascript optional node-mdn-browser-compat-data_4.1.13+~3.4.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI91z0ACgkQ9tdMp8mZ 7ulUNQ/8DLk+j9mfAU8mDnix1mn8vyh/iux6Xg2BRp7QuYDbMgqu8JGYUnX0XCCP ynp6nI6wBvimFnN9ldWDuDWyiWF7Fhyyr3CT+tmMbjIHnr//zKZUc9KtpEdBKbz9 NeYFfBmMTrlUAfZ8rkZRb8J8vc2KdqztkgBNw4iaypkA7n94/p0wY3Tli0pqXenU Z6o2MQSVP+4XI3BIorUmEJO3Ty+veqCCLy/8Lo88TAl6gJHzHHDYjvUim0qWDTRM tgi4yYi3vKfhTqQsM1jwh0hCamASYr5sDRXZkI9nEBTxlBrcJTeiDeQOkbk4VSIN h/OqLcjnHfoHEJGGdDN9dzIvhstIt7+gjtYq/K/+hTi1AdA8LJTPnNyWzsuj74Ul Bts9njrgWqOp2bK0Hor60g5+tmveLVpL66ABAyI7ZZ5zfjw+tR4HIkUVOEAz2aP5 9zXWGCu+L10W9BBVBRzR1ycp86iaisdklT1CUFyVOAna2ju6QwF5TerSBaLcXqI6 /8w2mg7YN9ZoT0RYnVLXVgYmGvBn9ihZOSH2I2z6diuiWOjqV8FtNizZpWm2yyGg YXZfgsbZ9QmJtJOcjTWuv7PNaMYtIYqH727giyVfXznB4xO/TxUZRkuEAhC8u457 zvbsX0OjkSrhVFqV4bHD+YRcILeSb1BEqQMHrkHa3nrd7vgwqJU= =mBAf -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-mdn-browser-compat-data_4.1.13+~3.4.0-1_sourceonly.changes
node-mdn-browser-compat-data_4.1.13+~3.4.0-1_sourceonly.changes uploaded successfully to localhost along with the files: node-mdn-browser-compat-data_4.1.13+~3.4.0-1.dsc node-mdn-browser-compat-data_4.1.13+~3.4.0.orig-browser-specs.tar.gz node-mdn-browser-compat-data_4.1.13+~3.4.0.orig.tar.gz node-mdn-browser-compat-data_4.1.13+~3.4.0-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-p-locate_6.0.0-2_sourceonly.changes
node-p-locate_6.0.0-2_sourceonly.changes uploaded successfully to localhost along with the files: node-p-locate_6.0.0-2.dsc node-p-locate_6.0.0-2.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-micromatch_4.0.5+~4.0.2-1_sourceonly.changes
node-micromatch_4.0.5+~4.0.2-1_sourceonly.changes uploaded successfully to localhost along with the files: node-micromatch_4.0.5+~4.0.2-1.dsc node-micromatch_4.0.5+~4.0.2.orig-types-micromatch.tar.gz node-micromatch_4.0.5+~4.0.2.orig.tar.gz node-micromatch_4.0.5+~4.0.2-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] New JS team mailing list?
On 3/25/22 8:09 PM, Jonas Smedegaard wrote: Everyone *are* allowed to post, we actively *chose* sensoring, and I *volunteer* to screen it to avoid spam on the list. ACK. If you disagree and think that we should permit spam on our lists, then that is a different topic than that of my post, and it is not entirely clear to me if you simply misunderstood me or you actively want us to change. I actively want us to change. As the signal to noise ratio is lowered due to tons of processing emails (and it is not only -my- opinion) Also, alioth lists (like the current one) break DKIM signatures and is a sort of a bummer since I see valid mails get to my spam folder sometimes. Please if you want to change our mailinglist handling then (preferably as a new separate thread) state your proposal explicitly, and let's discuss that. Hope this serves the purpose. But please note that there is already a bug for lists.d.o for a JS team mailing list here[1] it has been a long time since, though. Since you moderate this list, it would make a lot of sense if you could follow up there and do the needful with respect to the procedure. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946979 Kind Regards, Nilesh OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1008258: marked as done (libjs-bootstrap4: new version available upstream (v4.6.1))
Your message dated Fri, 25 Mar 2022 14:43:33 + with message-id and subject line Bug#1008258: fixed in twitter-bootstrap4 4.6.1+dfsg1-1 has caused the Debian Bug report #1008258, regarding libjs-bootstrap4: new version available upstream (v4.6.1) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1008258: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008258 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libjs-bootstrap4 Version: 4.5.2+dfsg1-7 Severity: wishlist I note that the latest version (of 4.*) available upstream is 4.6.1: https://github.com/twbs/bootstrap/releases/tag/v4.6.1 released 28 Oct 2021. The only reason I realised this is that openQA just switched to using 4.6.1. https://github.com/os-autoinst/openQA/pull/4579/files I would imagine that openQA should work well enough with 4.6.0 (not tried it yet), so if there's a good reason for not packaging 4.6.1, please say so and I'll feed that back to the openQA folks, and will then try to make sure that openQA supports both versions adequately. Cheers, Phil. --- End Message --- --- Begin Message --- Source: twitter-bootstrap4 Source-Version: 4.6.1+dfsg1-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of twitter-bootstrap4, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated twitter-bootstrap4 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 15:13:46 +0100 Source: twitter-bootstrap4 Architecture: source Version: 4.6.1+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1008258 Changes: twitter-bootstrap4 (4.6.1+dfsg1-1) unstable; urgency=medium . * Team upload * New upstream version 4.6.1+dfsg1 (Closes: #1008258) Checksums-Sha1: 07faea26b9c2bac4dd765a043275b572161b854d 2344 twitter-bootstrap4_4.6.1+dfsg1-1.dsc e98a1a8175e6450e984d87a197e3afc1aa8716f2 2329588 twitter-bootstrap4_4.6.1+dfsg1.orig.tar.xz 81ce0fb4218f6b858285f44fc26e555daf364063 19332 twitter-bootstrap4_4.6.1+dfsg1-1.debian.tar.xz Checksums-Sha256: 04557c04dd2175305bdbbb537c8d6e758982b490b8a6f45e38ed4877b08a693f 2344 twitter-bootstrap4_4.6.1+dfsg1-1.dsc a2fdd5c181d592deb7ea7b1676188978cc60ebf182d1e6c4d6c712e0c6eb8a54 2329588 twitter-bootstrap4_4.6.1+dfsg1.orig.tar.xz b65d62ef6045b4db14c8510a6aa6c909409f7c39649e5c853e3e02b10e08ff33 19332 twitter-bootstrap4_4.6.1+dfsg1-1.debian.tar.xz Files: 04230a1517aea7ed9cff09d1a64e33aa 2344 javascript optional twitter-bootstrap4_4.6.1+dfsg1-1.dsc d0b7793db9e3976ce87f34dda946affa 2329588 javascript optional twitter-bootstrap4_4.6.1+dfsg1.orig.tar.xz 2686f13b9fb4725c0e7ee67a92a2cc34 19332 javascript optional twitter-bootstrap4_4.6.1+dfsg1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI9zrcACgkQ9tdMp8mZ 7ukmoA//WulY6jodNjBNdSv1pHHPsZPy9kEWexBHNf2VNlqVRw1CdTdi5bixyOFT zRTBstGCnhWHw3vPStN0MEK2yJM51rkSNdmbkFChd3gI/J9MSsFEsczgjotR73Ia RdNN9ixUXX9MzzFMNdqWjcyHT5AI8L7Qh4EIjjQplHWz3uKaAvlS82TV4PjhNJZh fg70x+Gp/qHEvC6uQLD8fo7k70bTH1+ONsjuBSfZnQe8BD6FCzT2U/isqnu8A89Q TNUlHVSo+CCByV19Vk6whaabQabzjYb/PaEnsDYWUKNtWnCx80P4g9tSnPLnaDkB a2NbGicJLva1/IdY5N2Ik0NZycMNGfPyBcjYbPgcxXP9BYR2+AUUfDWN8/S7ZX07 xJGm/awcDz7gaa7ZwNzO96VGYWvOvxQZY4JayTQDF6riNRuEK5YSdRTmWtwu4sRT SMHSPndfXm6MWXMYan8uzAxuqkhzwAK3X03gMFZ/qvHpT2Y/P86O9Tmx2YC5+//h kXg9FQCyNEYK/vmMovqNYN6//yMAM3l1k1iQRWuGubEA+a6mCVCrOBeu86BbX+BH LtNCnoU5QdmD6FJMW3DemkRM2EUFbI4Eo3fPT+k4Nft3Dd1ta5eOFsuFXg+CLC3r pLoyTSGENBtdKHOLVfCwlhxxVMLyG43399BUsz1ODJKiHqSfqt8= =tLjr -END PGP SIGNATURE End Message --- -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1008200: marked as done (node-send: patched node-mime-types cause problems for other reverse-dependencies)
Your message dated Fri, 25 Mar 2022 14:42:20 + with message-id and subject line Bug#1008200: fixed in node-send 0.18.0+~cs1.19.1-1 has caused the Debian Bug report #1008200, regarding node-send: patched node-mime-types cause problems for other reverse-dependencies to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1008200: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-send Version: 0.17.2-2 Severity: important X-Debbugs-Cc: mer...@debian.org Hi Yadd, node-send is patched[1] to use node-mime-types instead of node-mime. However, this change is breaking node-shiny-server[2] build (not yet uploaded) with: | TypeError: send.mime.define is not a function |at Object. (/home/nilesh/packages/shinyserv/shiny-server/lib/router/directory-router.js:27:11) |at Module._compile (internal/modules/cjs/loader.js:999:30) |at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) |at Module.load (internal/modules/cjs/loader.js:863:32) mime-types used to have a "define" function which has been removed in version2 of the same. It is still not entirely clear to me as to why the patching was needed. If possible, can you revert it to use proper node-mime? If you happen to drop that patch, some tests fail due to new node-mime API; these can be fixed with a simple patch attached with this bug report. [1]: https://salsa.debian.org/js-team/node-send/-/blob/master/debian/patches/0001-use_ms_from_debug.patch#L15 [2]: https://salsa.debian.org/science-team/shiny-server Regards, Nilesh -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages node-send depends on: pn node-debug pn node-depd pn node-encodeurl pn node-escape-html pn node-etag pn node-fresh pn node-http-errors pn node-mime-types pn node-on-finished pn node-range-parser node-send recommends no packages. node-send suggests no packages. --- End Message --- --- Begin Message --- Source: node-send Source-Version: 0.18.0+~cs1.19.1-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-send, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1008...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-send package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 15:08:01 +0100 Source: node-send Architecture: source Version: 0.18.0+~cs1.19.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1008200 Changes: node-send (0.18.0+~cs1.19.1-1) unstable; urgency=medium . * Embed typescript declarations * New upstream version 0.18.0+~cs1.19.1 * Add dependency to node-ms and node-statuses and drop old patches (Closes: #1008200) * Add patch for mime >= 2 and statuses < 2 Checksums-Sha1: fe0c319bdd1ba64195ded39e7b67fcb82f49e070 3100 node-send_0.18.0+~cs1.19.1-1.dsc 0f2247ceb2f6cb1f8d6335ff9ad5f8cb0a3f22d0 6306 node-send_0.18.0+~cs1.19.1.orig-destroy.tar.gz ed4932b8a2a805f1fe362a70f4e62d0ac994e301 3634 node-send_0.18.0+~cs1.19.1.orig-types-send.tar.gz 3256e1cb1dbca2f639c3be3f78f056ce68bc20c8 24557 node-send_0.18.0+~cs1.19.1.orig.tar.gz b2d1a7a0ae433ee3bf107927333f01611c80 5008 node-send_0.18.0+~cs1.19.1-1.debian.tar.xz Checksums-Sha256: 53d5bff6d7350fb79976fccdd57a86b609bb45923b5372a42dadc1974b8ac208 3100 node-send_0.18.0+~cs1.19.1-1.dsc 97ee95ff7a8a12b9430dc4289e1845b05393fa3536892d233a429087a9d34c11 6306 node-send_0.18.0+~cs1.19.1.orig-destroy.tar.gz b3ec2c282405b24553912102d9336e094066ef8ceca077893c8eaf14c93a8711 3634 node-send_0.18.0+~cs1.19.1.orig-types-send.tar.gz
[Pkg-javascript-devel] twitter-bootstrap4_4.6.1+dfsg1-1_sourceonly.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 15:13:46 +0100 Source: twitter-bootstrap4 Architecture: source Version: 4.6.1+dfsg1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1008258 Changes: twitter-bootstrap4 (4.6.1+dfsg1-1) unstable; urgency=medium . * Team upload * New upstream version 4.6.1+dfsg1 (Closes: #1008258) Checksums-Sha1: 07faea26b9c2bac4dd765a043275b572161b854d 2344 twitter-bootstrap4_4.6.1+dfsg1-1.dsc e98a1a8175e6450e984d87a197e3afc1aa8716f2 2329588 twitter-bootstrap4_4.6.1+dfsg1.orig.tar.xz 81ce0fb4218f6b858285f44fc26e555daf364063 19332 twitter-bootstrap4_4.6.1+dfsg1-1.debian.tar.xz Checksums-Sha256: 04557c04dd2175305bdbbb537c8d6e758982b490b8a6f45e38ed4877b08a693f 2344 twitter-bootstrap4_4.6.1+dfsg1-1.dsc a2fdd5c181d592deb7ea7b1676188978cc60ebf182d1e6c4d6c712e0c6eb8a54 2329588 twitter-bootstrap4_4.6.1+dfsg1.orig.tar.xz b65d62ef6045b4db14c8510a6aa6c909409f7c39649e5c853e3e02b10e08ff33 19332 twitter-bootstrap4_4.6.1+dfsg1-1.debian.tar.xz Files: 04230a1517aea7ed9cff09d1a64e33aa 2344 javascript optional twitter-bootstrap4_4.6.1+dfsg1-1.dsc d0b7793db9e3976ce87f34dda946affa 2329588 javascript optional twitter-bootstrap4_4.6.1+dfsg1.orig.tar.xz 2686f13b9fb4725c0e7ee67a92a2cc34 19332 javascript optional twitter-bootstrap4_4.6.1+dfsg1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI9zrcACgkQ9tdMp8mZ 7ukmoA//WulY6jodNjBNdSv1pHHPsZPy9kEWexBHNf2VNlqVRw1CdTdi5bixyOFT zRTBstGCnhWHw3vPStN0MEK2yJM51rkSNdmbkFChd3gI/J9MSsFEsczgjotR73Ia RdNN9ixUXX9MzzFMNdqWjcyHT5AI8L7Qh4EIjjQplHWz3uKaAvlS82TV4PjhNJZh fg70x+Gp/qHEvC6uQLD8fo7k70bTH1+ONsjuBSfZnQe8BD6FCzT2U/isqnu8A89Q TNUlHVSo+CCByV19Vk6whaabQabzjYb/PaEnsDYWUKNtWnCx80P4g9tSnPLnaDkB a2NbGicJLva1/IdY5N2Ik0NZycMNGfPyBcjYbPgcxXP9BYR2+AUUfDWN8/S7ZX07 xJGm/awcDz7gaa7ZwNzO96VGYWvOvxQZY4JayTQDF6riNRuEK5YSdRTmWtwu4sRT SMHSPndfXm6MWXMYan8uzAxuqkhzwAK3X03gMFZ/qvHpT2Y/P86O9Tmx2YC5+//h kXg9FQCyNEYK/vmMovqNYN6//yMAM3l1k1iQRWuGubEA+a6mCVCrOBeu86BbX+BH LtNCnoU5QdmD6FJMW3DemkRM2EUFbI4Eo3fPT+k4Nft3Dd1ta5eOFsuFXg+CLC3r pLoyTSGENBtdKHOLVfCwlhxxVMLyG43399BUsz1ODJKiHqSfqt8= =tLjr -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-send_0.18.0+~cs1.19.1-1_sourceonly.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 15:08:01 +0100 Source: node-send Architecture: source Version: 0.18.0+~cs1.19.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 1008200 Changes: node-send (0.18.0+~cs1.19.1-1) unstable; urgency=medium . * Embed typescript declarations * New upstream version 0.18.0+~cs1.19.1 * Add dependency to node-ms and node-statuses and drop old patches (Closes: #1008200) * Add patch for mime >= 2 and statuses < 2 Checksums-Sha1: fe0c319bdd1ba64195ded39e7b67fcb82f49e070 3100 node-send_0.18.0+~cs1.19.1-1.dsc 0f2247ceb2f6cb1f8d6335ff9ad5f8cb0a3f22d0 6306 node-send_0.18.0+~cs1.19.1.orig-destroy.tar.gz ed4932b8a2a805f1fe362a70f4e62d0ac994e301 3634 node-send_0.18.0+~cs1.19.1.orig-types-send.tar.gz 3256e1cb1dbca2f639c3be3f78f056ce68bc20c8 24557 node-send_0.18.0+~cs1.19.1.orig.tar.gz b2d1a7a0ae433ee3bf107927333f01611c80 5008 node-send_0.18.0+~cs1.19.1-1.debian.tar.xz Checksums-Sha256: 53d5bff6d7350fb79976fccdd57a86b609bb45923b5372a42dadc1974b8ac208 3100 node-send_0.18.0+~cs1.19.1-1.dsc 97ee95ff7a8a12b9430dc4289e1845b05393fa3536892d233a429087a9d34c11 6306 node-send_0.18.0+~cs1.19.1.orig-destroy.tar.gz b3ec2c282405b24553912102d9336e094066ef8ceca077893c8eaf14c93a8711 3634 node-send_0.18.0+~cs1.19.1.orig-types-send.tar.gz 29f5c308d90bffecbed9ffc3fe6ec0e2ce90cd700f79ddafcb7834c647619da1 24557 node-send_0.18.0+~cs1.19.1.orig.tar.gz 62053e2fa50e1166c75cee2621e6e92b1907778ea56b66a1d6098b7c60b7f886 5008 node-send_0.18.0+~cs1.19.1-1.debian.tar.xz Files: 916805ccba74ee9a5f0007714b56879c 3100 javascript optional node-send_0.18.0+~cs1.19.1-1.dsc 4c28f9f9670828cba0478dcabe25159f 6306 javascript optional node-send_0.18.0+~cs1.19.1.orig-destroy.tar.gz e4c1cbe124e00f72178c8c2157d71568 3634 javascript optional node-send_0.18.0+~cs1.19.1.orig-types-send.tar.gz 6b4fd8f4d177246e66c01b68b0622a07 24557 javascript optional node-send_0.18.0+~cs1.19.1.orig.tar.gz ea4407c4901812f592a6d1ea4ff9ba4f 5008 javascript optional node-send_0.18.0+~cs1.19.1-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI9zVAACgkQ9tdMp8mZ 7umQkA/+OU5EDAn2O+Yg4jx2Um23Utm2mF5BRa8rnGWYAV2URcocE7iJr8zQedEM EUTeCgxQIcpG/vtPDB+MRsEZi7DlW9XBUv9HTZa1WNHjQ5GMUirk5QdGr84l1Dx9 HlMTeWCgQPmiwJwYiBeLTsNCx2ppQhr+g17OrUsISCnxCyvHVlicuwK2yiIYBvV7 3GfnQtP4i0ckRYXjDGgy8SEk+3YxigQ1JhGcp0x1/2sJEyG+sfZdotl6WC+D90X0 cIzelP6R+VbSmb19o8QmTEv4eWS+jAa4A5PIoUTwv8xXmn137YqvMxEY5hDFQAH9 2T9ZX6DxliPE1T02xnn/jrK6g99WwiCt1cDQP3rg8GYI1tmje7VbIW3GvYCBOmTg l2v6uFDmIJlaIc1p6+m+7A5R9MjZYNBgW8GmfQRJBkbMb3VakxA1vc6fjtObzzIu c4ZGbRck5y2OS9dR3kjQdh0ZIfljI0FllAsjUDJahh97HVAmwBJENgNVZKTCx+Mq zUb4WmQqRuN+J1BiNQ41W2HGmv8rAY7GO2+815YlXL+A/W2Al6rotFAz+YflT1BK NDeLXLsx7hdpVF5OpVHb8rFUA8terq7XF/fXonknkl13sSbCfVl7gKX+RrE8pGcc MwI0TbcIdakMk1M+9hmHTVcU4VGQ7KjLn0Mgv/aHk3pXsxa2x80= =GYDt -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Fwd: q2-composition - removed vega* from source tree
Quoting Nilesh Patra (2022-03-25 15:23:05) > On 3/25/22 6:55 PM, Jonas Smedegaard wrote: > > Quoting Nilesh Patra (2022-03-25 13:37:29) > >> Your message did not reach the js-team mailing list, hence > >> forwarding. > > > > This mailinglist is sensored - i.e. posts from people not subscribed > > gets held back and is manually screened for spam. > > > > Therefore, please give it some time before reposting. > > This is another good reason to move to lists.d.o instead. Less > processing emails, posting allowed by everyone :) Seems we are talking past each other here. Everyone *are* allowed to post, we actively *chose* sensoring, and I *volunteer* to screen it to avoid spam on the list. If you disagree and think that we should permit spam on our lists, then that is a different topic than that of my post, and it is not entirely clear to me if you simply misunderstood me or you actively want us to change. Please if you want to change our mailinglist handling then (preferably as a new separate thread) state your proposal explicitly, and let's discuss that. Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of pkg-js-tools_0.14.10_sourceonly.changes
pkg-js-tools_0.14.10_sourceonly.changes uploaded successfully to localhost along with the files: pkg-js-tools_0.14.10.dsc pkg-js-tools_0.14.10.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processed: Bug#1008229 marked as pending in pkg-js-tools
Processing control commands: > tag -1 pending Bug #1008229 [pkg-js-tools] pkg-js-tools: Issues with bundle packages with no main package Added tag(s) pending. -- 1008229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008229 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of twitter-bootstrap4_4.6.1+dfsg1-1_sourceonly.changes
twitter-bootstrap4_4.6.1+dfsg1-1_sourceonly.changes uploaded successfully to localhost along with the files: twitter-bootstrap4_4.6.1+dfsg1-1.dsc twitter-bootstrap4_4.6.1+dfsg1.orig.tar.xz twitter-bootstrap4_4.6.1+dfsg1-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Fwd: q2-composition - removed vega* from source tree
On 3/25/22 6:55 PM, Jonas Smedegaard wrote: Quoting Nilesh Patra (2022-03-25 13:37:29) Your message did not reach the js-team mailing list, hence forwarding. This mailinglist is sensored - i.e. posts from people not subscribed gets held back and is manually screened for spam. Therefore, please give it some time before reposting. This is another good reason to move to lists.d.o instead. Less processing emails, posting allowed by everyone :) -np OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-send_0.18.0+~cs1.19.1-1_sourceonly.changes
node-send_0.18.0+~cs1.19.1-1_sourceonly.changes uploaded successfully to localhost along with the files: node-send_0.18.0+~cs1.19.1-1.dsc node-send_0.18.0+~cs1.19.1.orig-destroy.tar.gz node-send_0.18.0+~cs1.19.1.orig-types-send.tar.gz node-send_0.18.0+~cs1.19.1.orig.tar.gz node-send_0.18.0+~cs1.19.1-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] Fwd: q2-composition - removed vega* from source tree
Quoting Nilesh Patra (2022-03-25 13:37:29) > Your message did not reach the js-team mailing list, hence forwarding. This mailinglist is sensored - i.e. posts from people not subscribed gets held back and is manually screened for spam. Therefore, please give it some time before reposting. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] pkg-js-tools_0.14.9~bpo11+1_amd64.changes is NEW
binary:dh-nodejs is NEW. binary:dh-nodejs is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of pkg-js-tools_0.14.9~bpo11+1_amd64.changes
pkg-js-tools_0.14.9~bpo11+1_amd64.changes uploaded successfully to localhost along with the files: pkg-js-tools_0.14.9~bpo11+1.dsc pkg-js-tools_0.14.9~bpo11+1.tar.xz dh-nodejs_0.14.9~bpo11+1_all.deb pkg-js-autopkgtest_0.14.9~bpo11+1_all.deb pkg-js-tools_0.14.9~bpo11+1_all.deb pkg-js-tools_0.14.9~bpo11+1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
Re: [Pkg-javascript-devel] q2-composition - removed vega* from source tree
[moved from the med packaging list to pkg-javascript-devel, not sure if I am a member, will find out, please CC me, just in case] Hi Nilesh, On 24.03.22 22:29, Nilesh Patra wrote: On 25 March 2022 12:48:33 am IST, "Steffen Möller" wrote: I am tempted to upload the package as it is. It is apparently version 4 of Vega that is expected, not version 5 that just entered the archive (many, many thanks!!) Now writing to this list, I should repeat to express my gratitude for you having addressed this. As a quick executive summary of the context: The upstream source tree is on https://github.com/qiime2/q2-composition/ with their vega-redistribution in https://github.com/qiime2/q2-composition/tree/master/q2_composition/assets/ancom/js : vega-embed.min.js vega.min.js and this was added four years ago. The qiime2 packages are about identifying bacteria and yeasts that live on us and in us and to learn about how this changes when we get sick, when we change the diet, when we get older, ... you guess it. Also in agriculture, it tells how the soil's bacteria change when salts change, temperature change, pesticides are applied, ... you get the picture. and they are apparently using https://github.com/vega/vega-embed which we yet do not have. However, those embedded vega files will affect the presentation of the results but not the results themselves and as such this package is already useful. I propose to craft a bug report early about the package to prevent its migration to testing and talk to upstream about. If the package is useful, I don't see much of a problem if it migrated to testing. It is somewhat tough to promote our qiime2 packaging to end users if they cannot be sure that they get the full reports. So, useful, I am confident, yes. But you lose that extra confidence in the software that should come with using a Debian package of it. This is why I would not want the package to migrate early but we could get it in and have the FTPmasters check it already. But I agree that it makes sense to contact upstream to ask if they would include vega-embed in the monorepo as well. Or one work around (meanwhile to buy time) could be to include vega-embed inside say, debian/resources And do something like: execute_before_dh_auto_configure: cp -a debian/resources $(CURDIR)/packages I would not mind in the sense that it gives some confidence that our package will behave exactly how upstream wants it to behave. On the other hand, this is not how progress works. If we would find it technically feasible to help qiime2 to update their code (does not look like much) to become compatible with the latest version then we should do that. And so this would help get vega-embed as well. Or in the worst case scenario, we could package node-vega-embed as a different source package. Since Vega is used by several qiime packages now, this seems like a good idea, except for that version problem that I interpreted from what I read in the sources. Now, the qiime packages would likely benefit from a transition to a later version of the vega JS, if my interpretation was correct in the first place and I am not confused over vega-embed, and whoever finds the time may find it rewarding to sync with upstream about it. https://salsa.debian.org/med-team/q2-composition What do you think? Let me know what you think, and also, this conversation should not be happening in the -med@ mailing list. Please consider sending query about this to the pkg-javascript-devel mailing list instead, since there are people who are specifically involved with JS stuff; even the vega.js maintainer would be easy to reach out. "Hello!" - and many thanks again Steffen -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1008258: libjs-bootstrap4: new version available upstream (v4.6.1)
Package: libjs-bootstrap4 Version: 4.5.2+dfsg1-7 Severity: wishlist I note that the latest version (of 4.*) available upstream is 4.6.1: https://github.com/twbs/bootstrap/releases/tag/v4.6.1 released 28 Oct 2021. The only reason I realised this is that openQA just switched to using 4.6.1. https://github.com/os-autoinst/openQA/pull/4579/files I would imagine that openQA should work well enough with 4.6.0 (not tried it yet), so if there's a good reason for not packaging 4.6.1, please say so and I'll feed that back to the openQA folks, and will then try to make sure that openQA supports both versions adequately. Cheers, Phil. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1008200: Bug#1008200: node-send: patched node-mime-types cause problems for other reverse-dependencies
Yadd, gentle ping on this? :) On 3/25/22 12:09 AM, Nilesh Patra wrote: On Thu, 24 Mar 2022 15:09:24 +0530 Nilesh Patra wrote: Package: node-send Version: 0.17.2-2 Severity: important X-Debbugs-Cc: mer...@debian.org Hi Yadd, node-send is patched[1] to use node-mime-types instead of node-mime. However, this change is breaking node-shiny-server[2] build (not yet uploaded) with: | TypeError: send.mime.define is not a function |at Object. (/home/nilesh/packages/shinyserv/shiny-server/lib/router/directory-router.js:27:11) |at Module._compile (internal/modules/cjs/loader.js:999:30) |at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10) |at Module.load (internal/modules/cjs/loader.js:863:32) mime-types used to have a "define" function which has been removed in version2 of the same. It is still not entirely clear to me as to why the patching was needed. If possible, can you revert it to use proper node-mime? If you happen to drop that patch, some tests fail due to new node-mime API; these can be fixed with a simple patch attached with this bug report. I forgot to attach earlier, should be attached with this mail. Regards, Nilesh OpenPGP_signature Description: OpenPGP digital signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Fwd: q2-composition - removed vega* from source tree
Your message did not reach the js-team mailing list, hence forwarding. Forwarded Message Subject: Re: q2-composition - removed vega* from source tree Date: Fri, 25 Mar 2022 10:03:02 +0100 From: Steffen Möller To: pkg-javascript-de...@lists.debian.org CC: Nilesh Patra [moved from the med packaging list to pkg-javascript-devel, not sure if I am a member, will find out, please CC me, just in case] Hi Nilesh, On 24.03.22 22:29, Nilesh Patra wrote: On 25 March 2022 12:48:33 am IST, "Steffen Möller" wrote: I am tempted to upload the package as it is. It is apparently version 4 of Vega that is expected, not version 5 that just entered the archive (many, many thanks!!) Now writing to this list, I should repeat to express my gratitude for you having addressed this. As a quick executive summary of the context: The upstream source tree is on https://github.com/qiime2/q2-composition/ with their vega-redistribution in https://github.com/qiime2/q2-composition/tree/master/q2_composition/assets/ancom/js : vega-embed.min.js vega.min.js and this was added four years ago. The qiime2 packages are about identifying bacteria and yeasts that live on us and in us and to learn about how this changes when we get sick, when we change the diet, when we get older, ... you guess it. Also in agriculture, it tells how the soil's bacteria change when salts change, temperature change, pesticides are applied, ... you get the picture. and they are apparently using https://github.com/vega/vega-embed which we yet do not have. However, those embedded vega files will affect the presentation of the results but not the results themselves and as such this package is already useful. I propose to craft a bug report early about the package to prevent its migration to testing and talk to upstream about. If the package is useful, I don't see much of a problem if it migrated to testing. It is somewhat tough to promote our qiime2 packaging to end users if they cannot be sure that they get the full reports. So, useful, I am confident, yes. But you lose that extra confidence in the software that should come with using a Debian package of it. This is why I would not want the package to migrate early but we could get it in and have the FTPmasters check it already. But I agree that it makes sense to contact upstream to ask if they wouldinclude vega-embed in the monorepo as well. Or one work around (meanwhile to buy time) could be to include vega-embed inside say, debian/resources And do something like: execute_before_dh_auto_configure: cp -a debian/resources $(CURDIR)/packages I would not mind in the sense that it gives some confidence that our package will behave exactly how upstream wants it to behave. On the other hand, this is not how progress works. If we would find it technically feasible to help qiime2 to update their code (does not look like much) to become compatible with the latest version then we should do that. And so this would help get vega-embed as well. Or in the worst case scenario, we could package node-vega-embed as a different source package. Since Vega is used by several qiime packages now, this seems like a good idea, except for that version problem that I interpreted from what I read in the sources. Now, the qiime packages would likely benefit from a transition to a later version of the vega JS, if my interpretation was correct in the first place and I am not confused over vega-embed, and whoever finds the time may find it rewarding to sync with upstream about it. https://salsa.debian.org/med-team/q2-composition What do you think? Let me know what you think, and also, this conversation should not be happening in the -med@ mailing list. Please consider sending query about this to the pkg-javascript-devel mailing list instead, since there are people who are specifically involved with JS stuff; even the vega.js maintainer would be easy to reach out. "Hello!" - and many thanks again Steffen -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1007248: Bug#1007248:
On 25 March 2022 4:51:44 pm IST, hardpenguin13 wrote: >Was also affected by this, ended up removing affected nodejs packages and >installing them again. No attempt to overwrite reported by dpkg. Same, I saw this yesterday and the same workaround worked. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#1007248:
Was also affected by this, ended up removing affected nodejs packages and installing them again. No attempt to overwrite reported by dpkg. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] pkg-js-tools_0.14.9~bpo11+1_source.changes REJECTED
Source-only uploads to NEW are not allowed. binary:dh-nodejs is NEW. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] node-builtins_4.1.0-1_sourceonly.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 25 Mar 2022 12:00:01 +0100 Source: node-builtins Architecture: source Version: 4.1.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Changes: node-builtins (4.1.0-1) unstable; urgency=medium . * Team upload * New upstream version 4.1.0 Checksums-Sha1: da45f54ceb3a0cfd94a236621e5a0a5b059d6328 2077 node-builtins_4.1.0-1.dsc d4a5c995d989f0e47da0768922801cffecc395d9 106650 node-builtins_4.1.0.orig.tar.gz 95c69a7f613b131b634c6c2835076dbe7ad34126 2688 node-builtins_4.1.0-1.debian.tar.xz Checksums-Sha256: a78b68bfcec0c6af99fe0c86305a6c92bd937c9c50f3bfe3e3b63522048f3425 2077 node-builtins_4.1.0-1.dsc ff37e989b3dfccfbdd9c4d3ca3090ada0217241236a3b5fab1ea77bfcefcbee2 106650 node-builtins_4.1.0.orig.tar.gz 4a8d92f3876f2805cf11aa5118d384ce2bf80a6b936328647f44026ea96aef25 2688 node-builtins_4.1.0-1.debian.tar.xz Files: acb63af354128832375d22b8ae51c7fd 2077 javascript optional node-builtins_4.1.0-1.dsc 581a0bec21edcfdf1a18b2052ab447a7 106650 javascript optional node-builtins_4.1.0.orig.tar.gz 5b06dda3fb5dbb16ba7de10a8b76b124 2688 javascript optional node-builtins_4.1.0-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmI9oQAACgkQ9tdMp8mZ 7uk7ng/+LgFaxX2Dw+ZkmREjlJXI0Nw5SWJk8QuiGJpuaw6YsKxtLe6ug685QKFY 3/taSIKhl9jM0HHeWxb++uRbU2TV/2MOKkuGwHBkvryMc9vSaNWw7YhMNePOqX/n iX8+udGVNqtE2UElaJG4kWUVRynLUglpdGjwdNWjbG8eZbfhOFjqxQ48oGiRokok N+SGNd19drW7AxKQpOJpz+bbVC7/GSIbO/hkhB6pbudeFD/YUCbqK+9cyQOTWQhl B/JgZigXWfxnllXhp3UJvEHjlbPehbJHNDScaTAcNQ3mL2mRAdX1RYQOw1e7gBvO esRLq20mr58KYEyb7T1+j0B5RdmxWpRrQstmV2zOnhJ0/60SH/ZCDi5uTuBd7Uiv NfeW9A0QtKPe84svCnwVntqRu2zw4F/nB2/dPC7IedVR+ptlxMnqWt3Ws08L9WNP EuepryZT3YfXeVJxJhye/7yvtP/pZXh3Sz5aUEZY8am+XyNLFl6wcSriOKzWxGcN hDrs3SEUzps6RYJ6tAF+pagL/ESTd6o5jbGEs+gGM+XeSGQ2Mc5C16ohREeH2LtH wbBwT64akUllPUxjvTdLOWHTWoKEeu8x1LUegbw4KuIEUFI6WNUiy0HHf0I9a/to 4zVOr41qyVfr7uRuRlQgkf+7f2NEzGkfKVP+tDfqj+BerDYIJkI= =csg1 -END PGP SIGNATURE- Thank you for your contribution to Debian. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of node-builtins_4.1.0-1_sourceonly.changes
node-builtins_4.1.0-1_sourceonly.changes uploaded successfully to localhost along with the files: node-builtins_4.1.0-1.dsc node-builtins_4.1.0.orig.tar.gz node-builtins_4.1.0-1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of pkg-js-tools_0.14.9~bpo11+1_source.changes
pkg-js-tools_0.14.9~bpo11+1_source.changes uploaded successfully to localhost along with the files: pkg-js-tools_0.14.9~bpo11+1.dsc pkg-js-tools_0.14.9~bpo11+1.tar.xz pkg-js-tools_0.14.9~bpo11+1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#994245: nodejs: improve bootstraping nodejs
On Fri, Mar 25, 2022 at 9:58 AM Bo YU wrote: > > > On Fri, Mar 25, 2022 at 4:12 PM Jérémy Lal wrote: > >> >> >> On Fri, Mar 25, 2022 at 7:10 AM Bo YU wrote: >> >>> hi, >>> >>> >> >> > Linking nodejs happens to use a lot of memory: make sure enough swap > space is available. > (I had similar crashes with 12GB of RAM and no swap). > Or the linker is broken on riscv64... let's hope it is not. > If you happen to reach the "building deb" stage, you can disable > -dbgsym package creation, > which is very long, with another build profile: noautodbgsym. > DEB_BUILD_PROFILES="nodoc nocheck noautodbgsym pkg.nodejs.nobuiltin" > Jérémy Today I checkout master-16.x, and I got: >>> sorry, add more useful info: >>> cc -o >>> /home/vimer/git/nodejs/out/Release/obj.target/llhttp/deps/llhttp/src/api.o >>> ../deps/llhttp/src/api.c '-DV8_DEPRECATION_WARNINGS' >>> '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_GLIBCXX_USE_CXX11_ABI=1' >>> '-DNODE_OPENSSL_CERT_STORE' '-D__STDC_FORMAT_MACROS' -I../deps/llhttp >>> -I../deps/llhttp/include -pthread -Wall -Wextra -Wno-unused-parameter >>> -fPIC -O3 -fno-omit-frame-pointer -MMD -MF >>> /home/vimer/git/nodejs/out/Release/.deps//home/vimer/git/nodejs/out/Release/obj.target/llhttp/deps/llhttp/src/api.o.d.raw >>> -fPIC -g -fPIC -g -fPIC -g -fPIC -g -c >>> make[3]: *** No rule to make target >>> '../deps/acorn/acorn/dist/acorn.js', needed by >>> '/home/vimer/git/nodejs/out/Release/obj/gen/node_javascript.cc'. Stop. >>> >> >> Maybe some symlink is missing, am checking it but it will take a >> while to rebuild. >> > > I pushed a fix for a mistake in debian/rules that happened while > renaming "nobuiltin". > At least it builds and produces deb packages here on amd64 without depending on nodejs itself. It have finished about compiling phrase, but dh_missing reports error: >>> make[1]: Entering directory '/home/vimer/git/nodejs' >>> make[1]: awk: No such file or directory >>> make[1]: awk: No such file or directory >>> sed 's/@DEB_HOST_MULTIARCH@/riscv64-linux-gnu/g' debian/libnode.install >>> > debian/libnode.install >>> sed -e 's/@DEB_HOST_MULTIARCH@/riscv64-linux-gnu/g' -e 's/@ABI@//g' >>> debian/libnode-dev.links.in > debian/libnode-dev.links >>> cp debian/nodejs.install.in debian/nodejs.install >>> echo "./lib /usr/share/nodejs/node/" >> debian/nodejs.install >>> deps_files="deps/v8/tools/splaytree.mjs deps/v8/tools/codemap.mjs >>> deps/v8/tools/consarray.mjs deps/v8/tools/csvparser.mjs >>> deps/v8/tools/profile.mjs deps/v8/tools/profile_view.mjs >>> deps/v8/tools/logreader.mjs deps/v8/tools/arguments.mjs >>> deps/v8/tools/tickprocessor.mjs deps/v8/tools/sourcemap.mjs >>> deps/v8/tools/tickprocessor-driver.mjs deps/acorn/acorn/dist/acorn.js >>> deps/acorn/acorn-walk/dist/walk.js deps/cjs-module-lexer/lexer.js"; \ >>> for src in $deps_files; do \ >>> dst=`dirname $src`; \ >>> echo "./$src /usr/share/nodejs/node/$dst" >> >>> debian/nodejs.install; \ >>> done >>> # and add uncompiled acorn >>> echo "./node-acorn/acorn/src /usr/share/nodejs/node/deps/acorn/acorn/" >>> >> debian/nodejs.install >>> echo "./node-acorn/acorn-walk/src >>> /usr/share/nodejs/node/deps/acorn/acorn-walk/" >> debian/nodejs.install >>> dh_install >>> make[1]: Leaving directory '/home/vimer/git/nodejs' >>>debian/rules override_dh_installdocs >>> make[1]: Entering directory '/home/vimer/git/nodejs' >>> dh_installdocs >>> find debian/nodejs-doc/usr/share/doc/nodejs-doc -name *.json -delete || >>> true >>> find: 'debian/nodejs-doc/usr/share/doc/nodejs-doc': No such file or >>> directory >>> make[1]: Leaving directory '/home/vimer/git/nodejs' >>>dh_installchangelogs -a >>>dh_installman -a >>>dh_lintian -a >>>dh_perl -a >>>dh_link -a >>>dh_strip_nondeterminism -a >>>dh_compress -a >>>dh_fixperms -a >>>dh_missing -a >>> dh_missing: warning: usr/lib/libnode.so.93 exists in debian/tmp but is >>> not installed to anywhere >>> The following debhelper tools have reported what they installed >>> (with files per package) >>> * dh_install: libnode-dev (179), libnode93 (0), nodejs (72), >>> nodejs-doc (0) >>> * dh_installdocs: libnode-dev (0), libnode93 (0), nodejs (0), >>> nodejs-doc (0) >>> * dh_installman: libnode-dev (0), libnode93 (0), nodejs (1), >>> nodejs-doc (0) >>> If the missing files are installed by another tool, please file >>> a bug against it. >>> When filing the report, if the tool is not part of debhelper >>> itself, please reference the >>> "Logging helpers and dh_missing" section from the "PROGRAMMING" >>> guide for debhelper (10.6.3+). >>> (in the debhelper package: >>> /usr/share/doc/debhelper/PROGRAMMING.gz) >>> Be sure to test with
[Pkg-javascript-devel] Bug#994245: nodejs: improve bootstraping nodejs
On Fri, Mar 25, 2022 at 4:12 PM Jérémy Lal wrote: > > > On Fri, Mar 25, 2022 at 7:10 AM Bo YU wrote: > >> hi, >> >> > > > Linking nodejs happens to use a lot of memory: make sure enough >>> swap >>> > space is available. >>> > (I had similar crashes with 12GB of RAM and no swap). >>> > Or the linker is broken on riscv64... let's hope it is not. >>> > If you happen to reach the "building deb" stage, you can disable >>> > -dbgsym package creation, >>> > which is very long, with another build profile: noautodbgsym. >>> > DEB_BUILD_PROFILES="nodoc nocheck noautodbgsym >>> pkg.nodejs.nobuiltin" >>> > Jérémy >>> Today I checkout master-16.x, and I got: >>> >> sorry, add more useful info: >> cc -o >> /home/vimer/git/nodejs/out/Release/obj.target/llhttp/deps/llhttp/src/api.o >> ../deps/llhttp/src/api.c '-DV8_DEPRECATION_WARNINGS' >> '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_GLIBCXX_USE_CXX11_ABI=1' >> '-DNODE_OPENSSL_CERT_STORE' '-D__STDC_FORMAT_MACROS' -I../deps/llhttp >> -I../deps/llhttp/include -pthread -Wall -Wextra -Wno-unused-parameter >> -fPIC -O3 -fno-omit-frame-pointer -MMD -MF >> /home/vimer/git/nodejs/out/Release/.deps//home/vimer/git/nodejs/out/Release/obj.target/llhttp/deps/llhttp/src/api.o.d.raw >> -fPIC -g -fPIC -g -fPIC -g -fPIC -g -c >> make[3]: *** No rule to make target >> '../deps/acorn/acorn/dist/acorn.js', needed by >> '/home/vimer/git/nodejs/out/Release/obj/gen/node_javascript.cc'. Stop. >> > > Maybe some symlink is missing, am checking it but it will take a while > to rebuild. > I pushed a fix for a mistake in debian/rules that happened while renaming "nobuiltin". >>> >>> At least it builds and produces deb packages here on amd64 without >>> depending on nodejs itself. >>> >>> It have finished about compiling phrase, but dh_missing reports error: >> make[1]: Entering directory '/home/vimer/git/nodejs' >> make[1]: awk: No such file or directory >> make[1]: awk: No such file or directory >> sed 's/@DEB_HOST_MULTIARCH@/riscv64-linux-gnu/g' debian/libnode.install >> > debian/libnode.install >> sed -e 's/@DEB_HOST_MULTIARCH@/riscv64-linux-gnu/g' -e 's/@ABI@//g' >> debian/libnode-dev.links.in > debian/libnode-dev.links >> cp debian/nodejs.install.in debian/nodejs.install >> echo "./lib /usr/share/nodejs/node/" >> debian/nodejs.install >> deps_files="deps/v8/tools/splaytree.mjs deps/v8/tools/codemap.mjs >> deps/v8/tools/consarray.mjs deps/v8/tools/csvparser.mjs >> deps/v8/tools/profile.mjs deps/v8/tools/profile_view.mjs >> deps/v8/tools/logreader.mjs deps/v8/tools/arguments.mjs >> deps/v8/tools/tickprocessor.mjs deps/v8/tools/sourcemap.mjs >> deps/v8/tools/tickprocessor-driver.mjs deps/acorn/acorn/dist/acorn.js >> deps/acorn/acorn-walk/dist/walk.js deps/cjs-module-lexer/lexer.js"; \ >> for src in $deps_files; do \ >> dst=`dirname $src`; \ >> echo "./$src /usr/share/nodejs/node/$dst" >> >> debian/nodejs.install; \ >> done >> # and add uncompiled acorn >> echo "./node-acorn/acorn/src /usr/share/nodejs/node/deps/acorn/acorn/" >> >> debian/nodejs.install >> echo "./node-acorn/acorn-walk/src >> /usr/share/nodejs/node/deps/acorn/acorn-walk/" >> debian/nodejs.install >> dh_install >> make[1]: Leaving directory '/home/vimer/git/nodejs' >>debian/rules override_dh_installdocs >> make[1]: Entering directory '/home/vimer/git/nodejs' >> dh_installdocs >> find debian/nodejs-doc/usr/share/doc/nodejs-doc -name *.json -delete || >> true >> find: 'debian/nodejs-doc/usr/share/doc/nodejs-doc': No such file or >> directory >> make[1]: Leaving directory '/home/vimer/git/nodejs' >>dh_installchangelogs -a >>dh_installman -a >>dh_lintian -a >>dh_perl -a >>dh_link -a >>dh_strip_nondeterminism -a >>dh_compress -a >>dh_fixperms -a >>dh_missing -a >> dh_missing: warning: usr/lib/libnode.so.93 exists in debian/tmp but is >> not installed to anywhere >> The following debhelper tools have reported what they installed >> (with files per package) >> * dh_install: libnode-dev (179), libnode93 (0), nodejs (72), >> nodejs-doc (0) >> * dh_installdocs: libnode-dev (0), libnode93 (0), nodejs (0), >> nodejs-doc (0) >> * dh_installman: libnode-dev (0), libnode93 (0), nodejs (1), >> nodejs-doc (0) >> If the missing files are installed by another tool, please file a >> bug against it. >> When filing the report, if the tool is not part of debhelper >> itself, please reference the >> "Logging helpers and dh_missing" section from the "PROGRAMMING" >> guide for debhelper (10.6.3+). >> (in the debhelper package: >> /usr/share/doc/debhelper/PROGRAMMING.gz) >> Be sure to test with dpkg-buildpackage -A/-B as the results may >> vary when only a subset is built >> If the omission is intentional or no other helper can take care >> of this
Re: [Pkg-javascript-devel] node12, node14, ... and alternatives to allow proper transitions
On Thu, Mar 24, 2022 at 11:38 AM Jérémy Lal wrote:
> Hi,
> (libnode72 is for nodejs 12, libnode83 is for nodejs 14)
>
> I made sure one can co-install libnode72 and libnode83, and removed
> libnode83 Breaks libnode72, because it made it really difficult
> to rebuild packages from unstable against the latest version of nodejs.
>
> when a libnode-dev (=12) addon is built, its dependencies are:
> libnode72
> nodejs:any
>
> However, if nodejs (=14), this doesn't work,
> because nodejs cannot load multiple libnodeXX
> $ node -e 'require("re2")'
> Will load libnode83 then re2 will load libnode72 and crash.
>
> The obvious solution is to let nodejs(=XX) install /usr/bin/nodeXX,
> and use an alternative /usr/bin/node symlink to point to the latest
> version.
>
> It will require fixing all node addons to depend on nodejs:any (=XX),
>
Maybe this change is just enough ?
Jérémy
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#994245: nodejs: improve bootstraping nodejs
On Fri, Mar 25, 2022 at 7:10 AM Bo YU wrote: > hi, > > On Fri, Mar 25, 2022 at 9:31 AM Jérémy Lal wrote: > >> >> >> On Fri, Mar 25, 2022 at 12:55 AM Jérémy Lal wrote: >> >>> >>> >>> On Fri, Mar 25, 2022 at 12:23 AM Jérémy Lal wrote: >>> On Fri, Mar 25, 2022 at 12:17 AM Bo YU wrote: > > > On Fri, Mar 25, 2022 at 7:11 AM Bo YU wrote: > >> On Thu, Mar 24, 2022 at 01:11:40AM +0100, Jérémy Lal wrote: >> > On Thu, Mar 24, 2022 at 1:05 AM Jérémy Lal <[1]kapo...@melix.org> >> > wrote: >> > >> > --build=any >> ... >> > >> > Hi, >> > After several times build fails about (on riscv hardware): >> > collect2: fatal error: ld terminated with signal 9 [Killed] >> > compilation terminated. >> > >> > Linking nodejs happens to use a lot of memory: make sure enough >> swap >> > space is available. >> > (I had similar crashes with 12GB of RAM and no swap). >> > Or the linker is broken on riscv64... let's hope it is not. >> > If you happen to reach the "building deb" stage, you can disable >> > -dbgsym package creation, >> > which is very long, with another build profile: noautodbgsym. >> > DEB_BUILD_PROFILES="nodoc nocheck noautodbgsym >> pkg.nodejs.nobuiltin" >> > Jérémy >> Today I checkout master-16.x, and I got: >> > sorry, add more useful info: > cc -o > /home/vimer/git/nodejs/out/Release/obj.target/llhttp/deps/llhttp/src/api.o > ../deps/llhttp/src/api.c '-DV8_DEPRECATION_WARNINGS' > '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_GLIBCXX_USE_CXX11_ABI=1' > '-DNODE_OPENSSL_CERT_STORE' '-D__STDC_FORMAT_MACROS' -I../deps/llhttp > -I../deps/llhttp/include -pthread -Wall -Wextra -Wno-unused-parameter > -fPIC -O3 -fno-omit-frame-pointer -MMD -MF > /home/vimer/git/nodejs/out/Release/.deps//home/vimer/git/nodejs/out/Release/obj.target/llhttp/deps/llhttp/src/api.o.d.raw > -fPIC -g -fPIC -g -fPIC -g -fPIC -g -c > make[3]: *** No rule to make target > '../deps/acorn/acorn/dist/acorn.js', needed by > '/home/vimer/git/nodejs/out/Release/obj/gen/node_javascript.cc'. Stop. > Maybe some symlink is missing, am checking it but it will take a while to rebuild. >>> >>> I pushed a fix for a mistake in debian/rules that happened while >>> renaming "nobuiltin". >>> >> >> At least it builds and produces deb packages here on amd64 without >> depending on nodejs itself. >> >> It have finished about compiling phrase, but dh_missing reports error: > make[1]: Entering directory '/home/vimer/git/nodejs' > make[1]: awk: No such file or directory > make[1]: awk: No such file or directory > sed 's/@DEB_HOST_MULTIARCH@/riscv64-linux-gnu/g' debian/libnode.install > > debian/libnode.install > sed -e 's/@DEB_HOST_MULTIARCH@/riscv64-linux-gnu/g' -e 's/@ABI@//g' > debian/libnode-dev.links.in > debian/libnode-dev.links > cp debian/nodejs.install.in debian/nodejs.install > echo "./lib /usr/share/nodejs/node/" >> debian/nodejs.install > deps_files="deps/v8/tools/splaytree.mjs deps/v8/tools/codemap.mjs > deps/v8/tools/consarray.mjs deps/v8/tools/csvparser.mjs > deps/v8/tools/profile.mjs deps/v8/tools/profile_view.mjs > deps/v8/tools/logreader.mjs deps/v8/tools/arguments.mjs > deps/v8/tools/tickprocessor.mjs deps/v8/tools/sourcemap.mjs > deps/v8/tools/tickprocessor-driver.mjs deps/acorn/acorn/dist/acorn.js > deps/acorn/acorn-walk/dist/walk.js deps/cjs-module-lexer/lexer.js"; \ > for src in $deps_files; do \ > dst=`dirname $src`; \ > echo "./$src /usr/share/nodejs/node/$dst" >> > debian/nodejs.install; \ > done > # and add uncompiled acorn > echo "./node-acorn/acorn/src /usr/share/nodejs/node/deps/acorn/acorn/" >> > debian/nodejs.install > echo "./node-acorn/acorn-walk/src > /usr/share/nodejs/node/deps/acorn/acorn-walk/" >> debian/nodejs.install > dh_install > make[1]: Leaving directory '/home/vimer/git/nodejs' >debian/rules override_dh_installdocs > make[1]: Entering directory '/home/vimer/git/nodejs' > dh_installdocs > find debian/nodejs-doc/usr/share/doc/nodejs-doc -name *.json -delete || > true > find: 'debian/nodejs-doc/usr/share/doc/nodejs-doc': No such file or > directory > make[1]: Leaving directory '/home/vimer/git/nodejs' >dh_installchangelogs -a >dh_installman -a >dh_lintian -a >dh_perl -a >dh_link -a >dh_strip_nondeterminism -a >dh_compress -a >dh_fixperms -a >dh_missing -a > dh_missing: warning: usr/lib/libnode.so.93 exists in debian/tmp but is not > installed to anywhere > The following debhelper tools have reported what they installed > (with files per package) > * dh_install: libnode-dev (179), libnode93 (0), nodejs (72), > nodejs-doc (0) > * dh_installdocs: libnode-dev (0), libnode93 (0), nodejs (0), > nodejs-doc (0) > * dh_installman: libnode-dev (0), libnode93 (0), nodejs (1), > nodejs-doc (0) >
[Pkg-javascript-devel] pkg-js-tools_0.14.9~bpo11+1_sourceonly.changes REJECTED
Source-only uploads to NEW are not allowed. binary:dh-nodejs is NEW. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processing of pkg-js-tools_0.14.9~bpo11+1_sourceonly.changes
pkg-js-tools_0.14.9~bpo11+1_sourceonly.changes uploaded successfully to localhost along with the files: pkg-js-tools_0.14.9~bpo11+1.dsc pkg-js-tools_0.14.9~bpo11+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#994245: nodejs: improve bootstraping nodejs
hi, On Fri, Mar 25, 2022 at 9:31 AM Jérémy Lal wrote: > > > On Fri, Mar 25, 2022 at 12:55 AM Jérémy Lal wrote: > >> >> >> On Fri, Mar 25, 2022 at 12:23 AM Jérémy Lal wrote: >> >>> >>> >>> On Fri, Mar 25, 2022 at 12:17 AM Bo YU wrote: >>> On Fri, Mar 25, 2022 at 7:11 AM Bo YU wrote: > On Thu, Mar 24, 2022 at 01:11:40AM +0100, Jérémy Lal wrote: > > On Thu, Mar 24, 2022 at 1:05 AM Jérémy Lal <[1]kapo...@melix.org> > > wrote: > > > > --build=any > ... > > > > Hi, > > After several times build fails about (on riscv hardware): > > collect2: fatal error: ld terminated with signal 9 [Killed] > > compilation terminated. > > > > Linking nodejs happens to use a lot of memory: make sure enough > swap > > space is available. > > (I had similar crashes with 12GB of RAM and no swap). > > Or the linker is broken on riscv64... let's hope it is not. > > If you happen to reach the "building deb" stage, you can disable > > -dbgsym package creation, > > which is very long, with another build profile: noautodbgsym. > > DEB_BUILD_PROFILES="nodoc nocheck noautodbgsym > pkg.nodejs.nobuiltin" > > Jérémy > Today I checkout master-16.x, and I got: > sorry, add more useful info: cc -o /home/vimer/git/nodejs/out/Release/obj.target/llhttp/deps/llhttp/src/api.o ../deps/llhttp/src/api.c '-DV8_DEPRECATION_WARNINGS' '-DV8_IMMINENT_DEPRECATION_WARNINGS' '-D_GLIBCXX_USE_CXX11_ABI=1' '-DNODE_OPENSSL_CERT_STORE' '-D__STDC_FORMAT_MACROS' -I../deps/llhttp -I../deps/llhttp/include -pthread -Wall -Wextra -Wno-unused-parameter -fPIC -O3 -fno-omit-frame-pointer -MMD -MF /home/vimer/git/nodejs/out/Release/.deps//home/vimer/git/nodejs/out/Release/obj.target/llhttp/deps/llhttp/src/api.o.d.raw -fPIC -g -fPIC -g -fPIC -g -fPIC -g -c make[3]: *** No rule to make target '../deps/acorn/acorn/dist/acorn.js', needed by '/home/vimer/git/nodejs/out/Release/obj/gen/node_javascript.cc'. Stop. >>> >>> Maybe some symlink is missing, am checking it but it will take a while >>> to rebuild. >>> >> >> I pushed a fix for a mistake in debian/rules that happened while renaming >> "nobuiltin". >> > > At least it builds and produces deb packages here on amd64 without > depending on nodejs itself. > > It have finished about compiling phrase, but dh_missing reports error: make[1]: Entering directory '/home/vimer/git/nodejs' make[1]: awk: No such file or directory make[1]: awk: No such file or directory sed 's/@DEB_HOST_MULTIARCH@/riscv64-linux-gnu/g' debian/libnode.install > debian/libnode.install sed -e 's/@DEB_HOST_MULTIARCH@/riscv64-linux-gnu/g' -e 's/@ABI@//g' debian/ libnode-dev.links.in > debian/libnode-dev.links cp debian/nodejs.install.in debian/nodejs.install echo "./lib /usr/share/nodejs/node/" >> debian/nodejs.install deps_files="deps/v8/tools/splaytree.mjs deps/v8/tools/codemap.mjs deps/v8/tools/consarray.mjs deps/v8/tools/csvparser.mjs deps/v8/tools/profile.mjs deps/v8/tools/profile_view.mjs deps/v8/tools/logreader.mjs deps/v8/tools/arguments.mjs deps/v8/tools/tickprocessor.mjs deps/v8/tools/sourcemap.mjs deps/v8/tools/tickprocessor-driver.mjs deps/acorn/acorn/dist/acorn.js deps/acorn/acorn-walk/dist/walk.js deps/cjs-module-lexer/lexer.js"; \ for src in $deps_files; do \ dst=`dirname $src`; \ echo "./$src /usr/share/nodejs/node/$dst" >> debian/nodejs.install; \ done # and add uncompiled acorn echo "./node-acorn/acorn/src /usr/share/nodejs/node/deps/acorn/acorn/" >> debian/nodejs.install echo "./node-acorn/acorn-walk/src /usr/share/nodejs/node/deps/acorn/acorn-walk/" >> debian/nodejs.install dh_install make[1]: Leaving directory '/home/vimer/git/nodejs' debian/rules override_dh_installdocs make[1]: Entering directory '/home/vimer/git/nodejs' dh_installdocs find debian/nodejs-doc/usr/share/doc/nodejs-doc -name *.json -delete || true find: 'debian/nodejs-doc/usr/share/doc/nodejs-doc': No such file or directory make[1]: Leaving directory '/home/vimer/git/nodejs' dh_installchangelogs -a dh_installman -a dh_lintian -a dh_perl -a dh_link -a dh_strip_nondeterminism -a dh_compress -a dh_fixperms -a dh_missing -a dh_missing: warning: usr/lib/libnode.so.93 exists in debian/tmp but is not installed to anywhere The following debhelper tools have reported what they installed (with files per package) * dh_install: libnode-dev (179), libnode93 (0), nodejs (72), nodejs-doc (0) * dh_installdocs: libnode-dev (0), libnode93 (0), nodejs (0), nodejs-doc (0) * dh_installman: libnode-dev (0), libnode93 (0), nodejs (1), nodejs-doc (0) If the missing files are installed by another tool, please file a bug against it. When filing the report, if the tool is not part of debhelper itself, please reference the "Logging helpers and dh_missing" section from
