Hi. I trying to update the packages for weeks, but I can't because termux found a conflict with the package libandroid-support::arch64.
Steps to reproduce
Just do pkg update or pkg upgrade.
Expected behavior
Packages are updated to last version.
Additional information
5 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done Building dependency tree
Reading state information... Done Calculating upgrade... Done
The following NEW packages will be installed: bzip2 coreutils curl diffutils dos2unix ed findutils
gawk grep gzip inetutils less libandroid-glob libcrypt libgmp libiconv libmpfr net-tools patch
pcre procps psmisc sed tar termux-licenses unzip
util-linux xz-utils The following packages will be upgraded:
apt bash busybox ca-certificates command-not-found
dash dpkg gpgv libandroid-support libbz2 libc++
libcurl libgcrypt libgpg-error liblzma libnghttp2
ncurses neofetch openssl readline termux-am
termux-exec termux-tools tracepath zlib
25 upgraded, 28 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/11.8 MB of archives.
After this operation, 32.9 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
E: This installation run will require temporarily removing the essential package libandroid-support:aarch64 due to a Conflicts/Pre-Depends loop. This is often bad, but if you really want to do it, activate the APT::Force-LoopBreak option.
E: Internal Error, Could not early remove libandroid-support:aarch64 (2)
Updatable packages:
apt/stable 1.4.9-16 aarch64 [upgradable from: 1.4.9-4] bash/stable 5.0.11 aarch64 [upgradable from: 5.0.7]
busybox/stable 1.30.1-9 aarch64 [upgradable from: 1.30.1-1]
ca-certificates/stable 20190828 all [upgradable from: 20190124]
command-not-found/stable 1.42 aarch64 [upgradable from: 1.37]
dash/stable 0.5.10.2-2 aarch64 [upgradable from: 0.5.10.2-1]
dpkg/stable 1.19.7-9 aarch64 [upgradable from: 1.19.4-1]gpgv/stable 2.2.17 aarch64 [upgradable from: 2.2.15-1]
libandroid-support/stable 25-2 aarch64 [upgradable from: 24] libbz2/stable 1.0.8-5 aarch64 [upgradable from: 1.0.6-2]
libc++/stable 20 aarch64 [upgradable from: 19b]
libcurl/stable 7.66.0-1 aarch64 [upgradable from: 7.64.1-1]
libgcrypt/stable 1.8.5 aarch64 [upgradable from: 1.8.4]
libgpg-error/stable 1.36-1 aarch64 [upgradable from: 1.36] liblzma/stable 5.2.4-7 aarch64 [upgradable from: 5.2.4]
libnghttp2/stable 1.39.2 aarch64 [upgradable from: 1.38.0] ncurses/stable 6.1.20190928 aarch64 [upgradable from: 6.1.20181117-1]
neofetch/stable 6.1.0 all [upgradable from: 6.0.0] openssl/stable 1.1.1d-1 aarch64 [upgradable from: 1.1.1b-2] readline/stable 8.0.1 aarch64 [upgradable from: 8.0] termux-am/stable 0.3 all [upgradable from: 0.2]
termux-exec/stable 0.4-1 aarch64 [upgradable from: 0.4] termux-tools/stable 0.72 all [upgradable from: 0.65]
tracepath/stable 20190709 aarch64 [upgradable from: 20190515]
zlib/stable 1.2.11-4 aarch64 [upgradable from: 1.2.11-3]
Subscribed repositories:
https://dl.bintray.com/grimler/science-packages-24 science/stable
https://dl.bintray.com/grimler/game-packages-24 games/stable
https://dl.bintray.com/termux/termux-packages-24 stable/main
System information:
Linux localhost 4.9.112-16702606 #2 SMP PREEMPT Thu Sep 5 23:54:59 KST 2019 aarch64 Android
Termux-packages arch:
aarch64
Android version:
9
Device manufacturer:
samsung
Device model:
SM-G9650
@bkdwt I managed to remove those conflict package manually first, then we had to set FAILSAFE SHELL PATH by export PATH=/sbin/:/vendor/bin:/system/sbin:/system/bin:/system/xbin:$PATH to make shell commands keep working on pkg upgrade ...
Hi, it seems that we unfortunately have made changes between last time you upgraded and now that causes these problems.
Easiest fix would be to run rm -rf $PREFIXand then restart the app, this will leave all files in $HOME intact but remove all installed packages. When you restart the app it will download the bootstraps with core packages again and give you a fresh installation, except that everything you have in $HOME is saved
Hi, it seems that we have unfortunately have made changes between last time you upgraded and now that causes these problems.
Easiest fix would be to run
rm -rf $PREFIXand then restart the app, this will leave all files in $HOME intact but remove all installed packages. When you restart the app it will download the bootstraps with core packages again and give you a fresh installation, except that everything you have in $HOME is saved
Thank you very much! rm -rf $PREFIX has solved this problem. :+1:
Most helpful comment
Hi, it seems that we unfortunately have made changes between last time you upgraded and now that causes these problems.
Easiest fix would be to run
rm -rf $PREFIXand then restart the app, this will leave all files in $HOME intact but remove all installed packages. When you restart the app it will download the bootstraps with core packages again and give you a fresh installation, except that everything you have in $HOME is saved