Remove old mention from debian/copyright. The remaining of the file

[roundcube.git] / debian / changelog

diff --git a/debian/changelog b/debian/changelog
index 7d4bc865b877f672a5ff425c984b9aeae8e58aa5..090f833b9dcc0351a239045f52580490d48b5d3f 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,11 +1,41 @@
+roundcube (0.5.1-2) unstable; urgency=low
+
+  * Add plugins. Closes: #550454.
+  * Update debian/copyright.
+
+ -- Vincent Bernat <bernat@debian.org>  Sun, 13 Feb 2011 15:25:45 +0100
+
+roundcube (0.5.1-1) unstable; urgency=low
+
+  * New upstream version. Some bugs are corrected in this release or in a
+    previous release:
+      + when switching to HTML mode, content type is now correctly set.
+        Closes: #611321.
+      + header delimiters handling has been fixed in 0.5.
+        Closes: #603489.
+  * Don't assign "skins" directory to www-data. Closes: #612552.
+  * Add instructions on how to install and upgrade when not using
+    dbconfig-common. We do not ship UPGRADING file any more since it is
+    misleading. Closes: #612511.
+  * Fix MySQL indexes if upgrading from 0.5-2 or lesser. Closes: #610725.
+  * Rework how symlinks work. The only directory to use is
+    /var/lib/roundcube. We use symlink from /usr/share/roundcube to
+    /var/lib/roundcube and not the other way. Moreover, plugins and skins
+    are also symlinked. A user should be able to add plugins and skins in
+    /var/lib/roundcube while default ones are in
+    /usr/share/roundcube. Closes: #612553.
+
+ -- Vincent Bernat <bernat@debian.org>  Wed, 09 Feb 2011 07:32:42 +0100
+
 roundcube (0.5-2) experimental; urgency=low
 
   * If 0.3.1 was installed from scratch, upgrade does not work on MySQL
     and PostgreSQL because we try to create an index which already
-    exists. With SQLite, the error is ignored. When using PostgreSQL, drop
-    the index if it already exists. Nothing similar seems to exist with
-    MySQL. Therefore, just don't create the index. We need to handle this
-    later. See bug #610725. Not closing.
+    exists. With SQLite, the error is ignored, no fix needed. When using
+    PostgreSQL, fix this by dropping the index if it already
+    exists. Nothing similar seems to exist with MySQL. Therefore, just
+    don't create the index. We need to handle this later. See bug
+    #610725. Not closing.
 
  -- Vincent Bernat <bernat@debian.org>  Fri, 21 Jan 2011 21:44:05 +0100