From: Kousik Sanagavarapu <five231003@gmail.com>
To: nsengiyumvawilberforce@gmail.com
Cc: git@vger.kernel.org, chriscool@tuxfamily.org,
hariom18599@gmail.com, jaydeepjd.8914@gmail.com,
gitster@pobox.com
Subject: Re: [PATCH v5 1/1] ref-filter: add new "signature" atom
Date: Fri, 28 Apr 2023 23:59:25 +0530 [thread overview]
Message-ID: <20230428182925.14975-1-five231003@gmail.com> (raw)
In-Reply-To: <20230311210607.64927-2-nsengiyumvawilberforce@gmail.com>
Nsengiyumva Wilberforce <nsengiyumvawilberforce@gmail.com> writes:
> +test_expect_success GPG 'test bare signature atom' '
I think this test is failing on CI because, as Junio said, there
are different versions of gpg coming into play here. In particular,
this test is failing on (according to the logs) linux32 (daald/ubuntu32:xenial).
The version of GPG that xenial can use is at a maximum v1.4.20 (this is
evident here https://packages.ubuntu.com/xenial/allpackages). But
according the code in lib-gpg.sh, we should be able to handle any GPG
version, except for v1.0.6.
Looking at the logs that Junio posted, I think that the cuplrit is
> + grep -v "checking the trustdb" out_orig >out &&
> + head -3 out >expected &&
> + tail -1 out >>expected &&
but I'm not really sure. So I would really be grateful if you could
explain this hack to me, the one you mentioned in the cover-letter.
Thanks
next prev parent reply other threads:[~2023-04-28 18:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 0:55 [PATCH] ref-filter: add new atom "signature" atom nsengaw4c via GitGitGadget
2022-12-27 2:20 ` Junio C Hamano
2023-01-02 4:49 ` NSENGIYUMVA WILBERFORCE
2023-01-02 8:37 ` Christian Couder
2023-01-03 0:58 ` Junio C Hamano
[not found] ` <CA+PPyiGd0-AiwhPa5e+fDdA9RybS+c5XeOYm5yycCZco3VHAxg@mail.gmail.com>
2023-01-08 15:21 ` NSENGIYUMVA WILBERFORCE
2022-12-27 6:11 ` Jeff King
2023-01-02 6:34 ` NSENGIYUMVA WILBERFORCE
2023-01-10 0:52 ` [PATCH v3 0/1] ref-filter: add new " Nsengiyumva Wilberforce
2023-01-10 0:52 ` [PATCH v3 1/1] " Nsengiyumva Wilberforce
2023-01-16 17:38 ` [PATCH v4 0/1] " Nsengiyumva Wilberforce
2023-01-16 17:38 ` [PATCH v4 1/1] " Nsengiyumva Wilberforce
2023-03-11 21:06 ` [PATCH v5 0/1] " Nsengiyumva Wilberforce
2023-03-11 21:06 ` [PATCH v5 1/1] " Nsengiyumva Wilberforce
2023-03-14 22:51 ` Junio C Hamano
2023-04-28 18:29 ` Kousik Sanagavarapu [this message]
2023-04-29 18:37 ` Kousik Sanagavarapu
2023-01-26 21:07 ` [PATCH v4 0/1] " Junio C Hamano
2023-01-10 9:13 ` [PATCH v3 " Christian Couder
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: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230428182925.14975-1-five231003@gmail.com \
--to=five231003@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hariom18599@gmail.com \
--cc=jaydeepjd.8914@gmail.com \
--cc=nsengiyumvawilberforce@gmail.com \
/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://80x24.org/mirrors/git.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).