Re: [sage-release] Re: Sage 6.2.beta3 released
That sounds like something which make doc-clean would fix. John On 6 March 2014 07:55, Dima Pasechnik dimp...@gmail.com wrote: On 2014-03-05, Volker Braun vbraun.n...@gmail.com wrote: You need to run make to update the banner and third-party code. The sage -b will only rebuild the Sage python library. now, after fighting with and aborting a merge, and then getting back to beta3 I am getting OSError: [reference] WARNING: Unable to fetch SAGEROOT/src/doc/output/doctrees/en/reference/numeric/environment.pickle while doing make. Is there any way to fix this, short of wiping out the whole thing and starting from scratch? Mind you, according to git, everything is fine: I have $ git status # On branch develop nothing to commit, working directory clean $ Needless to say, I did not commit anything myself after beta3 came out. Here is more dochtml.log - although it's pretty uninformative regarding a particular source file which is nuked: [reference] number_fields: 1 todos, 20 index, 5 citations, 19 modules [reference] numeric: [reference] WARNING: Unable to fetch /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/output/doctrees/en/reference/numeric/environment.pickle [reference] WARNING: Unable to fetch /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/output/doctrees/en/reference/numeric/environment.pickle Traceback (most recent call last): File /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/common/builder.py, line 83, in f execfile(sys.argv[0]) File /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/common/custom-sphinx-build.py, line 185, in module sphinx.cmdline.main(sys.argv) File /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/local/lib/python2.7/site-packages/Sphinx-1.1.2-py2.7.egg/sphinx/cmdline.py, line 206, in main print error File /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/common/custom-sphinx-build.py, line 165, in write self._write(str) File /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/common/custom-sphinx-build.py, line 139, in _write self._log_line(line) File /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/common/custom-sphinx-build.py, line 108, in _log_line raise OSError(line) OSError: [reference] WARNING: Unable to fetch /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/output/doctrees/en/reference/numeric/environment.pickle On Wednesday, March 5, 2014 2:27:57 PM UTC, Dima Pasechnik wrote: On 2014-03-05, Nathann Cohen nathan...@gmail.com javascript: wrote: Hell !! suppose I previosuly had beta2 installed from the tarball. What is the git way to get the update? Would 'git pull' followed by 'make' be enough? Yep. First make sure that your current branch is actually the beta2 release (and not some ticket's branch, or something you are working on), and then git pull. And make, which is not always necessary (when spkg were updated if I make no mistake). If something happens, then it works. If you get an error message, share it :-D something has happened, surely, but at the end I still see beta2 banner, even though git log says that the latest commit is commit ccab9854bf85180a261d71a8adc103d4c1f26342 Author: Volker Braun vbrau...@gmail.com javascript: Date: Mon Mar 3 16:05:18 2014 +0100 Updated Sage version to 6.2.beta3 and one can see that the banner is updated by this commit. Well, sage-banner in src/bin/ is different from the one in local/bin/; the latter stays on beta2. How are the scripts in local/bin updated? -- 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 sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/groups/opt_out. -- 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 sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/groups/opt_out.
[sage-release] Re: Sage 6.2.beta3 released
On 2014-03-05, Volker Braun vbraun.n...@gmail.com wrote: You need to run make to update the banner and third-party code. The sage -b will only rebuild the Sage python library. tried this several times, also with setting MAKE to make -j1. I doubt it is a race condition... On Wednesday, March 5, 2014 2:27:57 PM UTC, Dima Pasechnik wrote: On 2014-03-05, Nathann Cohen nathan...@gmail.com javascript: wrote: Hell !! suppose I previosuly had beta2 installed from the tarball. What is the git way to get the update? Would 'git pull' followed by 'make' be enough? Yep. First make sure that your current branch is actually the beta2 release (and not some ticket's branch, or something you are working on), and then git pull. And make, which is not always necessary (when spkg were updated if I make no mistake). If something happens, then it works. If you get an error message, share it :-D something has happened, surely, but at the end I still see beta2 banner, even though git log says that the latest commit is commit ccab9854bf85180a261d71a8adc103d4c1f26342 Author: Volker Braun vbrau...@gmail.com javascript: Date: Mon Mar 3 16:05:18 2014 +0100 Updated Sage version to 6.2.beta3 and one can see that the banner is updated by this commit. Well, sage-banner in src/bin/ is different from the one in local/bin/; the latter stays on beta2. How are the scripts in local/bin updated? -- 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 sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/groups/opt_out.
[sage-release] Re: Sage 6.2.beta3 released
I've never seen that error. The documentation is built at the end, so that means that Sage was built without errors. Can you try running the doctests? Perhaps some component is not working and somehow makes the numeric/environment.pickle invalid? If all fails, run make distclean make... On Thursday, March 6, 2014 7:55:12 AM UTC, Dima Pasechnik wrote: Here is more dochtml.log - although it's pretty uninformative regarding a particular source file which is nuked: [reference] number_fields: 1 todos, 20 index, 5 citations, 19 modules [reference] numeric: [reference] WARNING: Unable to fetch /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/output/doctrees/en/reference/numeric/environment.pickle [reference] WARNING: Unable to fetch /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/output/doctrees/en/reference/numeric/environment.pickle Traceback (most recent call last): File /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/common/builder.py, line 83, in f execfile(sys.argv[0]) File /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/common/custom-sphinx-build.py, line 185, in module sphinx.cmdline.main(sys.argv) File /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/local/lib/python2.7/site-packages/Sphinx-1.1.2-py2.7.egg/sphinx/cmdline.py, line 206, in main print error File /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/common/custom-sphinx-build.py, line 165, in write self._write(str) File /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/common/custom-sphinx-build.py, line 139, in _write self._log_line(line) File /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/common/custom-sphinx-build.py, line 108, in _log_line raise OSError(line) OSError: [reference] WARNING: Unable to fetch /home/scratch/dimpase/sage/6.1/sage-6.1.rc0/src/doc/output/doctrees/en/reference/numeric/environment.pickle -- 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 sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/groups/opt_out.
[sage-release] Re: Sage 6.2.beta3 released
On 2014-03-06, Volker Braun vbraun.n...@gmail.com wrote: I've never seen that error. The documentation is built at the end, so that means that Sage was built without errors. Can you try running the doctests? Perhaps some component is not working and somehow makes the numeric/environment.pickle invalid? If all fails, run make distclean make... Tried make distclean make, with no luck (!). I'm going to get the tarfile of beta3 and compare the sources, something must be fishy out there... -- 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 sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/groups/opt_out.
