Le 05/05/2017 à 08:16, Franco Fichtner a écrit :
>> On 4. May 2017, at 10:20 AM, Mathieu Arnold wrote:
>>
>> If you went as far as being able to create a pull request, you can do a
>> git show HEAD or git diff origin/trunk...HEAD and submit that in the
>> FreeBSD PR as well.
> It's pretty easy to
On Fri, May 05, 2017 at 12:17:06PM +0200, Mathieu Arnold wrote:
> Le 05/05/2017 à 08:16, Franco Fichtner a écrit :
> >> On 4. May 2017, at 10:20 AM, Mathieu Arnold wrote:
> >>
> >> If you went as far as being able to create a pull request, you can do a
> >> git show HEAD or git diff origin/trunk..
Le 05/05/2017 à 12:20, Baptiste Daroussin a écrit :
> On Fri, May 05, 2017 at 12:17:06PM +0200, Mathieu Arnold wrote:
>> Le 05/05/2017 à 08:16, Franco Fichtner a écrit :
On 4. May 2017, at 10:20 AM, Mathieu Arnold wrote:
If you went as far as being able to create a pull request, you
On Fri, May 05, 2017 at 12:27:13PM +0200, Mathieu Arnold wrote:
> Le 05/05/2017 à 12:20, Baptiste Daroussin a écrit :
> > On Fri, May 05, 2017 at 12:17:06PM +0200, Mathieu Arnold wrote:
> >> Le 05/05/2017 à 08:16, Franco Fichtner a écrit :
> On 4. May 2017, at 10:20 AM, Mathieu Arnold wrote:
On 05/05/2017 11:27, Mathieu Arnold wrote:
Le 05/05/2017 à 12:20, Baptiste Daroussin a écrit :
On Fri, May 05, 2017 at 12:17:06PM +0200, Mathieu Arnold wrote:
Le 05/05/2017 à 08:16, Franco Fichtner a écrit :
On 4. May 2017, at 10:20 AM, Mathieu Arnold wrote:
If you went as far as being able
On 5/5/17 8:17pm, Mathieu Arnold wrote:
> Le 05/05/2017 à 08:16, Franco Fichtner a écrit :
>>> On 4. May 2017, at 10:20 AM, Mathieu Arnold wrote:
>>>
>>> If you went as far as being able to create a pull request, you can do a
>>> git show HEAD or git diff origin/trunk...HEAD and submit that in the
Le 05/05/2017 à 12:37, Baptiste Daroussin a écrit :
> On Fri, May 05, 2017 at 12:27:13PM +0200, Mathieu Arnold wrote:
>> Le 05/05/2017 à 12:20, Baptiste Daroussin a écrit :
>>> I made a script which is a few lines of shell that converts pull
>>> requests to
>>> phabricator reviews automatically.
>>
Can you tell me how to solve this when trying to update the icu port?
I updated my ports before processing.
===> icu-58.2_2,1 has known vulnerabilities:
icu-58.2_2,1 is vulnerable:
icu -- multiple vulnerabilities
CVE: CVE-2017-7868
CVE: CVE-2017-7867
WWW:
https://vuxml.FreeBSD.org/freebsd/607
It seems the port has known vulnerabilities.
If you are sure about what you are doing, run the make command with
"DISABLE_VULNERABILITIES=yes" option as it suggests.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/fre
In trying to compile www/firefox on RPI2 running -current the build now stops
with
error: "NEON support not enabled"
The port at www/neon is compiled and installed.
Thanks for reading, any guidance appreciated.
bob prohaska
___
freebsd-ports@freebsd
I am really not a fan of that.
Better would be to solve the 'vulneratbilities' issue.
/Jos
Op 5-5-2017 om 17:24 schreef mokhi:
It seems the port has known vulnerabilities.
If you are sure about what you are doing, run the make command with
"DISABLE_VULNERABILITIES=yes" option as it suggests.
__
Hello,
On 05/05/2017 11:37 AM, Jos Chrispijn wrote:
I am really not a fan of that.
Better would be to solve the 'vulneratbilities' issue.
/Jos
The vulnerabilites are outlined in
http://www.vuxml.org/freebsd/607f8b57-7454-42c6-a88a-8706f327076d.html
and appear to be patched in devel/icu 58.2
Well, as I can see here < http://www.freshports.org/devel/icu/ > an
older version of this port is vulnerable not current version.
Maybe by updating your tree your problem will be solved :-]
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.
> On 5 May, 2017, at 9:48, mokhi wrote:
>
> Well, as I can see here < http://www.freshports.org/devel/icu/ > an
> older version of this port is vulnerable not current version.
> Maybe by updating your tree your problem will be solved :-]
Yes, this is the correct answer. After icu got patched, th
Yes I noticed as well.
Point is that after updating my tree, the issue still exists allthough I
have th correct portupdate in my ports.
Let me check what is going wrong here.
Thanks,
Jos
Op 5-5-2017 om 17:48 schreef mokhi:
Well, as I can see here < http://www.freshports.org/devel/icu/ > an
o
On 2017-May-5, at 8:13 AM, bob prohaska wrote:
> In trying to compile www/firefox on RPI2 running -current the build now stops
> with
>
> error: "NEON support not enabled"
>
> The port at www/neon is compiled and installed.
Wrong neon.
> Thanks for reading, any guidance appreciated.
https:
Op 5-5-2017 om 18:05 schreef Adam Weinberger:
On 5 May, 2017, at 9:48, mokhi wrote:
Well, as I can see here < http://www.freshports.org/devel/icu/ > an
older version of this port is vulnerable not current version.
Maybe by updating your tree your problem will be solved :-]
Yes, this is the co
On Fri, May 05, 2017 at 10:05:05AM -0600 I heard the voice of
Adam Weinberger, and lo! it spake thus:
>
> Yes, this is the correct answer. After icu got patched, the VuXML
> entry was lowered to mark 58.2_2,1 as non-vulnerable. Jos, it sounds
> like your ports tree is after the icu update but befo
On Fri, May 5, 2017 at 6:37 AM, Jos Chrispijn
wrote:
>
> Op 5-5-2017 om 18:05 schreef Adam Weinberger:
>
>> On 5 May, 2017, at 9:48, mokhi wrote:
>>>
>>> Well, as I can see here < http://www.freshports.org/devel/icu/ > an
>>> older version of this port is vulnerable not current version.
>>> Mayb
> On 5 May, 2017, at 11:13, Matthew D. Fuller wrote:
>
> On Fri, May 05, 2017 at 10:05:05AM -0600 I heard the voice of
> Adam Weinberger, and lo! it spake thus:
>>
>> Yes, this is the correct answer. After icu got patched, the VuXML
>> entry was lowered to mark 58.2_2,1 as non-vulnerable. Jos, i
On Fri, May 05, 2017 at 09:30:39AM -0700, Mark Millard wrote:
>
> Wrong neon.
>
>
Ahh, what I feared 8-)
> https://developer.arm.com/technologies/neon says:
>
I did find that page, but harbored a faint (and apparently
misguided) hope that the port might in some fashion implement
the vector i
On 2017-May-5, at 11:28 AM, bob prohaska wrote:
> On Fri, May 05, 2017 at 09:30:39AM -0700, Mark Millard wrote:
>>
>> Wrong neon.
>>
>>
> Ahh, what I feared 8-)
>
>
>> https://developer.arm.com/technologies/neon says:
>>
>
> I did find that page, but harbored a faint (and apparently
> misg
On 2017-05-04, scratch65...@att.net wrote:
> I can't imagine what code could possibly be in thunar and
> samba that the xfce desktop would need, (...)
Thunar is used to display the icons on the XFCE desktop. It
depends on gvfs, which is used for accessing remote file systems
and the trash inside
On Fri, May 05, 2017 at 12:38:14PM -0700, Mark Millard wrote:
>
> An rpi2 has Cortex-A7 (armv7-A) cores that have NEON
> but armv6 does not.
>
> There is some possibility that with something like
> -mcpu=cortex-a7 in use as a compiler option that
> NEON would be used.
What's the simplest way to
On 2017-May-5, at 4:01 PM, bob prohaska wrote:
> On Fri, May 05, 2017 at 12:38:14PM -0700, Mark Millard wrote:
>>
>> An rpi2 has Cortex-A7 (armv7-A) cores that have NEON
>> but armv6 does not.
>>
>> There is some possibility that with something like
>> -mcpu=cortex-a7 in use as a compiler optio
On Fri, May 05, 2017 at 05:44:16PM -0700, Mark Millard wrote:
>
> (There are some fairly general, but not universal,
> techniques for supplying compiler options to ports.
> I've no clue were firefox lands for such
> properties.)
>
It appears that using
make CFLAGS='-mcpu=cortex-a7'
is sufficient
26 matches
Mail list logo
