On 2020-04-20 18:30, Ed Greshko wrote:
On 2020-04-19 04:58, ToddAndMargo via test wrote:
Dear Testers,
To get FC32 to upgrade on one of my VM's, I have to add
--disablerepo=brave*
to the following:
#dnf --enablerepo=* update --refresh --disablerepo=brave*
...
# dnf system-upgrade download --refresh --releasever=32 --allowerasing --best
--disablerepo=brave*
I opened:
GPG check FAILED on RPM installation with Fedora 32
https://github.com/brave/brave-browser/issues/9315
I checked that open issue. It doesn't appear as any action has been taken
since it shows
Assignees No one assigned
Labels None yet
Projects None yet
Milestone No milestone
Linked pull requests Successfully merging a pull request may close this issue.
None yet
I did the following
1. Installed Brave on a fully updated F31 VM. No Problems
2. Installed Brave on a fully updated F32 Beta VM. No Problems
3. Upgraded the F31 VM by doing
sudo dnf system-upgrade download --releasever=32
And the upgrade succeeded without problems.
You may want to run your test again.
Hi Ed,
The problem was that
# rpm --import https://brave-browser-rpm-release.s3.brave.com/brave-core.asc
did not overwrite the old key. The old key had to
be removed manually, but you already know this as
you taught me how. :-)
Now the 64,000 dollar question is, is this a bug
or normal operation?
-T
_______________________________________________
test mailing list -- test@lists.fedoraproject.org
To unsubscribe send an email to test-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/test@lists.fedoraproject.org
