public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage:master commit in: cnf/
Date: Fri, 13 Oct 2023 10:19:05 +0000 (UTC)	[thread overview]
Message-ID: <1697192280.3bf2144eb34101c0539dc4d3e057c13d0790f8d7.sam@gentoo> (raw)

commit:     3bf2144eb34101c0539dc4d3e057c13d0790f8d7
Author:     Florian Schmaus <flow <AT> gentoo <DOT> org>
AuthorDate: Mon Oct  9 11:01:14 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Oct 13 10:18:00 2023 +0000
URL:        https://gitweb.gentoo.org/proj/portage.git/commit/?id=3bf2144e

repos.conf: set value of sync-rsync-verify-max-age for ::gentoo to 3

The value sync-rsync-verify-max-age specifies the default age in
days. The current value of 24 is too high for an repo with daily
changes like ::gentoo, and was set under the assumption that
max-age denotes hours [1].

1: 8d99acdb3f4f ("rsync: Issue an explicit warning if Manifest
timestamp is >24hr old")

Signed-off-by: Florian Schmaus <flow <AT> gentoo.org>
Fixes: 8d99acdb3f4f ("rsync: Issue an explicit warning if Manifest timestamp is >24hr old")
Closes: https://github.com/gentoo/portage/pull/1125
Signed-off-by: Sam James <sam <AT> gentoo.org>

 cnf/repos.conf | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/cnf/repos.conf b/cnf/repos.conf
index 6cb6e3b3c4..f16fd352ee 100644
--- a/cnf/repos.conf
+++ b/cnf/repos.conf
@@ -8,7 +8,7 @@ sync-uri = rsync://rsync.gentoo.org/gentoo-portage
 auto-sync = yes
 sync-rsync-verify-jobs = 1
 sync-rsync-verify-metamanifest = yes
-sync-rsync-verify-max-age = 24
+sync-rsync-verify-max-age = 3
 sync-openpgp-key-path = /usr/share/openpgp-keys/gentoo-release.asc
 sync-openpgp-keyserver = hkps://keys.gentoo.org
 sync-openpgp-key-refresh-retry-count = 40


             reply	other threads:[~2023-10-13 10:19 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-13 10:19 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-10 22:59 [gentoo-commits] proj/portage:master commit in: cnf/ Sam James
2023-08-03 21:15 Sam James
2023-08-03 21:15 Sam James
2022-04-11 20:17 Mike Gilbert
2022-02-06 19:19 Zac Medico
2021-11-16 21:17 Zac Medico
2020-05-03 20:32 Zac Medico
2019-10-21 18:07 Michał Górny
2019-09-26  0:03 Zac Medico
2019-07-05  5:39 Michał Górny
2019-04-19  5:16 Zac Medico
2018-12-12 18:41 Michał Górny
2018-08-12 10:05 Zac Medico
2018-07-11 18:01 Zac Medico
2018-05-11  7:48 Michał Górny
2017-12-11  2:27 Zac Medico
2017-08-02  8:06 Michał Górny
2017-01-06 22:13 Brian Dolbec
2017-01-06 18:00 Brian Dolbec
2017-01-06 18:00 Brian Dolbec
2015-12-15  8:40 Brian Dolbec
2015-03-10 17:53 Zac Medico
2014-11-02  3:02 Zac Medico
2013-07-25 22:00 Zac Medico
2013-05-10  4:09 Zac Medico
2013-01-21 16:52 Zac Medico
2013-01-21 16:48 Zac Medico
2012-11-05  8:52 Zac Medico
2012-09-06 20:06 Zac Medico
2012-08-17 21:36 Zac Medico
2012-08-05  8:13 Zac Medico
2012-07-23 17:45 Zac Medico
2012-07-09 21:03 Zac Medico
2012-07-06  6:43 Zac Medico
2012-05-05 16:41 Zac Medico
2011-12-22  4:30 Zac Medico
2011-12-22  4:22 Zac Medico
2011-12-21 21:45 Zac Medico
2011-11-11 21:23 Zac Medico
2011-08-26  3:52 Zac Medico
2011-06-03  5:24 Zac Medico

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=1697192280.3bf2144eb34101c0539dc4d3e057c13d0790f8d7.sam@gentoo \
    --to=sam@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