Bug#650552: [Pkg-javascript-devel] Bug#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'
Jonas Smedegaard d...@jones.dk writes: The package evidently builds fine now. Yes, this failure mode is gone, thanks. It looks like the armel and armhf builds are running into test suite timeouts, though: https://buildd.debian.org/status/fetch.php?pkg=node-expatarch=armelver=1.5.0-1stamp=1334337481 https://buildd.debian.org/status/fetch.php?pkg=node-expatarch=armhfver=1.5.0-1stamp=1334337523 -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650552: [Pkg-javascript-devel] Bug#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'
On Mon, 5 Dec 2011 15:37:04 +0700, Jonas Smedegaard wrote: On 11-12-05 at 09:24am, Jérémy Lal wrote: This problem is caused by the fact you're building with latest libv8-dev, but nodejs 0.4 wasn't. I'll upload a nodejs 0.4 built against libv8 3.5 later today. Hmm - I suspect this means nodejs-dev should then depend not only on libv8-dev equal-or-larger than current but also on libv8-dev lower than current+1. Not sure about the exact syntax, but believe it is used several other packages as well... I use that same kind of dependency with josm and josm-plugins. Depends: josm (= 0.0.svn4487) Breaks: josm (= 0.0.svn4488) (and the same with Build-Depends/Build-Conflicts) Sure, each time I upload a new josm, josm-plugins becomes uninstallable and gets an RC, but it's the only way to keep things consistent. (and yes, it's currently uninstallable just for that reason) My 0.02€, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature
Bug#650552: [Pkg-javascript-devel] Bug#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'
On 05/12/2011 17:53, David Paleino wrote: On Mon, 5 Dec 2011 15:37:04 +0700, Jonas Smedegaard wrote: On 11-12-05 at 09:24am, Jérémy Lal wrote: This problem is caused by the fact you're building with latest libv8-dev, but nodejs 0.4 wasn't. I'll upload a nodejs 0.4 built against libv8 3.5 later today. Hmm - I suspect this means nodejs-dev should then depend not only on libv8-dev equal-or-larger than current but also on libv8-dev lower than current+1. Not sure about the exact syntax, but believe it is used several other packages as well... I use that same kind of dependency with josm and josm-plugins. Depends: josm (= 0.0.svn4487) Breaks: josm (= 0.0.svn4488) I just used : libv8-dev (= 3.5.10.24), libv8-dev ( 3.6) Jérémy. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#650552: [Pkg-javascript-devel] Bug#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'
Hi Aaron, On 11-11-30 at 02:45pm, Aaron M. Ucko wrote: The automated build of node-expat on i386 (the only platform besides amd64 for which its build dependencies are available) failed with a test suite error: NODE_PATH=/.../node-expat-1.4.1/debian/node-node-expat//usr/lib/nodejs node test.js node.js:134 throw e; // process.nextTick error, or 'error' event on first tick ^ Error: EBADF, Bad file descriptor '/usr/lib/package.json' at Object.openSync (fs.js:221:18) at Object.readFileSync (fs.js:112:15) at Object.anonymous (/usr/lib/nodejs/vows.js:254:28) [snip] I don't have time to dig too deeply, but see that the npm package ships a package.json (under /usr/share/npm); a build dependency on it may be in order. At any rate, could you please take a look? Turns out node-vows depends on npm for resoĺving its version. I will patch it to have its version hardcoded instead (as npm really should be avoided whenever possible IMO). Not sure if the proper approach is to reasign or file another bug and make one of them affect the other - and since I maintain both packages I will simply spend my time on fixing the issue instead :-) Thanks for reporting, and for the helpful suggestion. - 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: Digital signature
Bug#650552: [Pkg-javascript-devel] Bug#650552: node-expat: FTBFS: EBADF, Bad file descriptor '/usr/lib/package.json'
Jonas Smedegaard d...@jones.dk writes: Not sure if the proper approach is to reasign or file another bug and make one of them affect the other - and since I maintain both packages I will simply spend my time on fixing the issue instead :-) Commendably practical; thanks for the prompt fix. :-) It looks like you may need to nudge the buildd maintainers, though; I'm not one myself, just a regular DD who keeps tabs on packages showing up on amd64 but not i386 or vice versa. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
