The bug is also in Debian's slurm-llnl package. The location of the header
files is not consistent anymore.
slurm.h is including
See
https://anonscm.debian.org/git/collab-maint/slurm-llnl.
git/commit/debian/libslurm-dev.install?id=08c387553a95e9a4a38047c82cf69a
4f733cee0d
https://anonscm.debian.
Package: nlohmann-json
Version: 2.1.1-1
Severity: grave
Some applications don't compile with nlohmann-json 2.1.1 and gcc 7.2 .
You can find details here:
https://github.com/nlohmann/json/issues/742
Please update the package.
Thanks
-Dominique
This happens due to a recent change in debian/libslurm-dev.install
https://anonscm.debian.org/git/collab-maint/slurm-llnl.git/commit/debian/libslurm-dev.install?id=08c387553a95e9a4a38047c82cf69a4f733cee0d
Anyway, I am thinking about removing the slurm-drmaa package from the
Debian archive. The po
You can find some pyside2 packages in following Ubuntu PPA
sudo apt-get install software-properties-common
sudo add-apt-repository ppa:thopiekar/pyside-git
sudo apt-get update
apt-get install python3-pyside2
For a quick test you can try to compile the packages in Debian testing.
# compile and
Package: blt
Version: 2.4z-4.1
Severity: grave
This package is using Tk 8.5 and is responsible for other
bugs like #536702
There is a statement on upstream's homepage
(http://blt.sourceforge.net/) regarding this issue:
"The latest release BLT 2.4z.tar.gz works with Tk versions 8.0, 8.1,
8.2, 8.
Hi,
I packaged ifrit 3.2.8 to close this bug.
Instead of setting VTKDIR explicitly I let cmake search for the
installed version.
chrpath can be used to remove RPath from the binary. But it is easier to
use cmake to skip the RPATH (-D CMAKE_SKIP_RPATH:BOOL=ON)
A NMU package can be found here :
h
Package: slicer
Version: 3.5.0~svn10636-1
Severity: grave
Justification: renders package unusable
$ slicer3
/usr/bin/Slicer3-real: error while loading shared libraries:
libgdcmDICT.so.2.0: cannot open shared object file: No such file or
directory
This seems to be caused by a bug in libgdcm2.0
Hi,
I am going to build sofa against the new available libtinyxml-dev
package in Sid.
Dominique
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi Felix,
thanks for providing a tinyxml package. I am using the package now
instead of a local copy for the sofa-framework package.
On Mon, 2010-03-22 at 11:49 +0100, Felix Geyer wrote:
> I decided to rename the STL variant from tinyxml to tinyxml-stl so no
> one links to it without thinking abo
Hi Mathieu,
You are right. Using /usr/share/java/vtk/vtk.jar solves the problem.
BTW, I was playing with vtk-5.4 in experimental and tried to compile
gdcm. There is another java related problem. I was getting an error
message. Here it is:
---
L
Thanks for the report, I am going to package 0.9.10 to fix the issue.
Dominique
On Tue, Nov 1, 2011 at 3:49 PM, Moritz Muehlenhoff wrote:
> Package: django-tastypie
> Severity: grave
> Tags: security
>
> Please see
> https://www.djangoproject.com/weblog/2011/nov/01/piston-and-tastypie-security-r
reassign 645193 libdrmaa-dev
I added conflicts to the pbs-drmaa package
Conflicts: libdrmaa-dev (<< 6.2u5-3)
Conflicts: libdrmaa1.0 (<< 6.2u5-3)
Upcoming gridengine packages should be renamed so that libdrmaa-dev
can be used as a virtual package.
--
To UNSUBSCRIBE, email to debian-bugs
> /bin/sh: 1: /usr/lib//vtkEncodeString: not found
>
I am going to move vtkEncodeString to /usr/bin where it belongs to.
This will create temporarily a conflict with the current paraview
package.
It looks like that future paraview releases don't ship this file
anymore, so uploading the new paraview
Hi,
I am going to fix this in the libslicer3-dev package with my next
upload. The library /usr/lib/libMRML.so will be moved to a private
location. This should fix the conflict.
Thanks
Dominique
On Fri, 2011-02-25 at 23:58 +0100, Ralf Treinen wrote:
> Package: libmrml1-dev,libslicer3-dev
> Versi
Hi Andreas,
Your patch looks fine. I will postpone the upload of igstk-4.4 and
will upload igstk-4.2.0-4 right now.
FYI, the package builds fine even without the patch. Something has
changed in gcc-4.5 again. ;)
But I will keep your change because it looks cleaner.
Thanks
-Dominique
--
To UN
On Tue, Mar 15, 2011 at 5:14 PM, Mehdi Dogguy wrote:
> >> [ 19%] Generating vtkKWEWireframePainter_vs.cxx /bin/sh:
> >> /usr/bin/vtkEncodeString: not found make[3]: ***
> >> [Rendering/vtkKWEWireframePainter_vs.cxx] Error 127
> >
>
> Looks like this failure is due to a typo in
> /usr/lib/vtk-5.6/
Hi,
this temporary workaround might help.
mv /usr/share/eucalyptus/groovy.jar /usr/share/eucalyptus/groovy.jar.bckup
ln -s /usr/share/java/groovy-all.jar /usr/share/eucalyptus/groovy.jar
Cheers
Dominique
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of
On Tue, 2011-01-18 at 13:55 +0100, Andreas Tille wrote:
> On Tue, Jan 18, 2011 at 11:31:43AM +0100, Julien Cristau wrote:
> > On Tue, Jan 18, 2011 at 11:12:43 +0100, Andreas Tille wrote:
> >
> > > Hi,
> > >
> > > I wonder why there is no answer on this a bit aged serios bug. For me
> > > it smel
#x27; type.
So, how do I set the language compliance level? Or should I use a
different compiler on kfreebsd and hppa?
Cheers
-Dominique
On Sun, 2011-02-20 at 17:00 +0100, Denis Barbier wrote:
> tags 614134 pending
> severity 614134 serious
> thanks
>
> Hi Dominique,
>
Hi Denis,
great, it is working. It compiles well it on kfreebsd-i386.
I looked at the build logs and found this line
/usr/lib/jvm/default-java/bin/javac -source 5
which links to ecj
/usr/lib/jvm/default-java/bin/javac -> /usr/bin/ecj
Since ecj understands the -source option there is no need
I agree that the 2.4 branch is completely outdated. We should switch to a
newer branch.
The 2.5 and 4.1 branches are not suitable for Debian due to licensing
issues.
But the 4.2 branch is licensed under the same license as the 2.4 branch, so
I suggest we upload the 4.2.9 release to unstable.
-Do
On Thu, Oct 30, 2014 at 8:42 PM, Dominique Belhachemi
wrote:
> I agree that the 2.4 branch is completely outdated. We should switch to a
> newer branch.
>
> The 2.5 and 4.1 branches are not suitable for Debian due to licensing
> issues.
>
> But the 4.2 branch is licensed u
Package: libsvm
Version: 3.12-1.1
Severity: serious
The source package contains binary files, see
https://sources.debian.net/src/libsvm/3.12-1.1/windows/
https://sources.debian.net/src/libsvm/3.12-1.1/java/
v3.12 is from 2012, please consider an update to a recent version (
https://github.com/c
I am going to upload a new package tonight.
Upstream removed only the Python 2.6 support, Python 2.7 is still
supported, so I will keep the python2 package.
-Dominique
Package: libinsighttoolkit3.20
Severity: serious
The removal of some vxl binaries causes ANTS and other packages to crash.
You can reproduce the problem by executing ANTS.
$ ANTS
ANTS: error while loading shared libraries: libitkvnl_algo.so.3.20:
cannot open shared object file: No such file or d
Hi Andreas,
You are right, some files have moved (e.g.
/usr/lib/x86_64-linux-gnu/libQtGui.so ). I will patch the code soon.
Cheers
-Dominique
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
There is a long email thread on upstream's mailing list and I am not sure
if we can update to 2.5.
http://www.supercluster.org/pipermail/torquedev/2011-January/003342.html
Let's see what people on debian-legal are thinking.
http://lists.debian.org/debian-legal/2012/01/msg00030.html
Thanks
-Do
Package: paraview
Severity: serious
Please remove Paraview's VTK directory and link instead against
Debian's vtk libraries.
Thanks
-Dominique
On Sat, Jan 7, 2012 at 2:08 PM, Steve M. Robbins wrote:
> On Sat, Jan 07, 2012 at 10:22:36AM +0100, Mathieu Malaterre wrote:
>
>> Really it boils down to two things:
>> - What is upstream position on this ? If upstream really do want to
>> release paraview on fixed schedule, with backward compati
Package: libdrmaa-dev
Severity: important
I added conflicts to the gridengine packages. But the main issue
persists, the package names for gridengine's drmaa implementations are
too general.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Tr
Slicer4 is currently using development versions of pythonqt and ctk.
I have to wait for a new upstream release of those packages before I
can continue working on the slicer4 package.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
The package FTBFS now with:
dpkg-source: info: using source format `3.0 (quilt)'
dpkg-source: info: patches are not applied, applying them now
dpkg-source: info: applying 12_doxygen.diff
dpkg-source: info: applying 34_disable_resource_intensely_tests.diff
dpkg-source: info: applying 90_examples.di
> What architecture is the following log from?
>
> On Sat, Jan 21, 2012 at 05:48:52PM -0500, Dominique Belhachemi wrote:
>> The package FTBFS now with:
>>
>>
>> CMake Warning at /usr/lib/InsightToolkit/UseITK.cmake:53 (FIND_PACKAGE):
>> Could not find module Find
On Sun, Jan 22, 2012 at 1:40 AM, Steve M. Robbins wrote:
> On Sat, Jan 21, 2012 at 11:12:45PM -0500, Dominique Belhachemi wrote:
>> Hi Steve,
>>
>> It occurred in a clean pbuilder environment on amd64 and the build
>> used the latest itk package:
>>
Package: slicer
Severity: serious
Keep Slicer3 out of testing, I am working on Slicer4...
Dominique
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
> Here is a list of files that are known to be shared by both packages
> (according to the Contents file for sid/amd64, which may be
> slightly out of sync):
>
> /usr/include/drmaa.h
> /usr/lib/libdrmaa.so
>
Those files might conflict as well:
/usr/lib/libdrmaa.so.x.y
/usr/lib/libdrmaa.la
/
Hi Moritz,
Thanks for finding the security issue. We are working on a solution.
Jordi, can you help out with the squeeze fix and upload? I think you
have done those things before, right?
Cheers
Dominique
On Mon, Jul 25, 2011 at 8:10 AM, Moritz Muehlenhoff wrote:
> Package: torque
> Severity:
clone 621950 -1 -2
reassign -2 libgtk2.0-dev
block -1 -2
On Sat, 9 Apr 2011, Lucas Nussbaum wrote:
Building C object CMakeFiles/z88g.dir/clr88.c.o
In file included from /usr/include/gtk-2.0/gdk/gdkcairo.h:28:0,
from /usr/include/gtk-2.0/gdk/gdk.h:33,
from /usr
Here is a test on a 64 bit GNU/kFreeBSD virtual machine.
### 1 ###
VM with 1GB memory.
The bottleneck seems to be the python wrapping for
"itkImageToImageFilterBPython". I am getting the error
virtual memory exhausted: Cannot allocate memory
[ 22%] Building CXX object
Wrapping/WrapITK/Modu
With 4GB of memory it compiles until here:
$ make
[SNIP]
[ 92%] Building
/home/domibel/insighttoolkit-3.20.0/obj-x86_64-kfreebsd-gnu/Wrapping/WrapITK/Java/InsightToolkit/VXLNumericsJava.class
cd
/home/domibel/insighttoolkit-3.20.0/obj-x86_64-kfreebsd-gnu/Wrapping/WrapITK/Java
&& /usr/bin/javac -c
Hi,
What is preferred by the release team?
a) Upload 5.8.0-9 with a cherry picked fix from vtk-5.10.0-rc1
b) Uploading the fresh release candidate vtk-5.10.0-rc1
c) Waiting for vtk-5.10.1 ?
I would go for a) followed by c).
-Dominique
On Sat, Apr 7, 2012 at 5:13 AM, Adam D. Barratt
wrote:
>
, Yaroslav Halchenko wrote:
> Hi Dominique,
>
> Could you please refresh my memory on the status of slicer in Debian?
>
> Would you need help in maintaining it (e.g. to push forward packaging of
> slicer4) etc?
>
> Thank you in advance!
> Yaroslav
>
> On Fri, 04 May
I am going to upload a simple workaround very soon. I just have to
update patches/110-kernel.diff .
-Dominique
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
I updated pbs-drmaa and slurm-drmaa to use Debian's alternative system.
I would like to do the same with the current libdrmaa1.0 package which
is gridengine specific. To stay compatible to the other
implementations I would like to change some binary package names as
well.
libdrmaa1.0 -> gridengin
Hi Yaroslav,
Slicer3 is not supported by upstream anymore.
Slicer4 is only supported on amd64 and is still based on non released
projects (VTK 5.10, CTK, PythonQt). Slicer4 also comes with a
pre-build launcher binary which has to be replaced by our own launcher
script.
Cheers
-Dominique
On Fri
Package: bamtools
Version: 2.4.0+dfsg-2
Severity: grave
This bug affects big endian systems (mips, powerpc, ...) . It is not
possible to handle bam files.
Here is a quick test case:
$ bamtools count -in test.bam
bamtools count ERROR: could not open input BAM file(s)... Aborting.
I filed a bug
On Sun, May 29, 2011 at 4:12 AM, Mehdi Dogguy wrote:
> Do you mind if we NMU your package, or do you intend to upload a fixed version
> really soon?
>
Hi Mehdi,
I don't mind at all. Please go ahead with the NMU.
Dominique
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
wi
Based on ( https://github.com/celery/librabbitmq#installation ) I should be
able to run a quick example:
>>> from librabbitmq import Connection
>>> conn = Connection(host="localhost", userid="guest",
... password="guest", virtual_host="/")
>>> channel = conn.channel()
>>> chann
I am surprised to see a vtk6 package in unstable. Please remove it and test
it in experimental.
-Dominique
Package: openigtlink
Version: 1.10.4~git20131104+3ac531115f-2
Severity: grave
https://github.com/openigtlink/OpenIGTLink/issues/29
Applications which include igtl_util.h (e.g.
OpenIGTLinkIF/MRML/vtkIGTLToMRMLImage.cxx) fail to build due to a missing
file:
/usr/include/openigtlink/igtl_util.h:19
Hi Andreas, please go ahead with the upload.
-Dominique
Hi Andreas,
I think you are right, this is a good time to go forward with the removal
request.
-Dominique
On Aug 21, 2014 3:54 AM, "Andreas Tille" wrote:
> Hi,
>
> as you might have noticed igstk is RC buggy and also lagging behind
> upstream (5.2). If nobody has any interest in keeping the pa
Thanks Gianfranco,
If you have some time, could you please help Anton with vtk6?
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747108
-Dominique
Package: cmake
Version: 2.8.12.1-1.1
Severity: serious
Please drop patch:
http://anonscm.debian.org/gitweb/?p=collab-maint/cmake.git;a=blob;f=debian/patches/multiarch-python-include-dirs.diff;hb=master
With the patch, other cmake based projects fail to build whenever
PYTHON_INCLUDE_DIR is us
Hi Luca,
Yes please, go ahead. I will add it back once it is buildable again.
-Dominique
On May 13, 2013 10:54 AM, "Luca Falavigna" wrote:
> Hi Dominique!
>
> slicer3 is one of the packages needed to be rebuilt to get rid of
> python2.6 dependencies. As it currently FTBFS, I wonder whether it
>
55 matches
Mail list logo
