public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nscd/29605] Regression in NSCD backend of getaddrinfo
Date: Mon, 26 Sep 2022 18:15:24 +0000 [thread overview]
Message-ID: <bug-29605-131-kZ4h5jXCkG@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29605-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29605
--- Comment #7 from Sam James <sam at gentoo dot org> ---
(In reply to Holger Hoffstätte from comment #6)
> (In reply to Siddhesh Poyarekar from comment #5)
> > Holger, do you have a vm where I can login and debug this? I'm unable to
> > reproduce this locally on Fedora with a built nscd.
>
> No, I cannot provide a VM unfortunately. I was afraid this would happen as
> Gentoo's glibc has assorted patches post-release (see #29607 for a link) and
> I don't know why/how they were chosen; I'm just a (contributing) user. It
> might well be a screwup with those patches.
>
We don't really apply anything notable in Gentoo. You can try USE=vanilla if in
doubt.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-09-26 18:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 11:19 [Bug nscd/29605] New: " joerg at bec dot de
2022-09-23 12:19 ` [Bug nscd/29605] " fweimer at redhat dot com
2022-09-23 17:55 ` siddhesh at sourceware dot org
2022-09-23 20:22 ` joerg at bec dot de
2022-09-25 11:05 ` holger@applied-asynchrony.com
2022-09-26 13:35 ` siddhesh at sourceware dot org
2022-09-26 17:57 ` siddhesh at sourceware dot org
2022-09-26 18:03 ` sam at gentoo dot org
2022-09-26 18:13 ` holger@applied-asynchrony.com
2022-09-26 18:15 ` sam at gentoo dot org [this message]
2022-09-26 19:18 ` holger@applied-asynchrony.com
2022-09-26 19:21 ` siddhesh at sourceware dot org
2022-09-28 16:47 ` cvs-commit at gcc dot gnu.org
2022-09-28 16:48 ` siddhesh at sourceware dot org
2022-09-28 16:49 ` cvs-commit at gcc dot gnu.org
2024-01-08 11:11 ` camila.camargodematos at canonical dot com
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=bug-29605-131-kZ4h5jXCkG@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).