This is a multi-part message in MIME format.
On 19/03/2025 11:03, Adrian Bunk wrote:
It's easy to reproduce even with the binary package when you remove
openssl (see #1099669).
I've now reproduced the bug.
It seems the package will build successfully as long as /etc/ssl/certs
exits, but will fail if that directory does not exist. Installing openssl
is one way to cause that directory to come into existence, but it's
not the only way, and the directory may (or may not) persist after
the package that caused it to exist is removed.
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">On 19/03/2025 11:03, Adrian Bunk wrote:<span
style="white-space: pre-wrap">
</span></div>
<blockquote type="cite" cite="mid:Z9qknoeGLBxwJgRU@localhost">
<pre wrap="" class="moz-quote-pre">It's easy to reproduce even with the binary package when you remove
openssl (see #1099669).
</pre>
</blockquote>
<p>I've now reproduced the bug.</p>
<p>It seems the package will build successfully as long as
/etc/ssl/certs<br>
exits, but will fail if that directory does not exist. Installing
openssl<br>
is one way to cause that directory to come into existence, but
it's<br>
not the only way, and the directory may (or may not) persist after<br>
the package that caused it to exist is removed.<br>
<br>
</p>
</body>
</html>
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)