[Voyage-linux] Github seems to be broken

[seabird]

Hi everyone,

just did a fresh install of my ALIX with voyage 0.9

Tried to get some software of github, but doesn't seem to work. The command
works fine on a (virtual) ubuntu install:

root at voyage:~# wget https://github.com/Whytey/py-openzwave/tarball/master
--2012-12-10 13:22:46-- 
https://github.com/Whytey/py-openzwave/tarball/master
Resolving github.com (github.com)... 207.97.227.239
Connecting to github.com (github.com)|207.97.227.239|:443... connected.
ERROR: The certificate of `github.com' is not trusted.
ERROR: The certificate of `github.com' hasn't got a known issuer.
[2]+  Killed                  wget --no-check-certificate
https://nodeload.github.com/Whytey/py-openzwave/legacy.tar.gz/master
root at voyage:~#

and with --no-check-certificate

root at voyage:~# wget https://github.com/Whytey/py-openzwave/tarball/master
--no-check-certificate
--2012-12-10 13:24:07-- 
https://github.com/Whytey/py-openzwave/tarball/master
Resolving github.com (github.com)... 207.97.227.239
Connecting to github.com (github.com)|207.97.227.239|:443... connected.
WARNING: The certificate of `github.com' is not trusted.
WARNING: The certificate of `github.com' hasn't got a known issuer.
HTTP request sent, awaiting response... 302 Found
Location:
https://nodeload.github.com/Whytey/py-openzwave/legacy.tar.gz/master
[following]
--2012-12-10 13:24:08-- 
https://nodeload.github.com/Whytey/py-openzwave/legacy.tar.gz/master
Resolving nodeload.github.com (nodeload.github.com)... 207.97.227.252
Connecting to nodeload.github.com
(nodeload.github.com)|207.97.227.252|:443... connected.
WARNING: The certificate of `nodeload.github.com' is not trusted.
WARNING: The certificate of `nodeload.github.com' hasn't got a known issuer.
HTTP request sent, awaiting response... Read error (The request is invalid.)
in headers.
Retrying.

--2012-12-10 13:24:13--  (try: 2) 
https://nodeload.github.com/Whytey/py-openzwave/legacy.tar.gz/master
Connecting to nodeload.github.com
(nodeload.github.com)|207.97.227.252|:443... connected.
...................

Did I overlook anything?? How to fix this??



--
View this message in context: http://voyage-linux.34677.n3.nabble.com/Github-seems-to-be-broken-tp4025398.html
Sent from the Voyage Linux mailing list archive at Nabble.com.