I think this problem has now gone away on my machine. I cannot be sure what
it was that helped. I removed all qt-* packages, and some of the
problematic packages mentioned as depending on the earlier versions. After
running
# emerge -utv world, I noted some dependencies, and may have
With regards to this:
I believe I'm in the same situation:
QUOTE
amit0 ~ # emerge -auvt world
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency
On Sunday 25 October 2009 11:43:59 Amit Dor-Shifer wrote:
With regards to this:
I believe I'm in the same situation:
SNIP
emerge: there are no ebuilds built with USE flags to satisfy
~x11-libs/qt-core-4.5.2[qt3support,-debug].
!!! One of the following packages is required to complete your
On 10/25/09, Amit Dor-Shifer ami...@oversi.com wrote:
!!! One of the following packages is required to complete your request:
- x11-libs/qt-core-4.5.2 (Change USE: +qt3support)
Have you tried doing what it says here, i.e., enabling
USE=qt3support in, e.g., make.conf? (Sorry if you've already
Amit Dor-Shifer ha scritto:
With regards to this:
I believe I'm in the same situation:
QUOTE
amit0 ~ # emerge -auvt world
These are the packages that would be merged, in reverse order:
Calculating dependencies... done!
!!! Multiple package instances within a single package slot have been
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
amit0 ~ # eselect profile show
Current make.profile symlink:
default/linux/amd64/10.0
amit0 ~ # euse -i qt3support
global use flags (searching: qt3support)
no matching entries found
local use flags (searching: qt3support)
Thanks econti ( arttu).
My point was that I don't have the relevant news listed, rather than
the actual solution to the issue.
Amit
econti wrote:
Amit Dor-Shifer ha scritto:
With regards to this:
I believe I'm in the same situation:
QUOTE
amit0 ~ # emerge -auvt world
These are the
On Sunday 25 October 2009 14:49:29 Alan E. Davis wrote:
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
Thank you Mr. MacKinnon:
On Sun, Oct 25, 2009 at 11:05 PM, Alan McKinnon alan.mckin...@gmail.com
Did you try the most straightforward (albeit lengthy) approach:
unmerge all of Qt
emerge world and let portage figure out what it wants to put back
How can I do this?
There is seldom a
On Sunday 25 October 2009 12:53:33 Amit Dor-Shifer wrote:
amit0 ~ # eselect profile show
Current make.profile symlink:
default/linux/amd64/10.0
You may want to change this to .../amd64/10.0/desktop or server depending on
what your machine is. Then I would think that the flags for
Yes. This is one of the issues I ran into. Done.
On Sun, Oct 25, 2009 at 11:13 PM, Mick michaelkintz...@gmail.com wrote:
On Sunday 25 October 2009 12:53:33 Amit Dor-Shifer wrote:
amit0 ~ # eselect profile show
Current make.profile symlink:
default/linux/amd64/10.0
You may want to
On Sunday 25 October 2009 15:11:36 Alan E. Davis wrote:
Thank you Mr. MacKinnon:
On Sun, Oct 25, 2009 at 11:05 PM, Alan McKinnon alan.mckin...@gmail.com
Did you try the most straightforward (albeit lengthy) approach:
unmerge all of Qt
emerge world and let portage figure out what it
To follow up, after removing qt (by mistake), and all the qt-* packages I
could find, this is what I found when running emerge -uDav world
x11-libs/qt-gui:4
('ebuild', '/', 'x11-libs/qt-gui-4.5.3-r1', 'merge') conflicts with
~x11-libs/qt-gui-4.5.2[-debug] required by ('ebuild', '/',
Thank you Alan.
On Sun, Oct 25, 2009 at 11:23 PM, Alan McKinnon alan.mckin...@gmail.comwrote:
Simplest way I can think of:
eix qt-
Scroll up and down and note which ones are installed, there's only 20 in
total
and the colourized output makes it easy to spot the installed ones. Unmerge
On Sunday 25 October 2009 15:26:19 Alan E. Davis wrote:
To follow up, after removing qt (by mistake), and all the qt-* packages I
could find, this is what I found when running emerge -uDav world
x11-libs/qt-gui:4
('ebuild', '/', 'x11-libs/qt-gui-4.5.3-r1', 'merge') conflicts with
I forgot to mention:
After rebuilding all of qt with this amount of changes, be prepared to rebuild
all of KDE-4 as well. Not doing this often results in weird behavviour that is
impossible to track down, hence the large elog warning in all the qt-*
ebuilds.
On Sunday 25 October 2009
I think that if default/linux/amd64/10.0 is a valid profile, it's
reasonable to expect that the relevant news item be listed on eselect.
Amit
Mick wrote:
On Sunday 25 October 2009 12:53:33 Amit Dor-Shifer wrote:
amit0 ~ # eselect profile show
Current make.profile symlink:
On Sunday 25 October 2009 14:20:00 Amit Dor-Shifer wrote:
I think that if default/linux/amd64/10.0 is a valid profile, it's
reasonable to expect that the relevant news item be listed on eselect.
It takes 1 minute to change it and try emerge -upDv world before you change it
back if you so
On Sun, 25 Oct 2009 15:23:24 +0200, Alan McKinnon wrote:
Simplest way I can think of:
eix qt-
Scroll up and down and note which ones are installed, there's only 20
in total and the colourized output makes it easy to spot the installed
ones. Unmerge those.
To see what's installed:
qlist
On Saturday 24 October 2009 02:46:32 Dale wrote:
Alan E. Davis wrote:
I have read a number of different explanations and suggestions, some
of them regarding an earlier, yet similar, tanglement between versions
of qt-*. I've tried a number of suggestions, and I have unmerged and
remerged
I have read a number of different explanations and suggestions, some of them
regarding an earlier, yet similar, tanglement between versions of qt-*.
I've tried a number of suggestions, and I have unmerged and remerged
packages.
I am now trying to individually merge packages with dependencies on
Alan E. Davis wrote:
I have read a number of different explanations and suggestions, some
of them regarding an earlier, yet similar, tanglement between versions
of qt-*. I've tried a number of suggestions, and I have unmerged and
remerged packages.
I am now trying to individually merge
I've tried alot of things, but I give up. Can someone help me with the knot
of dependencies that has been holding my system in hostage from any attempt
to update world, for weeks now?
This message asked if I want to merge these packages:
!!! The following update(s) have been skipped due to
On Donnerstag 22 Oktober 2009, Alan E. Davis wrote:
I've tried alot of things, but I give up. Can someone help me with the
knot of dependencies that has been holding my system in hostage from any
attempt to update world, for weeks now?
This message asked if I want to merge these packages:
Am Donnerstag 22 Oktober 2009 23:19:07 schrieb Alan E. Davis:
I've tried alot of things, but I give up. Can someone help me with the
knot of dependencies that has been holding my system in hostage from any
attempt to update world, for weeks now?
Please read your portage news, especially
26 matches
Mail list logo
