[Solved] Pyload on Geexbox ??

Home Forums GeeXboX on ARM SoCs [Solved] Pyload on Geexbox ??

This topic contains 17 replies, has 5 voices, and was last updated by  juanlucky 1 year, 4 months ago.

Viewing 3 posts - 16 through 18 (of 18 total)
  • Author
  • #11294


    Hi Rudy,
    It was a fresh one !




    Sorry for the delay, I was very busy ….
    Can you try this package : http://download.geexbox.org/cuboxi/python-pycurl_7.19.5.1-3_armv7.opk

    A quick test shows :

    Traceback (most recent call last):
      File "/bin/pyLoadCore.py", line 48, in <module>
        from module.network.RequestFactory import RequestFactory
      File "/usr/share/pyload/module/network/RequestFactory.py", line 22, in <module>
        from Browser import Browser
      File "/usr/share/pyload/module/network/Browser.py", line 6, in <module>
        from HTTPRequest import HTTPRequest
      File "/usr/share/pyload/module/network/HTTPRequest.py", line 20, in <module>
        import pycurl
    ImportError: pycurl: libcurl link-time ssl backend (openssl) is different from compile-time ssl backend (none/other)
    wget ftp://xxxxxxxxxxxxx//tmp/openbricks/binaries/binaries.cuboxi/packages/python-pycurl_7.19.5.1-3_armv7.opk
    Connecting to xxxxxxxxxxxx
    python-pycurl_7.19.5 100% |**********************************************************************************************************************************|   114k  0:00:00 ETA
    root@geexbox:~# opkg install /tmp/openbricks/binaries/binaries.cuboxi/packages/python-pycurl_7.19.5.1-3_armv7.opk
    root@geexbox:~# opkg install python-pycurl_7.19.5.1-3_armv7.opk 
    Upgrading python-pycurl from to on root.
    Configuring python-pycurl.
    root@geexbox:~# pyLoadCore.py 
    This is your first start, running configuration assistent now.
    Choose your Language / Wähle deine Sprache ([en], de, fr, it, es, nl, sv, ru, pl, cs, sr, pt_BR): ^C
    Setup interrupted


    thanks Tom,
    It works fine for me either !

Viewing 3 posts - 16 through 18 (of 18 total)

You must be logged in to reply to this topic.