Comment 5 for bug 559128

Revision history for this message
Gary Poster (gary) wrote :

OK, that clarifies the issue. The reason devs don't see this is because we don't build on one path and deploy on another. The heart of the problem is that the original build on the deployment machine has this line

site_dir = "/home/pqm/for_rollouts/edge/parts/scripts"

and the build on the front end (make clean && make build) has this line:

site_dir = "/srv/edge.launchpad.net/edge/launchpad-rev-10662/parts/scripts"

I'd like to transfer this discussion to a faster medium like IRC or phone, but the thoughts on my mind are these:

- Do you already rsync /home/pqm/for_rollouts/edge/lib and /home/pqm/for_rollouts/edge/eggs, or symlink them somehow on the ?
- Can we build on the deployment box using the same path that will be used on the frontend box?
- Buildout has an option to use relative paths which would solve this, I think. Right now, we can't use it because of some technical reasons. I can fix that, and I think it would solve the problem. I suspect that's your winning option, if I can get it to work :-)
- Other solutions are possible but the ones I can think of would involve significantly more effort, so they are not compelling.

I'll ask on IRC if we can get on the phone to nail this down. I want to make sure I understand the current process before I proceed.