Hi again,
On 2014-05-13, Simon King <[email protected]> wrote:
> Anyway, this was with 6.3.beta0, and I now retry with beta1.
Frankly I am disappointed about the current quality of doc-building.
After pulling, "make" fails with
Note: incremental documentation builds sometimes cause spurious
error messages. To be certain that these are real errors, run
"make doc-clean" first and try again.
Traceback (most recent call last):
File "/home/king/Sage/git/sage/src/doc/common/builder.py", line 1477, in
<module>
getattr(get_builder(name), type)()
File "/home/king/Sage/git/sage/src/doc/common/builder.py", line 276, in
_wrapper
getattr(get_builder(document), 'inventory')(*args, **kwds)
File "/home/king/Sage/git/sage/src/doc/common/builder.py", line 487, in
_wrapper
x.get(99999)
File "/home/king/Sage/git/sage/local/lib/python/multiprocessing/pool.py",
line 554, in get
raise self._value
OSError: [misc ] docstring of sage.misc.c3_controlled.HierarchyElement:10:
WARNING: Inline literal start-string without end-string.
"make doc-clean" followed by "make doc" solved the problem. But it really
sucks and consumes an awful amount of time that *most* non-trivial changes
of a branch result in these "spurious" error messages!
Anyway. Worse is: The tests in sage.dev fail as before. And it seems to
be because of the "git" that comes with sage: When I use the system git,
then of course "git pull" works. But in a sage shell, I get:
(sage-sh) king@linux-etl7:sage$ git pull
git: 'pull' ist kein Git-Kommando. Siehe 'git --help'.
Haben Sie das gemeint?
shell
So, both beta0 and beta1 are broken because of the "git" shipped by
Sage.
Best regards,
Simon
--
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
