� Guerrero wrote:
On Tue, 11 Sep 2007 03:36:13 +0200
Volker Armin Hemmann <[EMAIL PROTECTED]> wrote:

On Dienstag, 11. September 2007, Roy Wright wrote:
Howdy,

Well, I had to local mask

=x11-base/xorg-server-1.4-r1
=x11-base/xorg-server-1.4
=x11-base/xorg-x11-7.3

today to keep portage from blocking.  My guess
is that eventually a new version of nvidia-drivers
will be available and a new revision of xorg-server
will arrive that will support it (no longer block all
versions of nvidia-drivers).

Until that time will probably just keep masking
xorg-server and hope I remember to unmask
xorg-x11 at that time.

This seems inelegant.  So I'm hoping someone
has a better approach.

The really inelegant solution would be not to have the blocker. Most people would just update without looking even at the emerge -puDvN world output, and them complain on a huge and
useless thread on the forums, because something broke :P

If you have the blocker, you can't screw up the thing. Blockers
are the only solution for incompatible packages, and the new xorg
version is incompatible with all the nvidia-drivers version. In
fact, no future version of xorg will fix this, since it is completely
nvidia-side. So, I would change your snipped above by this one:

=x11-base/xorg-server-1.4-r1
=x11-base/xorg-server-1.4
=x11-base/xorg-x11-7.3

Note, the '>=' in front of the packages, those are not quotations
starting with '>', but '>=', because any new version will have the
same problem (since as I said, the problem is in the drivers, that
are just outdated).

If you have to incompatible packages, you need to decide what
your priority is, period. There is no way around that, until
nvidia decides to release a new version that is compatible with
the new abi.


remove the blocker? the current nvidia-drivers work fine, if you add -ignoreAbi to your X-start script (like kdm conf).

So the nvidia people say. Though I can confirm that in my installation
it doesn't work. It just lockups (and yes, I am sure that X composite
was off, because I always have it off).

The lockup is probably caused by having the hal use flag set when you compile xorg-server. If you disable it you should be able to run the X server without conflicting with hal/dbus which was the problem.
--
[EMAIL PROTECTED] mailing list

Reply via email to