aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorOlli Hauer <ohauer@FreeBSD.org>2014-04-15 18:46:37 +0000
committerOlli Hauer <ohauer@FreeBSD.org>2014-04-15 18:46:37 +0000
commit487fa667db7a9dfca26b6a1997451763f5e6f66c (patch)
treee6b94b53ee1670464bd9d39a118fef8c6256250b /UPDATING
parent44946a69cd6d3ee985cd42e38e9bd12a7dbdb81b (diff)
downloadports-487fa667db7a9dfca26b6a1997451763f5e6f66c.tar.gz
ports-487fa667db7a9dfca26b6a1997451763f5e6f66c.zip
- move www/mod_python3 -> www/mod_python33
- use DIST_SUBDIR - adjust devel/viewvc + add OPTION for www/mod_python35 - add entry to UPDATING and MOVED with hat apache@
Notes
Notes: svn path=/head/; revision=351359
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING22
1 files changed, 20 insertions, 2 deletions
diff --git a/UPDATING b/UPDATING
index 09c0e60b4f73..7624c148bea5 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,24 @@ they are unavoidable.
You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
+20140415:
+ AFFECTS: Users of mod_python3
+ AUTHOR: ohauer@FreeBSD.org
+
+ www/mod_python3 was renamed to www/mod_python33, additional www/mod_python35
+ with support for apache24 was added to the portstree.
+
+ To reflect the new port location use:
+
+ pkgng users:
+ # pkg set -o www/mod_python3:www/mod_python33
+
+ portmaster users:
+ # portmaster -o www/mod_python33 www/mod_python3
+
+ portupgrade users:
+ # portugrade -o www/mod_python33 www/mod_python3
+
20140414:
AFFECTS: Users of dmd 1.X and dmd 2.x.
AUTHOR: cy@FreeBSD.org
@@ -83,8 +101,8 @@ you update your ports collection, before attempting any port upgrades.
AFFECTS: users of textproc/elasticsearch
AUTHOR: tj@FreeBSD.org
- Elasticsearch has been updated to version 1.1.0. If you are updating
- from a version prior to 1.0.0 you will need to do a full cluster
+ Elasticsearch has been updated to version 1.1.0. If you are updating
+ from a version prior to 1.0.0 you will need to do a full cluster
shutdown for this update as it can not be performed in a rolling
fashion.