[Pkg-javascript-devel] Bug#880321: libjs-angular-gettext: FTBFS: debian/rules:4: /usr/share/openstack-pkg-tools/pkgos.make: No such file or directory
Source: libjs-angular-gettext Version: 2.3.8-1 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20171030 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > debian/rules:4: /usr/share/openstack-pkg-tools/pkgos.make: No such file or > directory > dh /usr/share/openstack-pkg-tools/pkgos.make > dh: Unknown sequence /usr/share/openstack-pkg-tools/pkgos.make (choose from: > binary binary-arch binary-indep build build-arch build-indep clean install > install-arch install-indep) > debian/rules:7: recipe for target '/usr/share/openstack-pkg-tools/pkgos.make' > failed > make: *** [/usr/share/openstack-pkg-tools/pkgos.make] Error 255 The full build log is available from: http://aws-logs.debian.net/2017/10/30/libjs-angular-gettext_2.3.8-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#880290: node-grunt-babel: FTBFS: Test failures
Source: node-grunt-babel Version: 7.0.0-2 Severity: serious Tags: buster sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20171030 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >dh_update_autotools_config >dh_auto_configure >dh_auto_build >debian/rules override_dh_auto_test > make[1]: Entering directory '/<>' > grunt > Running "clean:test" (clean) task > >> 0 paths cleaned. > > Running "babel:compile" (babel) task > Warning: Couldn't find preset "env" relative to directory "test/fixtures" > Use --force to continue. > > Aborted due to warnings. > debian/rules:13: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2017/10/30/node-grunt-babel_7.0.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#870963: requesting removal of packages that missed both jessie and stretch
reassign 870941 ftp.debian.org retitle 870941 RM: flickrfs -- RoQA; missed both jessie and stretch reassign 870991 ftp.debian.org retitle 870991 RM: mnemonicode -- RoQA; missed both jessie and stretch reassign 870977 ftp.debian.org retitle 870977 RM: xburst-tools -- RoQA; missed both jessie and stretch reassign 870947 ftp.debian.org retitle 870947 RM: libsearch-estraier-perl -- RoQA; missed both jessie and stretch reassign 870963 ftp.debian.org retitle 870963 RM: jarisplayer -- RoQA; missed both jessie and stretch reassign 871002 ftp.debian.org retitle 871002 RM: cipux-cat-web -- RoQA; missed both jessie and stretch reassign 870989 ftp.debian.org retitle 870989 RM: interchange -- RoQA; missed both jessie and stretch reassign 870932 ftp.debian.org retitle 870932 RM: ocamlduce -- RoQA; missed both jessie and stretch reassign 870995 ftp.debian.org retitle 870995 RM: couchdb -- RoQA; missed both jessie and stretch reassign 870971 ftp.debian.org retitle 870971 RM: qpid-tools -- RoQA; missed both jessie and stretch reassign 870919 ftp.debian.org retitle 870919 RM: node-zlib -- RoQA; missed both jessie and stretch reassign 870928 ftp.debian.org retitle 870928 RM: openclipart2 -- RoQA; missed both jessie and stretch reassign 870952 ftp.debian.org retitle 870952 RM: qpid-cpp -- RoQA; missed both jessie and stretch reassign 870988 ftp.debian.org retitle 870988 RM: moodle-debian-edu-theme -- RoQA; missed both jessie and stretch reassign 870994 ftp.debian.org retitle 870994 RM: gregorio -- RoQA; missed both jessie and stretch reassign 870937 ftp.debian.org retitle 870937 RM: cutter-testing-framework -- RoQA; missed both jessie and stretch reassign 870942 ftp.debian.org retitle 870942 RM: diet -- RoQA; missed both jessie and stretch reassign 870923 ftp.debian.org retitle 870923 RM: babel -- RoQA; missed both jessie and stretch reassign 870982 ftp.debian.org retitle 870982 RM: djbdns -- RoQA; missed both jessie and stretch reassign 871005 ftp.debian.org retitle 871005 RM: rinputd -- RoQA; missed both jessie and stretch reassign 871006 ftp.debian.org retitle 871006 RM: z88dk -- RoQA; missed both jessie and stretch reassign 870955 ftp.debian.org retitle 870955 RM: openbve -- RoQA; missed both jessie and stretch reassign 870998 ftp.debian.org retitle 870998 RM: android-permissions -- RoQA; missed both jessie and stretch reassign 870918 ftp.debian.org retitle 870918 RM: openmeeg -- RoQA; missed both jessie and stretch reassign 870933 ftp.debian.org retitle 870933 RM: twitter-recess -- RoQA; missed both jessie and stretch reassign 870976 ftp.debian.org retitle 870976 RM: varnish-agent -- RoQA; missed both jessie and stretch reassign 870962 ftp.debian.org retitle 870962 RM: uif2iso -- RoQA; missed both jessie and stretch reassign 870970 ftp.debian.org retitle 870970 RM: gnu-fdisk -- RoQA; missed both jessie and stretch reassign 871004 ftp.debian.org retitle 871004 RM: hyde -- RoQA; missed both jessie and stretch reassign 870940 ftp.debian.org retitle 870940 RM: controlaula -- RoQA; missed both jessie and stretch reassign 870992 ftp.debian.org retitle 870992 RM: bashdb -- RoQA; missed both jessie and stretch reassign 870980 ftp.debian.org retitle 870980 RM: django-ldapdb -- RoQA; missed both jessie and stretch reassign 870986 ftp.debian.org retitle 870986 RM: python-lua -- RoQA; missed both jessie and stretch reassign 870960 ftp.debian.org retitle 870960 RM: django-conneg -- RoQA; missed both jessie and stretch reassign 870958 ftp.debian.org retitle 870958 RM: python-django-feincms -- RoQA; missed both jessie and stretch reassign 871001 ftp.debian.org retitle 871001 RM: node-jquery -- RoQA; missed both jessie and stretch reassign 870920 ftp.debian.org retitle 870920 RM: drgeo -- RoQA; missed both jessie and stretch reassign 870935 ftp.debian.org retitle 870935 RM: pyfltk -- RoQA; missed both jessie and stretch reassign 870938 ftp.debian.org retitle 870938 RM: tmview -- RoQA; missed both jessie and stretch reassign 870999 ftp.debian.org retitle 870999 RM: planner-el -- RoQA; missed both jessie and stretch reassign 870939 ftp.debian.org retitle 870939 RM: tile -- RoQA; missed both jessie and stretch reassign 870931 ftp.debian.org retitle 870931 RM: udev-discover -- RoQA; missed both jessie and stretch reassign 870966 ftp.debian.org retitle 870966 RM: janest-core -- RoQA; missed both jessie and stretch reassign 870969 ftp.debian.org retitle 870969 RM: sbackup -- RoQA; missed both jessie and stretch reassign 871000 ftp.debian.org retitle 871000 RM: node-bones -- RoQA; missed both jessie and stretch reassign 870973 ftp.debian.org retitle 870973 RM: xgraph -- RoQA; missed both jessie and stretch reassign 870984 ftp.debian.org retitle 870984 RM: imview-doc -- RoQA; missed both jessie and stretch reassign 870997 ftp.debian.org retitle 870997 RM: libtext-vimcolor-perl -- RoQA; missed both jessie and stretch reassign 870922 ftp.debian.org retitle 870922 RM: elmerfem -- RoQA; missed both jessie and stretch reassign 870924
[Pkg-javascript-devel] Bug#870956: Bug#870956: node-jsdom: should node-jsdom be removed from unstable?
Hi, On 10/08/17 at 17:38 +0530, Pirate Praveen wrote: > I think (from what I remember) this is a dependency of > node-jquery-. Though it required many other build tools also > packaged, so it was not touched. I will see if I can confirm this in the > coming days. Ping? :) Lucas signature.asc Description: PGP signature -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#871000: node-bones: should node-bones be removed from unstable?
Source: node-bones User: debian...@lists.debian.org Usertags: qa-removals-post-stretch Hi, Following a discussion[1] on the debian-qa@ mailing list on packages that missed both jessie and stretch, I am proposing the removal of this package from unstable, because: it was in unstable at the time of the stretch freeze but wasn't part of stretch AND it was in unstable at the time of the jessie freeze but it wasn't part of jessie AND it is still not in testing AND it was not uploaded since the beginning of 2017. If you disagree and think that this package should remain in unstable, feel free to just close this bug. If this bug is still open one month from now (on 2017-09-06), it will be turned into a removal request, using: reassign -1 ftp.debian.org retitle -1 RM: node-bones -- RoQA; missed both jessie and stretch thanks - Lucas, for the QA team. [1] https://lists.debian.org/debian-qa/2017/07/msg00021.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
[Pkg-javascript-devel] Bug#871001: node-jquery: should node-jquery be removed from unstable?
Source: node-jquery User: debian...@lists.debian.org Usertags: qa-removals-post-stretch Hi, Following a discussion[1] on the debian-qa@ mailing list on packages that missed both jessie and stretch, I am proposing the removal of this package from unstable, because: it was in unstable at the time of the stretch freeze but wasn't part of stretch AND it was in unstable at the time of the jessie freeze but it wasn't part of jessie AND it is still not in testing AND it was not uploaded since the beginning of 2017. If you disagree and think that this package should remain in unstable, feel free to just close this bug. If this bug is still open one month from now (on 2017-09-06), it will be turned into a removal request, using: reassign -1 ftp.debian.org retitle -1 RM: node-jquery -- RoQA; missed both jessie and stretch thanks - Lucas, for the QA team. [1] https://lists.debian.org/debian-qa/2017/07/msg00021.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
[Pkg-javascript-devel] Bug#870963: jarisplayer: should jarisplayer be removed from unstable?
Source: jarisplayer User: debian...@lists.debian.org Usertags: qa-removals-post-stretch Hi, Following a discussion[1] on the debian-qa@ mailing list on packages that missed both jessie and stretch, I am proposing the removal of this package from unstable, because: it was in unstable at the time of the stretch freeze but wasn't part of stretch AND it was in unstable at the time of the jessie freeze but it wasn't part of jessie AND it is still not in testing AND it was not uploaded since the beginning of 2017. If you disagree and think that this package should remain in unstable, feel free to just close this bug. If this bug is still open one month from now (on 2017-09-06), it will be turned into a removal request, using: reassign -1 ftp.debian.org retitle -1 RM: jarisplayer -- RoQA; missed both jessie and stretch thanks - Lucas, for the QA team. [1] https://lists.debian.org/debian-qa/2017/07/msg00021.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
[Pkg-javascript-devel] Bug#870956: node-jsdom: should node-jsdom be removed from unstable?
Source: node-jsdom User: debian...@lists.debian.org Usertags: qa-removals-post-stretch Hi, Following a discussion[1] on the debian-qa@ mailing list on packages that missed both jessie and stretch, I am proposing the removal of this package from unstable, because: it was in unstable at the time of the stretch freeze but wasn't part of stretch AND it was in unstable at the time of the jessie freeze but it wasn't part of jessie AND it is still not in testing AND it was not uploaded since the beginning of 2017. If you disagree and think that this package should remain in unstable, feel free to just close this bug. If this bug is still open one month from now (on 2017-09-06), it will be turned into a removal request, using: reassign -1 ftp.debian.org retitle -1 RM: node-jsdom -- RoQA; missed both jessie and stretch thanks - Lucas, for the QA team. [1] https://lists.debian.org/debian-qa/2017/07/msg00021.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
[Pkg-javascript-devel] Bug#863934: node-dateformat: FTBFS: Test failures
Source: node-dateformat Version: 1.0.11-3 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170601-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): > [41m-Wed, 26 Nov 2014 13:19:44 GMT+[0m > [42m+Wed, 26 Nov 2014 13:19:44 UTC[0m > [0m[90m > at Context. (/<>/test/test_formats.js:64:14) > at Test.Runnable.run (/usr/lib/nodejs/mocha/lib/runnable.js:196:15) > at Runner.runTest (/usr/lib/nodejs/mocha/lib/runner.js:373:10) > at /usr/lib/nodejs/mocha/lib/runner.js:451:12 > at next (/usr/lib/nodejs/mocha/lib/runner.js:298:14) > at /usr/lib/nodejs/mocha/lib/runner.js:308:7 > at next (/usr/lib/nodejs/mocha/lib/runner.js:246:23) > at Immediate._onImmediate (/usr/lib/nodejs/mocha/lib/runner.js:275:5) > at processImmediate [as _immediateCallback] (timers.js:396:17) > [0m > > > debian/rules:7: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2017/06/01/node-dateformat_1.0.11-3_testing-i386.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#860634: node-grunt-contrib-copy: FTBFS on i386: Test failures
Source: node-grunt-contrib-copy Version: 1.0.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170418-i386 qa-ftbfs Justification: FTBFS in stretch on i386 Hi, During a rebuild of all packages in stretch (in a stretch chroot, not a sid chroot), your package failed to build on i386. Relevant part (hopefully): > at Object. (/usr/lib/nodejs/nodeunit/lib/core.js:236:16) > at /usr/lib/nodejs/nodeunit/lib/core.js:236:16 > at Object.exports.runTest (/usr/lib/nodejs/nodeunit/lib/core.js:70:9) > at /usr/lib/nodejs/nodeunit/lib/core.js:118:25 > at /usr/lib/nodejs/nodeunit/deps/async.js:513:13 > at iterate (/usr/lib/nodejs/nodeunit/deps/async.js:123:13) > at /usr/lib/nodejs/nodeunit/deps/async.js:134:25 > at /usr/lib/nodejs/nodeunit/deps/async.js:515:17 > at Immediate._onImmediate (/usr/lib/nodejs/nodeunit/lib/types.js:146:17) > at processImmediate [as _immediateCallback] (timers.js:396:17) > > > ✔ copy - timestamp_changed > > [1m[31mFAILURES: [39m[22m2/17 assertions failed (201ms) > debian/rules:13: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2017/04/18/node-grunt-contrib-copy_1.0.0-1_testing-i386.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#852923: dojo: FTBFS: OPTIMIZER FAILED: JavaException: java.lang.RuntimeException: null
Source: dojo Version: 1.11.0+dfsg-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20170128 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/dojo-1.11.0+dfsg' > ln -s /usr/share/java/js.jar /usr/share/java/shrinksafe.jar util/shrinksafe/ > cd util/buildscripts && ./build.sh profile=standard action=release > processing profile resource > /<>/dojo-1.11.0+dfsg/util/buildscripts/profiles/standard.profile.js > info(107) Package Version: package: dijit; version: 1.11.0 > processing profile resource > /<>/dojo-1.11.0+dfsg/dijit/dijit.profile.js > info(107) Package Version: package: dojox; version: 1.11.0 > processing profile resource > /<>/dojo-1.11.0+dfsg/dojox/dojox.profile.js > info(107) Package Version: package: dojo; version: 1.11.0 > processing profile resource > /<>/dojo-1.11.0+dfsg/dojo/dojo.profile.js > discovering resources... > starting reading resources... > starting processing raw resource content... > starting tokenizing resource... > starting processing resource tokens... > starting parsing resource... > starting processing resource AST... > warn(224) A plugin dependency was encountered but there was no build-time > plugin resolver. module: dijit/Fieldset; plugin: dojo/query > warn(224) A plugin dependency was encountered but there was no build-time > plugin resolver. module: dijit/RadioMenuItem; plugin: dojo/query > warn(224) A plugin dependency was encountered but there was no build-time > plugin resolver. module: dijit/Tree; plugin: dojo/query > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?./_BidiMixin; reference module id: > dijit/_WidgetBase > warn(224) A plugin dependency was encountered but there was no build-time > plugin resolver. module: dijit/form/_RadioButtonMixin; plugin: dojo/query > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?./bidi/Chart; reference module id: > dojox/charting/Chart > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?./bidi/Chart3D; reference module id: > dojox/charting/Chart3D > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?../bidi/action2d/ZoomAndPan; reference module > id: dojox/charting/action2d/MouseZoomAndPan > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?../bidi/action2d/Tooltip; reference module id: > dojox/charting/action2d/Tooltip > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?../bidi/action2d/ZoomAndPan; reference module > id: dojox/charting/action2d/TouchZoomAndPan > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?../bidi/axis2d/Default; reference module id: > dojox/charting/axis2d/Default > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?../bidi/widget/Chart; reference module id: > dojox/charting/widget/Chart > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?../bidi/widget/Legend; reference module id: > dojox/charting/widget/Legend > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?./bidi/_BidiMixin; reference module id: > dojox/grid/DataGrid > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?dojox/mobile/bidi/Accordion; reference module > id: dojox/mobile/Accordion > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?dojox/mobile/bidi/Badge; reference module id: > dojox/mobile/Badge > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?dojox/mobile/bidi/Button; reference module id: > dojox/mobile/Button > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?dojox/mobile/bidi/Carousel; reference module > id: dojox/mobile/Carousel > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?dojox/mobile/bidi/CarouselItem; reference > module id: dojox/mobile/CarouselItem > warn(224) A plugin dependency was encountered but there was no build-time > plugin resolver. module: dojox/mobile/DatePicker; plugin: > dojox/mobile/_PickerChooser > warn(216) dojo/has plugin resource could not be resolved during build-time. > plugin resource id: dojo-bidi?dojox/mobile/bidi/FormLayout; reference module > id: dojox/mobile/FormLayout > warn(216) dojo/has plugin resource could not be
[Pkg-javascript-devel] Bug#848749: node-fined: FTBFS: Test failures
Source: node-fined Version: 1.0.2-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161219 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > at Function.Module._load (module.js:300:12) > at Module.require (module.js:353:17) > at require (internal/module.js:12:17) > at /usr/lib/nodejs/mocha/lib/mocha.js:172:27 > at Array.forEach (native) > at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14) > at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31) > at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16) > at Module._compile (module.js:409:26) > at Object.Module._extensions..js (module.js:416:10) > at Module.load (module.js:343:32) > at Function.Module._load (module.js:300:12) > at Function.Module.runMain (module.js:441:10) > at startup (node.js:139:18) > at node.js:974:3 > debian/rules:13: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2016/12/19/node-fined_1.0.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#846743: node-normalize-path: FTBFS: Test failures
Source: node-normalize-path Version: 2.0.1-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161202 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > at Function.Module._load (module.js:300:12) > at Module.require (module.js:353:17) > at require (internal/module.js:12:17) > at /usr/lib/nodejs/mocha/lib/mocha.js:172:27 > at Array.forEach (native) > at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14) > at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31) > at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16) > at Module._compile (module.js:409:26) > at Object.Module._extensions..js (module.js:416:10) > at Module.load (module.js:343:32) > at Function.Module._load (module.js:300:12) > at Function.Module.runMain (module.js:441:10) > at startup (node.js:139:18) > at node.js:974:3 > debian/rules:13: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2016/12/02/node-normalize-path_2.0.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#846718: node-jquery-textcomplete: FTBFS: build-dependency not installable: node-jquery
Source: node-jquery-textcomplete Version: 1.7.3+dfsg-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161202 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper (>= 9), dh-buildinfo, nodejs, node-jquery, > grunt, node-grunt-contrib-concat, node-uglify > Filtered Build-Depends: debhelper (>= 9), dh-buildinfo, nodejs, node-jquery, > grunt, node-grunt-contrib-concat, node-uglify > dpkg-deb: building package > 'sbuild-build-depends-node-jquery-textcomplete-dummy' in > '/<>/resolver-B2iYrw/apt_archive/sbuild-build-depends-node-jquery-textcomplete-dummy.deb'. > dpkg-scanpackages: warning: Packages in archive but missing from override > file: > dpkg-scanpackages: warning: sbuild-build-depends-core-dummy > sbuild-build-depends-node-jquery-textcomplete-dummy > dpkg-scanpackages: info: Wrote 2 entries to output Packages file. > Ign:1 copy:/<>/resolver-B2iYrw/apt_archive ./ InRelease > Get:2 copy:/<>/resolver-B2iYrw/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/resolver-B2iYrw/apt_archive ./ Release.gpg > Get:4 copy:/<>/resolver-B2iYrw/apt_archive ./ Sources [541 B] > Get:5 copy:/<>/resolver-B2iYrw/apt_archive ./ Packages [625 B] > Fetched 2129 B in 0s (0 B/s) > Reading package lists... > W: No sandbox user '_apt' on the system, can not drop privileges > Reading package lists... > > Install node-jquery-textcomplete build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > sbuild-build-depends-node-jquery-textcomplete-dummy : Depends: node-jquery > but it is not going to be installed > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://aws-logs.debian.net/2016/12/02/node-jquery-textcomplete_1.7.3+dfsg-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#846692: node-repeat-element: FTBFS: Test failures
Source: node-repeat-element Version: 1.1.2+github-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161202 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > at Function.Module._load (module.js:300:12) > at Module.require (module.js:353:17) > at require (internal/module.js:12:17) > at /usr/lib/nodejs/mocha/lib/mocha.js:172:27 > at Array.forEach (native) > at Mocha.loadFiles (/usr/lib/nodejs/mocha/lib/mocha.js:169:14) > at Mocha.run (/usr/lib/nodejs/mocha/lib/mocha.js:356:31) > at Object. (/usr/lib/nodejs/mocha/bin/_mocha:366:16) > at Module._compile (module.js:409:26) > at Object.Module._extensions..js (module.js:416:10) > at Module.load (module.js:343:32) > at Function.Module._load (module.js:300:12) > at Function.Module.runMain (module.js:441:10) > at startup (node.js:139:18) > at node.js:974:3 > debian/rules:13: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2016/12/02/node-repeat-element_1.1.2+github-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#844938: node-inline-source-map: FTBFS: Tests failures
Source: node-inline-source-map Version: 0.6.1-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161118 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > pass: 0 > ok: false > count: 1 > fail: 1 > command: /usr/bin/nodejs > exitCode: 1 > timeout: 3 > arguments: > - test/source-content.js > file: test/source-content.js > ... > > 1..2 > # failed 2 of 2 tests > # time=402.429ms > debian/rules:11: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2016/11/18/node-inline-source-map_0.6.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#844913: node-isexe: FTBFS: Tests failures
Source: node-isexe Version: 1.1.2-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161118 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > module.js:327 > throw err; > ^ > > Error: Cannot find module 'nyc/bin/nyc.js' > at Function.Module._resolveFilename (module.js:325:15) > at Function.require.resolve (internal/module.js:16:19) > at getNycBin (/usr/lib/nodejs/tap/bin/run.js:10:21) > at respawnWithCoverage (/usr/lib/nodejs/tap/bin/run.js:409:15) > at main (/usr/lib/nodejs/tap/bin/run.js:119:5) > at Object. (/usr/lib/nodejs/tap/bin/run.js:52:1) > at Module._compile (module.js:409:26) > at Object.Module._extensions..js (module.js:416:10) > at Module.load (module.js:343:32) > at Function.Module._load (module.js:300:12) > debian/rules:13: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2016/11/18/node-isexe_1.1.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#844922: node-string-decoder: FTBFS: Tests failures
Source: node-string-decoder Version: 0.10.25-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161118 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > plan: > start: 1 > end: 0 > skipAll: true > failures: > - tapError: 'Plan of 1..0, but test points encountered' > command: /usr/bin/nodejs > arguments: > - test/simple/test-string-decoder-end.js > file: test/simple/test-string-decoder-end.js > ... > > 1..1 > # failed 1 of 1 tests > # time=158.079ms > debian/rules:11: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2016/11/18/node-string-decoder_0.10.25-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#844905: node-nan: FTBFS: Tests failures
Source: node-nan Version: 2.4.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20161118 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > # Subtest: wrappedobjectfactory > 1..4 > ok 1 - type is function > ok 2 - type is number > ok 3 - should be equal > ok 4 - should be equal > ok 1 - wrappedobjectfactory # time=12.252ms > > 1..1 > # time=38.425ms > ok 37 - test/js/wrappedobjectfactory-test.js # time=143.746ms > > 1..37 > # failed 1 of 37 tests > # time=7671.036ms > debian/rules:13: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2016/11/18/node-nan_2.4.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#844137: node-groove: FTBFS: Tests failures
Source: node-groove Version: 2.5.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-2016 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Leaving directory '/<>' >debian/rules override_dh_auto_test > make[1]: Entering directory '/<>' > mocha --reporter spec > > [0m[0m > [32m ✓[0m[90m version [0m > [32m ✓[0m[90m logging [0m > [32m ✓[0m[90m open fails for bogus file [0m > [32m ✓[0m[90m open file and read metadata [0m > [32m ✓[0m[90m update metadata [0m > [32m ✓[0m[90m create empty playlist [0m > Failed to create secure directory (/sbuild-nonexistent/.config/pulse): No > such file or directory > [32m ✓[0m[90m create empty player [0m > [32m ✓[0m[90m playlist item ids [0m > debian/rules:20: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/2016/11/11/node-groove_2.5.0-1_unstable.log This failure happens on a CPU with TSX extensions available, but is not reproducible on a machine without them. For context, I recommend reading the thread starting at https://lists.debian.org/debian-devel/2016/11/msg00210.html The node used is an Amazon EC2 VM with 64 cores. /proc/cpuinfo says: model: 79 model name : Intel(R) Xeon(R) CPU E5-2686 v4 @ 2.30GHz stepping : 1 A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#841614: node-es6-promise: FTBFS: compile-modules shows help
On 29/10/16 at 11:14 +0200, Julien Puydt wrote: > Hi, > > I tried to "pbuilder create" a new base.tgz, but it still had tzdata and > lsb-base, so I had to "pbuilder login --save-after-login" and remove them by > hand using "dpkg --purge" (then "apt-get autoremove" that did nothing). I > still had no problem building node-es6-promise. > > How can I get the clean, minimal and up-to-date chroot you mention in your > report? Hi Julien, You can install debfoster in the chroot, and then run debfoster -o UseRecommends=no -o MaxPriority=required to clean up the chroot from non-essential packages. Lucas -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#841614: node-es6-promise: FTBFS: compile-modules shows help
Source: node-es6-promise Version: 3.2.2+ds-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 sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/node-es6-promise-3.2.2+ds' > mkdir dist > compile-modules convert -f bundle -o dist/es6-promise.js > lib/es6-promise.umd.js > compile-modules [--help] [--version] [] > > Commands > > convert Converts modules from `import`/`export` to an ES5 equivalent. > help Display help for a given command. > debian/rules:10: recipe for target 'override_dh_auto_build' failed > make[1]: *** [override_dh_auto_build] Error 1 If the failure looks somehow time/timezone related: Note that this rebuild was performed without the 'tzdata' package installed in the chroot. tzdata used be (transitively) part of build-essential, but it no longer is. If this package requires it to build, it should be added to build-depends. For the release team's opinion on this, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185 If the failure looks LSB-related: similarly to tzdata, lsb-base is not installed in the build chroot. The full build log is available from: http://aws-logs.debian.net/2016/10/21/node-es6-promise_3.2.2+ds-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#841587: node-livescript: FTBFS: /bin/sh: 1: /usr/bin/lsc: not found
Source: node-livescript Version: 1.5.0+dfsg-2 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 sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules build > dh build >dh_testdir >dh_update_autotools_config >dh_auto_configure >dh_auto_build > make -j1 > make[1]: Entering directory '/<>/node-livescript-1.5.0+dfsg' > mkdir -p lib/ > /usr/bin/lsc --output lib --bare --compile "src/ast.ls" > /bin/sh: 1: /usr/bin/lsc: not found > Makefile:17: recipe for target 'lib/ast.js' failed > make[1]: *** [lib/ast.js] Error 127 If the failure looks somehow time/timezone related: Note that this rebuild was performed without the 'tzdata' package installed in the chroot. tzdata used be (transitively) part of build-essential, but it no longer is. If this package requires it to build, it should be added to build-depends. For the release team's opinion on this, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=836940#185 If the failure looks LSB-related: similarly to tzdata, lsb-base is not installed in the build chroot. The full build log is available from: http://aws-logs.debian.net/2016/10/21/node-livescript_1.5.0+dfsg-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#837285: node-iconv: FTBFS: Tests failures
Source: node-iconv
Version: 2.1.11-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160910 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> nodejs test/test-basic.js
>
> assert.js:90
> throw new assert.AssertionError({
> ^
> AssertionError: '?a va' == 'ca va'
> at Object. (/<>/test/test-basic.js:110:8)
> at Module._compile (module.js:409:26)
> at Object.Module._extensions..js (module.js:416:10)
> at Module.load (module.js:343:32)
> at Function.Module._load (module.js:300:12)
> at Function.Module.runMain (module.js:441:10)
> at startup (node.js:139:18)
> at node.js:968:3
> debian/rules:22: recipe for target 'override_dh_auto_test' failed
The full build log is available from:
http://aws-logs.debian.net/2016/09/10/node-iconv_2.1.11-1_unstable.log
(That DNS record was just updated. Use
http://ec2-52-58-237-241.eu-central-1.compute.amazonaws.com if it
doesn't work)
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#835704: node-ast-util: FTBFS: Error: Cannot find module './fork'
Source: node-ast-util Version: 0.6.0-1 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160828 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > ./bin/make-builder < helpers/get.js >> lib/helpers/get.js > module.js:327 > throw err; > ^ > > Error: Cannot find module './fork' > at Function.Module._resolveFilename (module.js:325:15) > at Function.Module._load (module.js:276:25) > at Module.require (module.js:353:17) > at require (internal/module.js:12:17) > at Object. (/usr/lib/nodejs/ast-types/main.js:1:80) > at Module._compile (module.js:409:26) > at Object.Module._extensions..js (module.js:416:10) > at Module.load (module.js:343:32) > at Function.Module._load (module.js:300:12) > at Module.require (module.js:353:17) > Makefile:6: recipe for target 'lib/helpers/get.js' failed > make[1]: *** [lib/helpers/get.js] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2016/08/28/node-ast-util_0.6.0-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. -- Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#831243: nodejs: FTBFS: Tests failures
Source: nodejs Version: 4.4.7~dfsg-2 Severity: serious Tags: stretch sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20160714 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/«PKGBUILDDIR»' > /usr/bin/python tools/test.py -p tap --mode=release --flaky-tests=dontcare \ > --arch=x64 --timeout=3000 message parallel sequential > 1..1012 > ok 1 parallel/test-arm-math-exp-regress-1376 > --- > duration_ms: 0.88 > ... > ok 2 parallel/test-assert > --- > duration_ms: 0.137 > ... > ok 3 parallel/test-assert-typedarray-deepequal > --- > duration_ms: 0.609 > ... > ok 4 parallel/test-async-wrap-check-providers > --- > duration_ms: 0.170 > ... > ok 5 parallel/test-async-wrap-disabled-propagate-parent > --- > duration_ms: 0.89 > ... > ok 6 parallel/test-async-wrap-propagate-parent > --- > duration_ms: 0.88 > ... > ok 7 parallel/test-async-wrap-throw-no-init > --- > duration_ms: 0.71 > ... > ok 8 parallel/test-bad-unicode > --- > duration_ms: 0.71 > ... > ok 9 parallel/test-beforeexit-event > --- > duration_ms: 0.88 > ... > ok 10 parallel/test-beforeexit-event-exit > --- > duration_ms: 0.71 > ... > ok 11 parallel/test-buffer > --- > duration_ms: 0.110 > ... > ok 12 parallel/test-buffer-arraybuffer > --- > duration_ms: 0.88 > ... > ok 13 parallel/test-buffer-ascii > --- > duration_ms: 0.71 > ... > ok 14 parallel/test-buffer-bytelength > --- > duration_ms: 0.89 > ... > ok 15 parallel/test-buffer-concat > --- > duration_ms: 0.89 > ... > ok 16 parallel/test-buffer-fakes > --- > duration_ms: 0.88 > ... > ok 17 parallel/test-buffer-indexof > --- > duration_ms: 0.89 > ... > ok 18 parallel/test-buffer-inheritance > --- > duration_ms: 0.71 > ... > ok 19 parallel/test-buffer-inspect > --- > duration_ms: 0.71 > ... > ok 20 parallel/test-buffer-iterator > --- > duration_ms: 0.71 > ... > ok 21 parallel/test-buffer-slow > --- > duration_ms: 0.89 > ... > ok 22 parallel/test-buffer-zero-fill-reset > --- > duration_ms: 0.72 > ... > ok 23 parallel/test-c-ares > --- > duration_ms: 0.89 > ... > ok 24 parallel/test-child-process-buffering > --- > duration_ms: 0.89 > ... > ok 25 parallel/test-child-process-constructor > --- > duration_ms: 0.89 > ... > ok 26 parallel/test-child-process-cwd > --- > duration_ms: 0.110 > ... > ok 27 parallel/test-child-process-default-options > --- > duration_ms: 0.89 > ... > ok 28 parallel/test-child-process-detached > --- > duration_ms: 0.170 > ... > ok 29 parallel/test-child-process-disconnect > --- > duration_ms: 0.211 > ... > ok 30 parallel/test-child-process-double-pipe > --- > duration_ms: 0.110 > ... > ok 31 parallel/test-child-process-env > --- > duration_ms: 0.89 > ... > ok 32 parallel/test-child-process-exec-buffer > --- > duration_ms: 0.89 > ... > ok 33 parallel/test-child-process-exec-cwd > --- > duration_ms: 0.110 > ... > ok 34 parallel/test-child-process-exec-env > --- > duration_ms: 0.110 > ... > ok 35 parallel/test-child-process-exec-error > --- > duration_ms: 0.110 > ... > ok 36 parallel/test-child-process-exit-code > --- > duration_ms: 0.263 > ... > ok 37 parallel/test-child-process-flush-stdio > --- > duration_ms: 0.110 > ... > ok 38 parallel/test-child-process-fork > --- > duration_ms: 0.212 > ... > ok 39 parallel/test-child-process-fork-and-spawn > --- > duration_ms: 0.264 > ... > ok 40 parallel/test-child-process-fork-close > --- > duration_ms: 0.170 > ... > ok 41 parallel/test-child-process-fork-dgram > --- > duration_ms: 0.328 > ... > ok 42 parallel/test-child-process-fork-exec-argv > --- > duration_ms: 0.263 > ... > ok 43 parallel/test-child-process-fork-exec-path > --- > duration_ms: 0.610 > ... > ok 44 parallel/test-child-process-fork-net > --- > duration_ms: 0.212 > ... > ok 45 parallel/test-child-process-fork-net2 > --- > duration_ms: 0.409 > ... > ok 46 parallel/test-child-process-fork-ref > --- > duration_ms: 0.509 > ... > ok 47 parallel/test-child-process-fork-ref2 > --- > duration_ms: 0.710 > ... > ok 48 parallel/test-child-process-fork-regr-gh-2847 > --- > duration_ms: 0.263 > ... > ok 49 parallel/test-child-process-fork3 > --- > duration_ms: 0.328 > ... > ok 50 parallel/test-child-process-internal > --- > duration_ms: 0.170 > ... > ok 51 parallel/test-child-process-ipc > --- > duration_ms: 0.170 > ... > ok 52 parallel/test-child-process-kill > --- > duration_ms: 0.89 > ... > ok 53 parallel/test-child-process-recv-handle > --- > duration_ms: 0.170 > ... > ok 54 parallel/test-child-process-send-cb > --- > duration_ms: 0.170 > ... > ok 55 parallel/test-child-process-send-utf8 > --- > duration_ms: 0.211 > ... >
[Pkg-javascript-devel] Bug#831161: libv8-3.14: FTBFS with GCC 6: ../src/spaces.h:837:39: error: nonnull argument 'this' compared to NULL [-Werror=nonnull-compare]
Source: libv8-3.14
Version: 3.14.5.8-10
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160713 qa-ftbfs
Justification: FTBFS with GCC 6 on amd64
Hi,
During a rebuild of all packages in sid using the gcc-defaults package
available in experimental to make GCC default to version 6, your package failed
to build on amd64. For more information about GCC 6 and Stretch, see:
- https://wiki.debian.org/GCC6
- https://lists.debian.org/debian-devel-announce/2016/06/msg7.html
Relevant part (hopefully):
> g++ '-DENABLE_DEBUGGER_SUPPORT' '-DENABLE_EXTRA_CHECKS'
> '-DV8_TARGET_ARCH_X64' '-DBUILDING_V8_SHARED' '-DV8_SHARED' -I../src -Wall
> -Werror -W -Wno-unused-parameter -Wnon-virtual-dtor -pthread -fno-rtti
> -fno-exceptions -pedantic -ansi -fvisibility=hidden -fPIC -fdata-sections
> -ffunction-sections -O3 -MMD -MF
> /«PKGBUILDDIR»/out/x64.release/.deps//«PKGBUILDDIR»/out/x64.release/obj.target/v8_base/src/spaces.o.d.raw
> -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time
> -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
> /«PKGBUILDDIR»/out/x64.release/obj.target/v8_base/src/spaces.o
> ../src/spaces.cc
> In file included from ../src/mark-compact.h:32:0,
> from ../src/incremental-marking.h:33,
> from ../src/heap.h:35,
> from ../src/elements.h:33,
> from ../src/objects-inl.h:38,
> from ../src/v8.h:60,
> from ../src/spaces.cc:28:
> ../src/spaces.h: In member function 'bool v8::internal::CodeRange::exists()':
> ../src/spaces.h:837:39: error: nonnull argument 'this' compared to NULL
> [-Werror=nonnull-compare]
>bool exists() { return this != NULL && code_range_ != NULL; }
>^
> ../src/spaces.h: In member function 'bool
> v8::internal::CodeRange::contains(v8::internal::Address)':
> ../src/spaces.h:839:5: error: nonnull argument 'this' compared to NULL
> [-Werror=nonnull-compare]
> if (this == NULL || code_range_ == NULL) return false;
> ^~
> cc1plus: all warnings being treated as errors
> make[2]: *** [/«PKGBUILDDIR»/out/x64.release/obj.target/v8_base/src/spaces.o]
> Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2016/07/13/libv8-3.14_3.14.5.8-10_unstable_gcc6.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#775627: Bug#775627: node-tap: FTBFS in jessie: Tests failures
On 18/01/15 at 02:45 +0100, Jérémy Lal wrote: Le dimanche 18 janvier 2015 à 01:42 +0100, Lucas Nussbaum a écrit : 8 http://aws-logs.debian.net/ftbfs-logs/2015/01/17/node-tap_0.4.13-1_jessie.log I'd like to know the output of nodejs -e console.log(process.platform) on that build machine, to see if it is nodejs that sets a wrong process.platform or if it is this node-tap test that assumes something wrong about the linux platform. Hi, # nodejs -e console.log(process.platform) linux Lucas ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#775627: Bug#775627: node-tap: FTBFS in jessie: Tests failures
On 18/01/15 at 18:43 +0100, Jérémy Lal wrote: Le dimanche 18 janvier 2015 à 10:04 +0100, Lucas Nussbaum a écrit : On 18/01/15 at 02:45 +0100, Jérémy Lal wrote: Le dimanche 18 janvier 2015 à 01:42 +0100, Lucas Nussbaum a écrit : 8 http://aws-logs.debian.net/ftbfs-logs/2015/01/17/node-tap_0.4.13-1_jessie.log I'd like to know the output of nodejs -e console.log(process.platform) on that build machine, to see if it is nodejs that sets a wrong process.platform or if it is this node-tap test that assumes something wrong about the linux platform. Hi, # nodejs -e console.log(process.platform) linux On linux platform the test expects exit code 128 + SIGTERM to be returned and on other platforms just SIGTERM. Fixing this test is easy, but since this is the first time it fails, is it possible the platform the tests were run on could be the cause of the different exit code ? Erm, I really don't know. There shouldn't be anything specific to the testbed that should have an influence here... But I can give you access to a VM if you want to dig further. Lucas ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#768738: jarisplayer: FTBFS in jessie: build-dependency not installable: haxe
Source: jarisplayer Version: 2.0.15+20131104~dfsg-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install jarisplayer build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-jarisplayer-dummy : Depends: haxe but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/jarisplayer_2.0.15+20131104~dfsg-1_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#768754: backbone: FTBFS in jessie: build-dependency not installable: phantomjs
Source: backbone Version: 0.9.10-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install backbone build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-backbone-dummy : Depends: phantomjs but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/backbone_0.9.10-1_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#768672: node-cssom: FTBFS in jessie: build-dependency not installable: node-jake
Source: node-cssom Version: 0.3.0-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install node-cssom build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-node-cssom-dummy : Depends: node-jake but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/node-cssom_0.3.0-1_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#768677: node-redis: FTBFS in jessie: Tests failures
Source: node-redis Version: 0.12.1-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): - optional_callback: 1 ms - optional_callback_undefined: 0 ms - enable_offline_queue_true:node_redis: no callback to send error: Length: 84 Uncaught exception: Error: Length: 84 at ReplyParser.anonymous (/«PKGBUILDDIR»/index.js:317:31) at ReplyParser.emit (events.js:95:17) at ReplyParser.send_error (/«PKGBUILDDIR»/lib/parser/javascript.js:296:10) at ReplyParser.execute (/«PKGBUILDDIR»/lib/parser/javascript.js:181:22) at RedisClient.on_data (/«PKGBUILDDIR»/index.js:547:27) at Socket.anonymous (/«PKGBUILDDIR»/index.js:102:14) at Socket.emit (events.js:95:17) at Socket.anonymous (_stream_readable.js:748:14) at Socket.emit (events.js:92:17) at emitReadable_ (_stream_readable.js:410:10) make[1]: *** [override_dh_auto_test] Error 1 debian/rules:13: recipe for target 'override_dh_auto_test' failed The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/node-redis_0.12.1-2_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#768681: nodejs: FTBFS in jessie: tests failures
Source: nodejs Version: 0.10.29~dfsg-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): make[2]: Entering directory '/«PKGBUILDDIR»/out' make[2]: Nothing to be done for 'all'. make[2]: Leaving directory '/«PKGBUILDDIR»/out' ln -fs out/Release/node node /usr/bin/python tools/test.py --arch=x64 simple [00:00|% 0|+ 0|- 0]: release test-abort-fatal-error [00:00|% 0|+ 1|- 0]: release test-arraybuffer-slice [00:00|% 0|+ 2|- 0]: release test-assert [00:00|% 0|+ 3|- 0]: release test-bad-unicode [00:00|% 0|+ 4|- 0]: release test-buffer [00:00|% 0|+ 5|- 0]: release test-buffer-ascii [00:00|% 0|+ 6|- 0]: release test-buffer-concat [00:00|% 1|+ 7|- 0]: release test-buffer-regress-GH-2659 [00:00|% 1|+ 8|- 0]: release test-c-ares [00:01|% 1|+ 9|- 0]: release test-chdir [00:01|% 1|+ 10|- 0]: release test-child-process-buffering [00:01|% 1|+ 11|- 0]: release test-child-process-customfd-bounded [00:01|% 1|+ 12|- 0]: release test-child-process-cwd [00:01|% 2|+ 13|- 0]: release test-child-process-detached [00:01|% 2|+ 14|- 0]: release test-child-process-disconnect [00:01|% 2|+ 15|- 0]: release test-child-process-double-pipe [00:01|% 2|+ 16|- 0]: release test-child-process-env [00:02|% 2|+ 17|- 0]: release test-child-process-exec-cwd [00:02|% 2|+ 18|- 0]: release test-child-process-exec-env [00:02|% 3|+ 19|- 0]: release test-child-process-exec-error [00:02|% 3|+ 20|- 0]: release test-child-process-exit-code [00:02|% 3|+ 21|- 0]: release test-child-process-fork [00:02|% 3|+ 22|- 0]: release test-child-process-fork-and-spawn [00:02|% 3|+ 23|- 0]: release test-child-process-fork-close [00:03|% 3|+ 24|- 0]: release test-child-process-fork-dgram [00:03|% 4|+ 25|- 0]: release test-child-process-fork-exec-argv [00:03|% 4|+ 26|- 0]: release test-child-process-fork-exec-path [00:04|% 4|+ 27|- 0]: release test-child-process-fork-getconnections [00:04|% 4|+ 28|- 0]: release test-child-process-fork-net [00:04|% 4|+ 29|- 0]: release test-child-process-fork-net2 [00:04|% 4|+ 30|- 0]: release test-child-process-fork-ref [00:05|% 5|+ 31|- 0]: release test-child-process-fork-ref2 [00:05|% 5|+ 32|- 0]: release test-child-process-fork3 [00:05|% 5|+ 33|- 0]: release test-child-process-internal [00:06|% 5|+ 34|- 0]: release test-child-process-ipc [00:06|% 5|+ 35|- 0]: release test-child-process-kill [00:06|% 5|+ 36|-
[Pkg-javascript-devel] Bug#768704: leaflet-markercluster: FTBFS in jessie: build-dependency not installable: node-jake
Source: leaflet-markercluster Version: 0.4.0~dfsg-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20141108 qa-ftbfs Justification: FTBFS in jessie on amd64 Hi, During a rebuild of all packages in jessie (in a jessie chroot, not a sid chroot), your package failed to build on amd64. Relevant part (hopefully): ┌──┐ │ Install leaflet-markercluster build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-leaflet-markercluster-dummy : Depends: node-jake but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/11/08/leaflet-markercluster_0.4.0~dfsg-1_jessie.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#759843: node-mapnik: FTBFS: vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No such file or directory
Source: node-mapnik Version: 1.2.3-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20140830 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): make[2]: Entering directory '/«PKGBUILDDIR»/build' gyp info spawn make gyp CXX(target) Release/obj.target/_mapnik/src/node_mapnik.o info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ] CXX(target) Release/obj.target/_mapnik/src/mapnik_map.o In file included from ../src/mapnik_map.cpp:10:0: /usr/include/vector_tile_processor.hpp:48:38: fatal error: mapnik3x_compatibility.hpp: No such file or directory #include mapnik3x_compatibility.hpp ^ compilation terminated. make[2]: *** [Release/obj.target/_mapnik/src/mapnik_map.o] Error 1 The full build log is available from: http://aws-logs.debian.net/ftbfs-logs/2014/08/30/node-mapnik_1.2.3-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. The build was done with DEB_BUILD_OPTIONS=parallel=4, so if your packaging tries to support this, it might be a good idea to explore whether this might be the cause of the failure. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#707503: node-postgres: FTBFS: xargs: node: No such file or directory
Source: node-postgres Version: 0.7.1-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: debian/rules build test -x debian/rules mkdir -p . Scanning upstream source for new/changed copyright notices... licensecheck -c '.*' -r --copyright -i '^debian/(changelog|copyright(|_hints|_newhints))' -l '9' * | /usr/lib/cdbs/licensecheck2dep5 debian/copyright_newhints 4 combinations of copyright and licensing found. WARNING: The following (and possibly more) new or changed notices discovered: License: Expat FIXME Files: debian/rules Copyright: 2011-2012, Jonas Smedegaard d...@jones.dk License: GPL-2+ To fix the situation please do the following: 1) Fully compare debian/copyright_hints with debian/copyright_newhints 2) Update debian/copyright as needed 3) Replace debian/copyright_hints with debian/copyright_newhints touch debian/stamp-copyright-check touch debian/stamp-upstream-cruft CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall CXXFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall CPPFLAGS=-D_FORTIFY_SOURCE=2 LINKFLAGS=-Wl,-z,relro NOCOLOR=1 NODE_PATH=/«PKGBUILDDIR»/debian/node-pg/usr/lib/nodejs/pg/native node-waf -v configure Checking for program g++ or c++ : /usr/bin/g++ Checking for program cpp : /usr/bin/cpp Checking for program ar : /usr/bin/ar Checking for program ranlib : /usr/bin/ranlib Checking for g++ : ok Checking for node path : not found Checking for node prefix : ok /usr Checking for program pg_config : /usr/bin/pg_config 'configure' finished successfully (0.056s) touch debian/stamp-node-waf-configure NOCOLOR=1 NODE_PATH=/«PKGBUILDDIR»/debian/node-pg/usr/lib/nodejs/pg/native node-waf -v build Waf: Entering directory `/«PKGBUILDDIR»/build' [1/2] cxx: src/binding.cc - build/Release/src/binding_1.o 16:39:45 runner system command - ['/usr/bin/g++', '-g', '-O2', '-fstack-protector', '--param=ssp-buffer-size=4', '-Wformat', '-Werror=format-security', '-Wall', '-g', '-D_LARGEFILE_SOURCE', '-fPIC', '-DPIC', '-D_LARGEFILE_SOURCE', '-D_FILE_OFFSET_BITS=64', '-D_FORTIFY_SOURCE=2', '-D_GNU_SOURCE', '-I/usr/include/postgresql', '-I/usr/include/nodejs', '../src/binding.cc', '-c', '-o', 'Release/src/binding_1.o'] ../src/binding.cc: In static member function 'static v8::Handlev8::Value Connection::DispatchParameterizedQuery(const v8::Arguments, bool)': ../src/binding.cc:196:19: warning: variable 'params' set but not used [-Wunused-but-set-variable] ../src/binding.cc: In constructor 'Connection::Connection()': ../src/binding.cc:247:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] ../src/binding.cc:247:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] ../src/binding.cc:247:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] ../src/binding.cc:249:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] ../src/binding.cc:249:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] ../src/binding.cc:249:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] [2/2] cxx_link: build/Release/src/binding_1.o - build/Release/binding.node 16:39:46 runner system command - ['/usr/bin/g++', 'Release/src/binding_1.o', '-o', '/«PKGBUILDDIR»/build/Release/binding.node', '-Wl,-z,relro', '-shared', '-L/usr/lib', '-Wl,-Bdynamic', '-lpq'] Waf: Leaving directory `/«PKGBUILDDIR»/build' 'build' finished successfully (1.168s) make test make[1]: Entering directory `/«PKGBUILDDIR»' xargs: node: No such file or directory make[1]: *** [test-unit] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/node-postgres_0.7.1-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#707510: node-expat: FTBFS: /bin/sh: 1: node: not found
Source: node-expat Version: 1.6.0-2 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: debian/rules build test -x debian/rules mkdir -p . WARNING: copyright-check disabled - licensecheck (from devscripts package) is missing. touch debian/stamp-copyright-check touch debian/stamp-upstream-cruft CFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall CXXFLAGS=-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall CPPFLAGS=-D_FORTIFY_SOURCE=2 LINKFLAGS=-Wl,-z,relro NOCOLOR=1 NODE_PATH=/«PKGBUILDDIR»/debian/node-node-expat/usr/lib/nodejs node-waf -v configure Checking for program g++ or c++ : /usr/bin/g++ Checking for program cpp : /usr/bin/cpp Checking for program ar : /usr/bin/ar Checking for program ranlib : /usr/bin/ranlib Checking for g++ : ok Checking for node path : not found Checking for node prefix : ok /usr Checking for header expat.h : 16:40:01 runner system command - ['/usr/bin/g++', '-g', '-O2', '-fstack-protector', '--param=ssp-buffer-size=4', '-Wformat', '-Werror=format-security', '-Wall', '-g', '-D_FORTIFY_SOURCE=2', '-I/usr/local/include', '-I/usr/include', '../test.cpp', '-c', '-o', 'Release/test_1.o'] 16:40:01 runner system command - ['/usr/bin/g++', 'Release/test_1.o', '-o', '/«PKGBUILDDIR»/build/.conf_check_0/testbuild/Release/testprog', '-Wl,-z,relro'] yes 'configure' finished successfully (0.207s) touch debian/stamp-node-waf-configure NOCOLOR=1 NODE_PATH=/«PKGBUILDDIR»/debian/node-node-expat/usr/lib/nodejs node-waf -v build Waf: Entering directory `/«PKGBUILDDIR»/build' [1/2] cxx: node-expat.cc - build/Release/node-expat_1.o 16:40:01 runner system command - ['/usr/bin/g++', '-g', '-O2', '-fstack-protector', '--param=ssp-buffer-size=4', '-Wformat', '-Werror=format-security', '-Wall', '-g', '-fPIC', '-DPIC', '-D_LARGEFILE_SOURCE', '-D_FILE_OFFSET_BITS=64', '-D_FORTIFY_SOURCE=2', '-D_GNU_SOURCE', '-I/usr/local/include', '-I/usr/include', '-I/usr/include/nodejs', '../node-expat.cc', '-c', '-o', 'Release/node-expat_1.o'] [2/2] cxx_link: build/Release/node-expat_1.o - build/Release/node_expat.node 16:40:02 runner system command - ['/usr/bin/g++', 'Release/node-expat_1.o', '-o', '/«PKGBUILDDIR»/build/Release/node_expat.node', '-Wl,-z,relro', '-shared', '-L/usr/lib', '-L/usr/lib64', '-L/usr/local/lib', '-L/usr/local/lib64', '-Wl,-Bdynamic', '-lexpat'] Waf: Leaving directory `/«PKGBUILDDIR»/build' 'build' finished successfully (0.939s) NODE_DISABLE_COLORS=1 node test.js /bin/sh: 1: node: not found make: *** [debian/stamp-node-waf-build] Error 127 The full build log is available from: http://people.debian.org/~lucas/logs/2013/05/09/node-expat_1.6.0-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#684828: backbone: FTBFS: build-dependency not installable: libnode-uglify
reopen 684828 thanks On 25/08/12 at 19:11 -0400, David Prévot wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Lucas, QA contributors, Le 14/08/2012 03:18, Lucas Nussbaum a écrit : Source: backbone […] Justification: FTBFS in wheezy on amd64 Hi, During a rebuild of all packages in *wheezy*, your package failed to build on amd64. […] The following packages have unmet dependencies: sbuild-build-depends-backbone-dummy : Depends: libnode-uglify but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. Actually its an OR dependency: libnode-uglify | yui-compressor The package builds fine in a Wheezy amd64 pbuilder chroot (pulling yui-compressor), thus closing the bug. I just wanted to put some light on this issue: maybe the resolver used to perform the archive rebuild could be improved to avoid this kind of false positive. Hi, By default, sbuild ignores alternative build-dependencies (a | b) and only uses the first package. that is to ensure reproducible builds, and avoid situations where packages build against different b-deps on different architectures. So the bug is valid, and should be fixed in wheezy (and I'm not aware of the release team considering those failures non-RC). I've tagged a few FTBFS on wheezy as unreproducible (because I didn't investigate why it failed ten days ago, or because I couldn't find an obvious reason), should I simply have closed them? Did you Cc me? I have very little time for Debian recently, but try to keep up with bugmail where I'm Cced. Anyway, a good way to make progress is usually to provide a build log, and a diff between my log and your log. Lucas ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#684828: backbone: FTBFS: build-dependency not installable: libnode-uglify
On 26/08/12 at 16:57 -0400, David Prévot wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Le 26/08/2012 13:28, Lucas Nussbaum a écrit : On 25/08/12 at 19:11 -0400, David Prévot wrote: Le 14/08/2012 03:18, Lucas Nussbaum a écrit : Source: backbone […] Justification: FTBFS in wheezy on amd64 Actually its an OR dependency: libnode-uglify | yui-compressor By default, sbuild ignores alternative build-dependencies (a | b) Thanks for your quick answer, and thanks Jonas who was even quicker, preparing a t-p-u right now. I've tagged a few FTBFS on wheezy as unreproducible (because I didn't investigate why it failed ten days ago, or because I couldn't find an obvious reason), should I simply have closed them? Did you Cc me? I have very little time for Debian recently, but try to keep up with bugmail where I'm Cced. No, sorry about that, those were #684833, #684837 and #684860. Cédric already looked at the last one with the same result than me, and should investigate again soon. Anyway, a good way to make progress is usually to provide a build log, and a diff between my log and your log. Thanks for the tip, I'll try to have a second look at the first two, following your advice. OK, the first two look like bugs that will be easier to understand with a diff (maybe a build-dep that was broken was fixed in the meantime?). For the third one, I'm a bit more puzzled. Note that I auto-retry builds before filing, so when I file a bug, it means that the build failed twice in a row. This does not exclude chroot configuration issues, or environment issues, but at least excludes all random/cosmic rays problems. Lucas ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#684828: backbone: FTBFS: build-dependency not installable: libnode-uglify
Source: backbone Version: 0.5.3-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120814 qa-ftbfs Justification: FTBFS in wheezy on amd64 Hi, During a rebuild of all packages in *wheezy*, your package failed to build on amd64. Relevant part: ┌──┐ │ Install backbone build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: sbuild-build-depends-backbone-dummy : Depends: libnode-uglify but it is not installable E: Unable to correct problems, you have held broken packages. apt-get failed. The full build log is available from: http://people.debian.org/~lucas/logs/2012/08/14/backbone_0.5.3-2_wheezy.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#678762: node-xmpp: FTBFS: Error: Cannot find module 'node-expat'
Source: node-xmpp Version: 0.3.2-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120624 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: debian/rules build test -x debian/rules mkdir -p . WARNING: copyright-check disabled - licensecheck (from devscripts package) is missing. touch debian/stamp-copyright-check touch debian/stamp-upstream-cruft vows --spec module.js:337 throw new Error(Cannot find module ' + request + '); ^ Error: Cannot find module 'node-expat' at Function._resolveFilename (module.js:337:11) at Function._load (module.js:279:25) at Module.require (module.js:359:17) at require (module.js:375:17) at Object.anonymous (/«PKGBUILDDIR»/lib/xmpp/stream_parser.js:3:13) at Module._compile (module.js:446:26) at Object..js (module.js:464:10) at Module.load (module.js:353:32) at Function._load (module.js:311:12) at Module.require (module.js:359:17) make: *** [build/node-node-xmpp] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/24/node-xmpp_0.3.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#676736: node-mapnik: FTBFS: parse.hpp:155:9: internal compiler error: Segmentation fault
Source: node-mapnik
Version: 0.6.7-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120609 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
make[1]: Entering directory `/«PKGBUILDDIR»'
node-waf build
Waf: Entering directory `/«PKGBUILDDIR»/build'
[ 1/12] cxx: src/node_mapnik.cpp - build/Release/src/node_mapnik_1.o
../src/node_mapnik.cpp:63:22: warning: 'v8::Handlev8::Value
node_mapnik::clearCache(const v8::Arguments)' defined but not used
[-Wunused-function]
[ 2/12] cxx: src/mapnik_map.cpp - build/Release/src/mapnik_map_1.o
../src/mapnik_map.cpp: In static member function 'static
v8::Handlev8::Value Map::renderLayerSync(const v8::Arguments)':
../src/mapnik_map.cpp:1670:12: warning: variable 'scale_factor' set but not
used [-Wunused-but-set-variable]
[ 3/12] cxx: src/mapnik_color.cpp - build/Release/src/mapnik_color_1.o
In file included from
/usr/include/boost/spirit/home/qi/detail/parse_auto.hpp:14:0,
from /usr/include/boost/spirit/home/qi/auto.hpp:16,
from /usr/include/boost/spirit/home/qi.hpp:15,
from /usr/include/boost/spirit/include/qi.hpp:16,
from /usr/include/mapnik/css_color_grammar.hpp:32,
from /usr/include/mapnik/color_factory.hpp:39,
from ../src/mapnik_color.cpp:4:
/usr/include/boost/spirit/home/qi/parse.hpp: In instantiation of 'struct
boost::spirit::qi::phrase_parse(Iterator, Iterator, const Expr, const
Skipper, boost::spirit::qi::skip_flag::enum_type, Attr) [with Iterator =
__gnu_cxx::__normal_iteratorconst char*, std::basic_stringchar ; Expr =
mapnik::css_color_grammar__gnu_cxx::__normal_iteratorconst char*,
std::basic_stringchar ; Skipper =
boost::proto::exprns_::exprboost::proto::tagns_::tag::terminal,
boost::proto::argsns_::termboost::spirit::tag::char_codeboost::spirit::tag::space,
boost::spirit::char_encoding::ascii , 0l; Attr =
mapnik::color]::error_invalid_expression155':
/usr/include/boost/spirit/home/qi/parse.hpp:155:9: required from 'bool
boost::spirit::qi::phrase_parse(Iterator, Iterator, const Expr, const
Skipper, boost::spirit::qi::skip_flag::enum_type, Attr) [with Iterator =
__gnu_cxx::__normal_iteratorconst char*, std::basic_stringchar ; Expr =
mapnik::css_color_grammar__gnu_cxx::__normal_iteratorconst char*,
std::basic_stringchar ; Skipper =
boost::proto::exprns_::exprboost::proto::tagns_::tag::terminal,
boost::proto::argsns_::termboost::spirit::tag::char_codeboost::spirit::tag::space,
boost::spirit::char_encoding::ascii , 0l; Attr = mapnik::color]'
/usr/include/boost/spirit/home/qi/parse.hpp:197:86: required from 'bool
boost::spirit::qi::phrase_parse(Iterator, Iterator, const Expr, const
Skipper, Attr) [with Iterator = __gnu_cxx::__normal_iteratorconst char*,
std::basic_stringchar ; Expr =
mapnik::css_color_grammar__gnu_cxx::__normal_iteratorconst char*,
std::basic_stringchar ; Skipper =
boost::proto::exprns_::exprboost::proto::tagns_::tag::terminal,
boost::proto::argsns_::termboost::spirit::tag::char_codeboost::spirit::tag::space,
boost::spirit::char_encoding::ascii , 0l; Attr = mapnik::color]'
/usr/include/mapnik/color_factory.hpp:60:46: required from here
/usr/include/boost/spirit/home/qi/parse.hpp:155:9: internal compiler error:
Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See file:///usr/share/doc/gcc-4.7/README.Bugs for instructions.
Preprocessed source stored into /tmp/ccgHFpuM.out file, please attach this to
your bugreport.
Waf: Leaving directory `/«PKGBUILDDIR»/build'
Build failed: - task failed (err #1):
{task: cxx mapnik_color.cpp - mapnik_color_1.o}
make[1]: *** [override_dh_auto_build] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/06/09/node-mapnik_0.6.7-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#676033: node-stringprep: FTBFS: (.text+0x20): undefined reference to `main'
Source: node-stringprep Version: 0.1.3-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120604 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: DC-Build-Header: node-stringprep 0.1.3-1 / Mon Jun 04 16:21:43 + 2012 DC-Task: logfile:/tmp/node-stringprep_0.1.3-1_unstable.log version:0.1.3-1 modes: chroot:unstable source:node-stringprep esttime:35 architecture:any DC-Sbuild-call: su user -c 'sbuild -n -A -s --force-orig-source --apt-update -d unstable -v node-stringprep_0.1.3-1' sbuild (Debian sbuild) 0.62.5 (13 Jul 2011) on ip-10-28-121-108.ec2.internal ╔══╗ ║ node-stringprep 0.1.3-1 (amd64)04 Jun 2012 16:21 ║ ╚══╝ Package: node-stringprep Version: 0.1.3-1 Source Version: 0.1.3-1 Distribution: unstable Architecture: amd64 I: NOTICE: Log filtering will replace 'build/node-stringprep-pQLvki/node-stringprep-0.1.3' with '«PKGBUILDDIR»' I: NOTICE: Log filtering will replace 'build/node-stringprep-pQLvki' with '«BUILDDIR»' I: NOTICE: Log filtering will replace 'var/lib/schroot/mount/unstable-amd64-sbuild-4228d8ab-66d0-41cb-90d5-4b707879cd1d' with '«CHROOT»' ┌──┐ │ Update chroot │ └──┘ Ign http://localhost unstable InRelease Get:1 http://localhost unstable Release.gpg [836 B] Get:2 http://localhost unstable Release [233 kB] Get:3 http://localhost unstable/main Sources/DiffIndex [7876 B] Get:4 http://localhost unstable/main amd64 Packages/DiffIndex [7876 B] Get:5 http://localhost unstable/main Translation-en/DiffIndex [7876 B] Get:6 http://localhost unstable/main 2012-06-04-0814.17.pdiff [9615 B] Get:7 http://localhost unstable/main 2012-06-04-0814.17.pdiff [9615 B] Get:8 http://localhost unstable/main amd64 2012-06-04-0814.17.pdiff [14.4 kB] Get:9 http://localhost unstable/main 2012-06-04-0814.17.pdiff [807 B] Get:10 http://localhost unstable/main amd64 2012-06-04-0814.17.pdiff [14.4 kB] Get:11 http://localhost unstable/main 2012-06-04-0814.17.pdiff [807 B] Fetched 282 kB in 4s (62.4 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. ┌──┐ │ Fetch source files │ └──┘ Check APT ─ Checking available source versions... Download source files with APT ── Reading package lists... Building dependency tree... Reading state information... NOTICE: 'node-stringprep' packaging is maintained in the 'Git' version control system at: git://git.debian.org/git/collab-maint/node-stringprep Need to get 9863 B of source archives. Get:1 http://localhost/debian/ unstable/main node-stringprep 0.1.3-1 (dsc) [2043 B] Get:2 http://localhost/debian/ unstable/main node-stringprep 0.1.3-1 (tar) [4097 B] Get:3 http://localhost/debian/ unstable/main node-stringprep 0.1.3-1 (diff) [3723 B] Fetched 9863 B in 0s (50.8 kB/s) Download complete and in download only mode Check arch ── Merged Build-Depends: build-essential, fakeroot Filtered Build-Depends: build-essential, fakeroot dpkg-deb: building package `sbuild-build-depends-core-dummy' in `/«BUILDDIR»/resolver-rdZanf/apt_archive/sbuild-build-depends-core-dummy.deb'. OK Reading package lists... ┌──┐ │ Install core build dependencies (apt-based resolver) │ └──┘ Installing build dependencies Reading package lists... Building dependency tree... Reading state information... The following NEW packages will be installed: sbuild-build-depends-core-dummy debconf: delaying package configuration, since apt-utils is not installed 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/708 B of archives. After this operation, 0 B of additional disk space will be used. Selecting previously unselected package sbuild-build-depends-core-dummy. (Reading database ... 11750 files and directories currently installed.) Unpacking sbuild-build-depends-core-dummy (from .../sbuild-build-depends-core-dummy.deb) ... Setting up sbuild-build-depends-core-dummy (0.invalid.0) ... Merged
[Pkg-javascript-devel] Bug#676117: mustache.js: FTBFS: invalid byte sequence in US-ASCII
Source: mustache.js Version: 0.4.2-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120604 qa-ftbfs User: debian-r...@lists.debian.org Usertags: default19 Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' rake commonjs mkdir -p lib cat wrappers/commonjs/mustache.js.tpl.pre mustache.js wrappers/commonjs/mustache.js.tpl.post lib/mustache.js Packaging for CommonJS rake aborted! invalid byte sequence in US-ASCII Tasks: TOP = commonjs (See full trace by running task with --trace) make[1]: *** [override_dh_auto_build] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/04/mustache.js_0.4.2-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. ___ Pkg-javascript-devel mailing list Pkg-javascript-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#669541: underscore.logger: FTBFS: SyntaxError: In src/underscore.logger.coffee, octal escape sequences \033[#{color}m are not allowed on line 53
Source: underscore.logger
Version: 0.3.0~2014-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120419 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
debian/rules build
test -x debian/rules
mkdir -p .
Scanning upstream source for new/changed copyright notices...
licensecheck -c '.*' -r --copyright -i
'^debian/(changelog|copyright(|_hints|_newhints))' -l '9' * |
/usr/lib/cdbs/licensecheck2dep5 debian/copyright_newhints
3 combinations of copyright and licensing found.
WARNING: The following (and possibly more) new or changed notices discovered:
Format: http://www.debian.org/doc/packaging-manuals/…
License: GPL-2+
HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER …
To fix the situation please do the following:
1) Fully compare debian/copyright_hints with debian/copyright_newhints
2) Update debian/copyright as needed
3) Replace debian/copyright_hints with debian/copyright_newhints
touch debian/stamp-copyright-check
touch debian/stamp-upstream-cruft
coffee -o build src/*.coffee
SyntaxError: In src/underscore.logger.coffee, octal escape sequences
\033[#{color}m are not allowed on line 53
at SyntaxError (unknown source)
at Lexer.error (/usr/lib/coffee-script/lib/coffee-script/lexer.js:686:13)
at Lexer.stringToken
(/usr/lib/coffee-script/lib/coffee-script/lexer.js:174:14)
at Lexer.tokenize
(/usr/lib/coffee-script/lib/coffee-script/lexer.js:35:137)
at Object.compile
(/usr/lib/coffee-script/lib/coffee-script/coffee-script.js:43:32)
at /usr/lib/coffee-script/lib/coffee-script/command.js:182:33
at /usr/lib/coffee-script/lib/coffee-script/command.js:152:18
at [object Object].anonymous (fs.js:115:5)
at [object Object].emit (events.js:64:17)
at afterRead (fs.js:1117:12)
make: *** [build/node-underscore.logger] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/04/19/underscore.logger_0.3.0~2014-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
[Pkg-javascript-devel] Bug#665237: nodejs: FTBFS: tests failed
Source: nodejs Version: 0.6.12~dfsg1-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120321 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' Waf: Entering directory `/«PKGBUILDDIR»/out' Waf: Leaving directory `/«PKGBUILDDIR»/out' 'build' finished successfully (0.041s) DEST_OS: linux DEST_CPU: x64 Parallel Jobs: 1 Product type: program -rwxrwxr-x 1 user user 4.5M Mar 22 02:11 out/Release/node python tools/test.py --mode=release simple message [00:00|% 0|+ 0|- 0]: release test-pipe [00:00|% 0|+ 1|- 0]: release test-memory-usage [00:00|% 0|+ 2|- 0]: release test-net-socket-destroy-twice [00:01|% 0|+ 3|- 0]: release test-net-pingpong [00:02|% 1|+ 4|- 0]: release test-http-keep-alive [00:02|% 1|+ 5|- 0]: release test-http-upgrade-server [00:02|% 1|+ 6|- 0]: release test-global [00:02|% 2|+ 7|- 0]: release test-http-url.parse-basic [00:02|% 2|+ 8|- 0]: release test-http-chunked [00:02|% 2|+ 9|- 0]: release test-http-contentLength0 [00:02|% 2|+ 10|- 0]: release test-child-process-exec-cwd [00:03|% 3|+ 11|- 0]: release test-exception-handler [00:03|% 3|+ 12|- 0]: release test-http-client-upload-buf [00:03|% 3|+ 13|- 0]: release test-path [00:03|% 4|+ 14|- 0]: release test-http-url.parse-search [00:03|% 4|+ 15|- 0]: release test-tcp-wrap [00:03|% 4|+ 16|- 0]: release test-http-head-request [00:03|% 5|+ 17|- 0]: release test-exec-max-buffer [00:03|% 5|+ 18|- 0]: release test-https-eof-for-eom [00:04|% 5|+ 19|- 0]: release test-next-tick-errors [00:04|% 5|+ 20|- 0]: release test-https-foafssl [00:04|% 6|+ 21|- 0]: release test-delayed-require [00:04|% 6|+ 22|- 0]: release test-fs-write-file [00:04|% 6|+ 23|- 0]: release test-net-connect-handle-econnrefused [00:04|% 7|+ 24|- 0]: release test-string-decoder [00:05|% 7|+ 25|- 0]: release test-chdir [00:05|% 7|+ 26|- 0]: release test-http-client-race [00:05|% 7|+ 27|- 0]: release test-tls-request-timeout [00:05|% 8|+ 28|- 0]: release test-debugger-repl [00:06|% 8|+ 29|- 0]: release test-tls-junk-closes-server [00:06|% 8|+ 30|- 0]: release test-fs-stat [00:07|% 9|+ 31|- 0]: release test-http-response-readable [00:07|% 9|+ 32|- 0]: release test-child-process-stdout-flush [00:07|% 9|+ 33|- 0]: release test-fs-mkdir [00:07|% 10|+ 34|- 0]: release test-child-process-cwd [00:07|% 10|+ 35|- 0]: release test-regress-GH-1697 [00:09|% 10|+ 36|- 0]: release test-script-static-this [00:09|% 10|+ 37|- 0]: release test-next-tick-ordering2 [00:09|% 11|+
[Pkg-javascript-devel] Bug#664912: node-sqlite3: FTBFS: ../src/sqlite3.cc:3:25: fatal error: node_events.h: No such file or directory
Source: node-sqlite3
Version: 2.0.17+ds1-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120321 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
make[1]: Entering directory `/«BUILDDIR»/node-sqlite3-2.0.17+ds1'
node-waf build
Waf: Entering directory `/«BUILDDIR»/node-sqlite3-2.0.17+ds1/build'
[1/4] cxx: src/sqlite3.cc - build/Release/src/sqlite3_1.o
../src/sqlite3.cc:3:25: fatal error: node_events.h: No such file or directory
compilation terminated.
Waf: Leaving directory `/«BUILDDIR»/node-sqlite3-2.0.17+ds1/build'
Build failed: - task failed (err #1):
{task: cxx sqlite3.cc - sqlite3_1.o}
make[1]: *** [build] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/03/21/node-sqlite3_2.0.17+ds1-2.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
___
Pkg-javascript-devel mailing list
Pkg-javascript-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-javascript-devel
