Community Packages

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#57279 - [splint] certificate error in package source

Attached to Project: Community Packages
Opened by Erich Eckner (deepthought) - Monday, 29 January 2018, 17:16 GMT
Last edited by Sergej Pupykin (sergej) - Tuesday, 09 July 2019, 18:10 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

package build fails with:

==> Making package: splint 3.1.2.git20180129-1 (Mo 29. Jan 18:12:25 CET 2018)
==> Retrieving sources...
-> Cloning splint-patched git repo...
Cloning into bare repository '/usr/src/archlinux/community/splint/repos/community-x86_64/splint-patched'...
fatal: unable to access 'https://repo.or.cz/splint-patched.git/': SSL certificate problem: self signed certificate in certificate chain
==> ERROR: Failure while downloading splint-patched git repo

Additional info:
* package version(s)
git revision c716be4957cc2d41c04a17383d4a76e26dff8fa4

Steps to reproduce:
> cd splint/repos/community-x86_64
> makepkg --verifysource
This task depends upon

Closed by  Sergej Pupykin (sergej)
Tuesday, 09 July 2019, 18:10 GMT
Reason for closing:  Fixed
Comment by Eli Schwartz (eschwartz) - Monday, 29 January 2018, 17:46 GMT
This is super-weird actually, I don't understand why they don't use LetsEncrypt now, like normal people.

http://repo.or.cz/rootcert.html

I've sent them an email asking about this.

Loading...