Closed dmgolembiowski closed 3 years ago
Update:
I'm not sure if this makes a difference, but running curl https://packages.edgedb.com/keys/edgedb.asc | sudo apt-key add -
hangs indefinitely. It makes me wonder if a robots.txt
or similar middleware is treating the curl user agent in a special way, as I have no trouble curl
-ing elsewhere.
In the browser, I have no trouble getting the edgedb.asc
so I should be fine to pipe it into the apt-key add.
Update: Nevermind.
cat ~/Downloads/edgedb.asc | sudo apt-key add -
[sudo] password for david:
gpg: invalid key resource URL '/etc/apt/trusted.gpg.d/shells:fish:release:3.gpg'
gpg: keyblock resource '(null)': General error
gpg: key 6B73A36E6026DFCA: 1 signature not checked due to a missing key
gpg: key 7721F63BD38B4796: 2 signatures not checked due to missing keys
gpg: key 8C718D3B5072E1F5: 75 signatures not checked due to missing keys
gpg: key 0F92290A445B9007: 6 signatures not checked due to missing keys
gpg: key DC30D7C23CBBABEE: 4 signatures not checked due to missing keys
gpg: key 4DFAB270CAA96DFA: 4 signatures not checked due to missing keys
gpg: key DCC9EFBF77E11517: 2 signatures not checked due to missing keys
gpg: key 7638D0442B90D010: 4 signatures not checked due to missing keys
gpg: key 9D6D8F6BC857C906: 4 signatures not checked due to missing keys
gpg: key CBF8D6FD518E17E1: 2 signatures not checked due to missing keys
gpg: key E0B11894F66AEC98: 5 signatures not checked due to missing keys
gpg: key EDA0D2388AE22BA9: 5 signatures not checked due to missing keys
gpg: key EF0F382A1A7B6500: 2 signatures not checked due to missing keys
gpg: key 2CE2AC08D880C8E4: 1 signature not checked due to a missing key
gpg: Total number processed: 32
gpg: skipped new keys: 32
So did you find solution?
Looks like you have some specific configuration of GPG that fails. I.e. here is how apt-key works on debian:
$ curl https://packages.edgedb.com/keys/edgedb.asc | sudo apt-key add -
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1664 100 1664 0 0 4413 0 --:--:-- --:--:-- --:--:-- 4413
OK
I.e. it's mostly silent. Try adding any other key and see if this works.
Also take a look if the key is already there:
$ apt-key list edgedb
pub rsa4096 2019-01-28 [SC]
9A9B 63DB D0BC 712B 94ED E003 A3FF 3633 DF29 BDBF
uid [ unknown] EdgeDB (release signing) <releases@edgedb.com>
Not yet. Both of my Debian machines fail to add keys. How bothersome.
curl -sS https://download.spotify.com/debian/pubkey_0D811D58.gpg | sudo apt-key add -
echo "deb http://repository.spotify.com stable non-free" | sudo tee /etc/apt/sources.list.d/spotify.list
Same as before:
gpg: invalid key resource URL '/etc/apt/trusted.gpg.d/shells:fish:release:3.gpg'
gpg: keyblock resource '(null)': General error
gpg: key 6B73A36E6026DFCA: 1 signature not checked due to a missing key
...
So I ran # rm /etc/apt/gpg.trusted.d/shells:fish:release:3.gpg
.
All good :smile:
# curl https://packages.edgedb.com/keys/edgedb.asc | sudo apt-key add -
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1664 100 1664 0 0 3087 0 --:--:-- --:--:-- --:--:-- 3081
OK
(I think this is the correct spot to report this error?)
Description:
I have no idea. Maybe the shell script checks my OS for a
.profile
and prioritizes that over.bashrc
as being indicative of Ubuntu (and Ubuntu specific apt packaging?). This is strange.Details:
Recreation Steps:
Shell output:
Am I just a smooth-brain who has a pre-existing installation? possibly. But only with the docker variety.