From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: racket: update to 7.8
Date: Wed, 21 Oct 2020 03:39:04 +0200 [thread overview]
Message-ID: <20201021013904.I69gks_7-ccUdaT6nDDSwiN7xDUyH5lUg8afRLQZzvg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25349@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/25349#issuecomment-713236810
Comment:
> I'm not sure my git skills are sufficient here. I assume I would need to cherry-pick (something I haven't attempted before). I could probably manually amend the commit quicker.
You can apply it manually, and `curl https://github.com/ericonr/void-packages/commit/beb2ac41143b2cd277cab21c005e067449cc49ac.patch | git apply` should also work, unless there are conflicts :P
> I haven't had this issue, but probably because I (for other reasons) already have libressl-devel installed?
exactly! It might be best to add `libressl-devel` as a `depends`, assuming people use `raco` often. The upstream issue has been open for a looong time: https://github.com/racket/racket/issues/1096
next prev parent reply other threads:[~2020-10-21 1:39 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-05 1:23 [PR PATCH] " emacsomancer
2020-10-15 6:01 ` ericonr
2020-10-20 18:37 ` ericonr
2020-10-21 1:22 ` emacsomancer
2020-10-21 1:22 ` emacsomancer
2020-10-21 1:39 ` ericonr [this message]
2020-10-21 2:32 ` emacsomancer
2020-10-21 4:41 ` ericonr
2020-10-21 19:15 ` [PR PATCH] [Updated] " emacsomancer
2020-10-21 19:17 ` emacsomancer
2020-10-25 17:42 ` emacsomancer
2020-11-11 23:15 ` emacsomancer
2020-11-24 22:14 ` racket: update to 7.9 ericonr
2020-11-25 19:33 ` [PR PATCH] [Updated] " emacsomancer
2020-11-25 19:34 ` emacsomancer
2020-11-25 19:54 ` ericonr
2020-11-25 20:13 ` emacsomancer
2020-11-25 20:14 ` [PR REVIEW] " ericonr
2020-11-25 20:26 ` emacsomancer
2021-01-25 13:53 ` ericonr
2021-02-14 3:14 ` [PR PATCH] [Updated] " emacsomancer
2021-10-27 15:25 ` racket: update to 8.0 sleibrock
2021-10-27 18:24 ` emacsomancer
2021-10-28 4:04 ` ericonr
2021-10-28 15:44 ` emacsomancer
2021-10-28 21:10 ` leahneukirchen
2021-10-28 21:16 ` emacsomancer
2021-10-28 22:16 ` leahneukirchen
2021-10-29 13:34 ` [PR PATCH] [Closed]: " leahneukirchen
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=20201021013904.I69gks_7-ccUdaT6nDDSwiN7xDUyH5lUg8afRLQZzvg@z \
--to=ericonr@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).