Conversation
Time frame? I assume this is required by that ticket, right, else the docs break? |
No, nothing breaks without this ticket. |
Just to make things clear. Jeroen has put links to the old location so |
|
Yes. Although ideally I would have wanted Jeroen to change the variable names so that what is currently |
d735fde
to
060e21e
Compare
New version for http://trac.sagemath.org/ticket/20030 |
This is now a requirement for http://trac.sagemath.org/ticket/20030 otherwise incremental building of documentation will break. Part of the problem is that |
Okay. Listen, if you (@kiwifb) can give a 100% positive review to this change I am happy to merge it and make a new release, though it might not happen for a few days. I know that I won't have time to check the complex interaction between sagenb and Sage on this this week. But all these changes seem pretty straightforward cleanup and then moving. Does the live documentation as well as pdf and html static links all seem to work with this change (as I expect they do)? |
With the exception to the change to I do one extra thing but that go beyond the scope of the change we want (Don't like using |
I also will need time to make a branch with the downstream change, do |
Hi - any sense on what a good test of this and corresponding sage change is? Just |
From
would tell you quite a bit. Also Volker said that incremental build is broken, not sure how to simulate that. But I think that with http://trac.sagemath.org/ticket/20030 without this the |
Thanks, @kiwifb - I'm not going to test that part, because I figure you guys have tested that. But I just want to do my due diligence as sagenb release manager. Everything on the testing side is fine, I will just check that sagenb itself (including doc) works tomorrow and then merge @jdemeyer's other things. |
Except:
|
What is |
Ah, it's a Catalan translation... why is that the problem, and why am I not having that file? It seems to have been dealt with in Trac 20030. I'll check back on this tomorrow (USA) if anyone has any updates. |
Well that's one of the reason we should need this PR, |
But I already have this PR and the Trac ticket in this branch... ? I do have |
Must have forgotten a change somewhere. Thing is sage-on-gentoo has also traditionally put those under |
Found it. I missed one thing that Jeroen should have changed in trac#20030, there is a |
|
And Sage too.
And sagenb still can find the docs. Only one problem remains - when you go to
(I still can't get live documentation to evaluate, but apparently I'm the only one with that problem and I don't think it's related to this.) |
I need a bit of time to check that. I must say I haven't given too much attention to pdf doc. It is sometimes difficult to build. |
I can confirm that the pdf issue is not related to this. See #365. |
Anyway, I'll wait to merge this until Trac 20030 is completely ready, and then I'll deal with the other two PRs in question. Do you want to open a Sage ticket for upgrading sagenb for this and put the dependencies on those tickets? |
OK will do later today. Earthquake at 5.9 just hit close by so there may be delay if someone I know needs assistance. |
Ack! OK will do later today. Earthquake at 5.9 just hit close by so there may be
Well, no rush on my end for sure! Take care of those in need. |
Done on trac. |
http://trac.sagemath.org/ticket/20047 is for the notebook upgrade. |
Thanks for the update. I'll get to this soon. |
We should use the new doc output location (
SAGE_DOC
) variable from http://trac.sagemath.org/ticket/20030