From: <rsbecker@nexbridge.com>
To: "'Junio C Hamano'" <gitster@pobox.com>, <git@vger.kernel.org>
Cc: "'Linux Kernel'" <linux-kernel@vger.kernel.org>,
<git-packagers@googlegroups.com>
Subject: [Test Failures] Git v2.37.1 (was RE: [ANNOUNCE] Git v2.37.1 and others)
Date: Wed, 13 Jul 2022 08:11:06 -0400 [thread overview]
Message-ID: <01af01d896b1$a48e32f0$edaa98d0$@nexbridge.com> (raw)
In-Reply-To: <xmqqv8s2fefi.fsf@gitster.g>
On July 12, 2022 1:07 PM, Junio C Hamano wrote:
>Git v2.37.1, together with v2.30.5, v2.31.4, v2.32.3, v2.33.4, v2.34.4, v2.35.4, and
>v2.36.2 for older maintenance tracks, are now available at the usual places.
>
>These are to address CVE-2022-29187, where the fixes in v2.36.1 and below to
>address CVE-2022-24765 released earlier may not have been complete.
Following are net new test failures with 2.37.1 compared with 2.37.0 are as follows on NonStop ia64 and x86 platforms:
t5516-fetch-push subtests 53, 113
t5545-push-options subtest 9
t5601-clone subtest 8
t7502-commit-porcelain subtests 20-26, 29-33, 42-47
t7528-signed-commit-ssh subtests 4, 5
I am investigating, but as it stands, we cannot package this release for our platform at this time.
Sincerely,
Randall
next prev parent reply other threads:[~2022-07-13 12:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 17:06 [ANNOUNCE] Git v2.37.1 and others Junio C Hamano
2022-07-13 12:11 ` rsbecker [this message]
2022-07-13 14:23 ` [Test Failures] Git v2.37.1 (was RE: [ANNOUNCE] Git v2.37.1 and others) rsbecker
2022-07-14 2:10 ` rsbecker
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='01af01d896b1$a48e32f0$edaa98d0$@nexbridge.com' \
--to=rsbecker@nexbridge.com \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@vger.kernel.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.
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.