Zyxel Forum - Herzlich Willkommen!

The reason is in the logfile:

admin@NAS520:/i-data/38aa86ff/.PKG/Entware-ng/opt/var/log$ cat Entware-ng.log
Opened logfile at Mon Aug 17 20:06:42 CEST 2026
Flushing memory buffer
Starting up
Flushing done
[20:06:42] Create symlink /opt -> /i-data/38aa86ff/.PKG/Entware-ng/opt
[20:06:42] Execute ...

In the package Tweaks the startscript contains this snippet:

[ -f /firmware/mnt/info/modelid ] && TWEAKS_MODEL=$( cat /firmware/mnt/info/modelid )
[ -f /zyxel/mnt/info/modelid ] && TWEAKS_MODEL=$( cat /zyxel/mnt/info/modelid )

The first line is for fw5 devices, and the 2nd one is for fw4, when ...

I added your repo to MetaRepository, and after a refrash it detected an upgrade for mc, which installed without troubles.

BTW, the `520 is an fw5 device.

Can you please provide me your script for further analysis to find out the concrete procedure to create zpkg files?

GenerateZypkgFramework.zip
It is desgined to be run in a subdirectory containing subdirectories data and control, and generates startscript, ZYPKG, control, ....

generate ...

It works for me on my NAS520:

admin@NAS520:/tmp/test$ wget http://zyxel.ddnss.eu/Users/Mijzelf/zypkg-repo/test/shv/fw5/MidnightCommander_4.6.1_arm_003.zpkg
Connecting to zyxel.ddnss.eu (130.61.246.67:80)
MidnightCommander_4. 100 ...

The PKG_DOWNLOAD_URL isn't replaced because the file /tmp/.MetaRepository/tmp/lasturl doesn't exist.

It does. MetaRepository puts it there, when downloading a package. But of course that doesn't survive a reboot. In most cases the file is there, but when the firmware package manager gets the ...

How are you trying to install it?

There is nothing special in zpkg files. I used a script to create them, but that was including generating a startscript and pre- and post install scripts. One thing that can go wrong these days is tar. The latest Plex packages cannot be installed anymore, because ...

That is actually a bug in the startscript. The startscript (${PKG_ROOT}/etc/init.d/MidnightCommand) contains this snippet:

Startup()
{
# Enable ld-linux.so on NAS5xx
[ ! -f /lib/ld-linux.so.3 -a -f /lib/ld-linux-armhf.so.3 ] && ln -s ld-linux-armhf.so.3 /lib/ld-linux.so.3

for file in /bin/mc ...

For completion:

The above leads indeed to a SSLeay.so like below:

ldd /i-data/70be7240/root/.cpan/build/Net-SSLeay-1.88-0/blib/arch/auto/Net/SSLeay/SSLeay.so
libssl.so.1.0.0 => not found
libcrypto.so.1.0.0 => not found
libz.so.1 => /opt/lib/libz.so.1 (0x2abc6000)
libgcc_s.so.1 => /opt/lib ...

I think the compiler/linker by default doesn't address the /opt prefix. If you run
ldd /i-data/70be7240/root/.cpan/build/Net-SSLeay-1.88-10/blib/arch/auto/Net/SSLeay/SSLeay.so it will show you a 'not found' for libssl.so.1.0.0, because is searches in /lib and /usr/lib.
That seems strange, as at ...