From: Ingo Schwarze <schwarze@usta.de>
To: zplus@peers.community, kristaps@bsd.lv
Cc: discuss@mandoc.bsd.lv
Subject: Re: Fwd: mandoc debian release
Date: Thu, 8 Jun 2023 20:17:42 +0200 [thread overview]
Message-ID: <ZIIbRuk+yJtoAJhv@asta-kit.de> (raw)
In-Reply-To: <d0af9e9b-87f3-bab8-3571-8f39bb912079@bsd.lv>
Hi zplus,
> -------- Forwarded Message --------
> Subject: mandoc debian release
> Date: Sun, 04 Jun 2023 18:23:58 +0200
> From: zPlus <zplus@peers.community>
> To: kristaps@bsd.lv
>
> Hello Kristaps,
> there seems to be a problem with mandoc when converting this page[1]
> [1] stress-ng.1.en: https://paste.centos.org/view/raw/86b12296
I suspect this to be exactly the same bug as discussed here:
https://bugzilla.suse.com/show_bug.cgi?id=1209830
> which I got
> from Debian. Basically, halfway through it gets stuck in an infinite
> loop, no
> error, 100% CPU, just keeps spinning. I used the most recent version,
> 1.14.6,
> which I found un Debian testing and unstable.
> I asked for help on IRC in #openbsd and they confirmed this is fixed in
> "yesterday's -current" version.
> They pointed me to your website, and suggested that I write to you
> asking for a
> new release. So this is the reason of my email, could you please make a new
> release of mandoc such that Debian can pick up the new changes too?
> Thank you a lot!
Eventually, we will certainly roll a new mandoc release, but i can't
give a time estimate yet when that will happen.
In the meantime, if you want to fix the Debian port, can you simply
include this patch:
https://cvsweb.openbsd.org/src/usr.bin/mandoc/out.c.diff?r1=1.54&r2=1.55
into the Debian port here:
https://salsa.debian.org/debian/mdocml/-/tree/master/debian/patches
Does that work for you, as a stopgap measure?
Yours,
Ingo
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
prev parent reply other threads:[~2023-06-08 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <47b8879324b03ab1700d14c2aaff93f822b3e660.camel@peers.community>
2023-06-08 17:54 ` Kristaps Dzonsons
2023-06-08 18:17 ` Ingo Schwarze [this message]
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=ZIIbRuk+yJtoAJhv@asta-kit.de \
--to=schwarze@usta.de \
--cc=discuss@mandoc.bsd.lv \
--cc=kristaps@bsd.lv \
--cc=zplus@peers.community \
/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).