hugin-devs team mailing list archive

[Sping <1181678@xxxxxxxxxxxxxxxxxx>]

commit 13d95cfe56b912f73214117a4af28560370305a4
Author: Sebastian Pipping <sping@xxxxxxxxxx>
Date:   Fri Aug 14 03:22:28 2015 +0200

    media-gfx/enblend: Fix texinfo compilation (bug #479978)
    
    Upstream patch (with version patching removed) from
    https://bugs.launchpad.net/enblend/+bug/1181678/comments/16
    http://hg.code.sf.net/p/enblend/code/rev/8387f0170f7b
    
    Signed-off-by: Sebastian Pipping <sping@xxxxxxxxxx>

 media-gfx/enblend/enblend-4.1.3-r1.ebuild          |  79 +++
 .../files/enblend-4.1.3-texinfo-5-more.patch       |  82 +++
 .../files/enblend-4.1.3-texinfo-5-upstream.patch   | 633 +++++++++++++++++++++
 3 files changed, 794 insertions(+)

-- 
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
https://bugs.launchpad.net/bugs/1181678

Title:
  build-error with texinfo 5.1

Status in Enblend:
  Fix Committed
Status in enblend package in Gentoo Linux:
  Unknown

Bug description:
  Hello,

  documentation generation fails with texinfo 5.1.  texinfo seems to have stopped supporting colons in variable names (@set <-> @value), causing errors like this one:
  -----
  doc/enfuse.texi:564: bad syntax for @value
  -----

  According to texinfo 5.1 documentation basically the only thing
  guaranteed to work are alpha-numericals:

  Subsequent characters, if any, may not be whitespace, ‘@’, braces,
  angle brackets, or any of ‘~`^+|’; other characters, such as ‘%’, may
  work. However, it is best to use only letters and numerals in a flag
  name, not ‘-’ or ‘_’ or others—they will work in some contexts, but
  not all, due to limitations in TeX.

  cu Andreas

  See http://bugs.debian.org/708800 or
  https://bugzilla.redhat.com/show_bug.cgi?id=919935

To manage notifications about this bug go to:
https://bugs.launchpad.net/enblend/+bug/1181678/+subscriptions