Message: previous - next
Month: September 2010

Re: [trinity-devel] python-kde3 (pykde) FTBFS - Solved!

From: Darrell Anderson <humanreadable@...>
Date: Thu, 23 Sep 2010 21:33:37 -0700 (PDT)
> > According to the failure error, kinputidalog.h has an
> undeclared class
> > QValidator. kinputidalog.h is installed from kdelibs.
> >
> OK, I have added a change to kdelibs in revision 1178028 to
> force
> inclusion of the tqt.h header when pykde uses the
> kinputdialog.h file. 
> You will need to rebuild/reinstall kdelibs, then try to
> rebuild pykde
> again.


I got python-kde3 (pykde3) to build!

I added the following:

#include <tqt.h>

 to three files:


All three header files are part of kdelibs. This would be the same change as made in kinputdialog.h.

If you officially patch those files I'll be sure to run another pass at building.

I built this pykde3 package from svn. According to, the svn version is 3.16.6 (pykde_version_str  = "3.16.6"). The latest version provided upstream is 3.16.7 ( Oddly, the upstream providers forgot to update the embedded version variable, which is still at 3.16.6 despite the tarball saying 3.16.7.


1. The folks who create python-kde3 refer to the package as pykde3. For consistency, should Trinity use the same name?

2. Should Trinity continue providing a version when upstream ( maintains package sources? You're not providing SIP and PyQt3 for that same reason.

I also built the upstream 3.16.7 with my new patches.

I still need to test building kdebindings against the three dependency packages, with both the svn version and upstream version of pykde3.