From: rubin55 <rubin55@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] Package request: ncurses-libtinfo-libs-32bit
Date: Wed, 01 Feb 2023 00:05:03 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42007@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 667 bytes --]
New issue by rubin55 on void-packages repository
https://github.com/void-linux/void-packages/issues/42007
Description:
### Package name
ncurses-libtinfo
### Package homepage
https://invisible-island.net/ncurses/announce.html
### Description
Ncurses is currently available for Void, and also has a 32bit compatibility package. However, this package misses a libtinfo-libs counterpart like the x86_64 package has.
I would like to run some older, binary software that has all dependencies fulfilled, except a 32bit version of `libtinfo.so.6`
### Does the requested package meet the package requirements?
System
### Is the requested package released?
Yes
next reply other threads:[~2023-01-31 23:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 23:05 rubin55 [this message]
2023-10-03 1:57 ` misuchiru03
2023-10-03 1:58 ` misuchiru03
2023-10-03 2:28 ` classabbyamp
2023-10-09 23:38 ` [ISSUE] [CLOSED] " classabbyamp
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42007@inbox.vuxu.org \
--to=rubin55@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).