How do I fix this key signing issue with NeuroScience Debian?
up vote
0
down vote
favorite
super sleep deprived but coherent. Hopefully not being a complete dope and this laptop has caused me some trouble before. I added the keys from Neuroscience Debian just yesterday no sweat on another machine. Not sure if it's the lack of sleep or what but I'm receiving an error I can't mentally process right now. Thanks for all the help.
Following the instructions on this link: http://neuro.debian.net/ and selecting "Ubuntu Xenial (16.04), USA California Server, I receive this from the instruction outputs:
" wget -O- http://neuro.debian.net/lists/xenial.us-ca.full | sudo tee /etc/apt/sources.list.d/neurodebian.sources.list
--2017-08-21 19:00:02-- http://neuro.debian.net/lists/xenial.us-ca.full
Resolving neuro.debian.net (neuro.debian.net)... 129.170.30.193
Connecting to neuro.debian.net (neuro.debian.net)|129.170.30.193|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 262 [text/plain]
Saving to: ‘STDOUT’
- 0%[ ] 0 --.-KB/s deb http://neurodeb.pirsquared.org data main contrib non-free
#deb-src http://neurodeb.pirsquared.org data main contrib non-free
deb http://neurodeb.pirsquared.org xenial main contrib non-free
#deb-src http://neurodeb.pirsquared.org xenial main contrib non-free
- 100%[===================>] 262 --.-KB/s in 0s
2017-08-21 19:00:04 (55.8 MB/s) - written to stdout [262/262]
"
That's fine and dandy, problem is the key ain't checking out:
"sudo apt-key adv --recv-keys --keyserver hkp://pool.sks-keyservers.net:80 0xA5D32F012649A5A9
Executing: /tmp/tmp.ZGsHDOyuEZ/gpg.1.sh --recv-keys
--keyserver
hkp://pool.sks-keyservers.net:80
0xA5D32F012649A5A9
gpg: requesting key 2649A5A9 from hkp server pool.sks-keyservers.net
gpgkeys: key A5D32F012649A5A9 can't be retrieved
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: keyserver communications error: keyserver helper general error
gpg: keyserver communications error: unknown pubkey algorithm
gpg: keyserver receive failed: unknown pubkey algorithm"
I tried clearing any existing keys and re-signing, updating and rebooting. Not a weird cache issue and not a lost packet error. Thanks again for any assistance.
ppa debian
edited Nov 18 '17 at 21:14
Tim
19.5k1483138
asked Aug 22 '17 at 2:14
Tmanok
175
add a comment |
up vote
0
down vote
favorite
super sleep deprived but coherent. Hopefully not being a complete dope and this laptop has caused me some trouble before. I added the keys from Neuroscience Debian just yesterday no sweat on another machine. Not sure if it's the lack of sleep or what but I'm receiving an error I can't mentally process right now. Thanks for all the help.
Following the instructions on this link: http://neuro.debian.net/ and selecting "Ubuntu Xenial (16.04), USA California Server, I receive this from the instruction outputs:
" wget -O- http://neuro.debian.net/lists/xenial.us-ca.full | sudo tee /etc/apt/sources.list.d/neurodebian.sources.list
--2017-08-21 19:00:02-- http://neuro.debian.net/lists/xenial.us-ca.full
Resolving neuro.debian.net (neuro.debian.net)... 129.170.30.193
Connecting to neuro.debian.net (neuro.debian.net)|129.170.30.193|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 262 [text/plain]
Saving to: ‘STDOUT’
- 0%[ ] 0 --.-KB/s deb http://neurodeb.pirsquared.org data main contrib non-free
#deb-src http://neurodeb.pirsquared.org data main contrib non-free
deb http://neurodeb.pirsquared.org xenial main contrib non-free
#deb-src http://neurodeb.pirsquared.org xenial main contrib non-free
- 100%[===================>] 262 --.-KB/s in 0s
2017-08-21 19:00:04 (55.8 MB/s) - written to stdout [262/262]
"
That's fine and dandy, problem is the key ain't checking out:
"sudo apt-key adv --recv-keys --keyserver hkp://pool.sks-keyservers.net:80 0xA5D32F012649A5A9
Executing: /tmp/tmp.ZGsHDOyuEZ/gpg.1.sh --recv-keys
--keyserver
hkp://pool.sks-keyservers.net:80
0xA5D32F012649A5A9
gpg: requesting key 2649A5A9 from hkp server pool.sks-keyservers.net
gpgkeys: key A5D32F012649A5A9 can't be retrieved
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: keyserver communications error: keyserver helper general error
gpg: keyserver communications error: unknown pubkey algorithm
gpg: keyserver receive failed: unknown pubkey algorithm"
I tried clearing any existing keys and re-signing, updating and rebooting. Not a weird cache issue and not a lost packet error. Thanks again for any assistance.
ppa debian
edited Nov 18 '17 at 21:14
Tim
19.5k1483138
asked Aug 22 '17 at 2:14
Tmanok
175
sounds like their key doesn't exist in the keyservers, or you've got something odd going on? Typically this isn't solvable by end-users, and needs to be handled by the people publishing the specific software.
– Thomas Ward♦
Aug 22 '17 at 2:16
Ok thanks Thomas, I wasn't sure what I could possibly be doing wrong... If there's any info I can provide let me know.
– Tmanok
Aug 22 '17 at 3:13
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
super sleep deprived but coherent. Hopefully not being a complete dope and this laptop has caused me some trouble before. I added the keys from Neuroscience Debian just yesterday no sweat on another machine. Not sure if it's the lack of sleep or what but I'm receiving an error I can't mentally process right now. Thanks for all the help.
Following the instructions on this link: http://neuro.debian.net/ and selecting "Ubuntu Xenial (16.04), USA California Server, I receive this from the instruction outputs:
" wget -O- http://neuro.debian.net/lists/xenial.us-ca.full | sudo tee /etc/apt/sources.list.d/neurodebian.sources.list
--2017-08-21 19:00:02-- http://neuro.debian.net/lists/xenial.us-ca.full
Resolving neuro.debian.net (neuro.debian.net)... 129.170.30.193
Connecting to neuro.debian.net (neuro.debian.net)|129.170.30.193|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 262 [text/plain]
Saving to: ‘STDOUT’
- 0%[ ] 0 --.-KB/s deb http://neurodeb.pirsquared.org data main contrib non-free
#deb-src http://neurodeb.pirsquared.org data main contrib non-free
deb http://neurodeb.pirsquared.org xenial main contrib non-free
#deb-src http://neurodeb.pirsquared.org xenial main contrib non-free
- 100%[===================>] 262 --.-KB/s in 0s
2017-08-21 19:00:04 (55.8 MB/s) - written to stdout [262/262]
"
That's fine and dandy, problem is the key ain't checking out:
"sudo apt-key adv --recv-keys --keyserver hkp://pool.sks-keyservers.net:80 0xA5D32F012649A5A9
Executing: /tmp/tmp.ZGsHDOyuEZ/gpg.1.sh --recv-keys
--keyserver
hkp://pool.sks-keyservers.net:80
0xA5D32F012649A5A9
gpg: requesting key 2649A5A9 from hkp server pool.sks-keyservers.net
gpgkeys: key A5D32F012649A5A9 can't be retrieved
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: keyserver communications error: keyserver helper general error
gpg: keyserver communications error: unknown pubkey algorithm
gpg: keyserver receive failed: unknown pubkey algorithm"
I tried clearing any existing keys and re-signing, updating and rebooting. Not a weird cache issue and not a lost packet error. Thanks again for any assistance.
ppa debian
edited Nov 18 '17 at 21:14
Tim
19.5k1483138
asked Aug 22 '17 at 2:14
Tmanok
175
super sleep deprived but coherent. Hopefully not being a complete dope and this laptop has caused me some trouble before. I added the keys from Neuroscience Debian just yesterday no sweat on another machine. Not sure if it's the lack of sleep or what but I'm receiving an error I can't mentally process right now. Thanks for all the help.
Following the instructions on this link: http://neuro.debian.net/ and selecting "Ubuntu Xenial (16.04), USA California Server, I receive this from the instruction outputs:
" wget -O- http://neuro.debian.net/lists/xenial.us-ca.full | sudo tee /etc/apt/sources.list.d/neurodebian.sources.list
--2017-08-21 19:00:02-- http://neuro.debian.net/lists/xenial.us-ca.full
Resolving neuro.debian.net (neuro.debian.net)... 129.170.30.193
Connecting to neuro.debian.net (neuro.debian.net)|129.170.30.193|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 262 [text/plain]
Saving to: ‘STDOUT’
- 0%[ ] 0 --.-KB/s deb http://neurodeb.pirsquared.org data main contrib non-free
#deb-src http://neurodeb.pirsquared.org data main contrib non-free
deb http://neurodeb.pirsquared.org xenial main contrib non-free
#deb-src http://neurodeb.pirsquared.org xenial main contrib non-free
- 100%[===================>] 262 --.-KB/s in 0s
2017-08-21 19:00:04 (55.8 MB/s) - written to stdout [262/262]
"
That's fine and dandy, problem is the key ain't checking out:
"sudo apt-key adv --recv-keys --keyserver hkp://pool.sks-keyservers.net:80 0xA5D32F012649A5A9
Executing: /tmp/tmp.ZGsHDOyuEZ/gpg.1.sh --recv-keys
--keyserver
hkp://pool.sks-keyservers.net:80
0xA5D32F012649A5A9
gpg: requesting key 2649A5A9 from hkp server pool.sks-keyservers.net
gpgkeys: key A5D32F012649A5A9 can't be retrieved
gpg: no valid OpenPGP data found.
gpg: Total number processed: 0
gpg: keyserver communications error: keyserver helper general error
gpg: keyserver communications error: unknown pubkey algorithm
gpg: keyserver receive failed: unknown pubkey algorithm"
I tried clearing any existing keys and re-signing, updating and rebooting. Not a weird cache issue and not a lost packet error. Thanks again for any assistance.
ppa debian
ppa debian
edited Nov 18 '17 at 21:14
Tim
19.5k1483138
asked Aug 22 '17 at 2:14
Tmanok
175
edited Nov 18 '17 at 21:14
Tim
19.5k1483138
asked Aug 22 '17 at 2:14
Tmanok
175
edited Nov 18 '17 at 21:14
Tim
19.5k1483138
edited Nov 18 '17 at 21:14
Tim
19.5k1483138
edited Nov 18 '17 at 21:14
Tim
19.5k1483138
19.5k1483138
asked Aug 22 '17 at 2:14
Tmanok
175
asked Aug 22 '17 at 2:14
Tmanok
175
asked Aug 22 '17 at 2:14
Tmanok
175
175
sounds like their key doesn't exist in the keyservers, or you've got something odd going on? Typically this isn't solvable by end-users, and needs to be handled by the people publishing the specific software.
– Thomas Ward♦
Aug 22 '17 at 2:16
Ok thanks Thomas, I wasn't sure what I could possibly be doing wrong... If there's any info I can provide let me know.
– Tmanok
Aug 22 '17 at 3:13
add a comment |
sounds like their key doesn't exist in the keyservers, or you've got something odd going on? Typically this isn't solvable by end-users, and needs to be handled by the people publishing the specific software.
– Thomas Ward♦
Aug 22 '17 at 2:16
Ok thanks Thomas, I wasn't sure what I could possibly be doing wrong... If there's any info I can provide let me know.
– Tmanok
Aug 22 '17 at 3:13
sounds like their key doesn't exist in the keyservers, or you've got something odd going on? Typically this isn't solvable by end-users, and needs to be handled by the people publishing the specific software.
– Thomas Ward♦
Aug 22 '17 at 2:16
sounds like their key doesn't exist in the keyservers, or you've got something odd going on? Typically this isn't solvable by end-users, and needs to be handled by the people publishing the specific software.
– Thomas Ward♦
Aug 22 '17 at 2:16
Ok thanks Thomas, I wasn't sure what I could possibly be doing wrong... If there's any info I can provide let me know.
– Tmanok
Aug 22 '17 at 3:13
Ok thanks Thomas, I wasn't sure what I could possibly be doing wrong... If there's any info I can provide let me know.
– Tmanok
Aug 22 '17 at 3:13
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
you could also just fetch the key from the neurodebian website directly... see http://neuro.debian.net/faq.html "What means “The following signatures couldn’t be verified...”?"
answered Aug 24 '17 at 6:03
Yaroslav Halchenko
581143
Hi Yaroslav, I was away for some time and my network turned into chaos. I will re-check whether this answer is correct. However on another machine off site I was able to install without any issues- perhaps the key has been fixed or perhaps this is a device specific issue. I will update you within the next few days. Thanks for your patience.
– Tmanok
Aug 29 '17 at 7:00
yes, in general fetching the key from public servers should work. But some times there are hiccups from the overloaded servers etc. That is why we also provide that key as a simple download (pointed in the FAQ)
– Yaroslav Halchenko
Aug 30 '17 at 13:42
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
you could also just fetch the key from the neurodebian website directly... see http://neuro.debian.net/faq.html "What means “The following signatures couldn’t be verified...”?"
answered Aug 24 '17 at 6:03
Yaroslav Halchenko
581143
Hi Yaroslav, I was away for some time and my network turned into chaos. I will re-check whether this answer is correct. However on another machine off site I was able to install without any issues- perhaps the key has been fixed or perhaps this is a device specific issue. I will update you within the next few days. Thanks for your patience.
– Tmanok
Aug 29 '17 at 7:00
yes, in general fetching the key from public servers should work. But some times there are hiccups from the overloaded servers etc. That is why we also provide that key as a simple download (pointed in the FAQ)
– Yaroslav Halchenko
Aug 30 '17 at 13:42
add a comment |
up vote
0
down vote
you could also just fetch the key from the neurodebian website directly... see http://neuro.debian.net/faq.html "What means “The following signatures couldn’t be verified...”?"
answered Aug 24 '17 at 6:03
Yaroslav Halchenko
581143
Hi Yaroslav, I was away for some time and my network turned into chaos. I will re-check whether this answer is correct. However on another machine off site I was able to install without any issues- perhaps the key has been fixed or perhaps this is a device specific issue. I will update you within the next few days. Thanks for your patience.
– Tmanok
Aug 29 '17 at 7:00
yes, in general fetching the key from public servers should work. But some times there are hiccups from the overloaded servers etc. That is why we also provide that key as a simple download (pointed in the FAQ)
– Yaroslav Halchenko
Aug 30 '17 at 13:42
add a comment |
up vote
0
down vote
up vote
0
down vote
you could also just fetch the key from the neurodebian website directly... see http://neuro.debian.net/faq.html "What means “The following signatures couldn’t be verified...”?"
answered Aug 24 '17 at 6:03
Yaroslav Halchenko
581143
you could also just fetch the key from the neurodebian website directly... see http://neuro.debian.net/faq.html "What means “The following signatures couldn’t be verified...”?"
answered Aug 24 '17 at 6:03
Yaroslav Halchenko
581143
answered Aug 24 '17 at 6:03
Yaroslav Halchenko
581143
answered Aug 24 '17 at 6:03
Yaroslav Halchenko
581143
answered Aug 24 '17 at 6:03
Yaroslav Halchenko
581143
581143
Hi Yaroslav, I was away for some time and my network turned into chaos. I will re-check whether this answer is correct. However on another machine off site I was able to install without any issues- perhaps the key has been fixed or perhaps this is a device specific issue. I will update you within the next few days. Thanks for your patience.
– Tmanok
Aug 29 '17 at 7:00
yes, in general fetching the key from public servers should work. But some times there are hiccups from the overloaded servers etc. That is why we also provide that key as a simple download (pointed in the FAQ)
– Yaroslav Halchenko
Aug 30 '17 at 13:42
add a comment |
Hi Yaroslav, I was away for some time and my network turned into chaos. I will re-check whether this answer is correct. However on another machine off site I was able to install without any issues- perhaps the key has been fixed or perhaps this is a device specific issue. I will update you within the next few days. Thanks for your patience.
– Tmanok
Aug 29 '17 at 7:00
yes, in general fetching the key from public servers should work. But some times there are hiccups from the overloaded servers etc. That is why we also provide that key as a simple download (pointed in the FAQ)
– Yaroslav Halchenko
Aug 30 '17 at 13:42
Hi Yaroslav, I was away for some time and my network turned into chaos. I will re-check whether this answer is correct. However on another machine off site I was able to install without any issues- perhaps the key has been fixed or perhaps this is a device specific issue. I will update you within the next few days. Thanks for your patience.
– Tmanok
Aug 29 '17 at 7:00
Hi Yaroslav, I was away for some time and my network turned into chaos. I will re-check whether this answer is correct. However on another machine off site I was able to install without any issues- perhaps the key has been fixed or perhaps this is a device specific issue. I will update you within the next few days. Thanks for your patience.
– Tmanok
Aug 29 '17 at 7:00
yes, in general fetching the key from public servers should work. But some times there are hiccups from the overloaded servers etc. That is why we also provide that key as a simple download (pointed in the FAQ)
– Yaroslav Halchenko
Aug 30 '17 at 13:42
yes, in general fetching the key from public servers should work. But some times there are hiccups from the overloaded servers etc. That is why we also provide that key as a simple download (pointed in the FAQ)
– Yaroslav Halchenko
Aug 30 '17 at 13:42
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f948504%2fhow-do-i-fix-this-key-signing-issue-with-neuroscience-debian%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
sounds like their key doesn't exist in the keyservers, or you've got something odd going on? Typically this isn't solvable by end-users, and needs to be handled by the people publishing the specific software.
– Thomas Ward♦
Aug 22 '17 at 2:16
Ok thanks Thomas, I wasn't sure what I could possibly be doing wrong... If there's any info I can provide let me know.
– Tmanok
Aug 22 '17 at 3:13