Your message dated Tue, 21 Feb 2017 10:24:27 +0800 with message-id <[email protected]> and subject line Re: nmu: petsc_3.7.5+dfsg1-4 has caused the Debian Bug report #854905, regarding nmu: petsc_3.7.5+dfsg1-4 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 [email protected] immediately.) -- 854905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854905 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: libpetsc3.7.5-dev Severity: grave Hi. Currently libpetsc3.7.5-dev is uninstallable. Sbuild resolver says: missing: pkg: package: libpetsc3.7.5-dev version: 3.7.5+dfsg1-4 architecture: amd64 unsat-dependency: libopenmpi-dev:amd64 (< 2.0.2~git.20161226) depchains: - depchain: - package: sbuild-build-depends-sundials-dummy version: 0.invalid.0 architecture: amd64 depends: libpetsc3.7-dev:amd64 - package: libpetsc3.7-dev version: 3.7.5+dfsg1-4 architecture: amd64 depends: libpetsc3.7.5-dev:amd64 Which is true, because libpetsc3.7.5-dev has Depends: libopenmpi-dev (>= 2.0.2~git.20161225), libopenmpi-dev (<< 2.0.2~git.20161226) But the only available libopenmpi-dev is 2.0.2-2
--- End Message ---
--- Begin Message ---On Mon, 20 Feb 2017 10:43:29 +0800 Drew Parsons <[email protected]> wrote: > > Hi again. There's some discussion on what to do about openmpi in > testing (#855217). Regardless of how we resolve that, can I > affirmatively request we trigger the binNMU for petsc? The binNMU has now been triggered. Thanks all, Drew
--- End Message ---
