From: balejk <balejk@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mtxclient causes nheko to segfault
Date: Wed, 08 Jun 2022 15:30:30 +0200 [thread overview]
Message-ID: <20220608133030.G77ycyRtIYbWyy45Cr2YBdlZKAQu1wZMHailu8J9VRg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37442@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 470 bytes --]
New comment by balejk on void-packages repository
https://github.com/void-linux/void-packages/issues/37442#issuecomment-1149919413
Comment:
I believe this was caused by a recent update of `spdlog`, which both `nheko` and `mtxclient` rely on. Only `nheko` was rebuilt against the new version as `spdlog` was not explicitly listed in `makedepends` of `mtxclient` and it was only pulled indirectly as a dependency of `coeurl`. I'm opening a pull request to address this.
next prev parent reply other threads:[~2022-06-08 13:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 4:33 [ISSUE] " RunningDroid
2022-06-08 13:30 ` balejk [this message]
2022-06-08 14:48 ` balejk
2022-06-08 21:12 ` deepbluev7
2022-06-08 21:12 ` deepbluev7
2022-06-11 9:44 ` kartikynwa
2022-06-11 10:26 ` [ISSUE] [CLOSED] " Johnnynator
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=20220608133030.G77ycyRtIYbWyy45Cr2YBdlZKAQu1wZMHailu8J9VRg@z \
--to=balejk@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).