Corrupt eggs in mailman-3.0.0a6.tar.gz
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNU Mailman |
Fix Released
|
Critical
|
Barry Warsaw |
Bug Description
Following up on this thread:
http://
I can reproduce the problem:
[cp ~/local/
Traceback (most recent call last):
File "./bin/buildout", line 17, in <module>
import zc.buildout.
ImportError: No module named zc.buildout.
The eggs/zc-buildout* directory is missing the *.py files. Similarly, the z3c.recipe.
In the end, I removed the eggs/ directory completely, and got much further down the road. (I am new to eggs, so I am not sure this is the best idea.)
Now, installation seems to fail at the logilab-common step.
Develop: '/home/
Page at http://
Uninstalling filetemplates.
Updating docs.
Generated script '/home/
Installing filetemplates.
Updating interpreter.
Installing pylint.
Getting distribution for 'logilab-
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/home/
with_
File "/home/
return f()
File "/home/
distclass=
File "/usr/lib/
dist.
File "/usr/lib/
self.
File "/usr/lib/
cmd_obj.run()
File "/home/
self.
File "/home/
return self.install_
File "/home/
dists = self.install_
File "/home/
unpack_
File "/home/
driver(
File "/home/
while member.islnk() or member.issym():
AttributeError: 'NoneType' object has no attribute 'islnk'
An error occurred when trying to install logilab-common 0.52.0. Look above this message for any errors that were output by easy_install.
While:
Installing pylint.
Getting distribution for 'logilab-
Error: Couldn't install: logilab-common 0.52.0
Let me know what else I can send you in regards to my environment. I am running a fairly fresh Ubuntu-10.04.1 with Python 2.6.
Related branches
- pierfort123: Pending requested
tags: | added: mailman3 |
Changed in mailman: | |
status: | Fix Committed → Fix Released |
The first problem (no module named zc.buildout. buildout) is due to a faulty MANIFEST.in that let the eggs/ and parts/ directories leak into the tarball. I've fixed this for alpha7 but you were exactly right that the workaround is just to delete those two directories and start over.
I can reproduce the AttributeError locally. I suspect this is a bug in setuptools- 0.6c12dev. I'll see if pinning the version for that fixes the problem and make sure that it's reported upstream. I'll follow up when any workaround I find.