Processing commands for control@bugs.debian.org:

# clear found so package can migrate
notfound 1104325 2.3.5+dfsg2-10

Bug #1104325 {Done: Santiago Vila <sanvila@debian.org>} [src:esys-particle] esys-particle: missing builds on armel, armhf, i386 (BD-Uninstallable)
No longer marked as found in versions esys-particle/2.3.5+dfsg2-10.

thanks

Stopping processing here.

Please contact me if you need assistance.
--
1104325: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104325
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi.

Already migrated yesterday, thanks:

$ rmadison esys-particle|grep testing
esys-particle | 2.3.5+dfsg2-10 | testing | source, amd64, arm64, mips64el, ppc64el, riscv64, s390x

If you are looking at tracker:

https://tracker.debian.org/pkg/esys-particle

there is indeed a missing announcement ("MIGRATED to testing") which is misleading.
Don't know the reasons.


Now I'm open for ideas about what to do here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946206

because there is a related autoremoval.

Thanks.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Hi Santiago,

* Santiago Vila <sanvila@debian.org> [250501 13:33]:

Now I'm open for ideas about what to do here:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946206

I took a brief look, and the ImportError is very interesting.

Let's strace python with just the import:

strace -ttf python3 -c 'from esys.lsm.util.FoundationPy import *'

...

14:10:56.209943 openat(AT_FDCWD, "/usr/lib/python3/dist-packages/esys/lsm/util/FoundationPy.so", O_RDONLY|O_CLOEXEC) = 3

good (kinda)

14:10:56.212278 openat(AT_FDCWD, "/usr/lib/python3.13/site-packages/esys/lsm/util/libFoundationPy.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
14:10:56.214012 openat(AT_FDCWD, "/lib/aarch64-linux-gnu/libFoundationPy.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
14:10:56.214587 openat(AT_FDCWD, "/usr/lib/aarch64-linux-gnu/libFoundationPy.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
14:10:56.215078 openat(AT_FDCWD, "/lib/libFoundationPy.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)
14:10:56.215528 openat(AT_FDCWD, "/usr/lib/libFoundationPy.so.0", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory)

All of these are correct, because libFoundationPy.so.0 is installed into /usr/lib/python3/dist-packages/esys/lsm/util. Note that for some reason, python looks in /usr/lib/python3.13/... first: a python-version specific path.

Now, looking at the actual *.so files, using ldd:

/usr/lib/python3/dist-packages/esys/lsm/util/FoundationPy.so:
libFoundationPy.so.0 => not found
libboost_python313.so.1.83.0 => /lib/aarch64-linux-gnu/libboost_python313.so.1.83.0 (0x0000ffff836c0000)
libpython3.13.so.1.0 => /lib/aarch64-linux-gnu/libpython3.13.so.1.0 (0x0000ffff82f20000)
[..]
/usr/lib/python3/dist-packages/esys/lsm/util/libFoundationPy.so:
libFoundation-2.3.4.so => /lib/aarch64-linux-gnu/libFoundation-2.3.4.so (0x0000ffff81a40000)
libboost_python313.so.1.83.0 => /lib/aarch64-linux-gnu/libboost_python313.so.1.83.0 (0x0000ffff819e0000)
libpython3.13.so.1.0 => /lib/aarch64-linux-gnu/libpython3.13.so.1.0 (0x0000ffff81240000)
[..]

In my opinion, _both_ FoundationPy.so and libFoundationPy.so link to a python-version specific library (libboost_python313.so.1.83.0). Therefore, they shall NOT be installed into usr/lib/python3/dist-packages, but into /usr/lib/python3.13/site-packages.

I would try rectifying this first, and then see if that solves the test failure.

Hope this helps.

Best,
Chris

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)