Owncloud-client Debian_10 repo for building/installing from OBS repo has expired gpg key

[dbanders]

Trying to building owncloud-client for install for Raspberry Pi OS 64 bit using Debian_10 following

Appendix Building the Client

apt update

W: GPG error: Debian_10 InRelease: The following signatures were invalid: EXPKEYSIG 4ABE1AC7557BEFF9 isv:ownCloud OBS Project isv:ownCloud@build.opensuse.org

N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

[jnweiger]

@dbanders

4ABE1AC7557BEFF9

Ouch, thanks for the report!
That key should have an expiry date of 2024-03-23
That is what public keyservers have. You can get a current copy of the GPG key with e.g.

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 4ABE1AC7557BEFF9
gpg --recv-keys --keyserver keyserver.ubuntu.com 4ABE1AC7557BEFF9

Regarding the OBS repo that is mentioned in this appendix:
It was last used for client 2.6.3 – and probably should have been removed long time ago. (Repo’s at OBS forget to refresh their GPG keys, when they don’t do rebuilds regularly, this is what now happened)

We have an update branch for the docs, but but no decision where and how to document client build instructions when that repo is gone. The instructions that we have compiled so far only work for reproducing exactly what we already have. It won’t currently help for Raspberry.

For the current draft see https://github.com/owncloud/docs-client-desktop/blob/fix_update_building_page/modules/ROOT/pages/appendices/building.adoc

[jnweiger]

It’d be much cleaner, if you could build using Index of /repositories/isv:/ownCloud:/Qt5152/Debian_10 or one of the other Qt5XXX repos. They are used by us too, but they don’t contain any client sources.

I cannot tell, how the build should work in that case.