Date: Tue, 25 Jan 2005 16:14:14 +0000 From: Chris Hodgins <chodgins@cis.strath.ac.uk> To: "Michael C. Shultz" <reso3w83@verizon.net> Cc: freebsd-questions@freebsd.org Subject: Re: Reparing FreeBSD ports tree. Message-ID: <41F67056.60100@cis.strath.ac.uk> In-Reply-To: <200501250753.08740.reso3w83@verizon.net> References: <41F60A3F.7040908@myunix.net> <200501250627.33542.reso3w83@verizon.net> <41F6694A.9000600@cis.strath.ac.uk> <200501250753.08740.reso3w83@verizon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Michael C. Shultz wrote: > On Tuesday 25 January 2005 07:44 am, you wrote: > >>Michael C. Shultz wrote: >> >>>On Tuesday 25 January 2005 12:58 am, Christian Tischler wrote: >>> >>>>Hi everyone. >>>>My primary question is how to repair a broken ports tree. I did a >>>>portupgrade to CVS FreeBSD 4.9 RELEASE, and now my ports tree ist >>>>all screwed up. There are tons of wrong/failed/whatever >>>>dependencies and some ports wont work. >>>>How can I repair this problem without an complete reinstall of the >>>>system? I have a lot of services running for my local net and a >>>>huge amount of configurations. >>>>For exsample when I do /usr/ports/make index I get: >>>>---------- >>>># make index >>>>Generating INDEX - please wait..apsfilter-7.2.5_5: >>>>"/usr/ports/print/acroread5" non-existent -- dependency list >>>>incomplete ===> print/apsfilter failed >>>>*** Error code 1 >>>>1 error >>> >>>In /usr/ports/MOVED, >>> >>>"print/acroread5|print/acroread|2004-12-23|last Acrobat Reader port >>>remaining" >>> >>>which means this directory has been moved. >>> >>>My advice is to run sysutils/portmanager and NEVER ever run pkgdb >>>-F if you want to keep your dependencies from getting messed up. >>> >>>portmanager will automatically remove your installed >>>print/acroread5 because it has been removed from cvs, it does not >>>use INDEX files so they will become a non issue for you as well. >>> >>> The only way to protect your "large amount of configurations" is >>>to back them up! You never know when a port is going to over write >>>a configuration file so if they are real important to you, back >>>them up. >>> >>>-Mike >>>_______________________________________________ >>>freebsd-questions@freebsd.org mailing list >>>http://lists.freebsd.org/mailman/listinfo/freebsd-questions >>>To unsubscribe, send any mail to >>>"freebsd-questions-unsubscribe@freebsd.org" >> >>Is portmanager now the generally accepted way of keeping your ports >>updated? > > > There are people who prefer portmanager, but many have never tried it > and still recommend portupgrade. Here is a link with some information > and comments about portmanager. > > http://bsdnews.com/index.php3?story_start=5 > > >>Also, what's this "extract" thing I have seen mentioned in >>relation to this? >> >>Chris > > > What extract thing? Be more specific please. > > -Mike > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > Thanks for the link. I have been using portupgrade for a while now and find it very usable. I shall give portmanager a shot on my other system. Don't worry about the extract thing. I did some research and found what I was after....it did have nothing to do with portmanager. :) Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41F67056.60100>