Every time I emerge world, qt will alternatingly upgrade to 3.3.4-r3 or downgrade to 3.3.3. From emerge -t, I figured out that mythtv requires <x11-libs/qt-3.3.4 But the next time I emerge world portage will instead notice that there is a newer version of qt and install 3.3.4. Reproducible: Always Steps to Reproduce:
Could you test, if mythtv-0.17-r1 works fine for you, please?
mythtv-0.18-r1 is fine because it doesn't require <x11-libs/qt-3.3.4. I still wonder why portage acted that way though. I havn't tried 0.17-r1, but since it doesnt have any maximum qt version, it should be fine too.
so can we assume it's fixed?
Um - no, forget about it. Tor: I explicitly asked for 0.17-r1 because this version is stable on amd64 and I can't test mythtv (beside if it compiles or not) and won't mark newer versions stable, before the maintainer does. media-tv herd: Could you open tracker bug, next time you're forced to break the stable tree, so such a problem can be resolved quickly!?
We didn't make that change. It was the AMD64 people that did it. Again, completely unaware. In fact, 0.17 lost it's stable marking on x86. It's basically a QT bug that had to be worked around.
Sorry Doug, assumed Jeremy would be a member of the media-tv herd. Well, since -r1 compiles and 0.17 was stable, it hopefuly works fine.
0.17 had a bug with dst when using qt-3.3.4. At the time, qt-3.3.4 was ~arch, so placing the <3.3.4 DEPEND did not break the stable tree. 0.17-r1 addressed the problem and works fine with qt-3.3.4.
>At the time, qt-3.3.4 was ~arch Qt 3.3.4 went stable in february, your change is from april. ;p
