Your message dated Tue, 06 Aug 2013 19:42:45 +0200 with message-id <52013595.4020...@debian.org> and subject line Re: more info needed on node-oauth FTBFS has caused the Debian Bug report #712301, regarding FTBFS: tests require internet connectivity to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 712301: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=712301 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: node-oauth Version: 0.9.8-1 Severity: serious Justification: fails to build from source This package requires internet connectivity for its test suite to pass. Package builds must not not rely on external network connectivity, but should be self-contained. Build log: [...] When performing a secure Request With a Callback And A 302 redirect is received and there is a location header ✓ it should (re)perform the secure request but with the new location When performing a secure Request With a Callback And A 302 redirect is received but there is no location header ✓ it should execute the callback, passing the HTTP Response code ♢ OAuth2 events.js:48 throw arguments[1]; // Unhandled 'error' event ^ Error: getaddrinfo EADDRINFO at errnoException (dns.js:31:11) at Object.onanswer [as oncomplete] (dns.js:140:16) make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory `/tmp/buildd/node-oauth-0.9.8' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2
--- End Message ---
--- Begin Message ---Hi, On 27.07.2013 15:26, Laszlo Boszormenyi (GCS) wrote: > Hi Felix, > > On Sat, 2013-07-27 at 11:29 +0200, Felix Geyer wrote: >> On 27.07.2013 10:38, Laszlo Boszormenyi (GCS) wrote: >>> I build my packages in a clear pbuilder chroot before uploading. As I >>> know, it doesn't have any internet connection. Now I've tried to rebuild >>> node-oauth with an unplugged ethernet cable. It still builds. >>> On the other hand, your bugreport states the exception occurs in >>> events.js which was called from dns.js . Neither one is present in my >>> pbuilder chroot and package builds fine. >> >> Maybe you still had the relevant entries in a local DNS cache? >> test/internet/test-dns.js definitely checks all sorts of internet >> hostnames like www.google.com, gmail.com, rackspace.com .... >> dns.js and events.js are built into nodejs (see lib/dns.js in the nodejs >> source package). > I don't have any DNS cache installed, especially not in the chroot. But > tested this case with 'host google.com; sleep 1; host google.com', > immediately pull out the ethernet cable after the first DNS resolution > succeed. It says ";; connection timed out; no servers could be reached" > as expected. This way when node-oauth builds here without internet > connection nor DNS resolution makes me wonder. What can be the problem > there? Sorry, those hostnames are queried in the nodejs testsuite, not node-oauth. Anyway, I just retried the build and it works fine now. nodejs has been updated in the meantime, maybe that somehow fixed it. >> It's minimal pbuilder chroot, see the attached full build log. > Do you have that pbuilder chroot somewhere? Is it up-to-date? Can you > re-run your test? The chroot isn't special in any way but I create a new network namespace so the build system can only talk to my local apt-cacher-ng instance. Cheers, Felix
--- End Message ---
