Bug#694942: Bug#701922: cloning 694942, reassign -1 to release-notes
On Sat, 2013-03-02 at 15:36 +0100, Julien Cristau wrote: On Sat, Mar 2, 2013 at 14:53:19 +0100, Julien Cristau wrote: Still seems like something that should be fixed instead of documenting that we're shipping non-working stuff. By which I guess I mean something like this: [...] Not even build-tested, so there's some work left, but hopefully you get the idea. As far as I can tell, this was fixed in dspam so there's no need for a release note. If I'm missing something, please apply relevant cluebats. :-) Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694942: Bug#701922: cloning 694942, reassign -1 to release-notes
Le samedi 2 mars 2013 15:36:23, Julien Cristau a écrit :
On Sat, Mar 2, 2013 at 14:53:19 +0100, Julien Cristau wrote:
Still seems like something that should be fixed instead of documenting
that we're shipping non-working stuff.
Ok, can I assume a tpu upload would be accepted then?
By which I guess I mean something like this:
--- dspam-3.10.1+dfsg.orig/src/pgsql_drv.c
+++ dspam-3.10.1+dfsg/src/pgsql_drv.c
@@ -3175,6 +3175,12 @@ PGconn *_pgsql_drv_connect(DSPAM_CTX *CT
return NULL;
}
+ if (PQserverVersion(dbh) = 90100)
+ {
+PGresult *result = PQexec(dbh, SET standard_conforming_strings TO
off;); +if (result)
+ PQclear(result);
+ }
return dbh;
FAILURE:
Not even build-tested, so there's some work left, but hopefully you get
the idea.
Wonderful. And it builds ! Arno, is it possible for you to forward me one of
the spams that triggered this bug (as an attached file)? Unfortunetely I
couldn't find a spam in my spam folder that would trigger this bug.
Best regards,
Cheers,
Julien
Thanks Julien, much appreciated.
Thomas
signature.asc
Description: This is a digitally signed message part.
Bug#694942: Bug#701922: cloning 694942, reassign -1 to release-notes
On Mon, Mar 4, 2013 at 14:59:35 +0100, Thomas Preud'homme wrote: Le samedi 2 mars 2013 15:36:23, Julien Cristau a écrit : On Sat, Mar 2, 2013 at 14:53:19 +0100, Julien Cristau wrote: Still seems like something that should be fixed instead of documenting that we're shipping non-working stuff. Ok, can I assume a tpu upload would be accepted then? No, but you can send a patch and request an ack on debian-release and find out. Cheers, Julien signature.asc Description: Digital signature
Bug#694942: Bug#701922: cloning 694942, reassign -1 to release-notes
On Sat, Mar 2, 2013 at 14:53:19 +0100, Julien Cristau wrote:
Still seems like something that should be fixed instead of documenting
that we're shipping non-working stuff.
By which I guess I mean something like this:
--- dspam-3.10.1+dfsg.orig/src/pgsql_drv.c
+++ dspam-3.10.1+dfsg/src/pgsql_drv.c
@@ -3175,6 +3175,12 @@ PGconn *_pgsql_drv_connect(DSPAM_CTX *CT
return NULL;
}
+ if (PQserverVersion(dbh) = 90100)
+ {
+PGresult *result = PQexec(dbh, SET standard_conforming_strings TO off;);
+if (result)
+ PQclear(result);
+ }
return dbh;
FAILURE:
Not even build-tested, so there's some work left, but hopefully you get
the idea.
Cheers,
Julien
signature.asc
Description: Digital signature
Bug#701922: cloning 694942, reassign -1 to release-notes
tags 701922 + patch thanks See attached for a proposed wording. Best regards, Thomas Index: en/upgrading.dbk === --- en/upgrading.dbk (revision 9601) +++ en/upgrading.dbk (working copy) @@ -1281,7 +1281,22 @@ killed or aborting the upgrade in order to resolve hand. /para /section +section id=issues-dspam +titleDspam/title +para +The version of systemitem role=packagePostgreSQL/systemitem shipped in +releasename; switched its default mode for string escaping from legacy to +standard-compliant. However, the version of systemitem +role=packagedspam/systemitem in releasename; does not support yet +standard-compliant mode which means some messages cannot be used for +retraining. One possible approach is to manually switch the default back to +legacy mode by setting standard_conforming_strings to off in +filename/etc/postgresql/9.1/main/postgresql.conf/filename. +Note that this might not be possible depending on the requirements of other +programs using PostgreSQL. +/para /section +/section !-- End of 'trouble' section -- /section signature.asc Description: This is a digitally signed message part.
