summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2009-01-14 00:43:51 +0000
committerZac Medico <zmedico@gentoo.org>2009-01-14 00:43:51 +0000
commit328730fc949f699d7c5397bd11ef2d4af59bf754 (patch)
tree45a8297cdf66e7c5df0e49a4da685e896e045c14 /RELEASE-NOTES
parentInside digestgen(), don't unnecessarily call fetch() in cases when the there (diff)
downloadportage-idfetch-328730fc949f699d7c5397bd11ef2d4af59bf754.tar.gz
portage-idfetch-328730fc949f699d7c5397bd11ef2d4af59bf754.tar.bz2
portage-idfetch-328730fc949f699d7c5397bd11ef2d4af59bf754.zip
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
Diffstat (limited to 'RELEASE-NOTES')
-rw-r--r--RELEASE-NOTES5
1 files changed, 5 insertions, 0 deletions
diff --git a/RELEASE-NOTES b/RELEASE-NOTES
index b68c02d9..c5a5dc6c 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
==================================