New answers tagged

1

After compiling your given code without errors with an current MiKTeX 2.9 I get the following list of used packages and versions numbers: *File List* moderncv.cls 2015/07/28 v2.0.0 modern curriculum vitae and letter document cl ass size11.clo 2014/09/29 v1.4h Standard LaTeX file (size option) etoolbox.sty 2015/08/02 v2.2a e-TeX tools for LaTeX (...


0

As a simplest way, $ equivs-control texlive-local $ cp debian-equivs-2015-ex.txt texlive-local $ equivs-build texlive-local


8

The change to hyperref was to fix this issue https://github.com/ho-tex/hyperref/issues/11 which I have just re-opened, pointing here. I will update hyperref to address this (somehow:-) but meanwhile, this works: \documentclass{article} \usepackage{amsthm} \usepackage{hyperref} \usepackage{cleveref} \newtheorem{thm}[equation]{Theorem} \makeatletter ...


0

I had the same problem while updating TeXLive 2016. It seems like after a update the perl gets buged or something, during install there might be no errors at all. Maybe some other program made the perl file corrupted, I don't know. So this what I did and worked for me: Browse to your ...\texlive\2016\tlpkg\ delete the whole tlperl directly, as this one ...


1

You probably set TeX programs: in 'TeX Live Utility->Preferences manually at some point. Please go to <http://www.tug.org/mactex/elcapitan.html> and look at section 6 of the linkedUpdating For El Capitan' document.


2

Open TeX Live Utility's Preferences window and ensure that the path is set correctly for MacTeX. Use the button to choose /Library/TeX/texbin or drop that folder on the path bar.


6

The easiest way is to load luatex85 package. You probably will need to load it before documentclass, using RequirePackage The longer story is that luatex now no longer defines many primitives with pdf prefix. The luatex85 package defines aliases of primitives which have the same names as in pdftex and earlier versions of luatex.


7

The fix is easy: add \RequirePackage{luatex85} as the very first line, a temporary workaround until standalone is updated. It should do no harm even after the update. \RequirePackage{luatex85} \documentclass{standalone} \begin{document} hi \end{document}


4

The reason is that for each package there is first a try via ftp and LWP that fails, see: TLDownload::get_file: response error: 400 FTP return code 000 (for ftp://tug.org/historic/systems/texlive/2015/tlnet-final/archive/ms.source.tar.xz) TLUtils::download_file: persistent connection ok, but download failed: ftp://tug.org/historic/systems/texlive/2015/tlnet-...


1

Yes, you can. As cfr pointed out in his comment, it is easiest when both are using the same architecture. If you use different archs you only need to install all of them with tlmgr arch add ..... After that it is a simple case of setting the PATH correct for the respective computer. Concerning rsync: I would do a rsync -avz --delete to make sure that files ...


1

My online book Formatting Information has full details of how to create a Personal TeX Directory (used for private or additional material not covered by tlmgr) and install packages in it (http://latex.silmaril.ie/formattinginformation/pkginst.html#installpkg).


0

I had the same issue Unknown directive ...containerchecksum using Debian on Docker. To overcome this I looked up all of my latex packages using: RUN apt-get install -y apt-file RUN apt-file update RUN apt-file search <name-of-latex-package> Most of them were in texlive-latex-base and texlive-latex-base and the only other one that I needed was ...


2

The files should not go under .../texlive/2016/texmf-dist/, but under .../texlive/texmf-local. The main tree is only for things in the official distribution: changing it might leave an unstable TeX system. Installing the files in the “distribution” tree has the consequence that everything has to be redone at every release of TeX Live. This said, the ...


0

As a temporary workaround, I finish with this $output = system("echo 'pass' | sudo -u user /usr/bin/pdflatex -output-directory /var/www/files --interaction batchmode files/".$name.".tex");


2

My answer is two-fold, depending on how you mean to use Qt (or any other poratble toolkit): if you want to use qt installer - this does not work as most installer routines are written in perl and converting them to qt installer would be a big procedure. I don't say it is impossible, but it needs work if you want to use the Qt Toolkit, that is perl/qt, then ...


2

I tried your example but did not find the issue you described. I am using the stock TeXLive 2016, updated just today. The fonts are the versions from Adobe Font Folio 11 (but I don't think the versions of the fonts are issues here). Though I do have the patch in https://github.com/wspr/fontspec/pull/231 applied to fontspec. I am not sure if that is the issue....


1

As long as LuaTeX suffers from bugs, install Adobe Cronos Pro for pdftex following this manual and support: https://github.com/sebschub/FontPro There are some discussion how to get it all to work here: Myriad Pro Condensed undefined


1

There are many things that have changed in TL 2016 with repect to luatex: First of all of course that many primitives have been changed, but also that the font loader has been rewritten in lua instead of using the fontforge libraries. While this is in principle a good idea, there surely are many bugs lurking and you are asked to report them to the bug ...


0

From Tunisia any mirror in Europe should be fine. Otherwise use one of the mirrors in Africa, that is: Algeria (http://ctan.epst-tlemcen.dz/tex-archive/) South Africa http://ctan.mirror.ac.za/ http://ftp.leg.uct.ac.za/pub/packages/ctan/ http://ftp.sun.ac.za/ftp/CTAN/ Not sure which one is the best. Concerning TeXmaker: you simply need to make sure ...


8

You are using tlmgr from TeX Live/Debian, that is the packaged version. This version does not work with current (2016) release, and there is no way around that. You have two options: install upstream TeX Live stop using Debian's tlmgr to install packages unless you find an archive of TL 2015 version. This should happen only rarely when we (TeX Live Team)...


1

There is a bug in current tlmgr (or at least two would be better) that returns an error during the action tlmgr path add. Thanks for the report, I will fix it (in due time). I have checked the source but didn't find any obvious bug, but I will eventually fix it as I see the same behaviour. Why on your side xindy.mem wasn't linked is strange, because in my ...


10

If you want to continue to use 2015 version you should set the repository to the archived version with: tlmgr option repository ftp://tug.org/historic/systems/texlive/2015/tlnet-final as is explained here How to install a package from an older version of TeXLive?.


8

In the new luatex \write18 is no longer special. To get the functionality back: Load the package shellesc and read its documentation.


1

The server you are using is not already updated, simply wait a day or two.


2

For the record, if you're using the TeXLive Utility GUI, you can also solve this issue by selecting the Configure > Configure Documentation..., checking the box labeled "Install documentation when updating", and confirming by clicking the Install now button. (I just ran into this issue after installing BasicTeX and the TeXLive Utility GUI on my Mac, by ...


12

A few answers: since about 5 years we had the option for upgrading installations, so there have been rolling releases. Don't mix it up with the freeze before DVD production, as I laid out in the answer to your other question this year the infrastructure has changed in incompatible way, in particular the checksum method was updated. This means that older ...


16

How can you roll an update to luatex that undefines many primitives, renames many primitives and has incompatible changes to the main lua node and callback interfaces? It takes months of contacting and pre-warning package authors to make changes required. Even then not all done by time TL2016 goes live. Not to mention testing building and packaging on all ...


5

As detailed in the tlmgr help, you want tlmgr option repository http://mirror.ctan.org/systems/texlive/tlnet run as Administrator/sudo if your TeX system was installed in that way. The above points tlmgr to the mirror network, almost always what you want.


0

Instead of using \usepackage[brazilian]{babel}, use \usepackage[brazil]{babel}. It should work. According to the documentation, brazilian should work as well as brazil, but it isn't. Perhaps brazilian was removed (no longer in use) but the documentation wasn't updated. The weird thing is that taking a fast look at the code, brazilian is there! Maybe it's a ...


1

At the moment it seems like the answer is there is no way, since Xindy doesn’t use kpathsea. In 2014 I posted a feature request at SourceForge and it is assigned to the 2.6 mile stone (current ist v2.3). So th easiest way to “install” is to copy the style file in the project folder.


2

The texlive-dummy packages on CTAN seem, unfortunately, not to include the source code. Thus, while they claim to be released under the LPPL, they are in practice difficult or impossible to modify. Since they are distribution specific and none is provided for Fedora as such, it isn't clear how well they might work in this case. To be honest, I had no idea ...


1

As daleif suggested, the package is on CTAN. It's called "texlive-dummy" (at least for RedHat-based distributions), and works like a charm.


3

I will add a different point of view. Two years ago when I started using Ubuntu I had quite some troubles installing all the LaTeX packages, citation styles, fonts etc (There are so many ways of doing it! See this discussion) Then, somehow I found this thread. I purged the original ubuntu-tex-live with everything else that had "tex" in it, and installed ...


0

I suggest you install TeXLive from TUG (http://tug.org/texlive/). It does not interfere with system package manager. And more or less, you can get the same behavior across all platforms. Just remember to put the PATH to texlive binary before everything else. It is possible that there might be some conflicts. For example, an executable within TeXLive has the ...



Top 50 recent answers are included