Date: Sat, 3 Dec 2005 14:18:39 +0000 From: Daniel Bye <freebsd-questions@slightlystrange.org> To: freebsd-questions@freebsd.org Subject: Re: Trouble upgrading ports collection Message-ID: <20051203141839.GB35163@catflap.slightlystrange.org> In-Reply-To: <200512021520.31635.ringworm01@gmail.com> References: <439093D2.3020905@wanadoo.fr> <20051202221718.GA35163@catflap.slightlystrange.org> <200512021520.31635.ringworm01@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--H1spWtNR+x+ondvy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 02, 2005 at 03:20:30PM -0800, Michael C. Shultz wrote: > Thanks for the info, is this really the recommended fix??? >=20 > Remove nvidia-driver port, then upgrade xorg-clients. After that you can= =20 > reinstall nvidia-driver. >=20 > I read the above as xorg-clients conflicts with nvidia-driver, if it was = set=20 > this way here is what portmanager would do: >=20 > 1) when upgrading xorg-clients finds conflicting port nvidia-driver insta= lled > and removes it unless user chooses otherwise before 5 minute timeout >=20 > 2) Upgrade xorg-clients >=20 > Athe this point something would have to have a dependency on nvidia-driver > for it to be pulled back in automatically else the user is going to need = to > install it manaually... Well I can see how this situation is causing pro= blems=20 > anyways....... >=20 > Has this issue been resolved yet? From reading your references it seems > like this fixed the problem with xdriinfo.c: >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D76257=20 > State-Changed-From-To: open->closed=20 > State-Changed-By: anholt=20 > State-Changed-When: Wed Nov 30 01:24:24 GMT 2005=20 > State-Changed-Why: =20 > A patch has been committed to fix this.=20 >=20 > But I saw no other solution to handling the nvidia port. >=20 > -Mike I agree it seems a trifle convoluted, and yes, in the vast majority cases, portmanager does the right thing. However, for this one (in my experience, at least), it couldn't handle it. I don't remember removing the nvidia drivers, but I think I reinstalled portions of the XOrg=20 subsystem, in particular the libs. As I said, though, I don't remember exactly how I got it all working again... Not much help, I'm afraid - I just wanted to point the OP at the threads on the other list (which I read only sporadically) in case they proved helpful. As to whether it's fixed yet, I really couldn't say - I belong firmly in the camp of end users, not developers or testers. A big thanks for portmanager - it's nice not to have to wrestle with the package db all the time! Dan --=20 Daniel Bye PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc PGP Key fingerprint: 3B9D 8BBB EB03 BA83 5DB4 3B88 86FC F03A 90A1 BE8F _ ASCII ribbon campaign ( ) - against HTML, vCards and X - proprietary attachments in e-mail / \ --H1spWtNR+x+ondvy Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFDkak/hvzwOpChvo8RAjf7AKDonZG4VSmTuLYvcjedkc0yr0b94QCeLcKy KznzFvphu2d/n6OB1+5cblA= =tOar -----END PGP SIGNATURE----- --H1spWtNR+x+ondvy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051203141839.GB35163>