Several branches needing review and merging fine get an "ApplyFailed" ticket bypatchbot runners (many thanks for the service BTW). This is due towhere there are workarounds. So please if you run a patchbot check your logs
It would be prudent to improve the instructions to no longer recommend installationof patchbot-2.1.spkg but a newer spkg if it exists (it still doesn't).
--
You received this message because you are subscribed to a topic in the Google Groups "sage-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-devel/GHMpjpAjmwA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-devel+...@googlegroups.com.
To post to this group, send email to sage-...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
Well if every release was tagged one could simply
point sage -I to the URL of the tarball that is automagically
created by github.
--
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 is hosted on github.
http://trac.sagemath.org/ticket/16259
Regards,
You received this message because you are subscribed to a topic in the Google Groups "sage-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-devel/GHMpjpAjmwA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-devel+...@googlegroups.com.