Whyever my package manager didn't surviced the last upgrade. Any chance for an manual reinstall or do I have to wait for the next snapshot?
Thx a lot,
meg
The package luci-app-opkg was renamed to luci-app-package-manager and now opkg is not a dependency anymore.
If you have owut installed, just execute:
owut upgrade --add luci-app-package-manager,opkg
Or use the Firmware Selector and create a custom build with your packages and make sure those 2 are included.
Cheers!
EDIT: there must not be any whitespaces on the list of packages.
5 Likes
owut upgrade --add luci-app-package-manager, opkg
owut - OpenWrt Upgrade Tool 2024.10.25~8c8907c6-r1 (/usr/bin/owut)
ERROR: 'opkg' is not a valid command or option
ah, whitespace xD
that was my first idea, at least adding opkg ...
1 Like
Sorry, remove the space between luci-app-manager,opkg. My apologies.
1 Like
Thx a lot for the fast response and the quick fix/solution 
1 Like
What the heck? Why would they do that? Is there any way to get luci, or any other package on there once you upgrade to this image with no opkg???
This makes no sense to me
Is there a commit/PR that I can look at to understand this better?
I believe that Opkg manager may have been replaced with the Alpine package manager. It seems to be what the latest OpenWrt snapshot is using now in the Software menu item.
Once I noticed that I needed to do "apk add" instead of "opkg install" I seemed good to go.
1 Like
it seems there's no way to install luci using apk right now
1 Like
Got it. Thank you!
apk add luci worked for me
Yeah, worked for me too in the end. On a different snapshot though. Maybe it was a snapshot issue.
The package in the repository for the current snapshot is missing for APK, "by default". Got used to not having to explicitly install a package manager. When they removed opkg from the builder / repository snapshots were being built with no package manager at all. Alpine documentation says the package is named apk-tools but for OpenWRT its actually just APK.
opkg was a built in package never having to be explicitly calling in the bot builder which lead me on a two day hunt on if anyone knew a way to pull an external APK from a link and load it. In the end I just made a new snapshot with APK and the firmware for my dual rtl8520 on a RP5.
A fix for this bug has been implemented by devs.
1 Like
for me it more feels like this bugfix killed the whole build process 
OPKG does not exist anymore in the repository for snapshot. You can't call it from the bot either. At this point consider anything made from a SNAPSHOT to no longer use OPKG. When making new snapshots replace OPKG with APK. That will give you the package allowing the use of Alpine Tools in the CLI.
I saw you opened an issue but its because you are still trying to use OPKG. Looking online they talked about and warned everyone this was coming. The only issue I still see is that Alpine Tools says the package name is apk-tools when in fact its actually just APK.
That said the change is quite simple as Alpine documentation is simple to read and understand where I got hung up is not realizing its not baked into the base. This was corrected by finding the appropriate package and then calling it in the builder bot. If it were me I would put a note on the builder bot page notifying users the OPKG is retired going forward and APK has to be intently called at build time for inclusion.
APK also works great from the luci interface as well.
^^ after managing the upgrade without Opkg, packages and sysupgrade is broken ... maybe not all decencies are still solved/fixed/migrated
I have not yet encountered anything that doesn't work on APK that worked on OPKG but I dont know and use everything.
When you build an image you have to manually call to the APK package so that the CLI commands can be used, it is not yet baked into the core like OPKG.
The main file for CLI is "apk-mbedtls" As long as I have that the Luci interface and the SSH interface both allow use of the apk package manager as a replacement for OPKG.
atm it seems like after the last sysupdate, which switched from opkg to apk there is neither Opkg nor apk. So remote repair would be somehow more complicated.
I cant help with the remote repair but what I can tell you is if you didnt put "apk-mbedtls" into your image there is no easy way to get the package put in remotely.
I suggest if you have it, revert to an older backup before this issue and build a new upgrade image with the above mention package. I too fought with how to load this package after the fact but I didn't find an easy way. Hence, just built a new image and made sure that I had all the proper base packages.