unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: Mathieu Othacehe <othacehe@gnu.org>, 49437@debbugs.gnu.org
Subject: [bug#49437] [PATCH core-updates] build-system/qt: Fix build failures when
Date: Tue, 4 Apr 2023 20:59:13 +0200	[thread overview]
Message-ID: <92014e75-5007-bcdd-93e0-9565df2660a2@telenet.be> (raw)
In-Reply-To: <87h6u4481q.fsf_-_@gmail.com>


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

Op 29-03-2023 om 04:15 schreef Maxim Cournoyer:
> Hi Maxime,
> 
> I hope you are doing well.
> 
> [...]
> 
> core-updates is pretty "hot" at the moment, so it may be a good time to
> test.
> 
> On the other hand, there aren't that many Qt packages, so it could also
> go to staging IMO.  And if it only touches cross-compilation drv,
> perhaps it's good for master too?
> 
> It just needs testing.

I am not participating in Guix development anymore, except perhaps for 
bug reports and for when Guix intersects GNUnet, and currently it 
appears a permanent decision.

Greetings,
Maxime.

[-- 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-04-04 19:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06 11:25 [bug#49437] [PATCH core-updates] build-system/qt: Fix build failures when Maxime Devos
2021-07-08 14:45 ` Mathieu Othacehe
2021-07-08 17:51   ` Maxime Devos
2021-07-08 19:37     ` Mathieu Othacehe
2021-07-08 20:59       ` Maxime Devos
2021-09-23  3:53         ` Maxim Cournoyer
2021-10-03  8:56           ` Maxime Devos
2023-03-29  2:15             ` Maxim Cournoyer
2023-04-04 18:59               ` Maxime Devos [this message]
2023-04-07 21:15                 ` Maxim Cournoyer
2024-01-20 21:11     ` bug#49437: " 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=92014e75-5007-bcdd-93e0-9565df2660a2@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=49437@debbugs.gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=othacehe@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).