From: Barbarossa93 <Barbarossa93@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New packages: vit-2.1.0_1 and python3-tasklib-2.4.3_1
Date: Thu, 13 Jan 2022 01:50:49 +0100 [thread overview]
Message-ID: <20220113005049.qIPcLYK6HLFWtDrloe5vuBd8COZgeRTPnFG-iesNBEI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35016@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
New comment by Barbarossa93 on void-packages repository
https://github.com/void-linux/void-packages/pull/35016#issuecomment-1011599530
Comment:
Unfortunately I'm stuck with the vit package. I'm getting an error that the terminfo database can't be found and I'm unsure of how to specify it. Some googling seems to indicate defining the TERMINFO env variable, but I'm sure of how to do that here.
next prev parent reply other threads:[~2022-01-13 0:50 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 18:37 [PR PATCH] New package: python3-tasklib-2.4.3_1 Barbarossa93
2022-01-12 18:41 ` [PR PATCH] [Updated] " Barbarossa93
2022-01-12 18:46 ` Barbarossa93
2022-01-12 18:52 ` Barbarossa93
2022-01-12 18:59 ` Barbarossa93
2022-01-12 19:01 ` Barbarossa93
2022-01-12 19:06 ` Barbarossa93
2022-01-12 19:09 ` Barbarossa93
2022-01-12 19:13 ` Barbarossa93
2022-01-12 19:21 ` Barbarossa93
2022-01-12 19:33 ` Barbarossa93
2022-01-12 19:36 ` Barbarossa93
2022-01-12 19:39 ` Barbarossa93
2022-01-12 19:40 ` Barbarossa93
2022-01-12 20:57 ` Barbarossa93
2022-01-12 21:06 ` [PR REVIEW] " paper42
2022-01-12 21:06 ` paper42
2022-01-12 21:09 ` [PR PATCH] [Updated] " Barbarossa93
2022-01-12 21:10 ` [PR REVIEW] " Barbarossa93
2022-01-12 21:13 ` Barbarossa93
2022-01-12 21:14 ` Barbarossa93
2022-01-12 21:15 ` paper42
2022-01-12 21:19 ` [PR PATCH] [Updated] " Barbarossa93
2022-01-12 21:19 ` Barbarossa93
2022-01-12 21:21 ` [PR REVIEW] " paper42
2022-01-12 21:25 ` [PR PATCH] [Updated] " Barbarossa93
2022-01-12 21:28 ` [PR REVIEW] " paper42
2022-01-12 21:29 ` Barbarossa93
2022-01-12 21:29 ` Barbarossa93
2022-01-12 21:33 ` [PR PATCH] [Updated] " Barbarossa93
2022-01-12 21:37 ` Barbarossa93
2022-01-12 21:38 ` [PR REVIEW] " ahesford
2022-01-12 21:42 ` ahesford
2022-01-12 21:42 ` [PR PATCH] [Updated] " Barbarossa93
2022-01-12 21:44 ` Barbarossa93
2022-01-12 21:48 ` [PR REVIEW] " Barbarossa93
2022-01-12 21:48 ` Barbarossa93
2022-01-12 21:58 ` [PR PATCH] [Updated] " Barbarossa93
2022-01-12 23:23 ` Barbarossa93
2022-01-12 23:26 ` [PR PATCH] [Updated] New packages: vit-2.1.0_1 and python3-tasklib-2.4.3_1 Barbarossa93
2022-01-12 23:31 ` Barbarossa93
2022-01-12 23:40 ` Barbarossa93
2022-01-13 0:50 ` Barbarossa93 [this message]
2022-01-13 0:57 ` Barbarossa93
2022-01-13 18:09 ` [PR PATCH] [Updated] " Barbarossa93
2022-01-13 19:30 ` Barbarossa93
2022-01-14 12:02 ` [PR REVIEW] " paper42
2022-01-14 12:02 ` paper42
2022-01-14 12:02 ` paper42
2022-01-14 13:13 ` [PR PATCH] [Updated] " Barbarossa93
2022-01-14 13:14 ` [PR REVIEW] " Barbarossa93
2022-01-14 13:27 ` [PR PATCH] [Updated] " Barbarossa93
2022-01-14 15:10 ` [PR PATCH] [Merged]: New packages: vit-2.1.0 and python3-tasklib-2.4.3 paper42
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=20220113005049.qIPcLYK6HLFWtDrloe5vuBd8COZgeRTPnFG-iesNBEI@z \
--to=barbarossa93@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).