[solved] x11-libs/qt-*-4.5.1 multiple blocks.

Message

Darth Marley · Post by **Darth Marley** » Sat Jun 06, 2009 4:28 am

Trying to do a usual emerge -uDN world, and the 4.5.1 versions of x11-libs/qt-*-4.5.1 seem to mutually block each other.

This results in me being unable to update until this is fixed in the tree.

What is the deal?

Code: Select all

[blocks b     ] <x11-libs/qt-dbus-4.5.1 ("<x11-libs/qt-dbus-4.5.1" is blocking x11-libs/qt-opengl-4.5.1, x11-libs/qt-svg-4.5.1-r1, x11-libs/qt-script-4.5.1, x11-libs/qt-test-4.5.1, x11-libs/qt-gui-4.5.1, x11-libs/qt-qt3support-4.5.1, x11-libs/qt-sql-4.5.1, x11-libs/qt-core-4.5.1)
[ebuild     U ] x11-libs/qt-script-4.5.1 [4.4.2] USE="iconv%*"
[blocks b     ] <x11-libs/qt-script-4.5.1 ("<x11-libs/qt-script-4.5.1" is blocking x11-libs/qt-opengl-4.5.1, x11-libs/qt-svg-4.5.1-r1, x11-libs/qt-dbus-4.5.1, x11-libs/qt-test-4.5.1, x11-libs/qt-gui-4.5.1, x11-libs/qt-qt3support-4.5.1, x11-libs/qt-sql-4.5.1, x11-libs/qt-core-4.5.1)
[ebuild     U ] x11-libs/qt-sql-4.5.1 [4.4.2-r1]
[blocks b     ] <x11-libs/qt-sql-4.5.1 ("<x11-libs/qt-sql-4.5.1" is blocking x11-libs/qt-opengl-4.5.1, x11-libs/qt-svg-4.5.1-r1, x11-libs/qt-script-4.5.1, x11-libs/qt-dbus-4.5.1, x11-libs/qt-test-4.5.1, x11-libs/qt-gui-4.5.1, x11-libs/qt-qt3support-4.5.1, x11-libs/qt-core-4.5.1)
[ebuild     U ] x11-libs/qt-test-4.5.1 [4.4.2] USE="iconv%*"
[blocks b     ] <x11-libs/qt-test-4.5.1 ("<x11-libs/qt-test-4.5.1" is blocking x11-libs/qt-opengl-4.5.1, x11-libs/qt-svg-4.5.1-r1, x11-libs/qt-script-4.5.1, x11-libs/qt-dbus-4.5.1, x11-libs/qt-gui-4.5.1, x11-libs/qt-qt3support-4.5.1, x11-libs/qt-sql-4.5.1, x11-libs/qt-core-4.5.1)
[ebuild     U ] x11-libs/qt-gui-4.5.1 [4.4.2-r3] USE="gtkstyle%* -raster%"
[blocks b     ] <x11-libs/qt-gui-4.5.1 ("<x11-libs/qt-gui-4.5.1" is blocking x11-libs/qt-opengl-4.5.1, x11-libs/qt-svg-4.5.1-r1, x11-libs/qt-script-4.5.1, x11-libs/qt-dbus-4.5.1, x11-libs/qt-test-4.5.1, x11-libs/qt-qt3support-4.5.1, x11-libs/qt-sql-4.5.1, x11-libs/qt-core-4.5.1)
[ebuild     U ] x11-libs/qt-qt3support-4.5.1 [4.4.2] USE="kde%* -phonon%"
[blocks b     ] <x11-libs/qt-qt3support-4.5.1 ("<x11-libs/qt-qt3support-4.5.1" is blocking x11-libs/qt-opengl-4.5.1, x11-libs/qt-svg-4.5.1-r1, x11-libs/qt-script-4.5.1, x11-libs/qt-dbus-4.5.1, x11-libs/qt-test-4.5.1, x11-libs/qt-gui-4.5.1, x11-libs/qt-sql-4.5.1, x11-libs/qt-core-4.5.1)
[ebuild     U ] x11-libs/qt-svg-4.5.1-r1 [4.4.2] USE="iconv%*"
[blocks b     ] <x11-libs/qt-svg-4.5.1 ("<x11-libs/qt-svg-4.5.1" is blocking x11-libs/qt-opengl-4.5.1, x11-libs/qt-script-4.5.1, x11-libs/qt-dbus-4.5.1, x11-libs/qt-test-4.5.1, x11-libs/qt-gui-4.5.1, x11-libs/qt-qt3support-4.5.1, x11-libs/qt-sql-4.5.1, x11-libs/qt-core-4.5.1)
[blocks b     ] >x11-libs/qt-opengl-4.4.2-r9999 (">x11-libs/qt-opengl-4.4.2-r9999" is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-gui-4.4.2-r3, x11-libs/qt-sql-4.4.2-r1, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-core-4.4.2-r2)
[ebuild     U ] x11-libs/qt-opengl-4.5.1 [4.4.2]
[blocks b     ] >x11-libs/qt-gui-4.4.2-r9999 (">x11-libs/qt-gui-4.4.2-r9999" is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-sql-4.4.2-r1, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-opengl-4.4.2, x11-libs/qt-core-4.4.2-r2)
[blocks b     ] >x11-libs/qt-sql-4.4.2-r9999 (">x11-libs/qt-sql-4.4.2-r9999" is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-gui-4.4.2-r3, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-opengl-4.4.2, x11-libs/qt-core-4.4.2-r2)
[blocks b     ] >x11-libs/qt-core-4.4.2-r9999 (">x11-libs/qt-core-4.4.2-r9999" is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-gui-4.4.2-r3, x11-libs/qt-sql-4.4.2-r1, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-opengl-4.4.2)
[blocks b     ] >x11-libs/qt-svg-4.4.2-r9999 (">x11-libs/qt-svg-4.4.2-r9999" is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-gui-4.4.2-r3, x11-libs/qt-sql-4.4.2-r1, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-opengl-4.4.2, x11-libs/qt-core-4.4.2-r2)
[blocks b     ] >x11-libs/qt-qt3support-4.4.2-r9999 (">x11-libs/qt-qt3support-4.4.2-r9999" is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-gui-4.4.2-r3, x11-libs/qt-sql-4.4.2-r1, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-opengl-4.4.2, x11-libs/qt-core-4.4.2-r2)
[blocks b     ] <x11-libs/qt-opengl-4.5.1 ("<x11-libs/qt-opengl-4.5.1" is blocking x11-libs/qt-svg-4.5.1-r1, x11-libs/qt-script-4.5.1, x11-libs/qt-dbus-4.5.1, x11-libs/qt-test-4.5.1, x11-libs/qt-gui-4.5.1, x11-libs/qt-qt3support-4.5.1, x11-libs/qt-sql-4.5.1, x11-libs/qt-core-4.5.1)
[blocks b     ] >x11-libs/qt-dbus-4.4.2-r9999 (">x11-libs/qt-dbus-4.4.2-r9999" is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-gui-4.4.2-r3, x11-libs/qt-sql-4.4.2-r1, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-opengl-4.4.2, x11-libs/qt-core-4.4.2-r2)
[blocks b     ] >x11-libs/qt-test-4.4.2-r9999 (">x11-libs/qt-test-4.4.2-r9999" is blocking x11-libs/qt-script-4.4.2, x11-libs/qt-dbus-4.4.2, x11-libs/qt-gui-4.4.2-r3, x11-libs/qt-sql-4.4.2-r1, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-opengl-4.4.2, x11-libs/qt-core-4.4.2-r2)
[blocks b     ] >x11-libs/qt-script-4.4.2-r9999 (">x11-libs/qt-script-4.4.2-r9999" is blocking x11-libs/qt-dbus-4.4.2, x11-libs/qt-gui-4.4.2-r3, x11-libs/qt-sql-4.4.2-r1, x11-libs/qt-qt3support-4.4.2, x11-libs/qt-svg-4.4.2, x11-libs/qt-test-4.4.2, x11-libs/qt-opengl-4.4.2, x11-libs/qt-core-4.4.2-r2)

