giantpinkrobots/varia

Is there any Installation guide without using flatpak?

denisgolius opened this issue ยท 8 comments

Hello!
Could you please add an instruction for users who don't want to use flatpak? I mean something like:

git clone (https://github.com/giantpinkrobots/varia.git
cd varia
install meson
run meson build...

I have added a 'Building' section to the README. Thanks for the suggestion.

The build instructions were broken, so I removed them and I am reopening this issue to serve as a reminder to fix the code to support non-Flatpak building.

Hi @giantpinkrobots

I've trying packaging varia with src2pkg on Slackware (15+) and I think I have the package itself sorted out:

cd $SRC_DIR
meson setup builddir
cd builddir
meson compile
DESTDIR=$PKG_DIR meson install

... where $SRC_DIR is the unpacked source code and $PKG_DIR is the target install folder (for packaging). These, as far as src2pkg is concerned, equate to:

$SRC_DIR = /tmp/varia-v2023.12.07-src-2 (builddir is inside here)
$PKG_DIR = /tmp/varia-v2023.12.07-x86_64-2

I'm using /usr/local as my base for the final installation target so the $PKG_DIR includes /usr/local/share and /usr/local/bin files from the meson install.

The issue: neither varia or aria2c initially runs and I get the following output:

/usr/local/bin/varia: line 4: /usr/local/share/varia/../../aria2/aria2c: No such file or directory
Traceback (most recent call last):
  File "/usr/local/share/varia/../../bin/varia-py.py", line 38, in <module>
    from variamain import main
  File "/usr/local/share/varia/varia/variamain.py", line 556
    match self.appconf["download_speed_limit"][-1]:

I can update /usr/local/bin/varia to point to the correct location of aria2c by changing:

$pkgdatadir/../../aria2/aria2c --enable-rpc --rpc-listen-port=6801 &

to

$pkgdatadir/../../../bin/aria2c --enable-rpc --rpc-listen-port=6801 &

(which is the correct location of aria2c now), but still get an error:

/usr/local/bin/varia

12/08 16:57:12 [WARN] Neither --rpc-secret nor a combination of --rpc-user and --rpc-passwd is set. This is insecure. It is extremely recommended to specify --rpc-secret with the adequate secrecy or now deprecated --rpc-user and --rpc-passwd.

12/08 16:57:12 [NOTICE] IPv4 RPC: listening on TCP port 6801

12/08 16:57:12 [NOTICE] IPv6 RPC: listening on TCP port 6801
Traceback (most recent call last):
  File "/usr/local/share/varia/../../bin/varia-py.py", line 38, in <module>
    from variamain import main
  File "/usr/local/share/varia/varia/variamain.py", line 556
    match self.appconf["download_speed_limit"][-1]:
          ^
SyntaxError: invalid syntax

At least now, arai2c itself is running, but still not varia. The file locations in the error section above are confirmed correct.

If I try to run the varia python directly:

Traceback (most recent call last):
  File "/usr/local/bin/varia-py.py", line 38, in <module>
    from variamain import main
  File "/usr/local/share/varia/varia/variamain.py", line 556
    match self.appconf["download_speed_limit"][-1]:

Any ideas?

Thanks, Robby

Hi @giantpinkrobots

I've trying packaging varia with src2pkg on Slackware (15+) and I think I have the package itself sorted out:

cd $SRC_DIR
meson setup builddir
cd builddir
meson compile
DESTDIR=$PKG_DIR meson install

... where $SRC_DIR is the unpacked source code and $PKG_DIR is the target install folder (for packaging). These, as far as src2pkg is concerned, equate to:

$SRC_DIR = /tmp/varia-v2023.12.07-src-2 (builddir is inside here) $PKG_DIR = /tmp/varia-v2023.12.07-x86_64-2

I'm using /usr/local as my base for the final installation target so the $PKG_DIR includes /usr/local/share and /usr/local/bin files from the meson install.

The issue: neither varia or aria2c initially runs and I get the following output:

/usr/local/bin/varia: line 4: /usr/local/share/varia/../../aria2/aria2c: No such file or directory
Traceback (most recent call last):
  File "/usr/local/share/varia/../../bin/varia-py.py", line 38, in <module>
    from variamain import main
  File "/usr/local/share/varia/varia/variamain.py", line 556
    match self.appconf["download_speed_limit"][-1]:

I can update /usr/local/bin/varia to point to the correct location of aria2c by changing:

$pkgdatadir/../../aria2/aria2c --enable-rpc --rpc-listen-port=6801 &

to

$pkgdatadir/../../../bin/aria2c --enable-rpc --rpc-listen-port=6801 &

(which is the correct location of aria2c now), but still get an error:

/usr/local/bin/varia

12/08 16:57:12 [WARN] Neither --rpc-secret nor a combination of --rpc-user and --rpc-passwd is set. This is insecure. It is extremely recommended to specify --rpc-secret with the adequate secrecy or now deprecated --rpc-user and --rpc-passwd.

12/08 16:57:12 [NOTICE] IPv4 RPC: listening on TCP port 6801

12/08 16:57:12 [NOTICE] IPv6 RPC: listening on TCP port 6801
Traceback (most recent call last):
  File "/usr/local/share/varia/../../bin/varia-py.py", line 38, in <module>
    from variamain import main
  File "/usr/local/share/varia/varia/variamain.py", line 556
    match self.appconf["download_speed_limit"][-1]:
          ^
SyntaxError: invalid syntax

At least now, arai2c itself is running, but still not varia. The file locations in the error section above are confirmed correct.

If I try to run the varia python directly:

Traceback (most recent call last):
  File "/usr/local/bin/varia-py.py", line 38, in <module>
    from variamain import main
  File "/usr/local/share/varia/varia/variamain.py", line 556
    match self.appconf["download_speed_limit"][-1]:

Any ideas?

Thanks, Robby

Right now Varia assumes a Flatpak environment, that's why my previous attempt at adding a non-Flatpak build guide failed miserably. It will require some modification to the code. I suggest you wait a bit until a non-Flatpak build is possible.

I don't have the time to contribute an installation guide, but I have created a pkgbuild install script for Arch linux which should be of some help to those on other distros since its mostly shell scripts. If you're an Arch user, it should be available for install with any AUR helper or package manager.

Its worth mentioning the launch script is broken outside of flatpak with the current release (2023.12.7), which is the reason for the patch used in the pkgbuild. This has been fixed and presumably won't be needed in the next release.

Thank you very much for the info; I'll have a go at adapting the Arch script. Looks very similar to what I've done but there are some small important items there that could resolve my issue.

Thank you and regards, Robby

Building from source guide is officially here, and it works. Thank you all for waiting.

Building from source guide is officially here, and it works. Thank you all for waiting.

Thanks you!