Well, I have a few problems on that. One is that I can't for the life of me find it's garage. It looks like it was uploaded as a binary image, so maybe it doesn't have one? Second, I've not made/submitted a package, and am not up to snuff on how to do it (even after prodding a bit... it's complex to put it mildly).

Understand, what I did was a hack. Literally all I did was un-ar the debian, un-tar the control files, delete "ba" out of the first line of the postinst script and re-tar/ar the whole thing back into the original debian. I didn't change the content files at all, nor did a re-build anything source code wise. This was purely a config script issue (which is why the MD5 signature for the content tar hasn't changed, so dpkg isn't complaining about it).

Were there a web interface where I could check out/in the script to fix it and trigger a build I would happily do that. If that exists and I just missed it, please do let me know where it is and I'll be happy make the change. But the system I found (requiring a build environment, dependency source packages installed, a key setup for talking to the SCM system, etc) is a little much for me to pick up right now to make a 2 character change... (Especially when the maintainer is active and chatty... )