dAlexis · Post by **dAlexis** » Sat Jun 06, 2009 5:35 am

Same thing on 64 bits. Your system is AMD64?

Darth Marley · Post by **Darth Marley** » Sat Jun 06, 2009 6:33 am

No, 32 bit.

This started just this week.
I suspect that many of these packages went "stable" this week.

DaggyStyle · Post by **DaggyStyle** » Sat Jun 06, 2009 6:48 am

you could start by unmerging all qt-*-r9999 packages

wklam · Post by **wklam** » Sat Jun 06, 2009 7:45 am

I had similar issue yesterday. I ended up doing unmerging all packages with keyword kde in it.

To get the list

Code: Select all

equery list |grep kde

To actually unmerge them:

Code: Select all

emerge --ask --unmerge `equery list |grep kde`

I assume that you have this in place [From the Gentoo kde-4.x howto]:

http://git.overlays.gentoo.org/gitweb/? ... ;hb=master

I then added the following in my /etc/portage/package.keyword:

Code: Select all

=x11-libs/qt-gui-4.5.1-r2 ~amd64
=x11-libs/qt-dbus-4.5.1 ~amd64
=x11-libs/qt-core-4.5.1 ~amd64
=x11-libs/qt-script-4.5.1 ~amd64
=x11-libs/qt-qt3support-4.5.1 ~amd64
=x11-libs/qt-sql-4.5.1 ~amd64
=x11-libs/qt-svg-4.5.1-r1 ~amd64
=x11-libs/qt-test-4.5.1 ~amd64
=x11-libs/qt-webkit-4.5.1 ~amd64
=x11-libs/qt-opengl-4.5.1 ~amd64
=x11-libs/qt-xmlpatterns-4.5.1 ~amd64
=x11-libs/qt-assistant-4.5.1 ~amd64
=kde-base/kde-env-4.2.4 ~amd64
=dev-python/PyQt4-4.4.4-r2 ~amd64
=x11-libs/qt-4.5.1 ~amd64

