Ian> I'm going to try again. I have low tolerance for pain and breakage Ian> (that's why I run testing), but I see it can't be helped :-(
It works, so go ahead and close this report. There must have been some other variable that made it break when I first tried and I misplaced the blame. There are other aspects of the package that disappointed me, though, and for the moment prevent me from using it. 1/ While dbconfig-common creates the database, it does not create the initial tables (ie. run the script tables-postgres.sql). That must be done by hand, the README document from which that can be seen is quite terse and there is no README.Debian to help. (For example, the original README doesn't give the path to tables-postgres.sql, how am I supposed to know where it is?) 2/ apache configuration bit is installed, but apache is not restarted, and in fact the bit is not checked for consistency with main apache configuration. In my case, when I restarted apache it failed because mod_env wasn't enabled to deal with the SetEnv line. I am pretty sure I hadn't _removed_ mod_env, so the webcalendar bit actually doesn't work with default Debian apache configuration. The postinst should probably do "apache-modconf enable mod_env" to deal with this. 3/ Creating the settings.php file: I expected this to be handled by package postinst, then realizing it isn't I tried the web method, which just gives me a page with "webcalendar: Fatal Error" and nothing else. So then I go back to the README and read that I can just customize a file called settings.php.orig. Again no path, oh well, I do "dpkg -L webcalendar" - and realize there's no such file in the package. thanks for trying, though :-) -- A true pessimist won't be discouraged by a little success. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
