Re: libsoqt3-20 is linked against Qt 4 (should be Qt 3)
Dear Release Team, Please unblock soqt to fix bug #593798 as described below. The change is only in debian files (control and rules). On Sat, Aug 21, 2010 at 04:43:40PM +0100, Adam D. Barratt wrote: On Sat, 2010-08-21 at 09:36 -0500, Steve M. Robbins wrote: libsoqt3 should be linked against Qt 3 but actually it is linked against Qt 4 (apart from the suffix, there is no difference between libsoqt3 and libsoqt4). I can see a few options: 1. Fix present source package to build libsoqt3-20 properly. That may take me a couple of weeks to get to. 2. Use present source package, removing libsoqt3-20 and libsoqt3-dev. This option takes a couple of days. 3. Package new upstream (1.5.0 released March 2010) that provides improved support for Qt4. This will take me a couple of weeks. Given that nothing in the archive uses the Qt3 libraries, either of #1 or #2 should be ok. Hopefully a fix could be found more quickly though. :) I tried option #1, but the code doesn't actually build with Qt3 anymore, so I went with option #2. Thanks, -Steve signature.asc Description: Digital signature
Re: libsoqt3-20 is linked against Qt 4 (should be Qt 3)
On Fri, 2010-09-03 at 01:18 -0500, Steve M. Robbins wrote: Please unblock soqt to fix bug #593798 as described below. The change is only in debian files (control and rules). [...] 1. Fix present source package to build libsoqt3-20 properly. That may take me a couple of weeks to get to. 2. Use present source package, removing libsoqt3-20 and libsoqt3-dev. This option takes a couple of days. [...] I tried option #1, but the code doesn't actually build with Qt3 anymore, so I went with option #2. Unblocked. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1283503278.17480.3922.ca...@kaa.jungle.aubergine.my-net-space.net
Re: Bug#593798: libsoqt3-20 is linked against Qt 4 (should be Qt 3)
On Sun, Aug 22, 2010 at 05:18:09PM +0100, David Claughton wrote: FWIW, I could be wrong, but it looks like configure is invoking pkgconfig to determine the QT version and it's always finding QT4 regardless of what QTDIR is set to. Maybe --enable-pkgconfig wasn't the default in the previous release? In any case adding --disable-pkgconfig *seems* to do the trick, although I didn't have time to test it thoroughly. Good idea, thanks. However, when I tried it, the build eventually failed with the following error. It seems that Qt3 doesn't have QImage::hasAlphaChannel(), etc: g++ -DHAVE_CONFIG_H -I../../../src -I../../../data -I../../../../src -I/usr/include/Inventor/annex -D_REENTRANT -I/usr/share/qt3/include -DSOQT_DEBUG=1 -DSOQT_INTERNAL -g -O2 -W -Wall -Wno-unused -Wno-multichar -Woverloaded-virtual -Wno-non-virtual-dtor -fno-builtin -finline-functions -Wreturn-type -Wchar-subscripts -Wparentheses -c ../../../../src/Inventor/Qt/SoQtImageReader.cpp -fPIC -DPIC -o .libs/SoQtImageReader.o In file included from ../../../../src/Inventor/Qt/SoQtImageReader.cpp:31: /usr/share/qt3/include/qimage.h: In member function 'bool QImageTextKeyLang::operator(const QImageTextKeyLang) const': /usr/share/qt3/include/qimage.h:61: warning: suggest parentheses around '' within '||' ../../../../src/Inventor/Qt/SoQtImageReader.cpp: In member function 'SbBool SoQtImageReader::readImage(const SbString, SbImage*) const': ../../../../src/Inventor/Qt/SoQtImageReader.cpp:65: error: 'class QImage' has no member named 'hasAlphaChannel' ../../../../src/Inventor/Qt/SoQtImageReader.cpp:66: error: 'class QImage' has no member named 'convertToFormat' ../../../../src/Inventor/Qt/SoQtImageReader.cpp:66: error: 'class QImage' has no member named 'hasAlphaChannel' ../../../../src/Inventor/Qt/SoQtImageReader.cpp:67: error: 'Format_ARGB32' is not a member of 'QImage' ../../../../src/Inventor/Qt/SoQtImageReader.cpp:67: error: 'Format_RGB32' is not a member of 'QImage' I think I'll just remove the Qt3 packages after all. -Steve signature.asc Description: Digital signature
Re: libsoqt3-20 is linked against Qt 4 (should be Qt 3)
On 21/08/10 15:36, Steve M. Robbins wrote: On Sat, Aug 21, 2010 at 02:52:48AM +0200, Gerhard Dirschl wrote: Package: libsoqt3-20 Version: 1.4.2~svn20090224-2 libsoqt3 should be linked against Qt 3 but actually it is linked against Qt 4 (apart from the suffix, there is no difference between libsoqt3 and libsoqt4). Wow. This was broken perhaps as long ago as March 2009 and no-one noticed until now. Must not be an important package :-) FWIW, I could be wrong, but it looks like configure is invoking pkgconfig to determine the QT version and it's always finding QT4 regardless of what QTDIR is set to. Maybe --enable-pkgconfig wasn't the default in the previous release? In any case adding --disable-pkgconfig *seems* to do the trick, although I didn't have time to test it thoroughly. Cheers, David. -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c714dc1.4060...@eclecticdave.com
Re: libsoqt3-20 is linked against Qt 4 (should be Qt 3)
On Sat, Aug 21, 2010 at 02:52:48AM +0200, Gerhard Dirschl wrote: Package: libsoqt3-20 Version: 1.4.2~svn20090224-2 libsoqt3 should be linked against Qt 3 but actually it is linked against Qt 4 (apart from the suffix, there is no difference between libsoqt3 and libsoqt4). Wow. This was broken perhaps as long ago as March 2009 and no-one noticed until now. Must not be an important package :-) Dear Debian-Release: SoQt is a library that provides Qt widgets for a visualization library (Coin). When I first packaged it, Qt was version 3. In early days of Qt4, it seemed important to provide SoQt for both Qt3 and Qt4. So I modified the soqt source package to produce both libsoqt3-20 (Qt3 version) and libsoqt4-20 (Qt4 version). This worked in the Lenny version. In March 2009, I updated the soqt sources and apparently broke this so that libsoqt3-20 also links against Qt4. :-) Since I'm not quite sure of the freeze timelines, I'd like your advice. First, it's clear that libsoqt3-20 (and libsoqt3-dev) shouldn't be released as-is. Is it possible to remove those two binary packages from testing while keeping the others (e.g. libsoqt4-20)? If so, I'd suggest that can be done immediately. Regardless of the above, I can prepare a new upload. I can see a few options: 1. Fix present source package to build libsoqt3-20 properly. That may take me a couple of weeks to get to. 2. Use present source package, removing libsoqt3-20 and libsoqt3-dev. This option takes a couple of days. 3. Package new upstream (1.5.0 released March 2010) that provides improved support for Qt4. This will take me a couple of weeks. Option #3 is my preference. If I have to invest the time to figure out what went wrong with linking to Qt3 and fix it, I'd prefer to also update the source at the same time. Given that SoQt is a minor library, I'd consider it low risk for the archive. If the release team feels otherwise, I can work with the present sources. Please advise whether an upload in 2 weeks (option #1) will make it into the next release or whether I should instead choose option #2. Thanks, -Steve signature.asc Description: Digital signature
Re: libsoqt3-20 is linked against Qt 4 (should be Qt 3)
On Sat, 2010-08-21 at 09:36 -0500, Steve M. Robbins wrote: libsoqt3 should be linked against Qt 3 but actually it is linked against Qt 4 (apart from the suffix, there is no difference between libsoqt3 and libsoqt4). [...] First, it's clear that libsoqt3-20 (and libsoqt3-dev) shouldn't be released as-is. Is it possible to remove those two binary packages from testing while keeping the others (e.g. libsoqt4-20)? If so, I'd suggest that can be done immediately. No; the packages will only get removed from testing when either the binary packages no longer exist in unstable or the source package is removed from testing. Regardless of the above, I can prepare a new upload. I can see a few options: 1. Fix present source package to build libsoqt3-20 properly. That may take me a couple of weeks to get to. 2. Use present source package, removing libsoqt3-20 and libsoqt3-dev. This option takes a couple of days. 3. Package new upstream (1.5.0 released March 2010) that provides improved support for Qt4. This will take me a couple of weeks. Given that nothing in the archive uses the Qt3 libraries, either of #1 or #2 should be ok. Hopefully a fix could be found more quickly though. :) [...] If the release team feels otherwise, I can work with the present sources. Please advise whether an upload in 2 weeks (option #1) will make it into the next release or whether I should instead choose option #2. How large is the diff between 1.4.2 and 1.5.0? Given that it would represent a year of development relative to unstable, I'm guessing it might be quite large. :-/ Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1282405420.19892.2504.ca...@kaa.jungle.aubergine.my-net-space.net
