From: lee2sman <lee2sman@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Keybase client cert error. Might need new package build instead of just an update.
Date: Sun, 17 Mar 2024 22:19:18 +0100 [thread overview]
Message-ID: <20240317211918.2B1DC2D1BE@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48036@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 544 bytes --]
New comment by lee2sman on void-packages repository
https://github.com/void-linux/void-packages/issues/48036#issuecomment-2002620546
Comment:
Well they fixed the Windows, Mac and Debian/Ubuntu clients (there's also fedora/red hat, arch aur) but they of course don't directly package for Void themselves. I'm not great at packaging and don't work in Go. It looks like some of the Go packages repo names have changed and I can't figure out where these are listed. It messes up when downloading some of the crypto libraries, not found in path.
next prev parent reply other threads:[~2024-03-17 21:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 1:16 [ISSUE] " lee2sman
2024-03-04 12:27 ` BlitDev
2024-03-05 2:53 ` lee2sman
2024-03-17 16:22 ` ar-jan
2024-03-17 21:19 ` lee2sman [this message]
2024-03-18 12:22 ` ar-jan
2024-05-02 19:58 ` lee2sman
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=20240317211918.2B1DC2D1BE@inbox.vuxu.org \
--to=lee2sman@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).