I'm one of the splashy developers. This should be a bug against lsb-base as it shouldn't provide the file /etc/lsb-base-logging.sh. This file is provided by packages that want to tap into the "hooks" from running the init scripts (/etc/init.d/*).
Splashy needs to do something as init scripts are starting or ending.
On post #26 Thomas Ohms posted a patch that breaks Debian policies. What should be done in case lsb-base cannot be changed, is to use dpkg-divert and move lsb-base-logging.sh out of the way so Splashy can replace it with it's own copy.
Thomas, please join us on #splashy at irc.freenode.net so we can work on a solution together and add this to Debian the proper way. From there it will go to Ubuntu when the repositories are sync'd.
Hello all,
I'm one of the splashy developers. This should be a bug against lsb-base as it shouldn't provide the file /etc/lsb- base-logging. sh. This file is provided by packages that want to tap into the "hooks" from running the init scripts (/etc/init.d/*).
Splashy needs to do something as init scripts are starting or ending.
On post #26 Thomas Ohms posted a patch that breaks Debian policies. What should be done in case lsb-base cannot be changed, is to use dpkg-divert and move lsb-base-logging.sh out of the way so Splashy can replace it with it's own copy.
Thomas, please join us on #splashy at irc.freenode.net so we can work on a solution together and add this to Debian the proper way. From there it will go to Ubuntu when the repositories are sync'd.