Your message dated Wed, 18 Jul 2012 09:47:10 +0000
with message-id <e1srqqc-0005ub...@franck.debian.org>
and subject line Bug#681379: fixed in django-celery 2.5.5-2
has caused the Debian Bug report #681379,
regarding django-celery: FTBFS: building documentation fails
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.)


-- 
681379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681379
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: django-celery
Version: 2.5.5-1
Severity: serious
Justification: fails to build from source

django-celery FTBFS:
| PYTHONPATH=. sphinx-build -b html -d .build/.doctrees -N docs .build/html
| Making output directory...
| Running Sphinx v1.1.3
| loading pickled environment... not yet created
| building [html]: targets for 22 source files that are out of date
| updating environment: 22 added, 0 changed, 0 removed
| reading sources... [  4%] changelog
|
| Exception occurred:
|   File "/usr/lib/pymodules/python2.7/sphinx/application.py", line 318, in 
emit_firstresult
|     for result in self.emit(event, *args):
|   File "/usr/lib/pymodules/python2.7/sphinx/application.py", line 314, in emit
|     results.append(callback(self, *args))
|   File "/usr/lib/pymodules/python2.7/sphinxcontrib/issuetracker.py", line 
138, in lookup_github_issue
|     output_format='json')
|   File "/usr/lib/pymodules/python2.7/sphinxcontrib/issuetracker.py", line 
108, in fetch_issue
|     with closing(urlopen(url)) as response:
|   File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
|     return _opener.open(url, data, timeout)
|   File "/usr/lib/python2.7/urllib2.py", line 401, in open
|     response = self._open(req, data)
|   File "/usr/lib/python2.7/urllib2.py", line 419, in _open
|     '_open', req)
|   File "/usr/lib/python2.7/urllib2.py", line 379, in _call_chain
|     result = func(*args)
|   File "/usr/lib/python2.7/urllib2.py", line 1219, in https_open
|     return self.do_open(httplib.HTTPSConnection, req)
|   File "/usr/lib/python2.7/urllib2.py", line 1181, in do_open
|     raise URLError(err)
| URLError: <urlopen error [Errno -2] Name or service not known>
| The full traceback has been saved in /tmp/sphinx-err-NXi4bQ.log, if you want 
to report the issue to the developers.
| Please also report this if it was a user error, so that a better error 
message can be provided next time.
| Either send bugs to the mailing list at 
<http://groups.google.com/group/sphinx-dev/>,
| or report them in the tracker at 
<http://bitbucket.org/birkenfeld/sphinx/issues/>. Thanks!
| make[1]: *** [override_dh_auto_build] Error 1
| make[1]: Leaving directory `/build/django-celery-Z6ODUX/django-celery-2.5.5'
| make: *** [build] Error 2

Internet access was not available during the build.

--
Jakub Wilk



--- End Message ---
--- Begin Message ---
Source: django-celery
Source-Version: 2.5.5-2

We believe that the bug you reported is fixed in the latest version of
django-celery, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 681...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Fladischer <fladischermich...@fladi.at> (supplier of updated 
django-celery package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Wed, 18 Jul 2012 10:14:52 +0200
Source: django-celery
Binary: python-django-celery python-django-celery-doc
Architecture: source all
Version: 2.5.5-2
Distribution: unstable
Urgency: low
Maintainer: Debian Python Modules Team 
<python-modules-t...@lists.alioth.debian.org>
Changed-By: Michael Fladischer <fladischermich...@fladi.at>
Description: 
 python-django-celery - Celery integration for Django
 python-django-celery-doc - Celery integration for Django (Documentation)
Closes: 681379
Changes: 
 django-celery (2.5.5-2) unstable; urgency=low
 .
   * Do not build issues by default, they need a network connection. Thanks to
     Evgeni Golov for the patch! (Closes: #681379)
Checksums-Sha1: 
 01414ac7cf8f1a251040181c0b4424673f82381a 1727 django-celery_2.5.5-2.dsc
 890c6685a9a3e8d387c2a94c6f3b24f164b410ed 6790 
django-celery_2.5.5-2.debian.tar.gz
 ffaaaed452053a01ba1404ea48e990fb3f98b17f 52738 
python-django-celery_2.5.5-2_all.deb
 28987301e4e3f9f4ee0c840242d721e0d35526ab 72360 
python-django-celery-doc_2.5.5-2_all.deb
Checksums-Sha256: 
 68262491f2a65a83b793a6b8e70b43b5cbfbd6678dd265e028088058913c51fc 1727 
django-celery_2.5.5-2.dsc
 5c55c5fbb0c703af8b16a4906b010e37b2c123949a67c8c3834b5f26574d2da5 6790 
django-celery_2.5.5-2.debian.tar.gz
 a38453113d309edc0ad89aee852a9be98fc83417103bb9f55ddf4ddc18c2ad5c 52738 
python-django-celery_2.5.5-2_all.deb
 5365402b7fb84ad2be66d759112297ac9cabdcc6d26c162cd202d210dd59de1b 72360 
python-django-celery-doc_2.5.5-2_all.deb
Files: 
 fd1c1e0ddb5b77a0417014e2f0bef1ee 1727 python optional django-celery_2.5.5-2.dsc
 3fc11e6c88fb962be212c9abb705256a 6790 python optional 
django-celery_2.5.5-2.debian.tar.gz
 edd084ff6a7261fe941529c59a91d2c3 52738 python optional 
python-django-celery_2.5.5-2_all.deb
 e44cb01ca35db0c4fc97473b7b0aba63 72360 doc optional 
python-django-celery-doc_2.5.5-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEYEARECAAYFAlAGhMAACgkQVty5d8XpUzOgEACeJbMahYOJrEaHxi5jZLqZeor8
mycAn2840bySygZfcSJEcoO5jSEdy7gA
=S2yr
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to