Your message dated Sat, 11 Oct 2025 10:47:28 +0300
with message-id <aOoLkMHUoCMqLJC1@localhost>
and subject line Fixed since 3.5.0+dfsg1-1
has caused the Debian Bug report #927140,
regarding getdp compiled without support for gmsh
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.)


-- 
927140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927140
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: getdp
Version: 3.0.4+dfsg1-1
Severity: important

Dear Maintainer,

I was trying to familiarize with dpget, running the tutorials available
on https://gitlab.onelab.info/doc/tutorials but when I followed the
instructions contained, e.g., in the MagneticForces subdirectory

 >  To compute the solution in a terminal:
 >  First generate the (3D) mesh and then run getdp with the chosen resolution 
 >      gmsh magnets.geo -3
 >      getdp magnets.pro -solve MagSta_a

I had the following response

 >  $ getdp magnets.pro -solve MagSta_a
 >  Info    : Running 'getdp magnets.pro -solve MagSta_a' [GetDP 3.0.4-git, 1 
 > node, max. 1 thread]
 >  Info    : Started (Mon Apr 15 15:09:54 2019, Wall = 0.759439s, CPU = 
 > 0.088765s, Mem = 25.0664Mb)
 >  Info    : Increasing process stack size (8192 kB < 16 MB)
 >  Info    : Loading problem definition 'magnets.pro'
 >  Info    : Loading problem definition 'magnets_common.pro'
 >  Info    : Selected Resolution 'MagSta_a'
 >  Info    : Loading Geometric data 'magnets.msh'
 >  Error   : You need to compile GetDP with Gmsh support to open 'magnets.msh'
 >  $ 

If I am correct assuming that in most cases one want to use getdp using
gmsh as its pre- and post-processor, the problem I'm reporting constitutes
a real breakage for most users.

Regards, gb

P.S.: maybe getdp should, at least, recommend the gmsh package.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, 
TAINT_UNSIGNED_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE=C.UTF-8 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages getdp depends on:
ii  libarpack2                       3.7.0-1
ii  libatlas3-base [liblapack.so.3]  3.10.3-8
ii  libc6                            2.28-8
ii  libgcc1                          1:8.3.0-6
ii  libgfortran5                     8.3.0-6
ii  libgsl23                         2.5+dfsg-6
ii  liblapack3 [liblapack.so.3]      3.8.0-2
ii  libopenmpi3                      3.1.3-10
ii  libpetsc-real3.10                3.10.5+dfsg1-1
ii  libpython2.7                     2.7.16-2
ii  libslepc-real3.10                3.10.2+dfsg1-1
ii  libstdc++6                       8.3.0-6

getdp recommends no packages.

getdp suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 3.5.0+dfsg1-1

getdp (3.5.0+dfsg1-1) experimental; urgency=medium

  [ Christophe Trophime ]
  * [9cd3415] fix #927140
...
 -- Francesco Ballarin <[email protected]>  Sun, 14 Apr 2024 
08:24:01 +0000

--- End Message ---

Reply via email to