nut-server: Fix the other/otherflag functionality

[rpavlik]

Signed-off-by: Rylie Pavlik rylie@ryliepavlik.com

📦 Package Details

Maintainer: @s-hamann, @hnyman, @tofurky, @neheb

Description:
There is an unclear reference to handling unknown config fields for driver config files in the wiki. This adjusts the service script so that they actually work.

• For each value "x" in the per-driver list "other", get the per-driver config variable "other_x", and if it is not empty, write "x = {value of other_x}" to the config file.
• For each value "x" in the per-driver list "otherflag", get the per-driver config variable "otherflag_x", and if it is true, write "x " to the config file.

I think this should be safe to backport, if desired. I tested it on a stable release device.

---

🧪 Run Testing Details

• OpenWrt Version: 24.10.5
• OpenWrt Target/Subtarget: mediatek/filogic
• OpenWrt Device: OpenWrt One

---

✅ Formalities

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

[rpavlik]

Not sure if the second commit is the right way to document that or if there's a better way that's less likely to become desynced.

I backported these commits along with all the others touching this package from master to 24.10 and rebuilt, and the resulting nut packages work well, I don't know the process or policy for backporting changes, but I would recommend it. See https://github.com/rpavlik/openwrt-packages-fork/tree/nut-backport