In years gone by, and I am thinking of FreeBSD 7.0 specifically, portmgr@
gave some latitude to *ALL* committers to just fix things to get a port
into shape. In the case of 7.0, it was making ports build for gcc4.
What we have laying ahead of us is a ports tree in various states of modern
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and
Hi Dewayne
Those vulnerabilities is fixed in version 5.1.1 for which the patch is already
submitted, but have not yet been applied. I will submit a new patch now with
high availability feature removed since this is not working correctly when I
performed further testing on the port.
I was
This is a resent with additional CC of the stable@ ML. This was done to
get more exposure, because the first mail didn't get much reaction. When
replying please only reply to freebsd-x11@, freebsd-ports@ and
freebsd-stable@ are only used to get this a bigger audience.
Greetings!
This is a
Hi,
I'd like to call for maintainer timeout on some PRs I filed.
These PRs are part of the preparations for upgrading lang/gcc to gcc 4.7,
which I'm helping gerald@ with.
All PRs were filed on 2013-12-07 (and most of that batch have already
been comitted), but to move things forward - these are
Kurt Jaeger wrote:
Hi!
After this upgrade, each port using Math/BigInt.pm shows warning:
# service sqlgrey restart
Stopping sqlgrey.
Waiting for PIDS: 986.
Starting sqlgrey.
overload arg '..' is invalid at
/usr/local/lib/perl5/site_perl/5.16/Math/BigInt.pm line 153.
[...]
Is it known
In years gone by, and I am thinking of FreeBSD 7.0 specifically, portmgr@
gave some latitude to *ALL* committers to just fix things to get a port
into shape. In the case of 7.0, it was making ports build for gcc4.
What we have laying ahead of us is a ports tree in various states of modern
On Mon, 06 Jan 2014 17:28:58 +0100
Koop Mast k...@rainbow-runner.nl wrote:
Greetings!
This is a weird call for testers.
First off before the real CFT. We are interested if people are still
using 8.x for there desktop. Is there a specific reason for not updating
to 9.x or 10.x?
So in
We are about to release GMP 5.2.
We have been forced to add three FreeBSD-related items to the releases
notes:
* This release will not work on FreeBSD/amd64 7.x, 8.x or 9 series
before 9.3 with a Haswell CPU or any other CPU which supports the
BMI2 instructions. The reason is
On 1/7/2014 01:02, Matthew Rezny wrote:
We are about to release GMP 5.2.
We have been forced to add three FreeBSD-related items to the releases
notes:
* This release will not work on FreeBSD/amd64 7.x, 8.x or 9 series
before 9.3 with a Haswell CPU or any other CPU which supports the
On Tue, 07 Jan 2014 03:11:28 +0100
John Marino freebsd.cont...@marino.st wrote:
On 1/7/2014 01:02, Matthew Rezny wrote:
We are about to release GMP 5.2.
We have been forced to add three FreeBSD-related items to the
releases notes:
* This release will not work on FreeBSD/amd64 7.x,
On 1/7/2014 04:25, Matthew Rezny wrote:
On Tue, 07 Jan 2014 03:11:28 +0100
John Marino freebsd.cont...@marino.st wrote:
whoa - this is pretty harsh if you assume Torbjorn was sincere to
begin with, and I haven't seen anything that indicates he wasn't.
It's pretty much the definition of no
On 2014-Jan-07 03:11:28 +0100, John Marino freebsd.cont...@marino.st wrote:
Yes, the criticism of well, what exactly is wrong? is valid, but the
guy did write a couple of PRs,
Well, he claims to have written a couple of PRs but has so far refused
to divulge any details. Tijl found one but we
While building ports-mgmt/portupgrade, I'm trying to build ruby19 on a new
system (9.2-RELEASE), portsnapped up to five minutes ago. I'm unable to find
ruby-1.9.3-p484.tar.bz2 on any of the FreeBSD mirrors that ports tries.
I thought this might be a new development (recently updated port, not
14 matches
Mail list logo
