From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id gCV2Lw6DuWTavAAASxT56A (envelope-from ) for ; Thu, 20 Jul 2023 20:55:10 +0200 Received: from aspmx1.migadu.com ([2001:41d0:403:4789::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id gKeKLw6DuWT6EwAAauVa8A (envelope-from ) for ; Thu, 20 Jul 2023 20:55:10 +0200 Received: from mail.notmuchmail.org (yantan.tethera.net [IPv6:2a01:4f9:c011:7a79::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 4980E4FEA1 for ; Thu, 20 Jul 2023 20:55:10 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=gmail.com header.s=20221208 header.b="Oj/3iwiB"; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2a01:4f9:c011:7a79::1 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1689879310; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding:list-id:list-help: list-owner:list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=YhHXFj7TH6oN/8BI3qe3NkT777D/z5h4gnAZ0ZmoyD4=; b=M7/y7BRQb9Ompw6E6Zrl1am/9EMqTZknAkq6o71TQXmuPbErn7uQ00RrZLvfkHiOYWrAl+ KmM2lUpom5/33VJUxP8nPEHdIyvzSDrat7JNLPDOiFGrzdel06wB3p3WrIXj1KnUdOUS/n d0lDLFhpaRpZY/KdAHxp/M8tSBlXFMswPXdGWl2PRQ8hGGJh9py5jRQAmzlL+P/ZrzPnb1 Zz6QWKdnWnps3+iOIUk3CnRzao3zS5vTzpCkAKGMXDt7mac2jBxyMONuhqfVNROu/Ti8yQ NmzriBvm7Wm2VjQaruUHh5yv4mHDPpsZpW7sipuTmuZ+q1mvSc7Yho4uJlraYg== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1689879310; a=rsa-sha256; cv=none; b=DTG+ABu5/t8GSpq7L/5AoyPFt+Qqz9VyR+73aSW8tOv7UQuRlYlxIAJrutyU0OOC3qFGtI SaQ2mJ4yDYVBbNBaziC6J3GnVJbfSnes0KVymLqPbTHjktjrq6K1QIfsfvgNGi6rp8Mnpi q1rZdkNPwnQj+Jm7vbcA/85I8HREmeKJzaHZKP7DMN2w5w+iKagK9ikOUOdaIMcqUxl0Zn OcmNPkPeo+p3xU2D8RHzqamnUayP4Q8HV3tZugbvIhA86y2Ocj9gE4Rq9y2guoC5nvQTsA wRMoXn6Bybe48P2+IZoYv/IwA7jLsMK2F4GKGkNQvo66+knch7dT6DJDSo112Q== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=fail ("body hash did not verify") header.d=gmail.com header.s=20221208 header.b="Oj/3iwiB"; spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2a01:4f9:c011:7a79::1 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org; dmarc=fail reason="SPF not aligned (relaxed)" header.from=gmail.com (policy=none) Received: from yantan.tethera.net (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 1C6F25F49F; Thu, 20 Jul 2023 18:55:07 +0000 (UTC) Received: from mail-ej1-x636.google.com (mail-ej1-x636.google.com [IPv6:2a00:1450:4864:20::636]) by mail.notmuchmail.org (Postfix) with ESMTPS id 308B65F38D for ; Thu, 20 Jul 2023 18:55:04 +0000 (UTC) Received: by mail-ej1-x636.google.com with SMTP id a640c23a62f3a-992af8b3b1bso190517566b.1 for ; Thu, 20 Jul 2023 11:55:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1689879303; x=1690484103; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=9cLa3qo/CxNXpTk2Zc0gDeWqh9ukhxJtqGML1T/dIIE=; b=Oj/3iwiBMALP/UWl0XYNSuBobALsSEnu/XF8bg096qWB9fSIEU9UQ53ZEsJ1biiJmC maO3rAqqG4uLYdiIabrx7oGCCk0v92CawXQYq6npPFUoaeK4lgYTTB9zaXaDjA0LH5Kc UPNr3NfIl6xBYlucdCItLZZlnSmYGvS78vCGCqlIwRJ1F0W/qO573DPqiHFZhnt9L83+ blziqq3icxpRPu1Af4M7UHlD48tdW2nEV2CH9rAXkra4Zm7EowonkyeF89r2b0I0lPv2 dmgIf9m9ieoySfWp/Eo0iB/jtB72FcSy0PMm0s8o2FM9xQX3Uho7UtTeO8VXgDaEt+Za MLOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689879303; x=1690484103; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=9cLa3qo/CxNXpTk2Zc0gDeWqh9ukhxJtqGML1T/dIIE=; b=WR+/MMe6rB/sCeGQXhkw28XWHI0S8HrsIvzALCjGwFSsfGj4Sgky35Z57YCJYOg4vg qgClOuI4Ei5ncYgiqZtAsumPgTfUABfPS5wyyUIB7RSj+9LiIby39ZQPcFdDwav5MtrG hXIjZTRD9yINYeKd3AzV15L3w66IrxiFiZNUK3eARpohyqW9JCv0pFrxeKTGNLlBZ+0h xfmXUf9g418swEYOxkxDGVSaqUHUItdeje/hI3QQkXLO4SLoxF9pITrF+if+qF7zeLYU a22VlNqrjiG1rpVveod9YGK2P6kZeO7jFWCN0gbBp5N9O6+JI8xoSyyWS83kqjLlMo9n fVEg== X-Gm-Message-State: ABy/qLbBTcDzqVxnfw1I6Mk/uSn8PkfrWWLU1s/2xUVMKnWZSRVYVAyn xzlSK0RnFsgipJbX3w8eYw0Q97FoyudKZyB92KEUY/f7TexbFg== X-Google-Smtp-Source: APBJJlHdObfOWnmDWVTTPHR/r7MnnbrGtf5JGRA/FpX7imw9OW2SBlD6jScV7urhiNpUcF9xCkev6J0WYiFHk9oaVEo= X-Received: by 2002:a17:906:518b:b0:994:1fee:3065 with SMTP id y11-20020a170906518b00b009941fee3065mr6861020ejk.15.1689879302918; Thu, 20 Jul 2023 11:55:02 -0700 (PDT) MIME-Version: 1.0 From: Michael J Gruber Date: Thu, 20 Jul 2023 20:54:51 +0200 Message-ID: Subject: T040 fails on Fedora 39 rebuild To: notmuch@notmuchmail.org Message-ID-Hash: PUWCY4AWLQON3YC77LJ7YK4X6MA5DZCV X-Message-ID-Hash: PUWCY4AWLQON3YC77LJ7YK4X6MA5DZCV X-MailFrom: michaeljgruber@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.3 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Migadu-Country: DE X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -3.89 X-Spam-Score: -3.89 X-Migadu-Queue-Id: 4980E4FEA1 X-Migadu-Scanner: mx1.migadu.com X-TUID: s/jPKMDjaBkF 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 Cheers Michael ``` T040-setup: Testing "notmuch setup" PASS Notmuch new without a config suggests notmuch setup FAIL Create a new config interactively --- T040-setup.2.config-with-comments 2023-07-20 16:58:16.513709261 +0000 +++ T040-setup.2.new-notmuch-config 2023-07-20 16:58:16.513709261 +0000 @@ -1,7 +1,3 @@ -# .notmuch-config - Configuration file for the notmuch mail system -# -# For more information about notmuch, see https://notmuchmail.org - # Database configuration # # The only value supported here is 'path' which should be the top-level @@ -11,8 +7,6 @@ # configured here named ".notmuch". # [database] -path=/path/to/maildir - # User configuration # # Here is where you can let notmuch know how you would like to be @@ -28,11 +22,8 @@ # recipient list of replies, and will set the From address based on the # address to which the original email was addressed. # +path=/path/to/maildir [user] -name=Test Suite -primary_email=test.suite@example.com -other_email=another.suite@example.com - # Configuration for "notmuch new" # # The following options are supported here: @@ -47,9 +38,10 @@ # names will be ignored, independent of its depth/location # in the mail store. # +name=Test Suite +primary_email=test.suite@example.com +other_email=another.suite@example.com [new] -tags=foo;bar; - # Search configuration # # The following option is supported here: @@ -59,9 +51,8 @@ # search results by default. Using an excluded tag in a # query will override that exclusion. # +tags=foo;bar; [search] -exclude_tags=baz - # Maildir compatibility configuration # # The following option is supported here: @@ -83,4 +74,5 @@ # and update tags, while the "notmuch tag" and "notmuch restore" # commands will notice tag changes and update flags in filenames # +exclude_tags=baz [maildir] PASS setup consistent with config-set for single items ```