[Pkg-javascript-devel] node-temp is marked for autoremoval from testing
node-temp 0.8.3-1 is marked for autoremoval from testing on 2018-06-16 It is affected by these RC bugs: 834915: node-temp: FTBFS (AssertionError: temp.createWriteStream did not create a file) -- 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-gyp 3.6.2-2 MIGRATED to testing
FYI: The status of the node-gyp source package in Debian's testing distribution has changed. Previous version: 3.6.2-1 Current version: 3.6.2-2 -- 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-querystring 0.2.0-2 MIGRATED to testing
FYI: The status of the node-querystring source package in Debian's testing distribution has changed. Previous version: 0.2.0-1 Current version: 0.2.0-2 -- 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
Re: [Pkg-javascript-devel] alioth is down: what to do with those 119 packages ?
(incidentally, doesn't js have a list on @l.d.o already?) On Fri, Jun 01, 2018 at 07:38:46AM +0200, Paolo Greppi wrote: > Hi as you know, since yesterday alioth is dead. finally. > There's still quite a few packages from the js-team sitting in the > new queue with the vcs* fields in debian/control set to: > https://anonscm.debian.org/cgit/pkg-javascript/... > > As mentioned here: > https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2018-May/026296.html > this work has been planned for a while. > > My proposal is to ask ftp-master to reject them all. > This is fair to them and will clean up the queue. > After that, we have all the time in the universe to reassign ITPs, > prepare team uploads etc. 1) we could have redirects added to https://salsa.debian.org/salsa/AliothRewriter/ And there already is a long list (1150 lines) for pkg-js' packages. If any are missing they could/should be added. This would amke the Vcs-* fields still perfectly valid. The very goal of that thing is to avoid having to do thousands of uploads only changing Vcs-*. 2) if really wanted, the packages could be updated while still being in NEW: just upload a newever version, then they will both be accepted at the same time whenever they will be processed. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP 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#899334: marked as done (node-sha.js: FTBFS and autopkgtest failure on 32-bit)
Your message dated Fri, 01 Jun 2018 13:21:33 + with message-id and subject line Bug#899334: fixed in node-sha.js 2.4.11-2 has caused the Debian Bug report #899334, regarding node-sha.js: FTBFS and autopkgtest failure on 32-bit 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.) -- 899334: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899334 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: node-sha.js Version: 2.4.11-1 Severity: serious Tags: patch Forwarded: https://github.com/crypto-browserify/sha.js/pull/56 User: debian...@lists.debian.org Usertags: needs-update Hi Maintainer Since the upload of 2.4.11-1 to unstable, node-sha.js FTBFS and fails its autopkgtests on 32-bit architectures [1][2] with the following error: RangeError: "size" argument must not be larger than 1073741823 at Function.Buffer.alloc (buffer.js:233:3) at Test. (/build/1st/node-sha.js-2.4.11/test/test.js:90:24) at Test.bound [as _cb] (/usr/lib/nodejs/tape/lib/test.js:76:32) at Test.run (/usr/lib/nodejs/tape/lib/test.js:95:10) at Test.bound [as run] (/usr/lib/nodejs/tape/lib/test.js:76:32) at Immediate.next [as _onImmediate] (/usr/lib/nodejs/tape/lib/results.js:71:15) at runCallback (timers.js:794:20) at tryOnImmediate (timers.js:752:5) at processImmediate [as _immediateCallback] (timers.js:729:5) Regards Graham [1] https://tests.reproducible-builds.org/debian/history/i386/node-sha.js.html [2] https://tests.reproducible-builds.org/debian/history/armhf/node-sha.js.html --- End Message --- --- Begin Message --- Source: node-sha.js Source-Version: 2.4.11-2 We believe that the bug you reported is fixed in the latest version of node-sha.js, 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 899...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastien Roucariès (supplier of updated node-sha.js 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, 01 Jun 2018 15:15:51 +0200 Source: node-sha.js Binary: node-sha.js Architecture: source Version: 2.4.11-2 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Bastien Roucariès Description: node-sha.js - Streamable SHA hashes in pure javascript Closes: 899334 Changes: node-sha.js (2.4.11-2) unstable; urgency=medium . * Bug fix: "FTBFS and autopkgtest failure on 32-bit", thanks to Graham Inggs (Closes: #899334). Checksums-Sha1: 966be8012c90a509927d46b00086875c5ed36829 2284 node-sha.js_2.4.11-2.dsc a125036f1659eab6bdc8f6ce3491927bdad2c54b 4772 node-sha.js_2.4.11-2.debian.tar.xz 8d1c6482cb4462f0464858572d497cd43033dabd 7821 node-sha.js_2.4.11-2_source.buildinfo Checksums-Sha256: 20205e68545071d3bcdf7644516cf981496c2c7034e07a231488f57de572d489 2284 node-sha.js_2.4.11-2.dsc 3876eb735c6bd640afe44371fb72725c945bca4a136acf0958d46fd88c44ae20 4772 node-sha.js_2.4.11-2.debian.tar.xz 40cdc215a9bcbc2098af769eb469aadf539da4970a9a4102f2f05e24d5dfc53b 7821 node-sha.js_2.4.11-2_source.buildinfo Files: 9200ce184e442cee1c8638b34da20651 2284 javascript optional node-sha.js_2.4.11-2.dsc d1d1d34d573ead90e79d7a84fad8f810 4772 javascript optional node-sha.js_2.4.11-2.debian.tar.xz f1ffa8019640b772ba285ffd36afff5d 7821 javascript optional node-sha.js_2.4.11-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAlsRR6wACgkQADoaLapB CF8oNA/9ENLigcCf1PfDC/NUpYyhHdcQJded1RhVm+QGynPFQrF/IX4YaY3DFEoz RLlWFqMAWyIszPT36mZtUujGitoaF4FjWE74RhWmSpMmHuT3P0mdVgSlgmlGkbJY al3ADq0ZauxT0Td7BesO+ucbG5Ve2yIWSxXEl4VjrwrWDu6FAPfu2g2NXr5kO3M4 NAHa0RWsMaAG7sDuJ/zHx5wA5TRRg/SlW9yIRKZDRWT6G2I6t2RYeszs1FrmVwlS JqRuVG/M4wxTT7DIvDfCAMkO7RvvarHvxBczMes7WtLXa6qldP4UR6gBecDm2hY4 DOQAyKlFnOyNhqpcfUOqVfLMETYsvLMAf/ndmA8qKVnIQ44W+7B+P+sugEa+DNhx CDkoKN+z3Q5Y/sWMZSGs58nzak9UfW9y55SDi5o1BswHg+COdOx7VynrOO+5MDJ4 5fQPJfe600M6kAhtf8JAXTEeQT4AxrCoyoENOWfBMzEWIhWQeyKfdy1qELOORuri W08DjpP1LOQ5YGCSmjNG9VKZzPswkeJpggyzevZR9/bevcIlHRVAGbutEEWOmFmB 5AQ6SwZQFxxVigHm9WxgS08039c2iSmoHurTJzoUQMev5Y2X64hqLdYEL7/JtYzn ozLEQ79VkPUwtItEUFnzQIjlwPon3LdABL8i98QFAZyoA0ZBkus= =xzz+ -END PGP
[Pkg-javascript-devel] node-retape_0.0.3-3_source.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 01 Jun 2018 15:04:25 +0200 Source: node-retape Binary: node-retape Architecture: source Version: 0.0.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Bastien Roucariès Description: node-retape - CommonJS test to tape adapter Changes: node-retape (0.0.3-3) unstable; urgency=medium . * Move to salsa * Bump policy and compat (no changes) Checksums-Sha1: a974ccbd0296801014527dba71956ddc66547aa7 2150 node-retape_0.0.3-3.dsc ac99b7375b3a78b9b703b9d375faffe7ff6997b4 2900 node-retape_0.0.3-3.debian.tar.xz 11342dfdae3db89ea0a61f2852acdc5707bcfdf5 7797 node-retape_0.0.3-3_source.buildinfo Checksums-Sha256: 4456fbe6b36b9e2b169cc6306bedd15a729e46b1a227bd9feaf7215d89b2bca3 2150 node-retape_0.0.3-3.dsc 309f204a350e9b0041133aeb4b22cbcb16de454026dba7f5ad9684db8d1f274d 2900 node-retape_0.0.3-3.debian.tar.xz 4a09256fa97fb7c2c69fb680bd38a91f0600ffb1728ad90cde27e0d559084522 7797 node-retape_0.0.3-3_source.buildinfo Files: f7be6c3c73c3f127c4fa665347843d6c 2150 javascript optional node-retape_0.0.3-3.dsc 9e92f19f429930cba9c48c5196302c1f 2900 javascript optional node-retape_0.0.3-3.debian.tar.xz 0cfb07a7d96e118bc85e855483717e63 7797 javascript optional node-retape_0.0.3-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXQGHuUCiRbrXsPVqADoaLapBCF8FAlsRRUEACgkQADoaLapB CF/gEg//fdI//igb514TkNW2t2yv2ivSTIOw09k7l16OY6Mlta3CZewkwU9Tpvrc l65yKMA81H5AA0vyD/p/GBaI36epafJwM6RmXysae/60zWNUUIW76f+lsrXIvhi7 7Rnsh+61NFplcJa3ttallqZP59JwseVdIYgx5aaIXXeuJRLH4sS3hmsTmoN3LlUi c/io/thpIj6I/ohhMxR6CVArISMyIes47V8k0gEOTd/H2iM1WoIocKHHnJhKiVzt YHA0mdpzJahwIXx9mdiellpK2qFZDQj8jhik4glORc5kQO3mj/Yr7te43YnpNa4U RhUUMEWkEin2uVqA8wygpyKTPbKIQfk8VzXKWaGwjSfaLOBqv28ToDsNq+n3Gu9z kL2ZqqW+eWr+xTdaIt5s5V6kXBaPBPkWqoMPt9yqmf9T6ASudZc//2lW0JVWvwdi ZiF2Z/LeMPKE0BkU31I2sXHDwvqGAD9CEqjVBy2ikcoWmXEVXCvFls0AQFJEv4JD y0kKyctTCgCa9Ys3uL/IkuupRATarA/WzKeM96JElAKtyxV2gkMFQfCkHZ0691IE XVcrdiDC0k190O7pn7vzMeAZQzedFaVb5tZh3OACzc2VGd+D36SLYlx2wF7y3cI7 wv5xKspe5eYIjcHFAlLbdhEPYDnnImIH1v9cY0qhpdw7gYyjxIY= =pBmv -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] Bug#834915: node-temp: FTBFS (AssertionError: temp.createWriteStream did not create a file)
As promised, full build logs available here: https://people.debian.org/~sanvila/build-logs/node-temp/ This time I tried 100 times and it failed 96 times, so it failed 96% of the time. BTW: My autobuilders have nothing to do with reproducible builds autobuilders. They use pbuilder, I use sbuild. They have multiple CPUs, I usually have a single CPU. But in either case, the fact that this happens in both sets of autobuilders makes this unlikely to be a local problem in my side. Thanks. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Processed: Re: node-temp: FTBFS (AssertionError: temp.createWriteStream did not create a file)
Processing commands for cont...@bugs.debian.org:
> reopen 834915
Bug #834915 {Done: Paolo Greppi } [src:node-temp]
node-temp: FTBFS (AssertionError: temp.createWriteStream did not create a file)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions node-temp/0.8.3-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
834915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834915
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
Re: [Pkg-javascript-devel] alioth is down: what to do with those 119 packages ?
Il 01/06/2018 08:09, Pirate Praveen ha scritto: > On Friday 01 June 2018 11:08 AM, Paolo Greppi wrote: >> Hi as you know, since yesterday alioth is dead. > > I think there will be a read only mirror. > >> There's still quite a few packages from the js-team sitting in the >> new queue with the vcs* fields in debian/control set to: >> https://anonscm.debian.org/cgit/pkg-javascript/... >> >> To find out which they are, try the "Debian NEW Packages fancy view" at: >> http://212.237.56.209/ >> check the "Only show active packages" checkbox then type this as search >> string: >> "https://anonscm.debian.org/cgit/pkg-javascript/; >> >> They are 119 ATM. >> >> As mentioned here: >> https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2018-May/026296.html >> this work has been planned for a while. >> >> Unfortunately most of the ITP owners failed to even register on salsa, nor >> have >> we prepared team uploads. >> You can track the WIP here: >> https://salsa.debian.org/js-team/current_itps/boards?label_name[]=NEW-alioth >> (BTW, they are 114 there so 5 are missing) >> >> Currently only node-ansicolors and node-classnames are in the RFC (request >> for comments) column i.e. almost ready for sponsoring. >> >> My proposal is to ask ftp-master to reject them all. >> This is fair to them and will clean up the queue. > > I don't think changing vcs url is worth a reject. > >> After that, we have all the time in the universe to reassign ITPs, >> prepare team uploads etc. >> >> Paolo Weren't packages supposed to be lintian-clean before uploading for the 1st time ? Those 119 are not because they get W vcs-deprecated-in-debian-infrastructure. And that's the FORMAL issue. But the real issue is that neither the ITP owner nor the team have been able to fix this simple issue, in all those months. For the new contributors, the question is whether they are "able and interested in not only releasing packages but also in maintaining them": https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2017-January/017236.html For the team, the question is whether we have the resources to make all those NMUs and sponsored uploads. If we are not sure about these things, it's better to be realistic and not dump on ftp-master the load of rejecting them. Let's rather ask for rejection: we'll gain in credibility ! Paolo -- 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] alioth is down: what to do with those 119 packages ?
On Friday 01 June 2018 11:08 AM, Paolo Greppi wrote: > Hi as you know, since yesterday alioth is dead. I think there will be a read only mirror. > There's still quite a few packages from the js-team sitting in the > new queue with the vcs* fields in debian/control set to: > https://anonscm.debian.org/cgit/pkg-javascript/... > > To find out which they are, try the "Debian NEW Packages fancy view" at: > http://212.237.56.209/ > check the "Only show active packages" checkbox then type this as search > string: > "https://anonscm.debian.org/cgit/pkg-javascript/; > > They are 119 ATM. > > As mentioned here: > https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2018-May/026296.html > this work has been planned for a while. > > Unfortunately most of the ITP owners failed to even register on salsa, nor > have > we prepared team uploads. > You can track the WIP here: > https://salsa.debian.org/js-team/current_itps/boards?label_name[]=NEW-alioth > (BTW, they are 114 there so 5 are missing) > > Currently only node-ansicolors and node-classnames are in the RFC (request > for comments) column i.e. almost ready for sponsoring. > > My proposal is to ask ftp-master to reject them all. > This is fair to them and will clean up the queue. I don't think changing vcs url is worth a reject. > After that, we have all the time in the universe to reassign ITPs, > prepare team uploads etc. > > Paolo > signature.asc 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
