Hey all, not so much a help me as more an issue:
When verifying the brave package the GConf2 problem is posted. This seems to be a non issue as GConf2 is correctly supplied and linked. Brave functions correctly regardless. Broken requirement check?
When upgrading to Brave 0.13.2 the brave-rpm-release repository is supplying it but no public key?
brave-0.13.2.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID 448eee6c: NOKEY V4 RSA/SHA256 Signature, key ID 448eee6c: NOKEY
everything works fine if you ignore the broken requirement and ignore gpg checks in upgrade or install, where can we get the keyfile? And just additionally is it possible to get the repository to keep the previous version available? That way if any future versions do cause significant issues we have a simple rollback available to us?