So... two weeks are now passed and i still see no objections from
maintainer. Can please anybody commit? It will be terrible sad if work
that took so much time and energy will remains unfinished. Thanks.
Ruslan Mahmatkhanov wrote on 17.08.2011 21:54:
So i split this up to three pr's as was
On Tue, 30 Aug 2011 17:57:10 +0200
Matthias Andree mand...@freebsd.org wrote:
I understand that keeping unchanging software can sometimes be
necessary, if you're working around its quirks.
At the same time I'd like to discourage new installations of dead
software so that it disappears over
On 31 Aug 2011 01:51, Conrad J. Sabatier conr...@cox.net wrote:
Odd little problem here I'm noticing with cvs.
When I do a cvs diff -uN, for some reason the -N switch is being
ignored. It vanishes completely in the header of the resulting
output. I've been trying to rename one of my patch
On Wed, 31 Aug 2011 09:17:52 +0100
Chris Rees utis...@gmail.com wrote:
On 31 Aug 2011 01:51, Conrad J. Sabatier conr...@cox.net wrote:
Odd little problem here I'm noticing with cvs.
When I do a cvs diff -uN, for some reason the -N switch is being
ignored. It vanishes completely in the
On Wed, Aug 31, 2011 at 03:50:04AM -0500 I heard the voice of
Conrad J. Sabatier, and lo! it spake thus:
[...] so I don't try to do anything that modifies the repo,
cvs add doesn't affect the repository, just the working tree state.
--
Matthew Fuller (MF4839) |
Hello all, i also ran into the libproxy upgrade problems.
So i tried al the stuff i found on the mailling list so far.
I tried the solution from j.kim
find /usr/local/lib -name *.la | \
xargs grep -l /usr/local/lib/libproxy.la | \
xargs -L 1 pkg_info -W | \
awk '{ print
This is the output from building varnish 3.0.1 on 8.2-RELEASE. I
recently built 3.0.0 without any problems.
/bin/sh ../../libtool --tag=CC --mode=link cc -std=gnu99 -O2 -pipe
-march=nocona -fno-strict-aliasing -D_THREAD_SAFE -pthread -Wextra
-Wno-missing-field-initializers -Wno-sign-compare
Hello all, i also ran into the libproxy upgrade problems.
So i tried al the stuff i found on the mailling list so far.
I tried the solution from j.kim
find /usr/local/lib -name *.la | \
xargs grep -l /usr/local/lib/libproxy.la | \
xargs -L 1 pkg_info -W | \
awk '{ print
On Wed, 2011-08-31 at 09:13 +, Johan Hendriks wrote:
Hello all, i also ran into the libproxy upgrade problems.
So i tried al the stuff i found on the mailling list so far.
I tried the solution from j.kim
find /usr/local/lib -name *.la | \
xargs grep -l
On Wed, 31 Aug 2011 03:51:27 -0500
Matthew D. Fuller fulle...@over-yonder.net wrote:
On Wed, Aug 31, 2011 at 03:50:04AM -0500 I heard the voice of
Conrad J. Sabatier, and lo! it spake thus:
[...] so I don't try to do anything that modifies the repo,
cvs add doesn't affect the
Van: Michal Varga [varga.mic...@gmail.com]
Verzonden: woensdag 31 augustus 2011 11:19
Aan: Johan Hendriks
CC: freebsd-ports@freebsd.org
Onderwerp: Re: libproxy and libnotify the story continues :D
This is another iteration of the same old issue:
per...@pluto.rain.com wrote on 31.08.2011 09:29:
Forwarding to ports@, which seems more likely to yield an answer to
this particular inquiry than questions@
Please keep the OP, who is probably not subscribed to ports@, in the
Cc: list.
On 25 August 2011 18:54, Chris Rees utis...@gmail.com wrote:
On 24 August 2011 16:14, per...@pluto.rain.com wrote:
When the specified or calculated rate exceeds 64KB/sec, the
required sleep interval between 64KB chunks is less than one
second. Since diskcheckd calculates the interval in
GnuTLS has been updated. URL:
http://article.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/5243
I was wondering if there is any work being done on getting the new
version into the ports tree. GnuTLS 3.0.x branch replaces the GnuTLS
2.12.x branch as the supported stable branch. The experimental
On Fri, Aug 26, 2011 at 03:30:47PM -0400, Carmel wrote:
After updating my system as per the UPDATING file, I now find that the
Nvidia driver no longer works with Xorg.
I've just updated the driver to version 280.13; perhaps you should update
your ports free, rebuild the driver, and see if the
per...@pluto.rain.com wrote on 31.08.2011 09:29:
Forwarding to ports@, which seems more likely to yield an answer to
this particular inquiry than questions@
Please keep the OP, who is probably not subscribed to ports@, in the
Cc: list.
On Wed, 31 Aug 2011 15:28:43 +0200
Kurt Jaeger articulated:
GnuTLS has been updated. URL:
http://article.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/5243
I was wondering if there is any work being done on getting the new
version into the ports tree. GnuTLS 3.0.x branch replaces
Hi!
gnutls-3.0.1 needs p11-kit in version 0.4 or newer, maybe that's why
we're still at 2.x ?
I am not even going to pretend to know what the problem is there.
Perhaps you can enlighten me as to why the p11-kit port cannot be
updated to the latest version.
I can't enlighten you, but
Hi,
I just committed an update, please do try.
I had some problems with 3.0.1, so be careful before you upgrade all
your servers: https://www.varnish-cache.org/trac/ticket/1001
Anders.
On ons, aug 31, 2011 at 10:42:06am +0200, Christer Solskogen wrote:
This is the output from building varnish
wen heping wrote on 31.08.2011 18:00:
2011/8/31 Ruslan Mahmatkhanovcvs-...@yandex.ru:
per...@pluto.rain.com wrote on 31.08.2011 09:29:
Forwarding to ports@, which seems more likely to yield an answer to
this particular inquiry than questions@
Please keep the OP, who is probably not
2011/8/31 Ruslan Mahmatkhanov cvs-...@yandex.ru:
per...@pluto.rain.com wrote on 31.08.2011 09:29:
Forwarding to ports@, which seems more likely to yield an answer to
this particular inquiry than questions@
Please keep the OP, who is probably not subscribed to ports@, in the
Cc: list.
So zgv 5.9 in the 8.2R ports is marked i386. I commented the
ONLY_FOR_ARCHS line. It compiles and seems to run like a charm
in amd64. Will my computer blow up?
--
Lars Eighner
http://www.larseighner.com/index.html
8800 N IH35 APT 1191 AUSTIN TX 78753-5266
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/30/11 4:25 PM, Ruslan Mahmatkhanov wrote:
Greg Larkin wrote on 31.08.2011 00:07:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/30/11 10:26 AM, Ruslan Mahmatkhanov wrote:
Greg Larkin wrote on 30.08.2011 17:56:
-BEGIN PGP SIGNED
Hello.
I've just compiled samba35 from ports with the extra config settings
ADS/SWAT/DNSUPDATE, no default settings were removed.
After joining the samba as a stand alone server in a windows AD.
settings in smb.conf are
snip
idmap backend = rid:domain=15000-2(edit: idmap_rid:... is
On 31 August 2011 15:08, Lars Eighner portsu...@larseighner.com wrote:
So zgv 5.9 in the 8.2R ports is marked i386. I commented the
ONLY_FOR_ARCHS line. It compiles and seems to run like a charm
in amd64. Will my computer blow up?
Perhaps you should look upstream to see.
The original port
On 2011-Aug-30, 13:45, Beech Rintoul wrote:
On Tuesday 30 August 2011 11:01:18 Ted Hatfield wrote:
On Tue, 30 Aug 2011, Matthias Andree wrote:
Am 30.08.2011 19:57, schrieb Mark Linimon:
On Tue, Aug 30, 2011 at 07:44:12PM +0200, Matthias Andree wrote:
It only warns, it does not prevent
On 31.08.2011 11:14 (UTC+1), Johan Hendriks wrote:
Hello all, i also ran into the libproxy upgrade problems.
So i tried al the stuff i found on the mailling list so far.
I tried the solution from j.kim
find /usr/local/lib -name *.la | \
xargs grep -l /usr/local/lib/libproxy.la | \
Am 30.08.2011 23:45, schrieb Beech Rintoul:
I second that, I also have it installed in several places and haven't had any
problems. I don't want to have to move to another app just because someone
feels like deprecating a mature port. I think the old addage if it ain't
broke applies here.
Oops, I just realized that this was answered in another mail from Michal
Varga. Sorry for the noise.
On 31.08.2011 19:06 (UTC+1), Rainer Hurling wrote:
On 31.08.2011 11:14 (UTC+1), Johan Hendriks wrote:
Hello all, i also ran into the libproxy upgrade problems.
So i tried al the stuff i found
Am 31.08.2011 07:43, schrieb Ade Lovett:
On Tue, 30 Aug 2011 18:06:15 +0200
Matthias Andree mand...@freebsd.org wrote:
Once you have the necessary error handling in place in
your .procmailrc, a .mailfilter file of equal usefulness in maildrop
is shorter and more concise.
1. In the context
We need to upgrade to php5-5.3.6 or later for PCI compliance.
When I check the ports list (http://www.freebsd.org/ports/lang.html),
the latest version is php5-5.3.3.
What happened to 5.3.6, which was released in March?
___
freebsd-ports@freebsd.org
Greg Larkin wrote on 31.08.2011 19:27:
Hi Martin,
I have a question about a commit you made in February 2011:
http://www.freshports.org/commit.php?message_id=201102250750.p1p7ofdg016...@repoman.freebsd.orgfiles=yes
Part of the commit changed:
USE_PYTHON=2.4+
to
USE_PYTHON=2.5+
Chris Meyer wrote on 31.08.2011 20:53:
We need to upgrade to php5-5.3.6 or later for PCI compliance.
When I check the ports list (http://www.freebsd.org/ports/lang.html),
the latest version is php5-5.3.3.
What happened to 5.3.6, which was released in March?
It's 5.3.8 actually. You may
On 31/08/2011 14:13, Ruslan Mahmatkhanov wrote:
per...@pluto.rain.com wrote on 31.08.2011 09:29:
Forwarding to ports@, which seems more likely to yield an answer to
this particular inquiry than questions@
Please keep the OP, who is probably not subscribed to ports@, in the
Cc: list.
Chris Whitehouse wrote on 31.08.2011 22:34:
On 31/08/2011 14:13, Ruslan Mahmatkhanov wrote:
per...@pluto.rain.com wrote on 31.08.2011 09:29:
Forwarding to ports@, which seems more likely to yield an answer to
this particular inquiry than questions@
Please keep the OP, who is probably not
On 31/08/2011 20:00, Ruslan Mahmatkhanov wrote:
Chris Whitehouse wrote on 31.08.2011 22:34:
On 31/08/2011 14:13, Ruslan Mahmatkhanov wrote:
per...@pluto.rain.com wrote on 31.08.2011 09:29:
Forwarding to ports@, which seems more likely to yield an answer to
this particular inquiry than
Chris Rees utis...@gmail.com wrote:
Committed. Thanks!
Oops. There was another file (not needing testing, since the
changes are only in the comments) that I was also going to include
in a final patch after the functional changes got whatever testing
they were going to get :)
The attached also
On Wed, 31 Aug 2011 19:11:02 +0200
Matthias Andree mand...@freebsd.org wrote:
Am 31.08.2011 07:43, schrieb Ade Lovett:
On Tue, 30 Aug 2011 18:06:15 +0200
1. In the context of a FreeBSD port, there is absolutely nothing
wrong with mail/procmail as it stands. That is to say, it compiles
Kurt Jaeger wrote:
GnuTLS has been updated. URL:
http://article.gmane.org/gmane.comp.encryption.gpg.gnutls.devel/5243
I was wondering if there is any work being done on getting the new
version into the ports tree. GnuTLS 3.0.x branch replaces the GnuTLS
2.12.x branch as the
39 matches
Mail list logo
