unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Z572 <873216071@qq.com>
Cc: 67332-done@debbugs.gnu.org, guix-devel@gnu.org
Subject: [bug#67332] what is the status of the core-updates now
Date: Tue, 28 Nov 2023 02:59:33 +0100	[thread overview]
Message-ID: <0e4a47d3-0447-3770-3960-ef94739ec488@telenet.be> (raw)
In-Reply-To: <tencent_83D66C333895260BEB0F5B87B37CA664B405@qq.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 783 bytes --]



Op 23-11-2023 om 13:02 schreef Z572:
> 
> Maxime Devos <maximedevos@telenet.be> writes:
> 
>> [[PGP Signed Part:Undecided]]
>>
>>
>> Op 21-11-2023 om 18:21 schreef Maxime Devos:
>>>   > [PATCH] gnu: ephemeralpg: Fix cross-compilation.
>>> There is already a patch for that:
>>> <https://issues.guix.gnu.org/49327#8>
>>> and (a rebased version of) it effectively has already been applied:
>>> <https://issues.guix.gnu.org/49327#150>
> ok, close it.
>>> I guess you could copy it from c-u to master if you don't want to
>>> wait for the c-u merge, but please use the search function at
>>> <https://issues.guix.gnu.org/>:
> 
> what is the status of the core-updates now,it on ci.guix.gnu.org only build
> 'core', is this a configuration error?

I don't know.

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 929 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]

  reply	other threads:[~2023-11-28  2:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <408e7447-bca3-7c1f-d1f3-7c083e9b3deb@telenet.be>
     [not found] ` <542716a2-c02f-347f-bcbe-a1e21b22ffff@telenet.be>
     [not found]   ` <877cm8d5jc.fsf@qq.com>
2023-11-23 12:02     ` bug#67332: what is the status of the core-updates now Z572 via Guix-patches via
2023-11-28  1:59       ` Maxime Devos [this message]
2023-12-04  1:21         ` Maxim Cournoyer

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=0e4a47d3-0447-3770-3960-ef94739ec488@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=67332-done@debbugs.gnu.org \
    --cc=873216071@qq.com \
    --cc=guix-devel@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).