On 2018-Nov-12, at 20:58, Kyle Evans wrote:
> On Mon, Nov 12, 2018 at 10:41 PM Mark Millard wrote:
>>
>> 11.x:
>> o 11.2-STABLE armv6 BANANAPI
>> o 11.2-STABLE armv6 BEAGLEBONE
>> o 11.2-STABLE armv6 CUBIEBOARD
>> o 11.2-STABLE armv6 CUBIEBOARD2
>> o 11.2-STABLE armv6 CUBOX-HUMMINGBOARD
>>
On Mon, Nov 12, 2018 at 10:41 PM Mark Millard wrote:
>
> 11.x:
> o 11.2-STABLE armv6 BANANAPI
> o 11.2-STABLE armv6 BEAGLEBONE
> o 11.2-STABLE armv6 CUBIEBOARD
> o 11.2-STABLE armv6 CUBIEBOARD2
> o 11.2-STABLE armv6 CUBOX-HUMMINGBOARD
> o 11.2-STABLE armv6 RPI-B
> o 11.2-STABLE armv6 RPI2
> o
11.x:
o 11.2-STABLE armv6 BANANAPI
o 11.2-STABLE armv6 BEAGLEBONE
o 11.2-STABLE armv6 CUBIEBOARD
o 11.2-STABLE armv6 CUBIEBOARD2
o 11.2-STABLE armv6 CUBOX-HUMMINGBOARD
o 11.2-STABLE armv6 RPI-B
o 11.2-STABLE armv6 RPI2
o 11.2-STABLE armv6 PANDABOARD
o 11.2-STABLE armv6 WANDBOARD
12.x+ (I got the
>> define(`confUSE_BLACKLIST', `true’)
>>
>> in .mc. I'll give that a try, thanks.
>
> Ok, that doesn't do anything to the .cf file, so I have now inserted the
> definition into sendmail.cf directly (which is uncool since my . cf
> files are generated automatically). We'll see.
If you don't
--On 12 November 2018 at 16:20:52 + Matthew Seaman
wrote:
Hi - thanks for your reply, and detailed info on ports / pkg behind the
scenes!
If it's 'quarterly' (which is the default) then you'll not get an update
until the beginning of the next quarter -- which would be the start of
On 2018-11-12 19:13, Leander Schäfer wrote:
Hello,
databases/mariadb103-server doesn't want to build any more. I use
poudriere to build own local package repositories. It seems like one of
the two last updates broke databases/mariadb103-server port for me:
- 12 Nov 2018 16:58:52 or
- 10 Nov
On 2018-Nov-12, at 05:54, Kyle Evans wrote:
> On Sun, Nov 11, 2018 at 9:11 PM Mark Millard wrote:
>>
>> [I still can not produce the problem below on demand.
>> It seems racy with no fixed context producing the
>> problem as far as which port is building. But the
>> general structure of what
I am not clear if it is the same error as in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233135
If it is, it is fixed few moments ago with
https://svnweb.freebsd.org/ports?view=revision=484810
___
freebsd-ports@freebsd.org mailing list
Hello,
databases/mariadb103-server doesn't want to build any more. I use
poudriere to build own local package repositories. It seems like one of
the two last updates broke databases/mariadb103-server port for me:
- 12 Nov 2018 16:58:52 or
- 10 Nov 2018 14:11:46
On 18. 11. 10., Nilton Jose Rizzo wrote:
> Problem with compiling VirtualBox-ose 5.2.22
>
>
> @cc -c -O2 -g -pipe -O2 -mtune=generic -fno-omit-frame-pointer
> -fno-strict-aliasing -fvisibility=hidden -DVBOX_HAVE_VISIBILITY_HIDDEN
> -DRT_USE_VISIBILITY_DEFAULT -fPIC -Wno-sign-compare
>
On 12/11/2018 14:58, Karl Pielorz wrote:
How long does it usually take for an updated port (e.g. mysql56-server
which in ports is at 5.6.42) to be available as a pkg? (pkg under FBSD
11.2 is currently 5.6.41).
Which branch are you trcking in your pkg(8) config? If it's 'latest',
then you'll
Hi All,
How long does it usually take for an updated port (e.g. mysql56-server
which in ports is at 5.6.42) to be available as a pkg? (pkg under FBSD 11.2
is currently 5.6.41).
I had previously thought all of this was mostly automated behind-the-scenes
"magic" kind of stuff - but four
Hi!
> On 12.11.18 07:20, Kurt Jaeger wrote:
>
> > Which feature breaks ?
>
> Relaying after auth with client certs. The patch manually resets
> openssl's ssl context state to trigger a second handshake after reneg
> and those fields are now opaque in openssl.
>
> > Patches can be applied
On Sun, Nov 11, 2018 at 9:11 PM Mark Millard wrote:
>
> [I still can not produce the problem below on demand.
> It seems racy with no fixed context producing the
> problem as far as which port is building. But the
> general structure of what hangs is the same each
> time so far.]
>
> The
On 12.11.18 07:20, Kurt Jaeger wrote:
> Which feature breaks ?
Relaying after auth with client certs. The patch manually resets
openssl's ssl context state to trigger a second handshake after reneg
and those fields are now opaque in openssl.
> Patches can be applied conditionally (e.g. only for
>>> Can someone confirm (or disprove) that the current version of Sendmail
>>> from ports (8.15.2_5), explicitly compiled with the blacklistd flag, has
>>> stopped feeding offending IPs (e.g. those failing do_auth) to blacklistd
>>> since Jan 3?
>> Hello.
>>
>> I used
On 12-11-2018 11:56, Dutch Daemon - FreeBSD Forums Administrator wrote:
> define(`confUSE_BLACKLIST', `true’)
>
> in .mc. I'll give that a try, thanks.
Ok, that doesn't do anything to the .cf file, so I have now inserted the
definition into sendmail.cf directly (which is uncool since my . cf
On 12-11-2018 11:51, Dutch Daemon - FreeBSD Forums Administrator wrote:
> On 12-11-2018 11:22, Masachika ISHIZUKA wrote:
>
>>> Can someone confirm (or disprove) that the current version of Sendmail
>>> from ports (8.15.2_5), explicitly compiled with the blacklistd flag, has
>>> stopped feeding
On 12-11-2018 11:22, Masachika ISHIZUKA wrote:
>> Can someone confirm (or disprove) that the current version of Sendmail
>> from ports (8.15.2_5), explicitly compiled with the blacklistd flag, has
>> stopped feeding offending IPs (e.g. those failing do_auth) to blacklistd
>> since Jan 3?
>
> Can someone confirm (or disprove) that the current version of Sendmail
> from ports (8.15.2_5), explicitly compiled with the blacklistd flag, has
> stopped feeding offending IPs (e.g. those failing do_auth) to blacklistd
> since Jan 3?
Hello.
I used sendmail+tls+sasl2-8.15.2_3 for a long
20 matches
Mail list logo
