From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Need GitHub snapshot hash verification failure samples
Date: Wed, 05 Jul 2017 21:48:12 +0200 [thread overview]
Message-ID: <1499284092.1134.1.camel@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 510 bytes --]
Hi, everyone.
I've seen multiple bugs related to hash verification failures for GitHub
snapshots lately. However, none of the maintainers have been so far able
to provide me with a sample of the old and new snapshot for comparison,
so we still have no clue what's happening exactly.
if you see your package failing or get a report for it, then *please*
save the original tarball before replacing it with the new one and send
me both for comparison. Thank you.
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 988 bytes --]
next reply other threads:[~2017-07-05 19:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 19:48 Michał Górny [this message]
2017-07-05 22:30 ` [gentoo-dev] Need GitHub snapshot hash verification failure samples Vadim A. Misbakh-Soloviov
2017-07-08 22:09 ` William L. Thomson Jr.
2017-07-06 20:15 ` Sergei Trofimovich
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=1499284092.1134.1.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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