summaryrefslogtreecommitdiff
path: root/metadata/news/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt
diff options
context:
space:
mode:
authorV3n3RiX <venerix@koprulu.sector>2021-10-20 10:22:14 +0100
committerV3n3RiX <venerix@koprulu.sector>2021-10-20 10:22:14 +0100
commit46eedbedafdb0040c37884982d4c775ce277fb7b (patch)
treedb33a91259730be84999e13a8d8168c799f50ac0 /metadata/news/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt
parente23a08d0c97a0cc415aaa165da840b056f93c997 (diff)
gentoo resync : 20.10.2021
Diffstat (limited to 'metadata/news/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt')
-rw-r--r--metadata/news/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt27
1 files changed, 16 insertions, 11 deletions
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 cfff10629da0..7154bc497e2e 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
@@ -44,7 +44,7 @@ Fixing a broken system is not always straightforward. It is strongly
recommended to take a backup of your full system before proceeding,
as well as a copy of /var/db/pkg (the VDB):
-1. A tool has been developed [5] to attempt to fix the consistency
+Step 1. A tool has been developed [5] to attempt to fix the consistency
of the Portage database. Using this tool to modify the VDB is NOT
mandatory (read the full news item before proceeding) - you can skip
to Step 2 if you wish, but fixing the integrity of the VDB
@@ -72,23 +72,28 @@ as well as a copy of /var/db/pkg (the VDB):
# into your real /var/db/pkg/ directory tree.
```
-2. Attempt to rebuild the affected packages, first upgrading
+Step 2. Attempt to rebuild the affected packages, first upgrading
app-misc/pax-utils to the latest version:
```
$ emerge --ask --verbose --oneshot ">=app-misc/pax-utils-1.3.3"
$ emerge --ask --verbose --oneshot --usepkg=n $(grep -v '#' broken_vdb_packages)
```
-Given that there are possible other side-effects of the corruption/bug,
-it is strongly recommended that if any corruption is detected, all
-packages on the system should be rebuilt, after following the above
-steps:
-```
-$ emerge --ask --emptytree --usepkg=n @world
-```
+ It's possible that the relevant versions have disappeared from the tree, so
+ if the emerge command fails, please attempt a normal world upgrade.
+
+Step 3. Given that there are possible other side-effects of the corruption/bug,
+ it is strongly recommended that if any corruption is detected, all
+ packages on the system should be rebuilt, after following the above
+ steps:
+ ```
+ $ emerge --ask --emptytree --usepkg=n @world
+ ```
+
+ Note that binary packages may need to be discarded given they may
+ contain corrupt metadata.
-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.
Please see the wiki [0] for a full description of the background
of this problem and handling corner cases such as e.g. already