On Sat, 12 Feb 2005 14:38:23 -0500, Joel Gwynn <[EMAIL PROTECTED]> wrote: > Thanks for your response. See below [...] > > 6. what has changed since that installation? > > I can't think of anything. I may have upgraded something using apt-get
My recollection says that Debian likes to place the modules that it installs in /usr/lib while the ones that you install go into /usr/local/lib. Guess which one is first on Perl's library path? This can cause problems when you've installed the needed version of a module but Debian has placed an older version somewhere earlier in your path. > > 7. do you know about any other problems from others with Geo::Code::US (it > > has failed before according to CPAN) and Bundle::CPAN (looks okay)? > > Both failed. > > > 8. do you have all the prerequisites already installed for these two > > modules? > > > > I thought the CPAN module was supposed to handle the dependencies. [...] The CPAN module is supposed to handle dependencies. Debian is supposed to handle dependencies. When the two argue about what to do and how to do it, you lose. And they can't both be in control. My solution is to configure CPAN to pass the install-time argument UNINST=1, which causes CPAN to delete the conflicting Debian version of a module on install. (If I'm going to CPAN, I know what I want to do and Debian doesn't know enough to manage the packages for me.) Good luck locating the conflicting module versions. Cheers, Ben _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
