Vuze's updater will not upgrade to 4.0.0.4

[tak]

Binary package hint: vuze

The updater will download the 4.0.0.4 package and restart, then ask to download said package again, and fails to update.

[goto (gotolaunchpad)]

Is this behaviour wanted? I mean, is it wanted, that an application updated itself? Firefox can update itself, but the function was deactivated and an 'apt-get upgrade' updates firefox to the new version.

If azureus should be able to update itself then this is a bug. And if azureus should not, then it should not even try to update.

[tak (tak)]

Vuze has a built in upgradeing system, yeah, It would be smarter to
leave it to the package manager, but the package manager hasen't
switched to the newest version, and can't keep up with Vuze's built in
system.
On Sun, 2008-11-23 at 14:57 +0000, bugmenot wrote:
> Is this behaviour wanted? I mean, is it wanted, that an application
> updated itself? Firefox can update itself, but the function was
> deactivated and an 'apt-get upgrade' updates firefox to the new version.
>
> If azureus should be able to update itself then this is a bug. And if
> azureus should not, then it should not even try to update.
>
> ** Bug watch added: Debian Bug tracker #506027
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506027
>
> ** Also affects: azureus (Debian) via
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=506027
> Importance: Unknown
> Status: Unknown
>

[qweadawdq (asdasdasd1q2wqeq)]

Geez, this is really annoying. Same bug here, ubuntu 8.10

[joris (joris-dobbelaer-gmail)]

It might be a good thing that 'apt-get upgrade' updates azureus and not the build in azureus update manager, but then the update manager should be turned off by default.

Now the update manager starts when you start vuze for the first time. It asks to update and when you agree, it asks to restart. After restart, it asks again if you want to update and asks again to restart. It took me three restarts to realise this is a loop.

Please remember that azureus is one of the most popular open source programs on windows. For a lot of newbies it will be one of the first things they try to install on ubuntu and this doesn't make a nice impression.

[Stefano Maioli (smaioli)]

joris wrote:
> It might be a good thing that 'apt-get upgrade' updates azureus and not
> the build in azureus update manager, but then the update manager should
> be turned off by default.
>
> Now the update manager starts when you start vuze for the first time. It
> asks to update and when you agree, it asks to restart. After restart, it
> asks again if you want to update and asks again to restart. It took me
> three restarts to realise this is a loop.
>
> Please remember that azureus is one of the most popular open source
> programs on windows. For a lot of newbies it will be one of the first
> things they try to install on ubuntu and this doesn't make a nice
> impression.
>

A fix is ready and waiting to be committed. Please be patient, I'm kind
of busy lately. Sorry.

[goto (gotolaunchpad)]

@Stefano Maioli:
Great news and thank you!

[tak (tak)]

I used it for the first time on ubuntu switching from ktorrent, then to
transmission, =x I used utorrent on windows, but vuze actually pritty
versatile, and the plugins are more custom,

vuze's not updateing the update manager in this, its updateing the core
of vuze, which the package manager doesn't yet have, though it works if
you download the source.

On Wed, 2008-11-26 at 16:24 +0000, joris wrote:
> It might be a good thing that 'apt-get upgrade' updates azureus and not
> the build in azureus update manager, but then the update manager should
> be turned off by default.
>
> Now the update manager starts when you start vuze for the first time. It
> asks to update and when you agree, it asks to restart. After restart, it
> asks again if you want to update and asks again to restart. It took me
> three restarts to realise this is a loop.
>
> Please remember that azureus is one of the most popular open source
> programs on windows. For a lot of newbies it will be one of the first
> things they try to install on ubuntu and this doesn't make a nice
> impression.
>

[Allan Nordhøy (comradekingu)]

Im also having this problem (8.10 64bit)
There is a thread about this on the azureus boards http://forum.vuze.com/thread.jspa?threadID=78780

[goto (gotolaunchpad)]

I think the solution is simply disabling the function, isn't it?

[tak (tak)]

not quite, because you still have an outdated version, download the
source for vuze 4.0.0.4, and install it on your own, until the bug is
fixed,
On Sat, 2008-11-29 at 12:14 +0000, bugmenot wrote:
> I think the solution is simply disabling the function, isn't it?
>

[goto (gotolaunchpad)]

In the forum one guy said you should use the package management *or* the integrated updater, which makes sense I think. What if you use the integrated update tool to update to a complete new version and then a security update comes in via package management and overwrites some setting or something like this.
I am not sure if this will work so well.
Is there a way that the package management recognises that there is a new version installed by the application itself?

