I submitted a PR for an update in January but nothing ever happened,
although a committer did take it.
http://www.freebsd.org/cgi/query-pr.cgi?pr=143209
Troels Kofoed Jacobsen
-- Forwarded message --
From: q...@freebsd.org
Date: Fri, Jun 18, 2010 at 3:10 AM
Subject:
In preparation for 8.1-RELEASE, the ports tree is now in feature freeze.
Normal upgrade, new ports, and changes that only affect other branches
are allowed without prior approval but with the extra Feature safe: yes
tag in the commit message. Any commit that is sweeping, i.e. touches a
large
On Fri, 18 Jun 2010 14:10:28 +0200
Erwin Lansing er...@freebsd.org wrote:
In preparation for 8.1-RELEASE, the ports tree is now in feature
freeze.
Normal upgrade, new ports, and changes that only affect other branches
are allowed without prior approval but with the extra Feature safe:
yes
George Hartzell hartz...@alerce.com wrote:
Mark writes:
Hi,
I've been using this port for some years to power my Squeezebox
devices
- thanks for keeping it up to date.
However, the latest update has killed my installation totally -
first it would not scan my music, and
www/mnogosearch, which was previously failing is OK after this commit.
Thanks for fixing it!
A description of the testing process can be found here:
http://T32.TecNik93.com/FreeBSD/QA-Tindy/
Thanks for your work on making FreeBSD better,
--
QAT - your friendly neighborhood Daemon,
preparing
On Fri, Jun 18, 2010 at 01:37:43PM +0200, Troels Kofoed Jacobsen wrote:
I submitted a PR for an update in January but nothing ever happened,
although a committer did take it.
http://www.freebsd.org/cgi/query-pr.cgi?pr=143209
It was marked closed via feedback timeout. However, there is no
I filed ports/147130 to fix security/keepassx about three weeks ago, and
haven't heard anything from the maintainer yet (Cc:'d).
Can this port be committed before the 8.1 release? Unless I'm missing
something (entirely possible), it's a fairly simple fix.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Damian Gerow wrote:
I filed ports/147130 to fix security/keepassx about three weeks ago, and
haven't heard anything from the maintainer yet (Cc:'d).
Can this port be committed before the 8.1 release? Unless I'm missing
something (entirely
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
(blind carbon copy to Lasse Collin, maintainer of xzutils upstream)
Greetings,
I've just had xz break my devel/libtool22 FreeBSD port build on a low
memory computer (128 MB).
Reason is that xz by default caps memory use at ~40% of physical RAM
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2010/06/18 09:54, Matthias Andree wrote:
So for FreeBSD, I propose to patch this Mk/bsd.port.mk line #2382 (as of
CVS rev. 1.642)
EXTRACT_CMD?= ${XZ_CMD}
to
EXTRACT_CMD?= ${XZ_CMD} $$(getconf LLONG_MAX)
Other
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 19.06.2010, 02:43 Uhr, schrieb Xin LI:
Will ${XZ_CMD} -M max work for you? This should have the same effect I
think (assuming the ports xz version supports it)
Thanks. Yes it does. I wonder why I've missed it in the manpage. This is
so much
I've been experimenting with the idea of using gcc 4.5.1 as my ports
compiler and ran into this problem:
CCCMD = /usr/local/bin/gcc45 -DPERL_CORE -c
-DAPPLLIB_EXP=/usr/local/lib/perl5/5.10.1/BSDPAN -DHAS_FPSETMASK
-DHAS_FLOATINGPOINT_H -DDEBUGGING -fno-strict-aliasing -pipe
12 matches
Mail list logo
