Updates are broken on OpenSUSE
See original GitHub issueDescription
While installation on OpenSUSE 15 works fine following our official instructions, updates do not work.
Steps to Reproduce
- Install OpenSUSE 15 in a VM.
- Follow the installation instructions
- Update the repository using
zypper ref
.
Actual result:
# zypper ref
Problem retrieving files from 'brave-browser'.
Permission to access 'https://brave-browser-rpm-release.s3.brave.com/x86_64/media.1/media' denied.
Please see the above error message for a hint.
Skipping repository 'brave-browser' because of the above error.
Repository 'google-chrome' is up to date.
...
Some of the repositories have not been refreshed because of an error.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Problems installing Online Updates | Support - SUSE
A Problem Temporary Fix (PTF) for a bug report has been installed on the system. ... Use YaST Online Update to install the...
Read more >updates not working - Applications - openSUSE Forums
A few months ago I updated to Leap 15.4. Since then I never had any updates which seems strange to me. There aro...
Read more >OpenSUSE Tumbleweed Broken after update! - Reddit
Ok, I updated OpenSUSE recently, and every time that I start up the thing, it's always send me into the text/console mode. I...
Read more >OpenSUSE Tumbleweed users beware: possible broken boot ...
Hey guys, Just putting this out there! You may want to cautiously apply updates or you may find an unbootable computer:
Read more >transactional-update/NEWS at master · openSUSE ... - GitHub
Fix broken logrotate due to typo in config file. [gh#openSUSE/transactional-update#87]. * create_dirs_from_rpmdb: Fix handling return code of create_dirs().
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Updates are now working on all channels, though there is still an “unsigned repo” warning that needs to be ignored (#3982).
While working on a different RPM problem (#3982), we discovered that the lack of signature on
repomd.xml
is also the root cause for thiszypper ref
failure, despite the unhelpful error messages I pasted above.A fix is being worked on in https://github.com/brave/brave-core/pull/3877.