All of a sudden I can't get python-tqt to build. Built ok for me a week or so ago.
No noticeable errors except, form the build output;
<< start output Do you accept the terms of the license? TQScintilla 1.7.1 is being used. Checking to see if the qtcanvas module should be built... Traceback (most recent call last): File "../configure.py", line 31, in <module> from sip4_tqt import sipconfig File "/usr/lib/python2.6/dist-packages/sip4_tqt/sipconfig.py", line 10, in <module> raise ImportError, 'No module named sipconfig; package python-sip-tqt-dbg not installed' ImportError: No module named sipconfig; package python-sip-tqt-dbg not installed [16791 refs] make: *** [dbg-build-2.6/configure-stamp] Error 1 make: *** Waiting for unfinished jobs.... This is the GPL version of PyTQt 3.18.1 (licensed under the GNU General Public License) for Python 2.7.3 on linux2.
end output
No error messages appear above this outpuyt, 'python-sip-tqt-dbg' is installed. Anybody any ideas?
All built form git, fresh debian wheezy (amd64) install, in this order;
tqt3 tqtinterface libcarddav libcaldav arts dbus-tqt dbus-1-tqt tqca-tls libart-lgpl avahi-tqt tdelibs tdebase sip4-tqt tqscintilla **python-tqt**
Cheers, Mike.
Hi Mike, looks like python-sip-tqt-dbg is not there or it can not be found. I would start making sure that the package is installed and that it is available for building. How do you build packages: locally or in a clean chroot environment?
Cheers Michele -------------------------------------------- Gio 3/7/14, Michael Howard mike@dewberryfields.co.uk ha scritto:
Oggetto: [trinity-devel] python-tqt FTBFS A: trinity-devel@lists.pearsoncomputing.net Data: Giovedì 3 luglio 2014, 21:18
All of a sudden I can't get python-tqt to build. Built ok for me a week or so ago.
No noticeable errors except, form the build output;
<< start output Do you accept the terms of the license? TQScintilla 1.7.1 is being used. Checking to see if the qtcanvas module should be built... Traceback (most recent call last): File "../configure.py", line 31, in <module> from sip4_tqt import sipconfig File "/usr/lib/python2.6/dist-packages/sip4_tqt/sipconfig.py", line 10, in <module> raise ImportError, 'No module named sipconfig; package python-sip-tqt-dbg not installed' ImportError: No module named sipconfig; package python-sip-tqt-dbg not installed [16791 refs] make: *** [dbg-build-2.6/configure-stamp] Error 1 make: *** Waiting for unfinished jobs.... This is the GPL version of PyTQt 3.18.1 (licensed under the GNU General Public License) for Python 2.7.3 on linux2.
end output
No error messages appear above this outpuyt, 'python-sip-tqt-dbg' is installed. Anybody any ideas?
All built form git, fresh debian wheezy (amd64) install, in this order;
tqt3 tqtinterface libcarddav libcaldav arts dbus-tqt dbus-1-tqt tqca-tls libart-lgpl avahi-tqt tdelibs tdebase sip4-tqt tqscintilla **python-tqt**
Cheers, Mike.
--
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
On 04/07/2014 03:07, Michele Calgaro wrote:
Hi Mike, looks like python-sip-tqt-dbg is not there or it can not be found. I would start making sure that the package is installed and that it is available for building. How do you build packages: locally or in a clean chroot environment?
Cheers Michele
Hi Michele,
I've tried tried it both ways, i.e. directly on a freshly installed PC and from within a freshly created chroot (on a freshly installed pc) and both ways fail the same way.
'python-sip-tqt-dbg ' is installed, as part of the build sequence, i.e. after each suite/prog is built (tqt3, tqtinterface etc) it is automatically installed and the next build sequence starts. Perhaps I'll try not installing and let the build sequence find and install the dependencies. If that fails (which I'm sure it will) I'll try and debug why the build system can't find the installed 'python-sip-tqt-dbg '.
Thanks for the input.
Cheers, Mike.
--
On 05/07/2014 09:02, Michael Howard wrote:
On 04/07/2014 03:07, Michele Calgaro wrote:
Hi Mike, looks like python-sip-tqt-dbg is not there or it can not be found. I would start making sure that the package is installed and that it is available for building. How do you build packages: locally or in a clean chroot environment?
Cheers Michele
Hi Michele,
I've tried tried it both ways, i.e. directly on a freshly installed PC and from within a freshly created chroot (on a freshly installed pc) and both ways fail the same way.
'python-sip-tqt-dbg ' is installed, as part of the build sequence, i.e. after each suite/prog is built (tqt3, tqtinterface etc) it is automatically installed and the next build sequence starts. Perhaps I'll try not installing and let the build sequence find and install the dependencies. If that fails (which I'm sure it will) I'll try and debug why the build system can't find the installed 'python-sip-tqt-dbg '.
As suspected, build still fails, complaining about missing 'python-sip-tqt-dbg', despite it being installed as a prerequisite;
The following NEW packages will be installed: libjs-jquery libtqscintilla-dev libtqscintilla7 python-sip-tqt python-sip-tqt-dbg python-sip-tqt-dev 0 upgraded, 6 newly installed, 0 to remove and 8 not upgraded. <snip> Setting up python-sip-tqt (4:14.0.0-0debian7.5.0) ... Setting up libjs-jquery (1.7.2+dfsg-1) ... Setting up python-sip-tqt-dev (4:14.0.0-0debian7.5.0) ... Setting up python-sip-tqt-dbg (4:14.0.0-0debian7.5.0) ... Setting up libtqscintilla7 (4:14.0.0-0debian7.5.0) ... Setting up libtqscintilla-dev (4:14.0.0-0debian7.5.0) ... Setting up python-tqt-build-deps (1.0) ... <snip>
I'll do some digging .....
Cheers, Mike.
Hi Mike, sorry for the late reply, I am going through a pretty busy period recently.
'python-sip-tqt-dbg ' is installed, as part of the build sequence, i.e. after each suite/prog is built (tqt3, tqtinterface etc) it is automatically installed and the next build sequence starts. Perhaps I'll try not installing and let the build sequence find and install the dependencies.
If I understand correctly from the above, you build a module/prog, then install it in your system, then move to the next one and so on. Correct? If so, here comes the next question: which command/tool do you use for building a module? debuild / pbuilder? dpkg-buildpackage? manual invocation of fakeroot debian/rules binary? Others? Perhaps python-sip-tqt-dbg is not installed in the right environment. For example you could have python-sip-tqt-dbg installed in your system, but debuild may not be able to find it.... or there may be other combinations.
Based on "how you build", let's see what the next step is, even though it seems strange that the problem came up all of a sudden in wheezy (jessie is a different beast, and there is no guarantee that what works now will still work the next hour.... been there many times :) )
Can you also upload a build log? It may help as well.
Cheers Michele
On 05/07/2014 13:47, Michele Calgaro wrote:
Hi Mike, sorry for the late reply, I am going through a pretty busy period recently.
Hey, no problem.
'python-sip-tqt-dbg ' is installed, as part of the build sequence, i.e. after each suite/prog is built (tqt3, tqtinterface etc) it is automatically installed and the next build sequence starts. Perhaps I'll try not installing and let the build sequence find and install the dependencies.
If I understand correctly from the above, you build a module/prog, then install it in your system, then move to the next one and so on. Correct? If so, here comes the next question: which command/tool do you use for building a module? debuild / pbuilder? dpkg-buildpackage? manual invocation of fakeroot debian/rules binary? Others?
Basically (using my own script to do various things befoore and after) I use tde-packaging environment and the commands 'mk-build-deps -ir debian/control' and 'dpkg-buildpackage -b -B -us -uc'
just running (command taken from rules file);
python configure.py \ -c -n /usr/include/tqscintilla \ -o /usr/lib -u -j 10 -d /usr/lib/python2.7/site-packages/python_tqt \ -l /usr/include/python2.7 \ -v /usr/share/sip/tqt -m /usr/lib/python2.7/config
in a copy of the source directoru succeeds so I guess there is something wrong with my build environment.
Perhaps python-sip-tqt-dbg is not installed in the right environment. For example you could have python-sip-tqt-dbg installed in your system, but debuild may not be able to find it.... or there may be other combinations.
I don't know much at all about python to be honest.
'python-sip-tqt-dbg' is definitely installed in the correct environment but 'getattr(sys, "pydebug")' is returning false, causing the failure, I think :)
Based on "how you build", let's see what the next step is, even though it seems strange that the problem came up all of a sudden in wheezy (jessie is a different beast, and there is no guarantee that what works now will still work the next hour.... been there many times :) )
Can you also upload a build log? It may help as well.
Output of the build attached.
Cheers, Mike.
On 05/07/2014 13:47, Michele Calgaro wrote:
Hi Mike, sorry for the late reply, I am going through a pretty busy period recently.
'python-sip-tqt-dbg ' is installed, as part of the build sequence, i.e. after each suite/prog is built (tqt3, tqtinterface etc) it is automatically installed and the next build sequence starts. Perhaps I'll try not installing and let the build sequence find and install the dependencies.
If I understand correctly from the above, you build a module/prog, then install it in your system, then move to the next one and so on. Correct? If so, here comes the next question: which command/tool do you use for building a module? debuild / pbuilder? dpkg-buildpackage? manual invocation of fakeroot debian/rules binary? Others? Perhaps python-sip-tqt-dbg is not installed in the right environment. For example you could have python-sip-tqt-dbg installed in your system, but debuild may not be able to find it.... or there may be other combinations.
Based on "how you build", let's see what the next step is, even though it seems strange that the problem came up all of a sudden in wheezy (jessie is a different beast, and there is no guarantee that what works now will still work the next hour.... been there many times :) )
Can you also upload a build log? It may help as well.
Cheers Michele
I must apologise, the script that I use was causing the build to use concurrent jobs masking the error. New build output attached.
The build fails with/at;
mkdir -p dbg-build-2.6 cd dbg-build-2.6 && echo yes \ | python2.6-dbg ../configure.py \ -c -n /usr/include/tqscintilla \ -o /usr/lib -u -j 10 \ -d /usr/lib/python2.6/dist-packages/python_tqt \ -l /usr/include/python2.6_d \ -v /usr/share/sip/tqt \ -m /usr/lib/python2.6/config_d \ CXXFLAGS_RELEASE="" CXXFLAGS="-O0 -g -I/usr/include/tqt" STRIP="" Traceback (most recent call last): File "../configure.py", line 31, in <module> from sip4_tqt import sipconfig File "/usr/lib/python2.6/dist-packages/sip4_tqt/sipconfig.py", line 10, in <module> raise ImportError, 'No module named sipconfig; package python-sip-tqt-dbg not installed' ImportError: No module named sipconfig; package python-sip-tqt-dbg not installed [16791 refs] make: *** [dbg-build-2.6/configure-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2
Cheers, Mike.
On 06/07/2014 17:11, Michael Howard wrote:
On 05/07/2014 13:47, Michele Calgaro wrote:
Hi Mike, sorry for the late reply, I am going through a pretty busy period recently.
'python-sip-tqt-dbg ' is installed, as part of the build sequence, i.e. after each suite/prog is built (tqt3, tqtinterface etc) it is automatically installed and the next build sequence starts. Perhaps I'll try not installing and let the build sequence find and install the dependencies.
If I understand correctly from the above, you build a module/prog, then install it in your system, then move to the next one and so on. Correct? If so, here comes the next question: which command/tool do you use for building a module? debuild / pbuilder? dpkg-buildpackage? manual invocation of fakeroot debian/rules binary? Others? Perhaps python-sip-tqt-dbg is not installed in the right environment. For example you could have python-sip-tqt-dbg installed in your system, but debuild may not be able to find it.... or there may be other combinations.
Based on "how you build", let's see what the next step is, even though it seems strange that the problem came up all of a sudden in wheezy (jessie is a different beast, and there is no guarantee that what works now will still work the next hour.... been there many times :) )
Can you also upload a build log? It may help as well.
Cheers Michele
I must apologise, the script that I use was causing the build to use concurrent jobs masking the error. New build output attached.
The build fails with/at;
mkdir -p dbg-build-2.6 cd dbg-build-2.6 && echo yes \ | python2.6-dbg ../configure.py \ -c -n /usr/include/tqscintilla \ -o /usr/lib -u -j 10 \ -d /usr/lib/python2.6/dist-packages/python_tqt \ -l /usr/include/python2.6_d \ -v /usr/share/sip/tqt \ -m /usr/lib/python2.6/config_d \ CXXFLAGS_RELEASE="" CXXFLAGS="-O0 -g -I/usr/include/tqt" STRIP="" Traceback (most recent call last): File "../configure.py", line 31, in <module> from sip4_tqt import sipconfig File "/usr/lib/python2.6/dist-packages/sip4_tqt/sipconfig.py", line 10, in <module> raise ImportError, 'No module named sipconfig; package python-sip-tqt-dbg not installed' ImportError: No module named sipconfig; package python-sip-tqt-dbg not installed [16791 refs] make: *** [dbg-build-2.6/configure-stamp] Error 1 dpkg-buildpackage: error: debian/rules build gave error exit status 2
It seems that it fails because 'python2.6-dbg ../configure.py' cannot find module sipconfig_d;
ImportError: No module named sipconfig_d
and indeed, it does not exist in the python2.6 tree, but does in the python2.7 tree.
Hi Michele,
My apologies for all this unnecessary noise. It turns out it was simply user error, i.e. my error.
python-sip-tqt had been built in parallel by mistake which meant sipconfig_d.py was missing from python-sip-tqt-dbg. oops!
Cheers, Mike.
My apologies for all this unnecessary noise. It turns out it was simply user error, i.e. my error.
No problem Mike. I have seen all your email just now, anyway ;-)
By the way, I suggest you spend a little time looking at pbuilder, it improves/simplifies the building process a lot. In Wheezy it is not much of a problem to build using dpkg-buildpackage because binutils is unlikely to change. But in Jessie binutils changes from time to time and if you want to move to the new binutils version, you would be forced to remove most of TDE packages, due to the strict dependency of libr0 to binutils version. With pbuilder/pdebuild you can rebuild TDE using the new binutils version in a separate environment, then just upgrade binutils and all TDE packages at the same time without problems. There are probably other ways to do the same thing, but I found pbuilder really straightforward once you hav eset it up. Here is a good HowTo https://wiki.ubuntu.com/PbuilderHowto
Cheers Michele
-
Michael Howard -
Michele Calgaro