08-07-2018, 10:04 PM
@rlugli
@FizzyTea
This error suggests to me a problem with security certificates in the TLS authentication process (called for by the "s" in "https:"). If you search the Web on it, you'll find that it turns up regularly in many different contexts. It's not specifically a moOde-build "thing".
I cannot repro your problem here (in Maryland USA) with a fresh install of 2018-06-27-raspbian-stretch-lite on a RPi0W with a WiFi connection. Cloning the ashuffle repo worked fine.
This was even before I performed the two-step apt update and upgrade procedure which upgraded 22 packages including, I note, "ca-certificates".
Cloning the ashuffle repo afresh after the upgrade worked fine too.
I confess I don't have an explanation for why you were able to complete the process on an RPi3. The only thing which comes to mind is that the RPi0W has an ARMv6 CPU and the RPi3B has an ARMv7 cpu. Possibly they exercise some different code paths in the libraries. I'm grasping at straws here. Maybe it was just the timing.
I'm curious where you are located in the world. The Internet is a complex enterprise. It's also possible we are being served files through different portals which can lead to differences at least in the short term.
Regards,
Kent
@FizzyTea
Code:
fatal: unable to access 'https://github.com/Joshkunz/ashuffle.git/': gnutls_handshake() failed: Error in the push function.
This error suggests to me a problem with security certificates in the TLS authentication process (called for by the "s" in "https:"). If you search the Web on it, you'll find that it turns up regularly in many different contexts. It's not specifically a moOde-build "thing".
I cannot repro your problem here (in Maryland USA) with a fresh install of 2018-06-27-raspbian-stretch-lite on a RPi0W with a WiFi connection. Cloning the ashuffle repo worked fine.
Code:
pi@raspberrypi:~ $ sudo git clone https://github.com/Joshkunz/ashuffle.git/
Cloning into 'ashuffle'...
remote: Counting objects: 259, done.
remote: Total 259 (delta 0), reused 0 (delta 0), pack-reused 259
Receiving objects: 100% (259/259), 50.10 KiB | 0 bytes/s, done.
Resolving deltas: 100% (163/163), done.
This was even before I performed the two-step apt update and upgrade procedure which upgraded 22 packages including, I note, "ca-certificates".
Cloning the ashuffle repo afresh after the upgrade worked fine too.
I confess I don't have an explanation for why you were able to complete the process on an RPi3. The only thing which comes to mind is that the RPi0W has an ARMv6 CPU and the RPi3B has an ARMv7 cpu. Possibly they exercise some different code paths in the libraries. I'm grasping at straws here. Maybe it was just the timing.
I'm curious where you are located in the world. The Internet is a complex enterprise. It's also possible we are being served files through different portals which can lead to differences at least in the short term.
Regards,
Kent