From: Zac Medico <zmedico@gentoo.org>
Date: Wed, 14 Jan 2009 00:43:51 +0000 (-0000)
Subject: Bug #254825 - Add a note about the need to use `ebuild --force <ebuild file>
X-Git-Tag: v2.2_rc22~4
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=328730fc949f699d7c5397bd11ef2d4af59bf754;p=portage.git

Bug #254825 - Add a note about the need to use `ebuild --force <ebuild file>
manifest` to update distfiles digests.

svn path=/main/trunk/; revision=12500
---

diff --git a/RELEASE-NOTES b/RELEASE-NOTES
index b68c02d90..c5a5dc6c2 100644
--- a/RELEASE-NOTES
+++ b/RELEASE-NOTES
@@ -47,6 +47,11 @@ portage-2.1.6
   used in ACCEPT_KEYWORDS.
   For packages that don't specify any other KEYWORDS you can use the new **
   token as documented in portage(5) to disable KEYWORDS filtering completely.
+* When generating manifests, existing distfiles digests will not be updated
+  in cases when the current file in $DISTDIR does not match. In order to
+  force digests to be updated, run `ebuild --force <ebuild file> manifest`.
+  This is a safety measure which protects valid distfiles digests from being
+  accidentally replaced by invalid digests.
 
 portage-2.1.5
 ==================================