From: CaptainDrewBoy <CaptainDrewBoy@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: libmbedcrypto breaking some apps
Date: Sat, 25 Jun 2022 12:47:17 +0200 [thread overview]
Message-ID: <20220625104717.JWlNaPNq_YhXJpTUnDsjlURliftbUKy8LofOzn8y7tQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37665@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 773 bytes --]
New comment by CaptainDrewBoy on void-packages repository
https://github.com/void-linux/void-packages/issues/37665#issuecomment-1166254498
Comment:
> I can not reproduce this, the file is not empty on my system. What's the output of xuname on your system? Please use the bug issue template next time when reporting bugs.
Firstly, sorry for not using the template.
xuname gives `Void 5.15.47_1 x86_64 GenuineIntel uptodate rrrmFFFFFF`
> `/usr/lib/libmbedcrypto.so.2.16.12` if this file is empty, `xbps-pkgdb` should report an errors. Are you sure you install `mbedtls` correctly?
`mbedtls` was pulled in as a dependency for something pretty quickly after I setup my system iirc. I've never really messed with its installation, xbps has just managed it for me.
next prev parent reply other threads:[~2022-06-25 10:47 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 1:31 [ISSUE] " CaptainDrewBoy
2022-06-24 1:39 ` HadetTheUndying
2022-06-24 4:26 ` sgn
2022-06-24 12:35 ` CaptainDrewBoy
2022-06-24 13:35 ` sgn
2022-06-24 18:18 ` CaptainDrewBoy
2022-06-24 18:18 ` CaptainDrewBoy
2022-06-24 18:18 ` CaptainDrewBoy
2022-06-24 18:19 ` CaptainDrewBoy
2022-06-24 18:57 ` paper42
2022-06-25 3:11 ` sgn
2022-06-25 10:47 ` CaptainDrewBoy [this message]
2022-06-25 13:36 ` sgn
2022-06-25 14:50 ` CaptainDrewBoy
2022-06-25 14:52 ` CaptainDrewBoy
2022-06-25 14:54 ` sgn
2022-06-25 15:02 ` [ISSUE] [CLOSED] " CaptainDrewBoy
2022-06-25 15:02 ` CaptainDrewBoy
2022-06-25 15:04 ` [ISSUE] [CLOSED] " sgn
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=20220625104717.JWlNaPNq_YhXJpTUnDsjlURliftbUKy8LofOzn8y7tQ@z \
--to=captaindrewboy@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).