You don't have permission to change the installation in any way, specifically, the directory /usr/local/texlive/2014/tlpkg/ is not writable. Please run this program as administrator, or contact your local admin.
@EnthusiasticStudent I think only if you have previously done tlmgr backup you can roll back to those saved ones (I never have done that though) see tlmg help
@EnthusiasticStudent I define alias sutlmgr='sudo /opt/texbin/tlmgr -gui' (approximately) in my .bashrc` file, so calling sutlmgr will do the right thing, without the dangerous sudo su
It used to be that this worked:
\documentclass{scrartcl}
\usepackage[utf8]{inputenc}
\usepackage[main=american,ngerman]{babel}
\addto\extrasamerican{\languageshorthands{ngerman}}
\begin{document}
Test"=Test
\end{document}
This is taken directly from the babel manual. We would expect to see...
I have a strange situation where cref is working great for single labels, i.e. \cref{eq:some equation} and for the first two multiple references of the form \cref{thm:first theorem,thm:second theorem,thm:amazing third theorem} works perfectly, and then after that multiple references get printed w...
@JosephWright It stopped in the middle of the tests just hung I killed it off and rebooted and windows said it was doing an update 1 of 28.... so I left it and went to bed:-) it's running now got to tlcs02 wherever that is in the scheme of things
@JosephWright I wouldn't worry about the non termination, last night windows gets a bit unstable if it has pending updates. I'll let you know when this finishes. See my mail on texlive list?
Typesetting e
This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014) (preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
LaTeX2e <2014/05/01>
Babel <3.9l> and hyphenation patterns for 79 languages loaded.
(../../build/doc/../../build/doc/e.tex
! Compilation failed
@JosephWright Didn't Frank mention glue fil earlier? tlb4069 in tools:
< .\hbox(6.94444+0.0)x167.5, glue set 103.8332fil
---
> .\hbox(6.94444+0.0)x167.5, glue set 103.83328fil
At least I think that's the problem there are .log and .etex.log files for that test showing that diff but no .diff files anywhere
@JosephWright yes I just ran build check in tools and it said all tests pass, but I just had a reply about xetex.. It would be nice if l3build would just stop rather than wait til the end then say it's not going to zip because of an error (what is it checking at that stage, can i see what it thinks was wrong?)
@JosephWright OK I removed my tools area and checked out a clean set and running build ctan in tools, see what happens this time, is it possible I had a stray e.tex ?
@JosephWright seems pretty strange to remove access to all windows fonts on a windows machine just because you might add some more and have an out of date cache
@JosephWright actually I think it was I just didn't see it, I think I had a stray e.tex which it then tried to typeset (not sure why) so then stopped at that point but it was so near the end I thought it was stopping at zip time because of an earlier error
@JosephWright OK can reproduce: run tex tools.ins "by hand" in the tools directory you get all sorts of interesting files in that directory..... build ctan then fails.
@PauloCereda If only I had never tested my code in the previous 20 years before @Joseph built a build tool, I wouldn't have output files in unexpected places in the source tree...
@DavidCarlisle Not that surprising for two reasons. First, l3build only 'cleans up' what it creates as we've had issues in the past being more aggressive. Second, the standard settings used *.<ext> as that's most convenient. However, we can tighten them up if required to just a specified list of files.
@JosephWright yes it was just unfortunate that e is rather inconspicuous:-) but I think it's not that uncommon to have generated files in the source directory, certainly if things are acting strangely I revert to doing things by hand rather than than use the build tool (whether make or l3build) not sure what that means for build clean though (or perhaps as you say it's not that build clean should delete but that build ctan should use a list. Not sure...
@DavidCarlisle As I say, it's quite possible to give l3build an explicit list of sources/typeset files/..., and this should mean it ignores anything else. It's just that this gets a bit tedious. I did tighten up the spec for tools in a checkin today.
@DavidCarlisle Problem is I think .tex as it's hidden on *nix but not on Windows
@DavidCarlisle I've tracked down why things were not halting on a check failure: I'd left a test line in l3build. Halts properly now, we should be good to go to CTAN with an update.
I just need to wait to hear what @PauloCereda has to say
@DavidCarlisle It looks like adding hyperlinks and the like to the LaTeX core distro will be pretty easy: I can grab a couple of Heiko's .cfg files and if we stick to pdfTeX that's just about it :-)