Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#76868 - [0ad] a26-2 requires which
Attached to Project:
Community Packages
Opened by Ryan Petris (ryanpetris) - Sunday, 18 December 2022, 06:44 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 19 December 2022, 09:34 GMT
Opened by Ryan Petris (ryanpetris) - Sunday, 18 December 2022, 06:44 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Monday, 19 December 2022, 09:34 GMT
|
DetailsDescription:
0ad does not launch unless the package "which" is installed. The actual binary "which" is only required by a handful of packages, and does not have a "built-in" equivalent in bash as zsh does. Since the 0ad launch script calls `which pyrogenesis` from /bin/sh, which is provided by bash, this causes the script to fail with the message "Error: pyrogenesis not found in (/usr/local/bin:...) Additional info: * package version(s): pyrogenesis * config and/or log files etc.: None * link to upstream bug report, if any :None Steps to reproduce: Perform a fresh install of Arch without installing which, or remove which, and attempt to launch 0ad via a desktop environment or via the 0ad command on the cli. |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Monday, 19 December 2022, 09:34 GMT
Reason for closing: Fixed
Monday, 19 December 2022, 09:34 GMT
Reason for closing: Fixed
Comment by Ryan Petris (ryanpetris) -
Sunday, 18 December 2022, 06:45 GMT
Package version should have been "a26-2"