On 11/05/2012 19:10, Julien Cristau wrote: > On Sat, May 5, 2012 at 20:25:14 +0200, Tobias Frost wrote: > >> Dear release team, >> >> to allow removal of old version of libv8 and allow transition of it to >> testing, please schedule a binnmu for its rdepends: >> >> drizzle >> osmium >> > Done.
Thank you. > What about chromium-browser's FTBFS on arm, and libv8-i18n? I'll update libv8-i18n. What's the relation with chromium FTBFS on arm (i guess you mean armel) ? > Somebody should talk to the v8 folks about ABI stability sometime. I do... no success yet [1] I would very much like to use libv8-x.y instead of libv8-x.y.z. Some tool like [2] seems to indicate that for example, there is no ABI breakage risk between libv8-3.9.24.1 and libv8-3.9.24.21, as upstream explains it in [1] too. But, as was discussed on debian-devel [3], it's hard to certify without upstream supporting this. Also it takes an experimented c++ programmer to support that. I'm not. Jérémy. [1] https://groups.google.com/d/topic/v8-users/VJRmaQV-M3E/discussion [2] http://www.upstream-tracker.org/versions/v8.html [3] http://lists.debian.org/debian-devel/2012/01/msg00671.html _______________________________________________ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel