aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorKirill Ponomarev <krion@FreeBSD.org>2005-03-20 09:38:26 +0000
committerKirill Ponomarev <krion@FreeBSD.org>2005-03-20 09:38:26 +0000
commit4fcee630766767906c7df241d0ac8cb86456546e (patch)
tree3bbcba0acde20e0394e84659cb6385887406d982 /UPDATING
parent8f5d0f33d7992b40fdb069f46a75144c3a55586d (diff)
downloadports-4fcee630766767906c7df241d0ac8cb86456546e.tar.gz
ports-4fcee630766767906c7df241d0ac8cb86456546e.zip
Notes
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING18
1 files changed, 18 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 89d135a3b733..bbcefd5c5f49 100644
--- a/UPDATING
+++ b/UPDATING
@@ -6,6 +6,24 @@ You should get into the habit of checking this file for changes each
time you update your ports collection, before attempting any port
upgrades.
+20050320:
+ AFFECTS: users of sysutils/portsnap
+ AUTHOR: cperciva@FreeBSD.org
+
+ As a result of shifting from SHA-1 to SHA-256, the structure of
+ portsnap's configuration file and compressed snapshot have both
+ changed. After upgrading to portsnap 0.9, you will have to
+ update your configuration file ($PREFIX/etc/portsnap.conf) and
+ delete your existing portsnap compressed snapshot:
+
+ # cd /usr/local/etc && cp portsnap.conf.sample portsnap.conf
+ # rm -r /usr/local/portsnap/*
+
+ In addition, be aware that the next runs of "portsnap fetch" and
+ "portsnap update" will take far longer than usual, since they
+ will need to download and extract a complete copy of the ports
+ tree.
+
20050319:
AFFECTS: users of databases/postgresql7[34]-server
AUTHOR: girgen@FreeBSD.org