Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#51352 - ca certificates broken out of the box

Attached to Project: Arch Linux
Opened by Eric Toombs (ewtoombs) - Thursday, 13 October 2016, 03:59 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 04 November 2016, 12:49 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I just finished a fresh install of archlinux. I tried a makepkg -si and got the following error message:

==> Retrieving sources...
-> Downloading cower-16.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (77) error setting certificate verify locations:
CAfile: /etc/ssl/certs/ca-certificates.crt
CApath: none
==> ERROR: Failure while downloading https://pkgbuild.com/~dreisner/sources/cower/cower-16.tar.gz
Aborting...

I fixed it by running update-ca-trust---something that clearly should have been done automatically by whatever ssley package is responsible for this type of thing.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 04 November 2016, 12:49 GMT
Reason for closing:  No response
Comment by Jonathan Roemer (pid1) - Wednesday, 26 October 2016, 02:02 GMT
What package are you actually reporting this bug against, and which version of that package? ca-certificates-mozilla successfully validates the pkgbuild.com Let's Encrypt certificate.
Comment by Eric Toombs (ewtoombs) - Wednesday, 26 October 2016, 22:55 GMT
I don't know which package is responsible for this. All I know is that right now, on fresh archlinux installs, for some reason you have to run update-ca-trust before SSL works right. I've seen it happen a few times now, since I've had to do a few fresh installs lately.

To reproduce, you just do a fresh archlinux install and try curling any https URL. Beyond that, sorry I'm completely baffled.
Comment by Doug Newgard (Scimmia) - Wednesday, 26 October 2016, 23:19 GMT
What install disk are you running? The pacman hook should be running this when you install. I've been looking around trying to find an explanation why it wouldn't get run, but I'm not finding much unless it's an old install disk.
Comment by Eric Toombs (ewtoombs) - Thursday, 27 October 2016, 00:23 GMT
oh, that's possible actually. The install image I used is pretty old now. OK, I'll try the same thing with a newer image. Thanks for the suggestion.

Loading...