The Azureus bittorrent client continuously complains about there being a new update out, downloads it and asks for a restart to upgrade. When you restart it, it hasn't upgraded and this behaviour continues. This is due to the way the Gentoo ebuild is installed, with the Azureus jar file in a global directory and Azureus expects it in a home directory. It would be better if Azureus executed the jar version it downloaded to the users home directory if available, and we should probably check that it is actually newer than the global jar too so when emerging a new version of Azureus, the reverse problem doesn't occur. I propose this patch (see attached).
Created attachment 55002 [details, diff]
Azureus never updating fix
Apply with patch -p0 <azureus.diff
What if we just bumped the ebuild so the program itself does not complain? :-(
einfo "Due to the nature of the portage system, we recommend"
einfo "that users check portage for new versions of Azureus"
einfo "instead of attempting to use the auto-update feature."
einfo "You can disable the upgrade warning in"