tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: tech@mdocml.bsd.lv
Subject: Remaining fatal processing errors with HEAD mandoc
Date: Fri, 23 Dec 2011 21:44:45 +0100	[thread overview]
Message-ID: <20111223204445.GA29265@britannica.bec.de> (raw)

Hi all,
the following list represent a pass over slightly older pkgsrc using all
packages that build on amd64. I have removed packages that use .so from
this list -- they will either use it as symlink (which will be fixed
appropiate) or wouldn't pass nroff without -s.

If there is interest, I will put the original files up for download.

Joerg

Canna-lib-3.6pl4nb2 ./ja_JP.EUC/man3/uilib.3:
mandoc: man.c:212: man_node_append: Assertion `MAN_BLOCK == p->parent->type' failed.
Aborted

Geomyidae-0.12 ./man8/Geomyidae.8:
./man8/Geomyidae.8:229:2: FATAL: child violates parent syntax

acr-0.4 ./man5/configure.acr.5:
./man5/configure.acr.5:41:1: FATAL: child violates parent syntax

autoconf-2.68 ./man1/config.sub.1:
./man1/config.sub.1:0:1: FATAL: no document body

autoconf-2.68 ./man1/config.guess.1:
./man1/config.guess.1:0:1: FATAL: no document body

awka-0.7.5nb2 ./man1/awka.1:
mandoc: man.c:212: man_node_append: Assertion `MAN_BLOCK == p->parent->type' failed.
Aborted

awka-0.7.5nb2 ./man5/awka-elm.5:
mandoc: man.c:212: man_node_append: Assertion `MAN_BLOCK == p->parent->type' failed.
Aborted

awka-0.7.5nb2 ./man5/awka-elmref.5:
mandoc: man.c:212: man_node_append: Assertion `MAN_BLOCK == p->parent->type' failed.
Aborted

bmon-2.0.1nb1 ./man1/bmon.1:
mandoc: man.c:212: man_node_append: Assertion `MAN_BLOCK == p->parent->type' failed.
Aborted

btpin-qt-1.4nb8 ./man1/btpin-qt.1:
./man1/btpin-qt.1:75:2: FATAL: child violates parent syntax

dash-0.5.5.1nb2 ./man1/dash.1:
./man1/dash.1:2136:1: FATAL: child violates parent syntax

file-5.03 ./man1/file.1:
./man1/file.1:178:16: FATAL: argument count wrong, violates syntax

freeradius-2.1.10nb1 ./man5/dictionary.5:
mandoc: man.c:212: man_node_append: Assertion `MAN_BLOCK == p->parent->type' failed.
Aborted

groonga-1.2.7 ./ja/man1/groonga.1:
mandoc: man.c:212: man_node_append: Assertion `MAN_BLOCK == p->parent->type' failed.
Aborted

groonga-1.2.7 ./man1/groonga.1:
mandoc: man.c:212: man_node_append: Assertion `MAN_BLOCK == p->parent->type' failed.
Aborted

ja-man-19990531nb3 ./ja_JP.EUC/man1/fpr.1:
./ja_JP.EUC/man1/fpr.1:60:2: FATAL: argument count wrong, violates syntax: columns == 0 (have 2)

ja-man-19990531nb3 ./ja_JP.EUC/man1/tr.1:
./ja_JP.EUC/man1/tr.1:136:2: FATAL: argument count wrong, violates syntax: columns == 0 (have 2)

ja-man-19990531nb3 ./ja_JP.EUC/man9/rnd.9:
./ja_JP.EUC/man9/rnd.9:72:1: FATAL: child violates parent syntax

ja-man-19990531nb3 ./ja_JP.EUC/man9/rnd_attach_source.9:
./ja_JP.EUC/man9/rnd_attach_source.9:72:1: FATAL: child violates parent syntax

ja-man-19990531nb3 ./ja_JP.EUC/man9/rnd_detach_source.9:
./ja_JP.EUC/man9/rnd_detach_source.9:72:1: FATAL: child violates parent syntax

ja-man-19990531nb3 ./ja_JP.EUC/man9/rnd_add_uint32.9:
./ja_JP.EUC/man9/rnd_add_uint32.9:72:1: FATAL: child violates parent syntax

ja-man-19990531nb3 ./ja_JP.EUC/man9/rnd_add_data.9:
./ja_JP.EUC/man9/rnd_add_data.9:72:1: FATAL: child violates parent syntax

mg2a-1.11 ./man1/mg.1:
./man1/mg.1:134:2: FATAL: child violates parent syntax: want parent Bl

mp-3.7.1nb3 ./man1/mimep_fr3.1:
./man1/newmail.1:13:2: FATAL: child violates parent syntax

openldap-nops-2.4.24 ./man5/slapo-nops.5:
./man1/irb19.1:162:2: FATAL: child violates parent syntax

ruby19-base-1.9.2pl290nb5 ./man1/ruby19.1:
./man1/ruby19.1:497:2: FATAL: child violates parent syntax

ruby19-base-1.9.2pl290nb5 ./man1/ri19.1:
./man1/ri19.1:168:2: FATAL: child violates parent syntax

ruby19-base-1.9.2pl290nb5 ./man1/erb19.1:
./man1/erb19.1:146:2: FATAL: child violates parent syntax

ruby193-base-1.9.3p0nb1 ./man1/irb193.1:
./man1/irb193.1:162:2: FATAL: child violates parent syntax

ruby193-base-1.9.3p0nb1 ./man1/ri193.1:
./man1/ri193.1:168:2: FATAL: child violates parent syntax

ruby193-base-1.9.3p0nb1 ./man1/ruby193.1:
./man1/ruby193.1:497:2: FATAL: child violates parent syntax

ruby193-base-1.9.3p0nb1 ./man1/erb193.1:
./man1/erb193.1:146:2: FATAL: child violates parent syntax

screws-0.56nb6 ./man1/screwsctl.1:
./man1/screwsctl.1:5:16: FATAL: argument count wrong, violates syntax

screws-0.56nb6 ./man5/screws.conf.5:
./man5/screws.conf.5:5:16: FATAL: argument count wrong, violates syntax

screws-0.56nb6 ./man8/screwsd.8:
./man8/screwsd.8:5:16: FATAL: argument count wrong, violates syntax

sj3-client-2.0.1.23p1 ./man1/sj3dic.1:
./man1/sj3dic.1:141:2: FATAL: argument count wrong, violates syntax

tinc-1.0.13nb2 ./man5/tinc.conf.5:
./man5/tinc.conf.5:179:1: FATAL: child violates parent syntax

tspc-2.1.1nb1 ./man8/tspc.8:
./man8/tspc.8:48:17: FATAL: argument count wrong, violates syntax
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

             reply	other threads:[~2011-12-23 20:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-23 20:44 Joerg Sonnenberger [this message]
2011-12-23 23:49 ` Kristaps Dzonsons
2011-12-28 17:36   ` Joerg Sonnenberger

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=20111223204445.GA29265@britannica.bec.de \
    --to=joerg@britannica.bec.de \
    --cc=tech@mdocml.bsd.lv \
    /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).