You are not logged in.
This error occurs on archlinux guest on a windows 10 host virtualbox behind a corporate proxy.
pacman -Syuworks. The error also occurs when I unset proxies and thether to my phone.
After cloning https://aur.archlinux.org/packages/roswell/ (also tried https://aur.archlinux.org/packages/package-query with same effect) i run
makepkg -siand get output
...
curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number
ERROR: Failure while downloading https://github.com/roswell/roswell/archive/v17.10.10.83.tar.gz
Aborting...When I try to build roswell from source I instead get this in the last step (where it tries to download sbcl-bin as part of the final setup.
...
Download Failed with status 2. See download_simple in src/download.c
[1] 7771 segmentation failt (core dumped) ros setupLooks much like this thread, which doesn't have a solution:
https://bbs.archlinux.org/viewtopic.php?id=227525
$ which curl
/usr/bin/curl
$ pacman -Q curl
curl 7.56.0-1
$ pacman -Qs openssl
local/openssl 1.1.0.f-2
local/openssl-1.0 1.0.2.l-1I recently setup a similar (apparently not identical!) virtualbox where I didn't encounter this problem, but perhaps I have forgotten to do something related to openssl? Any input welcome (obviously).
Offline
Are you fully up-to-date?
Offline
Are you fully up-to-date?
$ sudo pacman -Syu
...
there is nothing to do Offline
Is there a way I can improve the question?
Offline
Are you facing the curl problem described in https://bbs.archlinux.org/viewtopic.php?id=227520 and https://bbs.archlinux.org/viewtopic.php?id=226721 ?
Last edited by Lone_Wolf (2017-10-19 13:18:27)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Are you facing the curl problem described in https://bbs.archlinux.org/viewtopic.php?id=227520 and https://bbs.archlinux.org/viewtopic.php?id=226721 ?
First I didn't think so, but hopefully I am wrong.
I'm not behind my proxy for a few days, will try the solutions suggested ASAP.
Offline
Unfortuantely I have been on traveling foot for so long that I had to unset proxies and all sorts of other settings. The problem no longer exists and I am not sure I can reproduce the error in the same way as before.
Since I cannot offer a verified to solution to the problem I will have to let this rest until I again have a prolonger time behind a proxy.
Offline