On Aug 12, 2009, at 9:55 AM, Gary Poster wrote:
On Aug 12, 2009, at 6:10 AM, Graham Binns wrote:
2009/8/12 Gavin Panella <[email protected]>:
Running `make` in a fresh devel branch (with linked sourcecode)
does not
seem to be working:
ImportError: No module named buildout.buildout
Running `./bin/buildout` before `make` fixes this for me.
Can anyone else confirm this? It's important because rocketfuel-get
cannot complete cleanly because of this.
Yes. I saw the same issue and fixed it the same way.
I didn't see this when I just tried it--rocketfuel-get and
rocketfuel-branch were successful. Should I try something else?
That said, one way I know to recreate this symptom is to clear out
the egg directory the script expects to find. (bin/buildout will
repopulate it from the download-cache, which is why it fixes things.)
Barry and Curtis also reported this problem. We started diagnosing
it, but didn't discover any obvious sources of the problem for them.
They both then used the bin/buildout trick in a single branch, which
fixed the problem for all branches on the machine. I don't know why.
Because it is now fixed for them, I can't use their machines for
further diagnosis. If anyone wants to help me diagnose further,
please get in touch with me on IRC.
Meanwhile, if you encounter this and want to get on with your lives,
looks like running bin/buildout is the way to go.
Gary
_______________________________________________
Mailing list: https://launchpad.net/~launchpad-dev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~launchpad-dev
More help : https://help.launchpad.net/ListHelp
