Bug#778085: qt4-x11: ftbfs with GCC-5
On Tuesday 10 March 2015 02:07:49 Matthias Klose wrote: On 03/09/2015 02:04 PM, Lisandro Damián Nicanor Pérez Meyer wrote: Upstream's patch is available at https://codereview.qt-project.org/#/c/106514/ It's still failing to integrate due to tests failing, so we still need to fix stuff before this is fixed. [sni] could you elaborate which tests are failing? Sorry for the late reply. The integration tests, but they where failing due to other reasons. I'm about to upload a new upstream snapshot which should solve this issues, but I'm not closing the bug as requested. Kinds regards, Lisandro. -- Simulations are like miniskirts, they show a lot and hide the essentials. Hubert Kirrman Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
qt5 symbols in raspbian jessie.
I meant to bring this up earlier but didn't get arround to it. In raspbian jessie we have encountered some symbols differences from Debian armhf, so-far i've been marking the symbols in question as optional but i'm not positive if this is the right thing to do. You can see our debdiffs at http://debdiffs.raspbian.org/main/q/qtdeclarative-opensource-src/qtdeclarative-opensource-src_5.3.2-4%2brpi1.debdiff http://debdiffs.raspbian.org/main/q/qtwebkit-opensource-src/qtwebkit-opensource-src_5.3.2%2bdfsg-3%2brpi1.debdiff Are these symbols just template insanciations that can be safely marked as optional or is there more to it than that? -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5525c2d3@manchester.ac.uk
Bug#561759: marked as done (qt4-x11: predictable random number generator used)
Your message dated Wed, 08 Apr 2015 19:19:39 -0300 with message-id 2179690.C2ZR82Oekj@luna and subject line Not applicable since a long time ago has caused the Debian Bug report #561759, regarding qt4-x11: predictable random number generator used to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 561759: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561759 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- package: qt4-x11 version: 4:4.5.3-4 severity: important tags: security hello, it has been discovered that all of the major web browsers use a predictable pseudo-random number generator (PRNG), which has at a minimum the consequences described in [0]. please check whether this package is affected. [0] http://www.trusteer.com/temporary-user-tracking-in-major-browsers ---End Message--- ---BeginMessage--- Version: 4:4.8.2+dfsg-11 We are building the webkit part outside the qt4 tree since a long time ago, even in Wheezy. According to the dates of the bug this should neither be a problem anymore in the qtwebkit code. -- perezmeyer: Gus no tiene inet :-( PabloOdorico: oh perezmeyer: te mando una copia de lo que hagamos esta noche PabloOdorico: de ultima mandame un loro del parque con una flash en la pata ;) Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part. ---End Message---
Bug#782063: qtwebkit-opensource-src: FTBFS on sparc
On Tuesday 07 April 2015 09:40:30 Bálint Réczey wrote: Source: qtwebkit-opensource-src Version: 5.3.2+dfsg-4 Severity: important Dear Maintainer, The package fails to build properly on build official build boxes due to many missing symbols on sparc [1]. The lack of Qt development libraries prevent many other packages from building on sparc including Wireshark. Thanks, Balint https://buildd.debian.org/status/fetch.php?pkg=qtwebkit-opensource-srcarch= sparcver=5.3.2%2Bdfsg-4stamp=1427981198 It will be resolved in the next upload. Building webkit just for symbols stuff on non-release archs it's really a waste of power and time. -- perezmeyer: Gus no tiene inet :-( PabloOdorico: oh perezmeyer: te mando una copia de lo que hagamos esta noche PabloOdorico: de ultima mandame un loro del parque con una flash en la pata ;) Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Re: qt5 symbols in raspbian jessie.
On Thursday 09 April 2015 01:07:47 peter green wrote: I meant to bring this up earlier but didn't get arround to it. In raspbian jessie we have encountered some symbols differences from Debian armhf, so-far i've been marking the symbols in question as optional but i'm not positive if this is the right thing to do. You can see our debdiffs at http://debdiffs.raspbian.org/main/q/qtdeclarative-opensource-src/qtdeclarati ve-opensource-src_5.3.2-4%2brpi1.debdiff http://debdiffs.raspbian.org/main/q/qtwebkit-opensource-src/qtwebkit-openso urce-src_5.3.2%2bdfsg-3%2brpi1.debdiff Are these symbols just template insanciations that can be safely marked as optional or is there more to it than that? $ c++filt _ZN3WTF22isMainThreadOrGCThreadEv WTF::isMainThreadOrGCThread() Generally default constructors and destructors might appear and dissapear from gcc version to other. Check the header for the relevant file. $ c++filt _ZNSt8_Rb_treeISt4pairIiyES1_St9_IdentityIS1_ESt4lessIS1_ESaIS1_EE16_M_insert_uniqueIS1_EES0_ISt17_Rb_tree_iteratorIS1_EbEOT_ std::pairstd::(and more foo) Template instantiations are normally optional. Moreover should not expose any std:: symbol. So they are normally optional. There is a page in KDE's techbase wiki that explains all these, but as a general rule check the headers provided in the package. If the symbols in there have not changed then they are usually fine. -- Simulations are not data. In God we trust, all the others must supply data. Walter Opyd, Show Me The Data IEEE Spectrum's reader's comments, http://www.spectrum.ieee.org/nov04/4004 Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/ signature.asc Description: This is a digitally signed message part.
Bug#782153: qtbase-opensource-src: debian/rules clean fails
Source: qtbase-opensource-src Severity: minor It's hard to get back into a clean state (e.g. when trying to patch): / | make[3]: Entering directory '/usr/local/src/debian/qtbase-opensource-src-5.3.2+dfsg/qmake' | rm -f project.o option.o property.o main.o ioutils.o proitems.o qmakevfs.o qmakeglobals.o qmakeparser.o qmakeevaluator.o qmakebuiltins.o makefile.o unixmake2.o unixmake.o mingw_make.o winmakefile.o projectgenerator.o meta.o makefiledeps.o metamakefile.o xmloutput.o pbuilder_pbx.o msvc_vcproj.o msvc_vcxproj.o msvc_nmake.o msvc_objectmodel.o msbuild_objectmodel.o gbuild.o cesdkhandler.o qtextcodec.o qutfcodec.o qstring.o qstring_compat.o qstringbuilder.o qtextstream.o qiodevice.o qmalloc.o qglobal.o qarraydata.o qbytearray.o qbytearraymatcher.o qdatastream.o qbuffer.o qlist.o qfiledevice.o qfile.o qfilesystementry.o qfilesystemengine.o qfsfileengine.o qfsfileengine_iterator.o qregexp.o qvector.o qbitarray.o qdir.o qdiriterator.o quuid.o qhash.o qfileinfo.o qdatetime.o qstringlist.o qabstractfileengine.o qtemporaryfile.o qmap.o qmetatype.o qsettings.o qsystemerror.o qlibraryinfo.o qvariant.o qvsnprintf.o qlocale.o qlocale_tools.o qlinkedlist.o qnumeric.o qcryptographichash.o qxmlstream.o qxmlutils.o qlogging.o qjson.o qjsondocument.o qjsonparser.o qjsonarray.o qjsonobject.o qjsonvalue.o qfilesystemengine_unix.o qfilesystemiterator_unix.o qfsfileengine_unix.o qlocale_unix.o | rm -rf .deps | rm -f /usr/local/src/debian/qtbase-opensource-src-5.3.2+dfsg/bin/qmake | make[3]: Leaving directory '/usr/local/src/debian/qtbase-opensource-src-5.3.2+dfsg/qmake' | cd src/ ( test -e Makefile || /usr/local/src/debian/qtbase-opensource-src-5.3.2+dfsg/bin/qmake /usr/local/src/debian/qtbase-opensource-src-5.3.2+dfsg/src/src.pro -o Makefile ) /usr/bin/make -f Makefile distclean | make[3]: Entering directory '/usr/local/src/debian/qtbase-opensource-src-5.3.2+dfsg/src' | /usr/local/src/debian/qtbase-opensource-src-5.3.2+dfsg/bin/qmake -o Makefile src.pro | make[3]: /usr/local/src/debian/qtbase-opensource-src-5.3.2+dfsg/bin/qmake: Command not found | Makefile:757: recipe for target 'Makefile' failed | make[3]: *** [Makefile] Error 127 | make[3]: Leaving directory '/usr/local/src/debian/qtbase-opensource-src-5.3.2+dfsg/src' | Makefile:50: recipe for target 'sub-src-distclean' failed | make[2]: *** [sub-src-distclean] Error 2 | make[2]: Leaving directory '/usr/local/src/debian/qtbase-opensource-src-5.3.2+dfsg' | debian/rules:142: recipe for target 'override_dh_auto_clean' failed | make[1]: *** [override_dh_auto_clean] Error 2 | make[1]: Leaving directory '/usr/local/src/debian/qtbase-opensource-src-5.3.2+dfsg' | debian/rules:92: recipe for target 'clean' failed | make: *** [clean] Error 2 \ It appears we remove the 'qmake' binary but then still want to use it to make the rules to clean the rest of the build tree. -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (900, 'testing'), (900, 'stable'), (400, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, armel Kernel: Linux 3.16.7-ckt2-balti (SMP w/8 CPU cores; PREEMPT) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87k2xmljgo.fsf@balti.ashgrove
