Gentoo Archives: gentoo-commits

From: Sam James <sam@g.o>
To: gentoo-commits@l.g.o
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2021-09-29-possible-failure-to-preserve-libraries/
Date: Mon, 22 Nov 2021 06:32:08
Message-Id: 1637562718.ef0cfc2c0e68299ddfa355732c76cf7d9ed83fcb.sam@gentoo
1 commit: ef0cfc2c0e68299ddfa355732c76cf7d9ed83fcb
2 Author: Sam James <sam <AT> gentoo <DOT> org>
3 AuthorDate: Mon Nov 22 06:30:45 2021 +0000
4 Commit: Sam James <sam <AT> gentoo <DOT> org>
5 CommitDate: Mon Nov 22 06:31:58 2021 +0000
6 URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=ef0cfc2c
7
8 2021-09-29-possible-failure-to-preserve-libraries: mention when it's ok to skip -e
9
10 It should be okay to skip -e @world and instead only rebuild libraries +
11 their consumers in some cases.
12
13 Bug: https://bugs.gentoo.org/811462
14 Signed-off-by: Sam James <sam <AT> gentoo.org>
15
16 .../2021-09-29-possible-failure-to-preserve-libraries.en.txt | 7 ++++++-
17 1 file changed, 6 insertions(+), 1 deletion(-)
18
19 diff --git a/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt b/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt
20 index 7154bc4..68aa6af 100644
21 --- a/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt
22 +++ b/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt
23 @@ -93,7 +93,12 @@ Step 3. Given that there are possible other side-effects of the corruption/bug,
24 Note that binary packages may need to be discarded given they may
25 contain corrupt metadata.
26
27 - If no libraries were broken, it is likely safe to skip this step.
28 + If no libraries were broken, it is likely safe to skip this step. It
29 + should be sufficient, for resource-constrained machines, to simply
30 + rebuild any broken libraries and their consumers (reverse-dependencies):
31 + revdep-rebuild may help you do this.
32 +
33 + (If you do not know what that means, please proceed with Step 3.)
34
35 Please see the wiki [0] for a full description of the background
36 of this problem and handling corner cases such as e.g. already