From: "Zac Medico" <zmedico@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2018-03-13-portage-rsync-verification-unstable/
Date: Tue, 4 Jun 2019 17:12:27 +0000 (UTC) [thread overview]
Message-ID: <1559668284.5fde1d514bea51ac6f224540bffa7ca2315ba994.zmedico@gentoo> (raw)
commit: 5fde1d514bea51ac6f224540bffa7ca2315ba994
Author: Zac Medico <zmedico <AT> gentoo <DOT> org>
AuthorDate: Tue Jun 4 17:10:36 2019 +0000
Commit: Zac Medico <zmedico <AT> gentoo <DOT> org>
CommitDate: Tue Jun 4 17:11:24 2019 +0000
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=5fde1d51
2018-03-13-portage-rsync-verification-unstable: Drop obsolete news item
Signed-off-by: Zac Medico <zmedico <AT> gentoo.org>
...3-13-portage-rsync-verification-unstable.en.txt | 46 ----------------------
1 file changed, 46 deletions(-)
diff --git a/2018-03-13-portage-rsync-verification-unstable/2018-03-13-portage-rsync-verification-unstable.en.txt b/2018-03-13-portage-rsync-verification-unstable/2018-03-13-portage-rsync-verification-unstable.en.txt
deleted file mode 100644
index 9f96f27..0000000
--- a/2018-03-13-portage-rsync-verification-unstable/2018-03-13-portage-rsync-verification-unstable.en.txt
+++ /dev/null
@@ -1,46 +0,0 @@
-Title: Portage rsync tree verification unstable
-Author: Zac Medico <zmedico@gentoo.org>
-Posted: 2018-03-13
-Revision: 1
-News-Item-Format: 2.0
-Display-If-Installed: sys-apps/portage
-
-Portage rsync tree verification is being temporarily turned off by
-default, starting with sys-apps/portage-2.3.24. This permits
-stabilization of sys-apps/portage-2.3.24 while still working on bugs
-relating to tree verification [1]: deadlocks [2] & key fetching [3].
-
-If users wish to enable the 'rsync-verify' USE flag for sys-apps/portage,
-they need to follow these steps:
-
-1) In order to unmask the 'rsync-verify' USE flag, create a file named
-/etc/portage/profile/package.use.mask containing a line like the
-following:
-
- sys-apps/portage -rsync-verify
-
-2) Once the 'rsync-verify' USE flag has been unmasked as described
-in step 1, it can be enabled with a line like the following in
-/etc/portage/package.use:
-
- sys-apps/portage rsync-verify
-
-3) After the configuration changes in steps 1 and 2 have been made, run
-the following command:
-
- emerge --oneshot --newuse '>=sys-apps/portage-2.3.24'
-
-After all above steps are successfully completed, a line like the
-following should appear in the emerge --info output for the gentoo
-repository:
-
- sync-rsync-verify-metamanifest: yes
-
-If you wish to disable it for some reason, you can set
-'sync-rsync-verify-metamanifest = no' in your repos.conf.
-
-[1] https://bugs.gentoo.org/650144 sys-apps/portage: [TRACKER] issues
- related to 'rsync-verify' USE flag
-[2] https://bugs.gentoo.org/647964 app-portage/gemato-11.2: deadlock?
-[3] https://bugs.gentoo.org/649276 sys-apps/portage: gpg key refresh
- needs exponential backoff with jitter
next reply other threads:[~2019-06-04 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 17:12 Zac Medico [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-03-13 23:06 [gentoo-commits] data/gentoo-news:master commit in: 2018-03-13-portage-rsync-verification-unstable/ 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=1559668284.5fde1d514bea51ac6f224540bffa7ca2315ba994.zmedico@gentoo \
--to=zmedico@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