> > > >> hello - on current i found myself in a situation where python37 was
> > > >> unable to import ssl:
> > > >>
> > > >> $ python3.7
> > > >> Python 3.7.7 (default, May 9 2020, 01:37:42)
> > > >> [Clang 1
where python37 was
> > >> unable to import ssl:
> > >>
> > >> $ python3.7
> > >> Python 3.7.7 (default, May 9 2020, 01:37:42)
> > >> [Clang 10.0.0 (g...@github.com:llvm/llvm-project.git
> > >> llvmorg-10.0.0-0-gd32170d
On Tue, May 26, 2020 at 11:09 PM Stefan Eßer wrote:
> Am 27.05.20 um 04:24 schrieb Jan Beich:
> > Pete Wright writes:
> >
> >> hello - on current i found myself in a situation where python37 was
> >> unable to import ssl:
> >>
> >> $ python3.
Am 27.05.20 um 04:24 schrieb Jan Beich:
> Pete Wright writes:
>
>> hello - on current i found myself in a situation where python37 was
>> unable to import ssl:
>>
>> $ python3.7
>> Python 3.7.7 (default, May 9 2020, 01:37:42)
>> [Clang 10.0.0 (g...@g
On 5/26/20 5:24 PM, Jan Beich wrote:
Pete Wright writes:
hello - on current i found myself in a situation where python37 was
unable to import ssl:
$ python3.7
Python 3.7.7 (default, May 9 2020, 01:37:42)
[Clang 10.0.0 (g...@github.com:llvm/llvm-project.git
llvmorg-10.0.0-0-gd32170dbd on
Pete Wright writes:
> hello - on current i found myself in a situation where python37 was
> unable to import ssl:
>
> $ python3.7
> Python 3.7.7 (default, May 9 2020, 01:37:42)
> [Clang 10.0.0 (g...@github.com:llvm/llvm-project.git
> llvmorg-10.0.0-0-gd32170dbd on f
hello - on current i found myself in a situation where python37 was
unable to import ssl:
$ python3.7
Python 3.7.7 (default, May 9 2020, 01:37:42)
[Clang 10.0.0 (g...@github.com:llvm/llvm-project.git
llvmorg-10.0.0-0-gd32170dbd on freebsd13
Type "help", "copyright", &
On Tue, 28 Apr 2020 02:10:51 -0600
"@lbutlr" wrote:
> On 27 Apr 2020, at 17:32, ajtiM via freebsd-ports
> wrote:
> > qt5-webengine
>
> There is py-qt5-webengine which seems to want py37
>
And what is a point?
www/qt5-webengine has in Makefile python:27. If you
On 27.04.2020 21:48, Yasuhito FUTATSUKI wrote:
>> I don't want to add support for non-standard (not pre-generated) bindings
>> to port, to be honest. SWIG is major pain in the ass, and python2 will be
>> deprecated at the end of the year anyway.
>>
>> Update of subversion-lts port is other m
On 27 Apr 2020, at 17:32, ajtiM via freebsd-ports
wrote:
> qt5-webengine
There is py-qt5-webengine which seems to want py37
--
"Remember -- that which does not kill us can only make us stronger."
"And that which *does* kill us leaves us *dead*!”
_
I found that qt5-webengine needs Python 2.7:
Build dependencies:
bison : devel/bison
ninja : devel/ninja
yasm : devel/yasm
input.h : devel/evdev-proto
videodev2.h : multimedia/v4l_compat
gperf : devel/gperf
python2.7 : lang/python27
LTS, BOTH ports will be updated. And
>>> till 1.15.0 these ports will be equivalent!
>>
>> If we want to support application depends on Python 2 bindings only
>> for a while, please consider to leave 1.10.x. As far as I understand,
>> 1.10.x will support Python 2 its E
l be equivalent!
>
> If we want to support application depends on Python 2 bindings only
> for a while, please consider to leave 1.10.x. As far as I understand,
> 1.10.x will support Python 2 its EOL, however 1.14.x may drop it
> before EOL of 1.10.x, if there will exist good reas
On 24.04.2020 0:18, Yasuhito FUTATSUKI wrote:
Problem is, python2 will be removed from ports (relatively) soon, so support
python2 bindings in ports will be impossible after 2020-12-31 anyway...
> * Python application using Subversion SWIG Python bindings also need to
> modify to s
I have submitted a bug, bugzilla/show_bug.cgi?id=245799
<https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245799>, to update
math/gnumeric to run with python3. It's a bit odd because the current
version in ports builds and runs with either python 2 or 3 by default, but
the FreeBSD po
On Sat, 25 Apr 2020 16:21:25 -0700 (PDT)
Roger Marquis wrote:
> Kurt Jaeger wrote:
> > I prepared a patch to build lyx without the 2.7 restriction. The
> > patch needs a run-test, can you test and report back ?
>
> Has anyone enumerated the ports and applications which don
Kurt Jaeger wrote:
I prepared a patch to build lyx without the 2.7 restriction. The
patch needs a run-test, can you test and report back ?
Has anyone enumerated the ports and applications which don't work with
python{,2,2.7} symlinked from pypy? Mailman seems fine but fail2ban
does not
On Fri, 24 Apr 2020 14:16:15 +0200
Kurt Jaeger wrote:
> Hi!
>
> > > > I clean almost everything except print/lyx which I am using and
> > > > I like it (with latex-beamer). I try to build with Python 3.7
> > > > but not success. [...]
>
Hi!
> > > I clean almost everything except print/lyx which I am using and I
> > > like it (with latex-beamer). I try to build with Python 3.7 but not
> > > success. [...]
> It was solved long time ago but we have:
>
> Build dependencies:
>
> up
e it (with latex-beamer). I try to build with Python 3.7 but not
> > > success. I do not now if I am one of the "rare" user or is port
> > > dead.
> >
> > The port is up to date with version 2.3.4.2.
> >
> > Can you try to ask upstream ? In their bu
I posted it from wrong email address so I repost ...
--- Forwarded Message
To: l...@freebsd.org
Cc: d...@langille.org, freebsd-ports@freebsd.org, futat...@yf.bsdclub.org
Subject: Re: FreeBSD Port: devel/py-subversion - Python 3 flavor?
In-Reply-To: Your message of "Thu, 23 Apr 2020 18:
One more post ...
--- Forwarded Message
To: l...@freebsd.org
Cc: d...@langille.org, freebsd-ports@freebsd.org, futat...@yf.bsdclub.org
Subject: Re: FreeBSD Port: devel/py-subversion - Python 3 flavor?
In-Reply-To: Your message of "Thu, 23 Apr 2020 23:20:41
gt; So long as devel/py-subversion soon supports Python 3, I'm happy.
As soon as 1.14.0 will be released (I think it is matter of days, maybe
week).
--
Best regards,
Levmailto:l...@freebsd.org
___
freebsd-ports@
On Thu, 23 Apr 2020 21:46:15 +0200
Kurt Jaeger wrote:
> Hi!
>
> > I clean almost everything except print/lyx which I am using and I
> > like it (with latex-beamer). I try to build with Python 3.7 but not
> > success. I do not now if I am one of the "rare" user
On Thu, 23 Apr 2020 21:46:15 +0200
Kurt Jaeger wrote:
> Hi!
>
> > I clean almost everything except print/lyx which I am using and I
> > like it (with latex-beamer). I try to build with Python 3.7 but not
> > success. I do not now if I am one of the "rare" user
Hi!
> I clean almost everything except print/lyx which I am using and I like
> it (with latex-beamer). I try to build with Python 3.7 but not success.
> I do not now if I am one of the "rare" user or is port dead.
The port is up to date with version 2.3.4.2.
Can you try t
I clean almost everything except print/lyx which I am using and I like
it (with latex-beamer). I try to build with Python 3.7 but not success.
I do not now if I am one of the "rare" user or is port dead.
Thank you.
--
Ernst Lubitsch’s Ninotchka:
“‘Waiter! A cup of coffee without cre
so BOTH ports versions
> will be 1.14 with python3 support!
I must misunderstand completely.
So long as devel/py-subversion soon supports Python 3, I'm happy.
>
> > This sounds like two ports are required new & legacy, instead of flavors.
>
> > On Thu, Apr 23, 202
Hello Dan,
Thursday, April 23, 2020, 7:03:10 PM, you wrote:
Huh. There are no problems, as we now have "current" subversion and "lts"
one, version 1.9 was removed. And 1.14.x will be LTS, so BOTH ports versions
will be 1.14 with python3 support!
> This sounds like two ports are required new & l
ns of subversion in ports tree, and
> I'm not sure to do.
>
> > Hello Lev,
> >
> > Do you know of anything preventing devel/py-subversion from working with
> > Python 3?
> >
> > I ask because devel/py-subversion at present requires Python 2.7 whic
On 23.04.2020 17:43, Dan Langille wrote:
subversion 1.14.0 which is RC2 now will be python3 only.
But we are used to have old versions of subversion in ports tree, and I'm not
sure to do.
> Hello Lev,
>
> Do you know of anything preventing devel/py-subversion from working wi
On Thu, Apr 23, 2020 at 9:43 AM Dan Langille wrote:
>
> Hello Lev,
>
> Do you know of anything preventing devel/py-subversion from working with
> Python 3?
>
> I ask because devel/py-subversion at present requires Python 2.7 which is
> past EOL.
>
> While I was ty
Hello Lev,
Do you know of anything preventing devel/py-subversion from working with Python
3?
I ask because devel/py-subversion at present requires Python 2.7 which is past
EOL.
While I was typing this, I thought: I should just try it first.
I failed:
https://services.unixathome.org
Le dim. 19 avr. 20 à 11:24:30 +0200, Thierry Thomas
écrivait :
> > Hmpf - now I _had_ to fix FreeCAD - that thing has it's own dependency
> > on vtk, and we cannot have vtk6 and vtk8 at the same time.
>
> Thanks, I did not know that.
Christoph,
Unfortunately, I had to switch back to VTK-6.1 b
On 18/04/2020 11:57, D'Arcy Cain wrote:
> I tried building lilypond with python2.7 removed from USES but its
> configure script failed due to Python < 3.0. I couldn't find any
> discussion about upgrading the version of Python but WikipediA says that
> it has 120,000 line
Am 19.04.20 um 00:25 schrieb D'Arcy Cain:
> On 2020-04-18 17:23, Matthias Andree wrote:
>> Am 18.04.20 um 18:40 schrieb D'Arcy Cain:
>>> On 2020-04-18 10:18, ajtiM via freebsd-ports wrote:
BTW, I do not know why some apps need llvm60 still:
>>> I really wish there was only one llvm. It's one
On Sun, 19 Apr 2020 09:54:27 -0700
Kevin Oberman wrote:
> If you actually use inkscape, can you try inkscape with python37 an
> confirm whether or not it works? My guess is that it does not, but
> it does run and at least works to some degree. Maybe everything
> works. (Hope springs eternal.)
>
inkscape is being ported to Python3, so one has to wait...
On Mon, 20 Apr 2020, 00:55 Kevin Oberman, wrote:
> If you actually use inkscape, can you try inkscape with python37 an confirm
> whether or not it works? My guess is that it does not, but it does run and
> at least works to some degree.
If you actually use inkscape, can you try inkscape with python37 an confirm
whether or not it works? My guess is that it does not, but it does run and
at least works to some degree. Maybe everything works. (Hope springs
eternal.)
I suspect you know this, but you can just edit the Makefile to remo
And how and when will be solved Inkscape which is part of the GNOME
group:
Build dependencies:
concept_check.hpp : devel/boost-libs
cmake : devel/cmake
ninja : devel/ninja
update-desktop-database : devel/desktop-file-utils
gtk-update-icon-cache : graphics/g
On Sun, 19 Apr 2020 01:57:36 +0200, Dima Pasechnik
wrote:
scons ought to be updated to version 3 (the latest is 3.1.2), and
supports both python 2.7+ and 3.5+
Scons in ports is 3.1.1. This can compile and run with python 2 and 3. But
our USES=scons framework does not know how to
tly states in the build
that
2.x is required and it is not yet compatible with python3+. It appears
that
the default is to simply build gnumeric without Python bindings in which
case python2 is not required, but the port makes use of it, so it
probably
needs at least some massaging.
The
Le dim. 19 avr. 20 à 0:57:29 +0200, Christoph Moench-Tegeder
écrivait :
> Hmpf - now I _had_ to fix FreeCAD - that thing has it's own dependency
> on vtk, and we cannot have vtk6 and vtk8 at the same time.
Thanks, I did not know that.
> > Looks like vtk8 need some love... building as I write
Le sam. 18 avr. 20 à 22:37:19 +0200, Loïc Bartoletti
écrivait :
> > I just committed a switch to VTK-8.1.
> Salut,
>
> I'm working on a port which requires opencascade.
>
> Maybe I'm wrong, but just repalce vtk6 to vtk8 is not enough. Vtk8 does not
>
## Dima Pasechnik (dimpase+free...@gmail.com):
> But I don't see a problem in keeping Python 2.7 available for some
> time in FreeBSD - it just should stop being default one.
Python 2.7 hasn't been the default for quite exactly one year:
: r498529 | antoine | 2019-04-10 07:47:2
scons ought to be updated to version 3 (the latest is 3.1.2), and
supports both python 2.7+ and 3.5+
lilypond is another story - noone seems to have bitten the bullet and
ported it to Python 3.
But I don't see a problem in keeping Python 2.7 available for some
time in FreeBSD - it just s
tible with python3+. It appears that
the default is to simply build gnumeric without Python bindings in which
case python2 is not required, but the port makes use of it, so it probably
needs at least some massaging.
The big one is scons. It is required by virtualbox-ose, and that is rather
important
## Christoph Moench-Tegeder (c...@burggraben.net):
> > > Again, vtk6...
> > I just committed a switch to VTK-8.1.
>
> Cool!
Hmpf - now I _had_ to fix FreeCAD - that thing has it's own dependency
on vtk, and we cannot have vtk6 and vtk8 at the same time.
> Looks like vtk8 need some love... build
On Sat, 18 Apr 2020 20:24:21 +0200
Christoph Moench-Tegeder wrote:
> ## ajtiM via freebsd-ports (freebsd-ports@freebsd.org):
>
> > > asterisk16: 16.9.0
>
> That's surprising - asterisk16 with somewhat usual OPTIONS does not
> have a direct python dependency
On 2020-04-18 17:23, Matthias Andree wrote:
> Am 18.04.20 um 18:40 schrieb D'Arcy Cain:
>> On 2020-04-18 10:18, ajtiM via freebsd-ports wrote:
>>> BTW, I do not know why some apps need llvm60 still:
>> I really wish there was only one llvm. It's one of those things that
>> can take days to build.
Am 18.04.20 um 18:40 schrieb D'Arcy Cain:
> On 2020-04-18 10:18, ajtiM via freebsd-ports wrote:
>> BTW, I do not know why some apps need llvm60 still:
> I really wish there was only one llvm. It's one of those things that
> can take days to build. A minor upgrade can trigger multiple rebuilds.
>
On 2020-04-18 13:24, Christoph Moench-Tegeder wrote:
>>> asterisk16: 16.9.0
>
> That's surprising - asterisk16 with somewhat usual OPTIONS does not
> have a direct python dependency - I'd guess you're seeing an indirect
> dependency via newt (devel
wrong, but just repalce vtk6 to vtk8 is not enough. Vtk8 does
not have python, and also requires qt5. According to my tests, you
should add to opencascade
USES= qt:5 qmake
USE_QT= buildtools_build
But i'm still working on it.
Regards.
Loïc
__
## Thierry Thomas (thie...@freebsd.org):
> > Again, vtk6...
>
> I just committed a switch to VTK-8.1.
Cool!
Looks like vtk8 need some love... building as I write.
> But there is also inkspace (if the option DOXYGEN is selected). It
> should be upgraded to a newer version t
Le sam. 18 avr. 20 à 20:24:21 +0200, Christoph Moench-Tegeder
écrivait :
> > opencascade: 7.4.0_2
>
> Again, vtk6...
I just committed a switch to VTK-8.1.
But there is also inkspace (if the option DOXYGEN is selected). It
should be upgraded to a newer version to avoid Python
On Sat, 18 Apr 2020, D'Arcy Cain wrote:
As for mailman, it looks like we only need to upgrade to a current
version. The site says that 3.x uses Python 3. Requires it in fact.
Mailman 3 is a completely different system compared to Mailman 2.
CKAN is not in FreeBSD ports but is an ex
## ajtiM via freebsd-ports (freebsd-ports@freebsd.org):
> > asterisk16: 16.9.0
That's surprising - asterisk16 with somewhat usual OPTIONS does not
have a direct python dependency - I'd guess you're seeing an indirect
dependency via newt (devel/newt) which has PYTHO
On Fri, 17 Apr 2020 14:11:11 +0200, Dewayne Geraghty
wrote:
Its very confusing building ports at the moment. At
https://www.python.org/
there is a release candidate for 2.7.18, while our python 2.7 has been
marked as deprecated with an expiration date. Can the Expiration Date of
2020-12
On 2020-04-18 10:18, ajtiM via freebsd-ports wrote:
> BTW, I do not know why some apps need llvm60 still:
I really wish there was only one llvm. It's one of those things that
can take days to build. A minor upgrade can trigger multiple rebuilds.
In my case only llvm80 and llvm90 but still.
--
On Sat, 18 Apr 2020 04:57:32 -0500
D'Arcy Cain wrote:
> On 2020-04-18 04:06, andrew clarke wrote:
> > Out of interest I ran "pkg del python27" on my FreeBSD machine just
> > to see what would break. Conspicuous was devel/mercurial:
>
> I did the same thing. Out of 19 packages to be deleted here
rest are mainly dependencies for these
four.
asterisk16: 16.9.0
freeradius3: 3.0.20
lilypond: 2.18.2_10
mailman: 2.1.29_6
I was surprised to find Asterisk in that list. It appears to be due to
a dependency on net-snmp. I am rebuilding with Python bindings removed
from
On 2020-04-18 09:34:39, Matthew Seaman (matt...@freebsd.org) wrote:
> On 18/04/2020 03:19, Robert Huff wrote:
> > a) according to the Makefile, is it possible to build this with
> > python-37? (Or even -36?)
>
> If the Makefile for the port says:
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 18 Apr 2020 09:34:39 +0100
Matthew Seaman wrote:
> There are very few things still in the ports that use python and that
> only work with python-2.7. So, yes, everything can be upgraded to
> python-3. Whether that works entirely
On 18/04/2020 03:19, Robert Huff wrote:
> a) according to the Makefile, is it possible to build this with
> python-37? (Or even -36?)
If the Makefile for the port says:
USES= python:27
then the port is for python-2.7.x only. All other python ports will
support pyth
George Mitchell writes:
> >> But basically, expect all python 2.x using ports to go away, unless
> >> they get fixed to use python 3.x, or no python at all.
> >
> >Is there a method whereby - given a list of installed ports using
> > python 2
On Sat, Apr 18, 2020 at 8:20 AM Robert Huff wrote:
>
>
> Dimitry Andric writes:
>
> > But basically, expect all python 2.x using ports to go away, unless
> > they get fixed to use python 3.x, or no python at all.
>
> Is there a method whereby - given a
On 2020-04-17 20:19, Robert Huff wrote:
>
> Dimitry Andric writes:
>
>> But basically, expect all python 2.x using ports to go away, unless
>> they get fixed to use python 3.x, or no python at all.
>
> Is there a method whereby - given a list of installed p
Dimitry Andric writes:
> But basically, expect all python 2.x using ports to go away, unless
> they get fixed to use python 3.x, or no python at all.
Is there a method whereby - given a list of installed ports using
python 2 - one might determine which can and which can
On 17 Apr 2020, at 14:11, Dewayne Geraghty wrote:
>
> Its very confusing building ports at the moment. At https://www.python.org/
> there is a release candidate for 2.7.18, while our python 2.7 has been
> marked as deprecated with an expiration date. Can the Expiration Date of
>
Its very confusing building ports at the moment. At https://www.python.org/
there is a release candidate for 2.7.18, while our python 2.7 has been
marked as deprecated with an expiration date. Can the Expiration Date of
2020-12-31 be retracted?
It appears that devel/scons, at least, requires
On 04/04/20 11:41, Torfinn Ingolfsen wrote:
> FWIW, I only use basic functionality (I use the content server to
> transfer books to my readers). I tested the port built with python3.
> Everything works so far - I haven't found any issues.
>
> BTW, thanks for all the good work you're doing.
>
Hi
FWIW, I only use basic functionality (I use the content server to
transfer books to my readers). I tested the port built with python3.
Everything works so far - I haven't found any issues.
BTW, thanks for all the good work you're doing.
--
Regards,
Torfinn Ingolfsen
Hello!
I have committed just now changes to the calibre port to add an option
to build it against python 3. (r528772)
As you all know python 2 is on it's way out and all software must be
migrated, or removed from the ports tree.
You may also know that calibre porting to python 3 is
make.conf(5) except
> > DEVELOPER=true
> > But I get messages regarding python versions like:
> > llvm80-8.0.1_3 needs Python 3.6 at least, but 2.7 was specified.
> > But I make no demands on versions.
> > What causes this, and how can I stop it. :)
>
> Is you
On Thu, 27 Feb 2020 19:52:23 + Brooks Davis bro...@freebsd.org said
On Thu, Feb 27, 2020 at 08:44:59AM -0800, Chris wrote:
> I'm testing modifications of ports I maintain in
> a jail. I have nothing in make.conf(5) except
> DEVELOPER=true
> But I get messages regarding pyt
On Thu, Feb 27, 2020 at 07:52:23PM +, Brooks Davis wrote:
> On Thu, Feb 27, 2020 at 08:44:59AM -0800, Chris wrote:
> > I'm testing modifications of ports I maintain in
> > a jail. I have nothing in make.conf(5) except
> > DEVELOPER=true
> > But I get message
On Thu, Feb 27, 2020 at 08:44:59AM -0800, Chris wrote:
> I'm testing modifications of ports I maintain in
> a jail. I have nothing in make.conf(5) except
> DEVELOPER=true
> But I get messages regarding python versions like:
> llvm80-8.0.1_3 needs Python 3.6 at least, but 2.7 wa
I'm testing modifications of ports I maintain in
a jail. I have nothing in make.conf(5) except
DEVELOPER=true
But I get messages regarding python versions like:
llvm80-8.0.1_3 needs Python 3.6 at least, but 2.7 was specified.
But I make no demands on versions.
What causes this, and how can I
conto di Kubilay Kocak
Inviato: martedì 25 febbraio 2020 09:35
A: Alessandro Sagratini ; freebsd-ports@freebsd.org
Cc: python
Oggetto: Re: porting a python package with specific libraries versions as
dependency
On 25/02/2020 7:22 pm, Alessandro Sagratini wrote:
> Hello all,
> I was disc
On 25/02/2020 7:22 pm, Alessandro Sagratini wrote:
Hello all,
I was discussing [1] about porting oci-cli to ports tree. It is a python package, that
should not be a big deal, though, investigating a bit more "requires" field in
setup.py [2], I noticed it depends on specific python
Hello all,
I was discussing [1] about porting oci-cli to ports tree. It is a python
package, that should not be a big deal, though, investigating a bit more
"requires" field in setup.py [2], I noticed it depends on specific python
libraries, for example oci-sdk 2.10.5, configparser 3.
On 2019-12-30 03:26, Kubilay Kocak wrote:
Thanks to all that replied.
Especially the link to Python Ports Policy & Guidelines/Tips was very
useful, as I hadn't found this myself :(
I tried to follow all your suggestions, but I'm having some problems
with it...
Using
On 30/12/2019 4:54 am, Andrea Venturoli wrote:
Hi Andrea, nice first job on a Python port :)
# $FreeBSD$
PORTNAME= IMAPClient
Lowercase this PORTNAME
PORTVERSION= 2.1.0
CATEGORIES= mail python
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
MAINTAINER= m...@netfence.it
COMMENT
Andrea Venturoli wrote:
> I've got a system where I had to install a few Python libraries with
> pip, but I don't like this, since pkg info will not list them.
>
> Thus I'm trying to port them, but I never ported Python libraries
> before; so, before I submit my work
Hi!
> I've got a system where I had to install a few Python libraries with pip,
> but I don't like this, since pkg info will not list them.
>
> Thus I'm trying to port them, but I never ported Python libraries before;
> so, before I submit my work, I thought I'
Hello.
I've got a system where I had to install a few Python libraries with
pip, but I don't like this, since pkg info will not list them.
Thus I'm trying to port them, but I never ported Python libraries
before; so, before I submit my work, I thought I'd ask if someo
et a 2-line
patch to the python committed, and AFAICT, the commit was done
by portmgr instead python@.
https://lists.freebsd.org/pipermail/freebsd-ports/2019-December/117300.html
https://lists.freebsd.org/pipermail/svn-ports-all/2019-December/23569
ort framework quality, something that always seemed to linger in
> the background for the last couple of years and now it's finally here.
>
> And yes, lang/rust was one recent example that has python:3.3+ now and
> fails to build somewhere down the dependency chain.
>
>
> Chee
need to use Poudriere just to have a chance at building
ports we're at the point where Poudriere itself is becoming problematic
for port framework quality, something that always seemed to linger in
the background for the last couple of years and now it's finally here.
And yes, lang/rust was
On 12/24/19 5:56 PM, w.schwarzenfeld wrote:
> At least a workaround (maybe the sollutiion):
>
>
> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209881&action=diff
Another workaround if you don't want to modify files in the repo is to
simply go into the problem folder, /usr/ports/graphics/g
At least a workaround (maybe the sollutiion):
https://bugs.freebsd.org/bugzilla/attachment.cgi?id=209881&action=diff
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "
=> But maybe I have something strange in my setup, and no-one else
experiences it.
No it is a known issue.
See:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237795
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/lis
When I try to build certain ports, I get the error message "XXX needs
Python 3.4 at least, but 2.7 was specified." Below I give an example
when I try to build the x11/mate port. It gets this error when it tries
to build graphics/graphene as a dependency. If I then go to
graphics/gr
On Wed, 11 Dec 2019 06:21:29 +0100 Jan Beich jbe...@freebsd.org said
Chris writes:
> I struggled all day yesterday with various ports barfing with similar
> python messages. So today I blew everything off the disk, and started
> from scratch. Which only repeats what happened yest
Chris writes:
> I struggled all day yesterday with various ports barfing with similar
> python messages. So today I blew everything off the disk, and started
> from scratch. Which only repeats what happened yesterday. Is python
> multiplicity no longer available? Or?
See bug 2
On Tue, 10 Dec 2019 16:53:38 -0800 s...@troutmask.apl.washington.edu said
Thank you very much for taking the time to reply.
On Tue, Dec 10, 2019 at 04:47:06PM -0800, Chris wrote:
> I struggled all day yesterday with various ports barfing with similar
> python messages. So today
On Tue, Dec 10, 2019 at 04:47:06PM -0800, Chris wrote:
> I struggled all day yesterday with various ports barfing with similar
> python messages. So today I blew everything off the disk, and started
> from scratch. Which only repeats what happened yesterday. Is python
> multiplici
I've spent the past 2 days attempting a fresh build/install
of world/kernel && preferred ports/applications. The world/kernel
worked to perfection. But I can *not* get the ports to build,
and install. All *fatal* errors stem from python.
So after booting into a new world/kernel;
On 08/12/2019 18:16, Po-Chuan Hsieh wrote:
> For now, you could try using the patched setup.py from current version [1]:
>
> import setuptools
> if __name__ == "__main__":
> setuptools.setup(use_scm_version=True)
>
> At least it works for me for sysutils/py-ansible-lint 4.2.0.
Good idea. I'
setup.py. The docs now say that to install from
> source, you should run:
>
>pip install git+https://github.com/ansible/ansible-lint.git
>
> Do we have support in the ports for python modules setup in this way?
> Is there a similar example I can copy from?
On further in
101 - 200 of 859 matches
Mail list logo
