A BitTorrent client in Qt
qBittorrent is a bittorrent client programmed in C++ / Qt that uses libtorrent-rasterbar.
It aims to be a good alternative to all other bittorrent clients out there. qBittorrent is fast, stable and provides unicode support as well as many features.
- Devel package for openSUSE:Factory
-
14
derived packages
- Links to openSUSE:Factory / qbittorrent
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout network/qbittorrent && cd $_ - Create Badge
Refresh
Refresh
Source Files
Sources could not be expanded: conflict in file qbittorrent.spec
Comments 7
This comment has been deleted
The only practical solution I see here is to link the newer libtorrent-rasterbar from devel:libraries:c_c++ or Factory and have it build for 15.4. But I'm not a project maintainer, so you'll have to ask them. Merely disabling the version check might be very insidious.
Hello @alois,
Please trigger a 'global' rebuild (by increasing the release number - for example) as
LibTorrent-Rasterbar 2.0.10[https://build.opensuse.org/package/show/network/libtorrent-rasterbar] has been released.Also, it would be nice to reduce requirement for:
BuildRequires: pkgconfig(libtorrent-rasterbar) >= 2.0.9from>= 2.0.9to>= 2.0.8if you want the builds to be built for openSUSE Leap 15.4/15.5/15.6.Thank you in advance for compliance,
Martin from Liberec
@MartinVonReichenberg, the purpose of the first request evades me, unless you know for a fact that newer features of libtorrent-rasterbar would be used only if detected at buildtime.
As for the second, the build would fail, see https://github.com/qbittorrent/qBittorrent/blob/release-4.6.3/CMakeLists.txt#L15
The purpose of the first idea is almost always automatic in OBS. If dependency of a particular program/application is released and then applied, it will trigger rebuild for the program's successful builds automatically. That means the latest successful builds for Tumbleweed should already have LibTorrent-Rasterbar 2.0.10 included after installation/update.
The second idea could be easily done with another patch or with inclusion within the LibBoost patch . . .
Whatever, Up to you . . .
Triggered a rebuild, even though it doesn't make any sense to me.
As for the second, patches are welcome.
After I figure out how to make one, I shall let you know . . .