[Thread Prev][Thread Next][Thread Index]

Re: PM error after RH5.1->5.2 upgrade



Same problem. No idea how to fix it and I'd really like to. My initial
opinion is that there should be *no* modules that are private to PM. They
should all go into the public perl site-perl directory. This doesn't fix
anything but it would eliminate the perlTk module from the PM
distribution.

-- 
-Time flies like the wind. Fruit flies like a banana. steveo@xxxxxxxxxxxxxx
-Stranger things have happened but none stranger than this. Steven W. Orr-
Does your driver's license say Organ Donor?Black holes are where God \
-------divided by zero. Listen to me! We are all individuals!---------

On Mon, 14 Dec 1998, Derek R. Pizzagoni wrote:

=>Has anyone successfully run PilotManager on RedHat 5.2?  I upgraded last
=>month, and have not been able to run PilotManager since.  I have
=>received suggestions about installing a new version of Tk, but that's
=>about it.
=>
=>I have uninstalled the Tk rpm, and reinstalled it, but no help.  The
=>only solution I can think of is to revert back to RedHat 5.1 (which will
=>probably require a complete reload of my system), or revert one rpm at a
=>time, until I find the offending one.
=>
=>I'd really like to know if anyone has gotten it to work with 5.2 before
=>I go through the entire system reload.
=>
=>Thanks in advance for any help.

------------------------------------------------------------------------
***********************************************************
*             This is a public mailing list!              *
* Please do not publish Sun proprietary information here! *
*        -  -  -  -  -  -  -  -  -  -  -  -  -  -         *
*             http://www.moshpit.org/pilotmgr             *
***********************************************************


SourceForge.net Logo