Package Details: qbittorrent-git 3.3.4.r553.gc2abbed-1

Git Clone URL: (read-only)
Package Base: qbittorrent-git
Description: A bittorrent client powered by C++, Qt5 and the good libtorrent library (development version)
Upstream URL:
Keywords: qt torrent
Licenses: GPL, custom
Conflicts: qbittorrent
Provides: qbittorrent
Submitter: Sevenseven
Maintainer: carstene1ns (Eschwartz)
Last Packager: Eschwartz
Votes: 24
Popularity: 0.271033
First Submitted: 2011-06-28 01:40
Last Updated: 2016-05-25 19:48

Dependencies (6)

Required by (1)

  • sickrage (requires qbittorrent) (optional)

Sources (1)

Latest Comments

Eschwartz commented on 2016-01-13 03:55

Well, I *thought* the v3_3_x branch was "stable" development vs. alpha, but just looking at the history (there is none, it is stuck at the tag) I am no longer sure that is what it is for.

carstene1ns commented on 2015-12-26 09:41

What about having this package updated to QT5, but otherwise keep on using the "stable" branch approach and renaming 'qbittorrent-qt5-git' to 'qbittorrent-unstable-git' keeping updates from the master branch?

AlfredoRamos commented on 2015-12-22 00:31

@uncle Yes, currently it gives the alpha version, but not just alphas, betas and RCs as well. So I don't think naming it *-alpha would be the best way as it won't be consistent.

I think I answered to myself: It uses other branches than master to get the latest "stable" version.

I don't know how I feel about that, I like to have the latest versions of my apps even if they're a little unstable (with no critical issues), I mean, that's one of the reasons why I switched to Arch :P

I can still build my own version, so no worries.

uncle commented on 2015-12-21 23:36

@AlfredoRamos building from master branch gives you the alpha version (for example: 3.4.0), whereas using branch v3_3_x will give you the development version (for example: 3.3.1) of the most recent release, which is more stable than an alpha release. An idea that occurs to me would be for you to change the name of your package to something like "qbittorrent-alpha-git".

AlfredoRamos commented on 2015-12-21 22:23

@carstene1ns Sure, but I have a question: why you're using other branch than master? I've been using the master branch in the qbittorrent-qt5-git package since I adopted (back in AUR3) and I haven't had any critical issue.

In any case, can you keep using the get_version.pri[1] file and (at least something similar) in the pkgver()[2] function?

I like to know which version I'm using, the version we get with git describe and the one in the qBittorrent/version.pri are different, that small file I made gets the actual version.


carstene1ns commented on 2015-12-21 21:09

Considering my comment from 2015-05-31 I think we should merge qbittorrent-qt5-git[1] into this package now.


uncle commented on 2015-12-20 05:25

qBittorrent now uses Qt5 by default: The issue you mentioned earlier, which was caused by Qt5 has been closed: Also, the most recent branch is "v3_3_x", this package is still on "v3_2_x".

Eschwartz commented on 2015-06-02 02:01

Thanks for the fix. :)
BTW -- I didn't know either, until I googled and read the manpages obsessively trying to fix this nagging cosmetic issue. :D

As for the protocol used -- maybe there should be some sort of guideline (hah!)... anyway, it was just a little funny. Personally I wouldn't care, except that it cost me almost a whole 60 seconds of my life never to be recovered to change to my yaourt $develsrcdir and update the remote url before I could build it.

carstene1ns commented on 2015-05-31 09:08

@Eschwartz: Yes, I had updated this PKGBUILD to use qt5, but noticed then that there is a bug[1], that made the qbittorrent team revert to use qt4 by default. We also have a qbittorrent-qt5-git[2] package in the AUR, so I changed it to use qt4 again, but forgot to update the description... :) I wanted to contain the used version in the description so users can easily find it (also regarding [2]). If the team decides to switch to qt5 again, this package should use it and [2] should be removed (and a new package qbittorent-qt4-git could be added, if needed).

I agree that the revision count is better with your change, I did not know that one could specify a tag to get only commits since then.
The downside you mention is valid, however it will be gone once the next release is made. Considering I only introduced this change 5 days ago and the (lack of) popularity of this package, I think it does not really matter to change it now.

It is true that cloning with git:// url works, but it uses a port (9418) that may be blocked by company firewalls, proxies or whatever. Using the https:// protocol has the advantage to get through them.


Eschwartz commented on 2015-05-31 04:45

The current workaround for git describe counts every commit since forever, but of course to properly emulate describe, it would be nice to only list #commits since the version tag.

If I change the line:
_rev=$(git rev-list --count HEAD)
_rev=$(git rev-list --count release-${_tag}..HEAD)

then I get version 3.2.0.r17.2c1d76c-1 instead of version 3.2.0.r5793.2c1d76c-1, which I much prefer.
The downside would be that the package goes _down_ 5776 versions for anyone else who has already installed it......

P.S. the package description now refers to Qt5, but you switched it to use qt4 again. The qBittorrent team just went with "Qt". ;)
P.P.S. cloning works with git:// as well. :p

All comments