On Sat, Mar 10, 2018 at 01:22:49PM -0800, Zac Medico wrote: > Please review. This is needed in order to resolve > https://bugs.gentoo.org/650072. > > Title: Portage rsync tree verification unstable > Author: Zac Medico <zmed...@gentoo.org> > Posted: 2018-03-13 > Revision: 1 > News-Item-Format: 2.0 > Display-If-Installed: sys-apps/portage > > Starting with sys-apps/portage-2.3.24, Portage will no longer verify > the Gentoo repository after rsync by default, which contradicts the > earlier "Portage rsync tree verification" news item. Can we have something in this message that tells users WHY it's unstable, beyond just linking to bug 650144? I also don't see any stablereq bug for gemato yet, which should probably also be tracked.
A rewrite of this first paragraph to that effect: ]] 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] ]] ]] [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 -- Robin Hugh Johnson Gentoo Linux: Dev, Infra Lead, Foundation Treasurer E-Mail : robb...@gentoo.org GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136
signature.asc
Description: Digital signature
