Since version 2.9.10 to 3.0.8 dozens of bugs have been fixed. The new versions of qBitTorrent are bugsfix practitioner. See the link below: http://qbittorrent.sourceforge.net/news.php
Assignee: bugsquad => matteo.pasottiSummary: qbittorent update to 3.0.8 or newer for bugfixes => qbittorrent update to 3.0.8 or newer for bugfixesSource RPM: (none) => qbittorrent
As qBitTorrent is only a GUI for libtorrent-rasterbar, one should update libtorrent-rasterbar to v 0.16.7 for better performance, security and bugfix. https://bugs.mageia.org/show_bug.cgi?id=9178
iirc our policy doesn't allow version changes and we still do not provide backports. This means that I should patch qbittorrent or libtorrent-rasterbar to integrate bugfixes starting from 2.9.10 to 3.0.8 :-/ I mean that you should point out some specific bug you're experiencing not just the list of the bugfixes from the release notes. I used qbittorrent-2.9.10 compiled against libtorrent-rasterbar-0.15.9 (Mageia 2 default) till now without any issues. Consider moreover that qbittorrent version 3.0.x brings new features, not only bugfixes. Regards
I'll raise the bugfix in the dev site and post here. I would like to make some comments. I am a home user and use only a distro by machine. Need a solid and stable system as mageia to use in production on a day-to-day basis. However, domestic users need to have updated end applications such as browser, video player and how p2p file sharing. Mageia is one of the strongest and stable distros available between from the friendly and easy to use. Update the whole distro only would bring instability. However, it should be allowed to end applications update as mentioned above. When I report a bug I'm not thinking about my individual experience, but want to contribute to a better experience for all users mageia. Many home users do not report bugs for not knowing how to proceed or be easier to switch distro that contribute to its improvement.
Considered that there is no critical issues with the version of qbittorrent shipped with mga2 I would ask to close this bug report as resolved invalid. Anyone has other strong opinions on this subject? This should be classified as a backport request but we are not providing backports.
Component: RPM Packages => Backports
Keywords: (none) => Backport
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this request. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD