#35 — zopeskel plone3_buildout --svn-repository fails
by
Roel Bruggink
—
last modified
Jun 14, 2010 05:55 PM
| State | Resolved |
|---|---|
| Version: |
—
|
| Area | General |
| Issue type | Upstream |
| Severity | Low |
| Submitted by | Roel Bruggink |
| Submitted on | Mar 12, 2010 |
| Responsible | Cris Ewing |
| Target release: | 2.16 |
I'm using trunk after #24.
./bin/zopeskel plone3_buildout --svn-repository=https://support.fourdigits.nl/[…]/
Traceback (most recent call last):
File "./bin/zopeskel", line 16, in ?
zopeskel.zopeskel_script.run()
File "/Users/roel/workspace/zopeskel/src/ZopeSkel/zopeskel/zopeskel_script.py", line 347, in run
command.run( [ '-q', '-t', template_name ] + optslist )
File "/Users/roel/.buildout/eggs/PasteScript-1.7.3-py2.4.egg/paste/script/command.py", line 218, in run
result = self.command()
File "/Users/roel/.buildout/eggs/PasteScript-1.7.3-py2.4.egg/paste/script/create_distro.py", line 185, in command
self.add_svn_repository(vars, output_dir)
File "/Users/roel/.buildout/eggs/PasteScript-1.7.3-py2.4.egg/paste/script/create_distro.py", line 238, in add_svn_repository
egg_info_dir = pluginlib.egg_info_dir(output_dir, vars['project'])
File "/Users/roel/.buildout/eggs/PasteScript-1.7.3-py2.4.egg/paste/script/pluginlib.py", line 133, in egg_info_dir
raise IOError("No egg-info directory found (looked in %s)"
IOError: No egg-info directory found (looked in ./test.plone3_buildout/./test.plone3_buildout.egg-info, ./test.plone3_buildout/.svn/test.plone3_buildout.egg-info, ./test.plone3_buildout/bootstrap.py/test.plone3_buildout.egg-info, ./test.plone3_buildout/buildout.cfg/test.plone3_buildout.egg-info, ./test.plone3_buildout/products/test.plone3_buildout.egg-info, ./test.plone3_buildout/README.txt/test.plone3_buildout.egg-info, ./test.plone3_buildout/src/test.plone3_buildout.egg-info, ./test.plone3_buildout/var/test.plone3_buildout.egg-info)
./bin/zopeskel plone3_buildout --svn-repository=https://support.fourdigits.nl/[…]/
Traceback (most recent call last):
File "./bin/zopeskel", line 16, in ?
zopeskel.zopeskel_script.run()
File "/Users/roel/workspace/zopeskel/src/ZopeSkel/zopeskel/zopeskel_script.py", line 347, in run
command.run( [ '-q', '-t', template_name ] + optslist )
File "/Users/roel/.buildout/eggs/PasteScript-1.7.3-py2.4.egg/paste/script/command.py", line 218, in run
result = self.command()
File "/Users/roel/.buildout/eggs/PasteScript-1.7.3-py2.4.egg/paste/script/create_distro.py", line 185, in command
self.add_svn_repository(vars, output_dir)
File "/Users/roel/.buildout/eggs/PasteScript-1.7.3-py2.4.egg/paste/script/create_distro.py", line 238, in add_svn_repository
egg_info_dir = pluginlib.egg_info_dir(output_dir, vars['project'])
File "/Users/roel/.buildout/eggs/PasteScript-1.7.3-py2.4.egg/paste/script/pluginlib.py", line 133, in egg_info_dir
raise IOError("No egg-info directory found (looked in %s)"
IOError: No egg-info directory found (looked in ./test.plone3_buildout/./test.plone3_buildout.egg-info, ./test.plone3_buildout/.svn/test.plone3_buildout.egg-info, ./test.plone3_buildout/bootstrap.py/test.plone3_buildout.egg-info, ./test.plone3_buildout/buildout.cfg/test.plone3_buildout.egg-info, ./test.plone3_buildout/products/test.plone3_buildout.egg-info, ./test.plone3_buildout/README.txt/test.plone3_buildout.egg-info, ./test.plone3_buildout/src/test.plone3_buildout.egg-info, ./test.plone3_buildout/var/test.plone3_buildout.egg-info)
Added by
Roel Bruggink
on
Mar 12, 2010 06:58 PM
Buildout used:[buildout]
parts = zopeskel
sources = sources
extensions = mr.developer
auto-checkout = ZopeSkel
[zopeskel]
recipe = zc.recipe.egg:scripts
eggs = PasteDeploy
PasteScript
ZopeSkel
scripts = zopeskel
paster
[sources]
ZopeSkel = svn https://svn.plone.org/svn/collective/ZopeSkel/trunk/
Added by
Cris Ewing
on
Mar 15, 2010 08:42 PM
I see the same thing, but I'm wondering what should be done about this. I mean, we don't really want to be creating .egg-info directories for buildouts, do we? They aren't eggs as such. Perhaps this is a problem of over-specificity in the pastescript bit that is expecting an egg-info directory to be found in a buildout?
Issue state:
Unconfirmed
→
Confirmed
Severity:
Medium
→
Low
Added by
Cris Ewing
on
Mar 19, 2010 05:35 PM
according to claytron: 'It is definitely paster assuming that the template will be an egg and not a buildout when checking the code in.' This jibes with what I've seen. Claytron also suggests: 'In my custom code, I just set the svn:ignore property for stuff like that in the "post" method.' I'm going to do that for this particular case and see if it helps.
Issue state:
Confirmed
→
In progress
Responsible manager:
(UNASSIGNED)
→
cewing
Added by
Cris Ewing
on
Mar 19, 2010 05:43 PM
Crud.
Issue state:
In progress
→
Postponed
Responsible manager:
cewing
→
(UNASSIGNED)
Never mind. This particular problem cannot be solved in ZopeSkel. The issue is quite clearly in Paster, which assumes that everything it builds is an egg and will have an egg-info directory. Even setting svn-ignore will not solve this problem and so the only choice I think we have is to swallow the --svn-repository variable in all buildout templates.
Added by
Cris Ewing
on
Mar 19, 2010 05:45 PM
Issue state:
Postponed
→
Confirmed
Added by
Roel Bruggink
on
Mar 19, 2010 07:35 PM
Not supporting --svn-repository seems like a sensible solution to me. A workaround is to run ZopeSkel on a working copy.example:
cd src
svn co <repos> my.package
ZopeSkel create -t <type> my.package
Added by
Cris Ewing
on
Jun 14, 2010 05:55 PM
fixed in v2.16 by removing the possibility from users of the bin/zopeskel command. paster/create will still accept this argument, and it will still be problematic for buildout templates, as they shouldn't have egg-info, but I can't do anything about that without altering pastescript.
Issue state:
Confirmed
→
Resolved
Responsible manager:
(UNASSIGNED)
→
cewing
Target release:
None
→
2.16
No responses can be added.
If you can, please log in before submitting a reaction.
