On 5 Apr 2012, at 20:19, Yann Dirson wrote: > Disclaimer: I am still using an old dansguardian (2.9.9.7-2.1, last > pre-2.10 packaged version) because http://bugs.debian.org/536778 which > in itself is a blow in the face of us developers, but that's another > story which *should not* be related to compatibility breakages...
I can't reproduce this with 2.10; I'll try downgrading to 2.9 and see if I can reproduce it there. > Now dansguardian does not have a lot of debug traces to activate, and > I didn't look at the libpcre API yet. Any idea of a particular change > that could cause such a breakage ? I'm not aware of any change that's likely to cause such a breakage. There are two incompatible changes in this version of PCRE, one is that the pcre_info() has been removed, but I put that back in, the other is that the unicode code points that are reserved for encoding high characters in UTF-16 are not accepted in UTF-8 mode. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
