crontab code is generating wrong path to the launcher again..
Since the latest rework and version we're getting /home/poms/current/poms/current/cron/launcher
instead of $HOME/current/poms/cron/launcher -- the code in there to add a current link path is borked now that $POMS_DIR has the /current in it already...
#2 Updated by Marc Mengel over 2 years ago
- Status changed from New to Resolved
So the bug was in the code that tried to replace .../vx_y/poms in $POMS_DIR with .../current/poms. I changed it so it only tries to change it if:
1) there isn't already a "current" in the POMS_DIR
2) the directory it tries to rewrite it to actually exists.
so in our current virtualenv installs, it won't mess things up.