Bug#418873: Too high K sequence number for timidity init.d script - Breaks hwclock.sh

[Gilles Filippini <gilles.filippini@free.fr>]

Package: timidity
Version: 2.13.2-11

Timidity K init.d scripts are:
   /etc/rc0.d/K99timidity
   /etc/rc1.d/K99timidity
   /etc/rc6.d/K99timidity

Using 99 as sequence number implies that, on halt or reboot, hwclock.sh 
is called *before* timidity is stopped.
This is a problem on my box because hwclock --systohc can't work while 
timidity is running:
   # hwclock --debug --systohc --utc
   hwclock from util-linux-2.12r
   hwclock: Open of /dev/rtc failed, errno=16: Périphérique ou ressource
   occupé.
   No usable clock interface found.
   Cannot access the Hardware Clock via any known method.

Invoking hwclock --systohc *after* stopping timidity works fine:
   # invoke-rc.d timidity stop
   Stopping timidity.
   maison:/home/pini# hwclock --debug --systohc --utc
   hwclock from util-linux-2.12r
   Using /dev/rtc interface to clock.
   Last drift adjustment done at 1176302627 seconds after 1969
   [snip]
   ioctl(RTC_SET_TIME) was successful. 


   Not adjusting drift factor because it has been less than a day since
   the last calibration.

Could the timidity init.d script K sequence number be adjusted to, say, 
00 or 01?
   /etc/rc0.d/K01timidity
   /etc/rc1.d/K01timidity
   /etc/rc6.d/K01timidity

My box runs Debian 4.0 whith kernel 2.6.18-4 amd64-k8.
Thanks in advance.

--
Gilles.