Search Criteria
Package Details: arronax 0.8.1-7
Package Actions
| Git Clone URL: | https://aur.archlinux.org/arronax.git (read-only, click to copy) |
|---|---|
| Package Base: | arronax |
| Description: | Create and modify application, file and URI starters. |
| Upstream URL: | https://www.florian-diesch.de/software/arronax |
| Licenses: | GPL-3.0-or-later |
| Submitter: | max.bra |
| Maintainer: | yochananmarqos |
| Last Packager: | yochananmarqos |
| Votes: | 25 |
| Popularity: | 0.069046 |
| First Submitted: | 2015-02-05 16:23 (UTC) |
| Last Updated: | 2025-11-18 17:54 (UTC) |
Dependencies (13)
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classic-xfceAUR)
- libwnck3
- python-gobject
- python-pyxdg
- git (git-gitAUR, git-glAUR, git-wd40AUR) (make)
- intltool (make)
- python-build (make)
- python-installer (make)
- python-setuptools (make)
- python-wheel (make)
- nemo-python (nemo-python-gitAUR) (optional) – for Nemo extension
- python-caja (optional) – for Caja extension
- thunarx-pythonAUR (thunarx-python-gitAUR) (optional) – for Thunar plugin
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »
max.bra commented on 2022-01-22 23:28 (UTC)
@AZMCode no worries, these things happen and you are in good faith. I'm glad you found the source of the problem.
No it's not a change in base, i think.
who was the owner of /sbin (i mean pacman -Qo /sbin)? if it doesn't appear under any package there are two alternatives: you added it (along with the PATH change) and you don't remember it or some alternative package manager like flatpak did the things for you...
AZMCode commented on 2022-01-22 23:16 (UTC) (edited on 2022-01-22 23:17 (UTC) by AZMCode)
That's weird, I haven't manually altered my
$PATHat all.Perhaps it's a recent change in
base?I did install arch only recently.
In any case, This is Bug Over, Thank for y'alls support.
yochananmarqos commented on 2022-01-22 23:15 (UTC)
@AZMCode:
There's your problem. That is not default.
Apology accepted.
AZMCode commented on 2022-01-22 23:08 (UTC)
This was never a PKGBUILD issue, and I apologize for the inconvenience of spamming the comment section.
AZMCode commented on 2022-01-22 23:07 (UTC)
@yochananmarqos:
It's been a hectic day for me, so imma settle down and explain the summary of the bug:
In my system, as explained in https://man.archlinux.org/man/file-hierarchy.7.en
/sbinis a symlink to/usr/bin, which is where arronax is installed.Furthermore, my
$PATHcontains/sbinbefore/usr/bin, which means that all executables in/usr/binare by default executed from/sbin.Arronax, when executed from
/sbin, attempts to find itsuifiles and other necessary files for its operation starting from/sbin/arronax, which means that instead of finding/usr/share/arronaxit finds/share/arronax, which is wrong and causes the program to crash.This is fixed by a tiny patch now posted in the Launchpad bug page (https://bugs.launchpad.net/archlinux/+source/arronax/+bug/1958728) which simply resolves
/sbin/arronaxto/usr/bin/arronaxbefore attempting to find the required files, which works.yochananmarqos commented on 2022-01-22 22:59 (UTC)
@AZMCode: I don't know what's wrong on your system, but this is neither an upstream nor packaging issue. No one can reproduce it.
AZMCode commented on 2022-01-22 22:57 (UTC)
I've packaged the fix as a git patch and it's attached to the launchpad bug. I guess @max.bra could patch it in the PKGBUILD to all affected versions, but I'm not exactly sure how that sort of stuff works around these parts. Thank you for your patience.
AZMCode commented on 2022-01-22 22:23 (UTC) (edited on 2022-01-22 22:28 (UTC) by AZMCode)
Oh lord, um, I didn't expect this, but I found out that, in my system /sbin is a symlink to /usr/bin
That explains a lot of things
Relevant link: https://man.archlinux.org/man/file-hierarchy.7.en
Essentially this means that the program can break if
/sbinis before/usr/binin $PATHAZMCode commented on 2022-01-22 22:21 (UTC)
After a little bit of faffing about without much goal, I've decided to dig up the built package from the package cache (using yay to install this), and have found that the built package places the entry script at
/usr/bin, so it appears that this is not a problem with the PKGBUILDAZMCode commented on 2022-01-22 21:45 (UTC)
I'll try looking into the setuptools code to see what code decides where the executable is placed.
« First ‹ Previous 1 2 3 4 5 6 7 8 9 Next › Last »