From: lfdebrux <lfdebrux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: SHA256 mismatch for python-2.7.18.5
Date: Sun, 10 Jul 2022 17:44:37 +0200 [thread overview]
Message-ID: <20220710154437.ih7zwu5tbq6sbgp5gg3dLeU3nr6XN9Lwk4ShJzD5pdA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37978@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
New comment by lfdebrux on void-packages repository
https://github.com/void-linux/void-packages/issues/37978#issuecomment-1179751819
Comment:
I'm not sure how this happened, but I note that the last change to the python template (https://github.com/void-linux/void-packages/commit/1c93498810ba791da5d01d89913a883f0bce6cdf) was 12 days ago, while the relevant tag on the upstream repo (https://github.com/ActiveState/cpython/releases/tag/v2.7.18.5) was according to GitHub updated 10 days ago.
So maybe the release was updated for some reason? No idea how to check why it was though, or whether it was supposed to be.
next prev parent reply other threads:[~2022-07-10 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 15:42 [ISSUE] " lfdebrux
2022-07-10 15:44 ` lfdebrux [this message]
2022-07-11 3:20 ` sgn
2022-07-11 3:22 ` sgn
2022-07-11 3:22 ` [ISSUE] [CLOSED] " sgn
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=20220710154437.ih7zwu5tbq6sbgp5gg3dLeU3nr6XN9Lwk4ShJzD5pdA@z \
--to=lfdebrux@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).