Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: vuze 5.7.4.0-1

Git Clone URL: https://aur-dev.archlinux.org/vuze.git (read-only)
Package Base: vuze
Description: A feature-rich Java-based BitTorrent client (previously called 'Azureus')
Upstream URL: http://sourceforge.net/projects/azureus/
Licenses: GPL
Submitter: td123
Maintainer: Det
Last Packager: Det
Votes: 120
Popularity: 2.939921
First Submitted: 2011-07-31 04:31
Last Updated: 2016-12-17 21:03

Dependencies (5)

Sources (1)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

rafaelff commented on 2013-09-01 16:00

@vorbote: many thanks for the effort you put to rearrange the files in FHT. I looks awesome! And thanks for the instructions. It worked just fine for me.

As suggestion, here the command lines to apply the steps 3, 4 and 5 (obviously, replace CARCH with your architecture, i686 or x86_64):

mv /tmp/swt-4403-gtk-linux-${CARCH}.zip $HOME
sudo rm /usr/lib/vuze/swt64.jar
sudo unzip swt-4403-gtk-linux-${CARCH}.zip -d /usr/lib/vuze/swt64.jar
rm -rf ~/.swt/

vorbote commented on 2013-09-01 15:49

I haven't found a way to divine the direct download links for the latest SWT update, if someone discovers how to pull those files from some server at Vuze's it is much appreciated.

As some of you may have discovered yet, Vuze uses a development version of SWT that is not available in the repos nor the AUR. So I will outline here a procedure to *update manually* Vuze's private SWT copy:

0. VERY IMPORTANT: Update your installation to 5.1.0.0-3 as I have, finally, updated the PKGBUILD to install binaries in their proper FHS location, namely /usr/lib. Previously binaries where installed in /usr/share, which I should have corrected when I inherited this package. My bad.

1. Run Vuze. When it start up it asks you to download an updated SWT. Let it do its thing.

2. When Vuze restarts, it will ask again to download SWT. Ignore it and quit Vuze instead.

3. Go to /tmp, there you will find a ZIP file called swt-4403-gtk-linux-{$CARCH}.zip. Copy it somewhere safe.

4. Extract the swt.jar file from the ZIP file and overwrite /usr/lib/vuze/swt64.jar

5. Delete $HOME/.swt

And you are done.


4.

Etzos commented on 2013-08-18 02:03

I don't think it's a good idea to change the PKGEXT in a PKGBUILD like you do. I'm pretty sure that's supposed to be more of a user choice.

vorbote commented on 2013-08-16 22:10

@willemw **Sigh** That's the reality of taking care of inherited loot. :-) Thanks for spotting it. Fixed.

willemw commented on 2013-08-16 08:12

/usr/sbin in the .install file is obsolete now. Should be: /usr/bin.

vorbote commented on 2013-07-11 13:31

@evilxel Fixed.

BTW, your patched file is unnecesary and the proper fix was to edit a line in the PKGBUILD file. Would you mind removing your comment below? It may lead people to donwload an unneeded file and try to "fix" their installation by hand when the PKGBUILD is already working fine.

And another BTW, I like the idea behind your ordered download plugin. Why don't you upload a PKGBUILD to the AUR? You can use one of my other vuze-related PKGBUILDs as a guide.

vorbote commented on 2013-07-11 13:31

@evilxel Fixed.

BTW, your patched file is unnecesary and the proper fix was to edit a line in the PKGBUILD file. Would you mind removing your comment below? It may lead people to donwload an unneeded file and try to "fix" their installation by hand when the PKGBUILD is already working fine.

BTW, I like the idea behind your ordered download plugin. Why don't you upload a PKGBUILD to the AUR? You can use one of my other vuze-related PKGBUILDs as a guide.

Anonymous comment on 2013-07-11 12:11

Please add this in pkgbuild.

http://patraulea.com/azureus-ordered-download.patch/Azureus2-5.0.0.0.jar

Rename to Azureus2.jar

Copy to /usr/share/vuze/

Also Vuze won't start... thanks.

rafaelff commented on 2013-05-10 21:51

Guys, both of you, let's try to keep the courtesy, and avoid attacking each other. Please.

@Vorbote, allow me to partially agree with @zozi56 comments. Sometimes it happens all the that developers do a terrible job, and I agree with you of being mad at that.
But, in the end, who will read your PKGBUILD is not the developer, but the AUR user who might feel offended by the comments, which I know is not your intention.
My suggestion: Keep it clean, with relevant comments (e.g.: # This is bugged, won't work without the following workaround) and done - it will be flawless.
Except for that incident, keep up with the good work

vorbote commented on 2013-05-10 16:01

@zozi56 So I'm unprofessional for expressing my "emotional state"? I appreciate your politeness but not the speciousness of your affirmations. I'm not expressing "emotional state", I'm stating my contempt towards unprofessional (lack of) release engineering.

Why don't you remove the comments yourself? I'll be very happy to transfer the git repos ownership to you. When you have control of those, I'll orphan the package here in AUR. Else, the comments will remain until upstream fixes its package.