[17:44] <Laney> woe is gdcm
[17:49] <mitya57> Laney: did you see my gdcm branch in the sponsoring queue? :)
[17:50] <mitya57> (it needs updated gccxml first)
[17:50] <Laney> mitya57: no!
[17:50] <Laney> is it tested with new vtk?
[17:50] <mitya57> Laney: it builds, I don't know how to use it...
[17:54] <Laney> heh
[17:56] <Laney> mitya57: regarding gccxml, we should ask someone who can test build on ppc hardware to do that
[17:56] <Laney> I don't know that "builds in Debian" is a good guide here, since -3 also built there
[17:57] <Laney> infinity: ^? https://bugs.launchpad.net/ubuntu/+source/gccxml/+bug/1186577
[17:57] <mitya57> Laney: I've pinged BenC yesterday, but I think we can sync and then re-add a delta if it fails
[18:06] <Laney> mitya57: we can wait; it's not like the migration can happen without xpdf anyway ;-)
[18:10] <mitya57> Laney: do you have any thoughts about xpdf? :)
[18:11] <Laney> I didn't even look at it
[18:11] <Laney> was under the impression you were going to fix it
[18:12] <mitya57> I can offer some solutions but all are very ugly
[18:13] <mitya57> In short, we compile xpdf not with xpdf core, but with poppler core, and it uses lots of poppler's private methods
[18:14] <mitya57> ... and in new poppler lots of these methods were removed
[18:14] <mitya57> so we can either copy-paste some code from poppler to xpdf (via a patch)
[18:14] <mitya57> or don't build using poppler (security team doesn't like that)
[18:15] <mitya57> or drop it from the archive and wait for upstream/debian to fix it
[18:15] <mitya57> err, s/upstream\///g
[18:17] <mitya57> ah, we can also re-add those methods in poppler
[18:27] <mitya57> Laney: anyway, it's sleep time for me, see you tomorrow @ DMB meeting :)
[18:27] <Laney> nn
[22:28] <infinity> Laney: That patch is still needed on powerpc, FWIW.
[22:51] <infinity> Laney: I might simplify the patch however instead of doing a merge.  Testbuilding now.