X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/880d098dab86e09eece360d970dc921e5f734903..bed1f1037a4dfe6368c81ea2e2a0ac32f56126ce:/debian/NEWS diff --git a/debian/NEWS b/debian/NEWS index 9dd93c85e..4aac33b80 100644 --- a/debian/NEWS +++ b/debian/NEWS @@ -1,3 +1,35 @@ +ikiwiki (2.52) unstable; urgency=low + + All wikis need to be rebuilt on upgrade to this version. If you listed your + wiki in /etc/ikiwiki/wikilist this will be done automatically when the + Debian package is upgraded. Or use ikiwiki-mass-rebuild to force a rebuild. + + -- Joey Hess Sun, 06 Jul 2008 15:10:05 -0400 + +ikiwiki (2.49) unstable; urgency=low + + The search plugin no longer uses hyperestraier. Instead, to use it you + will now need to install xapian-omega, and the Search::Xapian, + HTML::Scrubber, and Digest::SHA1 perl modules. Ie, + `apt-get install xapian-omega libsearch-xapian-perl libhtml-scrubber-perl libdigest-sha1-perl` + + Also, wikis that use the search plugin will need to be rebuilt, + since the search form has changed. This will not be done automatically, + but can be done by running `ikiwiki-mass-upgrade` as root, or + running `ikiwiki -setup` on individual setup files. + + -- Joey Hess Wed, 04 Jun 2008 00:29:28 -0400 + +ikiwiki (2.48) unstable; urgency=high + + If you allowed password based logins to your wiki, those passwords were + stored in cleartext in the userdb. To guard against exposing users' + passwords, I recommend you install the Authen::Passphrase perl module, and + then run `ikiwiki-transition hashpassword /path/to/srcdir` to replace all + existing cleartext passwords with strong (blowfish) hashes. + + -- Joey Hess Thu, 29 May 2008 14:39:34 -0400 + ikiwiki (2.46) unstable; urgency=low There were some significant template changes in ikiwiki 2.42 (and 1.33.5). @@ -89,7 +121,7 @@ ikiwiki (2.14) unstable; urgency=low This version of ikiwiki is more picky about symlinks in the path leading to the srcdir, and will refuse to use a srcdir specified by such a path. - This was necessary to avoid some potential exploits, but could potentially + This was necessary to avoid some potential exploits, but could potentially break (semi-)working wikis. If your wiki has a srcdir path containing a symlink, you should change it to use a path that does not.