I think users that want the newest version load from azureus.sf.net and there works the integrated update, and the normal user does not need the integrated updater imo.

[Stefano Maioli (smaioli)]

Ok, this is going to be a bit of a mess. The problem is that, if I recall correctly, the update 3.1.1.0 -> 4.0.0.0 did work even on the packaged version. But maybe I'm mistaken.

Can anyone confirm that this actually happened:
- Installed 3.1.1.0 through package management.
- Updated to a newer version (e.g. 4.0.0.0) with the automatic updater.
- Verified that the update was successful and that azureus starts up as the new version.

If this is true, the azureus updater will be disabled by default but if the new version has already been downloaded we have to let the upgrade complete successfully. Otherwise some users will find themselves downgraded to 3.1.1.0 possibly losing settings and features. The downside of this solution is that if a users wants to stick with the ubuntu version (which should be the normal situation) he will have to manually delete his ~/.azureus directory.

To sum it up, we would:
- Turn the auto-update feature off by default.
- If a new jar has already been downloaded in the home directory, then use it.

I'm afraid the damage has been done to many home directories, which we cannot touch with package management. Blame debian for dropping the autoupdate-disable patch some time ago. :)

I think this is the way we should go, even if it doesn't really fit ubuntu's policy. I already implemented and tested this solution. If someone has suggestions, this is the time.

[Allan Nordhøy (comradekingu)]

Whats wrong with just updating the package to 4.0.0.4 from package management? It seems to work quite well. I removed the 3.0.0.1 package and manually installed the 4.0.0.4 from azureus.

The one at http://www.getdeb.net/comment/1566 seems to be incompatible according to the comments.

"This package is not correct
 By dalonso, 2008-11-06 22:26:50
This package should not be in the Intrepid category. The package depends on gtk-swt-3.2, that is incompatible with xulrunner-1.9, the version of gecko that comes with Intrepid.

You should rebuild it with gtk-swt-3.4, otherwise the Browser is not working. It's true that it works as long as downloading of torrents, but without the browser it is like using transmission.

So, please, please, rebuild with the correct dependencies so I can use this great program!!!"

I cant comment on this, but 4.0.0.4 seems to work fine using the classic UI, it even retained my settings and more importantly stopped the update loop.

I dont know about ubuntu policy, but why is there an ancient version in the repos? Since the package has been broken in the past in ubuntu i suggest stop pulling hacks out to fix it and just stick with the regular stable releases.
Either that or disable the auto-update check in vuze. There seems to be a lack of communication between the MOTU and the Vuze team. Hope it can be fixed soon :)

[tak (tak)]

On updating manually, it still asks for the 4.0.0.4 upgrade every
startup.
On Sun, 2008-11-30 at 02:03 +0000, kingu wrote:
> Whats wrong with just updating the package to 4.0.0.4 from package
> management? It seems to work quite well. I removed the 3.0.0.1 package
> and manually installed the 4.0.0.4 from azureus.
>
> The one at http://www.getdeb.net/comment/1566 seems to be incompatible
> according to the comments.
>
> "This package is not correct
> By dalonso, 2008-11-06 22:26:50
> This package should not be in the Intrepid category. The package depends on gtk-swt-3.2, that is incompatible with xulrunner-1.9, the version of gecko that comes with Intrepid.
>
> You should rebuild it with gtk-swt-3.4, otherwise the Browser is not
> working. It's true that it works as long as downloading of torrents, but
> without the browser it is like using transmission.
>
> So, please, please, rebuild with the correct dependencies so I can use
> this great program!!!"
>
> I cant comment on this, but 4.0.0.4 seems to work fine using the classic
> UI, it even retained my settings and more importantly stopped the update
> loop.
>
> I dont know about ubuntu policy, but why is there an ancient version in the repos? Since the package has been broken in the past in ubuntu i suggest stop pulling hacks out to fix it and just stick with the regular stable releases.
> Either that or disable the auto-update check in vuze. There seems to be a lack of communication between the MOTU and the Vuze team. Hope it can be fixed soon :)
>

[Allan Nordhøy (comradekingu)]

Not mine. Are you sure you removed the prior version that was installed from the repo? I can also "Check for updates..." without problems.

[WSmart (wsmart)]

The updates thing is a pain, but what really kills me is that my keyboard and mouse keep freezing. I can't access anything, have to hit reset.

Be real; be sober.

[Noel J. Bergman (noeljb)]

