This was long lost (60 days) as it came in via an auto sync so nobody kept track.
Thanks to a new report it is now on our radar (and future issues will be picked up sooner).
For this case we have a few options:
1. fix the issue in the code, but realize it is not a new issue just an old one exposed by a new warning
2. disable this particular new compiler warning for now and expect that upstream will have improved e.g. until next release
3. try to build the older version and do a +really upload to revert to that for now.
I'll do some checks to decide between those three and then report back here.
This was long lost (60 days) as it came in via an auto sync so nobody kept track.
Thanks to a new report it is now on our radar (and future issues will be picked up sooner).
For this case we have a few options:
1. fix the issue in the code, but realize it is not a new issue just an old one exposed by a new warning
2. disable this particular new compiler warning for now and expect that upstream will have improved e.g. until next release
3. try to build the older version and do a +really upload to revert to that for now.
I'll do some checks to decide between those three and then report back here.