Date: Tue, 24 Nov 2020 09:27:52 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 251329] textproc/asciidoc: extraneous carriage returns in output Message-ID: <bug-251329-7788-50i73ohX9c@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-251329-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-251329-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251329 Rainer Hurling <rhurlin@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rhurlin@FreeBSD.org --- Comment #1 from Rainer Hurling <rhurlin@FreeBSD.org> --- Created attachment 219917 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D219917&action= =3Dedit Alternative patch to the lineend problem with comms/fldigi Hi Diane, I just looked into the github sources and it seems, that this changes with DEFAULT_NEWLINE [1] were introduced, because Python 3 has universal newlines mode enabled. Eventually there is an alternive way to circumstance your build problem with comms/fldigi. There was another change in asciidoc.py [2], observed with Windows. Unix systems seem not to be affected, but let's try.=20 Could you please try my attached patch instead of yours, rebuild and reinst= all textproc/asciidoc, then try to build comms/fldigi and report back? Thanks in advance, Rainer (DH6BAG) [1] https://github.com/asciidoc/asciidoc-py3/commit/fba22e4d8e7adf414aca34272f6= b6938b6797cb6 [2] https://github.com/asciidoc/asciidoc-py3/commit/9b9dc0dba2f17bfd2c57c92dde2= 9b5ca4d3d46c7 --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-251329-7788-50i73ohX9c>