From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
"debian-alpha@lists.debian.org" <debian-alpha@lists.debian.org>
Cc: gentoo-alpha@lists.gentoo.org,
GNU C Library <libc-alpha@sourceware.org>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: Update on the glibc segfault issue on Alpha
Date: Thu, 5 Jan 2023 12:25:02 +0100 [thread overview]
Message-ID: <6dda443f-3014-6170-6ffe-451b8928a96d@physik.fu-berlin.de> (raw)
In-Reply-To: <9d2cac45-b81b-fa5f-e0e7-87396645bcfe@linaro.org>
Hi Adhemveral!
On 1/4/23 13:00, Adhemerval Zanella Netto wrote:
>> I can confirm that this patch fixes the problem for me. I have uploaded a manually built glibc
>> package with the patch applied to Debian »unreleased« so that the buildds can resume building
>> packages again.
>>
>> Would it be possible to backport this patch to 2.36 once it has been merged with the current
>> development tree? The reason is that I don't think that Debian is going to switch to anything
>> beyond 2.36 anytime soon due to the upcoming feature freeze in January.
>
> I have sent a more detailed patch [1] and I will probably backport to all affected releases
> once it is accepted.
Great, thanks a lot! This means, the fix will eventually be available in Debian and we won't have
to carry the patch for a long time.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer
`. `' Physicist
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
prev parent reply other threads:[~2023-01-05 11:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 11:44 John Paul Adrian Glaubitz
2023-01-02 17:37 ` John Paul Adrian Glaubitz
2023-01-03 12:09 ` Adhemerval Zanella Netto
2023-01-03 13:29 ` Florian Weimer
2023-01-03 13:47 ` Adhemerval Zanella Netto
2023-01-04 9:25 ` John Paul Adrian Glaubitz
2023-01-04 12:00 ` Adhemerval Zanella Netto
2023-01-05 11:25 ` John Paul Adrian Glaubitz [this message]
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=6dda443f-3014-6170-6ffe-451b8928a96d@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=adhemerval.zanella@linaro.org \
--cc=debian-alpha@lists.debian.org \
--cc=fweimer@redhat.com \
--cc=gentoo-alpha@lists.gentoo.org \
--cc=libc-alpha@sourceware.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 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).