On Wed, Dec 07, 2011 at 10:27:58PM +, Sven wrote:
> > > https://bugs.gentoo.org/show_bug.cgi?id=392407
> > If you know Gentoo devs then you know that just opening bug reports is
> > not going to accelerate things. On the other hand adding a new
> > revision of the Ebuild that includes the
> > https://bugs.gentoo.org/show_bug.cgi?id=392407
> If you know Gentoo devs then you know that just opening bug reports is
> not going to accelerate things. On the other hand adding a new
> revision of the Ebuild that includes the patch from above will sure get
> more attention.
The bug is
On 07.12.2011 21:14, Sven wrote:
> Tom Hendrikx whyscream.net> writes:
>> On a side note, I noticed DSPAM 3.10.1 made it to stable on gentoo this
>> week. Cake time :)
> Since both Postgres 9.1.1 and dspam 3.10.1 are stable on Gentoo now, people
> will
> loose mails here. At least on my boxes th
On Wed, Dec 07, 2011 at 08:14:26PM +, Sven wrote:
> Tom Hendrikx whyscream.net> writes:
> > On a side note, I noticed DSPAM 3.10.1 made it to stable on gentoo this
> > week. Cake time :)
>
> Since both Postgres 9.1.1 and dspam 3.10.1 are stable on Gentoo now, people
> will
> loose mails here
Tom Hendrikx whyscream.net> writes:
> On a side note, I noticed DSPAM 3.10.1 made it to stable on gentoo this
> week. Cake time :)
Since both Postgres 9.1.1 and dspam 3.10.1 are stable on Gentoo now, people will
loose mails here. At least on my boxes this issue caused mails to be swallowed
by dsp
On 29/11/11 23:35, Stevan Bajić wrote:
> On 29.11.2011 23:02, Tom Hendrikx wrote:
>> On 29-11-11 22:09, Stevan Bajić wrote:
>>> On 29.11.2011 15:39, Sven wrote:
> The workaround is to set standard_conforming_strings=off in
> postgresql.conf, downgrade to postgresql 9.0, or wait until dspam
On 29.11.2011 23:02, Tom Hendrikx wrote:
> On 29-11-11 22:09, Stevan Bajić wrote:
>> On 29.11.2011 15:39, Sven wrote:
The workaround is to set standard_conforming_strings=off in
postgresql.conf, downgrade to postgresql 9.0, or wait until dspam 3.10.2
is released, which will contain a
On 29-11-11 22:09, Stevan Bajić wrote:
> On 29.11.2011 15:39, Sven wrote:
>>> The workaround is to set standard_conforming_strings=off in
>>> postgresql.conf, downgrade to postgresql 9.0, or wait until dspam 3.10.2
>>> is released, which will contain a fix for this issue.
>> Thanks for the hint, I
On 29.11.2011 15:39, Sven wrote:
>> The workaround is to set standard_conforming_strings=off in
>> postgresql.conf, downgrade to postgresql 9.0, or wait until dspam 3.10.2
>> is released, which will contain a fix for this issue.
> Thanks for the hint, I guess I'll wait for 3.10.2 and then try wheth
> The workaround is to set standard_conforming_strings=off in
> postgresql.conf, downgrade to postgresql 9.0, or wait until dspam 3.10.2
> is released, which will contain a fix for this issue.
Thanks for the hint, I guess I'll wait for 3.10.2 and then try whether the
Gentoo ebuild works as is or n
On 29/11/11 14:53, Sven wrote:
> Hi
>
> I'm getting errors such as the following logged on a virgin install of the
> above
> versions:
>
> [11/29/2011 14:29:00] 29154: ERROR: invalid byte sequence for encoding
> "UTF8":
> 0xae: INSERT INTO dspam_signature_data (uid,signature,length,created_on
On Tue, 29 Nov 2011 13:53:27 + (UTC), Sven wrote:
> Hi
>
> I'm getting errors such as the following logged on a virgin install
> of the above
> versions:
>
> [11/29/2011 14:29:00] 29154: ERROR: invalid byte sequence for
> encoding "UTF8":
> 0xae: INSERT INTO dspam_signature_data
> (uid,signa
Hi
I'm getting errors such as the following logged on a virgin install of the above
versions:
[11/29/2011 14:29:00] 29154: ERROR: invalid byte sequence for encoding "UTF8":
0xae: INSERT INTO dspam_signature_data (uid,signature,length,created_on,data)
VALUES (1,E'4ed4de1c291545272412566',752,CURR
13 matches
Mail list logo
