Marek Habersack wrote: > So my guess is that for some weird reason the above pulls caudium-php4 and, > in consequence, caudium. I'm also wondering whether caudium asked you about > the port it should listen on - it should have done that precisely to avoid > clash with any installed webserver.
In my case, the upgrade was done with cron-apt, so I guess the question was suppressed. If I had done the apt-get dist-upgrade manually, I probably would have noticed something weird was afoot. > Now that I'm thinking, maybe it's a bug in apt not in php4. Either way, I'll > try to look closer into the issue and see where to assign the bug, Possibly the new version of the caudium-php4 package arrived in testing before libapache-mod-php4, and so apt took the rather drastic step of installing caudium to resolve the dependency. I don't know how I'd confirm that theory though. If it's true, I can prevent it happening again by uninstalling the "php4" package. Otherwise I might find myself with an unscheduled upgrade to Apache 2 next time :-) Adam -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
