Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 246774 - dev-lang/tk-8.4.19 does not build a good python Tkinter module
Summary: dev-lang/tk-8.4.19 does not build a good python Tkinter module
Status: RESOLVED DUPLICATE of bug 225999
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: TCL/TK Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: tcltk-8.5
  Show dependency tree
 
Reported: 2008-11-14 20:58 UTC by Ferris McCormick (RETIRED)
Modified: 2008-11-16 09:01 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Trace file (on sparc) of the Tkinter failure with the tk-8.4.19 upgrade (tk-8.4.19.trace,2.15 KB, text/plain)
2008-11-14 21:02 UTC, Ferris McCormick (RETIRED)
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ferris McCormick (RETIRED) gentoo-dev 2008-11-14 20:58:44 UTC
On both sparc and on amd64, with tk-8.4.19 an attempt on python to use the Tkinter module from
import Tkinter
results in a failure;  I'll attach a traceback demonstrating the problem from the pysol package:

1) This is dev-lang/python-2.5.2-r7;
2) Rebuilding python for tk-8.4.19 makes no difference;
3) But after downgrading to {tcl, tk}-8.4.18, everything is fine again.

I'm reporting against tk because the problem appears with the {tcl, tk} version change.
Comment 1 Ferris McCormick (RETIRED) gentoo-dev 2008-11-14 21:02:44 UTC
Created attachment 171746 [details]
Trace file (on sparc) of the Tkinter failure with the tk-8.4.19 upgrade

This little traceback from python shows the problem it has using Tkinter with tk-8.4.19.  This trace is from a sparc system, but results are the same on amd64.  Test program is the pysol solitaire games package, and it has been completely stable for many years (although perhaps not as a Gentoo package).  pysol is pure python, using tk as its took kit.
Comment 2 Ferris McCormick (RETIRED) gentoo-dev 2008-11-14 21:06:03 UTC
Adding python people in case this is really theirs.
Comment 3 Federico Ferri (RETIRED) gentoo-dev 2008-11-15 22:37:20 UTC
which version of tk exactly doesn't spots this problem?
is really 8.4.18, or perhaps it is 8.4.18-r1?

because since 8.4.18-r1 ebuild includes a patch that *should* have solved this problem.

please also tell me your version of x11-proto/xproto.
Comment 4 Ferris McCormick (RETIRED) gentoo-dev 2008-11-16 00:08:16 UTC
On both failing systems, xproto-7.0.13.  But here we go:
On the failing systems, genlop tells us:

Sun Oct 26 14:09:15 2008 >>> dev-lang/tk-8.4.19

Changelog tells us:


 27 Oct 2008; Federico Ferri <mescalinum@gentoo.org>
  +files/tk-8.4-lastevent.patch, +tk-8.4.18-r1.ebuild, tk-8.4.19.ebuild:
  adding patch 8.4-lastevent, fixes bug #225999

And if we rebuild tk-8.4.19 to include that patch, everything is fine.  So for me, it was fixed a day after I installed the version of tk which fails.  For me, this is fixed; I'll leave it to you to close in case there is something else lurking in the background.

I guess this argues that when a very small change fixes something, a version bump is a good idea.
Comment 5 Ferris McCormick (RETIRED) gentoo-dev 2008-11-16 00:10:07 UTC
Oh, there is a misprint in the ebuild for tk-8.4.19 --- you have

>=x11-proto/xproto-7.0.3

but you need:
>=x11-proto/xproto-7.0.13
Comment 6 Federico Ferri (RETIRED) gentoo-dev 2008-11-16 09:01:26 UTC
ok, so you installed tk-8.4.19 in the meanwhile of two commits. nice timing! ;)

I rev bumped the ebuild, in order to eliminate this problem, and I corrected the typo.

I'll mark this bug as a duplicate of bug #225999 just for tracking purposes.

thank you

*** This bug has been marked as a duplicate of bug 225999 ***