Hello all
I just wanted to report the same issue. I’ve noticed, that my FreedomBoxes did not automatically update since 24.18 anymore, so I wanted to do it manually in the cockpit and now face the same problem.
In my case, when trying to manually update in Plinth → System → Upgrades the freedombox package was held back because of your mentioned dependency issue and it was resolved by applying the commands mentioned above. Imho just try them out, worst that can happen is that you’re still stuck at version 24.18.
We have worked on features like DNSSEC and DNS-over-TLS that can improve security and privacy. For this we added systemd-resolved as a dependency. This dependency has caused a conflict with resolvconf package. Unattended-upgrades is refusing to remove this resolveconf package.
Earlier, versions 24.19 and 24.20 did not become available in Debian bookworm-backports because of a minor issue with automatic tests. We fixed that in version 24.20.1 and this version became available in bookworm-backports and so, became available to all our stable distribution users.
We are tracking this issue here Can't upgrade to version 24.20.1 (#2453) · Issues · FreedomBox / FreedomBox · GitLab and hope to fix it soon one way or the other. Meanwhile, the workaround suggested by @Shoxy in this thread is safe to perform and will fix the issue for you. It is also perfectly fine to ignore the upgrade failure (this is just a regular feature release and there are no urgent security that need be fixed). Your machine will directly upgrade to the next version which will be available in a week or two.
Sorry for the mess and thanks for your patience.
Edit: add advice that the issues could be ignored for now.
A fix has been posted for this issue and will likely be available in the next release. Without any intervention, FreedomBox will upgrade to the next version (skipping the versions in between, which is okay).