Hi Gregory! Gregory Sharp wrote:
On Fri, Nov 14, 2014 at 01:36:40PM +0100, Martin Steghöfer wrote:Problem seems resolved to be resolved: https://bugs.debian.org/768769#47Thanks. Please make sure that also the bug-closing magic will be done properly to ensure that plastimatch will not be auto-rejected at some point in timeIs there anything that needs to be done for plastimatch itself? It got a new bug report due to the build failure: https://bugs.debian.org/769975 Therefore it is ok I should just close it?
The original FTBFS issue #768769 seems to be solved (at least judging from local tests) and therefore can stay closed.
The new FTBFS issue #769975, however, isn't yet fixed and IMHO should therefore stay open for now (even if it's not plastimatch's "fault"). Judging from the message [1], I thought that the necessary binNMU for ITK3 was already requested, but I can't find any reference about it in [2]. So someone should request the binNMU for ITK3 (like described in [3]), mentioning bug #769975 (so it becomes clear what broke and the issue can be closed automatically after rebuild) as well as the analysis of the problem posted in [4].
As you were asking, if something needs to be done, maybe you volunteer to do it? I don't have much time right now myself (and no experience with binNMUs either), sorry.
Cheers, Martin [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768769#47[2] https://bugs.debian.org/cgi-bin/pkgreport.cgi?package=release.debian.org#_4_14_4
[3] https://release.debian.org/wanna-build.txt [4] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768769#42