1
20.7 Legacy Series / Re: Unbound service routinely stopping/crashing following 20.7.7 update
« on: December 20, 2020, 11:40:32 am »
I think @Animosity022 meant stop offering the broken unbound 1.13.0 package in System > Firmware > Updates, or releasing 20.7.7_2 with unbound pinned at 1.12.0, or withdrawing 20.7.7_1 altogether (I get there are security issues resolved in this release so that might not be the best option).
Is it possible to at least add a note in the release notes warning people about this issue if they are using unbound in their configuration? So they can then make a more informed decision about whether to upgrade or not.
My backup firewall hasn't been upgraded yet, and 20.7.7_1 with unbound 1.13.0 is still being offered when I check for upgrades. So even if I read the release notes carefully, if I hit upgrade on that firewall, it would be guaranteed to break until unbound is manually reverted (after figuring out unbound had crashed and then finding this thread).
Is it possible to at least add a note in the release notes warning people about this issue if they are using unbound in their configuration? So they can then make a more informed decision about whether to upgrade or not.
My backup firewall hasn't been upgraded yet, and 20.7.7_1 with unbound 1.13.0 is still being offered when I check for upgrades. So even if I read the release notes carefully, if I hit upgrade on that firewall, it would be guaranteed to break until unbound is manually reverted (after figuring out unbound had crashed and then finding this thread).