I followed the gentoo howto on kde-4.x "installation" part just like it was a brand new installation.

http://www.gentoo.org/proj/en/desktop/k ... -guide.xml

To install:

Code: Select all

emerge kde-meta:4.2

Afterwards, I ran a deep dep clean:

Code: Select all

emerge --ask --depclean
emerge --ask --update --newuse --deep @system @world
revdep

This worked for me.

The unmerging part is fast. The compiling of 250-ish packages took 12 hours on my 4 years old machine.

-William

Darth Marley · Post by **Darth Marley** » Sat Jun 06, 2009 10:55 am

Put another way, is this something that I can expect to be fixed by waiting and doing a sync next week, or is portage so broken that I have to uninstall KDE to my packages?

sparc · Post by **sparc** » Sat Jun 06, 2009 11:32 am

as stated earlier you have to remove all *-r9999 packages.

Portage is not broken, it is just a piece of software that does one thing very nicely. Once you add hard masked packages it is your responsibility afterwards. You shouldn't have added them in the first place.

Anyhow, the problem is that the two groups of packages are from different repositories and for that I *assume* that ordering is broken. Not portage. Package version ordering.

Darth Marley · Post by **Darth Marley** » Sun Jun 07, 2009 9:18 am

I don't see any '-r9999" packages installed.

Code: Select all

