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#78849 - [element-web] should be arch=any (it's TypeScript app)
Attached to Project:
Arch Linux
Opened by Marcell Meszaros (MarsSeed) - Wednesday, 21 June 2023, 01:36 GMT
Opened by Marcell Meszaros (MarsSeed) - Wednesday, 21 June 2023, 01:36 GMT
|
DetailsDescription:
The 'element-web' package from 'element.io' base package should be declared an arch=any package. Only its other split package, 'element-desktop', is x86_64 specific. An AUR user maintained an AUR/elment-web-bin package just because he could correctly set its metadata as arch=any and was able to use that package on ARM architecture, running it on Aarch64-built electron. That AUR package has been deleted (PRQ#42444), but then its former owner complained because he cannot use the repo 'element-web' package on ARM just because of this erroneously declared arch=x86_64 metadata. Additional info: * package version(s): element-web 1.11.33-1 * source of the problem: inherits arch=(x86_64) from basepkg * how to resolve: declare arch=(any) inside package_element-web(){} |
This task depends upon
Comment by Doug Newgard (Scimmia) -
Wednesday, 21 June 2023, 01:46 GMT
Things have been this way because devtools couldn't handle differing architectures in a split package. Unless that's changed in the latest updates, this can't be done right now.
Comment by Maksim (DragonX256) -
Wednesday, 21 June 2023, 02:31 GMT
And you got deleted element-web-bin from AUR just to wait for devtools update to fix this bug? Cool, guys, cool...