This issue is restricted to cases where patchbot was started with sage -patchbot. Just use python local/bin/patchbot/patchbot.py.
patchbot when started with sage -patchbot will clobber your Sage installation.
patchbot discriminates between safe and unsafe tickets (the former basically change
only files in src/). Unsafe tickets are supposed to be tested using installation of Sage in /tmp but that installation process not only reads from the base Sage directory (and so may not test changes done in /tmp) but, more importantly, installs many files and packages not into /tmp but back into original Sage.
Previous description was:
This issue is restricted to cases where patchbot was started with
sage -patchbot
. Just usepython local/bin/patchbot/patchbot.py
.patchbot when started with
sage -patchbot
will clobber your Sage installation. patchbot discriminates between safe and unsafe tickets (the former basically change only files insrc/
). Unsafe tickets are supposed to be tested using installation of Sage in/tmp
but that installation process not only reads from the base Sage directory (and so may not test changes done in /tmp) but, more importantly, installs many files and packages not into/tmp
but back into original Sage.This issue can be closed when the advice on http://patchbot.sagemath.org/ to use that command is removed.