On 11/16/06, Brian <[EMAIL PROTECTED]> wrote:
I started using this a few days ago, got a coredump today. Any of you
interested in the dumpfile or other debug? I'm tracking 6.stable, currently
at the 6.2-PRERELEASE stage.
What died? FuzzyOCR's page on the spamassassin wiki mentions patches
for
On Thu, 16 Nov 2006, James Seward wrote:
What died? FuzzyOCR's page on the spamassassin wiki mentions patches
for libungif and gocr to prevent segfaults, and AFAIK the libungif
port doesn't apply it (gocr does).
/JMS
The relevant corefile is named giftext.core, I'm assuming based on the
name
The port's maintainer updated it to a new version, and it seems to be
working fine for me now.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On 11/16/06, Brian <[EMAIL PROTECTED]> wrote:
The relevant corefile is named giftext.core, I'm assuming based on the
name that is a fuzzyocr dependency.
I'd suggest reinstalling your libungif port following step 3 of my
instructions here:
http://jamesoff.net/site/projects/freebsd/fuzzyocr-for-s
On Thu, Nov 16, 2006 at 09:21:08AM +, James Seward wrote:
>
> On 11/16/06, Brian <[EMAIL PROTECTED]> wrote:
> >I started using this a few days ago, got a coredump today. Any of you
> >interested in the dumpfile or other debug? I'm tracking 6.stable,
> >currently
> >at the 6.2-PRERELEASE sta
On Mon, November 13, 2006 19:20, Frank J. Laszlo wrote:
> Doug Poland wrote:
>>
>> I was searching the list archives and came across a post by Peter
>> Jeremy. He stated that he has a GNUCash 2.0 port. Does anyone know
>> the status of the port? I couldn't find it querying the PR
>> database.
>>
Hi,
I'm still getting the error below on our installations.
%uname -v
FreeBSD 4.10-RELEASE #0: Tue May 25 22:47:12 GMT 2004
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
- Original Message -
Updating the ports index ... Generating INDEX.tmp - please
wait.."/usr/ports/audio/gstreamer-p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Doug Poland wrote:
> On Mon, November 13, 2006 19:20, Frank J. Laszlo wrote:
>> Doug Poland wrote:
>>>
>> See ports/93216 and ports/94826.
>>
> Thank you. Those PR's relate to issues in the 1.9.x version of
> GnuCash. The post I'm referring to
> (
On Thu, November 16, 2006 09:58, Frank J. Laszlo wrote:
> Doug Poland wrote:
>>>
>>> See ports/93216 and ports/94826.
>>>
>> Thank you. Those PR's relate to issues in the 1.9.x version of
>> GnuCash. The post I'm referring to...
>>
> Please read the entire PR, including all comments. Most notabl
On Thu, Nov 16, 2006 at 10:38:07AM -0600, John Jetmore wrote:
>
> I am the author of the swaks smtp testing tool. The port in FreeBSD is a
> couple of releases behind. Is there an email address I could add to my
> announce list to help keep the port up to date? Sorry for the email to
> ports@ b
On 11/16/06, John Jetmore <[EMAIL PROTECTED]> wrote:
I am the author of the swaks smtp testing tool. The port in FreeBSD is a
couple of releases behind. Is there an email address I could add to my
announce list to help keep the port up to date? Sorry for the email to
ports@ but I couldn't fin
On Thu, Nov 16, 2006 at 05:53:46PM +0200, Nicki de Wet wrote:
>
> I'm still getting the error below on our installations.
>
> %uname -v
> FreeBSD 4.10-RELEASE #0: Tue May 25 22:47:12 GMT 2004
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
>
Upgrade to 4.11. Or better yet, 6.x.
--
Shaun Amot
On Sun, 2006-Nov-12 11:49:45 -0600, Scott T. Hildreth wrote:
>On Sun, 2006-10-22 at 10:11 +1000, Peter Jeremy wrote:
>> I've come up with a port for gnucash 2.0.2 and it seems to work so I
>> might just migrate rather than trying to get gnucash 1.8 working.
>>
>
>Peter is this port working?
I'v
On Thu, 2006-Nov-16 10:58:17 -0500, Frank J. Laszlo wrote:
>Please read the entire PR, including all comments. Most notably the
>last few on ports/93216.
Hmmm. I was unaware of that port - I will have to see how it differs
to what I did. Thanks for the pointer. For Doug's benefit, my port
can b
On Thu, November 16, 2006 12:30, Peter Jeremy wrote:
> On Thu, 2006-Nov-16 10:58:17 -0500, Frank J. Laszlo wrote:
>>Please read the entire PR, including all comments. Most notably the
>>last few on ports/93216.
>
> Hmmm. I was unaware of that port - I will have to see how it differs
> to what I d
In response to Sergey Matveychuk <[EMAIL PROTECTED]>:
> Hi.
>
> I think portupgrade-devel is quite stable now. I use it on all servers
> where I update ports often without problems. But anyway I need more
> testers who could confirm its stablity. After a week of testing I'll
> update portupgrade
Freshly installed FreeBSD 6.1-R-p10 box
Fresh ports tree from today. php 5.2.0 installed from ports with the
following extensions:
php5-5.2.0 PHP Scripting Language (Apache Module and CLI)
php5-ctype-5.2.0The ctype shared extension for php
php5-dom-5.2.0 The dom shared extensi
On Thursday 16 November 2006 15:09, Josh Paetzel wrote:
> Freshly installed FreeBSD 6.1-R-p10 box
>
> Fresh ports tree from today. php 5.2.0 installed from ports with
> the following extensions:
>
> php5-5.2.0 PHP Scripting Language (Apache Module and CLI)
> php5-ctype-5.2.0The ctype
On Thu, 2006-11-16 at 15:09 -0600, Josh Paetzel wrote:
> Freshly installed FreeBSD 6.1-R-p10 box
>
> Fresh ports tree from today. php 5.2.0 installed from ports with the
> following extensions:
> [...]
> Unloading the session module 'fixes' the problem. Unfortunately
> session support is missi
On Thursday 16 November 2006 11:50, Bill Moran wrote:
> In response to Sergey Matveychuk <[EMAIL PROTECTED]>:
> > Hi.
> >
> > I think portupgrade-devel is quite stable now. I use it on all servers
> > where I update ports often without problems. But anyway I need more
> > testers who could confirm
On Thu, 16 Nov 2006 11:12:05 -0600, Shaun Amott <[EMAIL PROTECTED]> wrote:
On Thu, Nov 16, 2006 at 05:53:46PM +0200, Nicki de Wet wrote:
I'm still getting the error below on our installations.
%uname -v
FreeBSD 4.10-RELEASE #0: Tue May 25 22:47:12 GMT 2004
[EMAIL PROTECTED]:/usr/obj/usr/src/s
21 matches
Mail list logo
