-
Notifications
You must be signed in to change notification settings - Fork 859
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make stable brave-browser depend on brave-keyring #2338
Conversation
I inspected the .deb and .rpm manually and they both included the correct metadata. I tried installing the generated release package on Fedora and it correctly pulled in the dependency:
I tried installing the generated .deb and it correctly failed due to a missing dependency:
Then I rebuilt the packages on the beta channel this time:
I was able to install both beta packages without brave-keyring:
and hand-inspection showed the correct dependency metadata. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great!
Fixes brave/brave-browser#4205.
Submitter Checklist:
npm test brave_unit_tests && npm test brave_browser_tests && npm run test-security
) onnpm run lint
)git rebase master
(if needed).git rebase -i
to squash commits (if needed).Test Plan:
With packages on the release channel:
brave-keyring
package (e.g.apt install brave-browser
)brave-keyring
will be pulled in automaticallybrave-browser
can't be installed on its ownbrave-keyring
(e.g.apt remote brave-keyring
):brave-browser
With packages on the beta or dev channels:
brave-keyring
:brave-keyring
won't be pulled in automaticallybrave-keyring
manually afterbrave-browser-beta
brave-keyring
brave-browser-beta
Reviewer Checklist:
After-merge Checklist:
changes has landed on.