Buildout reporting 'Temporary failure in name resolution' - any clue why?
Hi, Since some time when doing a "bin/buildout" I experience the following errors: Download error: (-3, 'Temporary failure in name resolution') -- Some packages may not be found! The problem is probably obvious - some URL may be wrong or the like, but I can't find out which one. The output looks like this (snippet): Installing 'bsp', 'zbsp', 'sdecstr', 'sa_tools', 'pybktools', 'ibanlib', 'sqlalchemy==0.5.6', 'pysqlite'. We have a develop egg: BSP 0.0.1 We have a develop egg: zbsp 0.1dev We have a develop egg: sdecstr 0.0.1 We have a develop egg: sa-tools 0.0.1 We have a develop egg: pybktools 0.0.1 We have a develop egg: ibanlib 0.0.1 We have the distribution that satisfies 'sqlalchemy==0.5.6'. Download error: (-3, 'Temporary failure in name resolution') -- Some packages may not be found! --- and 21 times the same error again --- Getting distribution for 'pysqlite'. File "build/bdist.linux-i686/egg/pysqlite2/test/py25tests.py", line 48 with self.con: ^ SyntaxError: invalid syntax zip_safe flag not set; analyzing archive contents... Got pysqlite 2.5.6. Download error: unknown url type: svn -- Some packages may not be found! Download error: unknown url type: svn -- Some packages may not be found! Getting distribution for 'lovely.remotetask'. Got lovely.remotetask 0.5. The problem seems to be somewhere in between SQLAlchemy and pysqlite (both install, however). It seems it works anyway. But these errors consume quite some time (around 10 minutes), any idea what to do? Best Regards, Hermann -- hermann@qwer.tk GPG key ID: 299893C7 (on keyservers) FP: 0124 2584 8809 EF2A DBF9 4902 64B4 D16B 2998 93C7
On Sat, Feb 20, 2010 at 4:33 PM, Hermann Himmelbauer <dusty@qwer.tk> wrote:
The problem seems to be somewhere in between SQLAlchemy and pysqlite (both install, however).
It seems it works anyway. But these errors consume quite some time (around 10 minutes), any idea what to do?
The problem is caused by pysqlite. If you look at it's PyPi page as seen by buildout / setuptools [1] you'll notice a number of links, all of which will be checked and accessed by buildout / setuptools. Among those are for example: http://pysqlite.org/ http://initd.org/pub/software/pysqlite/releases/2.3/2.3.3/ http://oss.itsystementwicklung.de/download/pysqlite/2.4/2.4.1/ The first one of these produces the NameError, as the domain isn't registered anymore. The later two resolve, but point to pages stating "This domain is for sale". The easiest way would be for the maintainer of pysqlite to remove these entries, by editing the old release metadata on PyPi. In your own buildout you can probably only work around this by using your own index and disallowing access to PyPi. I tried once to put in a find-links to the actual version I wanted and a version pin, but this still doesn't stop buildout to check all those links. Maybe you could also get this to work with a dedicated zc.recipe.egg part for pysqlite and an index restriction for just that part. Hanno [1] http://pypi.python.org/simple/pysqlite/
On Sat, Feb 20, 2010 at 04:46:18PM +0100, Hanno Schlichting wrote:
On Sat, Feb 20, 2010 at 4:33 PM, Hermann Himmelbauer <dusty@qwer.tk> wrote:
The problem seems to be somewhere in between SQLAlchemy and pysqlite (both install, however).
It seems it works anyway. But these errors consume quite some time (around 10 minutes), any idea what to do?
The problem is caused by pysqlite. If you look at it's PyPi page as seen by buildout / setuptools [1] you'll notice a number of links, all of which will be checked and accessed by buildout / setuptools.
Among those are for example:
http://pysqlite.org/ http://initd.org/pub/software/pysqlite/releases/2.3/2.3.3/ http://oss.itsystementwicklung.de/download/pysqlite/2.4/2.4.1/
The first one of these produces the NameError, as the domain isn't registered anymore. The later two resolve, but point to pages stating "This domain is for sale".
The easiest way would be for the maintainer of pysqlite to remove these entries, by editing the old release metadata on PyPi. In your own buildout you can probably only work around this by using your own index and disallowing access to PyPi. I tried once to put in a find-links to the actual version I wanted and a version pin, but this still doesn't stop buildout to check all those links. Maybe you could also get this to work with a dedicated zc.recipe.egg part for pysqlite and an index restriction for just that part.
Alternatively, if you have Python 2.5 or newer, you can switch to the sqlite3 module in the standard library and stop depending on pysqlite. Marius Gedminas -- http://pov.lt/ -- Zope 3 consulting and development
participants (3)
-
Hanno Schlichting -
Hermann Himmelbauer -
Marius Gedminas