The Debian unstable changelog lists as additional changes over the Saucy
version (among others):

texlive-bin (2013.20130722.31261-1) unstable; urgency=low

  * allow for different origin in make-orig-tar
  * Imported Upstream version 2013.20130722.31261
    - fix for crash of luatex on x32 archs in certain cases
    - update metapost to 1.803
  * ship new pmpost patch for 1.803
  * bump standards version, no changes necessary

 -- Norbert Preining <[email protected]>  Fri, 26 Jul 2013 14:39:43
+0900

This would appear to be the relevant change regarding Metapost.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-bin in Ubuntu.
https://bugs.launchpad.net/bugs/1220653

Title:
  mpost binary is broken

Status in “texlive-bin” package in Ubuntu:
  New

Bug description:
  The Metapost binary distributed on the TeXlive2013 CDROM is broken; an
  upgrade using tlmgr will fix it.

  The brokenness exhibits itself in both i386 as well as amd64 binaries:
  one result is that the fonts generated when building LilyPond are
  broken, showing (among other important broken glyphs) a severely ugly
  treble clef.

  This has been reported on <URL:https://lists.gnu.org/archive/html
  /lilypond-devel/2013-09/msg00000.html> as well as
  <URL:http://lists.gnu.org/archive/html/bug-
  lilypond/2013-09/msg00011.html> (the report starts for current Fedora
  which is also afflicted but the discussion evolves around the TeXlive
  source of the problem).

  I have checked that the Debian packages for either wheezy or sid are clean 
(at least for i386): those packages would be
  /home/dak/Downloads/texlive-binaries_2012.20120628-4_i386.deb
  /home/dak/Downloads/texlive-binaries_2013.20130729.30972-1_i386.deb

  In contrast, the current Saucy package is broken.  It is
  /var/cache/apt/archives/texlive-binaries_2013.20130529.30792-1build2_i386.deb

  It would seem that upgrading to current sid would likely do the trick
  though it is unclear exactly what caused the problem (apparently it
  was presumed to have been fixed in TeXlive by recompiling with a
  version of GCC newer than 4.5.4, but that would not seem to match the
  circumstances under which the problem appears here).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-bin/+bug/1220653/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to