From: Tim Harder <radhermit@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Updating all Manifest to contain SHA256 SHA512 WHIRLPOOL
Date: Sun, 20 Sep 2015 17:06:06 -0400 [thread overview]
Message-ID: <20150920210606.GA23625@tarragon.ad.analog.com> (raw)
In-Reply-To: <55FBD22E.9090208@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 738 bytes --]
On 2015-09-18 04:58, Justin (jlec) wrote:
> 2.
> Any suggestion how to do this? repoman has a manifest-check function but that is
> not functioning (bug filed). Any other tool around? Perhaps using pkgcheck?
With regards to pkgcheck, run the following in a configured gentoo repo
to generate a list of missing checksums in Manifest files:
pkgcheck -c repo_metadata
or a variation where the current working directory doesn't matter:
pkgcheck -c repo_metadata -r gentoo '*'
Note that this will probably output a bunch of metadata exceptions as
well since the tree has a bunch of ebuilds with unknown mirrors in it
(mostly berlios and bitbucket) and running the above disables the check
for them so they show up as errors instead.
Tim
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-09-20 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 8:58 [gentoo-dev] Updating all Manifest to contain SHA256 SHA512 WHIRLPOOL Justin (jlec)
2015-09-18 9:02 ` hasufell
2015-09-18 9:16 ` OpenPGP verification of source files (was: Re: [gentoo-dev] Updating all Manifest to contain SHA256 SHA512 WHIRLPOOL) Kristian Fiskerstrand
2015-09-18 12:30 ` Rich Freeman
2015-09-20 17:41 ` [gentoo-dev] Updating all Manifest to contain SHA256 SHA512 WHIRLPOOL Robin H. Johnson
2015-09-20 18:08 ` Justin Lecher (jlec)
2015-09-20 21:06 ` Tim Harder [this message]
2015-09-22 19:23 ` Justin Lecher (jlec)
2015-09-22 20:16 ` Tim Harder
2015-09-23 8:00 ` Justin (jlec)
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=20150920210606.GA23625@tarragon.ad.analog.com \
--to=radhermit@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