On Mar 20, 2008, at 3:44 PM, Ryan Schmidt wrote: > On Mar 20, 2008, at 17:40, Nehemiah Dacres wrote: > >> On Thu, Mar 20, 2008 at 5:30 PM, Ryan Schmidt wrote: >> >>> On Mar 20, 2008, at 17:21, Nehemiah Dacres wrote: >>> >>>> On Thu, Mar 20, 2008 at 5:13 PM, Nehemiah Dacres wrote: >>>> >>>>> On Thu, Mar 20, 2008 at 5:09 PM, Ryan Schmidt wrote: >>>>> >>>>>> On Mar 20, 2008, at 15:03, Nehemiah Dacres wrote: >>>>>> >>>>>>> when i install git core after uninstalling git-core , git-core >>>>>>> +no_svn I recieve this error message >>>>>>> >>>>>>> ---> Activating git-core 1.5.3.7_0+doc >>>>>>> Error: Target org.macports.activate returned: Image error: / >>> opt/ >>>>>>> local/lib/perl5/5.8.8/darwin-2level/perllocal.pod already >>> exists >>>>>>> and does not belong to a registered port. Unable to >>> activate port >>>>>>> git-core. >>>>>>> Error: Status 1 encountered during processing. >>>>>> >>>>>> This problem was fixed in r34462 on 2008-02-25. That means >>> your port >>>>>> definitions are out of date. "sudo port selfupdate" to get the >>>>>> latest >>>>>> MacPorts and port definitions. Then "sudo port uninstall git-core >>>>>> @1.5.3.7_0+doc" and "sudo port install git-core", which will this >>>>>> time get you the current version which is 1.5.4.4. >>>>> >>>>> thanks, sorry it didn't occur to me to do that but im use to the >>>>> debian modle which requires network access to check the repo >>>>> everytime you install (so this one is superior) >>>> >>>> spoke too soon .. >>>> MacPorts base version 1.600 installed >>>> >>>> Downloaded MacPorts base version 1.600 >>>> >>>> The MacPorts installation is not outdated and so was not updated >>>> selfupdate done! >>> >>> That is correct. MacPorts base was not outdated, therefore MacPorts >>> base was not updated. However, your port definitions were outdated, >>> and they were updated, even if it didn't say so. Now try installing >>> git-core again. >> >> naturlaly i already tried, I should note that I am on a Tiger based >> system. should I use port clean? (how ever one might use that) > > Sure, you could try port clean. "sudo port clean --work git-core". > Then try installing again. Manually cleaning shouldn't be necessary > though if the portfile was updated, since MacPorts will see that the > portfile differs and will clean automatically. > > Does it try to install 1.5.4.4 now or still 1.5.3.7? > > If it still doesn't work, what is the error message? > > P.S: Please use Reply All when replying so everybody gets your reply, > not just me. It also helps the flow of conversation if you bottom- > post instead of top-post.
Let it be said, however, that not everyone agrees. When I've read all the other messages already, I don't like having to scroll. ///ark _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
