newsSavane - News: Release 1.1: bugfixes

Show feedback again
Latest News
Security fix: scp restricted shell bypass posted by beuc, Thu Feb 2 22:02:09 2017 - 0 replies
New Savane release fixes symlink attack and privilege escalation posted by beuc, Wed Dec 2 22:24:18 2009 - 0 replies
Release 3.0: markup language and anti-spam tools posted by yeupou, Mon Dec 4 09:38:30 2006 - 2 replies
Release 2.0: interface heavy improvements, bugfixes and cosmetics posted by yeupou, Tue Oct 3 08:06:29 2006 - 2 replies
We need packagers! posted by yeupou, Tue Sep 19 18:09:45 2006 - 2 replies
[Submit News]
[23 news in archive]

Release 1.1: bugfixes

Item posted by Mathieu Roy <yeupou> on Tue Sep 13 14:01:22 2005.

One more Savane release, an unplanned one.

Obtaining it:

- The GPG-signed tarball is available at <>
- You can use apt-get with Debian, adding "deb stable/" (without quotes) in your /etc/apt/sources.list

Main purpose of the release:

We found the two following bugs (see ChangeLog) to be annoying enough to justify a release. The most annoying bug was inserted in the release 1.0.8 (one week old, err), the other one, more trivial, was inserted in the release 1.0.6. Sorry for the inconvenience.

Installing it/Upgrading it:

If you are running Savane 1.0.8, you should run sql and perl scripts included in savane/update/1.1, as described in savane/update/README (or shipped with the debian package savane-update).
These scripts will handle the trivial changes on the database needed. They are supposedly safe but you should, indeed, do a backup of your database first, just in case (using mysqldump, for instance).

If you are running an older version than 1.0.8, you should run the scripts in savane/update for each release you missed.

Also, take care to the sections [CONFIGURATION] and [SITE SPECIFIC CONTENT] of the
ChangeLog below, it will tells you which files should be added in your site specific content directory.

Otherwise, just follow INSTALL, or INSTALL.verbose if it not enough. You will probably want to take a look at more completes guides available at <>

If you encounter undocumented troubles, please fill a support request at <>



  • Fix a bug causing html content to be sent as html in items

comments and original submission (bug #2874). This bug was only
found in Savane 1.0.8, not in previous version.


  • Fix a typo that would create confusing between status "In Progress"

and "Need Info" (bug #2857).

That's all.


No messages in Release 1.1: bugfixes


Start a New Thread:

You could post if you were logged in
Show feedback again

Back to the top

Powered by Savane 3.1-cleanup