The built-in updater checks and makes many small in-flight updates as they are fixed and released by the project. If you download Vuze/Azureus today, you will get the code from October, and then it will automatically update itself.

So given the fact that this is how the project manages its own updates, and the fact that Ubuntu cannot manage to keep up with major releases, much less keep up with in-flight changes, yes, we want the project's own updater enabled and working. APT should be used for initial installation by newbies who don't know how to install it manually.

[goto (gotolaunchpad)]

Stephano Maioli:
Any news on this?

[Alps (alpsmathews)]

I am using Ubuntu, 8.10 and OpenJDK Java 6. I have installed vuze. But after it downloads the 4.0.0.4.jar update, it prompts me to restart the application (vuze) for insatlling the update. But after it restarts, its unable to install the update and again prompts me to restart and this process goes on. Its happening every time I open Vuze (Azureus)

[Dimitris Kalamaras (dimitris-kalamaras)]

Alps, I had the same problem with you, that is, I installed Vuze (from apt then 4.0.0.2 from their site) then tried to update but it kept on saying

"The following components need an update" ....
Core Azureus Version 4.0.0.4

although I did it again and again and again (and i had installed vuze 4.0.0.2!).

Then I realized that I was running the "azureus" script. When I clicked on "vuze" script, then voila there was my 4.0.0.2.

So, maybe you 're making the same mistake with me... Try the vuze script.

[John Ward (automail)]

Dimitris,

You say 4.0.0.2 was in the repositories yet I'm only seeing 3.0.1.0 ubuntu. Do you know what repository 4.0.0.2 is in?

I tried doing it as root, "sudo vuze" thinking to myself that as soon as the updater tried to remove or modify files in the system directories, ubuntu would refuse and hence the programme would fail to update, so running the programme as root would give it write access during the update process - no such luck, still at 3.0.1.0.

Is it possible to get a 4.0.0.4 into the repositories, and if not, why not?

[joris (joris-dobbelaer-gmail)]

For security reasons some trackers demand you use the latest stable versions of Azureus. At the moment i cannot upgrade to the most secure latest stable version from azureus in the repositaries. So i guess enabling the internal upgrade manager would be a good thing. I am not sure what the debian policy about this is, but from a pragmatic point of view i think it is a good thing if ubuntu users can get all the security and bugfixes available.

[Termina (termina)]

I've been having this same problem for months; is it ever going to be fixed?

[Davias (davias)]

Same problem on Ubuntu 8.10 amd64 w Sun Java: Azureus 3.1.1.0 tries to upgrade forever to 4.1.0.0.
I changed Java from default ubuntu conf., but no luck with Vuze; the rest works wonders with the sun java plugin 64 bit.
Thanks to all!

[Aaron Kelley (aaronkelley)]

It can't update itself because, if Vuze is installed by the Ubuntu package manager, it is installed system-wide and as a regular user, you do not have permission to modify the executable. If Vuze tries to update itself, it will not have permission, and fail. You may be able to force it somehow, but that's not a good idea, because then the version of Vuze that you have installed will be out of sync with the version that the Ubuntu package manager thinks you have.

Choices are:
 - Download Vuze from their web site, drop it somewhere in your home directory, and run it from there. It should be able to update itself fine.
 - Disable Vuze's automatic updates and rely on Ubuntu's update manager. Updates will be fewer and far between, but you get a nice pre-packaged app that gets installed for all users.

To solve this bug, I think that Vuze's built-in updater should be disabled (if you are using the version installed via Ubuntu's package manager), like it is with Firefox and some other apps. (However, Vuze should still be able to automatically check for updates to plug-ins that you have installed, because that works fine.)

[WSmart (wsmart)]

That would be Tools>Options>Interface>Start, there's a couple boxes there.

Looks like this topic is closed. Thanks all.

Be real, be sober.

[WSmart (wsmart)]

Now, how do we get debtorrent to work with Azureus? :)

[Jeffrey Theobald (jeffrey-theobald)]

As already stated several times, completely disabling the built in updater is not really a sensible solution. If your definitive answer is to not use the package manager version if you want auto updates, then you really need to think about what package management is meant to do.

The whole reason for package management is so that you know what is installed where and how, so that you can keep track of the hundreds of things installed. If you are honestly recommending not using the package manager version then you're making peoples lives unnecessarily hard. Why should I have to remember which programs need to be manually looked after because the package manager version is pointlessly crippled.

[Aaron Kelley (aaronkelley)]

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, ....).

[Noel J. Bergman (noeljb)]

