From: Michael Stapelberg <stapelberg@debian.org>
To: discuss@mandoc.bsd.lv
Subject: Re: mandoc-1.14.5 released
Date: Sun, 28 Apr 2019 15:24:51 +0200 [thread overview]
Message-ID: <CANnVG6mFY1Tz1GdhtEZncqzsn9pR0VGaqj0oYQAKM=GkLxnc8g@mail.gmail.com> (raw)
In-Reply-To: <20190310113237.GE23000@athene.usta.de>
[-- Attachment #1: Type: text/plain, Size: 4571 bytes --]
Sorry for the late reply on this, but I only now got a chance to (try to)
update manpages.debian.org to mandoc-1.14.5.
Unfortunately, I encounter an assertion failure when running:
% curl -s
https://manpages.debian.org/testing/libpcp3-dev/pmRegisterDerived.3.en.gz |
mandoc -Thtml
[…]
mandoc: html.c:809: print_text: Assertion `NULL == h->metaf' failed.
gdb> bt
#0 0x0000000000459eab in raise ()
#1 0x000000000040122a in abort ()
#2 0x0000000000401104 in __assert_fail_base.cold.0 ()
#3 0x00000000004550c2 in __assert_fail ()
#4 0x0000000000404444 in print_text (h=0x149e470, word=0x516d370
"delta(disk.dev.total_bytes) / delta(disk.dev.total)") at html.c:809
#5 0x000000000040a405 in roff_html_pre_ce (h=0x149e470, n=0x3136bc0) at
roff_html.c:77
#6 0x000000000040a369 in roff_html_pre (h=0x149e470, n=0x77b8120) at
roff_html.c:61
#7 0x0000000000404ec9 in print_man_node (man=0x149e2d0, n=0x77b8120,
h=0x149e470) at man_html.c:221
#8 0x0000000000404c93 in print_man_nodelist (man=0x149e2d0, n=0x77b8120,
h=0x149e470) at man_html.c:156
#9 0x0000000000404fb5 in print_man_node (man=0x149e2d0, n=0x833a300,
h=0x149e470) at man_html.c:234
#10 0x0000000000404c93 in print_man_nodelist (man=0x149e2d0, n=0x833a300,
h=0x149e470) at man_html.c:156
#11 0x0000000000404fb5 in print_man_node (man=0x149e2d0, n=0x2127fb0,
h=0x149e470) at man_html.c:234
#12 0x0000000000404c93 in print_man_nodelist (man=0x149e2d0, n=0x2127fb0,
h=0x149e470) at man_html.c:156
#13 0x0000000000404fb5 in print_man_node (man=0x149e2d0, n=0x382a510,
h=0x149e470) at man_html.c:234
#14 0x0000000000404c93 in print_man_nodelist (man=0x149e2d0, n=0x382a510,
h=0x149e470) at man_html.c:156
#15 0x0000000000404fb5 in print_man_node (man=0x149e2d0, n=0x8a00e80,
h=0x149e470) at man_html.c:234
#16 0x0000000000404c93 in print_man_nodelist (man=0x149e2d0, n=0x8a00e80,
h=0x149e470) at man_html.c:156
#17 0x0000000000404ba9 in html_man (arg=0x149e470, man=0x149e2d0) at
man_html.c:134
#18 0x000000000041c176 in process (parser=0x149db80, outtype=OUTT_HTML,
formatter=0x149e470) at mandocd.c:271
#19 0x000000000041bfab in main (argc=1, argv=0x7fffa4b775e8) at
mandocd.c:214
On Sun, Mar 10, 2019 at 12:32 PM Ingo Schwarze <schwarze@usta.de> wrote:
> Hello,
>
> i just released mandoc-1.14.5. This is a regular maintenance
> release. As structural changes are quite limited, i expect it to
> be very stable, so all downstream systems are encouraged to upgrade
> from any earlier version.
>
> As usual, the release is available from
>
> http://mandoc.bsd.lv/snapshots/mandoc-1.14.5.tar.gz
>
> New features include:
>
> * The apropos(1) utility now accepts case-insensitive extended
> regular expressions by default, improving POSIX compliance
> (thanks to Wolfram Schneider for the suggestion).
> * The new man(1) -O tag[=term] output option opens a page at the
> definition of a term (thanks to Klemens Nanni for the suggestion).
> * The output from tbl(7) has been significantly improved in both
> the HTML and the UTF-8 output modes (thanks to Pali Rohar for
> many reports and suggestions).
> * Several syntax errors have been fixed in HTML output and the
> HTML output code quality has been further improved, in particular
> with respect to paragraphs, tagged lists, and tooltips
> (thanks to John Gardner for significant help).
> * Low-level roff(7) support has been further improved such that
> mandoc can now handle the manual pages of the groff package.
> * Many bugs have been fixed.
>
> For more details, see:
>
> http://mandoc.bsd.lv/NEWS
> http://mandoc.bsd.lv/ChangeLog
>
> For doing a manual installation or setting up a packaging system,
> please have a look at the INSTALL file in the tarball:
>
> http://mandoc.bsd.lv/INSTALL
>
> The release was tested on the following systems:
>
> * OpenBSD -current and -stable
> * FreeBSD 12
> * NetBSD -current
> * SmartOS (illumos)
> * Void Linux x86_64/glibc-2.29 and x86_64/musl-1.1.21
> * openSUSE Linux Tumbleweed
> * Debian Linux -oldstable
> * MacOS X 10.13.6 High Sierra
> * Oracle Solaris 11.2
> * SunOS 5.10 and 5.9
>
> As usual, many thanks to the various developers who provided patches,
> bug reports, advice, suggestions, and release testing! For a full
> list of contributors to this release, see:
>
> http://mandoc.bsd.lv/NEWS
>
> Yours,
> Ingo
> --
> To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
>
>
--
Best regards,
Michael
[-- Attachment #2: Type: text/html, Size: 6100 bytes --]
next prev parent reply other threads:[~2019-04-28 13:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-10 11:32 Ingo Schwarze
2019-04-28 13:24 ` Michael Stapelberg [this message]
2019-04-30 16:08 ` Ingo Schwarze
2019-05-25 15:22 ` Michael Stapelberg
2019-05-27 6:34 ` Michael Stapelberg
2019-06-01 19:16 ` Ingo Schwarze
2019-06-03 17:01 ` Michael Stapelberg
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='CANnVG6mFY1Tz1GdhtEZncqzsn9pR0VGaqj0oYQAKM=GkLxnc8g@mail.gmail.com' \
--to=stapelberg@debian.org \
--cc=discuss@mandoc.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).