[Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."

2019-08-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795

Ting-Wei Lan  changed:

   What|Removed |Added

 CC||lant...@gmail.com

--- Comment #14 from Ting-Wei Lan  ---
(In reply to Walter Schwarzenfeld from comment #13)
What did you mean by posting this line? It doesn't look relevant to the issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."

2019-08-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795

--- Comment #13 from Walter Schwarzenfeld  ---
/usr/ports/MOVED:
lang/python34|lang/python36|2018-12-18|Has expired: Fails to build with recent
OpenSSL

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."

2019-08-14 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795

Walter Schwarzenfeld  changed:

   What|Removed |Added

 CC||w.schwarzenf...@utanet.at
   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2337
   ||23

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."

2019-07-04 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795

Alfredo Dal'Ava Júnior  changed:

   What|Removed |Added

 CC||alfredo.jun...@eldorado.org
   ||.br, lup...@freebsd.org

--- Comment #12 from Alfredo Dal'Ava Júnior  ---
I reproduce the same issue on powerpc64 using a clean FreeBSD 13/current:

# cd /usr/ports/www/firefox && make

It crashed with "needs Python 3.4 at least, but 2.7 was specified." on
'devel/gobject-introspection'

# cd /usr/ports/devel/gobject-introspection && make

It crashed with "needs Python 3.4 at least, but 2.7 was specified." now on
'devel/meson'


I did workaround this by doing:


# cd /usr/ports/devel/meson && make && make install
# cd /usr/ports/devel/gobject-introspection && make && make install
# cd /usr/ports/www/firefox && make

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."

2019-06-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795

tak...@takeda.tk changed:

   What|Removed |Added

 CC||tak...@takeda.tk

--- Comment #11 from tak...@takeda.tk ---
Similar thing is happening with meson when used as a build dependency for
deluge. We will have more of these occurrences as 2.7 is becoming EOL and
packages are dropping support for it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."

2019-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795

Kubilay Kocak  changed:

   What|Removed |Added

   See Also||https://bugs.freebsd.org/bu
   ||gzilla/show_bug.cgi?id=2386
   ||09

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."

2019-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795

Kubilay Kocak  changed:

   What|Removed |Added

 Status|Closed  |Open
   Assignee|ports-b...@freebsd.org  |ko...@freebsd.org
 Resolution|Overcome By Events  |---
 CC||gn...@freebsd.org
  Flags|maintainer-feedback?(gnome@ |
   |FreeBSD.org)|

--- Comment #10 from Kubilay Kocak  ---
I'll take this for now, and will re-summarise/classify accordingly.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."

2019-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795

--- Comment #9 from Kubilay Kocak  ---
(In reply to Mikhail Teterin from comment #8)

Sure, got it. Thanks for helping me get there. And the dependency is satisfied
after manual installation because it's a binary/filename *_DEPENDS, not a
package type.

So for case (2) of your two types, this type, one would need to be able to,
minimally at least, based on what we know now:

a) more finely declare the dependency kind (so as not to propagate for it)
b) declare it on a per-dependency basis (have it not apply to any other things
where it may not apply)

Independent to the feasibility, something like that is going to require some
very clear and precise "spec'ing" out before it goes to portmgr, as I suspect
it will need to. 

This is because I don't see this as being a bug, but rather a feature to more
finely control (perhaps more precisely: ability to constrain) python version
propagation, to take into account how a dependency is used.

It might be worth us chewing the fat on IRC (#freebsd-python) and coming up
with an unambiguous and lightweight "PEP" for it. Who knows, we may even be
able to come up with a hack^W workaround in the short term, or other
alternatives

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."

2019-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795

--- Comment #8 from Mikhail Teterin  ---
(In reply to Kubilay Kocak from comment #7)
> please elaborate with an example of 'installing it manually, not as a
> automatic, depends', that fixes *this* issue, which is:
>
> a) a port requiring one specific version (eg: only 2.7)
> b) cannot be built when one of its dependencies (eg: gobject-introspection)
> c) requires a version that does not overlap with its own (eg: 3.4+)

