all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Andy Tai <atai@atai.org>
Cc: 59093@debbugs.gnu.org, 61134@debbugs.gnu.org
Subject: [bug#61134] [bug#59093] [PATCH] Add motif and xnedit
Date: Wed, 01 Feb 2023 11:08:41 +0100	[thread overview]
Message-ID: <86zg9xu28m.fsf@gmail.com> (raw)
In-Reply-To: <CAJsg1E-kT9Nr626adUzi4OkCuLSvQp0fB+5vnP6FH3-NDPHSWg@mail.gmail.com>

Hi Andy,

On Tue, 31 Jan 2023 at 10:12, Andy Tai <atai@atai.org> wrote:
> To clarify, when I mentioned Guix QA shows failure, Guiox QA was
> showing "failure" trying to queue the issue to build, not that Gux QA
> was showing some build log with the patch failing to build in some
> way.
>
> So I don't know if you are saying people should look at Guix QA
> sources and help to fix that.  That is possible, of course, but people
> contributing to Guix patches may have no background at all at how Guix
> QA works.

I have understood the first time. :-)

I wrote: «It appears to me better to point the issues and then maybe fix
them instead of bypassing them.  My 2 cents.»

I am not saying that you should fix issues with QA, obviously not.
Instead, I am proposing that if you notice something unexpected with QA,
you should report it and not silently bypass it.

“Report it” means for example drop an email to guix-devel or open a bug
or roam on #guix and tell.  I do not know what is the best and it does
not mean that the issue about QA will be fixed.  It just helps in
improving the tools, IMHO.

Well, for what it is worth, I am trying to say that silently close and
reopen another ticket because QA does not behave as expected is a
short-term hack – and yes it is often necessary to have the task done
now :-) – but by silently closing it does not help for the longer term.

Thanks for your contributions and taking the time to discuss how we
could collectively improve Guix. :-)

Cheers,
simon




      reply	other threads:[~2023-02-01 10:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJsg1E9pb+vfoFdzxXNnDukX8tgwBBKJwmQwYXfUVqdTWnJMbA@mail.gmail.com>
2023-01-30 12:44 ` [bug#59093] [PATCH] Add motif and xnedit Simon Tournier
2023-01-30 15:35   ` Andy Tai
2023-01-31  9:56     ` Simon Tournier
2023-01-31 17:15       ` [bug#61134] " Andy Tai
2023-01-31 18:12         ` Andy Tai
2023-02-01 10:08           ` Simon Tournier [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86zg9xu28m.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=59093@debbugs.gnu.org \
    --cc=61134@debbugs.gnu.org \
    --cc=atai@atai.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.