From: ailiop-git <ailiop-git@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [NOMERGE] glibc: update to 2.31.
Date: Thu, 30 Apr 2020 14:35:18 +0200 [thread overview]
Message-ID: <20200430123518.ENOOnlZ6EItPveH-Dap1SJyD0WRm6rDnRI4LBCukhtQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18737@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 652 bytes --]
New comment by ailiop-git on void-packages repository
https://github.com/void-linux/void-packages/pull/18737#issuecomment-621805733
Comment:
thanks, I haven't had the time to look more into this, but one of the issues is that we don't know which other packages this change may break.
One idea could be to scan all binaries on the repo side by dumping their debug symbols and checking for usage of nanosleep/seccomp/prctl, and narrow it down to those pkgs so that we can check them before upgrading.
There's also the second issue mentioned above with the gcc fixincludes and statx headers, that I haven't check yet if it was resolved upstream.
next prev parent reply other threads:[~2020-04-30 12:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 11:21 [PR PATCH] " voidlinux-github
2020-02-02 15:39 ` voidlinux-github
2020-02-02 17:10 ` voidlinux-github
2020-02-02 18:37 ` [NOMERGE] " voidlinux-github
2020-02-02 18:53 ` voidlinux-github
2020-04-30 11:25 ` schnitzeltony
2020-04-30 12:15 ` pullmoll
2020-04-30 12:35 ` ailiop-git [this message]
2020-04-30 15:53 ` schnitzeltony
2020-09-27 18:01 ` kernle32dll
2020-12-05 20:42 ` ericonr
2021-01-05 21:34 ` leahneukirchen
2021-01-05 21:34 ` [PR PATCH] [Closed]: " leahneukirchen
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=20200430123518.ENOOnlZ6EItPveH-Dap1SJyD0WRm6rDnRI4LBCukhtQ@z \
--to=ailiop-git@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).