Cannot install luci (global build problem in buildbot today)

After bricking dlink dir-842 with my last attempt, I decided to try with another one.

This time I'm stuck with command opkg install luci. It just says: opkg_install_cmd: Cannot install package luci.
Why so? It downloaded everything and signatures were ok.
I retried opkg update and opkg install luci as someone suggested doing so in a bit old thread. It did not help. So what next? I wish I could finish this before the snapshot expires and things get More awry..

Post the output:

ubus call system board; opkg update; opkg install luci

1 Like

Why are you using a snapshot?

There's no other options available for this device as of I know.

1 Like

You can report the issue on the bug tracker and/or try to build it yourself.

Global build problem (when using SDK like buildbot).

All packages have failed to build in the buildbot...
(faillogs: )

Like this:

fakeroot: preload library `' not found, aborting.
../../ recipe for target '/builder/shared-workdir/build/sdk/bin/packages/arm_cortex-a15_neon-vfpv4/luci/luci_git-20.113.70804-9d02ef1_all.ipk' failed
make[3]: *** [/builder/shared-workdir/build/sdk/bin/packages/arm_cortex-a15_neon-vfpv4/luci/luci_git-20.113.70804-9d02ef1_all.ipk] Error 1
time: package/feeds/luci/luci/compile#0.39#0.14#0.74

Possibly fixed with;a=commit;h=5587f19c362a805636da91d9d550928b4a2998fc

But it will take some time to trickle down to packages building.

Try again in 1-2 days.

1 Like

As I'm not pro in doing this, is it as simple as it was when I try it for a second time?
As the instructions say that I shouldn't power-cycle the unit while doing an installation and I consider this not yet finished, wouldn't I brick the unit or get other big problems if I shut it down and start again?

It should be fine anyways, but you can use the reboot or poweroff command.

This looks like a major catastrophe in buildbot. Pretty much all downlodable packages for master have been removed.

Likely there will be flood of bugs, forum questions etc.

1 Like

So is that estimation of 1-2 days until fixed anywhere close to realistic estimation?

No, sadly after looking it more closely, it looks like building all SDKs will take 1-2 days and packages then 2-4 days.

It is partially random: if your router's kernel & SDK gets rebuilt first, and the next packages build happends right after that, it may take just a few hours. But if your router SDK gets rebuilt last and the packages build just missed that, it can take 2+4 days or so.

1 Like

Ok. Good to know. Thank you all for helpful answers. I'll try again at some time next week.

1 Like

It might be quicker. Maybe just a day or two (as the ath79 SDK has already been rebuilt).

You just need to monitor buildbot:

You just need the next build #337 of "mips_24kc"
(the previous failed one was "Sep 01 05:46 success #336")

Once that next build round completes, you can see the LuCI packages at

1 Like

Now as I'm planning to restart the project with this device, I have just one more question: As this is failed snapshot install (more specifically, luci failed to install because of the global problem), can I continue with just doing sysupgrade and then luci or what is the right starting point to fix the router? Just because I don't want to brick this one.


(You might even try opkg installing luci to your current firmware without sysupgrade. but it may fail if some package has already changed in snapshot. But the plain luci does not use kernel modules, so it might succeed.)

opkg update
opkg install luci

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