[sage-release] Re: Sage 6.2.beta3 released

2014-03-07 Thread Dima Pasechnik
On 2014-03-07, Volker Braun wrote: > I unpacked the sage-6.2.beta3 tarball and ran make && make doc-clean && > make and it worked without error. Somebody who can reproduce the failure > should investigate... try switching to the branch of http://trac.sagemath.org/ticket/15521 and then make etc

Re: [sage-release] Re: Sage 6.2.beta3 released

2014-03-07 Thread Volker Braun
I unpacked the sage-6.2.beta3 tarball and ran make && make doc-clean && make and it worked without error. Somebody who can reproduce the failure should investigate... On Friday, March 7, 2014 2:41:41 PM UTC, Volker Braun wrote: > > Does Sage actually work? Run "sage -btp src/" and ignore the do

[sage-release] Re: Sage 6.2.beta3 released

2014-03-07 Thread Dima Pasechnik
On 2014-03-07, Volker Braun wrote: > Does Sage actually work? Run "sage -btp src/" and ignore the doctests that > require the documentation built.. it seems that pickling in general got nuked, although parts not involving it seem work. Here is a typical failure: (apart from docs-related things)

[sage-release] Re: Sage 6.2.beta3 released

2014-03-07 Thread Dima Pasechnik
On 2014-03-07, Nathann Cohen wrote: >> Nathann, >> congratulations on creating the first Sage-docs tree eating git worm ;-) > > Come on, I just used "git commit --amend" to change a commit message. > I didn't kill anyone (I hope) :-P all we know at the moment is that the worm likes to eat *.pickl

Re: [sage-release] Re: Sage 6.2.beta3 released

2014-03-07 Thread Volker Braun
Does Sage actually work? Run "sage -btp src/" and ignore the doctests that require the documentation built.. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to s

Re: [sage-release] Re: Sage 6.2.beta3 released

2014-03-07 Thread Nathann Cohen
> Nathann, > congratulations on creating the first Sage-docs tree eating git worm ;-) Come on, I just used "git commit --amend" to change a commit message. I didn't kill anyone (I hope) :-P Nathann -- You received this message because you are subscribed to the Google Groups "sage-release" grou

[sage-release] Re: Sage 6.2.beta3 released

2014-03-07 Thread Dima Pasechnik
On 2014-03-07, Nathann Cohen wrote: > H I typed "make" then "make doc-clean" then "make" again, and > I now have exactly the same problem as Dima O_o > > OSError: [reference] WARNING: Unable to fetch > /home/ncohen/.Sage/src/doc/output/doctrees/en/reference/sets/environment.pickle > > make

Re: [sage-release] Re: Sage 6.2.beta3 released

2014-03-07 Thread Nathann Cohen
H I typed "make" then "make doc-clean" then "make" again, and I now have exactly the same problem as Dima O_o OSError: [reference] WARNING: Unable to fetch /home/ncohen/.Sage/src/doc/output/doctrees/en/reference/sets/environment.pickle make: *** [doc-html] Error 1 ~/.Sage$ cat /home/ncoh