-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sage-doc-6.5 fails due to babel problems #338
Comments
sage-doc is crufty I recommend use of sage-doc-bin (which I need to update now that the official docs are out). We seriously need to do something
Anyway this is stuff for #210 which is our long suffering ticket about building the doc and I understand if don't want to read it all. |
I have updated sage-doc-bin if you are interested in installing pdf documentation. |
Actually now that I remember it when I first created a sage-doc-bin for 6.4 I explicitly removed pdf generation for sage-doc-6.4 because we know it is broken. So It was a sloppy release from me. I'll put the ebuild in line. |
… Pointed out in issue #338. Package-Manager: portage-2.2.14
@kiwifb I just ran into this issue on ArchLinux (so not gentoo…). Did you eventually find out how to resolve this problem? Not sure what's so special about the German Tour of Sage. |
This problem is like https://trac.sagemath.org/ticket/17874 in fact. It seems to point to an underlying problem with missing a component of TeXlive. |
Apparently the sage docs fail to build for lack of some babel setting:
I guess this might have been for one of the non-english copies of the tour document; there were several similar errors later on. Perhaps my problem is the fact that I probably don't have babel support files for magyar, italian or brazil installed. Does this package perhaps depend on dev-texlive/texlive-lang{hungarian,italian}? What package do I need for brazil?
texmfind brazil.ldf
returns only somegloss-brazil.ldf
from xetex. I see the ebuild already depends on portuguese, so perhaps that's sufficient.I guess for the time being I'll disable the
pdf
USE flag, but I'd like you to know about these issues nevertheless. I'll give the package a re-run (with USE=pdf) after I merged the packages mentioned above, but not today.The text was updated successfully, but these errors were encountered: