On 12/04/2012 11:09, Chris Rees wrote:
Chris, I did misread your email-- portmanager appears absolutely fine,
and is in no danger of removal :)
That's good to know thank you. Sorry, portupgrade to portmanager was a
bit of a sneaky corner.
Chris
__
This is fixed in the latest version. Sorry for the inconvenience.
Doug
--
It's always a long day; 86400 doesn't fit into a short.
Breadth of IT experience, and depth of knowledge in the DNS.
Yours for the right price. :) http://SupersetSolutions.com/
Hi,
A new entry seems to be needed in the vuxml database to report this
new security issue for both nginx < 1.0.5 and nginx-dev < 1.1.19.
Regards,
Rodrigo OSORIO
On 13/04/12 12:11 +, Sergey A. Osokin wrote:
> osa 2012-04-13 12:11:04 UTC
>
> FreeBSD ports repository
>
> Modif
Hello all,
I was recently asked to do some FreeBSD ports support work. I mostly use a
Mac and the MacPorts system. MacPorts has the concept of a variant for a
port, but I can't find the analogue in the FreeBSD system.
Does the FreeBSD ports system have the concept of a variant? If so, can
some
On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote:
> I was recently asked to do some FreeBSD ports support work. I mostly use a
> Mac and the MacPorts system. MacPorts has the concept of a variant for a
> port, but I can't find the analogue in the FreeBSD system.
>
> Does the FreeBSD ports sy
Freddie Cash wrote on 13.04.2012 23:39:
On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote:
I was recently asked to do some FreeBSD ports support work. I mostly use a
Mac and the MacPorts system. MacPorts has the concept of a variant for a
port, but I can't find the analogue in the FreeBSD
On Apr 13, 2012, at 3:39 PM, Freddie Cash wrote:
> On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote:
>> I was recently asked to do some FreeBSD ports support work. I mostly use a
>> Mac and the MacPorts system. MacPorts has the concept of a variant for a
>> port, but I can't find the a
On Fri, Apr 13, 2012 at 11:41 AM, Doug Barton wrote:
> This is fixed in the latest version. Sorry for the inconvenience.
Quickly fixed - Thanks!
BTW, to the ones who reported and fixed it - also thanks for the
previous quick upgrade which fixed the security vulnerability.
>
> Doug
>
> --
>
>
13.04.2012, 23:55, "Chris Inacio" :
> On Apr 13, 2012, at 3:39 PM, Freddie Cash wrote:
>
>> On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote:
>>> I was recently asked to do some FreeBSD ports support work. I mostly use a
>>> Mac and the MacPorts system. MacPorts has the concept of a va
2012/4/13 Konstantin Tokarev :
>
>
> 13.04.2012, 23:55, "Chris Inacio" :
>> On Apr 13, 2012, at 3:39 PM, Freddie Cash wrote:
>>
>>> On Fri, Apr 13, 2012 at 12:04 PM, Chris Inacio wrote:
I was recently asked to do some FreeBSD ports support work. I mostly use
a
Mac and the MacP
Although the port currently does not build there is a PR 166409
containing a patch to fix it. With this patch applied port builds just
fine.
So I suggest to unDEPRECATE sqlrelay port or at least to shift an
EXPIRATION DATE.
--
Mikhail
___
freebsd-ports@
> Although the port currently does not build there is a PR 166409
> containing a patch to fix it. With this patch applied port builds just
> fine.
> So I suggest to unDEPRECATE sqlrelay port or at least to shift an
> EXPIRATION DATE.
>
> --
> Mikhail
Is this comment still true from the pr:
Sqlrel
> Is this comment still true from the pr:
> Sqlrelay 0.44 requires newer rudiments 0.35
Yes, It is. I just successfully built sqlrelay 0.44 against rudiments 0.35
> If so, I am building what the patch is now, however the portstree does
> have rudiments 0.35, now.
Looks like I have missed this updat
>> Is this comment still true from the pr:
>> Sqlrelay 0.44 requires newer rudiments 0.35
> Yes, It is. I just successfully built sqlrelay 0.44 against rudiments 0.35
>> If so, I am building what the patch is now, however the portstree does
>> have rudiments 0.35, now.
> Looks like I have missed th
Kevin Oberman wrote:
> While I think makefile-options is the way to go, I should also
> point out that for the specific case of emacs and X11, it is
> not used due to the very large differences. Other "variants"
> are handled via options, but there are separate emacs and
> emacs-nox11 ports.
> ..
15 matches
Mail list logo