Things would be a lot easier if the repo allowed http access from a browser to its root folder, i.e. W: GPG error: buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4FE13824E3FFC656Ĭhanging 'stable' to 'testing' or 'unstable', in order to avoid all those codenames which I can not even remember after 11.5+ years on debian, still pops the 403 error. However, since stretch will be labeled 'oldstable' this Saturday (July 6th 2019) with the release of debian 10, aka buster, I tried 'buster' there and it still works, mentioning only the missing key as above. Which can be resolved by installing brave-keyring, so the repo line is fine. W: GPG error: stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 4FE13824E3FFC656 Makes apt complain only about the missing keyring The reason is simple: frankendebian (google it if you do not know what it means).īut it results to a 403 error (forbidden) and apt reports thisĮ: Failed to fetch 403 Forbidden The brave-keyring is a mandatory ('hard') dependency as seen by apt-cacheįor starters, I won't use an ubuntu repo on my debian install. Is the issue reproducible on the latest version of Chrome? Noĭebian testing 圆4 and the installation/upgrade is done from the deb file provided from github (because there is no repo for debian).Does the issue resolve itself when disabling Brave Rewards? No.

Does the issue resolve itself when disabling Brave Shields? No.Can you reproduce this issue with the nightly channel? No.Can you reproduce this issue with the dev channel? No.Can you reproduce this issue with the beta channel? No,.Can you reproduce this issue with the current release? Yes, if you are on a debian based distro.The requested info from brave://version is not available because the browser can not be installed.

The installation should complete successfully. Įrrors were encountered while processing: Processing triggers for man-db (2.8.5-2).

Processing triggers for desktop-file-utils (0.23-4). Processing triggers for mime-support (3.62). ĭpkg: dependency problems prevent configuration of brave-browser:īrave-browser depends on brave-keyring however:ĭpkg: error processing package brave-browser (-install):ĭependency problems - leaving unconfigured

116920 files and directories currently installed.) $ sudo dpkg -i Downloads/brave-browser_0.66.99_b

Download the new version brave 1.58.137