From: Daniel Pielmeier <daniel.pielmeier@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] qt blockages...
Date: Tue, 20 Jan 2009 09:01:05 +0100 [thread overview]
Message-ID: <6142e6140901200001t7d29d980u83f279751c530ca7@mail.gmail.com> (raw)
In-Reply-To: <4974FC20.1090809@konstantinhansen.de>
2009/1/19 KH <gentoo-user@konstantinhansen.de>:
>
> This link was great help for me. Told me everything and how to read the
> blocker. So I did:
>
> #emerge -avC qt-4.3.3
> #emerge -DuavN world (This installed qt-4.4.2)
>
> But now I do have a problem. When I run
>
> #emerge --depclean -av
>
> I receive the following output:
> [snip]
>>>> These are the packages that would be unmerged:
>
> dev-db/sqlite
> selected: 2.8.16-r4
> protected: none
> omitted: 3.6.6.2
>
> x11-libs/qt
> selected: 4.4.2
> protected: none
> omitted: 3.3.8b-r1
>
> [snip some other qt-split-packages]
>
> What did I miss? This results in an infinite circle of unmerging and
> emerging.
>
I don't think --with-bdeps will solve this issue as qt- packages are
no build-time-dependencies they are needed at runtime too.
Did the affected packages got installed by your previous emerge world
command. My guess is that depclean wants to remove this packages
because they are simply not needed by other packages. Did they really
get pulled in when doing another world update after removing the
packages?
Maybe checking again your world file or the files in
/etc/portage/package.* for something suspicious is a good idea here.
--
Regards,
Daniel
next prev parent reply other threads:[~2009-01-20 8:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-18 22:26 [gentoo-user] qt blockages Mark Knecht
2009-01-18 22:54 ` Christopher Walters
2009-01-18 23:47 ` Mark Knecht
2009-01-19 10:31 ` Mick
2009-01-19 11:58 ` Dave Jones
2009-01-19 12:53 ` Markos Chandras
2009-01-20 11:46 ` Mick
2009-01-19 22:18 ` KH
2009-01-19 22:37 ` Mark Knecht
2009-01-19 23:13 ` Dale
2009-01-20 0:03 ` Paul Hartman
2009-01-20 0:18 ` Dale
2009-01-20 0:31 ` Mark Knecht
2009-01-20 1:19 ` Dale
2009-01-20 1:39 ` Mark Knecht
2009-01-20 0:46 ` Neil Bothwick
2009-01-20 1:36 ` Nickolas Fortino
2009-01-20 8:47 ` Neil Bothwick
2009-01-20 8:01 ` Daniel Pielmeier [this message]
2009-01-20 8:11 ` KH
2009-01-20 8:40 ` Daniel Pielmeier
2009-01-20 8:53 ` Nickolas Fortino
2009-01-20 9:12 ` KH
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=6142e6140901200001t7d29d980u83f279751c530ca7@mail.gmail.com \
--to=daniel.pielmeier@googlemail.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