AUR package build error: missing 'img/logo_256.png' in PKGBUILD for BaseX
Hi BaseX team,
I am writing to report a possible bug for the AUR package of BaseX.
For context, my environment is Omarchy/Arch Linux, and the command I am invoking is 'yay -S basex'.
Error:
install: cannot stat 'img/logo_256.png': No such file or directory ==> ERROR: A failure occurred in package(). Aborting... -> error making: basex-exit status 4 -> Failed to install the following packages. Manual intervention is required: basex - exit status 4
Investigation:
Looking on the upstream GitHub source I couldn't find any 'logo_256.png' file.
Please let me know if I can provide any more info to help address this error.
Thank you for reviewing my issue.
- Christian
hi Christian -
I don't know who manages the AUR packaging process in the Arch sphere of communities, but an update to the PKGBUILD process maybe needs to happen. It looks like there's an extract and install logo step[1] that needs a small syntax change:
from: jar -xf basex/BaseX.jar img/logo_256.png
to: jar -xf basex/BaseX.jar img/logo_large-0.png
Maybe there was a change in how BaseX bundles up those PNGs for the JAR back in the past.
Hopefully that helps! Best, Bridger
Quoted text · Christian Davidson · 36 lines
On Tue, Oct 21, 2025 at 10:05 AM Christian Davidson via BaseX-Talk <basex-talk at mailman.uni-konstanz.de> wrote: > > Hi BaseX team, > > I am writing to report a possible bug for the AUR package of BaseX. > > For context, my environment is Omarchy/Arch Linux, and the command I am > invoking is 'yay -S basex'. > > > Error: > > install: cannot stat 'img/logo_256.png': No such file or directory > ==> ERROR: A failure occurred in package(). > Aborting... > -> error making: basex-exit status 4 > -> Failed to install the following packages. Manual intervention is > required: > basex - exit status 4 > > > Investigation: > > Looking on the upstream GitHub source I couldn't find any > 'logo_256.png' file. > > > > Please let me know if I can provide any more info to help address this > error. > > Thank you for reviewing my issue. > > - Christian >
Written for BaseX 12.0. BaseX may have changed since: please check the current documentation.