ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Kip Warner <kip@thevertigo.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Broken Nightly 2012.02.29
Date: Thu, 01 Mar 2012 20:23:50 -0800	[thread overview]
Message-ID: <1330662230.3025.38.camel@kip-laptop> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1897 bytes --]

Hey list,

Another broken nightly to report. I got this error while compiling my
book:

...
structure       > sectioning > subsubsubject @ level 5 : 0.7.1.0.0 ->
\bf 44 Aquarius, 48 B.R.
structure       > sectioning > subsubsubject @ level 5 : 0.7.1.0.0 ->
\bf 48 Aries, 15 B.R.
structure       > sectioning > subsubsubject @ level 5 : 0.7.1.0.0 ->
\bf 12 Cancer, 14 B.R.
structure       > sectioning > subsubsubject @ level 5 : 0.7.1.0.0 ->
\bf 2 Libra, 14 B.R.
structure       > sectioning > subsubsubject @ level 5 : 0.7.1.0.0 ->
\bf 3 Libra, 14 B.R.
graphics        > invalid region for 'tbg:1'
! TeX capacity exceeded, sorry [input stack size=10000].
<argument> \next 
                 
\doifmeaningelse ...>\edef \!!stringa {\meaning #1
                                                  }\def \!!stringb
{#2}\edef...
\spac_lines_between ...ningelse \next \obeyedline 
                                                  {\linesparameter \c!
inbetw...
\doifmeaningelse ...meaning #1}\def \!!stringb {#2
                                                  }\edef \!!stringb
{\meanin...
\spac_lines_between ...ningelse \next \obeyedline 
                                                  {\linesparameter \c!
inbetw...
\doifmeaningelse ...meaning #1}\def \!!stringb {#2
                                                  }\edef \!!stringb
{\meanin...
...
l.34 ... and the methane/oxygen return propellant.
                                                  
!  ==> Fatal error occurred, no output PDF file produced!
mtx-context     | fatal error: return code: 1

Unfortunately my luck with ConTeXt hasn't been so good lately. Every
single nightly has been broken since late last January (2012.01.27).
Fortunately I still have debs I can revert to.

-- 
Kip Warner -- Software Engineer
OpenPGP encrypted/signed mail preferred
http://www.thevertigo.com

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

             reply	other threads:[~2012-03-02  4:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  4:23 Kip Warner [this message]
2012-03-02  9:34 ` Hans Hagen
2012-03-02 22:38   ` Kip Warner
     [not found] ` <B435B43A-8BCA-4728-836A-7C6963C0C327@st.estfiles.de>
2012-03-02 22:41   ` Kip Warner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1330662230.3025.38.camel@kip-laptop \
    --to=kip@thevertigo.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).