Installing python-sip4 remove hwdb-client-kde kubuntu-desktop python-qt4 on feisty

Bug #72302 reported by Allcolor-g
14
Affects Status Importance Assigned to Milestone
python-qt4 (Ubuntu)
Fix Released
Undecided
Unassigned
sip4-qt3 (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: python-sip4

Hi,

if I choose to install the last upgrade of python-sip4, apt want to remove hwdb-client-kde, kubuntu-desktop and python-qt4. It seems that python-qt4 requires an inferior version of python-sip4. Is it normal ?

Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

python-qt4 depends on python-sip4 (<< 4.5) but feisty version is 4.5-0ubuntu1.

This is probably a bug in python-qt4 package, not in python-sip4 (reject it if I'm wrong).

Revision history for this message
Caroline Ford (secretlondon) wrote :

In Edgy:

python-qt4 (4.0.1-1ubuntu1) depends on python-sip4 (<< 4.5) or python-sip4 (>= 4.4.5)

Current version in Edgy is python-sip4 (4.4.5-2ubuntu1) so it should be fine..

Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

confirming.

Changed in python-qt4:
status: Unconfirmed → Confirmed
Changed in sip4-qt3:
status: Unconfirmed → Confirmed
Revision history for this message
Sarah Kowalik (hobbsee-deactivatedaccount) wrote :

Creating pyuic4 wrapper...
Creating pyuic4 Makefile...
Creating pylupdate4 Makefile...
Creating pyrcc4 Makefile...
Creating pyqtconfig.py...
test ! -e failed-stamp && touch configure-stamp
rm -f failed-stamp
dh_testdir
rm -f failed-stamp
for version in 2.4;\
        do\
                cd build-$version;\
                /usr/bin/make || touch ../failed-stamp;\
                cd ..;\
        done
make[1]: Entering directory `/tmp/buildd/python-qt4-4.0.1/build-2.4'
make[2]: Entering directory `/tmp/buildd/python-qt4-4.0.1/build-2.4/QtCore'
g++ -c -pipe -fPIC -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_CORE_LIB -I. -I/usr/include/python2.4 -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtCore -I/usr/include/qt4 -I/usr/X11R6/include -o sipQtCorepart0.o sipQtCorepart0.cpp
g++ -c -pipe -fPIC -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_CORE_LIB -I. -I/usr/include/python2.4 -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtCore -I/usr/include/qt4 -I/usr/X11R6/include -o sipQtCorepart1.o sipQtCorepart1.cpp
g++ -c -pipe -fPIC -O2 -Wall -W -D_REENTRANT -DQT_NO_DEBUG -DQT_CORE_LIB -I. -I/usr/include/python2.4 -I/usr/mkspecs/linux-g++ -I/usr/include/qt4/QtCore -I/usr/include/qt4 -I/usr/X11R6/include -o sipQtCorepart2.o sipQtCorepart2.cpp
/usr/include/qt4/QtCore/qabstractfileengine.h: In copy constructor 'QFSFileEngine::QFSFileEngine(const QFSFileEngine&)':
/usr/include/qt4/QtCore/qabstractfileengine.h:153: error: 'QAbstractFileEngine::QAbstractFileEngine(const QAbstractFileEngine&)' is private
/usr/include/qt4/QtCore/qfsfileengine.h:36: error: within this context
sipQtCorepart2.cpp: In constructor 'sipQFSFileEngine::sipQFSFileEngine(const QFSFileEngine&)':
sipQtCorepart2.cpp:2783: note: synthesized method 'QFSFileEngine::QFSFileEngine(const QFSFileEngine&)' first required here
make[2]: *** [sipQtCorepart2.o] Error 1
make[2]: Leaving directory `/tmp/buildd/python-qt4-4.0.1/build-2.4/QtCore'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/tmp/buildd/python-qt4-4.0.1/build-2.4'
test ! -e failed-stamp && touch build-stamp
make: *** [build-stamp] Error 1
pbuilder: Failed autobuilding of package
 -> Aborting with an error
 -> unmounting dev/pts filesystem
 -> unmounting proc filesystem
 -> cleaning the build env
    -> removing directory /var/cache/pbuilder/build//8477 and its subdirectories

Bumping the build depends of python-sip4 wont help either.

Revision history for this message
Allcolor-g (allcolor) wrote :

It is resolved with today update.

Revision history for this message
Lionel Le Folgoc (mrpouit) wrote :

As Allcolor-g said, current python-qt4 package (4.1-0ubuntu1) fixed the issue:
Depends: python-sip4 (<< 4.6)
                python-sip4 (>= 4.5)

Changed in sip4-qt3:
status: Confirmed → Fix Released
Changed in python-qt4:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.