Re: gnutls error on Emacs for Android armeabi 7a

[Po Lu]

Lockywolf <for_help-gnu-emacs_at_gnu_org_2023-11-30@lockywolf.net>
writes:

> Disregard all of the above, I have re-installed the most recent Emacs,
> and now everything works, both gnutls and libxml2.
>
> On the other hand, may I ask the builds for termux-16 be restored?
>
> The "new" termux 0.119 has reinstated support for Android 5 and 6, and I
> would greatly enjoy having access to termux from Emacs. (I guess, I can
> re-pack it manually though.)

I think you're a victim of misinformation, since the Termux repository
states in no uncertain terms:

  Latest version is v0.118.0.

  NOTICE: It is highly recommended that you update to v0.118.0 or higher
  ASAP for various bug fixes, including a critical world-readable
  vulnerability reported here.  Also reminding again to users who have
  installed termux apps from google playstore that playstore builds are
  deprecated and no longer supported.  It is recommended that you shift to
  F-Droid or GitHub releases.

  Termux can be obtained through various sources listed below for only
  Android >= 7 with full support for apps and packages.

  Support for both app and packages was dropped for Android 5 and 6 on
  2020-01-01 at v0.83, however it was re-added just for the app without
  any support for package updates on 2022-05-24 via the GitHub sources.
  Check here for the details.

and a search revealed also this issue/discussion:

  https://github.com/termux/termux-app/discussions/3812

in which there are several strong words of caution from its maintainers
against packages purporting to be 0.119.  Since packaging support for
Android 5 and 6 remains inactive, and the limited support they do
provide was not functional when last I tried, I don't plan to continue
providing builds for such configurations until it is demonstrated that
they are in fact practical.  Recall that the recently superseded Termux
builds labeled "16" enforced a minimum API level of 24 in any case,
which state of affairs continued for a considerable period without any
reports from users of having been inconvenienced.

> Or, maybe there is some other way of supporting zip/unzip on stupid
> Android systems, which only have a busybox of unzip, but no zip at all.

If it's only nov.el that you need,

  (setq nov-unzip-args '("-o" filename "-d" directory))

the built-in arc-mode should detect busybox or Android unzip and adjust
its command line unassisted, but if not, please report the failure as a
bug.