TeX Live from the Terminal/Command Prompt (Windows/Mac/Linux)
Understanding the TeX Live update scheme
If you have a TeXLive distribution (including MacTeX) there are a few things to understand about updating your system.
All TeX distributions consist of both binaries (including scripts) and packages (including classes). It is important to understand ...
With MacTeX on Mac OS X you’ll have the TeX Live Utility installed. If you start this app it will connect with CTAN and list up the possible updates.
In the list you can see if a package is updated, removed from TeX Live (gray) or new/uninstalled (blue). Now make sure that you are not using one of the packages that will be deleted. If you are ...
Ok, here's an answer as the main developer of tlmgr and the whole TeX Live infrastructure. You have to decide two things:
the freeze period before release of a new version
upgradability from one release to the next
Concerning the former, freeze period: Normally during the year we do not make updates to the actual binaries, but only to scripts and the ...
MiKTeX has reorganized the package amslatex. Therefore the update removes it:
The package amslatex is split in amsmath and amscls. (Also there is a new package amslatex-primer):
However, the update has not installed the new packages automatically. Therefore I have installed them manually. For AmSLaTeX you need at least amsmath. It contains the ...
I can't speak for TeX Live in particular, but I have been involved with Linux distributions from their very beginning, and I believe my observations there are relevant for TeX Live too (both are collections of disparate pieces that have to be selected, integrated and convinced to work nice together, each piece evolves at their own pace).
While in a perfect ...
TeX Live GUI (Windows)
TeX Live on Windows includes a graphical user interface for managing installed packages. The first stage of using this, after starting it from the Start Menu, is to load the package list from the internet.
Once this is done, you can simply press the Update button to run the process.
Notice that I've chosen to reinstall any removed ...
in addition to @vonbrand's excellent answer, one important reason to upgrade and "freeze" tex live annually is to provide a stable snapshot on physical media, largely for the benefit of members of the various user groups, but also for tex users who don't have convenient internet access.
this dvd (it no longer fits on a cd) is also physically packaged with ...
amsmath is definitely not obsolete! It may have some old and unrepaired bugs, but it still has the status "maintained" and AMS has every intention of keeping it that way.
Something else must have gone wrong with your update.
EDIT: amsmath and the AMS document classes + amsthm used to be combined on CTAN under the name amslatex. They have always been ...
Meaning: this package is referenced as dependency in one of the collections, but not present. This can normally only happen by calling tlmgr remove --force. Sometimes when a tlmgr run is interrupted similar things might occur.
Fixing: To fix the problem you can run
tlmgr install <package>
to reinstall a single package or
tlmgr update --all --...
For some reasons (a bug in the Perl script, it appears), the double quotes surrounding Quick Start in the docfile tag are not properly escaped.
A fix has already been uploaded in the TeX Live repository, (see here for the differences or here for downloading the new version of the Perl module).
The easiest fix, before the new version of tlmgr propagates, is ...
MiKTeX from the Command line (Windows/macOS/Linux)
See also How should one maintain and update a MiKTeX installation?
The command line tool for MiKTeX package manager is called mpm. It can be used as:
The MiKTeX website has this description for the tool mpm.
MPM (MiKTeX Package Manager) is used to install packages from a MiKTeX
fixltx2e, etex, morefloats, latexrelease are all affected to some extent.
At each LaTeX release there is a one or two page newsletter describing the main changes (ltnews 22 and 23 for the 2015/01/01 and 2015/10/01 releases, respectively) these days we bundle them as one file texdoc ltnews or ltnews.pdf from CTAN.
As detailed in ltnews 23 fixltx2e is ...
I had the same problem - the sollution above didn't work for me, but what worked can be found at http://comments.gmane.org/gmane.editors.lyx.general/69152. The sollution is:
Problem solved. PDFLatex doesn't die after a problematic run due to an
uninstalled package. It was blocking some files which, I guess, needed
to be modified by the Package Manager....
Generally speaking, there’s always a risk that something will break and the usual caveats thus apply: never update on a deadline, check that the output of your document is satisfactory, etc.
That said, backward compatibility is, as David says in the comment, a primary concern of package developers. TeX and its associated programs have always been presented ...
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 ...
To add some more information to the answers of @vonbrand and @barbara beeton:
One other reason is to change infrastructural things. Some time ago the tlmgr management tool was introduced with a graphical interface for (mainly) windows users. Also the package format was changed (I think it was from TL2008 to TL2009) from LZO to XZ which was not possible if ...
You can manually update/install packages into your local TEXMF tree. Usually they are picked up there first so if you put a newer (or older) version of a package there it will be taken instead of the one installed in your distributions (TeX Live, MikTeX, etc.) TEXMF tree.
Under Linux, Unix and similar OSs your local TEXMF is usually simply ~/texmf. For ...
The 'proper' (internal) name of the primitive has always been \textdir, but for various reasons it used to be 'activated' as \luatextextdir in LuaLaTeX. The LaTeX team have recently revised this approach and all primitives now have their 'natural' names in LuaLaTeX. Thus you should either update your code or add
In case the issue is not due to tlcontrib, running update-tlmgr-latest.sh solves the problem.
Kudos to Norbert Preining for the answer on the TeX Live list!
I record here the required steps for posterity.
In case you don't have it, retrieve the script:
Check if you can run kpsewhich ...
The new texlive-core package requires user-intervention when updating. Running sudo pacdiff (this replaces existing files with the new .pacnew files)
followed by sudo fmtutil-sys --all should fix it.
For more complete instructions, see: https://www.archlinux.org/news/texlive-2013-update-may-require-user-intervention/
When you perform a TeX Live update, the specific packages that were updated is logged in tlmgr.log (located in ~/texmf-var/web2c/). It looks like this:
[Thu Jan 30 16:39:24 2014] update: sa-tikz (32788 -> 32815)
[Thu Jan 30 16:39:28 2014] update: texlive-msg-translations (32801 -> 32813)
[Thu Jan 30 16:39:32 2014] update: texlive-scripts (32798 -&...
If you use a graphical interface, the list of updates is available for inspection prior to doing the actual download. Here's an example with the Tcl-Tk interface
Here's the same with TeX Live Utility (Mac OS X)
Say you want to see what's changed in quoting: the remote version is 32818; go to
For me the biggest change is Lua(TeX): the ability to separate TeX's building blocks (processing the input / building the node lists / output). That way you can for example build a product that uses TeX's linebreaking and hyphenation algorithm and its superb output, but without its troublesome input language.
With the minimal TeX file
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 ...
The LaTeX3 team is well presented in the web. The current development branch is available at LaTeX Project - Source repository
To download the newest version you can use svn.
For Unix users
The following command download the complete trunk folder to the current folder of your opened terminal
~$ svn co http://www.latex-project.org/svnroot/experimental/...
TeX Live OpenBSD
All packages TeXLive included are compiled against specific version of OpenBSD i.e. package upgrade is not possible without upgrading kernel and userland first. A typical desktop user (i386, amd64, loongson, sparc64, macppc, sgi) moving from 2010 TeXLive version which was shipped with OpenBSD 5.0 released November 1 of 2011 to TeXLive 2011 ...
If I understand your question right:
The MiKTeX update process has generally three parts:
If there are changes in the basic system (miktex.exe etc.) MiKTeX downloads and updates only this files. Then the update process has to be started once again.
Are there packages to be deleted? If yes, then the MiKTeX update manager is programmed to mark only that ...
Just go to the /usr/local/texlive folder: do Command-Alt-G from the Finder and type /usr/local/texlive in the box
You'll be presented with folders named texmf-local, 2013 and 2014:
(I still have the 2012 version for testing).
Drag the 2013 folder to the trashcan; the system will ask for an Administrator password. Empty the trash. End of MacTeX 2013.
You don't need to write to Herb for a fix. Credit goes to Bruno Voisin for finding the solution to this. Some background is here:
I think the simplest solution is here, requiring use of the Terminal: