Search Criteria
Package Base Details: nx
Package Actions
Git Clone URL: | https://aur.archlinux.org/nx.git (read-only, click to copy) |
---|---|
Submitter: | arojas |
Maintainer: | polygamma |
Last Packager: | polygamma |
Votes: | 4 |
Popularity: | 0.31 |
First Submitted: | 2022-04-01 19:04 (UTC) |
Last Updated: | 2023-09-04 13:34 (UTC) |
Latest Comments
1 2 3 Next › Last »
haja commented on 2024-02-24 17:05 (UTC)
Currently failing with:
…
…
petaramesh commented on 2023-09-04 14:20 (UTC)
@polygamma OK it seems that the package not upgrading issue was related to pamac keeping previous AUR source / build files in cache in /var/tmp/pamac-build/<user>
It usually causes no problem for upgrading packages, on the contrary it speeds up the process, but in this case, maybe because it was both a new release of the same version and the nx package produces several children, something went wrong in the upgrade.
rm -rf /var/tmp/pamac-build/<user> followed by another upgrade using pamac nailed it.
petaramesh commented on 2023-09-04 13:29 (UTC)
BTW would you be so kind as to add “aarch64" in the supported architectures list in PKGBUILD, as I need to add it manually everytime for it to compile on my ARM systems ?
polygamma commented on 2023-09-04 13:27 (UTC) (edited on 2023-09-04 13:28 (UTC) by polygamma)
Users : Unwilling to provide instructions to reproduce the problem. As usual.
petaramesh commented on 2023-09-04 13:26 (UTC)
Developpers : « Works4me». As usual.
polygamma commented on 2023-09-04 13:23 (UTC) (edited on 2023-09-04 13:24 (UTC) by polygamma)
Unless you are able to provide instructions to reproduce your problem (without using pamac, just with pacman and makepkg), I assume this package is working as intended.
petaramesh commented on 2023-09-04 13:22 (UTC) (edited on 2023-09-04 13:25 (UTC) by petaramesh)
@polygamma It's not about debugging “my” system, I see this issue with the latest nx packages on 4 different machines, 2 x86_64 and 2 aarch64.
Never had this problem with previous nx builds.
Never have this kind of problem with pamac and any other AUR package (and I have dozens of them...)
So I beg to differ and consider this a problem with this precise package, not all my 4 different machines showing the same behaviour with the same package.
(And precisely, the matter is that pacman and pamac both report the installed package is 3.5.99.27-1 even though I see 3.5.99.27-2 being compiled and properly installed. So I bet 3.5.99.27-2 installation wrongly identifies itself as 3.5.99.27-1)
1 2 3 Next › Last »