On Thu, Oct 27, 2016 at 2:28 AM, Jochen Neumeister wrote:
>
>
> On 27.10.2016 08:08, Franco Fichtner wrote:
>>> On 27 Oct 2016, at 7:53 AM, Jochen Neumeister wrote:
>>>
>>> No, make makepatch delete the patches into /files and:
>> If there are no
On Thu, Oct 27, 2016 at 06:35:25PM +0200 I heard the voice of
Mathieu Arnold, and lo! it spake thus:
>
> Well, that is another problem, and you are right, OpenSSL's shlib
> should have been bumped, blame the former maintainer for that. I'll
> talk to the new maintainer about that.
The argument
Le 27/10/2016 à 20:36, Matthew D. Fuller a écrit :
> On Thu, Oct 27, 2016 at 06:35:25PM +0200 I heard the voice of
> Mathieu Arnold, and lo! it spake thus:
>> Well, that is another problem, and you are right, OpenSSL's shlib
>> should have been bumped, blame the former maintainer for that. I'll
>>
> Am 26.10.2016 um 14:28 schrieb Torsten Zuehlsdorff :
>
> Aloha,
>
> PHP 7.1 RC5 was released and it will hopefully not too far until the full
> release. Therefore i started some work on the new port.
>
> Sadly i haven't had much time in the last, so its not too much.
Le 27/10/2016 à 17:00, Matthew D. Fuller a écrit :
> On Thu, Oct 27, 2016 at 03:05:03PM +0200 I heard the voice of
> Mathieu Arnold, and lo! it spake thus:
>> Once you install openssl from ports, the ports framework will use
>> it, always.
> That is absolutely not the case since OpenSSL in base
On Oct 27 16:22, Matt Smith wrote:
I don't see this on my system which is FreeBSD 11.0-STABLE #0 r307132
$ ldd /usr/local/sbin/ntpd | grep -E '(crypto|ssl)'
libcrypto.so.38 => /usr/local/lib/libcrypto.so.38 (0x800cee000)
libssl.so.39 => /usr/local/lib/libssl.so.39 (0x801aca000)
Oh never mind,
On Thu, Oct 27, 2016 at 04:22:09PM +0100 I heard the voice of
Matt Smith, and lo! it spake thus:
>
> I don't see this on my system which is FreeBSD 11.0-STABLE #0 r307132
>
> $ ldd /usr/local/sbin/ntpd | grep -E '(crypto|ssl)'
> libcrypto.so.38 => /usr/local/lib/libcrypto.so.38 (0x800cee000)
>
On Oct 27 10:00, Matthew D. Fuller wrote:
On Thu, Oct 27, 2016 at 03:05:03PM +0200 I heard the voice of
Mathieu Arnold, and lo! it spake thus:
Once you install openssl from ports, the ports framework will use
it, always.
That is absolutely not the case since OpenSSL in base was updated to
On Thu, Oct 27, 2016 at 03:05:03PM +0200 I heard the voice of
Mathieu Arnold, and lo! it spake thus:
>
> Once you install openssl from ports, the ports framework will use
> it, always.
That is absolutely not the case since OpenSSL in base was updated to
.so.8 and ports wasn't re-bumped past it.
Le 27/10/2016 à 14:49, David Demelier a écrit :
> 2016-10-27 11:00 GMT+02:00 Mathieu Arnold :
>> Before changing the default, though, I need to change the way GSSAPI is
>> handled, and create a DEFAULT_VERSIONS+=gssapi=
>> and change all the ports with the
2016-10-27 11:00 GMT+02:00 Mathieu Arnold :
> Before changing the default, though, I need to change the way GSSAPI is
> handled, and create a DEFAULT_VERSIONS+=gssapi=
> and change all the ports with the USES=gssapi that gives options to the
> users.
> But I
> On 27 Oct 2016, at 04:20, Kurt Jaeger wrote:
>
> Hi!
>
>> # portlint
>> WARN: /usr/home/joneum/dev/ports/net/wpa_gui/files/patch-wpa_ctrl.c:
>> patch was not generated using ``make makepatch''. It is recommended to
>> use ``make makepatch'' when you need to [re-]generate a
> On 27 Oct 2016, at 11:00 AM, Mathieu Arnold wrote:
>
> Le 26/10/2016 à 15:44, David Demelier a écrit :
>> 2016-10-26 10:46 GMT+02:00 Mathieu Arnold :
>>> Le 26/10/2016 à 00:14, Don Lewis a écrit :
Then the question is, if DEFAULT_VERSIONS+=ssl=openssl
Le 26/10/2016 à 15:44, David Demelier a écrit :
> 2016-10-26 10:46 GMT+02:00 Mathieu Arnold :
>> Le 26/10/2016 à 00:14, Don Lewis a écrit :
>>> Then the question is, if DEFAULT_VERSIONS+=ssl=openssl is not in
>>> make.conf, then why is OpeSSL from ports installed? Nothing should
Em qui, 27 de out de 2016 03:31, Franco Fichtner
escreveu:
>
> > On 27 Oct 2016, at 8:28 AM, Jochen Neumeister
> wrote:
> >
> > Is this now right, that i can only use the new patch in /files? With
> > "make clean" i delete the work folder and the old
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated,
> On 27 Oct 2016, at 8:28 AM, Jochen Neumeister wrote:
>
> Is this now right, that i can only use the new patch in /files? With
> "make clean" i delete the work folder and the old patches.
If all the previous patches patch a single file, makepatch will generate the
patch
On 27.10.2016 08:08, Franco Fichtner wrote:
>> On 27 Oct 2016, at 7:53 AM, Jochen Neumeister wrote:
>>
>> No, make makepatch delete the patches into /files and:
> If there are no patches in files/ maybe you have no patches applied
> in the work/ dir? Does running "make
On Thu, Oct 27, 2016 at 07:47:06AM +0200, Jochen Neumeister wrote:
Hello Jochen!
> I will update the net/wpa_gui.
>
> # portlint
> WARN: /usr/home/joneum/dev/ports/net/wpa_gui/files/patch-wpa_ctrl.c:
> patch was not generated using ``make makepatch''. It is recommended to
> use ``make
Hi!
> # portlint
> WARN: /usr/home/joneum/dev/ports/net/wpa_gui/files/patch-wpa_ctrl.c:
> patch was not generated using ``make makepatch''. It is recommended to
> use ``make makepatch'' when you need to [re-]generate a patch to ensure
> proper patch format.
> 0 fatal errors and 1 warning found.
> On 27 Oct 2016, at 7:53 AM, Jochen Neumeister wrote:
>
> No, make makepatch delete the patches into /files and:
If there are no patches in files/ maybe you have no patches applied
in the work/ dir? Does running "make patch" before makepatch help?
Cheers,
Franco
21 matches
Mail list logo