aboutsummaryrefslogtreecommitdiff
path: root/UPDATING
diff options
context:
space:
mode:
authorRuslan Makhmatkhanov <rm@FreeBSD.org>2012-11-09 09:03:50 +0000
committerRuslan Makhmatkhanov <rm@FreeBSD.org>2012-11-09 09:03:50 +0000
commit543d40849126b54b67591839cf1f1b4284f3d42f (patch)
tree65becb9300c11146e325b896dbcfecab6ef168df /UPDATING
parent8439a08db4775006b2adc331c72085f1b0aa044d (diff)
downloadports-543d40849126b54b67591839cf1f1b4284f3d42f.tar.gz
ports-543d40849126b54b67591839cf1f1b4284f3d42f.zip
- update devel/py-liblarch to 2.1.0
- remove devel/py-liblarch_gtk because it was merged into devel/py-liblarch itself - add UPDATING entry for deskutils/gtg users Feature safe: yes
Notes
Notes: svn path=/head/; revision=307224
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING8
1 files changed, 8 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index d777c9590263..8a8daec4d5f2 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,14 @@ 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.
+20121109:
+ AFFECTS: users of devel/py-liblarch_gtk deskutils/gtg
+ AUTHOR: rm@FreeBSD.org
+
+ Code of py-liblarch_gtk has been merged into py-liblarch 2.1.0. To avoid
+ any conflicts, user need to remove py-liblarch_gtk before the update of
+ py-liblarch.
+
20121105:
AFFECTS: users of mail/postfix-current
AUTHOR: sahil@FreeBSD.org