sage -i
http://sage.math.washington.edu/home/robertwb/patches/patchbot-2.1.1.spkg
I've updated the instructions as well. I'm not sure what the best way
is to mix sage spkgs and a live repository--that has always been a
pain... Any ideas? (I suppose the spkg could go a git pull, but then
the
If your git project would be named 'patchbot' instead of 'sage-patchbot'
then every time you do a 'git tag' in your project a tarball with the right
directory structure (I believe) is created on github. See project page /
releases. This can then be installed via sage -I http...
Or any SPKG that
I just started trying to run patchbot yesterday. Even with the new spkg,
I'm having trouble with either build failures or apply failures. At least
one of these was caused by forgetting to do 'make distclean make' when
switching from master to develop or vice versa.
I had one successful
Oh, nice. I'll play with that.
On Tue, Apr 29, 2014 at 3:38 AM, Ralf Stephan gtrw...@gmail.com wrote:
If your git project would be named 'patchbot' instead of 'sage-patchbot'
then every time you do a 'git tag' in your project a tarball with the right
directory structure (I believe) is created
The error looks like a legitimate build failure:
Setting up build directory for matplotlib-1.3.1
Finished set up
...
Traceback (most recent call last):
File setup.py, line 10, in module
use_setuptools()
File
Yo !!!
Several branches needing review and merging fine get an ApplyFailed
ticket by
patchbot runners (many thanks for the service BTW). This is due to
https://github.com/robertwb/sage-patchbot/issues/10
where there are workarounds. So please if you run a patchbot check
Okay, I just installed a more recent version of the patchbot as it seems
that sage -i patchbot installs an old one, and here is the new result :
patchbot@silence:~/sage$ ./sage -patchbot
Getting trusted author list...
WARNING: Assuming sage-main is pristine.
WARNING: Do not use this copy of
Whats the recommended way for running the git version of the patchbot? Just
installing it manually? Maybe there is a better way?
On Monday, April 28, 2014 7:17:08 AM UTC+1, Ralf Stephan wrote:
Several branches needing review and merging fine get an ApplyFailed
ticket by
patchbot runners
Well if every release was tagged one could simply
point sage -I to the URL of the tarball that is automagically
created by github.
On 28 Apr 2014 12:11, Volker Braun vbraun.n...@gmail.com wrote:
Whats the recommended way for running the git version of the patchbot?
Just installing it manually?
