Created attachment 323202 [details] qbittorrent 3.0.2 compile fix There is unneeded line in torrentcontentmodelitem.cpp. We need to patch qbittorrent before compile. I've attached code patch and ebuild fix for qbittorrent 3.0.2.
Created attachment 323204 [details, diff] ebuild patch fixing qbittorrent 3.0.2 compilation
Created attachment 323206 [details, diff] qbittorrent 3.0.2 compile fix
Also fixed in current upstream where it's side effect of code refactoring.
Compiles for me just fine. You need to provide your emerge --info. Also please show me the upstream commit if you have it around
(In reply to comment #4) > Compiles for me just fine. You need to provide your emerge --info. Look into my compile fix patch. Problem occurs for <=net-libs/rb_libtorrent-0.15* and I'm almost sure that you use net-libs/rb_libtorrent-0.16*. > Also please show me the upstream commit if you have it around As I said earlier: upstream developers have made big code refactoring, so you won't find simple fix for this bug over there.
(In reply to comment #5) > (In reply to comment #4) > > Compiles for me just fine. You need to provide your emerge --info. > > Look into my compile fix patch. Problem occurs for > <=net-libs/rb_libtorrent-0.15* and I'm almost sure that you > use net-libs/rb_libtorrent-0.16*. > > > Also please show me the upstream commit if you have it around > > As I said earlier: upstream developers have made big code refactoring, > so you won't find simple fix for this bug over there. qbittorrent-3.0.2 is ~testing. Therefore you also need to use the ~testing rb_libtorrent which is 0.16.X. Is there a reason you want to use the old one?
(In reply to comment #6) > qbittorrent-3.0.2 is ~testing. Therefore you also need to use the ~testing > rb_libtorrent which is 0.16.X. That's what is generally recommended. But you should still raise the dep to >=0.16 to have a correct depgraph.
qbittorrent-3.0.X packages now depend on rb_libtorrent >= 0.16.3. Closing this bug as INVALID
> qbittorrent-3.0.2 is ~testing. Therefore you also need to use the ~testing > rb_libtorrent which is 0.16.X. Is there a reason you want to use the old one? That's "Everything or nothing" solution ;-) You want to say if I use qbittorrent from ~testing, I should also use xorg-server from ~testing? Bumping requirement for qbittorrent in gentoo, although upstream qbittorent doesn't require rb_libtorrent 0.15.x, is kind of nonsense...
(In reply to comment #9) > > qbittorrent-3.0.2 is ~testing. Therefore you also need to use the ~testing > > rb_libtorrent which is 0.16.X. Is there a reason you want to use the old one? > > That's "Everything or nothing" solution ;-) > You want to say if I use qbittorrent from ~testing, I should also use > xorg-server from ~testing? > Bumping requirement for qbittorrent in gentoo, although upstream qbittorent > doesn't require rb_libtorrent 0.15.x, is kind of nonsense... yes, if you use half of ~testing and half of stable packages, then this is an unsupported configuration for Gentoo and it has always been. I don't want to apply this custom patch without fist having upstream accepting it. I don't understand why you don't send your patch upstream. This patch is against 3.0.2 which should be similar with what upstream have in their git repo.
