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?
> 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? Laszlo/GCS -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
