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
On 06/03/14 15:07, Ubiratan S. Freitas wrote:
> On Thu, Mar 6, 2014 at 2:30 PM, Iain R. Learmonth wrote:
>> Thanks for offering to package this. (:
> My pleasure! I can only hope I am up to the task.
I can offer some help if you require it.
Have you read the Debian Med Group Policy yet? You can
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
Dear all,
a new version of elastix is out for some time, and because of the
changed dependencies of the lib-ITK package the currently available
version is broken (it wasn't linked with --as-needed and now needs some
libraries that are no longer provided by ITK)
Which means I will now prepare
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
Steve,
I noticed that itk is only being built on i386 and amd64 at the moment.
I haven't been keeping up with itk in debian for a bit, but is this due
to the failures we were seeing on big endian machines last summer?
Can we turn on the other architectures to get an idea of what issues
still rem
Hi Gert,
On Fri, Mar 07, 2014 at 05:37:25PM +0100, Gert Wollny wrote:
> a new version of elastix is out for some time, and because of the
> changed dependencies of the lib-ITK package the currently available
> version is broken (it wasn't linked with --as-needed and now needs
> some libraries that
Hi,
On Fri, Mar 07, 2014 at 11:23:38PM +0100, Andreas Tille wrote:
> I know that some people worked on Jmaol at Debian Med sprint. Does
> this work solve any of the problems mentioned below?
>
> I think we should not simply drop Jmol.
Just to be clear, I will not let it happen that Jmol gets dr
Hi,
I know that some people worked on Jmaol at Debian Med sprint. Does this
work solve any of the problems mentioned below?
I think we should not simply drop Jmol.
Kind regards
Andreas.
- Forwarded message from Michael Banck -
Date: Fri, 7 Mar 2014 19:37:01 +0100
From: Michae
+1 for Matt's suggestion of setting up a Nightly build
submitting to the ITK dashboard.
That's a great way to ensure that we follow up on the issue.
We will be happy to help get ITK available in more
architectures in Debian.
Thanks a lot for your hard work on packaging ITK !
Luis
12 matches
Mail list logo