Buildout -- Software for automating application assembly

Download error with too little detail

Reported by Christian Theune on 2007-06-10
20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Buildout
Undecided
Unassigned

Bug Description

The reported error message when a download error occurs is not helpful in debugging:

Download error: (11, 'Resource temporarily unavailable') -- Some packages may not be found!

We should show which download failed because something is definitely wrong in my DNS environment but I can't tell what because the URL (hostname) is missing.

Christian Theune (ct-gocept) wrote :

Oh. I noticed that I get this information when running with -v. Eventually we should provide this information also when running without -v.

Could you be more specific?

Could you share complete output so I can see the context. This is
really a setuptools missfeature that was fixed by setuptools 0.6c6
afaik. What version of setuptools are you using. (Look at your
buildout script to find out.)

Jim

On Jun 10, 2007, at 4:10 AM, Christian Theune wrote:

> Public bug reported:
>
> The reported error message when a download error occurs is not helpful
> in debugging:
>
> Download error: (11, 'Resource temporarily unavailable') -- Some
> packages may not be found!
>
> We should show which download failed because something is definitely
> wrong in my DNS environment but I can't tell what because the URL
> (hostname) is missing.
>
> ** Affects: zc.buildout (upstream)
> Importance: Undecided
> Status: Unconfirmed
>
> --
> Download error with too little detail
> https://bugs.launchpad.net/bugs/119661
> You received this bug notification because you are the bug contact for
> Buildout.

--
Jim Fulton mailto:<email address hidden> Python Powered!
CTO (540) 361-1714 http://www.python.org
Zope Corporation http://www.zope.com http://www.zope.org

Marius Gedminas (mgedmin) wrote :

Here's some sample output:

$ python bootstrap.py
Downloading http://pypi.python.org/packages/2.5/s/setuptools/setuptools-0.6c9-py2.5.egg
Generated script '/home/user/src/myapp/bin/buildout'.

$ bin/buildout
Upgraded:
  zc.buildout version 1.1.0;
restarting.
Generated script '/home/user/src/myapp/bin/buildout'.
Develop: '/home/user/src/myapp/src/'
Updating test.
Download error: (104, 'Connection reset by peer') -- Some packages may not be found!

The download error is entirely uninformative by default.

Adam Groszer (agroszer) wrote :

Even worse when it chokes on bootstrap:

adi@xubVM:~/blah$ python2.4 bootstrap.py
While:
  Initializing.

An internal error occured due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
  File "/tmp/tmpI0XdJV/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 1476, in main
    user_defaults, windows_restart, command)
  File "/tmp/tmpI0XdJV/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 113, in __init__
    _update(data, _open(os.path.dirname(config_file), config_file, []))
  File "/tmp/tmpI0XdJV/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 1171, in _open
    result = _update(_open(base, fname, seen), result)
  File "/tmp/tmpI0XdJV/zc.buildout-1.1.1-py2.4.egg/zc/buildout/buildout.py", line 1134, in _open
    fp = urllib2.urlopen(filename)
  File "/usr/lib/python2.4/urllib2.py", line 130, in urlopen
    return _opener.open(url, data)
  File "/usr/lib/python2.4/urllib2.py", line 364, in open
    response = meth(req, response)
  File "/usr/lib/python2.4/urllib2.py", line 471, in http_response
    response = self.parent.error(
  File "/usr/lib/python2.4/urllib2.py", line 402, in error
    return self._call_chain(*args)
  File "/usr/lib/python2.4/urllib2.py", line 337, in _call_chain
    result = func(*args)
  File "/usr/lib/python2.4/urllib2.py", line 480, in http_error_default
    raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
HTTPError: HTTP Error 404: Not Found

The thing is that ``extends`` in the buildout.cfg pointed to an invalid URL.

This bug is similar to #566167 and it was fixed in the trunk. Also note that python2.4 is not supported.

Changed in zc.buildout:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers