Retire security/clamav-devel, clamav is not being updated that much nowadays,
so a -devel version is not required anymore. Also removed OPTIONS on other
ports that pointed to clamav-devel as a dependency.
Approved by:portmgr (implict)
---
Hi!
> > Set the PR as an "Update"
>
> OOps put it as 'maintainer update' rather than 'update' ... is that
> wrong or is it as good as?
It's a maintainer update, if the update was submitted by the current
maintainer -- or with the intent to change the maintainer and the
old maintainer already app
openX open source is now obsolete in favor of the new Revive-adserver.
This changeset is primarily based on the (*) change submitted by Volodymyr
Kostyrko who have offered to keep the existing maintainer
of OpenX.
PR: ports/186606, ports/189439 (*)
Security: CVE-2013-7149
-
Hey people,
I have started to think about making sage compatible with FreeBSD-10.
The main problem thus far is that clang's c++ compiler is missing some
stuff like the include file ext/numeric.
I don't know if clang's c++ compiler is far behind gcc-4.7, or whether
it is a question of merely copyi
Kevin Oberman wrote:
>
> I think the answers to all of this arre found in the Porter's Handbook.
>
> Submit a PR (using either the send-pr command or the web page
> (http://www.freebsd.org/send-pr.html)
>
> Set the PR as an "Update"
OOps put it as 'maintainer update' rather than 'update' ... is t
Am Sat, 17 May 2014 02:09:07 +0200
schrieb "Dr. Peter Voigt" :
> I have just noticed that my freeradius2 2.2.5 server refuses to start
> with the following message:
>
> radiusd: Refusing to start with libssl version OpenSSL 1.0.1e-freebsd
> 11 Feb 2013 (in range 1.0.1 - 1.0.1f). Security advisory
I have just noticed that my freeradius2 2.2.5 server refuses to start
with the following message:
radiusd: Refusing to start with libssl version OpenSSL 1.0.1e-freebsd
11 Feb 2013 (in range 1.0.1 - 1.0.1f). Security advisory CVE-2014-0160
(Heartbleed)
radiusd: For more information see http://heart
On Fri, 16 May 2014, Marko Cupać wrote:
This is the point of failure:
libtool: compile: /usr/ports/lang/gcc/work/build/./gcc/gcj
-B/usr/ports/lang/gcc/work/build/x86_64-portbld-freebsd10.0/libjava/
-B/usr/ports/lang/gcc/work/build/./gcc/
-B/usr/local/x86_64-portbld-freebsd10.0/bin/
-B/usr/local
On Fri, May 16, 2014 at 9:21 AM, Michelle Sullivan wrote:
> New to the list so educate me not flame me please :)
>
> I wanted a newer version of PG Pool II (version 3.2 or above -
> particularly supporting memcached) .. Got no response from the
> maintainer (though it was only a couple of days ago
New to the list so educate me not flame me please :)
I wanted a newer version of PG Pool II (version 3.2 or above -
particularly supporting memcached) .. Got no response from the
maintainer (though it was only a couple of days ago when I emailed - so
not expecting an immediate response)..
Either
Jerry wrote:
> I am trying to create a new port. If I put:
>
> LICENSE= BSD
>
> portlint is happy; however, running "make makeplist" reports an error:
>
> LICENSE must not contain BSD, instead use BSD[234]CLAUSE
There's no such thing as "the" BSD license, you have to choose one of a
few v
Hey Thomas,
2014-05-16 18:27 GMT+02:00 FreeBSD Ports Management Team Secretary
:
> It is with great pleasure that the FreeBSD Ports Management Team announces
> that Frederic (culot@) Culot will take over responsibilities of team
> secretary effective immediately.
I would like to thank you for all
I am trying to create a new port. If I put:
LICENSE=BSD
portlint is happy; however, running "make makeplist" reports an error:
LICENSE must not contain BSD, instead use BSD[234]CLAUSE
I cannot find anything in the Porters Handbook that directly relates to
this.
--
Jerry
__
It is with great pleasure that the FreeBSD Ports Management Team announces
that Frederic (culot@) Culot will take over responsibilities of team
secretary effective immediately.
Read more at
http://blogs.freebsdish.org/portmgr/2014/05/16/frederic-culot-takes-over-as-portmgr-secretary/
Thomas
o
On Fri, 16 May 2014 06:11:21 -0700
David Wolfskill wrote:
> * I've been using 2G tmpfs for some time without issue.
> * The above error messages may be misleading: it is *possible* that
> the actual complaint is not lack of space, but lack of available
> inodes -- you can't tell from the mess
On Fri, May 16, 2014 at 02:43:09PM +0200, Marko Cupa?? wrote:
> ...
> I am using 10.0-RELEASE-p3 amd64, and am trying to build lang/gcc as a
> dependency for emulators/virtualbox-ose. Building fails giving the
> following messages:
>
> jc1: fatal error: error writing to /tmp/ccwgXZ8m.s: No space l
16.05.2014 15:43, Marko Cupać wrote:
Hi,
I am using 10.0-RELEASE-p3 amd64, and am trying to build lang/gcc as a
dependency for emulators/virtualbox-ose. Building fails giving the
following messages:
jc1: fatal error: error writing to /tmp/ccwgXZ8m.s: No space left on
device compilation terminat
Marko Cupać writes:
> Hi,
>
> I am using 10.0-RELEASE-p3 amd64, and am trying to build lang/gcc as a
> dependency for emulators/virtualbox-ose. Building fails giving the
> following messages:
>
> jc1: fatal error: error writing to /tmp/ccwgXZ8m.s: No space left on
> device compilation terminated.
Hi,
I am using 10.0-RELEASE-p3 amd64, and am trying to build lang/gcc as a
dependency for emulators/virtualbox-ose. Building fails giving the
following messages:
jc1: fatal error: error writing to /tmp/ccwgXZ8m.s: No space left on
device compilation terminated.
gmake[5]: *** [javax/crypto/spec.lo
The (automatic) update of port graphics/libosmesa fails due to an unfetchable
tarball
file:
===>>> Starting check for build dependencies
===>>> Gathering dependency list for graphics/libosmesa from ports
===>>> Dependency check complete for graphics/libosmesa
===>>> All >> libosmesa-10.1.1_1 (2/
20 matches
Mail list logo
