Github messages for voidlinux
 help / color / mirror / Atom feed
From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: ncurses-libs: provide libncurses.so.5
Date: Mon, 27 Jul 2020 04:08:01 +0200	[thread overview]
Message-ID: <20200727020801.XMt9cF_gGLhxkb-RfWdbFANIPOlWsX-nIDpYl3sfwcA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23862@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 730 bytes --]

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/23862#issuecomment-664081324

Comment:
the whole thing with void previously shipping the symlinks was xtraeme's misunderstanding of how ABI compat in ncurses works, I believe - they're still two distinct ABIs and there's no way to have them at once - if the symlink works for you you're probably just not running into the case where things changed, or you're getting an ABI mismatch subtle enough that it doesn't show

unfortunate about the LSI 1078, I have a friend with a Dell server that had the same PERC, and we solved it with me giving him one of my LSI SAS2038's and just replacing the thing, thing just wasn't flashable...

  parent reply	other threads:[~2020-07-27  2:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27  0:54 [PR PATCH] " gt7-void
2020-07-27  1:25 ` ahesford
2020-07-27  1:25 ` [PR PATCH] [Closed]: " ahesford
2020-07-27  1:42 ` q66
2020-07-27  1:44 ` q66
2020-07-27  1:48 ` q66
2020-07-27  2:01 ` gt7-void
2020-07-27  2:08 ` q66 [this message]
2020-07-27  2:10 ` q66
2020-07-27  2:43 ` gt7-void
2020-07-27  2:51 ` 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=20200727020801.XMt9cF_gGLhxkb-RfWdbFANIPOlWsX-nIDpYl3sfwcA@z \
    --to=q66@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).