From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Vivien Kraus <vivien@planete-kraus.eu>, 69756@debbugs.gnu.org
Cc: rg@raghavgururajan.name, maxim.cournoyer@gmail.com
Subject: [bug#69756] [PATCH gnome-team 1/1] gnu: libgda: Disable failing tests.
Date: Tue, 12 Mar 2024 22:12:38 +0100 [thread overview]
Message-ID: <ff03f9f24464ed908b88e1d7267c7d6eaaab3b32.camel@gmail.com> (raw)
In-Reply-To: <d35996fbccdaa39075774727489939847ab73223.camel@planete-kraus.eu>
Am Dienstag, dem 12.03.2024 um 19:03 +0100 schrieb Vivien Kraus:
> Le mardi 12 mars 2024 à 18:59 +0100, Liliana Marie Prikler a écrit :
> > > +Has been difficutl to reproduce the problem when this test
> > > +is running in Ci, so disabling until we can re-implement it
> > > +is the better choice
> > I assume the spelling is [sic]?
> Correct, I would consider it rude to reword a commit that was
> accepted by another project. Although it’s the first time I’m facing
> this situation, so maybe the etiquette says something different.
Well, we indeed prefer upstreamed patches, but some upstreams also add
their fixes on top of such patches, which we'd have to incorporate as
well in this case. In the case of libgda, it does however seem that
this is the newest modification to those files, so my worries were
somewhat unfounded.
Cheers
next prev parent reply other threads:[~2024-03-12 21:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 17:13 [bug#69756] [PATCH gnome-team 0/1] Fix libgda for gnome-team Vivien Kraus via Guix-patches via
2024-03-12 17:12 ` [bug#69756] [PATCH gnome-team 1/1] gnu: libgda: Disable failing tests Vivien Kraus via Guix-patches via
2024-03-12 17:59 ` Liliana Marie Prikler
2024-03-12 18:03 ` Vivien Kraus via Guix-patches via
2024-03-12 21:12 ` Liliana Marie Prikler [this message]
2024-03-16 11:00 ` bug#69756: " Christopher Baines
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=ff03f9f24464ed908b88e1d7267c7d6eaaab3b32.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=69756@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=rg@raghavgururajan.name \
--cc=vivien@planete-kraus.eu \
/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).