Date: Fri, 11 May 2007 17:30:10 -0500 From: WizLayer <wizlayer@gmail.com> To: Simon Castillo <smcas_m@yahoo.com.mx>, "FreeBSD, Questions" <freebsd-questions@freebsd.org> Subject: Re: Problem updating Freebsd ver 6.2 Message-ID: <200705111730.11048.wizlayer@gmail.com> In-Reply-To: <101899.64048.qm@web57814.mail.re3.yahoo.com> References: <101899.64048.qm@web57814.mail.re3.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart10342840.MFm7TZD1F4 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 11 May 2007 04:00:15 pm you wrote: > WizLayer <wizlayer@gmail.com> escribi=F3: On Friday 11 May 2007 11:23:11 = am=20 Simon Castillo wrote: > > > > Gerard Seibert escribi=F3: On Fri, 11 May 2007 > > 01:45:47 -0500 > > > > WizLayer wrote: > > > I could be wrong as I haven't used portmanager in a while (and that > > > was only a short time)... I believe that by default, portmanager > > > doesn't update dependencies more than a depth of 1 (maybe two?) > > > unless you use the -p flag. Then it updates dependencies all the way > > > back? A quick 'man portmanager' should verify this as I don't have > > > it installed anymore. > > > > Yes, update your ports tree and then run: > > > > portmanager -u -l -p > > > > You can substitute the 'f' flag for the 'p' one if you want to redo the > > system. > >=20 > > Hi Gerard: > > > > I tried your suggestion and I still have the same result. It updated > > couple more files, but the error (missing library) is still there. > > > > Any other suggestion? > > > > Thanks in advance > > > > Simon > > Top posting is generally considered rude, just so you know... > > Any rate, your next option is to locate the missing library, figure out > where your app thinks the library should be, and then ln to it so that yo= ur > app sees the link... > > Any particular reason you're using portmanager (I haven't used it recentl= y, > but have had bad experiences with it in the past. I'm one of those who > prefer portupgrade). Of course, I'm not saying this is a fault with > portmanager. I honestly don't know. I was just wondering why you were > using it (ie maybe it's been matured enough that I should check it out > again). > > Don't know what else to tell you. > > WizLayer > Hi WizLayer: > > Nope, no particular reason to use portmanager. I guess I'll one more that > suffer a bad experience. I don't see any other solution than re-install > every thing again. > > Thanks > > Simon > reinstalling everything isn't necessarily a bad thing. I do it on a regula= r=20 basis on my experiment boxes... Or are you talking about the whole OS? Th= at=20 would be a bit extreme, I think. I'm using 6.2s right now and am not having any problems with it at all, and= I=20 cvsup and portupgrade fairly regular. Before depopulating pkgdb, try=20 installing the portupgrade port, then cvsup, refetch the index file, and ru= n=20 your portupgrade -a. You can list the ports that need upgrading by using=20 the 'portversion | grep ">" | more' command. portupgrade will _only insta= ll=20 those listed if you tell it to 'portupgrade -aRrv' =20 If the problem still exists, and linking the file doesn't work, then mayhap= s a=20 reinstall of all the ports is necessary (I just don't see how unless you've= =20 specifically done something in your build options that put a ripple in the= =20 carpet). WizLayer =2D-=20 Life is better with a BSD. =46or more info, www.bsd.org. --nextPart10342840.MFm7TZD1F4 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBGRO5z2y0gbVRgU1ERAktZAKC6lfYujFvzs15j3FrFzbGrJ+BXuwCgrSzc F7K39jFxHgFjCGfhF2MCHJc= =k/PE -----END PGP SIGNATURE----- --nextPart10342840.MFm7TZD1F4--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200705111730.11048.wizlayer>