Your message dated Thu, 29 Jun 2017 17:21:34 +0200
with message-id <df97ab3e-0de3-2208-a763-de8450328...@debian.org>
and subject line Re: libpetsc3.7.5-dev: uninstallable on current sid
has caused the Debian Bug report #865526,
regarding libpetsc3.7.5-dev: uninstallable on current sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
865526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865526
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpetsc3.7.5-dev
Version: 3.7.5+dfsg1-4+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
since openmpi was upgraded in sid, libpetsc3.7.5-dev and libpetsc3.7.6-dev
became uninstallable on sid, since they depend on libopenmpi-dev (< 2.0.3).
I tried compiling the package from source but it gets stuck precisely when
checking mpi. Upon further checking it looks like the openmpi development
environment on my laptop is broken, despite all packages appear to be
correctly installed: many libs are installed only under
/usr/lib/x86_64-linux-gnu/openmpi/lib, with no soft links to
/usr/lib/x86_64-linux-gnu (even if running dpkg -L libopenmpi2 says they
should be!).
Any chance to have petsc-dev installable again soon? petsc and slepc are
key dependencies of my quite a bit of my home-developed scientific software.
Any suggestion for a quick-n-dirty fix to get it to compile with the newer
openmpi?
Thanks in advance. I'll let you know if/when I can compile a working petsc
package from source.
Bye
Giacomo
-- System Information:
Debian Release: 9.0
APT prefers buildd-unstable
APT policy: (400, 'buildd-unstable'), (401, 'unstable'), (10, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.25-jak (SMP w/4 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) (ignored: LC_ALL
set to it_IT.utf8), LANGUAGE=it_IT.utf8 (charmap=UTF-8) (ignored: LC_ALL set to
it_IT.utf8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libpetsc3.7.5-dev depends on:
ii gfortran 4:6.3.0-4
ii libblacs-mpi-dev 1.1-40
ii libfftw3-dev 3.3.6p2-1
ii libfftw3-mpi-dev 3.3.6p2-1
ii libhdf5-mpi-dev 1.10.0-patch1+docs-3
ii libhypre-dev 2.11.1-3
ii libmumps-dev 4.10.0.dfsg-4+b2
ii libopenmpi-dev 2.1.1-4
ii libpetsc3.7.5 3.7.5+dfsg1-4+b1
ii libptscotch-dev 5.1.12b.dfsg-2.1
ii libscalapack-mpi-dev 1.8.0-14
ii libspooles-dev 2.2-12+b1
ii libssl-dev 1.1.0f-3
ii libsuitesparse-dev 1:4.5.5-1
ii libsuperlu-dev 5.2.1+dfsg1-2
ii python 2.7.13-2
Versions of packages libpetsc3.7.5-dev recommends:
ii csh [c-shell] 20110502-2.2+b1
ii ksh 93u+20120801-3.1
ii mksh 54-2+b4
ii tcsh [c-shell] 6.20.00-7
ii zsh 5.3.1-5
Versions of packages libpetsc3.7.5-dev suggests:
pn libluminate-dev <none>
pn libpetsc3.7.5-dbg <none>
pn petsc-dev <none>
ii petsc3.7.5-doc 3.7.5+dfsg1-4
--- End Message ---
--- Begin Message ---
> since openmpi was upgraded in sid, libpetsc3.7.5-dev and libpetsc3.7.6-dev
> became uninstallable on sid, since they depend on libopenmpi-dev (< 2.0.3).
> I tried compiling the package from source but it gets stuck precisely when
> checking mpi. Upon further checking it looks like the openmpi development
> environment on my laptop is broken, despite all packages appear to be
> correctly installed: many libs are installed only under
> /usr/lib/x86_64-linux-gnu/openmpi/lib, with no soft links to
> /usr/lib/x86_64-linux-gnu (even if running dpkg -L libopenmpi2 says they
> should be!).
>
> Any chance to have petsc-dev installable again soon? petsc and slepc are
> key dependencies of my quite a bit of my home-developed scientific software.
> Any suggestion for a quick-n-dirty fix to get it to compile with the newer
> openmpi?
if you want it being installable, just stop using sid.
sid is meant for transitions, so stuff is uninstallable from time to time.
You can email release team if you want openmpi to migrate faster
G.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--
debian-science-maintainers mailing list
debian-science-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
