Bug#930277: unblock: gdcm_2.8.8-9

2019-06-09 Thread Gert Wollny
remove symbols file, with C++ libraries this +just doesn't work well enough. + + -- Gert Wollny Tue, 26 Mar 2019 22:07:17 +0100 + +gdcm (2.8.8-8) unstable; urgency=medium + + * d/libvtkgdcm2.8a.symbols: Attempt to fix symbols on mips/mipsel + + -- Gert Wollny Tue, 26 Mar 2019 19:35:

Bug#930275: unblock: dcmtk/3.6.4-2.1

2019-06-09 Thread Gert Wollny
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package dcmtk Upstream hasn't ported the package to use charls-2.yet, and the port tried by me resulted in serious regressions (as reported in #923433). This upload removes

Bug#836592: jessie-pu: package gdcm/2.4.4-3

2016-09-09 Thread Gert Wollny
As far as I can tell, the problem isn't the documentation, it's: make[3]: *** No rule to make target '/usr/lib/jvm/default-java/jre/lib/ppc64/libjawt.so', needed by 'bin/libvtkgdcmJava.so'. Stop. Agreed, I didn't see this because I was scanning for "error:". The compilation failure is stil

Bug#836592: jessie-pu: package gdcm/2.4.4-3

2016-09-09 Thread Gert Wollny
On 09.09.2016 03:03, Adam D. Barratt wrote: On Mon, 2016-09-05 at 22:32 +0100, Adam D. Barratt wrote: Unfortunately it FTBFS on ppc64el; see https://buildd.debian.org/status/fetch.php?pkg=gdcm&arch=ppc64el&ver=2.4.4-3%2Bdeb8u1&stamp=1473373168 Hmm, this bug seem to be completely unrelated

Bug#836592: jessie-pu: package gdcm/2.4.4-3

2016-09-04 Thread Gert Wollny
/changelog 2016-08-23 18:45:09.415835673 +0100 @@ -1,3 +1,11 @@ +gdcm (2.4.4-3+deb8u1) jessie-proposed-updates; urgency=medium + + * add patches: +- d/p/CVE-2015-8396.patch: fix according security vunerability +- d/p/CVE-2015-8397.patch: fix according security vunerability + + -- Gert

Bug#810611: nmu: plastimatch 1.6.2+dfsg-2

2016-01-10 Thread Gert Wollny
> That package failed to build last time it was uploaded (and > binNMUed): > > https://buildd.debian.org/status/package.php?p=plastimatch > > That needs fixing first. That was in December, and the problem was (most likely) that at that time insighttoolkit4 was still build against gdcm-2.4 (and

Bug#810611: nmu: plastimatch 1.6.2+dfsg-2

2016-01-10 Thread Gert Wollny
Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: normal Hello, two packages have been uploaded with new SO versions: gdcm and dcmtk. insighttoolkit4 is already build against these but plastimatch still pulls in the old packages. Please rebuild p

Bug#650601: fixed in elastix 4.8-3

2016-01-07 Thread Gert Wollny
On Thu, 2016-01-07 at 16:00 +, James Cowgill wrote: > Wrong bug number? Did you mean #809889 "elastix: FTBFS with > libpng16"? Yes, sorry, copied the number in the bug text instead of taking it from the subject. Best, Gert

Bug#808469: nmu: insighttoolkit4-4-8.2-1

2015-12-20 Thread Gert Wollny
Package: release.debian.org User: release.debian@packages.debian.org Usertags: binnmu Severity: normal Hello, two packages have been uploaded with new SO versions: gdcm and dcmtk. Please rebuild insighttoolkit4 to update these dependencies. nmu insighttoolkit4 4.8.2-1 . ANY . -m 'Rebuild a