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
Last edited by Antonio Rojas (arojas) - Wednesday, 21 June 2023, 08:47 GMT
Opened by Marcell Meszaros (MarsSeed) - Wednesday, 21 June 2023, 01:36 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 21 June 2023, 08:47 GMT
|
Details
Description:
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
Closed by Antonio Rojas (arojas)
Wednesday, 21 June 2023, 08:47 GMT
Reason for closing: Not a bug
Additional comments about closing: See comments
Wednesday, 21 June 2023, 08:47 GMT
Reason for closing: Not a bug
Additional comments about closing: See comments
I just tried to build it with `arch=(any)' inserted into package_element-web() and all went fine. Maybe that was a thing of the past?
> wait for devtools update to fix this bug? Cool, guys, cool...
@DragonX256, Please refer to the Arch Code of Conduct, especially this para [1]. You don't want to risk getting banned.
[1] https://terms.archlinux.org/docs/code-of-conduct/#do-not-flame
makepkg supports it fine, it's dbscripts (that moves the built packages to the repos) which doesn't support it.