On 26/03/19 13:46, Robert Nelson wrote:
On Tue, Mar 26, 2019 at 5:25 AM Sardar Vayghannezgad
<[email protected]> wrote:
Hi everyone.
I'm having a hrad time downloading the packages and whatnot.
My stats.
root@beaglebone:/home/machinekit# uname -a
Linux beaglebone 3.8.13-xenomai-r83 #1 Thu Jan 5 01:32:32 UTC 2017 armv7l
GNU/Linux
root@beaglebone:/home/machinekit# hostnamectl
Static hostname: beaglebone
Icon name: computer
Machine ID: f4ee2c0f817c4a6e91d28c4d1c48a642
Boot ID: 94201995500146bbaf62c8705208f177
Operating System: Debian GNU/Linux 8 (jessie)
Kernel: Linux 3.8.13-xenomai-r83
Architecture: arm
I am currently well on my way to have M.K on my BBB for using on my Windows
Desktop, but my problems are:
I am not exactly sure which link is for me here. Since I'm using Jessie, 6,7
and 8 on that link are out, right? (If so, what is that BBB in the 6.Debian
Stretch on armhf (BBB | RPi2/3 | Other armhf)?
What about #1-5? Does it matter that my Laptop Windows system, on which I
want to see my Machinekit interface, is 64-bit, Does that mean I should go for
#5. Debian Jessie on amd64? But, at the same time, I'm using Beaglebone Black.
Does this imply I download from 2.Debian Jessie on arm7 (BeagleBone)
Even if I attempt to download from whichever link, I can't seem to succeed;
this is what I get on my PuTTY:
root@beaglebone:/home/machinekit# sudo apt-key adv --keyserver
hkp://keyserver.ubuntu.com:80 --recv 43DDF224
Executing: gpg --ignore-time-conflict --no-options --no-default-keyring
--homedir /tmp/tmp.DGANIHYx8U --no-auto-check-trustdb --trust-model always
--keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring
/etc/apt/trusted.gpg.d/debian-archive-jessie-automatic.gpg --keyring
/etc/apt/trusted.gpg.d/debian-archive-jessie-security-automatic.gpg --keyring
/etc/apt/trusted.gpg.d/debian-archive-jessie-stable.gpg --keyring
/etc/apt/trusted.gpg.d/debian-archive-stretch-automatic.gpg --keyring
/etc/apt/trusted.gpg.d/debian-archive-stretch-security-automatic.gpg --keyring
/etc/apt/trusted.gpg.d/debian-archive-stretch-stable.gpg --keyring
/etc/apt/trusted.gpg.d/debian-archive-wheezy-automatic.gpg --keyring
/etc/apt/trusted.gpg.d/debian-archive-wheezy-stable.gpg --keyring
/etc/apt/trusted.gpg.d/rcn-ee-archive-2015.gpg --keyserver
hkp://keyserver.ubuntu.com:80 --recv 43DDF224
gpg: requesting key 43DDF224 from hkp server keyserver.ubuntu.com
gpg: keyserver timed out
gpg: keyserver receive failed: keyserver error
It helps to actually "read" the error message, as it's telling you
something important..
Now if you go to keyserver.ubuntu.com and enter 43DDF224 it'll also tell you:
"No results found
No results found: No keys found"
Which should make it obvious that 43DDF224 doesn't exist on that keyserver..
Regards,
Actually the key does exist.
$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv 43DDF224
Executing: /tmp/apt-key-gpghome.XmS0K1WNt4/gpg.1.sh --keyserver
keyserver.ubuntu.com --recv 43DDF224
gpg: key 31B5958F43DDF224: "Machinekit Signer <[email protected]>"
not changed
gpg: Total number processed: 1
gpg: unchanged: 1
Try just keyserver.ubuntu.com or with http:// or https:// prefixes
Sometimes it is unavailable for not good reason, or your firewall blocks
it, and GPG will come up with the wrong error
and tell you it does not exist.
Why the web form at http://keyserver.ubuntu.com/ tells you it does not
exist I don't know.
And yes, you need your BBB time set to real time, all sorts of problems
can occur if you don't, especially if it is in advance
of real time.
--
website: http://www.machinekit.io blog: http://blog.machinekit.io github:
https://github.com/machinekit
---
You received this message because you are subscribed to the Google Groups "Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.
