Reply in-line :- On 27/03/2020, jim_p <[email protected]> wrote: > Package: qbittorrent > Version: 4.1.7-1+b2 > Followup-For: Bug #946449 > > I know about tracker.debian.org. However, it does not show if there is a > new > version for all the packages. E.g. there is no such info for conky, so I > opened > an bug report asking for an update, because the package in the repo is > already > 1 major version behind.
For that the debian/watch file needs to be done/configured correctly. Sharing qbittorrent's watch file https://salsa.debian.org/debian/qbittorrent/-/blob/master/debian/watch This is something you can take up with the maintainer of conky and see if he can fix something there. I know the package but unfamiliar with how it works. > Also, as I have seen from other packages, the maintainers seem to ignore > its > presence completely and they simply leave their packages without updates. > That > is the only reason I open bug reports like this one, to draw some attention > and > eventually get the packages updated. > > As for the changes on qbittorrent 4.2.x, I have mentioned the most > important > one at the very top: the use of libtorrent 1.2.x. The rest are trivial for > me, > but they can be found in its site > https://www.qbittorrent.org/news.php > What we need to do is figure out the depends, build-depends as well as reverse-depends to see what needs to be fixed in order in order for libtorrent 1.2.x to be ok in Debian. I did that in the past once or twice, even tried to build it but failed but tried enough so the maintainer had no option but to package the new version. I guess if we do some of the hard work then the maintainer also gets interested. This is how it works. My memory is not as sharp but you could see what I did probably in old qbittorent reports, been a long long-time user of the package. > > -- System Information: > Debian Release: bullseye/sid > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.4.0-4-amd64 (SMP w/2 CPU cores) > Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, > TAINT_UNSIGNED_MODULE > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), > LANGUAGE=en_US:en (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > Init: systemd (via /run/systemd/system) > Just a slightly OT question , why are you using a tainted kernel ? Have an nvidia card or some other thing, just curious . > Versions of packages qbittorrent depends on: > ii geoip-database 20191224-2 > ii libboost-system1.67.0 1.67.0-17 > ii libc6 2.30-2 > ii libgcc-s1 [libgcc1] 10-20200324-1 > ii libgcc1 1:10-20200324-1 > ii libqt5core5a 5.12.5+dfsg-9 > ii libqt5dbus5 5.12.5+dfsg-9 > ii libqt5gui5 5.12.5+dfsg-9 > ii libqt5network5 5.12.5+dfsg-9 > ii libqt5widgets5 5.12.5+dfsg-9 > ii libqt5xml5 5.12.5+dfsg-9 > ii libstdc++6 10-20200324-1 > ii libtorrent-rasterbar9 1.1.13-1.1+b1 > ii python 2.7.17-2 > ii zlib1g 1:1.2.11.dfsg-2 > > qbittorrent recommends no packages. > > Versions of packages qbittorrent suggests: > pn qbittorrent-dbg <none> > > -- no debconf information > > -- > To unsubscribe, send mail to [email protected]. > -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C
