[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#701922: marked as done (dspam: incompatible with wheezy's postgresql version)

Your message dated Wed, 24 Apr 2013 20:37:32 +0100
with message-id <1366832252.18536.13.camel@jacala.jungle.funky-badger.org>
and subject line Re: Bug#701922: cloning 694942, reassign -1 to release-notes
has caused the Debian Bug report #701922,
regarding dspam: incompatible with wheezy's postgresql version
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org

701922: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701922
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: dspam
Version: 3.10.1+dfsg-5
Severity: normal

Dear Maintainer,

After migrating my dspam database to a new PostgreSQL server, I'm seeing the
following errors in PG's log (edited for readability):
ERROR:  invalid byte sequence for encoding "UTF8": 0xae:
  INSERT INTO dspam_signature_data (uid,signature,length,created_on,data)
  VALUES (1,E'4ed4de1c291545272412566',752,CURRENT_DATE,... ')
which results in the insert being aborted. Although the message gets delivered
succesfully, users cannot retrain on these messages because the signature
doesn't get stored in the database.

According to
the workaround is to set standard_conforming_strings=off in postgresql.conf,
which works for me but may not be possible for others (e.g. because of other
databases in the same cluster).

I can think of multiple solutions here:
- 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
- document this incompatibility+workaround in the release notes

Naturally the latter would be my least favourite option :)


-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (900, 'stable'), (300, 'unstable'), (200, 'stable-updates')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages dspam depends on:
ii  libc6                2.13-35
ii  libdspam7            3.10.1+dfsg-5
ii  libdspam7-drv-pgsql  3.10.1+dfsg-5
ii  libpq5               9.1.6-1
ii  lsb-base             4.1+Debian8
ii  perl                 5.14.2-15

Versions of packages dspam recommends:
ii  dspam-doc  3.10.1+dfsg-5
ii  procmail   3.22-20

Versions of packages dspam suggests:
pn  clamav-daemon      <none>
pn  dspam-webfrontend  <none>

-- Configuration Files:
/etc/default/dspam changed [not included]
/etc/dspam/default.prefs changed [not included]
/etc/dspam/dspam.conf changed [not included]
/etc/dspam/dspam.d/extlookup.conf [Errno 2] No such file or directory: u'/etc/dspam/dspam.d/extlookup.conf'

-- no debconf information

-- debsums errors found:
debsums: changed file /usr/bin/dspam_maintenance (from dspam package)

--- End Message ---
--- Begin Message ---
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. :-)



--- End Message ---

Reply to: