Update security/libassuan to version 2.0.0, which is required by gnupg 2.0.15

Unfortunately version 2.0.0 is largely incompatible with version 1.x, so it
is necessary to have a stopgap measure while ports that depend on libassuan
can be updated. In conversation with the maintainers of the dependent ports
it was originally considered ideal to prepare updates for the ports first,
then upgrade everything to libassuan 2.x en masse. Since no action has
arisen on that front, go with plan B:

Copy security/libassuan to security/libassuan-1, and update the dependent
ports accordingly. Because this is (intended to be) a _temporary_ measure,
and because no updates for libassuan 1.x are anticipated, and because the
hope is that it can be removed sooner rather than later, it's a copy instead
of a repocopy.

1 files changed, 23 insertions, 0 deletions

diff --git a/UPDATING b/UPDATING
index dddc907888d0..6070d0032292 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,29 @@ 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.
 
+20100613:
+  AFFECTS: users of deskutils/kdepim4, and  security/{dirmngr|gnupg|gpa|opensc}
+  AUTHOR: dougb@FreeBSD.org
+
+  The security/libassuan port has been updated to version 2.0.0, however
+  the applications listed above are not yet compatible with it.  Therefore
+  security/libassuan-1 has been created until they can be updated, and the
+  ports listed above have been updated to depend on it.  You must first
+  replace your existing libassuan with version 1 in the new location, then
+  you can update the ports listed above normally.
+
+  If you use portupgrade:
+
+	portupgrade -f -o security/libassuan-1 security/libassuan
+
+  If you use portmaster:
+
+	portmaster -o security/libassuan-1 libassuan
+
+  If you use neither:
+
+	pkg_delete -f libassuan*
+
 20100609:
   AFFECTS: users of audio/libogg and audio/libao
   AUTHOR: naddy@FreeBSD.org