Raspberry Pi raspbian build

Linux specific questions, problems.
Post Reply
Thewonderer

Raspberry Pi raspbian build

Post by Thewonderer »

Hi, I got myself a raspberry Pi 3 the other day and installed raspbian on it.  Works great and even pulled down a qbitorrent package using the apt-get command. 

From what I understand,  raspbian uses Debian at its core but is tweaked to work with the Pi.  It's got an armhf instruction set.

They version I got was old.  3.1.0 I think.

I tried to follow guides to compile the latest version but it always fails.  Even using guides for raspbian.

Can anyone help with a step by step guide?  My compile fails on libtorrent  part.  Didn't even get to qbitorrent.  Realize that libtorrent is the core and it's a special version 1.0.9 build for qbitorrent 3.36.

Using the qbitorrent - nox

Thanks
FFDA

Re: Raspberry Pi raspbian build

Post by FFDA »

I just compiled and installed headless qBittorrent following this guide.

BTW my Raspberry Pi B had freshly installed and updated to newest version Raspbian Jessie Lite.
Thewonderer

Re: Raspberry Pi raspbian build

Post by Thewonderer »

Thanks FFDA!!!  I will have to try and clean SD card to test this...

I noticed the guide use libtorrent 1.0.6 and it is now up to 1.1.0.  Did you use that exact version as it is in the script?

I have my Pi already running with 3.1.10 which is a default package in the Raspbian repository.  If there was an upgrade guide that would be great, if not I will try that script and post my results here so other people trying to upgrade will know.

Thanks.
FFDA

Re: Raspberry Pi raspbian build

Post by FFDA »

You do not have to reinstall Raspbian unless it is Wheezy (older version) and not Jessie. You simply need Jessie because Wheezy do not have Qt5 in it's repositories.

While I was reading up about compiling/installing newest version of qBittorrent on Rpi I read somewhere that libtorrent1.1.0 isn't completely compatible with qBitorrent and gives you errors while compiling so I followed this guide exactly, but now I'm compiling libtorrent1.0.9.

Here and here people writing that qBittorrent do not support or support for libtorrent1.1.0 is limited at best. One of them is qBittorrent project member.

If you what to try libtorrent1.0.9 simply use this line:

Code: Select all

wget https://github.com/arvidn/libtorrent/releases/download/libtorrent-1_0_9/libtorrent-rasterbar-1.0.9.tar.gz
instead of this:

Code: Select all

wget https://github.com/arvidn/libtorrent/releases/download/libtorrent-1_0_6/libtorrent-rasterbar-1.0.6.tar.gz
Edit: Everything works fine with libtorrent-rasterbar-1.0.9.
Last edited by FFDA on Sun Aug 07, 2016 9:26 am, edited 1 time in total.
Thewonderer

Re: Raspberry Pi raspbian build

Post by Thewonderer »

Success!!  Yes, Libtorrent compiled successfully (though there were a couple of errors).  I am now running qBittorrent 3.3.6 with libtorrent 1.0.9

A few issues. I had the original  repository build of qbittorrent running (3.1.10) and this was working OK.  the qbittorrent.conf  configuration file and other data was stored in /.config/qBittorrent  but when I upgraded it didn't pick up the old settings at all.  It seems this manually compiled version stores the information in /home/torrent/.config/qBittorrent/qBittorrent.conf  after hunting down for the file.  qBittorrent documentation states is should be in the /.config/qBitorrent  folder.

Worse still my partially finished torrents were discovered and when I re-added a torrent to download , it didn't pick up the original incomplete one from my USB HDD, it created a random directory name. I then had to pause that, move over the previous torrent files / folder and then force a re-check.  :(

I did a quick search and there is a posting about this from a few years back, someone said the boost version was to old and this cause a similar issue for them.  I am using the raspbian Boost version which I know is an older version.  Could this be why libtorrent is creating random folder names?  Could it be due to having a pre-existing version of libtorrent and qBitorrent.

I noticed that my Pi has 2 qbittorrent-nox processes running. I don't think that was the case before. Could it be the old version and this new version running? I had an issue after restarting my Pi that it wouldn't let me log into the webgui with my new password, another reboot sorted that.

Finally, but not related to the new install, when i rebooted my Pi (because I am not sure how to restart my qbitorrent-nox to pick up new changes to qBitorrent.conf)  it doesn't do a graceful shutdown of qBittorrent, even if I pause all my torrents and wait a few seconds.  Is there a way I can gracefully shutdown qBittorrent?
Last edited by Thewonderer on Sun Aug 07, 2016 8:43 pm, edited 1 time in total.
FFDA

Re: Raspberry Pi raspbian build

Post by FFDA »

[quote="Thewonderer"]
Finally, but not related to the new install, when i rebooted my Pi (because I am not sure how to restart my qbitorrent-nox to pick up new changes to qBitorrent.conf)  it doesn't do a graceful shutdown of qBittorrent, even if I pause all my torrents and wait a few seconds.  Is there a way I can gracefully shutdown qBittorrent?
[/quote]

As I understand you have Raspbian Jessie installed as your OS? How did you start your qBittorrent-nox at startup? Using crontab? If so you should set up your qBittorrent as a daemon using this guide. It will make your qBittorrent start at startup and you will be able to restart, start or stop it with CLI command. They are written in the guide.
User avatar
Peter
Administrator
Administrator
Posts: 3049
Joined: Wed Jul 07, 2010 6:14 pm

Re: Raspberry Pi raspbian build

Post by Peter »

What if you compile with "pbuilder"?

https://wiki.ubuntu.com/PbuilderHowto
http://packaging.ubuntu.com/html/
https://jodal.no/2015/03/08/building-ar ... -pbuilder/

0) I won't spoonfeed much, I learnt it from these tutorials and it's pretty simple.
Knowing how to use pbuilder is very useful.

1) You can use your PC to create the package, then you just have to transfer the finished deb packages.
2) You just have to download a so called ".dsc" file from Debian's site or a new Ubuntu build.
3) Then use pbuilder to set up the environment + build the package.

It's not so hard, with the entire tutorial and all it took a few hours only.
Post Reply