Hi Thomas, Thomas Preud'homme (robo...@debian.org on 2012-12-02 16:37 +0100): > Le dimanche 2 décembre 2012 15:53:13, vous avez écrit : [..] > > > > ERROR: invalid byte sequence for encoding "UTF8": 0xae: > > INSERT INTO dspam_signature_data [..] > > - unblock 3.10.2 because it is said to have a fix for this issue > > (not verified, I don't want to start mixing releases even before > > wheezy is released) > > - backport the 3.10.2 fix to wheezy's 3.10.1 > > Both of these solution are not possible since the bug is only > severity normal. It might be OK for the release team to unblock a > package with the workaround backported if the bug was severity > important but I don't think this bug is "important". Dspam only fails > to *retrain* (not filter) of *some* mails.
Ah, that's unfortunate but understandable, I guess. However *some* mails means 90% of my volume (it only succesfully recorded 71 signatures from nearly 800 e-mails). However I've taken a look at the upstream patch that fixes the issue, and agree that it's non-trivial to backport (even if this was RC) as it does way more than just fix string quoting for PostgreSQL 9.1: http://dspam.git.sourceforge.net/git/gitweb.cgi?p=dspam/dspam;a=commit;h=9bc231ae79f84a973ced531356833142c4ae2766 > > > - document this incompatibility+workaround in the release notes > > I'll think about this one. Is the bug related to the new version of > dspam? Were you using dspam with PostgreSQL before without this > problem? I've been using the same dspam version with PostgresQL 8.4 before and didn't have this issue. However, that database also had a default encoding of SQL_ASCII, and the new server uses UTF-8 as encoding, so it's not exactly comparing apples and apples. I did a little more digging, and came out here: http://postgresql.1045698.n5.nabble.com/PQescapeByteaConn-returns-wrong-string-for-PG9-1-Beta3-tp4667713p4668043.html which basically amounts to "dspam's usage of escaped strings only works in postgres' legacy mode, but PostgreSQL 9.1 is in standards-compliant mode by default". > > In addition, we can provide backports for wheezy once it's released. > I guess that would be an acceptable solution, yes. Thanks for the quick response, Arno -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
