python3-libtorrent linking libboost_python27.so instead of libboost_python36.so
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
boost1.67 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
Cosmic |
Won't Fix
|
Undecided
|
Unassigned | ||
libtorrent-rasterbar (Ubuntu) |
Fix Released
|
Critical
|
Unassigned | ||
Cosmic |
Fix Released
|
Critical
|
Unassigned |
Bug Description
[Impact]
Due to the libboost-python naming convention changing, python3-libtorrent incorrectly links to libboost_
[Test Case]
Run the command:
$ python3 -c "import libtorrent"
With 1.1.9-1 on cosmic, it will fail with:
Traceback (most recent call last):
File "<string>", line 1, in <module>
ImportError: /usr/lib/
The command should exit without error in the fixed version.
[Regression Potential]
There is little regression potential as the package is currently broken without this fix.
----
An error occurs when importing the libtorrent module from python 3.x script:
ImportError: /usr/lib/
How to reproduce:
1. Install packages:
python36
python3-libtorrent
2. Run any python script importing libtorrent module
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: python3-libtorrent 1.1.9-1
ProcVersionSign
Uname: Linux 4.18.0-10-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Oct 27 09:21:43 2018
InstallationDate: Installed on 2009-11-28 (3254 days ago)
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
SourcePackage: libtorrent-
UpgradeStatus: Upgraded to cosmic on 2018-10-25 (1 days ago)
Changed in libtorrent-rasterbar (Ubuntu): | |
status: | New → Confirmed |
importance: | Undecided → Critical |
Changed in boost1.67 (Ubuntu): | |
status: | Confirmed → Won't Fix |
Changed in libtorrent-rasterbar (Ubuntu Cosmic): | |
status: | New → Confirmed |
importance: | Undecided → Critical |
description: | updated |
Changed in libtorrent-rasterbar (Ubuntu Cosmic): | |
status: | Confirmed → In Progress |
Changed in libtorrent-rasterbar (Ubuntu): | |
status: | In Progress → Fix Committed |
The issue seems to be that in Cosmic the libboost-python lib naming convention has changed and that affects the debian rules scripts picking the correct lib python version.
Bionic: /usr/lib/ x86_64- linux-gnu/ libboost_ python- py36.so. 1.62.0 x86_64- linux-gnu/ libboost_ python36. so.1.67. 0
Cosmic: /usr/lib/
https:/ /packages. ubuntu. com/bionic/ amd64/libboost- python1. 62.0/filelist /packages. ubuntu. com/cosmic/ amd64/libboost- python1. 67.0/filelist
https:/