getsolus / getsolus/packages

Missing `perl` dependency for `openssl` (T9220)

Open
#194 8 comments 0 reactions 1 assignee View on GitHub

@silkeh is already working on this.

Since Aug 16, 2023.

Packaging Problem Priority: Normal State: Stale Topic: Plumbing
Dominant language
Python
Stars
141
Forks
146
Avg merge
11h 7m
Merged PRs (30d)
407

Description

Silke (#silke), 2020-07-26 11:36:20 UTC

The openssl package includes a Perl script for updating the SSL certificates (/usr/bin/c_rehash). This script is required for updating the SSL certificates. This means that SSL can be broken if perl is not installed.

The issue can be reproduced on a clean install of 4.1 with (at least) perl removed. The output below is from a system containing only system.base:

# eopkg up -y
Updating repositories
<snip>
 [✗] Updating SSL certificates                                           failed

A copy of the command output follows:

/usr/bin/env: ‘perl’: No such file or directory
<snip>

# eopkg it -y ripgrep # or any other package
Following packages will be installed:
pcre2  ripgrep
Total size of package(s): 1.59 MB
Downloading 1 / 2
Package pcre2 found in repository Solus
Program terminated.
Could not fetch destination file "https://mirrors.rit.edu/solus/packages/shannon/p/pcre2/pcre2-10.34-8-1-x86_64.eopkg": [Errno 14] curl#60 - "SSL certificate problem: self signed certificate in certificate chain"
Please use 'eopkg help' for general help.

Fixing this requires downloading gdbm and perl over HTTP:

# curl -s -o perl.eopkg "http://mirrors.rit.edu/solus/packages/unstable/p/perl/perl-22-24-1-x86_64.delta.eopkg"
# curl -s -o gdbm.eopkg "http://mirrors.rit.edu/solus/packages/shannon/g/gdbm/gdbm-1.18.1-7-1-x86_64.eopkg"
# eopkg it gdbm.eopkg perl.eopkg
<snip>
[✓] Updating SSL certificates                                          success
<snip>

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.