Splashy 0.3.13 will close this bug. We introduced a preinst stage that will move /etc/splashy/themes out of the way to /etc/splashy/themes.old. The user would need to dig into this directory to manually copy any customized themes into /usr/share/splashy/themes. Sorry about this but this seems to be the best way to avoid pissing too many people off (or loosing data).
Note that if Splashy is removed/purged, this themes.old directory will be removed also. I'll try to release Splashy 0.3.13 this afternoon (and send a message to the Debian Release Team to allow it into Lenny -- if not too late). This will be strictly bug fixes (the ones that prevented 0.3.12 from staying in Lenny) -- Luis Mondesi <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
