Dave Howorth wrote:
> Sloan wrote: >> Maia is not available as a package, it's a manual install. The problem >> seems to be mixing components of perl from different worlds. > > Indeed. My difficulty is that you made the claim that installing modules > from CPAN broke Suse packages. As far as I can see, you have presented > no evidence to back up that claim. I saw enough evidence to take a course of action which restored the system to operational status. > The most likely explanation I can see is that a third-party package that > you installed (maia) has dependency problems. Without details, it's > impossible to establish whether maia itself is the source of the problem > or one or more of the modules it uses is. As Patrick mentioned, it caused him grief with spamassassin. That is the same thing that failed for me IIRC. There's no connection to mailguard, other than the fact that it relies on the underlying components e.g. spamassassin (which was a genuine suse package, compiled from a factory source rpm) > In any event, all that I can > see is that packages sometimes have bugs, not that the CPAN installation > mechanism is broken or that it should not be used on Suse systems. That could be, perhaps the package would have had bugs regardless. But the quick fix was to nuke the cpan stuff and use suse rpms which worked a treat. Joe -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
