From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: poco: update to build with openssl3
Date: Mon, 30 Jan 2023 22:58:54 +0100 [thread overview]
Message-ID: <20230130215854.lMh7CSjkuBW_fNBqL6xOmhCBlhbdiRpLt9nEBLcei8w@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41963@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
New comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/pull/41963#issuecomment-1409414487
Comment:
You probably have a old version of the tarball cached locally (or did fetch it from sources.voidlinux.org).
The content of the tarball didn't change at all, only the compression changed. Can you update the checksum in the template to reflect the new file that github delivers.
```
1a6e5057dbb798d1d2259125651ee4425b58d69bea481e0f255bc30bc8c4df94 new.tar
1a6e5057dbb798d1d2259125651ee4425b58d69bea481e0f255bc30bc8c4df94 old.tar
d410fd8416f4e05b0bf6c0eeedac8dcfda1f1d960bed6cb69a9ddf8d4c04e803 new.tar.gz
1a6e5057dbb798d1d2259125651ee4425b58d69bea481e0f255bc30bc8c4df94 old.tar
87f14a611e3ae9f9babe2dff8e4a6c4f5495fa2883393edb36e796af3f19fb30 old.tar.gz
```
next prev parent reply other threads:[~2023-01-30 21:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 15:18 [PR PATCH] " dkwo
2023-01-30 15:40 ` dkwo
2023-01-30 15:45 ` [PR PATCH] [Updated] " dkwo
2023-01-30 15:48 ` juliendehos
2023-01-30 16:11 ` [PR PATCH] [Updated] " dkwo
2023-01-30 19:33 ` dkwo
2023-01-30 20:00 ` dkwo
2023-01-30 20:19 ` dkwo
2023-01-30 20:26 ` dkwo
2023-01-30 21:58 ` Johnnynator [this message]
2023-01-30 22:52 ` [PR PATCH] [Updated] " dkwo
2023-01-30 22:52 ` dkwo
2023-01-31 1:56 ` Johnnynator
2023-01-31 18:45 ` [PR PATCH] [Updated] " dkwo
2023-01-31 19:53 ` [PR PATCH] [Merged]: " Johnnynator
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=20230130215854.lMh7CSjkuBW_fNBqL6xOmhCBlhbdiRpLt9nEBLcei8w@z \
--to=johnnynator@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).