The version of Python, that's used by a dependency, may not actually matter,
when the dependency is not itself a Python-package -- that is, is not used by
the dependent as "import foo". Or, when Python is merely a BUILD-dependency for
the dependency... (Both of these examples fall under item 2. in my Comment #6.)

This is why, after you install gir manually -- allowing it to use whatever
version it wants -- build works.

Things break, when the build of gir is invoked automatically by the build of a
depending port, because in this case the Python-version is EXPLICITLY
PRESCRIBED (by adding PYTHON_VERSION to the environment, I think)...

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."

2019-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795

--- Comment #7 from Kubilay Kocak  ---
I have no idea how the situation ended up resolving itself, but being provided
that information, or an opportunity to obtain it may have been enlightening.

As far as I can see, the gnumeric case is a case of wrong dependencies.

gnumeric cannot logically *only* support 2.7, and have a set of dependencies
that *don't also* support 2.7.

Either gnumeric is incorrectly constraining itself to 2.7 when it supports 3.x,
or gobject-introspection is incorrectly constrained to 3.4+, when it also
supports 2.7, or some dependencies are spurious.

math/gnumeric (2.7)
`-- devel/pygobject3-common (no python version-spec, any version)
`-- devel/gobject-introspection (3.4+)

And I don't see how 'installing it manually' can fix *this* issue.

You cant install py36-gobject-introspection and have it be a satisfactory
dependency for py27-pygobject3-common

You also cant install py36-pygobject3-common to get py36-gobject-introspection
and have either of those satisfy math/gnumeric which only ever wants/supports
(at present) 2.7.

If I'm misunderstanding what you meant, please elaborate with an example of
'installing it manually, not as a automatic, depends', that fixes *this* issue,
which is:

 a) a port requiring one specific version (eg: only 2.7)
 b) cannot be built when one of its dependencies (eg: gobject-introspection)
 c) requires a version that does not overlap with its own (eg: 3.4+)

But I can't see how that's possible, as making (a)(b)(c) work is precluded
fundamentally just by the the Python ecosystem works.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."

2019-06-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795

--- Comment #6 from Mikhail Teterin  ---
Gentlemen, what's happening? The problem's been analyzed... When building a
port (P0), that -- for whatever reason -- wants Python-N, the Python-version is
propagated to all dependencies.

When one of the dependencies (Pk) is incompatible with Python-N, you get the 
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-version
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 incompatible at
run-time.
 2. I need to use Python-N, but I don't care, what you're using.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."

2019-06-15 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795

Marco Beishuizen  changed:

   What|Removed |Added

 Status|Open|Closed
 Resolution|--- |Overcome By Events

--- Comment #5 from Marco Beishuizen  ---
I need closing this one again because the bug seems to have disappeared.

I did notice that the bug doesn't appear when using portmaster. Portmaster is
builing devel/bison before building gobject-introspection, and then the bug
doesn't happen. Using portupgrade or doing a make install directly was
triggering the bug because devel/bison wasn't build first for some reason.

Trying to reproduce the bug today failed: bison does build before
gobject-introspection now, and the bug disappears.

My uname -a:
FreeBSD yokozuna 12.0-STABLE FreeBSD 12.0-STABLE r343805 YOKOZUNA  amd64

My make.conf:
CPUTYPE?=nocona
KERNCONF=YOKOZUNA
DISTDIR=/var/ports/distfiles
PACKAGES=/var/ports/packages
OPTIONS_UNSET=GNOME GCONF DCONF GSETTINGS CUPS AVAHI HAL ALSA PULSEAUDIO
WAYLAND COLORD
OPTIONS_SET=LPR NVIDIA NVTHREADS SNDIO OSS ZTS
PKG_NOCOMPRESS=1
WITH_MPM=event
#DEVELOPER=yes  
#BATCH=yes  
#DISABLE_VULNERABILITIES=yes
#FORCE_PKG_REGISTER=yes 
DEFAULT_VERSIONS+= mysql=8.0 pgsql=11 emacs=nox lua=5.3
MESA_LLVM_VER=80
.if ${.CURDIR:M*/editors/emacs*}
FLAVOR?=nox
.endif

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"


[Bug 237795] devel/gobject-introspection: "needs Python 3.4 at least, but 2.7 was specified."

2019-06-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795

Kubilay Kocak  changed:

   What|Removed |Added

   Keywords||needs-qa
 CC|ports-b...@freebsd.org  |ko...@freebsd.org,
   ||pyt...@freebsd.org
  Component|Ports Framework |Individual Port(s)
   Assignee|port...@freebsd.org |ports-b...@freebsd.org

--- Comment #4 from Kubilay Kocak  ---
(In reply to Marco Beishuizen from comment #0)

Can you please provide more information, including:

- Exact FreeBSD version (uname -a output)
- pkg version -v output (as an attachment)
- /etc/make.conf contents (as an attachment)
- Full build log, including portupgrade/portmaster command (as an attachment)

^Triage: Leave this as an individual port issue until (if) isolated to a
framework issue.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"