[SOLVED] OPKG - Upgrading of packages reports errors

Team,

When doing some updates from the repositories lately, I'm noticing this error messages:

Configuring luci-theme-material.
uci: Parse error (too many arguments) at line 18, byte 132
uci: Parse error (too many arguments) at line 21, byte 128
Configuring luci-app-statistics.
uci: Parse error (too many arguments) at line 18, byte 132
uci: Parse error (too many arguments) at line 21, byte 128
Configuring luci-app-adblock.
uci: Parse error (too many arguments) at line 18, byte 132
uci: Parse error (too many arguments) at line 21, byte 128
Configuring luci-theme-bootstrap.
uci: Parse error (too many arguments) at line 18, byte 132
uci: Parse error (too many arguments) at line 21, byte 128
Configuring luci-mod-admin-full.
uci: Parse error (too many arguments) at line 18, byte 132
uci: Parse error (too many arguments) at line 21, byte 128
Configuring luci-app-upnp.
uci: Parse error (too many arguments) at line 18, byte 132
uci: Parse error (too many arguments) at line 21, byte 128
Configuring luci-app-transmission.
uci: Parse error (too many arguments) at line 18, byte 132
uci: Parse error (too many arguments) at line 21, byte 128

BTW: I'm using the darkmatter them from this repo: src/gz reboot_darkmatter https://davidc502sis.dynamic-dns.net/snapshots/r4114/packages/arm_cortex-a9_vfpv3/darkmatter

Any clues of why this may be happening? Maybe an incompatibility with darkmatter?

Hey, anyone? :slight_smile:

There is a typo in one of your "/etc/config" files, and "uci" is complaining because it is called during the installation of new packages; execute "uci changes" to find the typo and fix it.

@eduperez thanks for the hint! I've did a uci changes, and it is just telling me this:

root@RouterACS:/etc# uci changes
uci: Parse error (too many arguments) at line 21, byte 128

How do I find which file is the offending one?

Paste following command into your terminal:

for x in /etc/config/*; do uci -q show "${x#/etc/config/}" >/dev/null || echo "$x is broken"; done

@jow Thanks for the script! I found the offending file, deleted it and now everything is working fine! Thanks again.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.