Control: block -1 by 780489 On 16/03/15 16:24, John Paul Adrian Glaubitz wrote: > Hi Tomasz! > > On 03/16/2015 04:14 PM, Tomasz Buchert wrote: > > I don't think it is the case. It seems to me (although I may be > > wrong) that dpkg-gensymbols does not demangle C++ symbols properly. > > I reported a bug yesterday: > > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780489 > > Indeed, you could be right. I just checked the build log for > verbiste_0.1.41-2 on sh4, for example, and the buildd was, indeed, using > dpkg_1.17.23 that time while it was using 1.17.24 for the last build.
That's a great observation, however I get the problem with 1.17.24 on i386. dpkg-gensymbols does not demangle a few symbols and I don't know why (I'd have to dig dpkg-gensymbols, but I have no time right now). > > >> Please see the available build logs [1] and use this information > >> to update the symbols file for all architectures. Please do also > >> remember to have a look at the builds logs for the port > >> architectures [2] as well to fix these as well. > > > > I'd appreciate if you'd take a look at the bug report I mentioned > > above. > > I could just do a manual build with a downgraded version of dpkg on one > of the buildds. I wasn't really expecting this to be a bug in dpkg as we > usually see this kind of FTBFS due to outdated symbols files. Feel free > to reassign and merge the bug report to dpkg. I also don't think it will change anything, but it is still rather mysterious why these symbols do not demangle on some archs. I'll leave your report open, but I'll mark it blocked by my previous report, since we should understand this anyway. > > Thanks for the heads up! You're welcome! > > Adrian Tomasz
signature.asc
Description: Digital signature
