From: xandkar <xandkar@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: collectd segfaults on launch
Date: Sat, 13 Mar 2021 00:35:29 +0100 [thread overview]
Message-ID: <20210312233529.lW6E6vkxeYQ4O9nPlu5o7_zxC2IXDkRXFGM95LZK3_I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29413@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
New comment by xandkar on void-packages repository
https://github.com/void-linux/void-packages/issues/29413#issuecomment-797814109
Comment:
Looks like I did have `libcrypto46` lingering[1], so I just removed it, but the problem persists.
```
$ xbps-query -s libssl
[*] libssl1.1-1.1.1j_2 Toolkit for Secure Sockets Layer and Transport Layer Security - SSL/TLS library
$ xbps-query -s libcrypto
[*] libcrypto1.1-1.1.1j_2 Toolkit for Secure Sockets Layer and Transport Layer Security - crypto library
[*] libcrypto46-3.1.5_2 Version of the TLS/crypto stack forked from OpenSSL - crypto library
```
This was the first time I installed the package/service, so I never had it in a working state (on Void).
[1]: I now remember installing it manually to run something which was linked to it.
next prev parent reply other threads:[~2021-03-12 23:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 14:11 [ISSUE] " xandkar
2021-03-12 20:09 ` ericonr
2021-03-12 23:35 ` xandkar [this message]
2021-03-13 0:01 ` ericonr
2021-03-13 1:20 ` xandkar
2021-03-14 14:00 ` xandkar
2021-03-14 14:43 ` ericonr
2021-03-14 15:10 ` leahneukirchen
2021-03-14 17:45 ` xandkar
2021-03-14 22:02 ` ericonr
2021-03-15 9:07 ` xandkar
2021-03-15 9:09 ` xandkar
2021-03-15 9:16 ` xandkar
2021-03-15 9:16 ` xandkar
2021-09-24 18:27 ` ericonr
2022-05-07 2:06 ` github-actions
2022-05-10 2:47 ` [ISSUE] [CLOSED] " ericonr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210312233529.lW6E6vkxeYQ4O9nPlu5o7_zxC2IXDkRXFGM95LZK3_I@z \
--to=xandkar@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).