Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

Brave RPM repository access denied #10894

Closed
git-ingham opened this issue Sep 11, 2017 · 5 comments · Fixed by #13174
Closed

Brave RPM repository access denied #10894

git-ingham opened this issue Sep 11, 2017 · 5 comments · Fixed by #13174

Comments

@git-ingham
Copy link

  • Did you search for similar issues before submitting this one?
    Yes.

  • Describe the issue you encountered:
    zypper dup on OpenSUSE tumbleweed gives:
    Permission to access 'https://s3-us-west-2.amazonaws.com/brave-rpm-release/x86_64/media.1/media' denied.
    Visiting https://s3-us-west-2.amazonaws.com/brave-rpm-release/ in a browser gives;
    AccessDeniedAccess DeniedF293577D864A2DACnf6K365Yvl7upFFvtwQ8gZpS6CKmLND48OUcf6qqsyR3FTl4LFIyJJ6XA1GMHDGGh2wtSEFgNGM=

  • Platform (Win7, 8, 10? macOS? Linux distro?):
    OpenSUSE tumbleweed

  • Brave Version (revision SHA): Irrelevant since I cannot get it.

  • Steps to reproduce:

    1. Visit the brave RPM repository
    2. See error message.
  • Actual result:
    See above

  • Expected result:
    Getting the latest version of Brave.

  • Will the steps above reproduce in a fresh profile? If not what other info can be added?
    They should work for anybody.

  • Is this an issue in the currently released version?

  • Can this issue be consistently reproduced?
    Yes.

  • Extra QA steps:
    1.
    2.
    3.

  • Screenshot if needed:

  • Any related issues:

@bsclifton
Copy link
Member

cc: @posix4e

@posix4e
Copy link
Contributor

posix4e commented Sep 12, 2017

Can you tell me what commands you ran?

@luixxiul luixxiul added the needs-info Another team member needs information from the PR/issue opener. label Sep 13, 2017
@git-ingham
Copy link
Author

Go to this page:
https://github.com/brave/browser-laptop/blob/master/docs/linuxInstall.md
Look under "OpenSUSE AMD64"
Look at the "sudo zypper addrepo" line
The URL listed gives a "Access Denied" XML reply.

So, what repository should I be using?

@bsclifton bsclifton added this to the Triage Backlog milestone Nov 27, 2017
@tqdv
Copy link
Contributor

tqdv commented Feb 8, 2018

@git-ingham Ok, so I managed to refresh the repository on openSUSE Leap 42.3.
Edit: Nevermind it broke again
Edit^2: Actually, the config somehow changed, and reverted it back to rmp-md. Sorry for the multiple edits.

What happened was that the repository type defaults to rpm-md, while brave's repo is yast2.
There doesn't seem to be a way to modify the repo type using zypper modifyrepo so edit the file directly.
(You can use grep -l brave /etc/zypp/repos.d/*to find it)

This should probably be added to the install instructions if it's correct.

@git-ingham
Copy link
Author

That solves the repository problem. However, I do get:
Problem: nothing provides GConf2 needed by brave-0.20.30-1.x86_64
I think that this is just a naming difference. OpenSUSE Tumbleweed has this as:
gconf2-3.2.6-11.1.x86_64 (version installed on my system)
Brave 0.20.30 installs (and more importantly appears to run OK) if I tell it that breaking the dependency is OK.

tqdv added a commit to tqdv/browser-laptop that referenced this issue Feb 18, 2018
@bsclifton bsclifton modified the milestones: Triage Backlog, 0.23.x (Nightly Channel) Feb 19, 2018
@bsclifton bsclifton added QA/test-plan-specified release-notes/include and removed needs-info Another team member needs information from the PR/issue opener. labels Feb 19, 2018
ryanml pushed a commit to ryanml/browser-laptop that referenced this issue Feb 27, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants