[sage-devel] Re: Enabling Merge Requests from GitLab

2018-08-23 Thread Dima Pasechnik
Simon, a very quick correspondence between trac and github/lab terms is as follows: trac ticket, no git branch - issue trac ticket, with a git branch - pull (merge, on gitlab) request github has a command line tool, called hub, allowing one to e.g. create pull requests and issues, without usi

Re: [sage-devel] Re: Enabling Merge Requests from GitLab

2018-08-23 Thread Daniel Krenn
On 08/23/2018 11:15 AM, Dima Pasechnik wrote: > github has a command line tool, called hub, allowing one to e.g. create pull > requests and issues, without using a browser. > https://hub.github.com/hub-pull-request.1.html > https://hub.github.com/hub-issue.1.html > > I don't know whether gitlab h

Re: [sage-devel] Workflows on GitLab

2018-08-23 Thread Erik Bray
On Thu, Aug 23, 2018 at 6:13 AM Julian Rüth wrote: > > Hello Jeroen, > > I agree that fragmentation can be a problem. Then again, I think that > sometimes splitting discussion on the issue and the discussion on an actual > attempt to solve that issue can be useful; at least it doesn't feel unnat

Re: [sage-devel] Workflows on GitLab

2018-08-23 Thread Erik Bray
On Thu, Aug 23, 2018 at 8:51 AM Dima Pasechnik wrote: > > > > On Thursday, August 23, 2018 at 7:13:32 AM UTC+3, Julian Rüth wrote: >> >> Hello Jeroen, >> >> I agree that fragmentation can be a problem. Then again, I think that >> sometimes splitting discussion on the issue and the discussion on a

Re: [sage-devel] Re: Enabling Merge Requests from GitLab

2018-08-23 Thread Erik Bray
On Wed, Aug 22, 2018 at 10:25 PM Simon King wrote: > > Hi Erik, > > On 2018-08-22, Erik Bray wrote: > > Really the workflow is meant to be you create an issue first, and then > > you create one or more pull requests to resolve that issue. I am also > > a fan of being able to "elevate" an issue t

[sage-devel] update installation guide - macOS user required

2018-08-23 Thread Vincent Delecroix
Dear all, At [#25595] we did update the outdated information of our installation guide. Though neither me nor the reviewer has access to a macOS and we would be happy to hear comment about whether the macOS app script has been broken (I did modify the Makefile to generate the app), what are the v

[sage-devel] recommendation: delete local/share/mathjax/mathjax, run make doc-clean, then make

2018-08-23 Thread John H Palmieri
I found that my Sage documentation directory was taking up 15GB of hard drive space, because of a bug (which I think has been fixed, but I don't remember where). The bug was caused by a recursive symlink local/share/mathjax/mathjax -> local/share/mathjax When the contents of local/share/mat

[sage-devel] Re: recommendation: delete local/share/mathjax/mathjax, run make doc-clean, then make

2018-08-23 Thread Travis Scrimshaw
Running the du command (which took quite a bit of time to run), mine was 21GB. That might have been why the docbuild for me was hanging after it had finished tutorial... Trying now. Best, Travis On Friday, August 24, 2018 at 6:13:11 AM UTC+10, John H Palmieri wrote: > > I found that my Sage do

[sage-devel] Re: recommendation: delete local/share/mathjax/mathjax, run make doc-clean, then make

2018-08-23 Thread Travis Scrimshaw
> Running the du command (which took quite a bit of time to run), mine was > 21GB. That might have been why the docbuild for me was hanging after it had > finished tutorial... Trying now. > Yep, that seems to have done the trick. Best, Travis -- You received this message because you are sub

[sage-devel] Re: recommendation: delete local/share/mathjax/mathjax, run make doc-clean, then make

2018-08-23 Thread Dima Pasechnik
Yeah, I also got hit by this, gigabytes of extra stuff :-( The symlink comes from sagenb/spkg-install, see https://trac.sagemath.org/ticket/18011 Some symlinking is still happening on 8.4.beta1, see $ git show 32f5bbeac80 commit 32f5bbeac804b37776007407eb00b8acd39559e7 Author: Erik M. Bray Date