Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Dec 2019 02:48:51 +0000
From:      bugzilla-noreply@freebsd.org
To:        python@FreeBSD.org
Subject:   [Bug 242842] security/suricata: Fails to build (5.0.0 PV=2) with Python 3.x
Message-ID:  <bug-242842-21822-84MZuZgdNw@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-242842-21822@https.bugs.freebsd.org/bugzilla/>
References:  <bug-242842-21822@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=3D242842

Kubilay Kocak <koobs@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|New                         |Open
           Severity|Affects Only Me             |Affects Some People
            Summary|security/suricata fails to  |security/suricata: Fails to
                   |compile (5.0.0 PV=3D2)        |build (5.0.0 PV=3D2) with
                   |                            |Python 3.x
                 CC|                            |koobs@FreeBSD.org,
                   |                            |python@FreeBSD.org
           Keywords|                            |needs-qa

--- Comment #3 from Kubilay Kocak <koobs@FreeBSD.org> ---
https://sourceforge.net/p/docutils/mailman/docutils-develop/thread/qk0aso$7=
48n$1@blaine.gmane.org/

In particular, bits marked "py3: Replace 'ur' prefix":

https://sourceforge.net/p/docutils/mailman/message/36748204/

Committed upstream as part of the larger py3 patchset in:

https://sourceforge.net/p/docutils/code/8366/

I've run docutil' test suite against all Python 3 versions (3.5-3.8) and
they fail with many Python 3 errors (including for 'ur' prefixes)

A possibly naive/premature resolution to this be to *correctly* declare the
Python versions textproc/docutils supports (limiting it to Python 2.7, as is
its current version support), which should have been the case in the first
place, *but* this may have implications for ports that don't otherwise
use/import/invoke sphinx at runtime, and don't particularly care what versi=
on
of Python sphinx was built with.

In the above sense, this is similar to bug 237795

@Reporter, could you attach a bull log of the suricata failure please. It w=
ould
be interesting to see where/how/when sphinx is being invoked and in what ex=
act
form

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242842-21822-84MZuZgdNw>