The package you got from GitHub is exactly what you get from the repo regardless of the keyword you use in the repo config file. The same packages are used for all Debian-based distros. There be dragons.ĭespite the name in our repo configuration, the packages are not specific to Ubuntu. I understand the confusion and you're right about not wanting to mix packages between the Debian and Ubuntu repositories. I think it would be reasonable to state somewhere that the deb and rpm repos provide packages for the amd64 architecture only.įor starters, I won't use an ubuntu repo on my debian install. I have ommited the part of the repo lines since I am on amd64 architecture and I do not use. thisīut it does not, so the right way can only be found via trial and error.įinally, I won't mind installing/upgrading to beta (or nightly or dev) version by manually downloading and installing the deb file from github each time, provided that these debs do not list brave-keyring as a direct dependency, for both now and in the future. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |