Matthias Andree wrote:
> > I agree, but I can think of another valid exception. System with
> > Hamming correction on the memory, gets a single bit (correctable)
> > error. Need to rewrite the memory contents to reset all the parity
> > bits!
> That's a matter of the EDAC stuff, not the business o
Chris Rees wrote:
> > I've had to deprecate sysutils/cfs ...
s/sysutils/security
(at least in my instance of the ports tree).
> Whoops, also missed a CVE -- buffer overflows can cause a DoS.
Er, am I the only one who does not recognize what "CVE" stands for?
BTW thanks for the heads-up, which
On Sun, Sep 04, 2011 at 10:32:30PM +0200, Julian H. Stacey wrote:
> It is not responsible to threaten to remove ports without warning
> between releases for non urgent reasons.
portmgr has no such policy.
Ports get deleted all the time due to various issues. I prefer to see
a 1- or 2-month warni
On 4 September 2011 21:32, Julian H. Stacey wrote:
>>
>> Whoops, also missed a CVE -- buffer overflows can cause a DoS.
>> Expiration date altered to 1 month accordingly.
>
> It is not responsible to threaten to remove ports without warning
> between releases for non urgent reasons.
>
> Better to
Hi,
Reference:
> From: Chris Rees
> Date: Sun, 4 Sep 2011 20:21:10 +0100
> Message-id:
>
Chris Rees wrote:
> On 4 September 2011 17:56, Chris Rees wrote:
> > Guys,
> >
> > I've had to deprecate sysutils/cfs -- there's a confirmed issue with
> > failing locks [1] which has
On 4 September 2011 17:56, Chris Rees wrote:
> Guys,
>
> I've had to deprecate sysutils/cfs -- there's a confirmed issue with
> failing locks [1] which has been open for two years with no fix.
>
> Please would someone consider stepping up to fix and maintain it? It
> has two months to live.
>
> Th
Guys,
I've had to deprecate sysutils/cfs -- there's a confirmed issue with
failing locks [1] which has been open for two years with no fix.
Please would someone consider stepping up to fix and maintain it? It
has two months to live.
Thanks!
Chris
[1] http://www.freebsd.org/cgi/query-pr.cgi?pr=
Hi m...@freebsd.org
cc Ruslan & ports@
Ruslan Mahmatkhanov wrote:
> Julian H. Stacey wrote on 03.09.2011 15:38:
> > Hi
> > I see this error (on current too)
> > cd /usr/ports/x11-toolkits/tk84
> > printenv
> > PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/bin
> > TERM=xterm
> >
> I agree, but I can think of another valid exception. System with
> Hamming correction on the memory, gets a single bit (correctable)
> error. Need to rewrite the memory contents to reset all the parity
> bits!
That's a matter of the EDAC stuff, not the business of applications.
_
On Sun, 04 Sep 2011 12:22:35 +0200
Matthias Andree wrote:
> Am 04.09.2011 10:45, schrieb Ivan Klymenko:
> > В Sun, 04 Sep 2011 09:34:33 +0200
> > Matthias Andree пишет:
> >
> >> Am 04.09.2011 09:12, schrieb Ivan Klymenko:
> >>
> >>> Maybe this will help:
> >>> *rdup_entry = *rdup_entry;
> >>
>
Am 04.09.2011 10:48, schrieb Mark Linimon:
> On Sun, Sep 04, 2011 at 05:09:05AM +0200, Gerald Pfeifer wrote:
>> Can you advise which value of __FreeBSD_version to use? The official
>> list at
>>
>> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/freebsd-versions.html
>> does n
Am 04.09.2011 10:45, schrieb Ivan Klymenko:
> В Sun, 04 Sep 2011 09:34:33 +0200
> Matthias Andree пишет:
>
>> Am 04.09.2011 09:12, schrieb Ivan Klymenko:
>>
>>> Maybe this will help:
>>> *rdup_entry = *rdup_entry;
>>
>> This is just guessing and probably triggers the same warning unless
>> it's v
В Sun, 04 Sep 2011 09:34:33 +0200
Matthias Andree пишет:
> Am 04.09.2011 09:12, schrieb Ivan Klymenko:
>
> > Maybe this will help:
> > *rdup_entry = *rdup_entry;
>
> This is just guessing and probably triggers the same warning unless
> it's volatile.
>
> Have the original author look at it.
T
On Sun, Sep 04, 2011 at 05:09:05AM +0200, Gerald Pfeifer wrote:
> Can you advise which value of __FreeBSD_version to use? The official
> list at
>
> http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/freebsd-versions.html
> does not have a reference from what I can see.
There is
Am 04.09.2011 08:42, schrieb Ruslan Mahmatkhanov:
> Roman Divacky wrote on 25.07.2011 19:59:
>> Hi!
>>
>>
>> Flz@ just run another exp-build with CC=clang and CXX=clang++. The
>> results can be
>> seen here:
>>
>>
>> http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.20110723205754/
>>
Am 04.09.2011 09:12, schrieb Ivan Klymenko:
> Maybe this will help:
> *rdup_entry = *rdup_entry;
This is just guessing and probably triggers the same warning unless it's
volatile.
Have the original author look at it.
___
freebsd-ports@freebsd.org maili
Am 04.09.2011 05:09, schrieb Gerald Pfeifer:
> On Mon, 25 Jul 2011, Matthias Andree wrote:
>> Namely: if a port sets USE_GCC=4.2+ (for instance, sysutils/busybox does
>> that), the Pointyhat build does not install GCC. I think the bug is in
>> ports/Mk/bsd.gcc.mk which is unaware that there are ne
В Sun, 04 Sep 2011 10:42:07 +0400
Ruslan Mahmatkhanov пишет:
> Roman Divacky wrote on 25.07.2011 19:59:
> > Hi!
> >
> >
> > Flz@ just run another exp-build with CC=clang and CXX=clang++. The
> > results can be seen here:
> >
> >
> > http://pointyhat.freebsd.org/errorlogs/amd64-errorlogs/e.9-exp.2
Ruslan wrote:
> Hi, i maintain port (sysutils/rdup) that is failing with clang:
I have looked at the problem, it is indeed in rdup source. If you look
at rdup git history for rdup-tr.c you will see
remove rdup_entry_c from the code, totally unneeded
in this modification, the line
rdup
19 matches
Mail list logo
