On Tue, 2008-11-04 at 12:55 -0500, Jason Bertoch wrote:
> > Use the advanced search tab. Or select 'All' instead of 'Open Bugs'.
>
> I suppose I should have mentioned I tried that. Even with all components,
> versions, statuses, resolutions, severities, priorities, hardware, and OS's
> checked, a
On Wed, 5 Nov 2008 11:17:31 -0500
Jerry <[EMAIL PROTECTED]> wrote:
>In my 'bogofilter.cf' file, I have this entry:
>
> SPAM_SUBJECT_TAG
>#
># tag added to "Subject: " line for identifying spam or unsure
># default is to add nothing.
>#
>spam_subject_tag=***SPAM***
>unsure_subject_t
In my 'bogofilter.cf' file, I have this entry:
SPAM_SUBJECT_TAG
#
# tag added to "Subject: " line for identifying spam or unsure
# default is to add nothing.
#
spam_subject_tag=***SPAM***
unsure_subject_tag=???UNSURE???
For some reason, there is never anything added to the s
On Wed, Nov 05, 2008 at 06:40:26AM -0800, Bill Randle said:
> On Wed, 2008-11-05 at 13:43 +0100, aCaB wrote:
> > Bill Randle wrote:
> > > My workaround was to add the following to the spec file:
> > > # hack to prevent libtoolize from being called. Since we don't patch
> > > # the configure
On Wed, 2008-11-05 at 13:43 +0100, aCaB wrote:
> Bill Randle wrote:
> > My workaround was to add the following to the spec file:
> > # hack to prevent libtoolize from being called. Since we don't patch
> > # the configure.in file, there's no need to re-configure.
> > mv configure.in con
Bill Randle wrote:
> My workaround was to add the following to the spec file:
> # hack to prevent libtoolize from being called. Since we don't patch
> # the configure.in file, there's no need to re-configure.
> mv configure.in configure.in.nu
Hi all,
Just a FYI, you can call libtoolize
