From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: glibc: neutralise supply chain attack
Date: Thu, 05 Jan 2023 13:45:49 +0100 [thread overview]
Message-ID: <20230105124549.w8T2VfSCHnT3o16Jen3nH2E-rN2aJ1JlXn9QB8LWIWM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41469@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/41469#issuecomment-1372170752
Comment:
I was under the impression that the plan was to swap it out to https://repo-default.voidlinux.org/distfiles/ once the infra people around to it. That is still my preference.
I'm not sure relying on runtime generated patches generated from a mirror not affiliated GNU (or us for that matter) really does much for us aside from breaking build when github or git changes the way patches generate (or if the mirror goes down).
The https://git.vuxu.org/mirror/glibc/ was created to be used in the PR but I didn't use it because at the time the snapshots generated broken tarballs and took forever to download. Not sure about now, but trying to download a snapshot resulted in my getting an error: `Sorry, the page you are looking for is currently unavailable.
Please try again later.`
next prev parent reply other threads:[~2023-01-05 12:45 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 11:46 [PR PATCH] " sgn
2023-01-05 12:30 ` [PR PATCH] [Updated] " sgn
2023-01-05 12:45 ` oreo639 [this message]
2023-01-05 12:47 ` oreo639
2023-01-05 12:48 ` oreo639
2023-01-05 12:49 ` oreo639
2023-01-05 12:49 ` oreo639
2023-01-05 12:51 ` oreo639
2023-01-05 12:55 ` oreo639
2023-01-05 12:55 ` oreo639
2023-01-05 12:56 ` oreo639
2023-01-05 13:05 ` oreo639
2023-01-05 13:06 ` oreo639
2023-01-05 13:12 ` oreo639
2023-01-05 13:13 ` oreo639
2023-01-05 13:15 ` oreo639
2023-01-05 13:16 ` oreo639
2023-01-05 13:17 ` oreo639
2023-01-05 13:22 ` oreo639
2023-01-05 14:10 ` [PR PATCH] [Updated] " sgn
2023-01-05 14:11 ` sgn
2023-01-05 17:41 ` CameronNemo
2023-01-05 21:00 ` leahneukirchen
2023-01-05 22:08 ` oreo639
2023-01-05 22:13 ` oreo639
2023-01-05 22:52 ` oreo639
2023-04-06 1:51 ` github-actions
2023-04-21 1:52 ` [PR PATCH] [Closed]: " github-actions
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=20230105124549.w8T2VfSCHnT3o16Jen3nH2E-rN2aJ1JlXn9QB8LWIWM@z \
--to=oreo639@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).