aboutsummaryrefslogtreecommitdiffstats
path: root/UPDATING
diff options
context:
space:
mode:
authorrm <rm@FreeBSD.org>2016-06-19 20:23:29 +0800
committerrm <rm@FreeBSD.org>2016-06-19 20:23:29 +0800
commitf581a12668cd15ec1edaff3ca0110dd21f957087 (patch)
treeb0e645bb5dd05cb6a0bad7ec7258b18a22379b28 /UPDATING
parent5ee8fdbadef1a9b890ea7dddafbc547e38349a90 (diff)
downloadfreebsd-ports-gnome-f581a12668cd15ec1edaff3ca0110dd21f957087.tar.gz
freebsd-ports-gnome-f581a12668cd15ec1edaff3ca0110dd21f957087.tar.zst
freebsd-ports-gnome-f581a12668cd15ec1edaff3ca0110dd21f957087.zip
Oops, forgot the UPDATING change to follow up r417115
PR: 210376 Submitted by: Vladimir Krstulja <vlad-fbsd@acheronmedia.com>
Diffstat (limited to 'UPDATING')
-rw-r--r--UPDATING11
1 files changed, 11 insertions, 0 deletions
diff --git a/UPDATING b/UPDATING
index 70aa47663461..d2e59aaf34a1 100644
--- a/UPDATING
+++ b/UPDATING
@@ -5,6 +5,17 @@ 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.
+20160619
+ AFFECTS: users of databases/py-apsw
+ AUTHOR: rm@FreeBSD.org
+
+ SQLite 3.12 completely changed the semantics of VFS.xGetLastError() in an
+ incompatible way. This required a rewrite of the relevant C, Python and test
+ code. If you implement or use this method then you have to rewrite your code
+ too. Also note that running the test suite from an earlier version of APSW
+ against this or future SQLite versions will result in consuming all memory,
+ swap or address space (an underlying integer changed meaning).
+
20160616
AFFECTS: users of security/openssl*, security/libressl*
AUTHOR: mat@FreeBSD.org