public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: meino.cramer@gmx.de
Subject: Re: [gentoo-user] nvidia-drivers conflicts
Date: Sat, 24 Apr 2010 01:23:13 +0200	[thread overview]
Message-ID: <201004240123.13469.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <20100423230846.GA6919@solfire>

On Saturday 24 April 2010 01:08:46 meino.cramer@gmx.de wrote:
> Hi,
> 
> before getting into too much trouble better I aask:
> While updateing I got the following message:
> 
>         ('ebuild', '/', 'x11-base/xorg-server-1.8.0', 'merge') conflicts
> with <x11-base/xorg-server-1.7.99 required by ('installed', '/',
> 'x11-drivers/nvidia-drivers-195.36.15', 'nomerge')
> 
> 
>         !!! The following update(s) have been skipped due to unsatisfied
> dependencies !!! triggered by backtracking:
>         x11-apps/xinit:0
> 
> 
> The first one I understand what I wants to say, but: Is the conflict
> based on the limition of the nvidia-driver not to run with
> xorg-server-1.8.0 even when recompiled after the new xorg-server
> is reinstalled or does the latter help to circumvent the problem?

The former:

http://bugs.gentoo.org/show_bug.cgi?id=315141#c3

> 
> What the second message wants to tell me is far beyond my knowledge ... :)

It's portage trying to tell you how those incompatible versions are in the 
list to be emerged. A backtrack is simply that - start with what you have, 
find out what pulled it in, and what pulled that in, till you come to the end 
(usually something in your world file).

Without digging into ebuilds, it looks like xinit pulls in xorg-x11 which 
pulls in xorg-server which conflicts with nvidia-drivers,.

This is a classic case of rule #1 of program output: never expose the 
underlying implementation in your output. That info is completely useless to 
most users and needs re-thinking. Decent programming practice says that output 
shout only be given if the user asks for it like that, with say a --debug 
option for example.

-- 
alan dot mckinnon at gmail dot com



      parent reply	other threads:[~2010-04-23 23:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-23 23:08 [gentoo-user] nvidia-drivers conflicts meino.cramer
2010-04-23 23:22 ` Peter Ruskin
2010-04-24  9:46   ` Alan McKinnon
2010-04-24 11:56     ` Peter Humphrey
2010-04-25 13:53       ` Peter Humphrey
2010-04-23 23:23 ` Alan McKinnon [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201004240123.13469.alan.mckinnon@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    --cc=meino.cramer@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox