You are not logged in.
Pages: 1
I read in the FAQ this question:
What if I run a full system upgrade and there will be
an update for a shared library, but not for the apps
that depend on it?
And the answer was:
This scenario should not happen at all.
I laughed, because I've had qBitTorrent stop working twice in the last 6 months due to the rasterbar library getting an update that wasn't compatible.
QUESTION: Is there any way (other than excluding qbittorrent and rasterbar) to "group" the compatible programs, only allowing an update when both are ready?
Thx!
Offline
I haven't seen that happen at all, but if you do then file a bugreport to have qbittorrent rebuilt...
When the FAQ says "This scenario should not happen at all" what they mean is "This scenario only happens when the maintainer makes a mistake deserving of a bugreport".
And no, there is no pacman feature to accommodate for errors in package maintenance. File a bugreport against qbittorrent.
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
Ok, thx!!
Offline
Are you using qbittorrent from the repos or one of the versions in the AUR?
Edit - Just seen from one of your other posts that you are using qbittorrent-qt4 from the AUR, this is what is causing the issue.
You are responsible for rebuilding packages from the AUR when a shared library gets updated - not pacman.
Simply rebuild and reinstall qbittorrent-qt4 every time librasterbar gets updated.
Your original wiki quote is correct - but only for packages in the official repositories. If you use the AUR then it's your responsibility.
Last edited by Slithery (2017-06-12 16:17:00)
Offline
I actually switched to the qbittorrent-qt4 in the AUR after having the problem with the qbittorrent in the arch repo.
(at first I used "pacman -S qbittorrent" but had 2 occasions where the rasterbar lib was updated and qbittorrent wouldn't run, so I did an "IgnorePkg = qbittorrent ...rasterbar..." in the /etc/pacman.conf for a while)
Then I tried the "yaourt -S qbittorrent-qt5" for a while, then IT ALSO had an issue, so I switched to the qbittorrent-qt4, which was easier for me to manage myself.
Offline
From the version history, qbittorrent seems to treat libtorrent ABI stable on at least point release versions, but according to eg. https://abi-laboratory.pro/tracker/comp … eport.html that's not entirely correct.
This might be an assertion violation upstream or a misconception by the qbittorrent maintainer. Feel free to raise that concern.
Offline
Pages: 1