| Summary: | ebuild information outdated | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Nuno Alexandre <ikaro> |
| Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED INVALID | ||
| Severity: | trivial | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
no, the problem will most likely hit on an 2.2 -> 2.4 upgrade because the engines (which are then still in 2.2 dir) can't be found by gtk+ 2.4. So this is still correct for the stable tree. |
The ebuild information is outdated. einfo "For gtk themes to work correctly after an update, you might have to rebuild your theme engines." einfo "Executing 'qpkg -f -nc /usr/lib/gtk-2.0/2.2.0/engines | xargs emerge' should do the trick if" einfo "you upgrade from gtk+-2.2 to 2.4 (requires gentoolkit)." The correct information should be: qpkg -f -nc /usr/lib/gtk-2.0/2.4.0/engines | xargs emerge' Reproducible: Always Steps to Reproduce: 1. 2. 3.