From 2771f79232c273bc2a57d23bf335dd81ccf6af28 Mon Sep 17 00:00:00 2001 From: V3n3RiX Date: Sun, 5 Dec 2021 02:47:11 +0000 Subject: gentoo resync : 05.12.2021 --- .../2021-09-29-possible-failure-to-preserve-libraries.en.txt | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'metadata/news/2021-09-29-possible-failure-to-preserve-libraries') diff --git a/metadata/news/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt b/metadata/news/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt index 7154bc497e2e..68aa6af5e8f1 100644 --- a/metadata/news/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt +++ b/metadata/news/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt @@ -93,7 +93,12 @@ Step 3. Given that there are possible other side-effects of the corruption/bug, Note that binary packages may need to be discarded given they may contain corrupt metadata. - If no libraries were broken, it is likely safe to skip this step. + If no libraries were broken, it is likely safe to skip this step. It + should be sufficient, for resource-constrained machines, to simply + rebuild any broken libraries and their consumers (reverse-dependencies): + revdep-rebuild may help you do this. + + (If you do not know what that means, please proceed with Step 3.) Please see the wiki [0] for a full description of the background of this problem and handling corner cases such as e.g. already -- cgit v1.2.3