tags 465094 - moreinfo tags 465094 + confirmed pending thankyou On Mon, Feb 11, 2008 at 02:41:00PM +0100, Wolfgang Weisselberg wrote: > I can produce an at least similar error by the following sequence: > > # dpkg --install festival_1.96~beta-5_amd64.deb > # echo "RUN_FESTIVAL=no" > /etc/default/festival > # dpkg --install /var/cache/apt/archives/festival_1.96~beta-3_amd64.deb > overwrite /etc/default/festival > # cat /etc/default/festival > # Set RUN_FESTIVAL=yes to start festival at boot time. > RUN_FESTIVAL=no > # dpkg --install /var/cache/apt/archives/festival_1.96~beta-5_amd64.deb > (Reading database ... 264707 files and directories currently installed.) > Preparing to replace festival 1.96~beta-3 (using > .../festival_1.96~beta-5_amd64.deb) ... > Unpacking replacement festival ... > Setting up festival (1.96~beta-5) ... > Installing new version of config file /etc/init.d/festival ... > Installing new version of config file /etc/default/festival ... > Starting Festival server: festival/usr/bin/festival already running. > invoke-rc.d: initscript festival, action "start" failed. > dpkg: error processing festival (--install): > subprocess post-installation script returned error exit status 1 > Errors were encountered while processing: > festival > #
Dear Wolfgang, This was a perfect reconstruction of the bug. I thank you for it. The solution is simple; the init script just exits if RUN_FESTIVAL is set to no. I have now modified it not to exit in case RUN_FESTIVAL is no, so that even if that is the case, festival is started, and even when start is specified, I restart festival to ensure that the process goes smoothly. This may seem an ugly hack, but works OK for festival. I'll think about a better way later, though. Thanks. Kumar -- Kumar Appaiah, 458, Jamuna Hostel, Indian Institute of Technology Madras, Chennai - 600 036
signature.asc
Description: Digital signature
