speedtest-cli => ImportError

speedtest-cli => ImportError

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 585 bytes --]

Hi,

being curious, I tested 'speedtest-cli' on Core 136.
This gives me:

***SNIP***
root(a)ipfire: ~ # speedtest-cli
Traceback (most recent call last):
  File "/usr/bin/speedtest-cli", line 5, in <module>
    from pkg_resources import load_entry_point
ImportError: No module named pkg_resources
***

As far as I can see, 'speedtest-cli' needs some modules from
'/usr/lib/python3.6/...' which are not part of the current Core 136 and
Core 137(!?) running 'python 2.7.15'.

See: rootfiles from 'python3' and 'python3-setuptools'.

Or is it my fault? Can anyone confirm?

Best,
Matthias

Re: speedtest-cli => ImportError

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 866 bytes --]

Hey,

Has this actually been resolved, or is the speedtest still broken in current nightly builds?

Best,
-Michael

> On 13 Oct 2019, at 13:48, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
> 
> Hi,
> 
> being curious, I tested 'speedtest-cli' on Core 136.
> This gives me:
> 
> ***SNIP***
> root(a)ipfire: ~ # speedtest-cli
> Traceback (most recent call last):
>  File "/usr/bin/speedtest-cli", line 5, in <module>
>    from pkg_resources import load_entry_point
> ImportError: No module named pkg_resources
> ***
> 
> As far as I can see, 'speedtest-cli' needs some modules from
> '/usr/lib/python3.6/...' which are not part of the current Core 136 and
> Core 137(!?) running 'python 2.7.15'.
> 
> See: rootfiles from 'python3' and 'python3-setuptools'.
> 
> Or is it my fault? Can anyone confirm?
> 
> Best,
> Matthias