Software tab missing

Installing and Using OpenWrt
1

HI,

do you know why in my LuCi the ''software'' tab is missing?

2

let's start with information about your device and your current version

What's the output of this:

ubus call system board
1 Like
3

you will tell me ;

you have the snapshot master :wink:

"kernel": "5.15.91",
        "hostname": "OpenWrt",
        "system": "ARMv7 Processor rev 0 (v7l)",
        "model": "Netgear Nighthawk X4S R7800",
        "board_name": "netgear,r7800",
        "rootfs_type": "squashfs",
        "release": {
                "distribution": "OpenWrt",
                "version": "SNAPSHOT",
                "revision": "r21981-8bc72ea7be",
                "target": "ipq806x/generic",
                "description": "OpenWrt SNAPSHOT r21981-8bc72ea7be"
4

Yup... do you actually need to run snapshot?
If not, run stable and everything should be there:
https://firmware-selector.openwrt.org/?version=22.03.3&target=ipq806x%2Fgeneric&id=netgear_r7800

2 Likes
5

Simply do opkg update and opkg install luci-app-opkg
Seems that the package luci-app-opkg is no longer installed by default in master.

4 Likes
6

In what context are you talking about?
It is most certainly installed on the most recent stable release (and has been for every stable release build I can remember) -- currently looking at 22.03.3.

Snapshot builds do not include LuCI, so the user must install it if desired... it may be true that luci-app-opkg needs to be explicitly installed in that context.

1 Like
7

I talk about the snapshot master as it is seen from the @Peacefuleight post.

1 Like
8

But LuCI isn't preinstalled anyway, so it follows that luci-app-opkg is also not installed by default.

9

He talks about "software" tab missing in his LuCI and that means he selected it anyway.
I've compiled a recent master build with LuCI and luci-app-opkg was missing in my build too. I haven't explicitly opted for it.
I don't talk about snapshot builds.

10

were all the usual subcomponents (i.e. luci-app-*) selected? Is the issue that the subcomponent is deselected by default? or that it is missing entirely from the list? Or that it was selected by didn't actualy get included in the final build?

11

I've simply used my usual diffconfig file where I haven't explicitly added luci-app-opkg but I had other lines.

CONFIG_PACKAGE_luci-ssl-openssl=y
CONFIG_PACKAGE_luci-app-commands=y
CONFIG_PACKAGE_luci-app-adblock=y
CONFIG_PACKAGE_luci-app-https-dns-proxy=y
CONFIG_PACKAGE_luci-theme-openwrt-2020=y
CONFIG_PACKAGE_luci-app-sqm=y
CONFIG_PACKAGE_luci-proto-wireguard=y
CONFIG_PACKAGE_kmod-wireguard=y
CONFIG_PACKAGE_wireguard-tools=y
CONFIG_PACKAGE_openssl-util=y

Till recently luci-app-opkg was always added in the final build but last time I compiled it was missing. I simply added it to my diffconfig.

1 Like
12

For the record, here's the commit that f**ked everything up.

commit 34dee82f29af74d6dee0616cc52a7b9e4f51d9f6
Author: Andre Heider <a.heider@gmail.com>
Date:   Mon Oct 24 14:57:47 2022 +0200

    luci-light: rework and reenable
    
    The `luci` collection contains package management and attended
    sysupgrades support, which are not that useful if not even undesired for
    self-compiled images.
    
    Rework the `luci-light` collection to exclude the two above mentioned
    features, and make `luci` instead depend on the light collection in
    additon to those features.
    
    The `luci-ssl` and `luci-ssl-openssl` collections then only need
    to depend on `luci-light`.
    
    We now have three variants with won't pull in `luci-app-opkg` or
    `luci-app-attendedsysupgrade`, making everybody happy.
    
    Signed-off-by: Andre Heider <a.heider@gmail.com>

I publish a custom build and was alerted by a user that luci-app-opkg was no longer in the build. This was unexpected. It seems like this was a default behavior change between 22.03 and 23.05.