[I--] [  ] dev-libs/dbus-qt3-old-0.70 (0)
[I--] [  ] sys-apps/qtparted-0.4.5 (0)
[I--] [  ] virtual/poppler-qt3-0.10.5 (0)
[I--] [  ] x11-libs/qt-3.3.8b-r1 (3)
[I--] [  ] x11-libs/qt-core-4.4.2-r2 (4)
[I--] [  ] x11-libs/qt-dbus-4.4.2 (4)
[I--] [  ] x11-libs/qt-gui-4.4.2-r3 (4)
[I--] [  ] x11-libs/qt-opengl-4.4.2 (4)
[I--] [  ] x11-libs/qt-qt3support-4.4.2 (4)
[I--] [  ] x11-libs/qt-script-4.4.2 (4)
[I--] [  ] x11-libs/qt-sql-4.4.2-r1 (4)
[I--] [  ] x11-libs/qt-svg-4.4.2 (4)
[I--] [  ] x11-libs/qt-test-4.4.2 (4)
[I--] [  ] x11-libs/qt-xmlpatterns-4.4.2 (4)

They all seem to be issues with upgrading from 4.4.2 to 4.5.1 which I would think should not be such a headache.
Assuming that it is an issue with slotted versions, I may try to remove the 4.4.2 versions manually, install the 4.5.1, if emerge will then do it, and see what is broken.

The packages mentioned in the "blocked" list I posted are not installed. Those are issues with the tree bringing in blockers.

DaggyStyle · Post by **DaggyStyle** » Sun Jun 07, 2009 10:21 am

what is the output of eix of each package?

tiou42 · Post by **tiou42** » Sun Jun 07, 2009 10:54 am

I've resolved this sort of circulard dependency by unmasking the following packages in package.keywords

>=x11-libs/qt-script-4.5.1
>=x11-libs/qt-gui-4.5.1
>=x11-libs/qt-qt3support-4.5.1
>=x11-libs/qt-svg-4.5.1
>=x11-libs/qt-webkit-4.5.1
>=x11-libs/qt-opengl-4.5.1
>=x11-libs/qt-sql-4.5.1
>=x11-libs/qt-core-4.5.1
>=x11-libs/qt-dbus-4.5.1
>=x11-libs/qt-test-4.5.1
>=x11-libs/qt-xmlpatterns-4.5.1
>=x11-libs/qt-assistant-4.5.1
>=x11-libs/qt-4.5.1

xmaes · Post by **xmaes** » Sun Jun 07, 2009 11:15 am

sparc wrote:as stated earlier you have to remove all *-r9999 packages.

Portage is not broken, it is just a piece of software that does one thing very nicely. Once you add hard masked packages it is your responsibility afterwards. You shouldn't have added them in the first place.

Anyhow, the problem is that the two groups of packages are from different repositories and for that I *assume* that ordering is broken. Not portage. Package version ordering.

Nothing to do with different repositories, i am using stable with the official repository and i am having the same problem.
That one things that i dont like about gentoo, i went away 3 weeks came back update my system and everything went well but sometimes you try to update your system from one day to the other and it is broken...

MorpheuS.Ibis · Post by **MorpheuS.Ibis** » Sun Jun 07, 2009 12:01 pm

it looks like something in the deptree wants <qt-4.5.1 (else portage would/should unmerge old qt automatically), but all of qt needs to be of the same version. unmerging qt completely, emerging new qt, revdep-rebuild, and then running the update should do the trick
I have not seen such problems on my ~amd64, and I do emerge @world -DNu quite often

Darth Marley · Post by **Darth Marley** » Sun Jun 07, 2009 12:15 pm

Undoubtedly it is an intermittent problem, or everyone would complain.

I removed avidemux, PyQT, and poppler-bindings after getting meaningful output by emerging each package in the update list one at a time.
qt-core is now compiling.

yngwin · Post by **yngwin** » Sun Jun 07, 2009 11:59 pm

Looking at the original post: those are soft blocks (note the small b instead of capital B), which portage resolves automatically, so a normal world update would go smooth.

v_andal · Post by **v_andal** » Tue Jun 09, 2009 10:04 am

Hm. It is true. Even though emerge -p reported blocks, the actual emerge worked just fine. At least in my case

Out of curiosity, what causes these "blocks" to appear? It looks like regular upgrade, without any binary incompatibility. On my system, I don't have KDE at all, just few applications that use Qt.