base16384: update to version 2.3.2

[BKPepe]

📦 Package Details

Maintainer: @fumiama
_{(You can find this by checking the history of the package Makefile.)}

Description:
Release notes:
https://github.com/fumiama/base16384/releases/tag/v2.3.2

---

✅ Formalities

• I have reviewed the CONTRIBUTING.md file for detailed contributing guidelines.

If your PR contains a patch:

• It can be applied using git am
• It has been refreshed to avoid offsets, fuzzes, etc., using

  make package/<your-package>/refresh V=s

• It is structured in a way that it is potentially upstreamable
  _{(e.g., subject line, commit description, etc.)
  We must try to upstream patches to reduce maintenance burden.}

[BKPepe]

The failing test is really interesting.

Use package specific test.sh
/ci/utils/base16384/test.sh: line 5: opkg: not found
/ci/utils/base16384/test.sh: line 8: base64: not found

[fumiama]

Wow, it is quite weird because only version is changed. In the new version, I only changed CMakeLists.txt, so maybe some changes in this repo caused this problem.

[wehagy]

The test.sh script is using opkg, but now we are using apk in the snapshot and probably in the next stable release. It's strange that the test is successful anyway, maybe it's because of the exit 0?

packages/utils/base16384/test.sh

Line 16 in fde2ee4

exit 0

I have this migration on my radar, as some documentation and scripts are using opkg only.

[BKPepe]

Related to #27607