On Tue, Sep 6, 2016 at 4:06 PM, Andreas Tille wrote:
[Paul, I wonder whether you realised the problems with opensurgsim]
Thanks for the heads up. Graham's GCC6 patch works for me. I'll get it
applied upstream.
Hi Graham,
On Thu, Aug 25, 2016 at 02:37:53PM +0200, Graham Inggs wrote:
Hi M
On Tue, 2015-10-27 at 11:20 +, Chris Lamb wrote:
> Source: opensurgsim
> Version: 0.6.0-3
> 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 M
On Fri, 11 Sep 2015 17:26:12 -0400 "Aaron M. Ucko"
wrote:
> Source: opensurgsim
> Version: 0.6.0-2
> Severity: important
> Justification: fails to build from source
>
> Builds of opensurgsim on mips, mipsel, and s390x all failed with
> errors in SurgSimFrameworkTest's TimerTest, along the followi
On Fri, 11 Sep 2015 14:44:15 -0400 "Aaron M. Ucko" wrote:
> Source: opensurgsim
> Version: 0.6.0-2
> Severity: serious
> Justification: fails to build from source
>
> The i386 and powerpc builds of opensurgsim both failed because many
> tests reported errors of the form
>
> SurgSim*Test: /usr/incl
gelog 2015-04-26 15:45:00.0 -0400
+++ yaml-cpp-0.5.2/debian/changelog 2015-08-04 15:08:28.0 -0400
@@ -1,3 +1,10 @@
+yaml-cpp (0.5.2-2) unstable; urgency=medium
+
+ * Rename libyaml-cpp0.5 to libyaml-cpp0.5v5 for gcc5 transition
+(Closes: #791317)
+
+ -- Paul Novotny Tue, 04 Aug 2015
Package: debian-maintainers
Severity: normal
Tags: patch
Please add my key to the Debian keyring. jetring changeset is attached.
Comment: Add Paul Novotny as a Debian Maintainer
Recommended-By:
Andreas Tille
Agreement:
http://lists.debian.org/debian-newmaint/2015/07/msg1.html
Hello, it looks like yaml-cpp 0.5.2 is not binary compatible with 0.5.1.
abi-compliance-checker confirms this. I did not notice this when I
updated the yaml-cpp package to 0.5.2. librivet11 may also be affected
by this bug, I will investigate.
-Paul
--
To UNSUBSCRIBE, email to debian-bugs-dist-
On Tue, 2015-03-17 at 14:53 +0100, Matthias Klose wrote:
> Package: src:insighttoolkit4
> Version: 4.6.0-3
>
> insighttoolkit is only built on amd64 and i386, while insighttoolkit3 worked
> on
> some more architectures. any reason for not trying to build that? Sure, it
> needs 50g - 100g disk f
Package: wnpp
Severity: wishlist
Owner: Paul Novotny
* Package name: opensurgsim
Version : 0.6.0
Upstream Author : Paul Novotny
* URL : http://www.opensurgsim.org/
* License : Apache 2.0
Programming Lang: C++
Description : A free platform for surgical
Attached are 2 patches that will allow ITKVTKGLUE to be turned back on.
They make the ITKVTKGLUE module compatible with vtk 5.8. The first
patch, insighttoolkit.patch, actually needs to be applied to the
insighttoolkit source. The second patch, wrapitk.patch, is for the
wrapitk-python source.
dif
Package: libvtkedge-dev
Version: 0.2.0~20110403-1
Severity: important
Tags: patch
This package needs to include the template files(*.txx) along with the header
files. I have included a patch that adds these files.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT polic
These are probably all caused by out of memory issues. Compiling this
package with the new WrapITK python wrappings uses a lot of memory. It
uses all my 8GB plus a little virtual memory on my machine (amd64).
Although I use 3 cores.
Increasing the memory (as Dominique showed above) or limiting the
Package: libvtkedge-dev
Version: 0.1.0-2
Severity: important
Tags: patch
When including vtkedge in a cmake based project, VTKEdgeConfig.cmake
is used to load the configuration of libvtkedge. In particular it
contains the location of UseVTKEdge.cmake. Because of the way this
package is created, Us
13 matches
Mail list logo
