[MacPorts] #27339: pdflatex.fmt doesn't match pdftex.pool
MacPorts
noreply at macports.org
Sun Jan 2 22:59:44 PST 2011
#27339: pdflatex.fmt doesn't match pdftex.pool
-------------------------------+--------------------------------------------
Reporter: ram@… | Owner: dports@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 1.9.2
Resolution: fixed | Keywords:
Port: texlive |
-------------------------------+--------------------------------------------
Comment(by dports@…):
Replying to [comment:15 vinc17@…]:
> So, it seems that xetex moved from texlive-bin to texlive-xetex. The
partial install could be the source of the problem, like with the
hyphenation.
Yes, basically. (To be precise: xetex is still *built* by texlive-bin, but
because it's not usable without texlive-xetex, it doesn't get installed
into $prefix/bin until texlive-xetex creates the symlink.)
In the end this should be harmless. What will happen when you upgrade from
texlive 2009 to 2010 is the following:
* updating texlive-bin will remove some of the existing binaries (xetex,
aleph, etc) from $prefix/bin
* after updating texlive-basic, fmtutil will be rerun to generate all
formats. Not all will succeed, because the binaries for xetex, aleph, etc.
aren't present. You should get approximately the same set of errors you
posted above.
* after texlive-xetex gets updated, fmtutil will be rerun to generate
xetex formats. Since xetex now exists, it should succeed.
* same for texlive-context, texlive-metapost, texlive-omega, etc.
Once all installed texlive ports have been upgraded, all formats should be
successfully updated. If you were to run `sudo fmtutil-sys --all`
afterwards (though you shouldn't need to do so), you shouldn't get any
errors. If that's not the case, let me know!
--
Ticket URL: <https://trac.macports.org/ticket/27339#comment:16>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list