Jeff, re-read Aaron's comments. The correct answer, which he gave, is to not install Vuze from the Ubuntu repositories, because you would end up with an out-of-date*, only partially usable**, package. Vuze should be installed from its own download site.

* Even if the currently download-able version were in the repository, it is already out-of-date because Vuze is *designed* to perform important, in-flight, updates. Aaron's ideal situation doesn't work simply because not even Vuze re-rolls the tarball with all of their in-flight updates, so his alternative solution would require someone to do a lot of work that Vuze does not do.

** q.v., "For security reasons some trackers demand you use the latest stable versions of Azureus."

By the way, the current version is now Vuze 4.1.

[WSmart (wsmart)]

Azureus updates via torrent files. Not sure how torrents work with the Ubuntu package manager. I guess there's deb torrent for that, now; but running two torrent clients.....not me like, my bad(: . I prefer to get my everything via torrent, so a direct download via source list would not be an ideal solution. There might be other issues related to the torrent based updates, too.

And aren't there issues with installing programs outside of the package management system? I think I remember a recommendation to uninstall before a distro upgrade...maybe that was Alberto Milone's Envy graphics driver program.

Just adding a .deb package to the repository manually would be a problem? Azureus would update itself normally but the repo, I guess, would not reflect any of the changes. Seems like that would be the easiest solution, but maybe that's full circle back to where we started and why doesn't the repo package update properly. If Azureus simply provided a .deb at their website and you added that manually to the package manger, would that also fail to update I wonder. If I had to add each new update manually, I wouldn't really care. Not a huge deal. That way I could still download via torrent and the repo would reflect the versions correctly.

Thanks for noodling on this Aaron.

Thanks all!

Be real, be sober.

[Aaron Kelley (aaronkelley)]

I'll respond to a couple points...

"If Azureus simply provided a .deb at their website and you added that manually to the package manger, would that also fail to update I wonder."

Yes, it would fail to update, for the same reason. The update failure is because Azureus/Vuze is installed in a location that users are not allowed to write to. (I am not aware of any .deb, from the Ubuntu repositories or not, that installs an application in a location or with permissions that a user would be allowed to modify it. But, maybe such a thing does exist.)

The ways that occur to me to fix this are...

 - As I've mentioned before, install Azureus/Vuze yourself in your home directory. Then automatic updates will work fine.
 - Azureus/Vuze is made to be more "Linux[/Ubuntu] aware" and prompts for credentials to run with elevated privileges so that it can update itself.
 - You go manually set permissions to be more relaxed, so that Azureus/Vuze can update itself without elevated privileges.

Those second two I think are bad ideas, again, if you're using the packaged version of an application, it shouldn't be updated by anything besides the package manager, so that the package manager is aware of the changes (and can possibly handle changed dependencies). Plus, I'm not even sure if they'd even work, the packaged version may be installed in a different manner than Vuze's updater expects. (I'm not aware of the fine details here.)

Side note - if the Azureus folks were to provide a .deb file, it wouldn't be a big leap from there to provide a Debian repository (and just update it as new versions of Azureus are released), which you could add to your list of repositories and solve this problem. However, I don't know of any plans of them to offer this, I don't see it happening in the near future, it's something you'd have to take up with them. :-)

This is not really just a problem with Vuze, but with any application with a built-in updater. If you used a packaged version, you are relying on the repository maintainers and package manager to keep you up to date. If you'd like to keep yourself up to date or let the application to it itself, you've got to install the application yourself...

[WSmart (wsmart)]

How 'bout adding the Azureus default directory to the source list where the torrent update is a .dcb?

A contribution share ratio provides a context to community contributions and empowers people to do more.

[Anders Kaseorg (andersk)]

Here’s a quick and dirty workaround. After using the Vuze updater, run

mkdir ~/bin
sed 's,/usr/share/java/Azureus2.jar,$HOME/.azureus/Azureus2.jar:/usr/share/java/commons-cli-1.1.jar:/usr/share/java/log4j-1.2.jar,' /usr/bin/azureus > ~/bin/azureus
chmod +x ~/bin/azureus

log out and log in (to ensure ~/.profile will add ~/bin to your PATH), then run vuze again.

[Davias (davias)]

Great! It worked like a charm! I just noted that ~/bin was already there so the first line (mkdir ~/bin) was not necessary

To make shure for others:

1) I run the updater from Vuze 3.1; when finished I closed Vuze instead of restarting.
2) followed Anders instructions
3) logout & login again

Now Vuze 4.1.04 has started! It asked to update the UPnP server to 2.5, and this time the autoupdater worked!

