Dear all,
I have read that upstream is joining Debian Science to package recent
upstream version VTK8. I expect that VTK6 will be removed from Debian
soon. So yes, I'd strongly recommend to follow the stable release cycle
of VTK upstream, which means that porting camitk to VTK7 is necessary
fo
On Mon, Sep 24, 2018 at 02:49:37PM +0200, Emmanuel Promayon wrote:
> - if there is no (easy) way to go back to vtk6 in gdcm (or to support both
> vtk6 and vtk7), does this means that we (upstream) need to update CamiTK to
> be based on VTK7 in order to fix this bug?
Disclaimer: I have no idea abou
Hello all
Thanks again to Andreas and Bernhard. You are right: the problem comes
from gdcm 2.8.7-2.
I tried to build the package with the previous version of vtkgdcm. With
version 2.8.7-1 all the tests pass and the packages are built normally
(and autopkgtest does not fail either).
If I un
Hello Emmanuel,
I made a mistake and did my first investigations on testing instead of unstable.
So my findings of my first mail are unrelated (but hope they still help).
So I did another try and got all tests fail like in the reproducible build log.
Something bad happens in these lines:
(gdb) l
On Fri, Sep 21, 2018 at 07:05:40PM +0200, Emmanuel Promayon wrote:
> Andreas, do you have any smart way to check the list of packages that have
> changed/been uploaded in sid in the dependencies of a package during a
> period of time (here from 9 Sep to 15 Sep)? This might help me finding how
> to
Dear Bernhard,
Thank you for your investigation and your time. You are right about
these double delete and this will have to be fixed.
But I am still puzzled:
1) your patch is absolutely required for handling delete properly (btw
thanks for the corresponding references!) but unfortunately it
Control: tags -1 upstream
Hi Bernhard,
thanks a lot for your investigation. Emmanuel Promayon is Uploader and
Upstream and I think he will come back to you and hopefully will
implement the fix soon.
Kind regards
Andreas.
On Thu, Sep 20, 2018 at 06:01:38PM +0200, Bernhard Übelacker wrot
Hello all,
I tried to reproduce this issue.
Unfortunately I never get the "(SEGFAULT)" output for all tests,
just "(Failed)" for most. But some do really segfault in my amd64 VM.
I think the segfaults are caused by the line "delete component;", that
invalidates the iterator by removing its elemen
8 matches
Mail list logo
