public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: metadata/
Date: Mon, 19 Feb 2018 17:49:19 +0000 (UTC)	[thread overview]
Message-ID: <1519062478.a08c63bc78563ae0ff4a59288cd15e3cf5e4f703.mgorny@gentoo> (raw)

commit:     a08c63bc78563ae0ff4a59288cd15e3cf5e4f703
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Mon Feb 19 17:47:58 2018 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Mon Feb 19 17:47:58 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a08c63bc

metadata/layout.conf: Update manifest-required-hashes to BLAKE2B

Update manifest-required-hashes according to the Council-approved plan
outlined in [1]. The Portage version supporting BLAKE2B is amd64-stable
for 3 months already.

[1]:https://archives.gentoo.org/gentoo-dev/message/682618f6d1cf4d63b30577cb1e9bd269

 metadata/layout.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/metadata/layout.conf b/metadata/layout.conf
index d9cfaf7c147..c68ab815082 100644
--- a/metadata/layout.conf
+++ b/metadata/layout.conf
@@ -12,7 +12,7 @@ manifest-hashes = BLAKE2B SHA512
 # The following hashes are required on all Manifest entries. If any
 # of them are missing, repoman will refetch and rehash old distfiles.
 # Otherwise, old distfiles will keep using their current hash set.
-manifest-required-hashes = SHA512
+manifest-required-hashes = BLAKE2B
 
 # 2013-04-09 gentoo's council says to deprecate EAPIs 1 and 2 (bug #470670).
 # 2014-02-25 council meeting deprecated EAPIs 0 and 3.


             reply	other threads:[~2018-02-19 17:49 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 17:49 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-05 12:55 [gentoo-commits] repo/gentoo:master commit in: metadata/ Michael Orlitzky
2024-08-26 16:43 Arthur Zamarin
2024-02-24 10:26 Michał Górny
2024-02-12 21:02 Ulrich Müller
2024-01-15  9:17 Ulrich Müller
2023-12-30  9:58 Ulrich Müller
2023-01-07  8:17 Ulrich Müller
2022-11-22 17:48 Michał Górny
2022-10-22 10:54 Ulrich Müller
2022-10-22 10:54 Ulrich Müller
2022-07-18 15:49 Jakov Smolić
2021-08-13  9:03 Ulrich Müller
2021-08-08 23:14 Ulrich Müller
2021-07-11 21:12 Ulrich Müller
2021-06-23 17:55 Ulrich Müller
2021-05-19  8:12 Michał Górny
2020-11-26 13:32 Sam James
2020-09-26 12:15 Ulrich Müller
2020-03-05  5:57 Michał Górny
2020-03-05  5:57 Michał Górny
2019-12-09 20:44 Ulrich Müller
2019-12-09 20:30 Aaron Bauman
2019-11-02 11:45 Michał Górny
2019-10-04 20:25 Andreas K. Hüttel
2019-08-05 20:39 Zac Medico
2019-03-16  4:22 Michael Palimaka
2019-02-02 17:25 Michał Górny
2018-12-24 21:20 Ulrich Müller
2018-12-20 22:55 Ulrich Müller
2018-05-20  0:20 Andreas Hüttel
2018-05-14  5:49 Ulrich Müller
2018-05-14  5:47 Ulrich Müller
2017-11-28 11:20 Michael Palimaka
2017-11-21 20:09 Michał Górny
2017-11-21 17:48 Michał Górny
2017-11-10 17:19 Michał Górny
2017-10-13 20:57 Ulrich Müller
2017-10-13 20:53 Ulrich Müller
2017-07-15  2:22 Brian Dolbec
2017-04-21  5:37 Jason Zaman
2017-01-14 15:51 Manuel Rüger
2016-05-04  5:15 Jason Zaman
2016-01-20 15:36 Justin Lecher
2016-01-18  9:48 Mike Frysinger
2016-01-18  9:48 Mike Frysinger
2016-01-17  6:48 Robin H. Johnson
2016-01-15 10:44 Justin Lecher
2015-10-14 14:56 Julian Ospald
2015-08-25  0:21 Mike Gilbert
2015-08-15 16:56 Julian Ospald
2015-08-11  4:01 Mike Frysinger

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=1519062478.a08c63bc78563ae0ff4a59288cd15e3cf5e4f703.mgorny@gentoo \
    --to=mgorny@gentoo.org \
    --cc=gentoo-commits@lists.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