On Sat, Jan 16, 2016 at 06:41:26PM +0100, Gert Wollny wrote:
> > >dcut dm --uid "Gert Wollny" --allow plastimatch
> >
> > well, I wouldn't give out DM powers to somebody I've never heard
> > about before :) (and for sure using name/surname as a uid...)
> > sorry.
> No worries, that was more
> https://buildd.debian.org/status/package.php?p=plastimatch
>
> this was done today (I didn't notice it).
> So, amd64 and i386 succeeded, but all the other failed.
> nice. no ^^
>
> Do you know something about this too?
Well, I'm not sure what are the problems there in the actual build, it
se
On Sat, Jan 16, 2016 at 06:14:51PM +0100, Gert Wollny wrote:
> Well, there was bug #808491 (now resolved) in ITK+GDCM that made
> builds against ITK fail, that's why I set it as blocker.
ah, ok.
> Andreas Beckmann already requested a NMU (i.e. re-opend the NMU bug
> #808401 I had filed a few da
> Gert seemed to know what was up with this, and TBH I don't really
> understand what he wrote...
Well, there was bug #808491 (now resolved) in ITK+GDCM that made
builds against ITK fail, that's why I set it as blocker.
Andreas Beckmann already requested a NMU (i.e. re-opend the NMU bug
#808401
On Sat, Jan 16, 2016 at 05:25:18PM +0100, Andreas Tille wrote:
> On Sat, Jan 16, 2016 at 02:00:27AM +, Mattia Rizzolo wrote:
> > That bug has now been fixed, can this proceed, then?
> I'm AFK for the next 12+x hours - feel free to do a team upload.
well, I haven't investigated this at all, and
On Sat, Jan 16, 2016 at 02:00:27AM +, Mattia Rizzolo wrote:
> >
> > Well, it turns out that Emilio from the release team already tried to
> > build ITK against the new gdcm.
> >
> > Which means this bug is now blocked by #808491, which is something for
> > which I need help from upstream ITK
On Sun, Dec 20, 2015 at 03:19:16PM +0100, Gert Wollny wrote:
> On Sat, 2015-12-19 at 22:55 +0100, Andreas Tille wrote:
> > Hi Gert,
> >
> > On Sat, Dec 19, 2015 at 09:32:58PM +0100, Gert Wollny wrote:
> > > It seems that there is a conflict in which gdcm version is used.
> > > The log says that g
On Sat, 2015-12-19 at 22:55 +0100, Andreas Tille wrote:
> Hi Gert,
>
> On Sat, Dec 19, 2015 at 09:32:58PM +0100, Gert Wollny wrote:
> > It seems that there is a conflict in which gdcm version is used.
> > The log says that gdcm-2.6 was found but later the include files
> > for gdcm-2.4 are used.
Hi Gert,
On Sat, Dec 19, 2015 at 09:32:58PM +0100, Gert Wollny wrote:
> It seems that there is a conflict in which gdcm version is used. The
> log says that gdcm-2.6 was found but later the include files for gdcm
> -2.4 are used.
>
> I guess itk needs to be rebuild against gdcm-2.6 since it seem
It seems that there is a conflict in which gdcm version is used. The
log says that gdcm-2.6 was found but later the include files for gdcm
-2.4 are used.
I guess itk needs to be rebuild against gdcm-2.6 since it seems to pull
in the old version.
Best
Gert
Hi Gregory,
I tried to add libgdcm2-dev as additional Build-Depends since the header
file is part of this package but this was to simple as a fix and did not
worked.
Could you find a better fix?
Kind regards
Andreas.
On Sat, Dec 19, 2015 at 05:26:09PM +, Chris Lamb wrote:
> Source:
Source: plastimatch
Version: 1.6.2+dfsg-2
Severity: serious
Justification: fails to build from source
User: reproducible-bui...@lists.alioth.debian.org
Usertags: ftbfs
X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
Dear Maintainer,
plastimatch fails to build from source in unstable/amd
12 matches
Mail list logo
