public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alan E. Davis" <lngndvs@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Uncle: qt-*:4 dependencies/blocks preventing world  update
Date: Sun, 25 Oct 2009 22:49:29 +1000	[thread overview]
Message-ID: <7bef1f890910250549n2a93425el213352f7d22f13c0@mail.gmail.com> (raw)
In-Reply-To: <4AE445F7.9010408@alice.it>

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

I finally was able to emerge -NuDav world, and revdep-rebuild passed the
system as clean.  However, when I try emerge -uDav world again, that same
message, or some permutation of it, is presented.

I have set the flags "dbus qt3support qt3 qt4" and so on.  So that's not
it.

I unmerged a number of the involved packages, that looked something like
"qt-*".  I did this just before running the more or less successful "emerge
-NuDav world".  A week ago, I ran "emerge -e world".  Perhaps I need to do
this again.

I've read a plethora of postings, such as a sticky post on the Gentoo
Forums, and some of these emails, as well as googling, and tried several
things.

When this all began, about three weeks ago, or longer, I noticed problems
with

   hplip
   python

I have python 3.1 and python 2.6 installed,  Some advice was seen to make
sure eselect is pointing to 2.6.  I also ran python-updater.

A new work week is starting, my system is responding normally, I will avoid
KDE4, and type this all shakes itself out, over the next week or so.

Thank you to those who have helped.  Good luck to others.

Alan

[-- Attachment #2: Type: text/html, Size: 1295 bytes --]

  reply	other threads:[~2009-10-25 12:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-22 21:19 [gentoo-user] Uncle: qt-*:4 dependencies/blocks preventing world update Alan E. Davis
2009-10-22 21:28 ` Volker Armin Hemmann
2009-10-23  5:33 ` Dirk Heinrichs
2009-10-24  1:29   ` Alan E. Davis
2009-10-24  1:46     ` Dale
2009-10-24 23:44       ` Mick
2009-10-25 11:43   ` Amit Dor-Shifer
2009-10-25 12:08     ` Mick
2009-10-25 12:53       ` Amit Dor-Shifer
2009-10-25 13:13         ` Mick
2009-10-25 13:18           ` Alan E. Davis
2009-10-25 14:20           ` Amit Dor-Shifer
2009-10-25 15:45             ` Mick
2009-10-25 12:26     ` Arttu V.
2009-10-26 13:00       ` Alan E. Davis
2009-10-25 12:35     ` econti
2009-10-25 12:49       ` Alan E. Davis [this message]
2009-10-25 13:05         ` Alan McKinnon
2009-10-25 13:11           ` Alan E. Davis
2009-10-25 13:23             ` Alan McKinnon
2009-10-25 13:27               ` Alan E. Davis
2009-10-25 17:00               ` Neil Bothwick
2009-10-25 13:26             ` Alan E. Davis
2009-10-25 13:36               ` Alan McKinnon
2009-10-25 13:37                 ` Alan McKinnon
2009-10-25 12:58       ` Amit Dor-Shifer

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=7bef1f890910250549n2a93425el213352f7d22f13c0@mail.gmail.com \
    --to=lngndvs@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /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