Re: Any volunteer to fix a FTBFS in mia arch all builds of mia?

Am Freitag, den 01.01.2021, 21:36 +0100 schrieb Andreas Tille: > it would be great if someone could have a look at mia build > > > https://buildd.debian.org/status/fetch.php?pkg=mia=all=2.4.7-5=1609527793=0 > > I have it on m ylist, only last time I could not reproduce the problem, so I

Re: Packaging ITK version 5

Hello Steve, thanks for looking into this. Am Sonntag, den 15.11.2020, 13:07 -0600 schrieb Steven Robbins: > Hi, > > I have a bit of time today and thought I'd look into packaging ITK > 5.1.1. > > My thought is to upload to experimental first. I don't see any > "experimental" branch in

Re: RFS: Bug#957360: insighttoolkit4: ftbfs with GCC-10

Am Dienstag, den 11.08.2020, 08:40 -0500 schrieb Steven Robbins: > > > On my i386 chroot build, there are even more failures: [...] So far these failures were usually coming from using the old FPU on i386, which results in in 80 bit intermediate accuracy (that' what the -fstore-float flag tries

Re: RFS: Bug#957360: insighttoolkit4: ftbfs with GCC-10

Am Samstag, den 08.08.2020, 16:38 -0500 schrieb Steven Robbins: > On Saturday, August 8, 2020 3:28:45 P.M. CDT Étienne Mollier wrote: > > > > Looking back to the upstream branch, if I understand correctly, > > previous upstream/$vers-dfsg1 tags are pointing to a directory > > with both source and

push castxml changes

Hello Steven, I've seen that you uploaded a new version of castxml (0.2.0-3) but it seems you forgot to push the changes to salsa. Could you do this? I've lined up a fix to make it build with llvm-9 that I'd like to upload, since it might help to be able to build insighttoolkit4 with gcc-9 and

Re: DCMTK #913304

Hello, Am Donnerstag, den 17.01.2019, 22:36 +0100 schrieb Julien Lamy: > > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913304 > > > > I think that Gert's idea in one of his latest commits [1] was > actually to be able to have several dictionaries installed, one for > each

Re: Bug#914483: Control: reassign -1 src:gdcm 2.8.7-2

Am Freitag, den 23.11.2018, 20:14 +0100 schrieb Mattia Rizzolo: > Hi, > > so, if you don't particularly mind, I'm happy to just take the least > and fix all the involved packages here, so src:vtk7 I just uploaded vtk7, I knew where to look because I did the changes that made the libraries go

Re: Control: reassign -1 src:gdcm 2.8.7-2

Hello, Am Freitag, den 23.11.2018, 16:30 +0100 schrieb Emmanuel Promayon: > Dear all > > Thank to Paul for your answers about the autoremoval and explanation > about the ABI problem. It seems that Adrian Bunk's triage message in > 909120 (added blocking bug(s) of 909120: 911793) did push the

Re: NDEBUG and CMake

Am Mittwoch, den 25.04.2018, 12:32 +0200 schrieb Sébastien Jodogne: > > cmake -DCMAKE_C_FLAGS=-DNDEBUG -DCMAKE_CXX_FLAGS=-DNDEBUG [...] > > Please someone could validate this approach? TIA! Add this at the top of d/rules: export DEB_CFLAGS_MAINT_APPEND=-DNDEBUG export

Re: GitLab pages (Was: Migration from Alioth to Salsa)

Am Samstag, den 17.02.2018, 09:15 +0100 schrieb Andreas Tille: > > > All the Debian GIS repository are configured to use debian/.gitlab- > > ci.yml instead of the default .gitlab-ci.yml (in the root of the > > repository), this avoids triggering the CI for upstream projects > > that include a

Re: Salmon

Am Samstag, den 16.12.2017, 10:28 +0100 schrieb Andreas Tille: > Hi Gert, > > I once injected version 0.8.0 where I ended up with  > >   /usr/bin/cc  -g -O2 -fdebug-prefix-map=/build/salmon-0.8.0+ds1=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2

Salmon

Hi all, since in the build-tree there is also a version 0.8, and I had to give up fixing that version - there was some include "FrugalBooMap.hpp" missing, I've fixed the RC bug in an new branch: "version-7.2". Best, Gert

Re: Failed to find source code of gromacsgui

Am Freitag, den 08.12.2017, 14:44 +0100 schrieb Andreas Tille: > Hi, > > when trying to migrate unfinished packaging code from SVN to Git I > check the availablity of the upstream source code (to add it as > pristine-tar). > Unfortunately I have not found any souce code download. How about this

Re: [Ann] Changed Debian Med policy: SVN is now deprecated

Am Freitag, den 22.09.2017, 12:15 +0200 schrieb Andreas Tille: > Hi Gert, > > On Fri, Sep 22, 2017 at 12:06:03PM +0200, Gert Wollny wrote: > > > I hope everybody is happy with this - feel free to move a package > > > of > > > your choice according to these i

Re: [Ann] Changed Debian Med policy: SVN is now deprecated

Hello, Am Freitag, den 22.09.2017, 11:19 +0200 schrieb Andreas Tille: > > I hope everybody is happy with this - feel free to move a package of > your choice according to these instructions. I'll certainly take care of amide, ginkgocadx, and dicomscope. As for insighttoolkit ... Has anyone

Re: Bug#853687: trinityrnaseq: ftbfs with GCC-7

Am Freitag, den 01.09.2017, 15:16 +0200 schrieb Andreas Tille: > Hi, > > > I admit I have no idea why this and other header files are not found. In  Chrysalis/Makefile it is only tested up until gcc version 6 to set the include path, for 7 no additional include path is set. I've pushed the

insighttoolkit4 on i386 (+sse2)

Dear all, since every time upstream release a new major version, tests are failing on i386 - a result from using the i387 FPU instructions, and since I only know this after about 8 hours of build time, I have now decided that with the latest release (4.12) I'd enable sse2. Incidentally, I also

VTK6

Dear all, as discussed before, we will probably need a version of the vtk-6 libraries for some reverse dependencies that can not (yet) handle the new OpenGL2 interface (like ginkgocadx and itksnap) to which we will most likely default with vtk-7.  To minimize the conflicts with vtk-7, in the

Re: Please consider a free license for Java Statistical Classes

Am Dienstag, den 11.04.2017, 12:00 +0200 schrieb Andreas Tille: > Hi, > > the contact address has bounced.  Is there anybody who has any idea > how to contact the author Andrew James Bertie? There is one address in the same domain: ajber...@nildram.co.uk found at [1], and two co-authors,

Re: bits about the future with VTK in Buster

> I wonder whether we could keep VTK-6 for projects using the old API > and force VTK-7-only projects to use the new one? VTK-6 and VTK-7 > should be co-installable, right? > I think the language bindings are not co-installable, but those could be dropped from the VTK-6 package. -Gert

bits about the future with VTK in Buster

Hello all, I just drop this here for future reference. I've experimented a bit with VTK-7.1 and among other, minor issues I came across the problem that VTK now defaults to,  and, hence, encourages the use of, a new renderer backend, called OpenGL2 that requires an OpenGL 3.2 context. The old

Re: SOFA Debian package

Hello Andres, Am Mittwoch, den 29.03.2017, 16:05 +0200 schrieb Andreas Tille: > Is this package still active ?  > > The last changes were done by Gert Wollny in our packaging SVN (Gert, > could you please commit the latest status - it says UNRELEASED > currently). Whil

Re: ezDicom

Hello Mark, I gave the program a shot running the bundled windows executable in wine (the Windows executable is in the zip file). I think you would probably be better off using something else - Karsten metioned aeskulap, and gingkocadx, but also amide and xmedcon are packaged. - it would

Re: Insighttoolkit 4.11.0 is out

Hi Andreas On 24.01.2017 08:29, Andreas Tille wrote: > I have no idea whether its feasible nor whether it is a good idea to > bump itk to the latest upstream version but since I noticed the new > version right now I wanted at least let you know. > As Ben suggested I will make a build for

Done: Please help: openmolar is marked for autoremoval from testing

Corrected, tested, and uploaded.  Best,  Gert 

Re: Please help: openmolar is marked for autoremoval from testing

Am Dienstag, den 10.01.2017, 10:30 +0100 schrieb Gert Wollny: > Am Dienstag, den 10.01.2017, 10:10 +0100 schrieb Andreas Tille: > > > > Hi Gert, > > > > On Tue, Jan 10, 2017 at 09:55:27AM +0100, Gert Wollny wrote: > > > > > > > > > >

Re: Please help: openmolar is marked for autoremoval from testing

Am Dienstag, den 10.01.2017, 10:10 +0100 schrieb Andreas Tille: > Hi Gert, > > On Tue, Jan 10, 2017 at 09:55:27AM +0100, Gert Wollny wrote: > > > > > > > > It would be *really* cool if somebody could step in, possibly > > &g

Re: Please help: openmolar is marked for autoremoval from testing

Am Dienstag, den 10.01.2017, 09:03 +0100 schrieb Andreas Tille: >  > It would be *really* cool if somebody could step in, possibly ignore > the test failure by adding > >   override_dh_auto_test: > dh_auto_test || true > > and upload the package after testing that the binary will start. I

Sponsoring request: security fix in dcmtk for CVE2015-8979

Dear all, because of #796095 I can not upload to security-master as a DM, therefore I ask for sponsering of package dcmtk-3.6.0 in jessie fixing CVE-2015-8979 (#848830). Because the git packaging

hilive ready for upload

Hi, I've looked into hilive and made the package build properly:  - the new upstream version closes #833392 (checked on i386)  - it builds only with seqan2 (so this question is resolved)  - I've also added a patch to remove some forced CXX flags Since my DD status is still pending (but AM

orthanc: FTBFS: build-dependency not installable: libssl-dev

Hi,  orthnac build depends on libdcmtk-dev, and this pulls in libssl1.0-dev (since dcmtk (a) does not yet support openssl-1.1 and (b) it is used by programs that require QT which conflicts with openssl-1.1).  libssl1.0-dev conflicts with libssl-dev, and hence the build failure.  The solution is

Sponsoring request: DCMTK to experimental (so-name change)

Dear all,  I've prepared the latest version of DCMTK [1] that will require a transition because the so-name change.  Changes are:    * New upstream version 3.6.1~20160630   * d/* Update package names and build rules to new SO-version many thanks,  Gert  [1]

gtkglextmm sponsoring or upload rights

Hi all, I've prepared a new gtkglextmm upload, but since my NM process is still ongoing I will need either sponsoring or someone to grant me upload rights. Since the package was orphaned and is needed by mia-viewit I am adopting it and set up the packaging git within debian-med (for now, once I

Re: Remaining gcc-6 errors

Hello, On 09.09.2016 15:54, Andreas Tille wrote: #831126 vxl: FTBFS with GCC 6: vcl_compiler.h:127:4: error: #error "Dunno about this gcc" In the ITK embedded copy this is patched, but when I tried to apply the patch to the stand-alone version I found out the last released stand-alon

Please push changes to mia from last sponsoring

Hello Andreas,  could you please push the changes you did to mia when you were sponsoring it? Many thanks,  Gert

Sponsoring request: mia-2.4.2 -> experimental

Dear all,  I've prepare the latest upstream version of mia in the packaging git [1].  Changes:    * Imported Upstream version 2.4.2    * Update package to new upstream version - rename versioned package to 2.4  - add dependency on libjs-mathjax - remove dependency on doxygen-latex   

Sponsoring request: berkeley-express [RC]

Hi all, I've prepared a new upload of berkeley-express [1], changelog reads:    * d/p/gcc-6: Fix compilation with gcc-6, Closes: #811859   * cme fix dpkg-control:  - update standards version to 3.9.8 - update to secure packaging urls   * d/p/correct-debug-flags: don't force debug flags

Re: Sponsoring request [RC]: librg-blast-parser-perl

Am Samstag, den 23.07.2016, 08:09 +0200 schrieb Andreas Tille: > Hi Gert, > > On Fri, Jul 22, 2016 at 08:24:38PM +0200, Gert Wollny wrote: > > > > * Force -std=c++03, because of #829604, Closes: #811702 > I just uploaded even if there is a chance that it becomes &g

Re: Thanks to Gert and Sascha - other please keep on fixing bugs (Was: Thanks to Sascha for his bug fixing - but we should do more (Was: Strengthening team by fixing other members bugs))

Hello all,  Am Freitag, den 22.07.2016, 13:29 +0200 schrieb Andreas Tille: > Hi folks, > > But we need to do more specifically the gcc-6 bugs are quite a > blocker.  I'd like to re-generate metapackages soon.  It would be not > nice if these would not miss the gcc-6 affected losses we currently

Re: Sponsoring request: ITK-4.10 (addendum)

Am Donnerstag, den 14.07.2016, 19:44 -0500 schrieb Steve M. Robbins: > On Thursday, July 14, 2016 8:04:28 AM CDT Andreas Tille wrote: > It's too bad that source-only is not an option.  That seems an > arbitrary limitation and the wiki doesn't shed any light on it.   I would guess that the

Re: Sponsoring request: ITK-4.10 (addendum)

Am Mittwoch, den 13.07.2016, 08:22 +0200 schrieb Andreas Tille: > Hi Gert, > > I admit I either need to find a powerful box *and* a connection with > better bandwidth for upload than I usually have.  I have put Steve > who did previous uploads explicitly in CC.  Steve, please state > explicitly

Re: Sponsoring request: ITK-4.10 (addendum)

I might add, I'd appreciate if someone takes another look at the d/copyright file, it is a complete overhaul.  * There are warnings about "missing-field-in-dep5-copyright", but this is source code in the "public domain"  * There are files that are both under "Apache-2.0" and VTK-copyright, and

Sponsoring request: ITK-4.10

Dear all,  I've prepared the new version of ITK in the packaging svn [1]. Changes:  * New upstream release * d/rules: remove installation of VNL valgrind suppression file,   it is no longer distributed. * d/rules, d/control: switch to automatically created debug packages * d/rules: separate

Sponsoring request sitplus 1.0.3 [RC]

Hello all,  I've prepared the gcc.6 fix for sitplus-1.0.3 in a branch  Changes:    * d/p/siteplus-1.0.3-gcc-6: Fix compilation with gcc-6,      Closes: 811795   * d/copyright: DEP5 corrections   * cme fix dpkg-control   * d/: remove sitplus.menu file   * d/rules: Enable hardening and remove

Sponsoring request [RC]: sofa-framework

Dear all,  I've fixed compilation of sofa framework [1] with gcc-6:    Changes:    * d/p/gcc-6: Add patch to fix compilation with gcc-6, Closes: #811747   * cme fix dpkg-control    * d/copyright: DEP5 - remove duplicate entries    * d/rules: hardening += all    * d/rules: enable parallel builds 

Regarding sga ...

Hi,  I've included the upstream patch to fix compilation with gcc-6.  However, the package overrides the CXXFLAGS so that no debug information is created and the auto-debug package is empty which equals a lintian warning.  In src/configure the flags are forced to "-O3" so I was wondering whether

regarding librostlab-blast

Hello Tatiana. I've seen that you worked on librostlab-blast and it is currently in an unreleased state.  Please take note that I've committed some changed to quell bug #811992.  Best,  Gert 

Another Sponsoring request: proftmb

Hello all,  changelog:    * Team upload.   * d/p/gcc-6: Fix compilation with gcc-6, Closes:  #811830 Am Montag, den 04.07.2016, 14:24 +0200 schrieb Andreas Tille: > Uploaded.  I keep on repeating that your work on fixing gcc-6 bugs is > very appreciated.  Andreas. Well, these are low hanging

Re: Sponsoring request: libgtextutils; - next package I'll work on: libbpp-core

Am Mittwoch, den 29.06.2016, 18:15 +0200 schrieb Gert Wollny: > Am Mittwoch, den 29.06.2016, 17:24 +0200 schrieb Andreas Tille: > > > > > > -   return input_stream ; > > +   return static_cast(input_stream) ; Actually, after reading up on this [1] it

Sponsoring request: libmems

Hi all,  I've update libmems:    * d/p/05: Add patch to fix compilation with g++-6, Closes: #811870   * d/control: cme fix dpkg-control Best,  Gert 

Re: Sponsoring request: libgtextutils; - next package I'll work on: libbpp-core

Am Mittwoch, den 29.06.2016, 17:24 +0200 schrieb Andreas Tille: > there is another UNRELEASED changelog entry from Fabian Klötzl who  > has not created a quilt patch but directly changed the source: Oh, I completely overlooked this, because the given fix is just wrong:  > -   return

Re: Open issue with libbpp-core

Am Mittwoch, den 29.06.2016, 15:39 + schrieb Mattia Rizzolo: > On Wed, Jun 29, 2016 at 05:29:50PM +0200, Gert Wollny wrote: > > > > W: libbpp-core-dev: maintscript-calls-ldconfig postrm > > > > Since so far I have never added these pre/post scripts manually,

Sponsoring request: relion; - next package I'll work on: libgtextutils

Hello all,  I've prepared a new upload for relion [1]:  Changelog    * Team upload.   * d/p/0005: Correct compilation with gcc-6, Closes: #811641   * d/p/0006: Correctly copy only 4 byte, corresponding to the target array size   * d/control: Update standards version to 3.9.8 Many thanks, 

working on gcc-6 build failures, starting with relion

Dear all,  I'm starting to work through the gcc-6 build failures attributed to our blend.  I will work down this list [1] starting with relion and skip those tags that are tagged "upstream" or are blocked.  If someone is already working on relion (or any other package on the list) please say so

insighttoolkit4 licenses & stuff

Hello all, taking on the latest version of ITK (4.10) I've realized that the copyright statement is quite outdated, i.e. it is mostly a copy of what the original tarball provides that misses quite some parts - from the looks of it most of these are in the Modules/ThirdParty directory. Now

Re: Help with CMake linking Debian's LLVM libs

Am Dienstag, den 07.06.2016, 14:54 + schrieb Gianfranco Costamagna: > Hi, > > > > > $ ./debian/rules build > > which llvm version did upstream bundle? > > LLVM folks are known for breaking API between releases, so maybe just > you need a specific llvm version rather than the default one.

libzeep-fixes commited

Hi all,  If someone feels like sponsoring, I've added a patch to libzeep to fix #824013 (FTBFS  with g++6 and boost1.60), and applied some minor packaging fixes.  BTW: is there actually a secure version of the Vcs-Svn url? Best,  Gert 

Re: Request for sponsoring: dcmtk to experimental

Hello Mattia,  > Okay, done, tested, and pushed.  I also pushed the new upstream tag > > now, forgot to do it before.  > uploaded, enjoy! :) > I just did a couple of tiny (hopefully uncontroversial) changes > before > it.  I hope that's fine. Thanks for the cleanup,  With the URL's I saw the

Re: Request for sponsoring: dcmtk to experimental

Am Sonntag, den 08.05.2016, 17:36 + schrieb Mattia Rizzolo: >  > > > > I'll ping you on the list when this is done.  > Thanks. > Okay, done, tested, and pushed.  I also pushed the new upstream tag now, forgot to do it before.  many thanks,  Gert 

Re: Request for sponsoring: dcmtk to experimental

Am Sonntag, den 08.05.2016, 16:42 + schrieb Mattia Rizzolo: > On Sun, May 08, 2016 at 05:31:07PM +0200, Gert Wollny wrote: > > > > - Because upstream set the so-version to 8 I also changed the > > library > > package version to libdcmtk8 (instead of 6).  > &

Request for sponsoring: dcmtk to experimental

Dear all,  I've prepared the latest version of dcmtk in the packaging git for uploading. The version changes the SO-Name of the library, hence I'd suggest to upload first to experimental so I can later check whether all reveres dependencies build properly.  Major changes:  - Because upstream

Re: Bug#808475 closed by Gert Wollny <gw.foss...@gmail.com> (Bug#808475: fixed in gdcm 2.6.1-2)

Hello Mattia,  Am Freitag, den 29.04.2016, 19:05 + schrieb Mattia Rizzolo: > If this process automagically worked in the past is only because > somebody noticed and filed a RM bug for it, but I wouldn't mind > spreading knowledge and having also maintainers be aware of more > in-depth things

Re: [Debian-med-packaging] Bug#798167: camitk: depends on vtk 5

Hello,  while moving to VTK 6 please take into account that we are preparing a transition to VTK 6.3.  Compared to VTK 6.2 version 6.3 removes some deprecated macros  and removes the module "vtkRenderingFreeTypeOpenGL".  You should be able to catch most of the problems related to macros by

Re: [Debian-med-packaging] Bug#798167: camitk: depends on vtk 5

Hi,  > At the moment I am trying some last faint hope solution (basically  > patching QVTKWidget2 with upstream VTK code)... It seems the proposed solution with QVTKWidget3 posted on stackoverfow [1] that you referenced would work. Why not use this one?  > If anyone else has some insight

Re: Anybody who might have fun fixing this? [Was: Bug#821015: harvest-tools: FTBFS with memcpy-related errors]

Hi,  Am Donnerstag, den 14.04.2016, 18:28 +0200 schrieb Andreas Tille: > Hi folks, > > at the end the bug submitter gives some valuable hints to deal with > this problem.  Is there any volunteer to follow the advises? I just pushed the changes. I'll now test-build this on powerpc and armhf to

Re: Help needed for "gbp:error: upstream/2.3.0 is not a valid treeish" (Was: Please finalise new version of ncbi-blast+ since build system is quite tricky)

Hello,  Am Dienstag, den 12.04.2016, 17:42 +0200 schrieb Andreas Tille: > Hi Olivier, > > On Tue, Apr 12, 2016 at 03:33:43PM +, olivier sallou wrote: > > > > > > > > I imported the new upstream version and I **hope** I refreshed > > > the quilt > > > patches correctly.  However, even the

Re: EEG visualization

Am Dienstag, den 12.04.2016, 16:02 +0200 schrieb Karsten Hilbert: > On Tue, Apr 12, 2016 at 03:40:13PM +0200, Gert Wollny wrote: > > > > > > > > > > > > > > long time no update, but relevant for Debian Med: > > > > > > > >

Re: EEG visualization

Hi,  Am Dienstag, den 12.04.2016, 14:53 +0200 schrieb Andreas Tille: >  > > long time no update, but relevant for Debian Med: > > > >    https://github.com/asamardzic/tempo > Any volunteer to package this (may be in a MoM project)? If no-one steps up for a MoM , I'll prepare the package.  best, 

Re: Can "PDB" license be considered free ?

Hi,  > * The user assumes all responsibility for insuring that intellectual > property claims associated with any data set deposited in the PDB > archive are honored.  It should be understood that the PDB data files > do not contain any information  on intellectual property claims with > the

Re: [Debian-med-packaging] Bug#753809: Bug#753809: ginkgocadx, orthanc and sending/receiving data

Thanks for the insight!  > So my guess is the following: > > -Either the AE title that should receive the images is not configured >  with IP and port on the server. It should be configured correctly, because when I run the downloadable pre-compiled version of Ginkgocadx, it uses the same

ginkgocadx -> experimental

Hello all, I've just uploaded an updated version of ginkgocadx to experimental. It is known to crash on exit [1], and at this point I'm not sure how to fix this. Also, the main window is always maximized, and if one closes the main window while the history is still open, it may happen that

Re: [karsten.hilb...@gmx.net: wishlist: add --dicomdir commandline option]

On Wed, 2016-02-17 at 12:29 +0100, Karsten Hilbert wrote: > BTW, may I kindly recall to attention this Aeskulap wishlist item ? Well, I had a look last week, and it is actually not that easy: * The way the DICOM files are loaded is somewhat wired (first they are scanned and then they are loaded

castxml

Hello Gianfranco, tanks for doing the NMU, I was traveling without a computer :) Could you either push the changes to the debian-med git repo, or send me the diff? Many thanks, Gert

New upstream repo: (was Re: Ginkgo CADx free version, status?)

Dear all, the new upstream repo is now here: https://github.com/gerddie/ginkgocadx If anyone wants to join the development, you are _very_ welcome - especially someone with knowledge about the workflows this software is used for. In the next few days I will try to package and upload a

Re: Ginkgo CADx free version, status?

Hi all, unfortunately Carlos was no longer valid, so I interchanged some messages with him on LinkedIn - in Spanish :) He told me that he actually mentioned on Debian-med that a fork would be a good idea at the time when Metaemotion was acquired by Nielsen. He also told me that there is no

Ginkgo CADx free version, status?

Dear Carlos, on the Debian-med list we were discussion the current status of the program Ginkgo CADx in Debian, because it needs some work to be adapted to new versions of DCMTK (3.6.1) and VTK (6.2). Since no new free (as in LPGL-3) version was released since 2014 and since Metaemotion has

Re: castxml sponsoring or upload rights and insighttoolkit-4.9

Hello all, On Wed, 2016-02-03 at 07:17 +0100, Andreas Tille wrote: > upload permissions for castxml granted. Thanks, Andreas. > I can't upload itk until I'm arrived in Kpenhagen (hope we have a > perfect connection there). IT would be cool if somebody else would be > faster than me with

Re: castxml sponsoring or upload rights and insighttoolkit-4.9

On Wed, 2016-02-03 at 08:19 -0600, Steve M. Robbins wrote: > I'd be happy to do the build & upload. > Gert: Is the repo ready to go NOW? Yes, I tested the build last night on amd64. thanks, Gert

castxml sponsoring or upload rights and insighttoolkit-4.9

Dear all, I've prepared the latest snapshot of castxml in the packaging git. It fixes some problems with g++-6 interaction and this update is also required for building insighttoolkit-4.9. Please sponsor the package, or if Steve doesn't object, give me the upload permissions. Once the new

Re: ginkgocadx ...The good, the bad, and the ugly

Hi, just wanted to give you the heads up on how this goes: The good: I got it to build and it runs, thumbnails now work, and also the loading of the borked dicom file (thanks to Matheu's patch for GDCM). The bad: This was all done on Gentoo, because the current versions of VTK and GDCM

Re: ginkgocadx ...

Hello Michael, > As one of the DCMTK developers I maybe can help (or contact the > adequate person of the DCMTK team), so let me know what kind of > problems you encountered. Nice, here they are: (1) UID_FINDGeneralPurposeWorklistInformationModel is gone (no changelog entry though) My

Re: ginkgocadx ...

Hi Karsten, On Thu, 2016-01-28 at 21:27 +0100, Karsten Hilbert wrote: [...] > and upstream is no more. > What is your source of information that says upstream is no more? On the Gonkgo CADX web page [1], the at least update the page copyright year to 2016, and on the sourceforge projects page

Re: ginkgocadx ...

+0100, Karsten Hilbert wrote: > On Thu, Jan 28, 2016 at 08:54:50PM +0100, Gert Wollny wrote: > Unfortunately, it currently doesn't do what it is supposed to > (there's a bug) and upstream is no more. I also had a look at that bug report [1], and I think I found the culprit, I'm not sure how

ginkgocadx ...

Hi all, I've updated the ginkgocadx package to make it compile with VTK6 and DCMTK-3.6.1-20150924. There are some problems, however: Some of the changes for the VTK6 transition are guess-work, and since I have no idea what the program is actually supposed to do, I can not test whether the

Re: No rule to make target 'ITKCommon_LIB-NOTFOUND', needed by 'lib/libfwItkIO.so.0.1'

Hello, On Mon, 2016-01-18 at 09:45 +0100, Corentin Desfarges wrote: > This log ? [snip] Where did you get this log from? It seems to contain mostly the CXX feature tests but I don't see any library detection. I was more thinking along the lines of the log you get when you run cmake

Re: No rule to make target 'ITKCommon_LIB-NOTFOUND', needed by 'lib/libfwItkIO.so.0.1'

On Mon, 2016-01-18 at 12:16 +0100, Corentin Desfarges wrote: > I'm not sure my previous mail has been correctly sent. Maybe it was > too big... > The cmake log is available there : http://pastebin.com/1pmrgv90 ; That gives some pointers, on one hand the log doesn't contain much of ITK, but I also

Re: No rule to make target 'ITKCommon_LIB-NOTFOUND', needed by 'lib/libfwItkIO.so.0.1'

On Fri, 2016-01-15 at 17:30 +0100, Corentin Desfarges wrote: > Hi everybody > > I'm still working on the packaging of the new upstream release of > FW4SPL. > > Today, I get this errror : > > > make[3]: *** No rule to make target 'ITKCommon_LIB-NOTFOUND', > > needed by 'lib/libfwItkIO.so.0.1'.

sponsoring or upload rights: itksnap

Dear all, I've updated itksnap in the team-git to now use libdcmtk-dev. This upload will also update the dependencies to the latest version of ITK and gdcm. Please sponsor this package or give me upload rights. I didn't add closes for #777921 or #789931 - #777921 actually looks like an

Re: sponsoring or upload rights: itksnap

Hello Michael, >@Gert: FTR it build fine for me. If you are building it again for > upload, you could consider killing the menu file, as having both menu > and desktop files in a package is no longer wanted. Done and uploaded. I notes that the maintainer list e-mail is actually

Re: Fwd: orthanc REMOVED from testing

Hello all, Since I'm in the same situation as Sébastien, I did a bit of digging: > > * dcmtk fails to build on m68k [1], due to a qemu error [2, look for > "qemu: unhandled CPU exception"] But AFAIK, m68k is not a release arch, so should an error like this really hinder migration? merry

Re: fw4spl : undefined reference to itk:: ...

On Wed, 2015-12-23 at 10:27 +0100, Andreas Tille wrote: > On Wed, Dec 23, 2015 at 10:04:58AM +0100, Corentin Desfarges wrote: > > Ok I just saw (and remembered) that insighttoolkit3 has been > > requested to > > be removed. > > Does this mean we have to make FW4SPL compatible with the last ITK > >

Re: transitions and binnmu

Hi Andreas, > I'd suggest we migrate all our packages manually to be sure. Well, for insighttoolkit4 I request a binnmu, this build occupies the computer for 12+ hours, the others in debian-med I'll do manually. > Please let me know if you need more upload permissions. For now this would

Re: transitions and binnmu

On Sun, 2015-12-20 at 14:17 +0100, Karsten Hilbert wrote: > > For now this would be aeskulap. > > Yay, hands up !! Actually, I just saw that packages like amide and aeskulap were already build against the latest dcmtk. https://release.debian.org/transitions/html/auto-dcmtk.html So it seems

Re: transitions and binnmu

On Sun, 2015-12-20 at 16:31 +0100, Karsten Hilbert wrote: > On Sun, Dec 20, 2015 at 04:07:40PM +0100, Gert Wollny wrote: > > > Actually, I just saw that packages like amide and aeskulap were > > already > > build against the latest dcmtk. > > > > https://rele

transitions and binnmu

Hi all, now that I took some more responsibility, i.e. also for gdcm and dcmtk I'm wondering about one detail: with the changed SO-versions of these packages should I request BinNMUs or is this done automatically. For example I see a auto-dcmtk transition but not auto-gdcm. I've read the

dicom3tools mayhem bugs

Dear all, I'm busy fixing #715786, #715809, #715811, and while I'm on it I'll also move packaging to git. Later on I will ask for sponsoring or upload rights :) Best, Gert

Re: [MoM] Re: bart - tools for computational magnetic resonance imaging

On Mon, 2015-12-07 at 08:58 +, Ghislain Vaillant wrote: > You could use something like libgsl0-dev | libgsl-dev to stay > compatible with earlier versions? This should probably be the other way around, i.e. libgsl-dev | libgsl0-dev so that the new package takes precedence. Best,

Sponsoring request vtk-dicom-0.7.1

Dear all, I've prepared the new upstream version of vtk-dicom for upload. Notable changes: * Move to git: git://git.debian.org/debian-med/vtk-dicom.git * New SONAME * Builds against vtk6, Closes: #803595 * Disable java bindings because they depends on the (non-existing) vtk-java

Sponsoring request DCMTK-3.6.1~20150924

Dear all, I've prepared the new upstream snapshot of dcmtk. Important changes are: - the package is now build in git [1] - upstream dropped the www support, i.e. the removed the related perl scripts and programs from the source. Hence the package dcmtk-www will no longer be build. -

Removal of mummy and activiz.net

Hi all, considering that these two packages won't see any fixes, (they require the abandoned gccxml), I guess that apart from tagging the related bugs as wontfix (done), I also should request the removal of the packages. What I'm wondering now is how this is done for a team packages? Since I

  1   2   3   >