| Summary: | kde-base/pykde-3.5.5-r2 depends on ~dev-python/PyQt-3.14.1, not in portage tree | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | boxcars |
| Component: | New packages | Assignee: | Gentoo KDE team <kde> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | gentoo.wayne |
| Priority: | High | ||
| Version: | 2008.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
boxcars
2008-10-29 21:43:37 UTC
Oops. Well, maybe it is time to stabilize one of the newer pykde ebuilds, since they don't seem to have any outstanding bugs. Let's see what pykde maintainers have to say. So far i can see that it is masked for reason. #164027 But i cant test it so you have to wait for someone working on kde3. The conclusion on that bug seemed to be that the newer pykde ebuilds built fine with the current stable dev-python/sip and dev-python/PyQt ebuilds. I guess it has not been verified yet by a KDE dev yet though, or else the pykde dependencies would have been updated in the tree... Related: kde-base/pykde-3.5.8[M], 3.5.9[M], 3.5.10[M] depend on PyQt-3.17.2, not in portage tree. kde-base/pykde-3.5.7[M] depends on PyQt-3.14.1, not in portage tree. There is thus no way pykde can be built on x86, even when unmasking. dev-python/pykde 3.16.2 builds ok and works for me. I do not know how the two packages are related. We (KDE team) have been talking about this. Our current opinion is that we should just nuke PyKDE-3.5.X. We're going to have a meeting this Thursday, so give us until that to reach a decision and to fix this issue. The remaining pykde-3.5 packages have been masked to be removed, but 3.5.5-r2 has already been dropped, so we can close this. |