Bug ID 1200324
Summary Build service creates broken meta files in repositories
Classification openSUSE
Product openSUSE.org
Version unspecified
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component BuildService
Assignee screening-team-bugs@suse.de
Reporter sndirsch@suse.com
QA Contact adrian.schroeter@suse.com
Found By ---
Blocker ---

Just noticed that the Build Service apparently creates broken meta files in
repositories.

https://build.opensuse.org/project/show/X11:Drivers:Video

# sudo zypper addrepo
https://download.opensuse.org/repositories/X11:/Drivers:/Video/SLE_15_SP4/
X11:Drivers:Video2
Adding repository 'X11:Drivers:Video2'
...................................[done]
Repository 'X11:Drivers:Video2' successfully added

URI         :
https://download.opensuse.org/repositories/X11:/Drivers:/Video/SLE_15_SP4/
Enabled     : Yes
GPG Check   : Yes
Autorefresh : No
Priority    : 99 (default priority)

Repository priorities in effect:                (See 'zypper lr -P' for
details)
      80 (raised priority)  :  2 repositories
      90 (raised priority)  :  2 repositories
      99 (default priority) : 12 repositories
     100 (lowered priority) :  9 repositories

# sudo zypper ref X11:Drivers:Video
[...]
New repository or package signing key received:

  Repository:       X11:Drivers:Video
  Key Fingerprint:  C574 FD10 5C13 81E5 53E5 A73E 5904 01A1 E38F B563
  Key Name:         X11:Drivers:Video OBS Project
<X11:Drivers:Video@build.opensuse.org>
  Key Algorithm:    RSA 2048
  Key Created:      Fri 13 May 2022 05:21:38 PM UTC
  Key Expires:      Sun 21 Jul 2024 05:21:38 PM UTC
  Rpm Name:         gpg-pubkey-e38fb563-627e93a2



    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: A GPG pubkey is clearly identified by it's fingerprint. Do not rely
the keys name. If you
    are not sure whether the presented key is authentic, ask the repository
provider or check his
    web site. Many provider maintain a web page showing the fingerprints of the
GPG keys they are
    using.

Do you want to reject the key, trust temporarily, or trust always? [r/t/a/?]
(r): t
Retrieving repository 'X11:Drivers:Video' metadata
..............................................................................................................[error]
Repository 'X11:Drivers:Video' is invalid.
[X11:Drivers:Video|https://download.opensuse.org/repositories/X11:/Drivers:/Video/SLE_15_SP4/]
Valid metadata not found at specified URL
History:
 - File
'./repodata/3cfe905631eef842d7d8a2e7f64a687db42f7aa2bc15807330ed76e0badb38e2-primary.xml.gz'
not found on medium
'https://download.opensuse.org/repositories/X11:/Drivers:/Video/SLE_15_SP4/'
 - Can't provide
./repodata/3cfe905631eef842d7d8a2e7f64a687db42f7aa2bc15807330ed76e0badb38e2-primary.xml.gz

Please check if the URIs defined for this repository are pointing to a valid
repository.
Skipping repository 'X11:Drivers:Video' because of the above error.
Some of the repositories have not been refreshed because of an error.


You are receiving this mail because: