| 1 |
commit: 8e7f2dd261654f4876ac16cf9f50b24003f4f7e2 |
| 2 |
Author: Sam James <sam <AT> gentoo <DOT> org> |
| 3 |
AuthorDate: Wed Oct 13 00:29:17 2021 +0000 |
| 4 |
Commit: Sam James <sam <AT> gentoo <DOT> org> |
| 5 |
CommitDate: Wed Oct 13 00:29:38 2021 +0000 |
| 6 |
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=8e7f2dd2 |
| 7 |
|
| 8 |
2021-09-29-possible-failure-to-preserve-libraries: clarify world upgrade |
| 9 |
|
| 10 |
Signed-off-by: Sam James <sam <AT> gentoo.org> |
| 11 |
|
| 12 |
...9-possible-failure-to-preserve-libraries.en.txt | 27 +++++++++++++--------- |
| 13 |
1 file changed, 16 insertions(+), 11 deletions(-) |
| 14 |
|
| 15 |
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 |
| 16 |
index cfff106..7154bc4 100644 |
| 17 |
--- a/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt |
| 18 |
+++ b/2021-09-29-possible-failure-to-preserve-libraries/2021-09-29-possible-failure-to-preserve-libraries.en.txt |
| 19 |
@@ -44,7 +44,7 @@ Fixing a broken system is not always straightforward. It is strongly |
| 20 |
recommended to take a backup of your full system before proceeding, |
| 21 |
as well as a copy of /var/db/pkg (the VDB): |
| 22 |
|
| 23 |
-1. A tool has been developed [5] to attempt to fix the consistency |
| 24 |
+Step 1. A tool has been developed [5] to attempt to fix the consistency |
| 25 |
of the Portage database. Using this tool to modify the VDB is NOT |
| 26 |
mandatory (read the full news item before proceeding) - you can skip |
| 27 |
to Step 2 if you wish, but fixing the integrity of the VDB |
| 28 |
@@ -72,23 +72,28 @@ as well as a copy of /var/db/pkg (the VDB): |
| 29 |
# into your real /var/db/pkg/ directory tree. |
| 30 |
``` |
| 31 |
|
| 32 |
-2. Attempt to rebuild the affected packages, first upgrading |
| 33 |
+Step 2. Attempt to rebuild the affected packages, first upgrading |
| 34 |
app-misc/pax-utils to the latest version: |
| 35 |
``` |
| 36 |
$ emerge --ask --verbose --oneshot ">=app-misc/pax-utils-1.3.3" |
| 37 |
$ emerge --ask --verbose --oneshot --usepkg=n $(grep -v '#' broken_vdb_packages) |
| 38 |
``` |
| 39 |
|
| 40 |
-Given that there are possible other side-effects of the corruption/bug, |
| 41 |
-it is strongly recommended that if any corruption is detected, all |
| 42 |
-packages on the system should be rebuilt, after following the above |
| 43 |
-steps: |
| 44 |
-``` |
| 45 |
-$ emerge --ask --emptytree --usepkg=n @world |
| 46 |
-``` |
| 47 |
+ It's possible that the relevant versions have disappeared from the tree, so |
| 48 |
+ if the emerge command fails, please attempt a normal world upgrade. |
| 49 |
+ |
| 50 |
+Step 3. Given that there are possible other side-effects of the corruption/bug, |
| 51 |
+ it is strongly recommended that if any corruption is detected, all |
| 52 |
+ packages on the system should be rebuilt, after following the above |
| 53 |
+ steps: |
| 54 |
+ ``` |
| 55 |
+ $ emerge --ask --emptytree --usepkg=n @world |
| 56 |
+ ``` |
| 57 |
+ |
| 58 |
+ Note that binary packages may need to be discarded given they may |
| 59 |
+ contain corrupt metadata. |
| 60 |
|
| 61 |
-Note that binary packages may need to be discarded given they may |
| 62 |
-contain corrupt metadata. |
| 63 |
+ If no libraries were broken, it is likely safe to skip this step. |
| 64 |
|
| 65 |
Please see the wiki [0] for a full description of the background |
| 66 |
of this problem and handling corner cases such as e.g. already |
Archives