Common workaround is to drop those metapackages and explicitly add only the required packages one by one.
This process quite often seems to break https - mine, too.
Here some older pointers:
As of 2023.5.05, with mbedtls as encryption standard, I found this list to work for e.g. for an access point:
tls-configuration appears to be a moving target.
Thus, a metapackage keeping encryption in sync, but without pulling unnecessary stuff, would be desirable.
I'll have a look at issue list.
(To keep threads tidy, I separate this (underlying) issue from another thread, covering the way to solution.)
Based on what? And given the issue is caused by users using devices with insufficient storage space I'm not sure the solution is to create additional meta-packages.
Using openwrt on 8mb devices is going to continue being difficult (and reach a point where it's realistically not possible) as new versions get released. In the meantime you'd probably be better off learning to use the full build system which will give you much more flexibility to fine-tune a build.
Can you please stop starting new topics about essentially (minor variations of) the same issue?
Basically everything has already been said, by almost everybody - the facts won't change.
Either you can make it fit (your full set of requirements is …ambitious) - or you can't, the challenge is yours.
You pay either way, either with your time - or your money for more capable devices. Just don't try to make others pay for you and with their time (anymore). Please stick to one thread, if there's really anything else to say about this.