Well I zfs destory'd my jails and redone everything, Works now
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
On 12/09/2018 13:33, Robert Huff wrote:
How many ports_require_ python 3?
How many ports_require_ python 2?
yeah, I'd like to know too. I mean, I've never installed python as like
requiring it to program - it's installed as a dependency of other stuff
I want to actually run. And I thought
On Wed, 12 Sep 2018, Koichiro Iwao wrote:
Hi,
OpenSSL 1.1.1 has been added to ports tree. AFAIK OpenSSL 1.1.1 supports
TLSv1.3
but no port options for TLSv1.3. There're only TLS1, TLS1_1, TLS1_2.
I assume TLSv1.3 will be enabled by default unless disabled explicitly so
security/openssl111
Hi,
OpenSSL 1.1.1 has been added to ports tree. AFAIK OpenSSL 1.1.1 supports
TLSv1.3
but no port options for TLSv1.3. There're only TLS1, TLS1_1, TLS1_2.
I assume TLSv1.3 will be enabled by default unless disabled explicitly
so
security/openssl111 will always be built with TLSv1.3 enabled,
Mesa provides OpenGL/Vulkan drivers for Intel/AMD cards and also VAAPI/VDPAU
drivers for AMD cards. Recently, a new minor version was released. So far it
was only tested Skylake with drm-stable-kmod on 12.0-CURRENT. Can someone test
on FreeBSD < 11.2 for regressions? If you find any don't forget
tech-lists writes:
> > The only question I have there - why we still don't switched to
> > python3 by default?)
>
> yeah!!! :D
How many ports _require_ python 3?
How many ports _require_ python 2?
Curiously,
> > Removed that file from those ports and didn't seem to help
>
> Can you tell if installing port lang/python36 alone instead of as a
> dependency works? I think it does not.
> The problem might be at the end of lang/python36/Makefile (from
> line 140 and down). There is a similiar block at the
Am 12.09.18 um 07:58 schrieb Matthias Fechner:
> Dear Stefan, Dear Mathieu,
>
> Am 10.09.18 um 14:10 schrieb Stefan Esser:
>> This is a design decision in portmaster that has existed for at least
>> a decade.
>>
>> Use INSTALL_DEPENDS if you depend on a port being available and upgraded
>> before
> Removed that file from those ports and didn't seem to help
Can you tell if installing port lang/python36 alone instead of as a
dependency works? I think it does not.
The problem might be at the end of lang/python36/Makefile (from
line 140 and down). There is a similiar block at the end of
On 12/09/2018 09:50, Ruslan Makhmatkhanov wrote:
The only question I have there - why we still don't switched to python3
by default?)
yeah!!! :D
--
J.
___
freebsd-ports@freebsd.org mailing list
> Maybe I need to stop using portupgrade. What is the best replacement?
I never liked traditional updaters: to me, they seem too complex for a task that
should be rather simple. Thus I wrote one myself: Caronte.
It has not yet been committed to the port tree, but you can find the port
here,
tech-lists wrote on 9/12/18 11:09 AM:
Hello,
On 11/09/2018 15:54, Ruslan Makhmatkhanov wrote:
No, it's because pylint2 as itself requires python > 3.4. User should
switch to older devel/pylint1 if he needs to stick with 2.7.
But I'm not upgrading pylint2:
>>> (pylint-py27-1.9.2) wants
Hello,
On 11/09/2018 15:54, Ruslan Makhmatkhanov wrote:
No, it's because pylint2 as itself requires python > 3.4. User should
switch to older devel/pylint1 if he needs to stick with 2.7.
But I'm not upgrading pylint2:
>>> (pylint-py27-1.9.2) wants to upgrade to pylint-py36-2.1.1
Maybe I
Dear Stefan, Dear Mathieu,
Am 10.09.18 um 14:10 schrieb Stefan Esser:
> This is a design decision in portmaster that has existed for at least
> a decade.
>
> Use INSTALL_DEPENDS if you depend on a port being available and upgraded
> before your port's do-install is invoked.
>
> Changing the
14 matches
Mail list logo
