Re: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available

2020-04-28 Thread @lbutlr
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*!” _

Re: FreeBSD Port: devel/py-subversion - Python 3 flavor?

2020-04-28 Thread Lev Serebryakov
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

Re: Oddities possibly contributing to lang/gcc9 not building (amd64->aarch64 poudriere based cross build)

2020-04-28 Thread Matthias Andree
Am 28.04.20 um 04:57 schrieb Mark Millard via freebsd-ports: > It appears that quoting vs. option handling is not > working as the build expects or some odd file > names involved: > > > libtool: compile: mv -f "-fgnu-runtime.o" ".libs/NXConstStr.o" > mv: illegal option -- g > usage: mv [-f | -i | -

Re: mail/mailman v3?

2020-04-28 Thread Dan Langille
On Fri, Apr 24, 2020, at 9:32 AM, Dan Langille wrote: > > On Apr 24, 2020, at 9:04 AM, Kurt Jaeger wrote: > > > > Hi! > > > >> With mail/mailman being Python 2.7 (which is end-of-life), and mailman 3 > >> being Python 3 compatible: > >> > >> Do you know of any plans to port Mailman 3? > > > >

Re: mail/mailman v3?

2020-04-28 Thread Kurt Jaeger
Hi! > I see the mailman lists themselves are now on Mailman 3: > > https://mail.python.org/archives/list/mailman-annou...@python.org/thread/HHQN7V6NY7G5CTOSC3WBU7VXW5KEBGVO/ Interesting! Looks like a very uncomfortable design for uniq URLs 8-( -- p...@freebsd.org +49 171 3101372

Re: mail/mailman v3?

2020-04-28 Thread Matthias Andree
Am 28.04.20 um 16:34 schrieb Dan Langille: > On Fri, Apr 24, 2020, at 9:32 AM, Dan Langille wrote: >>> On Apr 24, 2020, at 9:04 AM, Kurt Jaeger wrote: >>> >>> Hi! >>> With mail/mailman being Python 2.7 (which is end-of-life), and mailman 3 being Python 3 compatible: Do you kno

Re: mail/mailman v3?

2020-04-28 Thread Matthias Andree
[Dan, Kurt, this is a re-send of my message written 2020-04-24 with a different sender address.] Am 24.04.20 um 15:04 schrieb Kurt Jaeger: > Hi! > >> With mail/mailman being Python 2.7 (which is end-of-life), and mailman 3 >> being Python 3 compatible: >> >> Do you know of any plans to port Mailm

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-28 Thread Mark Millard via freebsd-ports
On 2020-Apr-28, at 07:39, Emmanuel Vadot wrote: > On Mon, 27 Apr 2020 20:14:47 -0700 > Mark Millard wrote: > >> On 2020-Apr-27, at 17:15, Mark Millard wrote: >> >>> On 2020-Apr-27, at 11:46, Emmanuel Vadot wrote: >>> On Mon, 27 Apr 2020 12:32:46 +0200 Emmanuel Vadot wrote: >>>

Re: mail/mailman v3?

2020-04-28 Thread @lbutlr
On 28 Apr 2020, at 09:33, Matthias Andree wrote: > Leaving Python 3.x compatibility aside, But that is the main issue. Python 2.7 is dead. Well, fine, it’s not quite dead yet, but it is also not feeling any better. (I ran mailman lists for many years, but never made the move to mailman 3 and t

Re: mail/mailman v3?

2020-04-28 Thread Chris
On Tue, 28 Apr 2020 16:43:49 +0200 Kurt Jaeger p...@freebsd.org said Hi! > I see the mailman lists themselves are now on Mailman 3: > > > https://mail.python.org/archives/list/mailman-annou...@python.org/thread/HHQN7V6NY7G5CTOSC3WBU7VXW5KEBGVO/ Interesting! Looks like a very uncomfortable

Re: mail/mailman v3?

2020-04-28 Thread Chris
On Tue, 28 Apr 2020 17:33:41 +0200 Matthias Andree matthias.and...@gmx.de said [Dan, Kurt, this is a re-send of my message written 2020-04-24 with a different sender address.] Am 24.04.20 um 15:04 schrieb Kurt Jaeger: > Hi! > >> With mail/mailman being Python 2.7 (which is end-of-life), and mai

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-28 Thread Mark Millard via freebsd-ports
On 2020-Apr-28, at 09:23, Mark Millard wrote: > On 2020-Apr-28, at 07:39, Emmanuel Vadot wrote: > >> On Mon, 27 Apr 2020 20:14:47 -0700 >> Mark Millard wrote: >> >>> On 2020-Apr-27, at 17:15, Mark Millard wrote: >>> On 2020-Apr-27, at 11:46, Emmanuel Vadot wrote: > On Mon, 2

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-28 Thread Mark Millard via freebsd-ports
[Found a cause of the poudiere vs. not distinction.] On 2020-Apr-28, at 13:01, Mark Millard wrote: > > On 2020-Apr-28, at 09:23, Mark Millard wrote: > >> On 2020-Apr-28, at 07:39, Emmanuel Vadot wrote: >> >>> On Mon, 27 Apr 2020 20:14:47 -0700 >>> Mark Millard wrote: >>> On 2020-Apr-2

Re: python 2.7 marked as deprecated and EOL while 2.7.18 RC is available

2020-04-28 Thread ajtiM via freebsd-ports
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 delete :27 will pull python 3.7

Re: aarch64 host based sysutils/u-boot-{pine64, rock64, rpi[34]} builds fail for: "aarch64-none-elf-gcc: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found"

2020-04-28 Thread Mark Millard via freebsd-ports
[Looks like more than objdump may be involved for /usr/local/aarch64-none-elf/bin/ use.] On 2020-Apr-28, at 14:00, Mark Millard wrote: > [Found a cause of the poudiere vs. not distinction.] > > On 2020-Apr-28, at 13:01, Mark Millard wrote: >> >> On 2020-Apr-28, at 09:23, Mark Millard wrote:

Re: mail/mailman v3?

2020-04-28 Thread Greg Veldman
On Tue, Apr 28, 2020 at 01:02:14PM -0700, Chris wrote: > It also wouldn't be that difficult to simply modify mailman(2) > to adopt the py3.x language changes. To simply make it work, perhaps not. To make it work well and be reliable... might be more difficult than you think. A large chunk of wha