My system: Ubuntu 8.10 AMD64, Linux v2.6.27-11-generic,
Java 1.6.0_12-ea Sun Microsystems Inc. SWT v3448, gtk,
amd64Athlon X2 4800, 2 GB, 2 x 400GB Sata Raid 1 (mdadm)
VMWare server 2

Thank you Anders, Vuze 3 was leaking memory all over, and my system was swapping to disk too much...
Thanks!

[WSmart (wsmart)]

How's the package manager feeling after that Davias?

Thanks for posting this work around Anders. You managed to provide a solution that addressed the problem in the context that it was presented. Oh those crazy humans.

[Davias (davias)]

If you mean the Install/Remove standard Ubuntu packet manager, fine. Vuze was installed from there (3.1) and still results installed.

[WSmart (wsmart)]

I mean synaptic(System>Administration>Synaptic). Didn't think that you could insall Vuze via add/remove. I suppose Synaptic is not showing the new version as installed version, but I'm curious.

[Anders Kaseorg (andersk)]

The Vuze built-in updater will install the updated Vuze inside your home directory (~/.azureus). The system Vuze package will not be affected (so, for example, Synaptic will still show the old version). All my workaround does is let you run the copy of Vuze that was installed in your home directory, rather than the copy that was installed by the package manager.

[Stephen Hanafin (shanafin)]

This is still broken following the release of Jaunty :(

Why is the vuze version in the repos so ancient anyway? I know the repos don't update as often as vuze themselves do but 3.x is ancient history.

[Aaron Kelley (aaronkelley)]

Once again, Vuze's built-in updater is not expected to work if you are using the version installed by the package manager. This copy of Vuze should only be updated by the package manager. If you want Vuze's built-in updater to work, just download it from their web site and run it from somewhere in your home directory.

That being said, I'm also disappointed that the version in the repositories is so old. However, it looks like Ubuntu just gets Vuze from Debian's repositories, and they have a really old copy too. Might be worth filing a bug over there, or looking into what it would take to get the new version packaged and distributed in Ubuntu.

[noisymime (josh-noisymime)]

I've packaged up Vuze 4.2.0.2 for ubuntu in case anyone is desperate for the update. Its in my ppa at http://launchpad.net/~josh-noisymime/+archive/ppa

I know its not a great solution to the problem, but at least it gives people an option.

[sirald66 (sirald66)]

8 months down for a major package. Impressive.

[sirald66 (sirald66)]

Java 1.6.0_0 Sun Microsystems Inc. [OpenJDK]
SWT v3448, gtk
Linux v2.6.28-14-generic, i386
Ubuntu 9.04
Gnome 2.26.1
Vuze 4.2.0.2

EXPECTED: Install fresh Vuze, full abilities.

ACTUAL: Install fresh Vuze, bittorrent interface loads, but not multimedia site interface and skin.

DETAILS: Had to manually nuke version 3 out of /root/.azureus and /home/user/.azureus before fresh install from NoisyMime's PPA. Ran jaunty janitor. Post install, answered setup questions and received two additional updates (plugins I think).

ANDY

[[e-mail] (brody-pierre)]

I get the same phenomenon, but my version of Vuze is 3.1.1.0 and it is asking to upload to 4.2.0.8

[Adrian Perez (adrianperez-deb)]

Hello.
Since azureus 4.2.0.4-1 I've disabled *core* updates within azureus. I hope you agree with my decision that the debian archive must have precedence over individual updates, and we shouldn't let break sync with it.
There are still some minor plugins being updated since they not affect the azureus core functionality, although I think I'll have to disable some more.
Currently, azureus in debian has the following components disabled:
* Core Updater
* Core Patcher updates
* SWT library updates

Hope this clarifies a little.
Hopefully, 4.2.0.8-1 will be included in karmic.

[milkham (milkham)]

If i remove the version I installed through the package manager will all my in-progress torrents be removed as well? or will they show up again after i install the version downloaded directly from vuze?

[Adrian Perez (adrianperez-deb)]

I don't see the reason why to download vuze directly, since the version
in the repos is the current upstream release.
As long as you don't delete ~/.azureus your configuration and/or
torrents will stay untouched among upgrades.

On Tue, 2009-10-06 at 04:51 +0000, milkham wrote:
> If i remove the version I installed through the package manager will all
> my in-progress torrents be removed as well? or will they show up again
> after i install the version downloaded directly from vuze?
>
> ** Description changed:
>
--
Best regards,
Adrian Perez <email address hidden>