Package: fenics
Version: 1:2017.1.0.1
Severity: minor
Hi,
I tried to install the Suggested and Recommended packages, but found two are
non-existent.
python-scitools: appears to have existed at one time, but now removed from
Debian; see
Package: python-sfepy
Version: 2016.2-2
Severity: normal
I tried to run the examples using:
sfepy-run simple examples/diffusion/poisson_short_syntax.py
and obtained:
sfepy: left over: ['verbose', '__builtins__', '__file__', '__doc__',
'__name__', 'data_dir', '__package__', '_filename']
On Tuesday, November 15, 2016 1:02:10 AM CST Santiago Vila wrote:
> Package: librospack-dev,libgtest-dev,src:ros-image-common
> Severity: serious
>
> Dear maintainer:
>
> I tried to build ros-image-common in stretch with "dpkg-buildpackage -A"
> (which is what the "Arch: all" autobuilder would
On Monday, June 27, 2016 12:38:45 PM CDT Chris Lamb wrote:
> please clarify src/ipelib/ipebitmap.cpp
Can I request that you ask a more specific question, please?
Thanks,
-Steve
signature.asc
Description: This is a digitally signed message part.
--
debian-science-maintainers mailing list
Package: diet
Severity: normal
Boost 1.55 has not built correctly since the GCC 5 introduction in July 2015
and I plan
to ask for its removal from unstable very shortly. It has already been removed
from
testing.
The package diet appeared on a list of reverse dependencies generated
using 'dak
Package: limereg
Severity: normal
Boost 1.55 has not built correctly since the GCC 5 introduction in July 2015
and I plan
to ask for its removal from unstable very shortly. It has already been removed
from
testing.
The package limereg appeared on a list of reverse dependencies generated
Well,
Thank you.
On April 21, 2014 04:56:21 PM Niels Möller wrote:
Magnus Holmgren holmg...@debian.org writes:
Oh well, I went ahead and did it for you. However, as you can see, some
symbols went missing in both 5.1 and 6.0.
Are those the ones in the #MISSING: lines in your file? They
On Sat, Apr 12, 2014 at 07:08:35PM +0200, Benjamin Eltzner wrote:
I have no idea, whether this bug is in the package or in the upstream
library. If it concerns upstream, I would be very glad if you forwarded
it and set me to CC.
There is only one tiny patch to gmp in this version: to disable
On April 1, 2014 08:59:13 AM you wrote:
As explained in details libs have different SONAME (vtkCommon !=
vtkCommonCore) however they provide the same symbols (up to the ABI
diff). This is bad (tm) !
Sorry, what details are you referring to?
-Steve
signature.asc
Description: This is a
On April 1, 2014 09:12:24 AM Anton Gladky wrote:
2014-03-31 10:58 GMT+02:00 Mathieu Malaterre ma...@debian.org:
Typical scenarios that should not happen is an app linked against
vtkCommon and vtkCommonCore. This gets even worst with python
$ python
import vtkCommon
import
On March 31, 2014 10:58:28 AM Mathieu Malaterre wrote:
Package: libvtk6
Clearly there is something missing here. libvtk6 can be co-installed
with libvtk5.8. VTK API (ABI too) is completely incompatible in
between those two versions.
Clearly I'm missing something, because it is routine to
AM, Leopold Palomo-Avellaneda l...@alaxarxa.net
wrote:
A Dimecres, 5 de març de 2014, Steve M. Robbins va escriure:
On March 3, 2014 09:22:01 AM Leopold Palomo-Avellaneda wrote:
[1] https://svn.boost.org/trac/boost/ticket/8731
[2] https://svn.boost.org/trac/boost/changeset/84950
12 matches
Mail list logo
