unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Artyom V. Poptsov" <poptsov.artyom@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 67570@debbugs.gnu.org
Subject: [bug#67570] [PATCH] gnu: go-golang-org-x-sys: Update to 0.8.0.
Date: Fri, 29 Dec 2023 12:55:22 +0300	[thread overview]
Message-ID: <87tto1z62d.fsf@gmail.com> (raw)
In-Reply-To: <875y154us6.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 10 Dec 2023 22:22:49 +0100")

[-- Attachment #1: Type: text/plain, Size: 611 bytes --]

Hello!

> This is being built:
>
>   https://qa.guix.gnu.org/issue/67570

So what is the status of this?  Last time I checked the link the
information about the build was gone and it's not obvious for me how to
get this info again.

Before I saw that some new packages were failing, I'd like to check if I
can fix them.

Could you provide a new link or the info itself?

Thanks!

- 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 --]

  reply	other threads:[~2023-12-29  9:56 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 [this message]
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

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=87tto1z62d.fsf@gmail.com \
    --to=poptsov.artyom@gmail.com \
    --cc=67570@debbugs.gnu.org \
    --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).