[SOLVED] MX-18.1 package request: "Tribler"

[MX-16_fan]

Many HTTP(S)-based content delivery services do a poor job when used with a low-band or unreliable internet connection (e.g. when travelling in a train).

Hence, I'd like to do an academic (seminar) test on Tribler, a software developed within an official research project of the Delft University of Technology (Netherlands).

According to crunchbase, Tribler's founders "created ... a pan-European conglomerate of 21 industrial partners, media content providers and research institutions" which was "announced a €15 million grant from the European Union", and another "€4 million ... donated by [the] 21 project partners" from "12 different countries, including large European players". The project aim was defined as the development of "an open source, efficient, trusted, personalized, user-centric ... media delivery mechanism", which promises to avoid congestion of the Internet, and to contribute to a "technologically-competitive future Europe".

The source code of the most current version (7.2.2) can be downloaded here: https://github.com/Tribler/tribler/rele ... 2.2.tar.xz. It is on GitHub also: https://github.com/Tribler/tribler/tree/v7.2.2.

There's a "debianization example" available here: https://github.com/Tribler/tribler/rele ... .2_all.deb. Mind that Lintian (on MX 17.1) outputs some issues. They look minor to me, but I'm not completely sure, so I wouldn't dare to install their binary package.


Greetings, and thanks in advance for your feedback, Joe

[Stevo]

Here's the package built on MX, though lintian will show the same minor issues: https://drive.google.com/open?id=1th7aj ... EWtzN97jPz

[MX-16_fan]

@Stevo:

Here's the package built on MX, though lintian will show the same minor issues: https://drive.google.com/open?id=1th7aj ... EWtzN97jPz

Thanks, Stevo!


1.)
What about the issues - what do they mean?


2.)
I cannot install this package on MX-17.1 (so I guess it won't work on MX-18.1 either). GDebi claims that the package isn't a Debian package, and that its MIME-type is 'application/x-debian-package', which can't be installed.


Hope that helps.



Greetings, Joe

[Stevo]

Sometime gdebi has a bug like that, which is one of the reasons I prefer to install debs with the right-click action in Thunar or Dolphin instead. Can you install it from the test repo?

[MX-16_fan]

@Stevo:

(...) Can you install it from the test repo?

Tested installation on MX-17.1 from the MX Test Repo, installs o.k., and at first starts o.k.

However, it takes approximately more than a minute until its initial window shows up, and in that window I see nothing except a heading ("Tribler", in orange color), two orange-colored rack-wheels and "Loading...", which never stops. Doesn't have a proper icon in the xfce4-panel either. I guess something is wrong here.

Will test with MX-18.1 also.

What do the Lintian issues mean (please see above)?


Greetings, Joe

[Stevo]

Can you list the lintian issues?

[MX-16_fan]

@Stevo:

Can you list the lintian issues?

Just checked it with the package you built - nearly all issues mentioned by Lintian gone there (this test done with MX-17.1). The only remaining Lintian mentioning is this one:

W: tribler: command-in-menu-file-and-desktop-file tribler usr/share/menu/tribler:6

Lintian finished with exit status 0

* What does that mean?


* In the meantime, I tried to make Tribler start on MX-18.1 also, but to no avail either. Can you reproduce that?


Greetings, Joe

[Stevo]

I get the same thing, but am at a library that blocks Bittorrent, so can't help troubleshoot it much. I wonder if other distros get the same problem.

Code: Select all

W: tribler: command-in-menu-file-and-desktop-file tribler usr/share/menu/tribler:6

That means it doesn't like line 6 in /usr/share/menu/tribler. Menu files are pretty much deprecated, though, and I could take that out.

[MX-16_fan]

@Stevo:

I just noticed that some people have had the same problem before, e.g. on Arch Linux (see e.g. https://forum.tribler.org/t/unable-to-s ... linux/4808).

I went through the log file that can be found in /tmp. It says:

INFO 1561905782.14 single_application:23 (root) __init__()
INFO 1561905782.22 single_application:49 (root) self._outSocket.error() = '2'
INFO 1561905782.22 single_application:60 (root) __init__(): returning
QFont::setPointSize: Point size <= 0 (-1), must be greater than 0
INFO 1561905789.27 event_request_manager:151 (TriblerGUI) Will connect to events endpoint
INFO 1561905789.38 event_request_manager:53 (TriblerGUI) Got Tribler core error: 1
Traceback (most recent call last):
File "run_tribler.py", line 94, in <module>
start_tribler_core(base_path, api_port)
File "run_tribler.py", line 45, in start_tribler_core
from Tribler.Core.Session import Session
File "/usr/share/tribler/Tribler/Core/Session.py", line 18, in <module>
import Tribler.Core.permid as permid_module
File "/usr/share/tribler/Tribler/Core/permid.py", line 10, in <module>
from Tribler.pyipv8.ipv8.keyvault.private.libnaclkey import LibNaCLSK
ImportError: No module named pyipv8.ipv8.keyvault.private.libnaclkey

1.)
Does that look similar on your machine?


2.)
This thread here: https://github.com/Tribler/tribler/issues/3700, where someone has the same "pyipv8.ipv8.keyvault.private.libnaclkey" stuff in his logfile, says something about submodules that have to be included when packaging, which apparently can easily forgotting when cloning the repo.


3.)
This older posting: https://bugs.archlinux.org/task/60575 relating to an only slightly older version indicates that in any case a package named python2-pyopenssl has to be installed. Confirmed by the above-mentioned thread https://github.com/Tribler/tribler/issues/3700. However, I can't find that package in Debian's/MX's repos.


4.)
In https://github.com/Tribler/tribler/issues/4192, someone says:

To be able to run from the source code obtained from github, you'll need to install all the dependencies. Here is a supporting documentation page.
https://tribler.readthedocs.io/en/next/ ... linux.html

Also here, someone else says:

Just to be safe, did you also run this command: https://github.com/Tribler/py-ipv8#dependencies

Maybe they made a mistake when defining the dependencies? A little unclear to me, as the above-mentioned page https://tribler.readthedocs.io/en/next/ ... linux.html explicitly relates to "Tribler development environment[s]", whatever that is.

You probably understand this far better than I do .


Greetings, Joe

[MX-16_fan]

UPDATE:


@Stevo:

In the meantime, a friend of mine found the Tribler project's IRC channel, and directly asked the people there why the MX test package doesn't work.

According to my friend, the Tribler people then had a look at the package you thankworthily built for testing purposes (the one that's in the MX Test Repo), and told him that there was a slight packaging error to be seen, as described in 2.) (please see above).

I guess that'll make fixing the issue easy .


Greetings, and thanks in advance for looking into this, Joe