From: Jeff King <peff@peff.net>
To: Carlo Arenas <carenas@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Fabian Stelzer <fs@gigacodes.de>,
git@vger.kernel.org, git-packagers@googlegroups.com
Subject: Re: [ANNOUNCE] Git v2.34.0-rc2
Date: Wed, 10 Nov 2021 04:35:31 -0500 [thread overview]
Message-ID: <YYuSYz+XFWmBkIiz@coredump.intra.peff.net> (raw)
In-Reply-To: <CAPUEspjzs0ZvDGUwp=XYxdHb_t+1yx0C1epaNhhiAn6SsPeidQ@mail.gmail.com>
On Wed, Nov 10, 2021 at 01:15:52AM -0800, Carlo Arenas wrote:
> On Wed, Nov 10, 2021 at 12:22 AM Jeff King <peff@peff.net> wrote:
> >
> > On Wed, Nov 10, 2021 at 12:11:12AM -0800, Carlo Arenas wrote:
> >
> > > On Tue, Nov 9, 2021 at 10:02 PM Jeff King <peff@peff.net> wrote:
> > >
> > > > - we're not really testing the desired behavior, just looking for a
> > > > known-problem. The segfault may get fixed but we'd still have other
> > > > bugs.
> > >
> > > This openssh bug was fixed in 8.8 per the release notes; indeed the
> > > fix[1] (which was misapplied but fixed next commit) looks familiar and
> > > it is just a straight up crasher, hence unlikely to cause other
> > > issues.
> >
> > Ah, thanks for digging. I agree that this is a small isolated bug, so
> > the prereq check I showed would be a good test for it.
> >
> > IMHO it's worth doing. It looks like 8.7 is the only affected openssh
> > version, but it is likely to cause confusion right when we release.
>
> It was discussed[1] before, and I think the plan was to at least
> mention the brokenness with 8.7 in the release notes, but guess I
> dropped the ball by not raising it earlier.
Ah, thanks. I looked in the archive, but assumed any mention would have
been more recent (not realizing that Debian's packaging was simply
lagging the upstream releases by quite a bit).
-Peff
next prev parent reply other threads:[~2021-11-10 9:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 0:59 [ANNOUNCE] Git v2.34.0-rc2 Junio C Hamano
2021-11-10 5:41 ` Jeff King
2021-11-10 6:00 ` Jeff King
2021-11-10 8:11 ` Carlo Arenas
2021-11-10 8:22 ` Jeff King
2021-11-10 9:15 ` Carlo Arenas
2021-11-10 9:35 ` Jeff King [this message]
2021-11-10 9:39 ` [PATCH] RelNotes: mention known crasher when ssh signing with OpenSSH 8.7 Carlo Marcelo Arenas Belón
2021-11-10 21:39 ` Junio C Hamano
2021-11-10 22:11 ` Junio C Hamano
2021-11-11 9:16 ` Jeff King
[not found] ` <YY7/peK1EOHtATEI@camp.crustytoothpaste.net>
2021-11-13 0:16 ` Junio C Hamano
2021-11-10 21:49 ` [ANNOUNCE] Git v2.34.0-rc2 Junio C Hamano
2021-11-10 6:35 ` Johannes Altmanninger
2021-11-10 8:22 ` Jeff King
2021-11-10 21:43 ` Junio C Hamano
2021-11-11 12:07 ` Jeff King
2021-11-11 17:32 ` Junio C Hamano
2021-11-11 20:23 ` Jeff King
2021-11-11 20:33 ` Junio C Hamano
2021-11-15 15:06 ` Patrick Steinhardt
2021-11-15 15:27 ` Jeff King
2021-11-15 16:52 ` Jeff King
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=YYuSYz+XFWmBkIiz@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=carenas@gmail.com \
--cc=fs@gigacodes.de \
--cc=git-packagers@googlegroups.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).