termux / termux-app

Termux - a terminal emulator application for Android OS extendible by variety of packages.
https://f-droid.org/en/packages/com.termux
Other
31.29k stars 3.32k forks source link

[Bug]: nodejs Dependencies #3925

Closed Vanillma closed 3 weeks ago

Vanillma commented 3 weeks ago

Problem description

Hi there,

After updating libicu, I noticed that nodejs is complaining about missing softlinks from the previous version. :) Screenshot_20240421-110530_Termux Screenshot_20240421-110628_Termux

Should I create them myself? Use the previous version of libicu? (Since it's still available in the repository) Or will there be an update for nodejs?

Thanks,

Steps to reproduce the behavior.

apt update libicu npm ls -gt or Any command

Biswa96 commented 3 weeks ago

libicu dependencies are being rebuilt. Please wait until those are completed. The pending pull requests can be found here https://github.com/termux/termux-packages/pulls

Vanillma commented 3 weeks ago

libicu dependencies are being rebuilt. Please wait until those are completed. The pending pull requests can be found here https://github.com/termux/termux-packages/pulls

Thanks for the explanation...so I'll close this issue...and wait...until then I'll use the previous version :)

If anyone had a similar problem pkg update && pkg upgrade

TomJo2000 commented 3 weeks ago

If anyone had a similar problem pkg i libicu=74.2-1

Termux uses a "rolling release" model. We don't keep or support older versions of packages, please just do a full package upgrade. Using: pkg up

TomJo2000 commented 3 weeks ago

NodeJS is rebuilding right now, I'm sorry that got delayed, PHP in the same batch was having some issues, it's been moved to a separate rebuild batch now. We should have it updated within 4-5 hours, not accounting for mirror sync delays.

This same song and dance happens every new libicu version. And building out specific backward compatibility for the usually 6 to 12 hour period of interruptions caused by it is not worth the effort and overhead required.

TomJo2000 commented 3 weeks ago

If you absolutely need NodeJS as soon as possible, (i.e like 3 hours earlier than when it's gonna be updated on the repos)

You can grab it from the build artifacts of the CI run linked above once that finishes.


(This is a pre-written, saved reply.) If you want to test this PR please download the appropriate DEB package(s) from the build artifacts of the associated PR's latest CI run. image

After downloading the build artifact, make sure to unzip and un-tar it.

Detailed instructions, if needed.

```bash # finding out what architecture you need # architecture is just below the TERMUX_VERSION termux-info # e.g. # [...] # TERMUX_MAIN_PACKAGE_FORMAT=debian # TERMUX_VERSION=0.118.0 # TERMUX__USER_ID=0 # Packages CPU architecture: # aarch64 # [...] # ======================= # make sure `unzip` and `tar` are installed using pkg install unzip tar # unzip the artifact (if you have a different architecture this might be arm, i686 or x86_64 instead) unzip debs-aarch64-*.zip # untar the artifact tar xf debs-aarch64-*.tar # You should now have a debs/ directory in your current working directory # Install the packages from the local source using pkg install -- ./debs/*.deb # to clean up, you can remove the debs/ directory, .tar file and .zip file rm -rfi debs debs-aarch64-*.zip debs-aarch64-*.tar ```

Vanillma commented 3 weeks ago

If you absolutely need NodeJS as soon as possible, (i.e like 3 hours earlier than when it's gonna be updated on the repos)

You can grab it from the build artifacts of the CI run linked above once that finishes.

(This is a pre-written, saved reply.) If you want to test this PR please download the appropriate DEB package(s) from the build artifacts of the associated PR's latest CI run. image

After downloading the build artifact, make sure to unzip and un-tar it.

Detailed instructions, if needed.

Thank you very much...now I saw that the previous version of the library is no longer available...so I edited the above message...thanks again for your quick support :)

TomJo2000 commented 3 weeks ago

For anyone just coming across this issue now.


This is a known issue caused by the libicu update to 75.1 we're working on getting all packages that depend on it rebuilt, but that does take a while. We apologize for any inconvenience please direct any further questions towards the PSA issue over at the packages repo.