[CFW 3.14] Customised Firmware v3.14 released.

[prpr]

I am concerned by the number of errors

It's not great. I have to say I have never thought to test that path.

I realise it's likely a dependency

Yes, but not of as many things as it should be. But that's not the real problem.

pkill not found? pgrep not found? Do these matter? /mod/bin/pgrep: can't load library 'libproc-3.2.8.so' - why not?

Because the environment set up by the Administration (Telnet) menu doesn't have the path set (for what I would call "correctly").
Having tested it, it probably hasn't broken anything but you should be able to confirm/fix by running this lot:

cat /mod/var/spool/cron/crontabs/root
sed -i "s/opkg upgrade/modenv opkg upgrade/" /mod/boot/2/tmenu
for p in anacron recmon epg sysmon; do opkg remove --force-depends "$p";opkg install "$p";done
cat /mod/var/spool/cron/crontabs/root

and I'll put looking at all that again back on the to-do list.

 

[Owen Smith]

It's not great. I have to say I have never thought to test that path.

I use the telnet menu more often than not to update packages.

Given I still have my parents and my aunt's boxes to do, what method avoids this issue? I can't put them on auto update, my aunt has no broadband for a start and I use my iPad as a hotspot when I update her box.

I'll run the commands you gave this evening probably.

 

[prpr]

what method avoids this issue?

Update the tmenu package first - opkg update; opkg upgrade tmenu from a command prompt.
If you do this first on the box you already tried to upgrade, then you should skip doing the 'sed' line from post #21.

 

[Owen Smith]

And if I do this on a box I haven't upgraded at all will it all be fine now as you've updated tmenu?

 

[Black Hole]

That's the idea. Update tmenu as the preliminary step, then you can run the rest of the update from there.

 

[prpr]

It worked when I tried it, so hopefully yes.