Your message dated Tue, 21 Nov 2023 10:43:46 +0000 with message-id <zvyj3kkxlompm...@harlock.unige.ch> and subject line Re: dico-module-python: loading the python module in the config fails with "cannot load module python: file not found" has caused the Debian Bug report #1028487, regarding dico-module-python: loading the python module in the config fails with "cannot load module python: file not found" 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.) -- 1028487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: dico-module-python Version: 2.10-1 Severity: important X-Debbugs-Cc: simon.heimb...@heimberg-ea.ch Dear Maintainer, I found a problem in dico-module-python. * What led up to the situation? I wanted to write a python module for dico, but could not load python "mode". * What exactly did you do (or not do) that was effective (or ineffective)? When I included the following in the config file (/etc/dicod.conf), the python module failed to load already. load-module python; # other variants with "load-module python {command python ...};" did the same * What was the outcome of this action? This error message was printed: cannot load module python: file not found * What outcome did you expect instead? I expected it to load the python module, to be able to load a database loaded by my python code thereafter. After research, I found out that /usr/lib/x86_64-linux- gnu/dico/python.so does not find a dependant library. (LD_DEBUG=all /bin/dicod ...) I managed to get it running with setting a variable before the run: LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libpython3.9.so.1.0 /bin/dicod ... or LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libpython3.9.so.1 /bin/dicod ... No idea if this happens on many systems. So here some more information about mine: The library l*n3.9.so.1 is a symlink to the other one (l*n3.9.so.1.0). There is no other libpython* on my system (in any lib path). Of course /lib is a symlink to /usr/lib/, so this files are shown once more. By the way, why does the package not depend on or recommend libpython3.9 (which contains the library)? So I append some package information additionally: ii libpython3.9 3.9.2-1 -- System Information: Debian Release: 11.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-19-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8), LANGUAGE=de_CH:de Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dico-module-python depends on: ii dicod 2.10-1 ii libc6 2.31-13+deb11u5 ii libdico2 2.10-1 dico-module-python recommends no packages. dico-module-python suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---fixed 1028487 2.11-2+b3 usertags 1028487 + pca.it-communication thanks Version: 2.11-2+b3 Hi there, On Wed, 11 Jan 2023 22:55:24 +0300, Simon Heimberg wrote: > Package: dico-module-python > Version: 2.10-1 [...] > * What led up to the situation? > I wanted to write a python module for dico, but could not load python > "mode". > > * What exactly did you do (or not do) that was effective (or > ineffective)? > When I included the following in the config file (/etc/dicod.conf), the > python module failed to load already. > > load-module python; > # other variants with "load-module python {command python ...};" did > the same I experienced the same bug on my old 11.8/bullseye installation, but then upgrading to 12.2/bookworm fixed it, bug marked as fixed. > After research, I found out that /usr/lib/x86_64-linux- > gnu/dico/python.so does not find a dependant library. (LD_DEBUG=all > /bin/dicod ...) > > I managed to get it running with setting a variable before the run: > LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libpython3.9.so.1.0 /bin/dicod ... > or > LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libpython3.9.so.1 /bin/dicod ... > > No idea if this happens on many systems. So here some more information > about mine: > The library l*n3.9.so.1 is a symlink to the other one (l*n3.9.so.1.0). > There is no other libpython* on my system (in any lib path). > Of course /lib is a symlink to /usr/lib/, so this files are shown once > more. Here the current situation: ``` $ ls -l /usr/lib/x86_64-linux-gnu/libpython* lrwxrwxrwx 1 root root 51 Sep 19 09:10 /usr/lib/x86_64-linux-gnu/libpython2.7.a -> ../python2.7/config-x86_64-linux-gnu/libpython2.7.a lrwxrwxrwx 1 root root 17 Sep 19 09:10 /usr/lib/x86_64-linux-gnu/libpython2.7.so -> libpython2.7.so.1 lrwxrwxrwx 1 root root 19 Sep 19 09:10 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1 -> libpython2.7.so.1.0 -rw-r--r-- 1 root root 3393936 Sep 19 09:10 /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0 lrwxrwxrwx 1 root root 20 Mar 13 2023 /usr/lib/x86_64-linux-gnu/libpython3.11.so.1 -> libpython3.11.so.1.0 -rw-r--r-- 1 root root 7732544 Mar 13 2023 /usr/lib/x86_64-linux-gnu/libpython3.11.so.1.0 $ ``` > By the way, why does the package not depend on or recommend > libpython3.9 (which contains the library)? So I append some package > information additionally: > ii libpython3.9 3.9.2-1 IMHO this was a bug. And it has been fixed at least in 2.11-2+b3 (I could not find any reference in `changelog.Debian.gz`, though): ``` 0 [2023-11-21 11:31:12] capello@harlock:~ $ apt-cache show dico-module-python | grep -E '^(Version|Depends): ' Version: 2.11-4 Depends: dicod, libc6 (>= 2.4), libdico2 (>= 2.0.91), libpython3.11 (>= 3.11.5) Version: 2.11-3 Depends: dicod, libc6 (>= 2.4), libdico2 (>= 2.0.91), libpython3.11 (>= 3.11.0) Version: 2.11-2+b3 Depends: dicod, libc6 (>= 2.4), libdico2 (>= 2.0.91), libpython3.11 (>= 3.11.0) Version: 2.10-1 Depends: dicod, libc6 (>= 2.4), libdico2 (>= 2.0.91) 0 [2023-11-21 11:31:47] capello@harlock:~ $ ``` Thx, bye, Gismo / Luca -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (100, 'bookworm-fasttrack'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.5.0-0.deb12.1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dico-module-python depends on: ii dicod 2.11-2+b3 ii libc6 2.36-9+deb12u3 ii libdico2 2.11-2+b3 ii libpython3.11 3.11.2-6 dico-module-python recommends no packages. dico-module-python suggests no packages. -- no debconf information
signature.asc
Description: PGP signature
--- End Message ---
