Bug#849021: ITP: node-split -- split a Text Stream into a Line Stream

Package: wnpp Severity: wishlist Owner: "Jérémy Lal" <kapo...@melix.org> * Package name: node-split Version : 1.0.0 Upstream Author : Dominic Tarr <dominic.t...@gmail.com> (http://bit.ly/dominictarr) * URL : http://github.com/domin

Bug#849007: ITP: node-ap -- Like Function.bind without setting "this"

Package: wnpp Severity: wishlist Owner: "Jérémy Lal" <kapo...@melix.org> * Package name: node-ap Version : 0.2.0 Upstream Author : James Halliday <m...@substack.net> (http://substack.net) * URL : https://github.com/substack/node-ap * L

Bug#848886: node-stringprep: Please use dh_nodejs

Source: node-stringprep Severity: normal Hi, dh_nodejs should be called during build, (the package will need to depend on nodejs-dev). This ensures this addon depends on nodejs-abi-xx metapackage. Thank you for your help, Jérémy -- System Information: Debian Release: stretch/sid APT

Bug#848884: RM: node-topcube -- ROM; dead upstream; RC-buggy; unmaintained

Package: ftp.debian.org Severity: normal This package has no reverse dependencies, is basically useless too, and need much work for the webkit2gtk transition. Please remove it, Jérémy.

Bug#848827: reportbug: Wrongly appends @hostname to "My Name <my@hostname>"

Package: reportbug Version: 7.1.1 Severity: normal Hi, i tried to reportbug using 7.1.1, and From header was set to "Jérémy Lal <kapo...@melix.org>"@imac.localdomain Reverting to 6.6.6 fixes the issue. Thanks, Jérémy. -- Package-specific info: ** Environment settings

Bug#848825: lintian: Does not applies source-is-missing overrides unless path has wildcard

Package: lintian Version: 2.5.49 Severity: normal This doesn't override anything: source/lintian-overrides source-is-missing deps/v8/benchmarks/regexp.js source-is-missing doc/api_assets/sh_javascript.min.js source-is-missing test/fixtures/throws_error5.js source-is-missing

Bug#847553: epiphany-browser: display not updated (after some random time)

Package: libx11-6 Followup-For: Bug #847553 Control: reassign -1 epiphany-browser 3.22.3-1 Downgrading libx11-6 didn't fix the issue after all. Reassigning to epiphany.

Bug#847553: epiphany-browser: display not updated (after some random time)

Package: epiphany-browser Version: 3.22.3-1 Followup-For: Bug #847553 Control: reassign -1 libx11-6 1.6.4-2 I downgraded libx11-6 to version 1.6.3-1 since this morning, and did not reproduce the problem since. I think it's best to reassign to that package. Jérémy

Bug#847553: epiphany-browser: display not updated (after some random time)

Package: epiphany-browser Version: 3.22.3-1 Severity: important On about any web site, the page display stops being updated from time to time (several times a day here): - the mouse pointer still changes on hover - if i click on an anchor on a single page website, url changes but display is still

Bug#834915: node-temp: FTBFS (AssertionError: temp.createWriteStream did not create a file)

2016-12-08 16:30 GMT+01:00 Santiago Vila : > retitle 834915 node-temp: FTBFS (AssertionError: temp.createWriteStream did > not create a file) > thanks > > It really happens all the time, and it also happens here: > >

Bug#828457: nodejs: FTBFS with openssl 1.1.0

2016-11-03 17:49 GMT+01:00 Kurt Roeckx : > On Thu, Nov 03, 2016 at 10:42:50AM -0400, Sandro Tosi wrote: >> On Sun, 11 Sep 2016 20:10:53 +0200 =?UTF-8?B?SsOpcsOpbXkgTGFs?= >> wrote: >> > 2016-09-11 14:25 GMT+02:00 Kurt Roeckx : >> > >> > > tags

Bug#847091: update node-extend to latest upstream release

2016-12-05 15:32 GMT+01:00 Pirate Praveen : > package: node-extend > version: 2.0.0-1 > severity: wishlist > control: block 847052 by -1 > > node-through2-filter depends on node-extend (>= 4.0.0) Do you mean node-xtend ? Jérémy

Bug#846191: ITP: node-json-stable-stringify -- deterministic JSON.stringify()

Hello 2016-11-29 7:51 GMT+01:00 Pirate Praveen : > Package: wnpp > Severity: wishlist > Owner: Pirate Praveen > X-Debbugs-CC: debian-de...@lists.debian.org > > * Package name: node-json-stable-stringify > Version : 1.0.1 > Upstream Author :

Bug#846016: devscripts: debuild clean fails with bad invocation of dpkg-buildpackage

Package: devscripts Version: 2.16.10 Severity: important Hi, dpkg-buildpackage -rfakeroot -us -uc --hook-check=cd ..; clean --check-command=lintian dpkg-buildpackage: error: unknown option or argument clean Use --help for program usage information. debuild: fatal error at line 1100:

Bug#844905: node-nan: FTBFS: Tests failures

2016-11-27 7:06 GMT+01:00 Pirate Praveen : > On Sat, 19 Nov 2016 08:02:29 +0100 Lucas Nussbaum wrote: >> During a rebuild of all packages in sid, your package failed to build on >> amd64. > > > From upstream discussion, > > "The bug is that the Global

Bug#845745: node-rimraf: please make the build reproducible

2016-11-26 13:23 GMT+01:00 Chris Lamb : > Source: node-rimraf > Version: 2.5.4-1 > Severity: wishlist > Tags: patch > User: reproducible-bui...@lists.alioth.debian.org > Usertags: umask > X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org > > Hi, > > Whilst working on the

Bug#845617: node-nopt: FTBFS: Error: Cannot find module 'abbrev'

2016-11-25 9:32 GMT+01:00 Chris Lamb : > Source: node-nopt > Version: 3.0.6-2 > Severity: serious > Justification: fails to build from source > User: reproducible-bui...@lists.alioth.debian.org > Usertags: ftbfs > X-Debbugs-Cc: reproducible-b...@lists.alioth.debian.org > > Dear

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-24 9:12 GMT+01:00 Joerg Jaspert <jo...@debian.org>: > On 14501 March 1977, Jérémy Lal wrote: >>> - This is not a blanket for having embedded code copies all over the >>>place. >>>So yes, this should Provide: all those submodules and make t

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-24 0:42 GMT+01:00 Joerg Jaspert : > On 14500 March 1977, Michael Prokop wrote: > >>> > Overall, I'm not sure we are providing our users something good with >>> > the current situation. Though what realistic options do we have get >>> > forward here? Any thoughts? > > It

Bug#844938: The new node-tap is causing FTBFS in node-inline-source-map

2016-11-23 21:47 GMT+01:00 Ross Gammon : > tag 844938 + upstream > forwarded 844938 https://github.com/thlorenz/inline-source-map/issues/18 > thanks > > Hi, > > I have just investigated what has changed that might be causing this > failure of the upstream testsuite, and it

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

2016-11-23 15:45 GMT+01:00 Paolo Greppi : > On 23/11/2016 14:57, Jonas Smedegaard wrote: >> Npm is an *alternative* to using Debian packaged nodejs code. >> >> Users of Debian cannot tell anything about how same or similar tasks >> could be solved using Debian, because they

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

ave any way out of this... > > * Jérémy Lal [Tue Nov 15, 2016 at 11:27:02PM +0100]: > >> > Is really no one from the Debian Javascript Maintainers working on >> > the npm packaging or interested in having an up2date version >> > available for stretch? Are there an

Bug#844922: [Pkg-javascript-devel] Bug#844922: Node-string-decoder

2016-11-23 8:53 GMT+01:00 Ross Gammon : > Hi, > > This node module was originally packaged as it was a dependency of something > (I can't remember). > > If there is nothing depending on it, we should probably remove it from the > archive. The string-decoder function from the

Bug#845245: apt-cacher-ng: exStartTradeOff does not accept suffix

Package: apt-cacher-ng Version: 1-2 Severity: normal Set ExStartTradeOff: 500m in /etc/apt-cacher-ng/local.conf and restart daemon. It fails. -- Package-specific info: -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'),

Bug#844998: node-tap: Cannot find module nyc/bin/nyc.js

Package: node-tap Version: 8.0.0-1 Severity: normal Many packages are actually using command-line switches that prompt node-tap to try to load "nyc". tap should fail gracefully and still run the tests instead of throwing an error. -- System Information: Debian Release: stretch/sid APT prefers

Bug#844521: flot: homepage changed

No development for 4 years, for a browser lib, means it is dead. Could we remove this package ? 2016-11-16 15:01 GMT+01:00 W. Martin Borgert : > Source: flot > Version: 0.8.3+dfsg-1 > Severity: minor > > code.google.com is gone. > The new homepage is

Bug#794890: [Pkg-javascript-devel] Bug#794890: npm: new upstream version

> Is really no one from the Debian Javascript Maintainers working on > the npm packaging or interested in having an up2date version > available for stretch? Are there any known blockers? Besides "takes a lot of time", no. The amount of work needed to complete that task is simply discouraging :(

Bug#844389: npm2deb: properly install files if files section is not present in package.json

2016-11-15 7:38 GMT+01:00 Shanavas M : > Package: npm2deb > Version: 0.2.6-1 > Severity: normal > > Dear Maintainer, > > If files section is missing in package.json include everything excluding files > ignored by .npmignore and .gitignore > >

Bug#844312: [Pkg-javascript-devel] Bug#844312: please include package.json for bundled modules

2016-11-14 12:36 GMT+01:00 Pirate Praveen : > package: node-should > version: 8.4.0~dfsg-1 > severity: important > > Without this every module that looks for node-should needs patching. > Right now, this fails for node-nodeunit > > Error: Cannot find module 'should-type' >

Bug#844075: leaflet: Please provide the latest Leaflet package including a node module

2016-11-12 10:45 GMT+01:00 Ross Gammon : > Source: leaflet > Version: 0.7.7+20160312-1 > Severity: wishlist > > Dear Maintainer, > > I am trying to finalise the packaging of the new kosmtik package, but it > requires a newer version of Leaflet (>= 1.0.0-beta.2) including the

Bug#826560: kosmtik needs newer node-carto as well

2016-11-12 10:31 GMT+01:00 Ross Gammon : > Hi, > > I am packaging node-kosmtik which also needs a newer node-carto version > (>= 0.15.2). > > If I can help with preparing an upload, I am happy to help out. > > Node-mapnik seems to be the only current reverse dependency. > >

Bug#844014: node-js-yaml

Putting back in the right order... > On 12/11/16 00:25, Jérémy Lal wrote: > > > > 2016-11-11 20:48 GMT+01:00 Ross Gammon <rossgam...@mail.dk>: > >> Package: node-js-yaml >> Version: 3.6.1+dfsg-1 >> Severity: grave >> Justification: renders packa

Bug#844014: node-js-yaml

2016-11-11 20:48 GMT+01:00 Ross Gammon : > Package: node-js-yaml > Version: 3.6.1+dfsg-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > Node-js-yaml is currently uninstallable in unstable due to a tight > dependency > on node-esprima (<

Bug#844030: ITP: node-tap-parser -- Test anything protocol stream parser - Node.js module

Package: wnpp Severity: wishlist Owner: "Jérémy Lal" <kapo...@melix.org> * Package name: node-tap-parser Version : 3.0.3 Upstream Author : James Halliday <m...@substack.net> (http://substack.net) * URL : https://github.com/substack/tap-parser * L

Bug#844023: ITP: node-marked-man -- Markdown to man page conversion - Node.js

Package: wnpp Severity: wishlist Owner: "Jérémy Lal" <kapo...@melix.org> * Package name: node-marked-man Version : 0.1.6 Upstream Author : Jérémy Lal <kapo...@melix.org> * URL : https://github.com/kapouer/marked-man * License : Ex

Bug#844022: ITP: node-marked-man -- Markdown to man page conversion - Node.js

Package: wnpp Severity: wishlist Owner: "Jérémy Lal" <kapo...@melix.org> * Package name: node-marked-man Version : 0.1.5 Upstream Author : Jérémy Lal <kapo...@melix.org> * URL : https://github.com/kapouer/marked-man * License : Ex

Bug#843990: ITP: node-tmatch -- Match an object against a "pattern" object - Node.js module

Package: wnpp Severity: wishlist Owner: "Jérémy Lal" <kapo...@melix.org> * Package name: node-tmatch Version : 3.0.0 Upstream Author : Isaac Z. Schlueter <i...@izs.me> (http://blog.izs.me/) * URL : https://github.com/isaacs/tmatch#readme *

Bug#843021: RFP: yarn -- a fast, reliable, and secure package manager for Node.js

2016-11-03 13:32 GMT+01:00 Paolo Greppi : > On 03/11/2016 09:10, Lars Wirzenius wrote: > > On Thu, Nov 03, 2016 at 08:36:21AM +0100, Paolo Greppi wrote: > >>Package name: yarn > >> URL: https://github.com/yarnpkg/yarn > > > > My cmdtest package provides

Bug#842465: npm2deb: Use npm registry url in watch files

2016-10-29 15:08 GMT+02:00 Shanavas M : > Package: npm2deb > Version: 0.2.5-1 > Severity: important > > Dear Maintainer, > > Using git repo url in debian/watch file creates the following issues. > > 1. Tags in git repo need not match with npm versions, in such cases >

Bug#841981: nodejs should recommend ca-certificates

2016-10-25 1:43 GMT+02:00 Daniel Lo Nigro : > Apart from that, is there a good reason to use Recommend instead of Depend >> ? > > > I'm not sure. wget and libcurl3-gnutls both "Recommend" rather than > "Depend" on ca-certificates. I think it's because wget still mostly works >

Bug#841981: nodejs should recommend ca-certificates

2016-10-25 0:26 GMT+02:00 Daniel Lo Nigro : > Package: nodejs > Version: 4.6.0~dfsg-2 > Severity: normal > > Dear Maintainer, > > When CA certificates are not available, Node.js scripts that try to > connect to remote servers using TLS/SSL fail with "Error: unable to get >

Bug#841558: node-tap: FTBFS: help2man: can't get `--help' info from bin/tap.js

2016-10-21 15:52 GMT+02:00 Lucas Nussbaum : > Source: node-tap > Version: 0.7.1-1.1 > Severity: serious > Tags: stretch sid > User: debian...@lists.debian.org > Usertags: qa-ftbfs-20161021 qa-ftbfs > Justification: FTBFS on amd64 > > Hi, > > During a rebuild of all packages in

Bug#766461: gitg: upload 3.22 to unstable

Package: gitg Followup-For: Bug #766461 Hi Dmitry, just a few words to say that i'm having an incredibly good user experience with gitg 3.22. It's fast, it's packed with wonderful features (uncomparably better than old 0.2.7 version) and upstream seems to be going in a very pragmatic direction.

Bug#840464: nodejs: 'npm install' command fails with compilation error in Kerberos header

2016-10-11 21:03 GMT+02:00 David L Lambert : > Package: nodejs > Version: 0.10.29~dfsg-2 > Severity: normal > > Dear Maintainer, > > After installing packages "nodejs", "nodejs-legacy", and "libkrb5-dev", > I still get a compilation error blocking completion of "npm install >

Bug#840330: [Build-common-hackers] Bug#840330: cdbs: licensecheck runs twice during build

2016-10-10 20:59 GMT+02:00 Jonas Smedegaard <d...@jones.dk>: > Quoting Jérémy Lal (2016-10-10 18:51:53) > > cdbs runs licensecheck two times during build: > > https://buildd.debian.org/status/fetch.php?pkg=nodejs; > arch=mips64el=4.6.0~dfsg-1=1476084143 > > Than

Bug#840330: cdbs: licensecheck runs twice during build

Package: cdbs Version: 0.4.148 Severity: normal Hi, cdbs runs licensecheck two times during build: https://buildd.debian.org/status/fetch.php?pkg=nodejs=mips64el=4.6.0~dfsg-1=1476084143 and it crashes too. Is there some way to avoid completely running licensecheck when building on sbuild. It's

Bug#836415: nodejs: SIGILL when running nodejs

2016-10-06 12:28 GMT+02:00 Jérémy Lal <kapo...@melix.org>: > > > 2016-09-04 16:41 GMT+02:00 Sam Imberman <simber...@gmail.com>: > >> >> >> This is using nodejs 4.4.7 from sid: >> >> (gdb) run >> Starting program: /usr/bin/nodejs &g

Bug#836415: Bug#838440: [Pkg-javascript-devel] Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries

2016-10-09 23:02 GMT+02:00 Sebastiaan Couwenberg <sebas...@xs4all.nl>: > On 10/09/2016 10:25 PM, Jérémy Lal wrote: > > Now the same is going to happen with "powerpc" arch: libv8 is actually > not > > compatible with all processors supported by debian (ppc64xx are

Bug#838440: [Pkg-javascript-devel] Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries

2016-10-06 12:24 GMT+02:00 Sebastiaan Couwenberg <sebas...@xs4all.nl>: > On 10/06/2016 12:21 PM, Jérémy Lal wrote: > > 2016-09-21 11:53 GMT+02:00 Sebastiaan Couwenberg <sebas...@xs4all.nl>: > > > >> On 09/21/2016 11:34 AM, Jérémy Lal wrote: > >>> 2

Bug#840199: libc6: setlocale(LC_ALL, "C.UTF-8") used to work in jessie

Package: libc6 Version: 2.24-3 Severity: normal Hi, This used to work in jessie: export LC_ALL="C.UTF-8" echo "ça va" | iconv -f UTF-8 -t "ascii//TRANSLIT" > ca va Now it doesn't: > ?a va Jérémy -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500,

Bug#830242: [Pkg-javascript-devel] Bug#830242: nodejs: accesses the internet during build

2016-09-17 15:51 GMT+02:00 Mattia Rizzolo <mat...@debian.org>: > control: found -1 4.3.1~dfsg-1 > > On Sat, Sep 17, 2016 at 03:42:49PM +0200, Jérémy Lal wrote: > > > Is this a regression in 4.4.7, or is 4.3.1 also affected? This is > blocking > > > te

Bug#836415: nodejs: SIGILL when running nodejs

2016-09-04 16:41 GMT+02:00 Sam Imberman : > > > This is using nodejs 4.4.7 from sid: > > (gdb) run > Starting program: /usr/bin/nodejs > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/powerpc-linux-gnu/ > libthread_db.so.1". > [New

Bug#838440: [Pkg-javascript-devel] Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries

2016-09-21 11:53 GMT+02:00 Sebastiaan Couwenberg <sebas...@xs4all.nl>: > On 09/21/2016 11:34 AM, Jérémy Lal wrote: > > 2016-09-21 10:24 GMT+02:00 Emilio Pozuelo Monfort <po...@debian.org>: > >> I see you dropped support for armel in #818552 and requested the remo

Bug#839904: licensecheck: maybe should not look into LICENSE file ?

Package: licensecheck Version: 3.0.24-1 Severity: wishlist I just noticed LICENSE file of the software itself ended up inside copyright_hints, filled with a long list of licenses. Ignoring that file might be something safe to do ? Bye, Jérémy

Bug#839116: ITP: node-webcomponentsjs-custom-element-v0 -- CustomElements polyfill from the webcomponentsjs project

2016-09-29 11:06 GMT+02:00 Potter, Tim (HPE Linux Support) < timothy.pot...@hpe.com>: > On 29 Sep 2016, at 4:28 pm, Jérémy Lal <kapo...@melix.org> wrote: > > > Two things are wrong with this package: > > > > - wrong upstream, why not choose the or

Bug#839116: ITP: node-webcomponentsjs-custom-element-v0 -- CustomElements polyfill from the webcomponentsjs project

2016-09-29 6:49 GMT+02:00 Potter, Tim (HPE Linux Support) < timothy.pot...@hpe.com>: > Package: wnpp > Severity: wishlist > Owner: Tim Potter > X-Debbugs-CC: debian-de...@lists.debian.org > > * Package name: node-webcomponentsjs-custom-element-v0 > Version : 1.0.1 >

Bug#838440: nodejs: can't migrate to testing because of lack of armel binaries

2016-09-21 10:24 GMT+02:00 Emilio Pozuelo Monfort : > Source: nodejs > Version: 4.4.7~dfsg-2 > Severity: serious > > Hi, > > I see you dropped support for armel in #818552 and requested the removal > of the outdated armel binaries. That's fine. However, nodejs doesn't > migrate

Bug#830242: [Pkg-javascript-devel] Bug#830242: nodejs: accesses the internet during build

2016-09-17 15:20 GMT+02:00 Emilio Pozuelo Monfort : > Hi, > > On Thu, 07 Jul 2016 16:38:15 +0200 Chris Lamb wrote: > > Source: nodejs > > Version: 4.4.7~dfsg-2 > > Severity: serious > > Justification: Policy 4.9 > > User: la...@debian.org > > Usertags:

Bug#837929: npm: Should suggest nodejs-legacy

2016-09-16 10:22 GMT+02:00 Jonas Smedegaard : > Quoting Matijs van Zuijlen (2016-09-16 09:57:52) > > I read through bug 614907, and I think the very best solution would be > > for npm to ensure the correct node executable is referenced in each > > package's executable. I don't know

Bug#837929: npm: Should suggest nodejs-legacy

(reordered your reply to the bottom) On 15/09/16 19:22, Jonas Smedegaard wrote: > > Quoting Jérémy Lal (2016-09-15 17:21:30) > >> 2016-09-15 17:12 GMT+02:00 Matijs van Zuijlen <mat...@matijs.net>: > >> > >>> Package: npm > >>> Version: 1.4.21

Bug#837929: npm: Should suggest nodejs-legacy

2016-09-15 17:12 GMT+02:00 Matijs van Zuijlen : > Package: npm > Version: 1.4.21+ds-2 > Severity: wishlist > > Executables installed with npm need the /usr/bin/node executable, which > is provided in the nodejs-legacy package. This information is currently > only in the

Bug#837808: gnome-online-accounts: 30% CPU Load with a Google account

Package: gnome-online-accounts Version: 3.21.91-1 Severity: normal I have set up a google online account using the gnome control panel, and when i log into gnome session as usual after reboot, goa-daemon runs at 30% cpu load for a long (possibly forever) time. Nothing weird is logged that i

Bug#828457: nodejs: FTBFS with openssl 1.1.0

2016-09-11 14:25 GMT+02:00 Kurt Roeckx : > tags 828457 + patch > > A patch for it is available at: > https://github.com/nodejs/node/pull/8491 > > Wonderful, and thank you. I'll upload nodejs 6.x in experimental with your patch applied. Jérémy.

Bug#748215: Provide a C.UTF-8 locale by default

Package: libc6 Version: 2.24-2 Followup-For: Bug #748215 Something important has changed w.r.t. that matter: export LANG=C.UTF-8 echo "ça va が" | iconv -f UTF-8 -t 'ascii//translit' in Jessie, it returns expectedly > ca va iconv: illegal input sequence at position 7 in Stretch, it returns >

Bug#836415: nodejs: SIGILL when running nodejs

2016-09-02 21:37 GMT+02:00 Sam Imberman : > Package: nodejs > Version: 6.0.0~dfsg-1 > Severity: important > > Dear Maintainer, > > I am unable to run nodejs at all on a PowerBook G4 12", because of an > illegal > instruction. This is true for both the version in "sid"

Bug#830242: nodejs: accesses the internet during build

2016-07-07 16:38 GMT+02:00 Chris Lamb : > Source: nodejs > Version: 4.4.7~dfsg-2 > Severity: serious > Justification: Policy 4.9 > User: la...@debian.org > Usertags: network-access > > Dear Maintainer, > > Whilst nodejs builds successfully on unstable/amd64, according to >

Bug#773671: [Pkg-javascript-devel] Bug#773671: libv8-3.14: multiple security issues

The rationale behind opening the RC bugs was improving transparency on > >> my side. I think more people follow bugs than the security tracker. > > > > Ok. In the past we didn't file bugs on libv8 since they were unlikely > > to be dealt with anyway. We'll file bug

Bug#829654: Overwrite Debian fcgiwrap git repository

2016-07-11 20:10 GMT+02:00 Peter Colberg : > Hi Jérémy, > > I am co-maintaining fcgiwrap together with its current maintainer > Jordi (CC'd) and for this purpose converted the svn history to git. > Now that I am about to upload the git repository to collab-maint, I > found an

Bug#828457: nodejs: FTBFS with openssl 1.1.0

2016-06-26 20:24 GMT+02:00 Kurt Roeckx <k...@roeckx.be>: > On Sun, Jun 26, 2016 at 06:53:42PM +0200, Jérémy Lal wrote: > > > > I'm on it, and after a couple things i could solve, i need a "gentle > push" > > to continue solving these: > > They all see

Bug#828457: nodejs: FTBFS with openssl 1.1.0

2016-06-26 12:23 GMT+02:00 Kurt Roeckx : > Source: nodejs > Version: 4.4.3~dfsg-1 > Severity: important > Control: block 827061 by -1 > > Hi, > > OpenSSL 1.1.0 is about to released. During a rebuild of all packages using > OpenSSL this package fail to build. A log of that build

Bug#827931: RM: nodejs [armel] -- ANAIS; nodejs > 0.10 no longer supports armel arch

Package: ftp.debian.org Severity: normal nodejs >= 4 never supported < armv7 cpu. It went undetected because armel buildd servers all have >= armv7 cpu. Thanks, Jérémy

Bug#826890: [Pkg-javascript-devel] Bug#826890: Bug#826890: nodejs: not Multi-Arch: foreign

2016-06-19 19:18 GMT+02:00 Jérémy Lal <kapo...@melix.org>: > 2016-06-10 2:05 GMT+02:00 Jonas Smedegaard <d...@jones.dk>: > >> Quoting Thorsten Glaser (2016-06-10 00:38:25) >> > Jonas Smedegaard dixit: >> >> Uhm, wouldn't it make more sense to instead

Bug#826890: [Pkg-javascript-devel] Bug#826890: nodejs: not Multi-Arch: foreign

2016-06-10 2:05 GMT+02:00 Jonas Smedegaard : > Quoting Thorsten Glaser (2016-06-10 00:38:25) > > Jonas Smedegaard dixit: > >> Uhm, wouldn't it make more sense to instead file bugreports against > >> stuff like node-iglify, to get _more_ of Debian multiarch'ified? > > > >

Bug#818552: [Pkg-javascript-devel] Bug#818552: Bug#818552: nodejs on armel (v5l) fails with "illegal instruction"

2016-06-18 20:38 GMT+02:00 Jonas Smedegaard <d...@jones.dk>: > Quoting Jérémy Lal (2016-06-18 20:20:24) > > 2016-06-18 14:47 GMT+02:00 Jonas Smedegaard <d...@jones.dk>: > > > > > Quoting Jérémy Lal (2016-06-18 14:16:11) > > > > > Update

Bug#818552: [Pkg-javascript-devel] Bug#818552: Bug#818552: nodejs on armel (v5l) fails with "illegal instruction"

2016-06-18 14:47 GMT+02:00 Jonas Smedegaard <d...@jones.dk>: > Quoting Jérémy Lal (2016-06-18 14:16:11) > > > Update: v8 has dropped armv5 support, see > > > https://github.com/nodejs/node/issues/5810 > > > https://groups.google.com/forum/#!topic/v8-users/a

Bug#818552: nodejs on armel (v5l) fails with "illegal instruction"

> Update: v8 has dropped armv5 support, see > https://github.com/nodejs/node/issues/5810 > https://groups.google.com/forum/#!topic/v8-users/aSOFbaAQvMk > I'm going to remove "armel" from the list of Architectures. And as usual, i'm completely lost when it comes to that part. It's easy to do

Bug#818552: nodejs on armel (v5l) fails with "illegal instruction"

2016-05-09 15:41 GMT+02:00 Jérémy Lal <kapo...@melix.org>: > Hi, > > sorry for the delay, > Update: v8 has dropped armv5 support, see https://github.com/nodejs/node/issues/5810 https://groups.google.com/forum/#!topic/v8-users/aSOFbaAQvMk I'm going to remove &qu

Bug#818552: nodejs on armel (v5l) fails with "illegal instruction"

Hi, sorry for the delay, somehow i did not receive this bug report. Could you give me the output of `cat /proc/cpuinfo` ? Could you tell me if you get the same error with versions 4.3.1 or 4.4.3 If it does crash on version 4.3.1, and since this bug prevents migration to testing, i might lower

Bug#823597: npm: If npm is updated with npm install npm -g, /usr/share/npm/npmrc is lost

Package: npm Version: 1.4.21+ds-3 Severity: normal Tags: upstream Got hit again by https://github.com/npm/npm/issues/533 I'm sharing it here so other users can find a workaround. `npm install npm -g` will correctly install latest version of npm in /usr/local (provided current user is member of

Bug#821228: libjavascriptcoregtk: segfault when opening a page

2016-04-28 11:05 GMT+02:00 Alberto Garcia <be...@igalia.com>: > Control: tags -1 upstream > Control: forwarded -1 https://bugs.webkit.org/show_bug.cgi?id=157126 > > On Sat, Apr 16, 2016 at 10:32:01PM +0200, Jérémy Lal wrote: > > > when opening http://gexpertise.fr

Bug#728422: sbuild: fails to getent group sbuild when running with init=/bin/systemd

Package: sbuild Version: 0.68.0-1 Followup-For: Bug #728422 Maybe the problem comes simply from the fact that i booted on linux image 4.5 today, and booting on linux image 4.4.6 makes it work again. Something with my config ? [sid-amd64-sbuild] aliases=sid type=directory union-type=overlay

Bug#728422: sbuild: fails to getent group sbuild when running with init=/bin/systemd

Package: sbuild Version: 0.68.0-1 Followup-For: Bug #728422 I reproduce the issue, same symptoms. I think it started after the sbuild-update i did few days ago. Any command returns "permission denied", even `ls`. As root or as user in the sbuild group. The files in the chroot are owned by

Bug#822358: letsencrypt: should provide cron.monthly "letsencrypt renew"

Package: letsencrypt Severity: wishlist While i was adding that monthly cron script on several servers, i figured it would be best installed as a default. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (690, 'unstable'), (650, 'testing'), (630,

Bug#822314: gpaste: cannot connect to gpaste daemon

2016-04-23 20:05 GMT+02:00 Ritesh Raj Sarraf <r...@debian.org>: > On Sat, 2016-04-23 at 19:40 +0200, Jérémy Lal wrote: > > Absolutely no idea ! > > I forwarded to upstream here > > https://github.com/Keruspe/GPaste/issues/145 > > > > Thanks. I've replied

Bug#822314: gpaste: cannot connect to gpaste daemon

2016-04-23 19:22 GMT+02:00 Ritesh Raj Sarraf <r...@debian.org>: > On Sat, 2016-04-23 at 20:59 +0530, Ritesh Raj Sarraf wrote: > > On Sat, 2016-04-23 at 12:04 +0200, Jérémy Lal wrote: > > > > > > Here i get > > > avril 20 08:46:52 imac /usr/

Bug#822314: gpaste: cannot connect to gpaste daemon

2016-04-23 11:41 GMT+02:00 Ritesh Raj Sarraf : > Package: gpaste > Version: 3.20-1 > Severity: important > > The new gpaste does not seem to work at all. The notification in system > tray says that it cannot connect to gpaste daemon. > > In the logs, we have: > > Apr 23 15:07:09

Bug#820309: libwebkit2gtk-4.0-37: missing default theme for checkboxes, scrollbars, select

2016-04-08 9:17 GMT+02:00 Alberto Garcia : > On Thu, Apr 07, 2016 at 02:47:04PM +0200, Alberto Garcia wrote: > > > > > This might be caused by me running gnome / gtk 3.20 from > > > > debian/experimental, i'll downgrade and make sure of that. > > > > > > Confirmed ! I downgraded

Bug#821228: libjavascriptcoregtk: segfault when opening a page

Package: libjavascriptcoregtk-4.0-18 Version: 2.12.1-1 Severity: normal File: libjavascriptcoregtk Hi, when opening http://gexpertise.fr/activites/metiers/stockage with MiniBrowser, this did not happen with version 2.10: Program received signal SIGSEGV, Segmentation fault.

Bug#821184: webkit2gtk: debug build ?

Source: webkit2gtk Version: 2.12.1-1 Severity: normal Hi, it seems there is no more dbg package available, and doing DEB_BUILD_OPTIONS=debug debuild failed at link time with Source/JavaScriptCore/runtime/WriteBarrier.h:53 : erreur : référence à «  JSC::JSCell::structure() const » non définie

Bug#820859: libuv1: Temporarily block testing migration, phase-locking it to nodejs LTS

2016-04-13 20:36 GMT+02:00 Julian Gilbey : > On Wed, Apr 13, 2016 at 10:25:19AM +0200, Luca Bruno wrote: > > Package: libuv1 > > Version: 1.9.0-1 > > Severity: normal > > > > We still need to clear up whether nodejs LTS are locked to spcific libuv1 > > minor versions or not. > >

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

2016-04-08 15:26 GMT+02:00 Jérémy Lal <kapo...@melix.org>: > 2016-04-08 15:10 GMT+02:00 Sebastiaan Couwenberg <sebas...@xs4all.nl>: > >> On 04/08/2016 02:20 PM, Jérémy Lal wrote: >> > 2016-04-08 14:04 GMT+02:00 Sebastiaan Couwenberg: >> >> The test

Bug#820737: ITP: node-tar-pack -- Pack and unpack a Node.js module

Package: wnpp Severity: wishlist Owner: "Jérémy Lal" <kapo...@melix.org> * Package name: node-tar-pack Version : 3.1.3 Upstream Author : Forbes Lindesay * URL : https://github.com/ForbesLindesay/tar-pack * License : BSD-2-Clause Programming

Bug#820563: Native addon deployment tool for Node.js

Package: wnpp Severity: normal To: sub...@bugs.debian.org Subject: ITP: node-pre-gyp -- Node.js native addon binary install tool Package: wnpp Severity: wishlist Owner: Jérémy Lal <kapo...@melix.org> X-Debbugs-CC: debian-de...@lists.debian.org * Package name: node-pre-gyp V

Bug#820515: find, load, flatten json or ini application configuration

Package: wnpp Severity: normal To: sub...@bugs.debian.org Subject: ITP: node-rc -- hardwired configuration loader Package: wnpp Severity: wishlist Owner: Jérémy Lal <kapo...@melix.org> X-Debbugs-CC: debian-de...@lists.debian.org * Package name: node-rc Version : 1.1.6 Up

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

2016-04-08 15:10 GMT+02:00 Sebastiaan Couwenberg <sebas...@xs4all.nl>: > On 04/08/2016 02:20 PM, Jérémy Lal wrote: > > 2016-04-08 14:04 GMT+02:00 Sebastiaan Couwenberg: > >> The test target fails because it requires node-pre-gyp, as do the > >> bin/mapnik-*.js

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

2016-04-08 14:04 GMT+02:00 Sebastiaan Couwenberg <sebas...@xs4all.nl>: > On 04/08/2016 01:54 PM, Jérémy Lal wrote: > > 2016-04-08 12:49 GMT+02:00 Sebastiaan Couwenberg <sebas...@xs4all.nl>: > > > >> On 04/08/2016 12:34 PM, Jérémy Lal wrote: > >>>

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

2016-04-08 12:24 GMT+02:00 Sebastiaan Couwenberg <sebas...@xs4all.nl>: > On 04/08/2016 12:09 PM, Jérémy Lal wrote: > > 2016-04-08 11:32 GMT+02:00 Sebastiaan Couwenberg <sebas...@xs4all.nl>: > > > >> On Wed, 8 Jul 2015 09:31:46 +0200 Jérémy Lal wrote: >

Bug#791725: [Pkg-javascript-devel] Bug#791725: node-mapnik: FTBFS against mapnik 3.0.0

2016-04-08 11:32 GMT+02:00 Sebastiaan Couwenberg <sebas...@xs4all.nl>: > On Wed, 8 Jul 2015 09:31:46 +0200 Jérémy Lal wrote: > > 2015-07-07 23:43 GMT+02:00 Emilio Pozuelo Monfort <po...@debian.org>: > > > Your package fails to build against mapnik 3.0.0: > &g

Bug#820309: libwebkit2gtk-4.0-37: missing default theme for checkboxes, scrollbars, select

2016-04-07 13:50 GMT+02:00 Jérémy Lal <kapo...@melix.org>: > > 2016-04-07 13:26 GMT+02:00 Alberto Garcia <be...@igalia.com>: > >> Control: tags -1 moreinfo >> >> On Thu, Apr 07, 2016 at 12:13:32PM +0200, Jérémy Lal wrote: >> > Package: libwebkit2gt

Bug#820309: libwebkit2gtk-4.0-37: missing default theme for checkboxes, scrollbars, select

2016-04-07 13:26 GMT+02:00 Alberto Garcia <be...@igalia.com>: > Control: tags -1 moreinfo > > On Thu, Apr 07, 2016 at 12:13:32PM +0200, Jérémy Lal wrote: > > Package: libwebkit2gtk-4.0-37 > > Version: 2.12.0-2 > > > This can be easily verified by opening Mi

<    3   4   5   6   7   8   9   10   11   12   >