From cf635737ede4b1db7bdcb396a49f0abd0b62cd66 Mon Sep 17 00:00:00 2001 From: "Yann E. MORIN" Date: Sat, 28 Oct 2023 23:09:04 +0200 Subject: [PATCH] docs/manual: svn downloads can be hash-checked Since commit 89f5e989323a (support/download/svn: generate reproducible svn archives), we've been able to generate reproducible archives, and thus we have been able to verify the hashes for those archives. However, the manual was not changed, and still falsely hinted that this was not the cae. Fix that. Signed-off-by: Yann E. MORIN Signed-off-by: Peter Korsgaard (cherry picked from commit 6898781f03140e301196a533953a202751be2f59) Signed-off-by: Peter Korsgaard --- docs/manual/adding-packages-directory.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/manual/adding-packages-directory.txt b/docs/manual/adding-packages-directory.txt index 04f5241d05..7150018a3b 100644 --- a/docs/manual/adding-packages-directory.txt +++ b/docs/manual/adding-packages-directory.txt @@ -534,9 +534,9 @@ typically indicates that the +.hash+ file is wrong but the downloaded file is probably OK. Hashes are currently checked for files fetched from http/ftp servers, -Git repositories, files copied using scp and local files. Hashes are -not checked for other version control systems (such as Subversion, -CVS, etc.) because Buildroot currently does not generate reproducible +Git or subversion repositories, files copied using scp and local files. +Hashes are not checked for other version control systems (such as CVS, +mercurial) because Buildroot currently does not generate reproducible tarballs when source code is fetched from such version control systems.