1 |
On Sat, Mar 10, 2018 at 01:22:49PM -0800, Zac Medico wrote: |
2 |
> Please review. This is needed in order to resolve |
3 |
> https://bugs.gentoo.org/650072. |
4 |
> |
5 |
> Title: Portage rsync tree verification unstable |
6 |
> Author: Zac Medico <zmedico@g.o> |
7 |
> Posted: 2018-03-13 |
8 |
> Revision: 1 |
9 |
> News-Item-Format: 2.0 |
10 |
> Display-If-Installed: sys-apps/portage |
11 |
> |
12 |
> Starting with sys-apps/portage-2.3.24, Portage will no longer verify |
13 |
> the Gentoo repository after rsync by default, which contradicts the |
14 |
> earlier "Portage rsync tree verification" news item. |
15 |
Can we have something in this message that tells users WHY it's |
16 |
unstable, beyond just linking to bug 650144? I also don't see any |
17 |
stablereq bug for gemato yet, which should probably also be tracked. |
18 |
|
19 |
A rewrite of this first paragraph to that effect: |
20 |
|
21 |
]] Portage rsync tree verification is being temporarily turned off by |
22 |
]] default, starting with sys-apps/portage-2.3.24. This permits |
23 |
]] stabilization of sys-apps/portage-2.3.24 while still working on bugs |
24 |
]] relating to tree verification [1]: deadlocks [2] & key fetching [3] |
25 |
]] |
26 |
]] [1] https://bugs.gentoo.org/650144 sys-apps/portage: [TRACKER] issues related to 'rsync-verify' USE flag |
27 |
]] [2] https://bugs.gentoo.org/647964 app-portage/gemato-11.2: deadlock? |
28 |
]] [3] https://bugs.gentoo.org/649276 sys-apps/portage: gpg key refresh needs exponential backoff with jitter |
29 |
|
30 |
-- |
31 |
Robin Hugh Johnson |
32 |
Gentoo Linux: Dev, Infra Lead, Foundation Treasurer |
33 |
E-Mail : robbat2@g.o |
34 |
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 |
35 |
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136 |