Builds for OpenSUSE Tumbleweed gone?

[fei0316]

Hi, thank you for maintaining this project! I am a OpenSUSE Tumbleweed user and have been using your builds for a few years already. Recently I noticed that Tumbleweed is gone from [https://copr.fedorainfracloud.org/coprs/emixampp/synology-drive/]. Is this related to any difficulties building for Tumbleweed? I would very much want to continue receiving updates from this repo, but I understand if this is not possible/not happening.

[EmixamPP]

Hi @fei0316, indeed builds were failing which then force me to think to retry days/weeks after.
Nonetheless I will retry today!

[EmixamPP]

I added all the x86 distro I could, but Tumbleweed is the only one that is failing. I do not know if this is an issue on COPR side.
Error log: https://download.copr.fedorainfracloud.org/results/emixampp/synology-drive/opensuse-tumbleweed-x86_64/10740483-synology-drive/builder-live.log.gz

It seems the build fails because DNF5 expects a signed repository metadata file repodata/repomd.xml.asc, but the COPR returns 404 for that file. Since metadata GPG verification is enabled, DNF throw an error.

[fei0316]

Hi @EmixamPP , thanks for looking into this! Sorry for the delay, life was busy. I'm also getting the same issue when refreshing the repo, where it complains it doesn't have GPG signature to the repomd.xml file. Is it some configuration on your build pipeline or repo? I don't know too much about COPR unfortunately. I definitely do not remember having to accept an unsigned file.

sudo zypper ref
Refreshing service 'openSUSE'.
Repository 'update-tumbleweed' is up to date.                                                                                                                           
Looking for gpg keys in repository Synology Drive COPR.
  gpgkey=https://download.copr.fedorainfracloud.org/results/emixampp/synology-drive/opensuse-tumbleweed-x86_64/repodata/repomd.xml.key
Warning: File 'repomd.xml' from repository 'Synology Drive COPR' is unsigned.

    Note: Signing data enables the recipient to verify that no modifications occurred after the data
    were signed. Accepting data with no, wrong or unknown signature can lead to a corrupted system
    and in extreme cases even to a system compromise.

    Note: File 'repomd.xml' is the repositories master index file. It ensures the integrity of the
    whole repo.

    Warning: We can't verify that no one meddled with this file, so it might not be trustworthy
    anymore! You should not continue unless you know it's safe.

File 'repomd.xml' from repository 'Synology Drive COPR' is unsigned.
Continue? [yes/no] (no):