![]() Repository 'Update Repository (Non-Oss)' is up to date. Skipping repository 'Visual Studio Code' because of the above error. Repository 'Visual Studio Code' is invalid. Retrieving repository 'Visual Studio Code' metadata. So it seems like refreshing via zypper is broken, but with yast it works. Sorry, what I mean is I would get the error using zypper ref, then open yast software manager and it would report success refreshing the repos, and immediately afterwards I tried zypper ref again and it worked without error (probably because as it says, it didn’t need to check again). I do not quite get your story about the fact that it seems to work sometimes. +-+-+-+-+-+-ġ | PlexRepo | PlexRepo | No | - | - | Ģ | code | Visual Studio Code | Yes | (r ) Yes | Yes | ģ | packman | packman | No | - | - | Ĥ | repo-debug | Debug Repository | No | - | - | ĥ | repo-debug-non-oss | Debug Repository (Non-OSS) | No | - | - | Ħ | repo-debug-update | Update Repository (Debug) | No | - | - | ħ | repo-debug-update-non-oss | Update Repository (Debug, Non-OSS) | No | - | - | Ĩ | repo-non-oss | Non-OSS Repository | Yes | (r ) Yes | Yes | ĩ | repo-oss | Main Repository | Yes | (r ) Yes | Yes | ġ0 | repo-source | Source Repository | No | - | - | ġ1 | repo-source-non-oss | Source Repository (Non-OSS) | No | - | - | ġ2 | repo-update | Main Update Repository | Yes | (r ) Yes | Yes | ġ3 | repo-update-non-oss | Update Repository (Non-Oss) | Yes | (r ) Yes | Yes | ġ4 | snappy | snappy | Yes | (r ) Yes | Yes | # | Alias | Name | Enabled | GPG Check | Refresh | URI All enabled repositories share the same priority. Repository priorities are without effect. The truly odd thing for me is that the repos appear to refresh successfully if I use yast, and then zypper ref will work for a little while (as long as it says ‘already up to date’). I was afraid touching the repo settings might cause issues… I tried disabling packman to troubleshoot the issue. The only thing I can think of that changed regarding repos recently was that I added packman. I hoped it would fix itself if I waited, but it persists after a week+. Googling these errors hasn’t brought me to anything helpful and I am unsure how to proceed. This is a relatively recent install of Leap 15.2 so I could evaluate openSUSE. Some of the repositories have not been refreshed because of an error. Skipping repository 'Update Repository (Non-Oss)' because of the above error. Repository 'Update Repository (Non-Oss)' is invalid. Retrieving repository 'Update Repository (Non-Oss)' metadata. ![]() Skipping repository 'Main Update Repository' because of the above error. Please check if the URIs defined for this repository are pointing to a valid repository. libgpgme error in 'gpgme_ctx_set_engine_info': Invalid crypto engine Valid metadata not found at specified URL Repository 'Main Update Repository' is invalid. Retrieving repository 'Main Update Repository' metadata. Repository 'Main Repository' is up to date. Repository 'Non-OSS Repository' is up to date. Repository 'Visual Studio Code' is up to date.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |