diff options
| author |   Repository mirror & CI <repomirrorci@gentoo.org> | 2021-11-22 11:51:46 +0000 |
|---|---|---|
| committer | Repository mirror & CI <repomirrorci@gentoo.org> | 2021-11-22 11:51:46 +0000 |
| commit | 19e1ed1813267f3f8e481e12e941340e8bca5f8e (patch) | |
| tree | ccaca92c371872d96f1d26ccf07e11a3cfbd5d72 /metadata/news | |
| parent | Merge updates from master (diff) | |
| parent | 2021-09-29-possible-failure-to-preserve-libraries: mention when it's ok to sk... (diff) | |
| download | gentoo-19e1ed1813267f3f8e481e12e941340e8bca5f8e.tar.gz gentoo-19e1ed1813267f3f8e481e12e941340e8bca5f8e.tar.bz2 gentoo-19e1ed1813267f3f8e481e12e941340e8bca5f8e.zip | |
Merge commit 'ef0cfc2c0e68299ddfa355732c76cf7d9ed83fcb'
Diffstat (limited to 'metadata/news')
2 files changed, 7 insertions, 1 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 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 diff --git a/metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt b/metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt index feddaf62ba42..1b80f95cc5ea 100644 --- a/metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt +++ b/metadata/news/2021-10-18-libxcrypt-migration-stable/2021-10-18-libxcrypt-migration-stable.en.txt @@ -44,6 +44,7 @@ need to take the following steps: * unmask and enable the crypt USE flag of sys-libs/glibc * mask the system USE flag of sys-libs/libxcrypt * mask >=virtual/libcrypt-2 +* unmask virtual/libcrypt:0/1 If you wish to manually migrate now, there are a series of steps described on the wiki (see below), but the outline is: |