Alexey Shuvaev wrote:
You should probably want news/sabnzbdplus. It is at 0.4.0 in the ports now.
If you want 0.4.2 you can contact maintainer off-list for the updating plans.
Good suggestion, I will do that.
thanks,
Jos
___
freebsd-ports@freebsd.o
On Sat, Aug 16, 2008 at 08:29:34PM +0200, Jos Chrispijn wrote:
> Just installed from /usr/ports/news/sabnzbd; found out that the port
> that is 'live'installed is version 0.2.5_1 instead of 0.4.2
> Is this a port that is not maintained anymore or am I just stupid asking
> this?
>
You should pro
Just installed from /usr/ports/news/sabnzbd; found out that the port
that is 'live'installed is version 0.2.5_1 instead of 0.4.2
Is this a port that is not maintained anymore or am I just stupid asking
this?
thanks for sharing,
Jos
___
freebsd-ports@f
Hi,
The build which triggered this email is done under tinderbox-2.4.3, on
7-STABLE on amd64, with tinderd_flags="-nullfs -plistcheck -onceonly"
and ccache support, with the "official" up-to-date Ports Tree, with the
following vars set:
NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_
Chad,
This error is the same I got this morning. After the new commit this problem
was solved.
Please update the ports tree and try again.
Jack
- Original Message -
From: "Chad Perrin" <[EMAIL PROTECTED]>
To:
Sent: Saturday, August 16, 2008 9:17 AM
Subject: Re: Ruby port broken? S
On Sat, Aug 16, 2008 at 08:35:00AM +0200, Jack Raats wrote:
> The new commit solved the problem.
Apparently, whatever worked for you hasn't done me any good:
===> Patching for ruby-1.8.6.287,1
===> Applying FreeBSD patches for ruby-1.8.6.287,1
Ignoring previously applied (or reversed) pat
On Sat, Aug 16, 2008 at 7:30 AM, Jack Raats <[EMAIL PROTECTED]> wrote:
> hera# make clean
> ===> Cleaning for ruby-1.8.6.287,1
> hera# make install
> ===> Vulnerability check disabled, database not found
> ===> Found saved configuration for ruby-1.8.6.287,1
> ===> Extracting for ruby-1.8.6.287,
