Re: Re: poudriere, FLAVOR and rebuilding for python3.6

2018-09-11 Thread Bjarne
Mailtrouble - hopefully this is not duplicated. Thanks for your response On 10-09-2018 08:11, Matthew Seaman wrote: On 09/09/2018 19:34, Bjarne wrote: I have been using python 2.7 so far for all ports, which means all python packages  are built as py27-something. These python packages are

Re: Poudriere

2018-09-11 Thread Nathan Owens via freebsd-ports
Removed that file from those ports and didn't seem to help On Tuesday, September 11, 2018, 11:32:14 AM CDT, Nathan Owens wrote: It happens only on non x86 no matter version of freebsd.  Py-pytest at py36 does it for me. Koobs tested it in his arm64 at py36.  It’s not the port

zsh 5.6

2018-09-11 Thread Jeffrey Bouquet via freebsd-ports
building 5.6 or 5.6.1 results in three errors here. Most critical is 'bindkey: not found" rendering the terminal near useless. I restored most functionality putting /usr/local/lib/zsh/5.5.1 files back where 5.6 can find them but no luck with 5.6.1 either

Re: Poudriere

2018-09-11 Thread Lorenzo Salvadore via freebsd-ports
> > It happens only on non x86 no matter version of freebsd.  Py-pytest at py36 > > does it for me. Koobs tested it in his arm64 at py36.  It’s not the port > > itself. As the file that touches during build isn’t related to the port The > > freebsd11 changes to freebsd12 according to jail

Re: Poudriere

2018-09-11 Thread Lorenzo Salvadore via freebsd-ports
> It happens only on non x86 no matter version of freebsd.  Py-pytest at py36 > does it for me. Koobs tested it in his arm64 at py36.  It’s not the port > itself. As the file that touches during build isn’t related to the port The > freebsd11 changes to freebsd12 according to jail version  >

Re: Poudriere

2018-09-11 Thread Nathan Owens via freebsd-ports
I’ve also tried reinstalling poudriere and install poudriere-devel reinstall qemu static I don’t know what else it can be Sent from Yahoo Mail for iPhone On Tuesday, September 11, 2018, 11:32 AM, Nathan Owens wrote: It happens only on non x86 no matter version of freebsd.  Py-pytest at

Re: Poudriere

2018-09-11 Thread Nathan Owens via freebsd-ports
It happens only on non x86 no matter version of freebsd.  Py-pytest at py36 does it for me. Koobs tested it in his arm64 at py36.  It’s not the port itself. As the file that touches during build isn’t related to the port The freebsd11 changes to freebsd12 according to jail version 

Re: how to enforce one version of python

2018-09-11 Thread Ruslan Makhmatkhanov
Baptiste Daroussin wrote on 9/11/18 5:51 PM: On Tue, Sep 11, 2018 at 03:28:15PM +0100, tech-lists wrote: Hi, There are a number of ports that seem to have their own preferential flavour of python, and some for example want to install python27 and python36 in the same place, and it's a pain

Re: how to enforce one version of python

2018-09-11 Thread Lorenzo Salvadore via freebsd-ports
> Hi, > There are a number of ports that seem to have their own preferential > flavour of python, and some for example want to install python27 and > python36 in the same place, and it's a pain when using portupgrade or > similar tools. > I have this in my /etc/make.conf: > DEFAULT_VERSIONS+=

Re: how to enforce one version of python

2018-09-11 Thread Baptiste Daroussin
On Tue, Sep 11, 2018 at 03:28:15PM +0100, tech-lists wrote: > Hi, > > There are a number of ports that seem to have their own preferential flavour > of python, and some for example want to install python27 and python36 in the > same place, and it's a pain when using portupgrade or similar tools.

how to enforce one version of python

2018-09-11 Thread tech-lists
Hi, There are a number of ports that seem to have their own preferential flavour of python, and some for example want to install python27 and python36 in the same place, and it's a pain when using portupgrade or similar tools. I have this in my /etc/make.conf: DEFAULT_VERSIONS+= python=2.7

[m...@openssl.org: Re: [openssl-users] openssl 1.0.2 and TLS 1.3]

2018-09-11 Thread The Doctor via freebsd-ports
- Forwarded message from Matt Caswell - Date: Tue, 11 Sep 2018 15:01:38 +0100 From: Matt Caswell To: openssl-us...@openssl.org Subject: Re: [openssl-users] openssl 1.0.2 and TLS 1.3 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 On

Re: Poudriere

2018-09-11 Thread Lorenzo Salvadore via freebsd-ports
> Submitting this here as I believe this may be best place to ask the question > as I use poudriere to test ports before sending patches > I am on 12 current. If I’m building a port that can use either py27 or py36 > on an non x86based system the py27 works fine on all my jails. If I test with

Poudriere

2018-09-11 Thread Nathan Owens via freebsd-ports
Submitting this here as I believe this may be best place to ask the question as I use poudriere to test ports before sending patches I am on 12 current. If I’m building a port that can use either py27 or py36 on an non x86based system the py27 works fine on all my jails. If I test with py36

[patch] [maintainer timeout, 24 days] Bug 230753 - comms/minicom: Change minicom's permissions for security reasons

2018-09-11 Thread Samy Mahmoudi
Dear committer, Could you please commit the changes associated with Bug 230753 . Best regards, Samy Mahmoudi ___ freebsd-ports@freebsd.org mailing list

[SOLVED] Re: check_mssql_collection

2018-09-11 Thread Andrea Venturoli
On 9/8/18 10:15 PM, Miroslav Lachman wrote: Hello. I cannot speak about Nagios but if you really want to use PHP I don't care much if it's PHP, python, whatever, as long as it works :) to connect to MSSQL, you can use databases/php71-pdo_dblib Thanks. This solved. I didn't realize

Re: FreeBSD Port: databases/couchdb upgrade to 2.2

2018-09-11 Thread Dave Cottlehuber
On Mon, 10 Sep 2018, at 11:33, Miroslav Lachman wrote: > Hi, > > are there any plans to create port for CouchDB 2.2? > According to latest vulnerability in 1.7.2 and statement on upstream > website http://docs.couchdb.org/en/stable/cve/2018-11769.html there are > no plans to fix it in 1.7,