From: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Christopher Baines <guix@cbaines.net>, 67570-done@debbugs.gnu.org
Subject: [bug#67570] [PATCH] gnu: go-golang-org-x-sys: Update to 0.8.0.
Date: Mon, 08 Jan 2024 20:13:59 +0300 [thread overview]
Message-ID: <87eder4ujs.fsf@gmail.com> (raw)
In-Reply-To: <87frz9ci8s.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 07 Jan 2024 15:48:03 +0100")
[-- Attachment #1: Type: text/plain, Size: 601 bytes --]
Hello,
as far as I remember, one of the packages that was failing is
"go-github-com-charmbracelet-glamour" -- this is not directly related to
"go-golang-org-x-sys" as the package build has started failing before my
patch, but anyways. Yesterday I sent a patch that should fix
"go-github-com-charmbracelet-glamour" build:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=68311
- avp
--
Artyom "avp" Poptsov <poptsov.artyom@gmail.com>
Home page: https://memory-heap.org/~avp/
CADR Hackerspace co-founder: https://cadrspace.ru/
GPG: D0C2 EAC1 3310 822D 98DE B57C E9C5 A2D9 0898 A02F
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
prev parent reply other threads:[~2024-01-08 17:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 19:08 [bug#67570] [PATCH] gnu: kubo: Fix build Artyom V. Poptsov
2023-12-02 10:04 ` Ludovic Courtès
2023-12-09 8:22 ` [bug#67570] [PATCH] gnu: go-golang-org-x-sys: Update to 0.8.0. (was: [PATCH] gnu: kubo: Fix build.) Artyom V. Poptsov
2023-12-10 21:22 ` [bug#67570] [PATCH] gnu: go-golang-org-x-sys: Update to 0.8.0 Ludovic Courtès
2023-12-29 9:55 ` Artyom V. Poptsov
2024-01-07 14:48 ` bug#67570: " Ludovic Courtès
2024-01-07 15:34 ` [bug#67570] " Christopher Baines
2024-01-08 17:02 ` Ludovic Courtès
2024-01-08 17:13 ` Artyom V. Poptsov [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eder4ujs.fsf@gmail.com \
--to=poptsov.artyom@gmail.com \
--cc=67570-done@debbugs.gnu.org \
--cc=guix@cbaines.net \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).