Package Details: biglybt 2.5.0.0-1

Git Clone URL: https://aur.archlinux.org/biglybt.git (read-only, click to copy)
Package Base: biglybt
Description: Feature-filled Bittorrent client based on the Azureus project
Upstream URL: https://www.biglybt.com/
Licenses: GPL3
Submitter: Det
Maintainer: mrxx
Last Packager: mrxx
Votes: 10
Popularity: 0.091641
First Submitted: 2017-12-26 15:31
Last Updated: 2020-09-23 17:36

Required by (0)

Sources (1)

Latest Comments

1 2 3 4 Next › Last »

kinghat commented on 2020-12-03 19:38

i get this hangup when building: https://0bin.net/paste/d52-eFT+#O9O008BjsFTl+w1XA3v72dVTW9rC+qKGp7vXewFf6y4

ector commented on 2020-09-25 12:06

Thank @mrxx. Cheers

mrxx commented on 2020-09-24 22:49

ector, it is always a good idea to be sceptical of AUR packages generally (after all, anyone can submit them) and especially if a PKGBUILD wants to execute an external shell file.

Here, the PKGBUILD is doing the same as you would do manually, it executes the installer provided as a shell script from the BiglyBT developers. If you do not trust them, download the installer yourself from their homepage and inspect it before installing this package.

ector commented on 2020-09-24 09:06

Hi, from my terminal havi this : archlabs% baph -i biglybt
:: Cloning biglybt package repo... Clone in 'biglybt' in corso... remote: Enumerating objects: 144, done. remote: Counting objects: 100% (144/144), done. remote: Compressing objects: 100% (116/116), done. remote: Total 144 (delta 28), reused 144 (delta 28), pack-reused 0 Ricezione degli oggetti: 100% (144/144), 40.00 KiB | 553.00 KiB/s, fatto. Risoluzione dei delta: 100% (28/28), fatto. :: View/Edit the PKGBUILD for biglybt? [Y/n] n error: PKGBUILD contains a banned (possibly malicious) command on line 35: 'sh GitHub_BiglyBT_Installer_$pkgver.sh -q -dir "$srcdir"/$pkgname'

centqwerG7890FCT commented on 2020-05-26 03:00

Wow. I thought that maybe this could be improved so I deleted the link to libswt-gtk-4924r25.so and then restarted BiglyBT. BiglyBT remade libswt-gtk-4934r5.so the instant I opened it. The file is different than the libswt-gtk-4934r5.so that was already on it, ie. different sum. It appears that libswt-gtk-4934r5.so was corrupt. If anyone else has the problem then rename that file so BiglyBT can remake the file.

centqwerG7890FCT commented on 2020-05-26 02:52

Thanks mrxx. Got it working. When I saw your post the first thing I thought of is that Manjaro didn't offer openjdk 14. I had 13 as the default because that was the highest version I had. I installed jdk 14 from the AUR and set it as default but I get the exact same error. Maybe its an Arch vs. Manjaro thing going on here. So I then uninstalled jdk 14 since that wasn't it. Then I noticed that libswt-gtk-4934r5.so is actually on my computer and biglybt is loading it. I left out a part of the error message because I had to type it in. Something about a PowerPC library was not compatible with an AMD platform. So I renamed the libswt-gtk-4934r5.so file to libswt-gtk-4934r5.so.bak and made a link from libswt-gtk-4924r25.so to libswt-gtk-4934r5.so. This last part fixed it. Your post helped immensely. Thanks again.

mrxx commented on 2020-05-25 21:40

centqwerG7890FCT, on my machines it starts like this:

Starting BiglyBT...

Suitable java version found [java = openjdk 14.0.1 2020-04-14]

Using swt/swt-x86_64.jar v4.924

Maybe you're using an incompatible java package.

Use "archlinux-java" to fix your java environment or select a different one (I've installed jre-openjdk).

centqwerG7890FCT commented on 2020-05-23 20:58

Can't launch. I get the following errors: GUI could not be loaded. java.lang.UnsatisfiedLinkError: Could not find SWT library. Reasons: no swt-gtk-4934r5 in java.library.path [/opt/biglybt] no swt-gtk in java.library.path [/opt/biglybt] ~/.swtlib/linux/x86_64/libswt-gtk-4934r5.so Can't load library: ...

mrxx commented on 2020-03-18 22:39

Thanks, eschwartz and SolarAquarion.

A fake homedir is created below $srcdir now and the installer writes everything into it.

eschwartz commented on 2020-03-18 21:53

Can't you trick the installer into writing those files into the $srcdir by faking the $HOME?