Same issue here as well. When I checked the key of danielbermond@gmail.com it showed:
sudo pacman-key -l dbermond@archlinux.org
pub rsa2048 2016-06-27 [SC]
3FFA6AB7B69AAE6CCA263DDE019A7474297D8577
uid [vollständig] Daniel Bermond <danielbermond@gmail.com>
uid [vollständig] Daniel Bermond <dbermond@archlinux.org>
sub rsa2048 2016-06-27 [E]
pub ed25519 2021-10-30 [SC] [verfällt: 2026-10-29]
80247D99EABD3A4D1E3A1836E85B8683EB48BC95
uid [ marginal ] Daniel Bermond <dbermond@archlinux.org>
sub cv25519 2021-10-30 [E] [verfällt: 2026-10-29]
My solution was to trust the second key (the one with marginal trust) locally:
sudo pacman-key --lsign-key 80247D99EABD3A4D1E3A1836E85B8683EB48BC95
After that it is shown as trusted:
sudo pacman-key -l dbermond@archlinux.org
pub rsa2048 2016-06-27 [SC]
3FFA6AB7B69AAE6CCA263DDE019A7474297D8577
uid [vollständig] Daniel Bermond <danielbermond@gmail.com>
uid [vollständig] Daniel Bermond <dbermond@archlinux.org>
sub rsa2048 2016-06-27 [E]
pub ed25519 2021-10-30 [SC] [verfällt: 2026-10-29]
80247D99EABD3A4D1E3A1836E85B8683EB48BC95
uid [vollständig] Daniel Bermond <dbermond@archlinux.org>
sub cv25519 2021-10-30 [E] [verfällt: 2026-10-29]
Now the update executed as expected.