Dear all,
now that itk-4.5 is in unstable I was wondering how is the status on
compiling in the python support?
Since we need this I will put some effort into getting the python-itk
package, but there are lot of options regarding the python bindings
(dimensions, supported pixel types, ...) s
I would like to appropriately thank [1] the packagers that have put
the effort in making this happen, and re-iterate that collaborations
with upstream for any issues that arise are welcome and encouraged.
Thanks,
Matt
[1] http://opensource.com/business/14/2/thank-a-linux-packager-today
On Fri, F
Hello,
I've seen that fftw is currently disabled. Since the last related mail
about this is from 2012/04/24
https://lists.debian.org/debian-med/2012/04/msg00089.html
I would re-enable it and see how it goes. If it still fails on i386
would there it be okay to enable fftw only on amd64?
To document a bit where I stand with this endeavor: so far I hit three
problems,
the first is a cmake bug:
http://public.kitware.com/Bug/view.php?id=13794,
Indicator: all python test fail.
The workaround is to set the preferred python version on the cmake
command line.
The second one se
On Wed, Feb 26, 2014 at 6:06 PM, Gert Wollny wrote:
> To document a bit where I stand with this endeavor: so far I hit three
> problems,
>
> the first is a cmake bug:
>
>http://public.kitware.com/Bug/view.php?id=13794,
>
> Indicator: all python test fail.
> The workaround is to set the preferr
Hello Matt,
On 02/27/14 04:51, Matthew McCormick wrote:
This is a long standing issue that effects many projects. I've pushed
a patch to stage based on the comments in the bug report and will do
my best to get it resolved.
Great.
There have been recent patches that address some of these wa
>> There have been recent patches that address some of these warnings. I
>> backported them to the "release" branch, which will become 4.5.2.
>
>
>> The python wrapping is in flux. We could do a short online hackathon
>> to work on remaining issues if you are interested.
>
> I'll get back to you
On Thu, Feb 27, 2014, at 03:55 PM, Matthew McCormick wrote:
> >> The python wrapping is in flux. We could do a short online hackathon
> >> to work on remaining issues if you are interested.
> >
> > I'll get back to you on this, but probably only next week.
Let me know if you schedule something. I
On 03/01/14 17:34, p...@paulnovo.us wrote:
On Thu, Feb 27, 2014, at 03:55 PM, Matthew McCormick wrote:
The python wrapping is in flux. We could do a short online hackathon
to work on remaining issues if you are interested.
I'll get back to you on this, but probably only next week.
Let me kn
Hi,
it seems all test pass now and the python package builds.
I've uploaded the current state to a branch:
svn.debian.org/svn/debian-med/trunk/packages/insighttoolkit/branches/itk4-enable-python
in case someone wants to have a look.
There will only be support for python-2.7, it doesn't seem t
On Sat, Mar 1, 2014 at 11:34 AM, wrote:
> On Thu, Feb 27, 2014, at 03:55 PM, Matthew McCormick wrote:
> > >> The python wrapping is in flux. We could do a short online hackathon
> > >> to work on remaining issues if you are interested.
> > >
> > > I'll get back to you on this, but probably only
On March 4, 2014 02:38:51 PM Gert Wollny wrote:
> Hi,
>
> it seems all test pass now and the python package builds.
That's fantastic! Thanks for doing this.
> I've uploaded the current state to a branch:
>
> svn.debian.org/svn/debian-med/trunk/packages/insighttoolkit/branches/itk4-en
able-p
Hello,
>> I haven't tested to build it in a pbuilder environment yet. I'll get
back to you when this is done in for i386 and amd64, Just running these
which will probably take two more days.
amd64 run fine, but i386 hit a (known) problem, gccxml can not parse
__float128:
http://public.kitwa
On Fri, 2014-03-07 at 12:08 +0100, Gert Wollny wrote:
> Hello,
>
> >> I haven't tested to build it in a pbuilder environment yet. I'll get
> >> back to you when this is done in for i386 and amd64, Just running these
> >> which will probably take two more days.
>
> amd64 run fine, but i386 hit a
Hello Paul,
> Gert, would you mind if I merged your current rules file with what we
had back in itk 3? When we last had wrapitk python packages?
That's fine with me. I've committed all my changes to the branch
"itk4-enable-python"
My personal preference would have been to get this package
On Fri, Mar 07, 2014 at 12:08:54PM +0100, Gert Wollny wrote:
> Hello,
>
> >> I haven't tested to build it in a pbuilder environment yet. I'll get
> >>back to you when this is done in for i386 and amd64, Just running these
> >>which will probably take two more days.
>
> amd64 run fine,
That's go
Hi,
On Fri, 2014-03-07 at 11:34 -0600, Steve M. Robbins wrote:
> On Fri, Mar 07, 2014 at 12:08:54PM +0100, Gert Wollny wrote:
> That's good news. But, oddly, I tried a pbuilder build of your branch
> and it failed for me. I think it encountered an Internal Compiler Error.
The cowbuilder enviro
Hello Steve,
just wanted to mention that my last revision r16399 built on both amd64
and i386 sid. I've never done a merge on svn so I'd leave it to you to
merge the branch itk4-enable-python into the main trunk.
It may be that the gccxml requirement is now a bit strict, but this is
only imp
On March 12, 2014 04:40:35 PM Gert Wollny wrote:
> Hello Steve,
>
> just wanted to mention that my last revision r16399 built on both amd64
> and i386 sid.
OK, great! I noticed a discrepancy between control.in and control so I re-
generated and checked-in the latter. Running a build now...
> I
On March 12, 2014 11:16:05 PM Steve M. Robbins wrote:
> On March 12, 2014 04:40:35 PM Gert Wollny wrote:
> > Hello Steve,
> >
> > just wanted to mention that my last revision r16399 built on both amd64
> > and i386 sid.
>
> OK, great! I noticed a discrepancy between control.in and control so I r
On 03/18/14 02:19, Steve M. Robbins wrote:
On March 12, 2014 11:16:05 PM Steve M. Robbins wrote:
On March 12, 2014 04:40:35 PM Gert Wollny wrote:
Sorry, it seems I didn't run lintian at all - spoiled from
git-buildpackage which does it always I forgot to run it manually. Now
I've configured
Hi Steve,
the latest upload should now work with only three lintian warnings left,
> W: insighttoolkit4 source: changelog-should-mention-nmu
W: insighttoolkit4 source: source-nmu-has-incorrect-version-number 4.5.1-1
These two you can ignore as I'll fix the changelog to be a non-NMU upload.
Hi Steve,
as expected cowbuilder did run through without problems for the latest
upload and i386 + amd64, and the only lintian warning I see is
* libinsighttoolkit4-dev: binary-without-manpage usr/bin/itkTestDriver
lintian infos are:
libinsighttoolkit4.5:
spelling-error-in-binary
hardeni
On Wed, 2014-03-26 at 12:10 +0100, Gert Wollny wrote:
>"-Wall -Wextra -Wdeprecated-declarations -O2 -g -funroll-loops
> -ftree-vectorize -pthread -march=native -mtune=native"
>
> in the shell, and when I don't undefine these before running
> svn-buildpackage they are actually used, resulting
On Wed, 2014-03-26 at 11:51 -0400, Paul Novotny wrote:
> On Wed, 2014-03-26 at 12:10 +0100, Gert Wollny wrote:
> >"-Wall -Wextra -Wdeprecated-declarations -O2 -g -funroll-loops
> > -ftree-vectorize -pthread -march=native -mtune=native"
> >
> > in the shell, and when I don't undefine these bef
On March 26, 2014 12:10:13 PM Gert Wollny wrote:
> Hi Steve,
>
> as expected cowbuilder did run through without problems for the latest
> upload and i386 + amd64, and the only lintian warning I see is
>
> * libinsighttoolkit4-dev: binary-without-manpage usr/bin/itkTestDriver
OK, thanks! I'll ru
On March 27, 2014 12:43:47 AM Steve M. Robbins wrote:
> On March 26, 2014 12:10:13 PM Gert Wollny wrote:
> > Hi Steve,
> >
> > as expected cowbuilder did run through without problems for the latest
> > upload and i386 + amd64, and the only lintian warning I see is
> >
> > * libinsighttoolkit4-dev
> > OK, thanks! I'll run a build and upload.
>
> Mmm. It failed again:
>
> The following tests FAILED:
> 1813 - itkSimpleImageRegistrationTestFloat (Failed)
> Errors while running CTest
No, I didn't see this, never.
> I have an amd64 system but did the build in a 32-bit chroot. This
Hi,
> I will let it run and then we will see if this upgrade introduces some
> regression.
Well, the build run through without problems (non-parallel build).
You wrote that the last time you needed various attempts to build it. My
next guess would be that you might have a hardware problem ...
On March 27, 2014 10:24:56 AM Steve M. Robbins wrote:
> On March 27, 2014 12:43:47 AM Steve M. Robbins wrote:
> > On March 26, 2014 12:10:13 PM Gert Wollny wrote:
> > > Hi Steve,
> > >
> > > as expected cowbuilder did run through without problems for the latest
> > > upload and i386 + amd64, and t
30 matches
Mail list logo
