From: Michael J Gruber <michaeljgruber+grubix+git@gmail.com>
To: notmuch@notmuchmail.org
Subject: Re: T040 fails on Fedora 39 rebuild
Date: Thu, 20 Jul 2023 21:33:57 +0200 [thread overview]
Message-ID: <CAA19uiTyB8w6rus3cRwaKHmUpmYwWT3uCd7p+G___i1r-90r6g@mail.gmail.com> (raw)
In-Reply-To: <CAA19uiSz6axecyAahaix3F8Q-MGm=iBzhkTN4Y3=_Bjudf6t5Q@mail.gmail.com>
Am Do., 20. Juli 2023 um 20:54 Uhr schrieb Michael J Gruber
<michaeljgruber+grubix+git@gmail.com>:
>
> Hi there,
>
> funny failures again during the mass rebuild for the (not quite yet)
> upcoming Fedora rebuild. This test passed just a few weeks ago, so the
> failure is related to something else changing. But still it shows that
> the order in which `notmuch config` produces new config can depend on
> something else. It looks a bit like a buffering problem, but what do I
> know ... In any case, this is with notmuch 0.37, and I did not see any
> commit in master which could change that.
>
> I vaguely remember we had g_key_file ordering issues before - maybe in
> another project?
>
> The group comment for the next group is written too early, or the keys
> for the current group are written too late. This results in a
> functionally equivalent config with "misplaced" comments.
>
> Test still passes on Fedora 38. Glib2 versions are:
>
> 2.76.4-1.fc38
> 2.77.0-6.fc39
In fact, glib2 may come with a fix when 2.77.1 is released:
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3380
I'm not sure we should or can work around 2.77.0's behaviour. (It
might get triggered by the add/remove trick.)
Cheers
Michael
next prev parent reply other threads:[~2023-07-20 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 18:54 T040 fails on Fedora 39 rebuild Michael J Gruber
2023-07-20 19:33 ` Michael J Gruber [this message]
2023-07-21 1:40 ` David Bremner
2023-07-21 5:55 ` Michael J Gruber
[not found] ` <87sf8kk28s.fsf@tethera.net>
2023-08-15 23:53 ` David Bremner
2023-08-16 0:23 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA19uiTyB8w6rus3cRwaKHmUpmYwWT3uCd7p+G___i1r-90r6g@mail.gmail.com \
--to=michaeljgruber+grubix+git@gmail.com \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).