Bug#865967: backport to stretch

Is it possible to back port this fix to debian stretch, stretch backports? As far as I can tell, this package simply won't work in Debian Stretch if you are using the postgres backend (maybe it works with other backends, not entirely sure). Thanks for your work packaging it! jamie signature.

Bug#921095: gajim: traceback when starting gajim: got an unexpected keyword argument 'lang'

Package: gajim Version: 1.1.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, After upgrading to gajim 1.1.2, I received a traceback when starting gajim. Gajim started, but was unable to connect to any servers. The problem went away with this change: --- /usr/lib/pyth

Bug#750460: python-pisa: fails with python-reportlab version 3 or higher

Package: python-pisa Version: 3.0.32-1 Severity: grave Tags: patch Justification: renders package unusable Dear Maintainer, When running xhtml2pdf I get the following backtrace: 0 jamie@animal:cdtemp.yjGXVb$ xhtml2pdf /home/iceweasel/Downloads/page.break.html page.break.pdf ***

Bug#724731: fixed by re-installing packages

I also had the problem of loging in via gdm3 and getting a blank screen (with the exception of the debian logo at the bottom). I started having this problem after upgrading a jessie machine on Friday, November 22 in the morning (America/New_York). In the evening of the same day I fixed the problem

Bug#628237: upgrading to 2.4.25-1.1 fixes problem

I can confirm the experience of JPPO: upgrading solves the problem. I pulled in the following three packages from unstable: Selected version '2.4.25-1.1' (Debian:unstable [amd64]) for 'slapd' Selected version '2.4.25-1.1' (Debian:unstable [amd64]) for 'libldap-2.4-2' Selected version '2.4.25-1.1'

Bug#565706: same problem - fixed with 1.98-1

I had the same error message after upgrading grub from 1.98~20100101-1 to 1.98~20100115-1. The problem went away after I upgraded to 1.98-1 jamie signature.asc Description: Digital signature

Bug#525518: link to relevent bug report

For anyone else following this trail - the relevant bug report against cryptsetup is here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=514729 jamie signature.asc Description: Digital signature

Bug#525516: s/SYSFS/ATTR/g worked for me

Thanks for the suggested fix. I had the same problem described in this bug (interfaces not being properly renamed). I did the following: * replaced SYSFS with ATTR in my existing 0-persistent-net.rules file * commented out the newly added lines * rebooted My two relevent (working) lines are:

Bug#385359: opensync-plugin-syncml: Still not listing plugin in msynctool

I'm getting the same behavior. Just updated the package, the .la file is now in place, but msynctool --listplugins does not list the syncml plugin. Thanks for your help!! jamie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#385359: opensync-plugin-syncml: after installing this package, msynctool --listplugins does not list syncml

Package: opensync-plugin-syncml Version: 0.4.0+svn20060725-3 Severity: grave Justification: renders package unusable multisync-tools is pinned to unstable, the rest of the packages are coming from testing. When I run msynctool --listplugins I expect to see syncml, but it is not listed. Also I n