Hi Stefan,
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
I took a look at this further and found that python 2.7.17 is in Bionic
and 2.7.18 is in Focal (see: rmadison libpython2.7). With that, I am a
bit confused as to how are you facing this error.
Furthermore, I took a look a look at the .so and saw the same .so being linked
for both, Focal and Bionic:
$ ldd /usr/lib/apache2/modules/mod_python.so
linux-vdso.so.1 (0x00007ffdfcdd0000)
libpython2.7.so.1.0 => /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
(0x00007fc61fd48000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fc61f957000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007fc61f73a000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007fc61f51b000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fc61f317000)
libutil.so.1 => /lib/x86_64-linux-gnu/libutil.so.1 (0x00007fc61f114000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fc61ed76000)
/lib64/ld-linux-x86-64.so.2 (0x00007fc6204e8000)
Now, I am a bit unsure as to how did you figure out that the .so is
"statically" linked with is? Could you perhaps show us the output of
`apt-cache policy libapache2-mod-python libpython2.7`? Because at this
point, I am worried that you might somehow be running different versions
of the two packages (one from Focal and the other from Bionic).
Whilst at it, could you also help me provide the steps to reproduce this
error/failure?
Since there isn't enough information in your report to differentiate
between a local configuration problem and a bug in Ubuntu, I'm marking
this bug as "Incomplete" for now.
If indeed this is a local configuration problem, you can find pointers
to get help for this sort of problem here:
http://www.ubuntu.com/support/community. Or if you believe that this is
really a bug, then you may find it helpful to read "How to report bugs
effectively" (http://www.chiark.greenend.org.uk/~sgtatham/bugs.html).
We'd be grateful if you would then provide a more complete description
of the problem, explain why you believe this is a bug in Ubuntu rather
than a problem specific to your system, and then change the bug status
back to New.
Once done, I'll be happy to take a look at this and figure out from
there on. Thanks, again, for reporting this though! :)
** Changed in: libapache2-mod-python (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1919923
Title:
mod_python statically linked to wrong python 2.7 version
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libapache2-mod-python/+bug/1919923/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
