Your message dated Sun, 8 Mar 2015 13:47:58 +0100
with message-id <20150308124758.ge19...@werner.olasd.eu>
and subject line Re: Bug#779662: package fails to build without network 
connection
has caused the Debian Bug report #779662,
regarding package fails to build without network connection
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.)


-- 
779662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:fedmsg-meta-fedora-infrastructure
Version: 0.2.18-1
Severity: serious
Tags: sid jessie

The package fails to build in an unstable environment on amd64 without having
network access. the build log shows errors like these, which go away if you have
network connection.

======================================================================
FAIL: test_secondary_icon 
(fedmsg_meta_fedora_infrastructure.tests.TestGithubDelete)
Does fedmsg.meta produce the expected secondary icon?
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/fedmsg/tests/test_meta.py", line 44, in
inner
    return func(self)
  File "/usr/lib/python2.7/dist-packages/fedmsg/tests/test_meta.py", line 100,
in test_secondary_icon
    eq_(actual_icon, self.expected_secondary_icon)
AssertionError: None !=
'https://seccdn.libravatar.org/avatar/9c9f7784935381befc302fe3c814f9136e7a33953d0318761669b8643f4df55c?s=64&d=retro'

======================================================================
FAIL: test_icon (fedmsg_meta_fedora_infrastructure.tests.TestGithubFork)
Does fedmsg.meta produce the expected icon?
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/fedmsg/tests/test_meta.py", line 44, in
inner
    return func(self)
  File "/usr/lib/python2.7/dist-packages/fedmsg/tests/test_meta.py", line 94, in
test_icon
    eq_(actual_icon, self.expected_icon)
AssertionError: 'https://apps.fedoraproject.org/img/icons/git-logo.png' !=
'https://apps.fedoraproject.org/img/icons/github.png'

======================================================================
FAIL: test_link (fedmsg_meta_fedora_infrastructure.tests.TestGithubFork)
Does fedmsg.meta produce the expected link?
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/fedmsg/tests/test_meta.py", line 44, in
inner
    return func(self)
  File "/usr/lib/python2.7/dist-packages/fedmsg/tests/test_meta.py", line 88, in
test_link
    eq_(actual_link, self.expected_link)
AssertionError: None != 'https://github.com/kushal124/github2fedmsg'

--- End Message ---
--- Begin Message ---
Version: 0.2.18-1

* Nicolas Dandrimont <ol...@debian.org> [2015-03-08 12:42:20 +0100]:

> Control: tags -1 + unreproducible
> 
> * Matthias Klose <d...@debian.org> [2015-03-03 20:26:38 +0100]:
> 
> > Package: src:fedmsg-meta-fedora-infrastructure
> > Version: 0.2.18-1
> > Severity: serious
> > Tags: sid jessie
> > 
> > The package fails to build in an unstable environment on amd64 without 
> > having
> > network access. the build log shows errors like these, which go away if you 
> > have
> > network connection.
> 
> Hi,
> 
> I couldn't reproduce this on my laptop disconnected from the internet. Please
> be more specific as to what you mean by "no network access".
> 
> I'm pretty sure those tests need access to localhost, and I'm not sure "no
> localhost" is a supported configuration for our build environment.

It has been pointed out to me that pbuilder restricts access to the network
during build by default. I retried the build with pbuilder, and it succeeded.

Since version 0.215+nmu3, pbuilder establishes a new loopback interface after
creating a new network namespace to isolate the chroot.

I'll therefore close this bug as invalid.

Thanks,
-- 
Nicolas Dandrimont

"All language designers are arrogant.  Goes with the territory..."
(By Larry Wall)

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to