Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 16 Jun 2019 10:04:45 +0000
From:      bugzilla-noreply@freebsd.org
To:        python@FreeBSD.org
Subject:   [Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."
Message-ID:  <bug-237795-21822-Zf2zU01I1a@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-237795-21822@https.bugs.freebsd.org/bugzilla/>
References:  <bug-237795-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=3D237795

--- Comment #6 from Mikhail Teterin <mi@FreeBSD.org> ---
Gentlemen, what's happening? The problem's been analyzed... When building a
port (P0), that -- for whatever reason -- wants Python-N, the Python-versio=
n is
propagated to all dependencies.

When one of the dependencies (Pk) is incompatible with Python-N, you get th=
e=20
error...

In Marco's case, for example, P0 is math/gnumeric, which insists on Python-=
2.7
-- and Pk is devel/gobject-introspection, which wants 3.4+ or higher.

This is difficult to reproduce, because, once you have the dependency (such=
 as
gir) installed -- either through a direct "make install" or via a pre-built
package -- the dependents will build just fine... The problem strikes only,
when the dependency is built automatically -- with the requested Python-ver=
sion
passed from the dependent.

The bug is not with devel/gobject-introspection itself. This is a portmgr (=
or
python@ ?) issue -- there needs to be a way to distinguish between the two
cases:

 1. I'm going to use Python-N, and so must you, or else we'd be incompatibl=
e at
run-time.
 2. I need to use Python-N, but I don't care, what you're using.

--=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-237795-21822-Zf2zU01I1a>