On 11-12-05 at 09:24am, Jérémy Lal wrote: > On 05/12/2011 02:42, Jonas Smedegaard wrote: > > On 11-12-05 at 08:32am, Jonas Smedegaard wrote: > >> On 11-12-04 at 07:06pm, Aaron M. Ucko wrote: > >>> 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. > >> > >> The package needs a minor update anyway - I just wanted to wait > >> another cycle (and get some sleep) to ensure the fixed d-shlibs had > >> entered unstable, as I don't want to use versioned dependencies for > >> bugfixes if avoidable. > > > > node-vows, off course (not d-shlibs - I am confused this morning). > > > > ...but then when rebuilding node-expat now it fails with another > > error mysterious to me: > > > > Waf: Entering directory `/tmp/buildd/node-expat-1.4.1/build' > > [1/2] cxx: node-expat.cc -> build/default/node-expat_1.o > > [2/2] cxx_link: build/default/node-expat_1.o -> > > build/default/node-expat.node > > Waf: Leaving directory `/tmp/buildd/node-expat-1.4.1/build' > > 'build' finished successfully (0.821s) > > NODE_PATH=/tmp/buildd/node-expat-1.4.1/debian/node-node-expat//usr/lib/nodejs > > node test.js > > node: symbol lookup error: > > /tmp/buildd/node-expat-1.4.1/build/default/node-expat.node: undefined > > symbol: _ZNK2v86String10WriteAsciiEPciii > > make: *** [build/node-node-expat] Error 127 > > > > > > I have now pushed the work, for others to try repeat the error from > > the Git. Perhaps Jérémy Lal has a clue about it...? > > 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... - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
Description: Digital signature