Hi! On Sat, Aug 08, 2009 at 08:44:49PM +0200, Giuseppe Iuculano wrote: > Gerfried Fuchs ha scritto: > > Beg your pardon, but that sounds rather like the ABI of wxwidgets2.8 > > has changed - and then it's not pgadmin3's job to fix it, rather the > > library should bump its compatibility level, not? > > > > Can this please get investigated properly? I don't object to a > > scheduled binNMU of pgadmin3 (given that there won't be any source > > changes needed), but if wxwidgets2.8 changes its ABI/API it shouldn't do > > that in disguise. > > You are right, but I don't think my small patch[1] introduced in the latest > security/QA upload caused an API breakage... > > _ZN21wxMemoryFSHandlerBase19AddFileWithMimeTypeERK8wxStringPKvjS2_@WXU_2.8 > 2.8.7.1-2 and > _ZN21wxMemoryFSHandlerBase19AddFileWithMimeTypeERK8wxStringPKvjS2_@WXU_2.8.5 > 2.8.7.1-1 > > I have no idea... Is it possible that something changed with symbol mangling in > latest gcc-4.3 version? > > [1]http://patch-tracking.debian.net/patch/series/view/wxwidgets2.8/2.8.7.1-2/CVE-2009-2369.dpatch > since amd64 seems to be the only architecture with (known) problems, and that the version that was built on the uploaders machine, I am suspecting it was a build problem caused by the uploaders machine. I'm working on (waiting for) wx to rebuild on my amd64 and then I'll test to see if that fixes it. Cheers, Ryan -- _________________________ Ryan Niebur ryanryan52@gmail.com
Attachment:
signature.asc
Description: Digital signature