Summary: | Skencil 0.6.16 can't start, "No module named Tkinter" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Aldo "xoen" Giambelluca <xoen.gnu> |
Component: | Current packages | Assignee: | Hanno Böck <hanno> |
Status: | RESOLVED DUPLICATE | ||
Severity: | major | CC: | ed |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Aldo "xoen" Giambelluca
2005-02-10 00:27:45 UTC
Problem solved...after an : #emerge --deep --update --newuse world ... Also portage updated (2.3.4-r1), but I think the problem is the tcltk use flag... I've tryed this : #USE="-tclt" emerge --newuse world Python is recompiled... ...now skencil not start with the same error before... ...so the solution is: #USE="tcltk" emerge python PS: My firt bug fixed ;) Skencil needs python built with tcltk, as we have no possibility to depend on specific package/useflag-combinations, I can't do anything about this at the moment. *** This bug has been marked as a duplicate of 2272 *** For now, couldn't we put a built_with_use check in pkg_setup()? forget that, see bug 103217. |