Comment 29 for bug 301189

I don't think that the built in updater should be completely disabled in the packaged version of Vuze. It simply should not check for updates to Azureus/Vuze by default -- since that is the package manager's job (and also, updates Vuze attempts to apply to itself will fail, which is the reason for this problem). Of course, the built-in update manager is useful for updating things like plug-ins that were installed through their built-in plug-in management system.

I suggested installing Azureus in your home directory without using the package manager not because that is the best solution, but that is what you have to do if you want to use the most current version, as Vuze in the repositories is not updated very often (4.x is not even in the jaunty repos at the moment), and also, the built-in update manager will actually work.

Using Vuze's auto updater with the packaged version is not a good idea. The package manager will not be aware of updates to Vuze in this case, extra files may be added with new versions that the package manager is not aware of, dependencies may change, etc. When using the packaged version, updates should come through the package manager.

The most ideal solutions to this situation are:
 - Vuze is updated more frequently in the repositories.
 - The Vuze folks run their own Debian repository that you can add to sources.list to receive updates through the package manager. This way, new versions can be made available immediately to users of the packaged version, without relying on Ubuntu repository managers to get the update packaged and available right away. (There are already a number of application writers that make their applications available through their own repositories, so that updates can be retrieved automatically by the package manager: VirtualBox, Opera, Google Desktop/Picasa, MKVToolNix, Ubuntu Tweak, ....).