[gentoo-user] Re: qt3support conflict
On 06/27/2009 07:24 PM, Andrew Gaydenko wrote: On Sunday 28 June 2009 02:54:59 walt wrote: On 06/27/2009 03:32 PM, Andrew Gaydenko wrote: make.conf hasn't qt3support at all. Adding qt3support to qt-opengl shows... well... something horrible (see below) :-) //== emerge -pvDuN world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] x11-libs/qt-core-4.5.2 [4.5.1] USE=glib iconv qt3support ssl -debug -doc -pch 0 kB [ebuild U ] x11-libs/qt-test-4.5.2 [4.5.1] USE=iconv -debug -pch 0 kB [blocks b ]x11-libs/qt-test-4.5.2 (x11-libs/qt-test-4.5.2 is blocking x11-libs/qt-assistant-4.5.2, x11- I recently went through the same thing on ~amd64 and emerge made me uninstall every qt package before it would start building the updates. I have no idea why, but everything finally came out okay. I'd say go ahead and emerge -C all of those qt blockers as emerge suggests. Walt, thanks! At my case portage has ovecome those blocks without direct unmerging. Ah, I see portage wants to update my qt4 *again* today, and I see a new package comment that emerging qt will pull in more qt sub-packages than I probably want -- very true. So now I'm just emerging qt-core instead. I hope it has everything that VirtualBox needs. I'll see.
Re: [gentoo-user] Re: qt3support conflict
On Sunday 28 June 2009 16:12:26 walt wrote: On 06/27/2009 07:24 PM, Andrew Gaydenko wrote: On Sunday 28 June 2009 02:54:59 walt wrote: On 06/27/2009 03:32 PM, Andrew Gaydenko wrote: make.conf hasn't qt3support at all. Adding qt3support to qt-opengl shows... well... something horrible (see below) :-) //= = emerge -pvDuN world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] x11-libs/qt-core-4.5.2 [4.5.1] USE=glib iconv qt3support ssl -debug -doc -pch 0 kB [ebuild U ] x11-libs/qt-test-4.5.2 [4.5.1] USE=iconv -debug -pch 0 kB [blocks b ]x11-libs/qt-test-4.5.2 (x11-libs/qt-test-4.5.2 is blocking x11-libs/qt-assistant-4.5.2, x11- I recently went through the same thing on ~amd64 and emerge made me uninstall every qt package before it would start building the updates. I have no idea why, but everything finally came out okay. I'd say go ahead and emerge -C all of those qt blockers as emerge suggests. Walt, thanks! At my case portage has ovecome those blocks without direct unmerging. Ah, I see portage wants to update my qt4 *again* today, and I see a new package comment that emerging qt will pull in more qt sub-packages than I probably want -- very true. So now I'm just emerging qt-core instead. I hope it has everything that VirtualBox needs. I'll see. You do not need qt-anything in world. It is a library, and ebuilds pull it in as needed. Remove all mention of qt ebuilds from the world file and double check that things are still correct via a null output from emerge -uND world emerge --depclean Then add USE=qt3support to make.conf -- alan dot mckinnon at gmail dot com
[gentoo-user] Re: qt3support conflict
On 06/28/2009 12:51 AM, Andrew Gaydenko wrote: Trying to upgrade to qt 4.5.2: kde4 wants qt3support for qt-core: x11-libs/qt-core-4.5.2 (Change USE: +qt3support) (dependency required by x11-libs/qt-qt3support-4.5.2 [ebuild]) (dependency required by kde-base/kteatime-4.2.4 [installed]) (dependency required by kde-base/kdetoys-meta-4.2.4 [installed]) (dependency required by kde-base/kde-meta-4.2.4 [installed]) OK, let's try: adding qt3support to qt-core wants qt3support for qt-gui adding qt3support to qt-gui wants qt3support for qt-sql adding qt3support to qt-sql conflicts with x11-libs/qt-opengl - last one insits on -qt3support for qt-core. At ~amd64. Where is my mistake? You forgot to add qt3support to qt-opengl too :) Anyway, I find all this a bit strange. qt3support is on by default, why do you have to enable it explicitly? Did you put -qt3support in make.conf? If yes, you should remove it.
Re: [gentoo-user] Re: qt3support conflict
On Sunday 28 June 2009 02:23:38 Nikos Chantziaras wrote: On 06/28/2009 12:51 AM, Andrew Gaydenko wrote: Trying to upgrade to qt 4.5.2: kde4 wants qt3support for qt-core: x11-libs/qt-core-4.5.2 (Change USE: +qt3support) (dependency required by x11-libs/qt-qt3support-4.5.2 [ebuild]) (dependency required by kde-base/kteatime-4.2.4 [installed]) (dependency required by kde-base/kdetoys-meta-4.2.4 [installed]) (dependency required by kde-base/kde-meta-4.2.4 [installed]) OK, let's try: adding qt3support to qt-core wants qt3support for qt-gui adding qt3support to qt-gui wants qt3support for qt-sql adding qt3support to qt-sql conflicts with x11-libs/qt-opengl - last one insits on -qt3support for qt-core. At ~amd64. Where is my mistake? You forgot to add qt3support to qt-opengl too :) Anyway, I find all this a bit strange. qt3support is on by default, why do you have to enable it explicitly? Did you put -qt3support in make.conf? If yes, you should remove it. make.conf hasn't qt3support at all. Adding qt3support to qt-opengl shows... well... something horrible (see below) :-) //== emerge -pvDuN world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] x11-libs/qt-core-4.5.2 [4.5.1] USE=glib iconv qt3support ssl -debug -doc -pch 0 kB [ebuild U ] x11-libs/qt-test-4.5.2 [4.5.1] USE=iconv -debug -pch 0 kB [blocks b ] x11-libs/qt-test-4.5.2 (x11-libs/qt-test-4.5.2 is blocking x11-libs/qt-assistant-4.5.2, x11- libs/qt-opengl-4.5.2, x11-libs/qt-xmlpatterns-4.5.2, x11-libs/qt-dbus-4.5.2, x11-libs/qt-script-4.5.2, x11-libs/qt- svg-4.5.2, x11-libs/qt-qt3support-4.5.2, x11-libs/qt-gui-4.5.2, x11-libs/qt-webkit-4.5.2, x11-libs/qt-core-4.5.2, x11-libs/qt-sql-4.5.2) [ebuild U ] x11-libs/qt-script-4.5.2 [4.5.1] USE=iconv -debug -pch (-custom-cxxflags%) 0 kB [blocks b ] x11-libs/qt-script-4.5.2 (x11-libs/qt-script-4.5.2 is blocking x11-libs/qt-assistant-4.5.2, x11- libs/qt-opengl-4.5.2, x11-libs/qt-xmlpatterns-4.5.2, x11-libs/qt-dbus-4.5.2, x11-libs/qt-test-4.5.2, x11-libs/qt- svg-4.5.2, x11-libs/qt-qt3support-4.5.2, x11-libs/qt-gui-4.5.2, x11-libs/qt-webkit-4.5.2, x11-libs/qt-core-4.5.2, x11-libs/qt-sql-4.5.2) [ebuild U ] x11-libs/qt-sql-4.5.2 [4.5.1] USE=iconv mysql qt3support sqlite -debug (-firebird) -odbc -pch - postgres (-custom-cxxflags%) 0 kB [blocks b ] x11-libs/qt-sql-4.5.2 (x11-libs/qt-sql-4.5.2 is blocking x11-libs/qt-assistant-4.5.2, x11- libs/qt-opengl-4.5.2, x11-libs/qt-xmlpatterns-4.5.2, x11-libs/qt-dbus-4.5.2, x11-libs/qt-script-4.5.2, x11-libs/qt- test-4.5.2, x11-libs/qt-svg-4.5.2, x11-libs/qt-qt3support-4.5.2, x11-libs/qt-gui-4.5.2, x11-libs/qt-webkit-4.5.2, x11-libs/qt-core-4.5.2) [ebuild U ] x11-libs/qt-dbus-4.5.2 [4.5.1] USE=-debug -pch (-custom-cxxflags%) 0 kB [blocks b ] x11-libs/qt-dbus-4.5.2 (x11-libs/qt-dbus-4.5.2 is blocking x11-libs/qt-assistant-4.5.2, x11- libs/qt-opengl-4.5.2, x11-libs/qt-xmlpatterns-4.5.2, x11-libs/qt-script-4.5.2, x11-libs/qt-test-4.5.2, x11-libs/qt- svg-4.5.2, x11-libs/qt-qt3support-4.5.2, x11-libs/qt-gui-4.5.2, x11-libs/qt-webkit-4.5.2, x11-libs/qt-core-4.5.2, x11-libs/qt-sql-4.5.2) [ebuild U ] x11-libs/qt-xmlpatterns-4.5.2 [4.5.1] USE=-debug -pch (-custom-cxxflags%) 0 kB [blocks b ] x11-libs/qt-xmlpatterns-4.5.2 (x11-libs/qt-xmlpatterns-4.5.2 is blocking x11-libs/qt- assistant-4.5.2, x11-libs/qt-opengl-4.5.2, x11-libs/qt-dbus-4.5.2, x11-libs/qt-script-4.5.2, x11-libs/qt-test-4.5.2, x11-libs/qt-svg-4.5.2, x11-libs/qt-qt3support-4.5.2, x11-libs/qt-gui-4.5.2, x11-libs/qt-webkit-4.5.2, x11-libs/qt- core-4.5.2, x11-libs/qt-sql-4.5.2) [ebuild U ] x11-libs/qt-gui-4.5.2 [4.5.1-r2] USE=accessibility cups dbus glib mng qt3support tiff -debug -gtk% - nas -nis -pch -raster -xinerama (-custom-cxxflags%) (-gtkstyle%*) 0 kB
[gentoo-user] Re: qt3support conflict
On 06/28/2009 01:32 AM, Andrew Gaydenko wrote: On Sunday 28 June 2009 02:23:38 Nikos Chantziaras wrote: On 06/28/2009 12:51 AM, Andrew Gaydenko wrote: Trying to upgrade to qt 4.5.2: kde4 wants qt3support for qt-core: x11-libs/qt-core-4.5.2 (Change USE: +qt3support) (dependency required by x11-libs/qt-qt3support-4.5.2 [ebuild]) (dependency required by kde-base/kteatime-4.2.4 [installed]) (dependency required by kde-base/kdetoys-meta-4.2.4 [installed]) (dependency required by kde-base/kde-meta-4.2.4 [installed]) OK, let's try: adding qt3support to qt-core wants qt3support for qt-gui adding qt3support to qt-gui wants qt3support for qt-sql adding qt3support to qt-sql conflicts with x11-libs/qt-opengl - last one insits on -qt3support for qt-core. At ~amd64. Where is my mistake? You forgot to add qt3support to qt-opengl too :) Anyway, I find all this a bit strange. qt3support is on by default, why do you have to enable it explicitly? Did you put -qt3support in make.conf? If yes, you should remove it. make.conf hasn't qt3support at all. Adding qt3support to qt-opengl shows... well... something horrible (see below) :-) //== emerge -pvDuN world These are the packages that would be merged, in order: [...] I got that too, but portage (I'm on 2.1.6.13) has automatically resolved all blocks. Are you using Paludis? If yes, uninstall all packages that are to be upgraded and install them afterwards. Or wait for someone who actually knows a Paludis workaround for this.
Re: [gentoo-user] Re: qt3support conflict
On Sunday 28 June 2009 02:41:53 Nikos Chantziaras wrote: On 06/28/2009 01:32 AM, Andrew Gaydenko wrote: On Sunday 28 June 2009 02:23:38 Nikos Chantziaras wrote: On 06/28/2009 12:51 AM, Andrew Gaydenko wrote: Trying to upgrade to qt 4.5.2: kde4 wants qt3support for qt-core: x11-libs/qt-core-4.5.2 (Change USE: +qt3support) (dependency required by x11-libs/qt-qt3support-4.5.2 [ebuild]) (dependency required by kde-base/kteatime-4.2.4 [installed]) (dependency required by kde-base/kdetoys-meta-4.2.4 [installed]) (dependency required by kde-base/kde-meta-4.2.4 [installed]) OK, let's try: adding qt3support to qt-core wants qt3support for qt-gui adding qt3support to qt-gui wants qt3support for qt-sql adding qt3support to qt-sql conflicts with x11-libs/qt-opengl - last one insits on -qt3support for qt-core. At ~amd64. Where is my mistake? You forgot to add qt3support to qt-opengl too :) Anyway, I find all this a bit strange. qt3support is on by default, why do you have to enable it explicitly? Did you put -qt3support in make.conf? If yes, you should remove it. make.conf hasn't qt3support at all. Adding qt3support to qt-opengl shows... well... something horrible (see below) :-) //== emerge -pvDuN world These are the packages that would be merged, in order: [...] I got that too, but portage (I'm on 2.1.6.13) has automatically resolved all blocks. Are you using Paludis? If yes, uninstall all packages that are to be upgraded and install them afterwards. Or wait for someone who actually knows a Paludis workaround for this. No, I don't use Paludis. What do you mean saying has automatically resolved all blocks? Do you mean you have added those qt3support flags and started emerging and got successfull upgrading to 4.5.2 without any problems and in spite of those blocks?
[gentoo-user] Re: qt3support conflict
On 06/27/2009 03:32 PM, Andrew Gaydenko wrote: make.conf hasn't qt3support at all. Adding qt3support to qt-opengl shows... well... something horrible (see below) :-) //== emerge -pvDuN world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] x11-libs/qt-core-4.5.2 [4.5.1] USE=glib iconv qt3support ssl -debug -doc -pch 0 kB [ebuild U ] x11-libs/qt-test-4.5.2 [4.5.1] USE=iconv -debug -pch 0 kB [blocks b ]x11-libs/qt-test-4.5.2 (x11-libs/qt-test-4.5.2 is blocking x11-libs/qt-assistant-4.5.2, x11- I recently went through the same thing on ~amd64 and emerge made me uninstall every qt package before it would start building the updates. I have no idea why, but everything finally came out okay. I'd say go ahead and emerge -C all of those qt blockers as emerge suggests.
[gentoo-user] Re: qt3support conflict
On 06/28/2009 01:51 AM, Andrew Gaydenko wrote: On Sunday 28 June 2009 02:41:53 Nikos Chantziaras wrote: I got that too, but portage (I'm on 2.1.6.13) has automatically resolved all blocks. Are you using Paludis? If yes, uninstall all packages that are to be upgraded and install them afterwards. Or wait for someone who actually knows a Paludis workaround for this. No, I don't use Paludis. What do you mean saying has automatically resolved all blocks? Do you mean you have added those qt3support flags and started emerging and got successfull upgrading to 4.5.2 without any problems and in spite of those blocks? I did not add qt3support anywhere. It seems to be enabled by default here. Anyway, you went past that problem anyway. Your current is something else: the blockers. What portage version are you using? If portage won't resolve those blockers automatically for you, you can do it the traditional way. Unmerge all packages that would be updated and then update again. I would do it like this: emerge -aC `qlist -IC x11-libs/qt*:4` emerge -auDN world
Re: [gentoo-user] Re: qt3support conflict
On Sunday 28 June 2009 03:05:48 Nikos Chantziaras wrote:
On 06/28/2009 01:51 AM, Andrew Gaydenko wrote:
On Sunday 28 June 2009 02:41:53 Nikos Chantziaras wrote:
I got that too, but portage (I'm on 2.1.6.13) has automatically resolved
all blocks. Are you using Paludis? If yes, uninstall all packages that
are to be upgraded and install them afterwards. Or wait for someone who
actually knows a Paludis workaround for this.
No, I don't use Paludis. What do you mean saying has automatically
resolved all blocks? Do you mean you have added those qt3support flags
and started emerging and got successfull upgrading to 4.5.2 without any
problems and in spite of those blocks?
I did not add qt3support anywhere. It seems to be enabled by default
here. Anyway, you went past that problem anyway. Your current is
something else: the blockers. What portage version are you using? If
portage won't resolve those blockers automatically for you, you can do
it the traditional way. Unmerge all packages that would be updated
and then update again. I would do it like this:
emerge -aC `qlist -IC x11-libs/qt*:4`
emerge -auDN world
Thanks, Portage has resolved conflicts, I'm on 4.5.2 now. It seems like
qt3support
flags deletion doesn't work for me. Now, after upgrading, I have tried to
comment out
those flags in package.use and got conflicts (below).
===
emerge -pvDuN world
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] x11-libs/qt-core-4.5.2 USE=glib iconv ssl -debug -doc -pch
-qt3support* 0 kB
[ebuild R ] x11-libs/qt-gui-4.5.2 USE=accessibility cups dbus glib mng
tiff -debug -gtk -nas -
nis -pch -qt3support* -raster -xinerama 0 kB
[ebuild R ] x11-libs/qt-opengl-4.5.2 USE=-debug -pch -qt3support* 0 kB
Total: 3 packages (3 reinstalls), Size of downloads: 0 kB
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
x11-libs/qt-core:4
('ebuild', '/', 'x11-libs/qt-core-4.5.2', 'merge') pulled in by
~x11-libs/qt-core-4.5.2[glib,-debug,-qt3support] required by ('ebuild',
'/', 'x11-libs/qt-
gui-4.5.2', 'merge')
~x11-libs/qt-core-4.5.2[-debug,-qt3support] required by ('ebuild', '/',
'x11-libs/qt-
opengl-4.5.2', 'merge')
(and 19 more)
('installed', '/', 'x11-libs/qt-core-4.5.2', 'nomerge') pulled in by
=x11-libs/qt-core-4.5.1:4[qt3support,ssl] required by ('installed', '/',
'kde-
base/kfourinline-4.2.4', 'nomerge')
=x11-libs/qt-core-4.5.1:4[qt3support,ssl] required by ('installed', '/',
'kde-
base/ksystraycmd-4.2.4', 'nomerge')
=x11-libs/qt-core-4.5.1:4[qt3support,ssl] required by ('installed', '/',
'kde-base/bomber-4.2.4',
'nomerge')
(and 274 more)
x11-libs/qt-gui:4
('installed', '/', 'x11-libs/qt-gui-4.5.2', 'nomerge') pulled in by
~x11-libs/qt-gui-4.5.2[qt3support] required by ('installed', '/',
'x11-libs/qt-core-4.5.2',
'nomerge')
=x11-libs/qt-gui-4.4:4[qt3support,dbus] required by ('installed', '/',
'net-im/psi-0.12.1',
'nomerge')
~x11-libs/qt-gui-4.5.2[qt3support,accessibility,-debug] required by
('installed', '/', 'x11-
libs/qt-qt3support-4.5.2', 'nomerge')
(and 286 more)
('ebuild', '/', 'x11-libs/qt-gui-4.5.2', 'merge') pulled in by
~x11-libs/qt-gui-4.5.2[-debug,-qt3support] required by ('ebuild', '/',
'x11-libs/qt-opengl-4.5.2',
'merge')
(and 286 more)
It may be possible to solve this problem by using package.mask to
prevent one of those packages from being selected. However, it is also
possible that conflicting dependencies exist such that they are
impossible to satisfy simultaneously. If such a conflict exists in the
dependencies of two different packages, then those packages can not be
installed simultaneously.
For more information, see MASKED PACKAGES section in the emerge man page
or refer to the Gentoo Handbook.
[gentoo-user] Re: qt3support conflict
On 06/28/2009 03:35 AM, Andrew Gaydenko wrote: On Sunday 28 June 2009 03:05:48 Nikos Chantziaras wrote: On 06/28/2009 01:51 AM, Andrew Gaydenko wrote: On Sunday 28 June 2009 02:41:53 Nikos Chantziaras wrote: I got that too, but portage (I'm on 2.1.6.13) has automatically resolved all blocks. Are you using Paludis? If yes, uninstall all packages that are to be upgraded and install them afterwards. Or wait for someone who actually knows a Paludis workaround for this. No, I don't use Paludis. What do you mean saying has automatically resolved all blocks? Do you mean you have added those qt3support flags and started emerging and got successfull upgrading to 4.5.2 without any problems and in spite of those blocks? I did not add qt3support anywhere. It seems to be enabled by default here. Anyway, you went past that problem anyway. Your current is something else: the blockers. What portage version are you using? If portage won't resolve those blockers automatically for you, you can do it the traditional way. Unmerge all packages that would be updated and then update again. I would do it like this: emerge -aC `qlist -IC x11-libs/qt*:4` emerge -auDN world Thanks, Portage has resolved conflicts, I'm on 4.5.2 now. It seems like qt3support flags deletion doesn't work for me. Now, after upgrading, I have tried to comment out those flags in package.use and got conflicts. What profile do you use? (Find out with eselect profile show.)
Re: [gentoo-user] Re: qt3support conflict
On Sunday 28 June 2009 04:55:57 Nikos Chantziaras wrote: ... Thanks, Portage has resolved conflicts, I'm on 4.5.2 now. It seems like qt3support flags deletion doesn't work for me. Now, after upgrading, I have tried to comment out those flags in package.use and got conflicts. What profile do you use? (Find out with eselect profile show.) eselect profile show Current make.profile symlink: default/linux/amd64/2008.0 Something wrong with it?
[gentoo-user] Re: qt3support conflict
On 06/28/2009 04:12 AM, Andrew Gaydenko wrote: On Sunday 28 June 2009 04:55:57 Nikos Chantziaras wrote: ... Thanks, Portage has resolved conflicts, I'm on 4.5.2 now. It seems like qt3support flags deletion doesn't work for me. Now, after upgrading, I have tried to comment out those flags in package.use and got conflicts. What profile do you use? (Find out with eselect profile show.) eselect profile show Current make.profile symlink: default/linux/amd64/2008.0 Something wrong with it? Nope, I use the same. I guess I've no more ideas of why qt3support is enabled automatically on my machine, but not on yours. But in the end, it doesn't really matter that much; it's just a USE flag. The easiest way is to enable it in make.conf so that you won't have to create a dozen entries in package.use.
Re: [gentoo-user] Re: qt3support conflict
On Sunday 28 June 2009 02:54:59 walt wrote: On 06/27/2009 03:32 PM, Andrew Gaydenko wrote: make.conf hasn't qt3support at all. Adding qt3support to qt-opengl shows... well... something horrible (see below) :-) //== emerge -pvDuN world These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild U ] x11-libs/qt-core-4.5.2 [4.5.1] USE=glib iconv qt3support ssl -debug -doc -pch 0 kB [ebuild U ] x11-libs/qt-test-4.5.2 [4.5.1] USE=iconv -debug -pch 0 kB [blocks b ]x11-libs/qt-test-4.5.2 (x11-libs/qt-test-4.5.2 is blocking x11-libs/qt-assistant-4.5.2, x11- I recently went through the same thing on ~amd64 and emerge made me uninstall every qt package before it would start building the updates. I have no idea why, but everything finally came out okay. I'd say go ahead and emerge -C all of those qt blockers as emerge suggests. Walt, thanks! At my case portage has ovecome those blocks without direct unmerging.
