Bug#710554: kopete: cannot connect to google talk/jabber account
Hi, I think the bug can be closed since it is not reproducible anymore. It seems the problem was with kopeterc file. The solution that worked for me was to delete the file and let kopete to recreate it anew. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (500, 'testing'), (450, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kopete depends on: ii kde-runtime 4:4.11.3-1 ii kdepim-runtime 4:4.11.5-1 ii libc6 2.18-4 ii libexpat1 2.1.0-4 ii libgadu31:1.12.0~rc2-2 ii libgif4 4.1.6-11 ii libglib2.0-02.40.0-2 ii libidn111.28-1 ii libjasper1 1.900.1-debian1-1 ii libkabc44:4.11.5-4+b1 ii libkcmutils44:4.11.5-3 ii libkde3support4 4:4.11.5-3 ii libkdecore5 4:4.11.5-3 ii libkdeui5 4:4.11.5-3 ii libkdnssd4 4:4.11.5-3 ii libkemoticons4 4:4.11.5-3 ii libkhtml5 4:4.11.5-3 ii libkio5 4:4.11.5-3 ii libkmime4 4:4.11.5-4+b1 ii libknewstuff2-4 4:4.11.5-3 ii libknotifyconfig4 4:4.11.5-3 ii libkopete4 4:4.11.5-1 ii libkparts4 4:4.11.5-3 ii libkpimidentities4 4:4.11.5-4+b1 ii libmeanwhile1 1.0.2-4.1 ii libmediastreamer-base3 3.6.1-2.1+b3 ii libmsn0.3 4.2-2 ii libortp93.6.1-2.1+b3 ii libphonon4 4:4.7.1-1 ii libqca2 2.0.3-5 ii libqimageblitz4 1:0.0.6-4 ii libqt4-dbus 4:4.8.5+git242-g0315971+dfsg-2 ii libqt4-network 4:4.8.5+git242-g0315971+dfsg-2 ii libqt4-qt3support 4:4.8.5+git242-g0315971+dfsg-2 ii libqt4-sql 4:4.8.5+git242-g0315971+dfsg-2 ii libqt4-xml 4:4.8.5+git242-g0315971+dfsg-2 ii libqtcore4 4:4.8.5+git242-g0315971+dfsg-2 ii libqtgui4 4:4.8.5+git242-g0315971+dfsg-2 ii libsolid4 4:4.11.5-3 ii libsrtp01.4.5~20130609~dfsg-1 ii libssl1.0.0 1.0.1g-3 ii libstdc++6 4.8.2-16 ii libv4l-01.0.1-1 ii libx11-62:1.6.2-1 ii libxml2 2.9.1+dfsg1-3 ii libxslt1.1 1.1.28-2 ii perl5.18.2-2+b1 ii phonon 4:4.7.1-1 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages kopete recommends: ii libqca2-plugin-ossl 2.0.0~beta3-2 ii libqt4-sql-sqlite4:4.8.5+git242-g0315971+dfsg-2 Versions of packages kopete suggests: pn kdeartwork-emoticons ii khelpcenter4 4:4.11.3-1 ii texlive-latex-base2013.20140408-1 -- no debconf information Thank you, Best regards, Aaron -- 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/53639525.2020...@gmail.com
Bug#704770: qt: Adding multiple files whose filenames contain more than one consecutive space fails
Package: libqtcore4 Version: 4:4.8.2+dfsg-11 Severity: normal Hello, I've tried adding multiple files whose filenames contain more than one consecutive space with 'Add files' dialog in several applitcaions (SMPlayer, VLC, qmmp) and as the result files are either not added or added but cannot be played, for example, SMPlayer shows the first of consecutive space in filename as %20. Adding directory that contains files with such a names works fine. I don't know which qt package this bug belongs to, so it needs to be assigned properly. Linux 3.2.0-4-amd64 #1 SMP Debian 3.2.41-2 x86_64 GNU/Linux kde-workspace4:4.8.4-6 -- Best regards, Aaron -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/515f0793.3090...@gmail.com
Bug#710554: kopete: cannot connect to google talk/jabber account
Package: kopete Version: 4:4.8.4-1+b1 Severity: important Dear Maintainer, As the subject says, kopete fails to connect to google talk/jabber account with the following error: There was an error authenticating with the server: Login failed with unknown reason. There is console output: Unknown signature value: 668 Unknown signature value: 795 Unknown signature value: 795 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 795 Unknown signature value: 668 Unknown signature value: 795 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 669 Unknown signature value: 795 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 668 Unknown signature value: 668 unexpected version response I think that these bugreports can be related to this issue: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1022167 https://bugs.kde.org/show_bug.cgi?id=303268 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kopete depends on: ii kde-runtime 4:4.8.4-2 ii kdepim-runtime 4:4.4.11.1-6 ii libc6 2.17-3 ii libexpat1 2.1.0-3 ii libgadu31:1.11.2-1 ii libgif4 4.1.6-10 ii libglib2.0-02.36.1-2build1 ii libidn111.25-2 ii libjasper1 1.900.1-14 ii libkabc44:4.8.4-2 ii libkcmutils44:4.8.4-4 ii libkde3support4 4:4.8.4-4 ii libkdecore5 4:4.8.4-4 ii libkdeui5 4:4.8.4-4 ii libkdnssd4 4:4.8.4-4 ii libkemoticons4 4:4.8.4-4 ii libkhtml5 4:4.8.4-4 ii libkio5 4:4.8.4-4 ii libkmime4 4:4.8.4-2 ii libknewstuff2-4 4:4.8.4-4 ii libknotifyconfig4 4:4.8.4-4 ii libkopete4 4:4.8.4-1+b1 ii libkparts4 4:4.8.4-4 ii libkpimidentities4 4:4.8.4-2 ii libmeanwhile1 1.0.2-4.1 ii libmediastreamer1 3.5.2-10 ii libmsn0.3 4.2-2 ii libortp83.5.2-10 ii libotr2 3.2.1-1 ii libphonon4 4:4.6.0.0-3 ii libqca2 2.0.3-4 ii libqimageblitz4 1:0.0.6-4 ii libqt4-dbus 4:4.8.4+dfsg-4 ii libqt4-network 4:4.8.4+dfsg-4 ii libqt4-qt3support 4:4.8.4+dfsg-4 ii libqt4-sql 4:4.8.4+dfsg-4 ii libqt4-xml 4:4.8.4+dfsg-4 ii libqtcore4 4:4.8.4+dfsg-4 ii libqtgui4 4:4.8.4+dfsg-4 ii libsolid4 4:4.8.4-4 ii libssl1.0.0 1.0.1e-3 ii libstdc++6 4.8.0-9 ii libv4l-00.8.9-3 ii libx11-62:1.5.0-1+deb7u1 ii libxml2 2.8.0+dfsg1-7+nmu1 ii libxslt1.1 1.1.26-14.1 ii perl5.14.2-21 ii phonon 4:4.6.0.0-3 ii zlib1g 1:1.2.8.dfsg-1 Versions of packages kopete recommends: ii libqca2-plugin-ossl 2.0.0~beta3-2 ii libqt4-sql-sqlite4:4.8.4+dfsg-4 Versions of packages kopete suggests: pn kdeartwork-emoticons ii khelpcenter4 4:4.8.4-2 ii texlive-latex-base2013.20130530-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130531202047.8906.42961.reportbug@localhost
Bug#677291: KWin crashes when gwenview enters full-screen mode
Package: kde-window-manager Version: 4:4.8.4-2 Package: gwenview Version: 4:4.7.4-2+b1 Severity: normal Dear Maintainer, When gwenview is trying to enter full-screen mode, KWin crashes. Here is KWin backtrace: Application: KWin (kwin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7fc4fef22780 (LWP 3804))] Thread 2 (Thread 0x7fc4dbcff700 (LWP 3815)): #0 0x7fc4f33cb2d4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fc4fb21a1c7 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #2 0x7fc4fb21a1f9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4 #3 0x7fc4f33c6b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7fc4fe75e6dd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #5 0x in ?? () Thread 1 (Thread 0x7fc4fef22780 (LWP 3804)): [KCrash Handler] #5 0x7fc4e270fece in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #6 0x7fc4e270faa0 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #7 0x7fc4e26f97b8 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #8 0x7fc4e26e6a4f in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #9 0x7fc4e2800ea4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #10 0x7fc4fac42717 in ?? () from /usr/lib/libkwinglutils.so.1 #11 0x7fc4fac42815 in KWin::GLVertexBuffer::render(QRegion const&, unsigned int) () from /usr/lib/libkwinglutils.so.1 #12 0x7fc4feac71f0 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #13 0x7fc4feacdb28 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #14 0x7fc4feab8c8e in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #15 0x7fc4fead8385 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #16 0x7fc4feab7d06 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #17 0x7fc4fead8685 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #18 0x7fc4feab86eb in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #19 0x7fc4feab9589 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #20 0x7fc4feab7c34 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #21 0x7fc4fead8203 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #22 0x7fc4feaba828 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #23 0x7fc4feace64d in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #24 0x7fc4feab4ac1 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #25 0x7fc4f9f3e8dc in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #26 0x7fc4f92d370c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #27 0x7fc4f92d7b8a in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #28 0x7fc4fe262c16 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #29 0x7fc4f9f29bde in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #30 0x7fc4f9f5aac2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #31 0x7fc4f9f5ac78 in QEventDispatcherUNIX::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #32 0x7fc4f937570f in ?? () from /usr/lib/x86_64-linux-gnu/libQtGui.so.4 #33 0x7fc4f9f2892f in QEventLoop::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #34 0x7fc4f9f28bb8 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #35 0x7fc4f9f2dd78 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4 #36 0x7fc4fea6f23e in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so #37 0x7fc4fe6a4ead in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #38 0x00400771 in _start () -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kde-window-manager depends on: ii kde-runtime 4:4.8.4-1 ii kde-style-oxygen 4:4.8.4-2 ii libc6 2.13-33 ii libgl1-mesa-glx [libgl1] 8.0.2-2 ii libice6 2:1.0.8-2 ii libkactivities6 4:4.8.4-1 ii libkcmutils4 4:4.8.3-2 ii libkdeclarative5 4:4.8.3-2 ii libkdecorations4 4:4.8.4-2 ii libkdecore5 4:4.8.3-2 ii libkdeui5 4:4.8.3-2 ii libkephal4abi14:4.8.4-2 ii libkio5 4:4.8.3-2 ii libknewstuff3-4 4:4.8.3-2 ii libkwineffects1abi3 4:4.8.4-2 ii libkwinglutils1
Bug#302921: kuser: corrupts username information
Package: kuser
Version: 4:3.4.0-0pre1
Severity: critical
Tags: experimental
Justification: breaks unrelated software
1. Do a fresh net install of Debian Sarge RC3
2. Upgrade to Unstable
3. Add pkg-kde.alioth.debian.org to sources.list
4. Apt-get install x-window-system kde kdm cupsys sane
5. Log into KDE using the username created while installing Debian
6. Open Kuser, select the username, then click the edit button
7. Select the groups tab, then select the lpadmin, saned, and scanner
groups
8. Select OK, then close Kuser (there is no save button)
9. Watch the problems start :{ - Konsole no longer works correctly, KDM
does not list the username, reopening Kuser shows the username is on the
same level number as root (0)
10. I have not discovered a fix. Attempting to recover the user account
with usermod
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-386
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages kuser depends on:
ii kdelibs4 4:3.4.0-0pre2 core libraries for all KDE
applica
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries
an
ii libgcc11:3.4.3-12GCC support library
ii libqt3c102-mt 3:3.3.3-8 Qt GUI Library (Threaded
runtime v
ii libstdc++5 1:3.3.5-12The GNU Standard C++ Library v3
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#302921: Confirmed that kuser now works (4.3-pre2)
Sorry I haven't replied quicker. I work on computers in my spare time (of which I have very little). Thank you guys so much for such a quick fix. I downloaded the updated kdeadmin and tested kuser, which works perfectly! Again, thank you Debian, KDE, and FOSS. The computer that I finished setting up is destined for a men's recovery home, so the work that you guys do will make some people very happy. Aaron Johnson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#848180: konsole: Includes application name in window title when configured not to do so
Package: konsole Version: 4:16.08.3-1 Severity: minor Dear Maintainer, After unchecking the "Show application name on the titlebar" option in the Configure Konsole dialog it still inludes " - Konsole" at the end of window titles. This occurs even after closing all Konsole windows and restarting the application. I first observed this with version 4:16.08.2-2 of both the konsole and konsole-kpart packages. I upgraded both of those to 4:16.08.3-1 from unstable to check if the issue was still present (and I again made sure to close all windows after the upgrade). Before I installed the version from testing yesterday I hadn't used this package in long time, so I can't say how long this bug has existed. Thank you for your work on Debian, Aaron -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.7.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages konsole depends on: ii kio 5.27.0-2 ii konsole-kpart 4:16.08.3-1 ii libc6 2.24-7 ii libkf5completion5 5.27.0-1 ii libkf5configcore5 5.27.0-1 ii libkf5configgui5 5.27.0-1 ii libkf5configwidgets5 5.27.0-1 ii libkf5coreaddons5 5.27.0-1 ii libkf5crash5 5.27.0-1 ii libkf5dbusaddons5 5.27.0-1 ii libkf5i18n5 5.27.0-2 ii libkf5iconthemes5 5.27.0-1 ii libkf5kiowidgets5 5.27.0-2 ii libkf5notifyconfig5 5.27.0-1 ii libkf5widgetsaddons5 5.27.0-1 ii libkf5windowsystem5 5.27.0-1 ii libkf5xmlgui5 5.27.0-1 ii libqt5core5a 5.7.1~20161021+dfsg-6 ii libqt5gui55.7.1~20161021+dfsg-6 ii libqt5widgets55.7.1~20161021+dfsg-6 ii libstdc++66.2.1-5 konsole recommends no packages. konsole suggests no packages. -- no debconf information
Bug#1057883: signond: Some optional symbols are not marked as such in the symbols files
Package: signond Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu noble ubuntu-patch X-Debbugs-Cc: arraybo...@ubuntu.com Some symbols in the symbols files are optional, and vanish when the package is built on Ubuntu, resulting in an FTBFS. While not strictly necessary in Debian at the moment, it would be helpful for these symbols were marked optional. (There's also a couple of Lintian overrides that need syntax fixes.) In Ubuntu, the attached patch was applied to fix both of these issues. Thanks for considering the patch. -- System Information: Debian Release: trixie/sid APT prefers noble APT policy: (500, 'noble') Architecture: amd64 (x86_64) Kernel: Linux 6.5.0-9-generic (SMP w/8 CPU threads; PREEMPT) Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) diff -Nru signond-8.61/debian/libsignon-extension1.symbols signond-8.61/debian/libsignon-extension1.symbols --- signond-8.61/debian/libsignon-extension1.symbols2022-03-11 20:45:00.0 + +++ signond-8.61/debian/libsignon-extension1.symbols2023-12-10 02:45:20.0 + @@ -55,16 +55,16 @@ _ZN6SignOn18AbstractKeyManagerD0Ev@Base 8.57+20150423 _ZN6SignOn18AbstractKeyManagerD1Ev@Base 8.57+20150423 _ZN6SignOn18AbstractKeyManagerD2Ev@Base 8.57+20150423 - _ZN6SignOn18ExtensionInterfaceD0Ev@Base 8.57+20150423 - _ZN6SignOn18ExtensionInterfaceD1Ev@Base 8.57+20150423 - _ZN6SignOn18ExtensionInterfaceD2Ev@Base 8.57+20150423 + (optional) _ZN6SignOn18ExtensionInterfaceD0Ev@Base 8.57+20150423 + (optional) _ZN6SignOn18ExtensionInterfaceD1Ev@Base 8.57+20150423 + (optional) _ZN6SignOn18ExtensionInterfaceD2Ev@Base 8.57+20150423 _ZN6SignOn18setFilePermissionsERK7QString6QFlagsIN11QFileDevice10PermissionEEb@Base 8.57+20150423 - _ZN6SignOn19ExtensionInterface2D0Ev@Base 8.57+20150423 - _ZN6SignOn19ExtensionInterface2D1Ev@Base 8.57+20150423 - _ZN6SignOn19ExtensionInterface2D2Ev@Base 8.57+20150423 - _ZN6SignOn19ExtensionInterface3D0Ev@Base 8.57+20150423 - _ZN6SignOn19ExtensionInterface3D1Ev@Base 8.57+20150423 - _ZN6SignOn19ExtensionInterface3D2Ev@Base 8.57+20150423 + (optional) _ZN6SignOn19ExtensionInterface2D0Ev@Base 8.57+20150423 + (optional) _ZN6SignOn19ExtensionInterface2D1Ev@Base 8.57+20150423 + (optional) _ZN6SignOn19ExtensionInterface2D2Ev@Base 8.57+20150423 + (optional) _ZN6SignOn19ExtensionInterface3D0Ev@Base 8.57+20150423 + (optional) _ZN6SignOn19ExtensionInterface3D1Ev@Base 8.57+20150423 + (optional) _ZN6SignOn19ExtensionInterface3D2Ev@Base 8.57+20150423 _ZN6SignOn21AbstractCryptoManager10initializeERK4QMapI7QString8QVariantE@Base 8.57+20150423 _ZN6SignOn21AbstractCryptoManager11qt_metacallEN11QMetaObject4CallEiPPv@Base 8.57+20150423 _ZN6SignOn21AbstractCryptoManager11qt_metacastEPKc@Base 8.57+20150423 diff -Nru signond-8.61/debian/libsignon-plugins-common1.symbols signond-8.61/debian/libsignon-plugins-common1.symbols --- signond-8.61/debian/libsignon-plugins-common1.symbols 2022-03-11 21:01:01.0 + +++ signond-8.61/debian/libsignon-plugins-common1.symbols 2023-12-10 02:45:20.0 + @@ -22,9 +22,9 @@ _ZN6SignOn13BlobIOHandler8sendDataERK4QMapI7QString8QVariantE@Base 8.57+20150423 _ZN6SignOn13BlobIOHandlerC1EP9QIODeviceS2_P7QObject@Base 8.57+20150423 _ZN6SignOn13BlobIOHandlerC2EP9QIODeviceS2_P7QObject@Base 8.57+20150423 - _ZN6SignOn13BlobIOHandlerD0Ev@Base 8.57+20150423 - _ZN6SignOn13BlobIOHandlerD1Ev@Base 8.57+20150423 - _ZN6SignOn13BlobIOHandlerD2Ev@Base 8.57+20150423 + (optional) _ZN6SignOn13BlobIOHandlerD0Ev@Base 8.57+20150423 + (optional) _ZN6SignOn13BlobIOHandlerD1Ev@Base 8.57+20150423 + (optional) _ZN6SignOn13BlobIOHandlerD2Ev@Base 8.57+20150423 (optional=templinst)_ZN7QVectorI10QByteArrayE6appendERKS0_@Base 8.57+20150423 (optional=templinst)_ZN7QVectorI10QByteArrayE7reallocEi6QFlagsIN10QArrayData16AllocationOptionEE@Base 8.60 (optional=templinst)_ZN8QMapNodeI7QString8QVariantE14destroySubTreeEv@Base 8.57+20150423 @@ -46,29 +46,29 @@ _ZN19AuthPluginInterface11qt_metacastEPKc@Base 8.57+20150423 _ZN19AuthPluginInterface13statusChangedE15AuthPluginStateRK7QString@Base 8.57+20150423 _ZN19AuthPluginInterface16staticMetaObjectE@Base 8.57+20150423 - _ZN19AuthPluginInterface18userActionFinishedERKN6SignOn13UiSessionDataE@Base 8.57+20150423 + (optional) _ZN19AuthPluginInterface18userActionFinishedERKN6SignOn13UiSessionDataE@Base 8.57+20150423 _ZN19AuthPluginInterface18userActionRequiredERKN6SignOn13UiSessionDataE@Base 8.57+20150423 - _ZN19AuthPluginInterface5abortEv@Base 8.57+20150423 + (optional) _ZN19AuthPluginInterface5abortEv@Base 8.57+20150423 _ZN19AuthPluginInterface5errorERKN6SignOn5ErrorE@Base 8.57+20150423 _ZN19AuthPluginInterface5storeERKN6SignOn11SessionDataE@Base 8.57+20150423 - _ZN19AuthPluginInterface6cancelEv@Base 8.57+20150423 + (optional) _ZN19AuthPluginInterface6cancelEv@Base 8.57+20150423 _ZN19Au
Bug#617980: qt4-qtconfig: Font anti-aliasing settings aren't shared with gtk
Package: qt4-qtconfig Version: 4:4.6.3-4 Severity: normal When I set my fonts through the normal font configuration dialog (for either xfce or gnome), those settings aren't shared with qt4, despite using the gtk theme. This creates a noticeable difference between the look of qt4 and native gtk applications. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qt4-qtconfig depends on: ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib ii libgcc1 1:4.5.2-4 GCC support library ii libqt4-qt3support 4:4.6.3-4 Qt 3 compatibility library for Qt ii libqtcore44:4.6.3-4 Qt 4 core module ii libqtgui4 4:4.6.3-4 Qt 4 GUI module ii libstdc++64.5.2-4The GNU Standard C++ Library v3 qt4-qtconfig recommends no packages. qt4-qtconfig suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110313030149.14869.42228.report...@main.sd.cox.net
Bug#332652: Konqueror stays transparent even when it has focus
Package: konqueror Version: 4:3.4.2-3 When Konqueror is moved or resized, the window will retain the opacity of a background application, even when it has focus. This only occurs randomly, however. Many times, it will exhibit normal behavior. Sometimes exiting and restarting the x server will correct the behavior. What is strange is that javascript pop-up windows, that do not have a toolbar and opened by clicking a link, will maintian normal transparency behavior. No other applications that I use exhibit this behavior. This occurs whether I started it in file manager mode or web browsing mode. My settings are: Control Center > Window Behavior > Translucency > Use Translucency/Shadows The settings are: Translucency: Inactive window: 50%, Treat 'keep above' windows as active ones Shadows: Use shadows, 12, 6, 3, 75%, 75% Effects: none selected I am running the latest version of Debian Unstable, with KDE 3.4 and X.org. This has occured with all Debian updates to KDE 3.4, X.org, and Linux 2.6 kernels (2.6.8 and 2.6.12). I have a an Intel 82865G onboard graphics chip with max ram used for video. This has also occurred on my home system with a Via Pro Savage KM266 onboard chip, with 32mb used for video, though not as often; probably because I reboot more frequently and don't use Konqueror as much. I have a feeling this bug will be a tough one to duplicate. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#346274: Konqueror cannot connect to an AD Windows share as a user
Package: kdenetwork-filesharing Version: 4:3.4.3-3 When attempting to connect to a Windows XP share on a coputer that is part of Active Directory, using smb://[EMAIL PROTECTED], Konqueror will keep displaying the password dialog until the action is cancelled, leading to an access denied. However, konqueror connects to the shared folder when run as root, or when a windows computer is not using Active Directory for authentication. Thanks, Aaron Johnson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#392846: kicker: Eats up lots of cpu and occasionally hangs
Package: kicker Version: 4:3.5.5a-1 Severity: important After updating 2 machines to kicker 4:3.5.5a-1 I noticed the idle cpu on both computers was quite high, and often 100%. Top revealed that kicker was to blame. Further inspection showed that kicker would be unresponsive and fail to redraw when the cpu hit 100%. Running strace on kicker on one of the machines showed that it was repeatedly trying to open xlcUTF-8.so.2, a file that does not exist in any package. creating a link with that name to xlcUTF8Load.so.2.0.0 in /usr/lib/X11/locale/common seems to have solved that particular issue, and resulted in slightly better kicker performance, but it is still way, way worse than it should be. Downgrading to 4:3.5.5-1 solved the problem. -- System Information: Debian Release: testing/unstable APT prefers dapper APT policy: (500, 'dapper'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kicker depends on: ii kdebase-data4:3.5.5a-1 shared data files for the KDE base ii kdelibs4c2a 4:3.5.5a-1 core libraries and binaries for al ii libacl1 2.2.41-1 Access control list shared library ii libart-2.0-22.3.17-1 Library of functions for 2D graphi ii libattr12.4.32-1 Extended attribute shared library ii libaudio2 1.8-2The Network Audio System (NAS). (s ii libc6 2.3.6-16 GNU C Library: Shared libraries ii libfam0 2.7.0-10 Client library to control the FAM ii libfontconfig1 2.4.1-2 generic font configuration library ii libfreetype62.2.1-5 FreeType 2 font engine, shared lib ii libgcc1 1:4.1.1-15 GCC support library ii libice6 1:1.0.1-2X11 Inter-Client Exchange library ii libidn110.6.5-1 GNU libidn library, implementation ii libjpeg62 6b-13The Independent JPEG Group's JPEG ii libkonq44:3.5.5a-1 core libraries for Konqueror ii libpng12-0 1.2.8rel-5.2 PNG library - runtime ii libqt3-mt 3:3.3.6-4Qt GUI Library (Threaded runtime v ii libsm6 1:1.0.1-3X11 Session Management library ii libstdc++6 4.1.1-15 The GNU Standard C++ Library v3 ii libx11-62:1.0.3-1X11 client-side library ii libxau6 1:1.0.1-2X11 authorisation library ii libxcomposite1 1:0.3-2 X11 Composite extension library ii libxcursor1 1.1.7-4 X cursor management library ii libxext61:1.0.1-2X11 miscellaneous extension librar ii libxfixes3 1:4.0.1-4X11 miscellaneous 'fixes' extensio ii libxft2 2.1.10-3 FreeType-based font drawing librar ii libxi6 1:1.0.1-3X11 Input extension library ii libxinerama11:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-4 X11 RandR extension library ii libxrender1 1:0.9.1-3X Rendering Extension client libra ii libxt6 1:1.0.2-2X11 toolkit intrinsics library ii libxtst61:1.0.1-5X11 Testing -- Resource extension ii zlib1g 1:1.2.3-13 compression library - runtime kicker recommends no packages. -- no debconf information !DSPAM:452fa1d0154021599314407! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#238417: FAM and famd are causing a conflict
As noted in the kde bug report, killing famd or removing fam (apt-get remove fam) and restarting the computer seems to resolve the problem. Aaron _ Express yourself instantly with MSN Messenger! Download today - it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Bug#194248: lo interface
I've seen this if the lo interface is not up in KDE. =a= -- === Aaron Straus [EMAIL PROTECTED]
Re: Bug#256862: kmenuedit: kde3.3: no default menu and kmenuedit complains of invalid window parameter
>when I try to edit the non-existent menu that suddenly arrived with the >last apt-get upgrade to kde 3.3. So I now have no menu nor an ability to >re-create the one I lost. KDE Panel was similarly blank on login but >the icons and programs can be replaced (by selecting non-KDE application >- even for Konqueror) but the usual "select from KMenu" option is empty > in the panel too. I'm having nearly the exact same problem. In addition to this, all the mime associations are gone. kmenuedit opens from the terminal, but no changes are saved when I save them. The menu is entirely blank. Debian Release: Unstable Architecture: i686 Kernel: Linux 2.6.12-3 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#1089004: sddm: Informational messages from PAM modules block login on Debian 12
Package: sddm
Version: 0.19.0-5
Severity: normal
Tags: patch
X-Debbugs-Cc: adrela...@kicksecure.com, arraybo...@gmail.com
NOTICE: This bug only affects Bookworm to my awareness. This bug is
present in SDDM 0.19.0 upstream, and does not exist in SDDM 0.20.0
upstream from my testing, and both Trixie and Sid use SDDM 0.21.0.
SDDM supports reading several kinds of messages from PAM, including
informational messages intended for display to the end-user. These
messages can be generated if, for instance, a line is present in
/etc/pam.d/common-auth such as:
authoptionalpam_exec.so debug stdout seteuid
/usr/bin/script-that-writes-to-stdout
While SDDM currently lacks the ability to actually display these
messages, it's designed to read them and log them, and their presence
should not block login. Unfortunately, these informational message
actually do block login on Debian 12. If any PAM module outputs info
to stdout that SDDM considers "informational", it may result in SDDM
hanging forever while trying to log in. To reproduce:
* Install Debian 12 with a desktop environment that comes with SDDM.
KDE Plasma and LXQt both work here.
* Log in.
* Create a script at /usr/bin/messup.sh, with the following contents:
#!/bin/bash
echo 'Mess1'
echo 'Mess2'
echo 'Mess3'
echo 'Mess4'
echo 'Mess5'
echo 'Mess6'
echo 'Mess7'
* Set /usr/bin/messup.sh executable.
* In a new terminal, run `sudo -i` and ensure you see seven lines of
text, 'Mess1' through 'Mess7' displayed.
* Add a line to /etc/pam.d/common-auth as follows:
authoptionalpam_exec.so debug stdout seteuid /usr/bin/messup.sh
* Log out.
* Attempt to log back in. SDDM will hang.
* To recover, switch to a TTY, log in, run `sudo vi
/usr/bin/messup.sh`, and comment out all seven 'Mess' lines.
Save the file, then run `sudo systemctl restart sddm`.
I tested SDDM upstream and discovered that 0.19.0 had this bug, but
0.20.0 did not. I then bisected between them, and found that the first
good commit was 6a9d0875, "Port to Qt6 QRegularExpression". This
significantly changed how several regular expressions in SDDM were
parsed. I then applied the changes made in this commit to Debian 12's
SDDM package (adjusting the patch as necessary for it to work with
Debian's SDDM), tested it by repeating the steps above, and found that
the issue persisted.
After checking the systemd journal for anything about SDDM, I
discovered that SDDM was failing to read all of the output from my
messup.sh script. This bug was also already fixed in SDDM upstream,
in commit 48a9ec7b, "Process all available auth messages in a loop".
This commit also required some slight changes to make it apply to
Debian's SDDM. After applying this patch as well, I ran the above
tests again, and the issue was resolved.
The final patch I used is as follows. Some notes:
* I have no idea why changing the way regex matches are done fixes
the problem. I've looked through all of the regexes in this patch and
they all look exactly the same in both the old and new versions.
* The changes to the src/auth/Auth.cpp file's
Auth::Private::dataPending function (seen just below the line
`SafeDataStream str(socket);` below) may look alarming, but it's
only because of `diff -u` being weird. The only change I backported
from upstream in this area was to wrap a large block of code in a
`while (socket->bytesAvailable() > 0) { ... }` block, and fix
indentation as appropriate. Apparently the extra intendation made
diff throw a tantrum.
-
diff -r -u sddm-0.19.0.bak/src/auth/Auth.cpp sddm-0.19.0/src/auth/Auth.cpp
--- sddm-0.19.0.bak/src/auth/Auth.cpp 2024-12-03 20:49:22.259092853 -0600
+++ sddm-0.19.0/src/auth/Auth.cpp 2024-12-03 21:01:03.363190219 -0600
@@ -24,6 +24,7 @@
#include "SafeDataStream.h"
#include
+#include
#include
#include
#include
@@ -101,7 +102,7 @@
static std::unique_ptr self;
if (!self) {
self.reset(new SocketServer());
-
self->listen(QStringLiteral("sddm-auth%1").arg(QUuid::createUuid().toString().replace(QRegExp(QStringLiteral("[{}]")),
QString(;
+
self->listen(QStringLiteral("sddm-auth%1").arg(QUuid::createUuid().toString().replace(QRegularExpression(QStringLiteral("[{}]")),
QString(;
}
return self.get();
}
@@ -152,55 +153,57 @@
Auth *auth = qobject_cast(parent());
Msg m = MSG_UNKNOWN;
SafeDataStream str(socket);
-str.receive();
-str >> m;
-switch (m) {
-case ERROR: {
-QString message;
-Error type = ERROR_NONE;
-str >> message >> type;
-Q_EMIT auth->error(message, type);
-break;
-}
-case INFO: {
-QString message;
-Info type = INFO_NONE;
-str >> message >> type;
-Q_EMIT auth->info(message, type);
Bug#790080: kwidgetsaddons: FTBFS on arm*: kwidgetsaddons-kcolumnresizertest fails
Source: kwidgetsaddons
Version: 5.11.0-1
Severity: important
Builds of kwidgetsaddons for arm64, armel, and armhf (but no other
architectures) all failed. The arm64 build simply reports
7/10 Test #10: kwidgetsaddons-kcolumnresizertest ...***Failed0.48 sec
* Start testing of KColumnResizerTest *
Config: Using QtTest library 5.4.2, Qt 5.4.2 (arm64-little_endian-lp64 shared
(dynamic) release build; by GCC 4.9.2)
PASS : KColumnResizerTest::initTestCase()
FAIL! : KColumnResizerTest::test(forms) 'widget1' returned FALSE. ()
Loc: [../../autotests/kcolumnresizertest.cpp(66)]
FAIL! : KColumnResizerTest::test(grids) 'widget1' returned FALSE. ()
Loc: [../../autotests/kcolumnresizertest.cpp(66)]
FAIL! : KColumnResizerTest::test(grid-and-form) 'widget1' returned FALSE. ()
Loc: [../../autotests/kcolumnresizertest.cpp(66)]
PASS : KColumnResizerTest::cleanupTestCase()
Totals: 2 passed, 3 failed, 0 skipped, 0 blacklisted
* Finished testing of KColumnResizerTest *
The armel and armhf builds yield similar output, but with one
additional message that could be relevant (or simply a red herring):
libEGL warning: DRI2: failed to open swrast (search paths
/usr/lib/arm-linux-gnueabi/dri:${ORIGIN}/dri:/usr/lib/dri)
libEGL warning: DRI2: failed to open swrast (search paths
/usr/lib/arm-linux-gnueabihf/dri:${ORIGIN}/dri:/usr/lib/dri)
Could you please take a look? You can find the full logs at
https://buildd.debian.org/status/logs.php?pkg=kwidgetsaddons&ver=5.11.0-1
Thanks!
--
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/20150626203910.12678.28275.report...@ghostwheel.internal.ucko.debian.net
Bug#884468: qbs: FTBFS on alpha: many tests fail
Source: qbs Version: 1.8.1+dfsg-4 Severity: important Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-al...@lists.debian.org Usertags: alpha The build of qbs for alpha (admittedly not a release architecture) failed with many test suite errors, as detailed at https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=alpha&ver=1.8.1%2Bdfsg-4&stamp=1505226406&raw=0: Totals: 80 passed, 94 failed, 54 skipped, 0 blacklisted, 87187ms * Finished testing of TestBlackbox * Makefile:371: recipe for target 'check' failed make[5]: *** [check] Error 94 Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#884470: qbs: FTBFS on hurd-i386: processNameByPid implementation missing
Source: qbs Version: 1.8.1+dfsg-4 Severity: important Tags: upstream Justification: fails to build from source User: debian-h...@lists.debian.org Usertags: hurd-i386 Builds of qbs for hurd-i386 (admittedly not a release architecture) have been failing. The (immediate) error is tools/processutils.cpp:61:5: error: #error Missing implementation of processNameByPid for this platform. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#884469: qbs: FTBFS on hppa: most tests fail
Source: qbs Version: 1.8.1+dfsg-4 Severity: important Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-h...@lists.debian.org Usertags: hppa The build of qbs for hppa (admittedly not a release architecture) failed with a great many test suite errors, as detailed at https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=hppa&ver=1.8.1%2Bdfsg-4&stamp=1505844196&raw=0: Totals: 78 passed, 194 failed, 54 skipped, 0 blacklisted, 226338ms Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#884472: qbs: FTBFS on x32: qbs-setup-qt (qmake?) bus error
Source: qbs Version: 1.8.1+dfsg-4 Severity: important Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-am...@lists.debian.org Usertags: x32 Builds of qbs for x32 (admittedly not a release architecture) have been failing lately: + /<>/qbs-1.8.1+dfsg/bin/qbs-setup-qt /usr/bin/qmake qbs_autotests Bus error debian/rules:46: recipe for target 'override_dh_auto_test-arch' failed It's not clear from the log which program encountered the bus error, so this might (or might not!) turn out to be a qmake bug. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#884471: qbs: FTBFS on kFreeBSD: many tests fail
Source: qbs Version: 1.8.1+dfsg-4 Severity: important Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-...@lists.debian.org Usertags: kfreebsd Builds of qbs for kfreebsd-* (admittedly not release architectures) have been failing lately with quite a few test suite errors, as detailed at https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=kfreebsd-amd64&ver=1.8.1%2Bdfsg-4&stamp=1505222966&raw=0 https://buildd.debian.org/status/fetch.php?pkg=qbs&arch=kfreebsd-i386&ver=1.8.1%2Bdfsg-4&stamp=1505223063&raw=0: Totals: 97 passed, 75 failed, 56 skipped, 0 blacklisted, 120526ms * Finished testing of TestBlackbox * Makefile:365: recipe for target 'check' failed make[5]: *** [check] Error 75 (The total execution time varies by a couple of seconds, but the other statistics match up.) Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#884472: qbs: FTBFS on x32: qbs-setup-qt (qmake?) bus error
Lisandro Damián Nicanor Pérez Meyer writes: > El 15 dic. 2017 1:39 p.m., "Aaron M. Ucko" escribió: > [...] > + /<>/qbs-1.8.1+dfsg/bin/qbs-setup-qt /usr/bin/qmake > qbs_autotests > Bus error [...] > In my experience bus errors are arch-related. Of course this case might be > different, but I certainly would not start by checking qmake. My point was simply that the message did not indicate whether qbs-setup-qt or qmake encountered the bus error, which is presumably arch-related regardless. Sorry if that was unclear. > I suggest you to ping porters. I've copied debian-amd64 accordingly. (I'm not aware of an x32-specific list, but the port runs on amd64 hardware.) -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#887679: kcoreaddons: please version doxygen B-D per CMake check
Source: kcoreaddons Version: 5.37.0-3 Severity: important Justification: fails to build from source (but built successfully in the past) User: debian-powe...@lists.debian.org Usertags: powerpcspe Builds of kcoreaddons for powerpcspe (admittedly not a release architecture) have been failing lately: CMake Error at /usr/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find Doxygen: Found unsuitable version "1.8.12", but required is at least "1.8.13" (found /usr/bin/doxygen) Please version its build dependency on doxygen accordingly. (FWIW, doxygen's own build dependencies have been uninstallable on powerpcspe for a while due to issues with the Ruby stack.) Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#891605: kconfig: please version doxygen B-D per upstream
Source: kconfig Version: 5.42.0-2 Severity: normal User: debian-powe...@lists.debian.org Usertags: powerpcspe Builds of kconfig for powerpcspe (admittedly not a release architecture) have been failing lately: CMake Error at /usr/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find Doxygen: Found unsuitable version "1.8.12", but required is at least "1.8.13" (found /usr/bin/doxygen) (Doxygen is out of date on this architecture, apparently due to Ruby toolchain issues.) Could you please version the build dependency on doxygen to (>= 1.8.13~) to match upstream's requirements? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#891606: kwayland: please version doxygen B-D per upstream
Source: kwayland Version: 4:5.42.0-2 Severity: normal User: debian-powe...@lists.debian.org Usertags: powerpcspe Builds of kwayland for powerpcspe (admittedly not a release architecture) have been failing lately: CMake Error at /usr/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find Doxygen: Found unsuitable version "1.8.12", but required is at least "1.8.13" (found /usr/bin/doxygen) (Doxygen is out of date on this architecture, apparently due to Ruby toolchain issues.) Could you please version the build dependency on doxygen to (>= 1.8.13~) to match upstream's requirements? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#892239: ki18n: please version doxygen B-D per upstream
Source: ki18n Version: 5.42.0-3 Severity: important Justification: fails to build from source (but built successfully in the past) User: debian-powe...@lists.debian.org Usertags: powerpcspe Builds of ki18n for powerpcspe (admittedly not a release architecture) have been failing lately: CMake Error at /usr/share/cmake-3.9/Modules/FindPackageHandleStandardArgs.cmake:137 (message): Could NOT find Doxygen: Found unsuitable version "1.8.12", but required is at least "1.8.13" (found /usr/bin/doxygen) (Doxygen is out of date on this architecture, apparently due to Ruby stack issues.) Could you please version the build dependency on doxygen to (>= 1.8.13~) to match upstream's requirements? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#799543: dh_doxygen: fails if no docs found, even in binary-only builds
Package: doxygen Version: 1.8.9.1-5 Severity: important Builds of signond covering only its architecture-dependent binary packages (as on the autobuilders) have been failing: dh_doxygen dh_doxygen: Doxygen documentation not found make[2]: *** [override_dh_install] Error 2 I presume this error represents an intended sanity check, which could be helpful in some circumstances. However, the typical dh_* convention is to treat having nothing to do as a (trivial) success rather than a failure. This convention is particularly appropriate here, because many source packages (signond included) split documentation into architecture-independent binary packages that not all builds cover. As such, please either downgrade this error to a warning or suppress it altogether, at least in the case of builds covering only a subset of possible binary packages. See also sphinx-common bug https://bugs.debian.org/745690. Thanks!
Bug#802290: libsignon-glib: FTBFS on non-amd64: hardcodes x86_64-linux-gnu paths
Source: libsignon-glib Version: 1.12-1 Severity: important Justification: fails to build from source Builds of libsignon-glib for architectures other than amd64 (such as i386) have been failing: dh_install --list-missing dh_install: libsignon-glib1 missing files (usr/lib/x86_64-linux-gnu/libsignon-glib.so.1*), aborting debian/rules:21: recipe for target 'override_dh_install' failed Please adjust *.files to use wildcards as appropriate rather than hardcoding x86_64-linux-gnu. Thanks!
Bug#847821: qt3d-opensource-src: FTBFS: tst_QAspectEngine times out (hangs?)
Source: qt3d-opensource-src Version: 5.7.1~20161122+dfsg-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of the latest qt3d-opensource-src release failed on several architectures with tst_QAspectEngine timeouts, perhaps due to intermittent hangs. Specifically, these timeouts affected shouldNotCrashOnShutdownWhenComponentIsCreatedWithParentBeforeItsEntity on i386, mips, and the non-release architecture hppa, and setRootEntity on s390x and the non-release architecture hurd-i386. Could you please take a look, and ensure that all tests reliably succeed? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#847822: qt3d-opensource-src: FTBFS on powerpc: __atomic_fetch_add_8 undefined
Source: qt3d-opensource-src Version: 5.7.1~20161122+dfsg-2 Severity: important Justification: fails to build from source The latest build of qt3d-opensource-src for powerpc (admittedly not a release architecture) failed: g++ -specs=/usr/share/dpkg/pie-link.specs -Wl,-z,relro -Wl,--as-needed -Wl,--no-undefined -Wl,--version-script,Qt3DCore.version -Wl,-O1 -Wl,--enable-new-dtags -shared -Wl,-soname,libQt53DCore.so.5 -o libQt53DCore.so.5.7.1 .obj/qtickclock.o ... obj/moc_propertychangehandler_p.o -lQt5Gui -lQt5Network -lQt5Core -lpthread -lGL .obj/qnodeid.o: In function `std::__atomic_base::fetch_add(unsigned long long, std::memory_order)': /usr/include/c++/6/bits/atomic_base.h:514: undefined reference to `__atomic_fetch_add_8' collect2: error: ld returned 1 exit status Could you please take a look? Linking against -latomic might help; since you're already using -Wl,--as-needed, I expect you should even be able to list that library unconditionally without getting a runtime dependency on architectures that don't require it here. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#847822: qt3d-opensource-src: FTBFS on powerpc: __atomic_fetch_add_8 undefined
Lisandro Damián Nicanor Pérez Meyer writes: > Flags are really set from qtbase itself. And qtbase requires gcc atomics > support (not sure if that's really involved, but I think so). Thanks for looking into this report. Please note that libatomic comes with GCC, just isn't used by default. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#860507: qtcharts-opensource-src: FTBFS on armhf: Illegal instruction
Source: qtcharts-opensource-src Version: 5.7.1-1 Severity: important Justification: fails to build from source The armhf build of qtcharts-opensource-src failed: /«PKGBUILDDIR»/tests/auto/qml-qtquicktest/target_wrapper.sh ./tst_qml-qtquicktest make[3]: Entering directory '/«PKGBUILDDIR»/tests/auto/qml' make[3]: Nothing to be done for 'check'. make[3]: Leaving directory '/«PKGBUILDDIR»/tests/auto/qml' Makefile:287: recipe for target 'check' failed make[3]: *** [check] Illegal instruction make[3]: Leaving directory '/«PKGBUILDDIR»/tests/auto/qml-qtquicktest' Makefile:1724: recipe for target 'sub-qml-qtquicktest-check' failed make[2]: *** [sub-qml-qtquicktest-check] Error 2 Could you please take a look? I don't have further details, but perhaps you can reproduce the error on a porterbox. Thanks!
Bug#860508: qtcharts-opensource-src: FTBFS on hurd-i386: test hangs
Source: qtcharts-opensource-src Version: 5.7.1-1 Severity: important Justification: fails to build from source The build of qtcharts-opensource-src for hurd-i386 (admittedly not a release architecture) failed: make[3]: Entering directory '/<>/tests/auto/qml-qtquicktest' /<>/tests/auto/qml-qtquicktest/target_wrapper.sh ./tst_qml-qtquicktest Unrecognized OpenGL version Unrecognized OpenGL version Makefile:279: recipe for target 'check' failed make[3]: *** [check] Killed [...] E: Build killed with signal TERM after 180 minutes of inactivity E: Build killed with signal KILL after 360 minutes of inactivity E: Build killed with signal KILL after 540 minutes of inactivity E: Build killed with signal KILL after 720 minutes of inactivity Could you please take a look? Thanks!
Bug#860509: qtcharts-opensource-src: FTBFS on sparc64: Segmentation fault
Source: qtcharts-opensource-src Version: 5.7.1-1 Severity: important Justification: fails to build from source The qtcharts-opensource-src build for sparc64 (admittedly not a release architecture) failed: make[3]: Leaving directory '/<>/tests/auto/qml' JIT is disabled for QML. Property bindings and animations will be very slow. Visit https://wiki.qt.io/V4 to learn about possible solutions for your platform. Makefile:287: recipe for target 'check' failed make[3]: *** [check] Segmentation fault make[3]: Leaving directory '/<>/tests/auto/qml-qtquicktest' Makefile:1724: recipe for target 'sub-qml-qtquicktest-check' failed make[2]: *** [sub-qml-qtquicktest-check] Error 2 make[2]: Leaving directory '/<>/tests/auto' dh_auto_test: make -j4 check -Ctests/auto QML2_IMPORT_PATH=/<>/test_root/usr/lib/sparc64-linux-gnu/qt5/qml returned exit code 2 debian/rules:39: recipe for target 'override_dh_auto_test' failed make[1]: *** [override_dh_auto_test] Error 2 Could you please take a look? I don't have further details, but perhaps you can reproduce the problem on a porterbox. Thanks!
Bug#864323: qtwebengine-opensource-src: FTBFS on armel: gnu/stubs-hard.h missing
Source: qtwebengine-opensource-src Version: 5.7.1+dfsg-6.1 Severity: important Tags: upstream Justification: fails to build from source The armel build of qtwebengine-opensource-src failed: /usr/include/arm-linux-gnueabi/gnu/stubs.h:10:29: fatal error: gnu/stubs-hard.h: No such file or directory # include This error presumably relates to the use of -mfloat-abi=hard, which is inappropriate on armel and redundant on armhf. Could you please look into it? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#864324: qtwebengine-opensource-src: FTBFS on big-endian archs -- skia errors
Source: qtwebengine-opensource-src Version: 5.7.1+dfsg-6.1 Severity: important Tags: upstream Justification: fails to build from source Builds of qtwebengine-opensource-src on big-endian architectures (of which only mips has all build dependencies available) have been failing with skia errors, as excerpted below. Could you please take a look? If these errors are infeasible to fix, please restrict qtwebengine-opensource-src's Architecture: field accordingly so autobuilders that are guaranteed to fail don't bother trying to touch it. Thanks! /«BUILDDIR»/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/skia/config/SkUserConfig.h:194:2: error: #error Read the comment at this location #error Read the comment at this location ^ In file included from /«BUILDDIR»/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/core/SkPixmap.h:13:0, from /«BUILDDIR»/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/src/core/SkBlitMask.h:13, from /«BUILDDIR»/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/src/opts/SkBlitMask_opts_none.cpp:8: /«BUILDDIR»/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/core/SkImageInfo.h:84:6: error: #error "SK_*32_SHFIT values must correspond to BGRA or RGBA byte order" #error "SK_*32_SHFIT values must correspond to BGRA or RGBA byte order" ^ /«BUILDDIR»/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/core/SkImageInfo.h: In static member function 'static SkImageInfo SkImageInfo::MakeN32(int, int, SkAlphaType, SkColorProfileType)': /«BUILDDIR»/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/core/SkImageInfo.h:185:43: error: 'kN32_SkColorType' was not declared in this scope return SkImageInfo(width, height, kN32_SkColorType, at, pt); ^~~~ /«BUILDDIR»/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/core/SkImageInfo.h: In static member function 'static SkImageInfo SkImageInfo::MakeN32Premul(int, int, SkColorProfileType)': /«BUILDDIR»/qtwebengine-opensource-src-5.7.1+dfsg/src/3rdparty/chromium/third_party/skia/include/core/SkImageInfo.h:193:43: error: 'kN32_SkColorType' was not declared in this scope return SkImageInfo(width, height, kN32_SkColorType, kPremul_SkAlphaType, pt); -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#864325: qtwebengine-opensource-src: FTBFS on ppc64el: architecture officially unsupported
Source: qtwebengine-opensource-src Version: 5.7.1+dfsg-6.1 Severity: important Tags: upstream Justification: fails to build from source The ppc64el build of qtwebengine-opensource-src failed: QtWebEngine can only be built for x86, x86-64, ARM, Aarch64, MIPSel, and MIPS64 architectures. QtWebEngine will not be built. I suppose you could try disabling this sanity check, but I suspect you'll then have non-trivial porting to do, so you may simply need to limit qtwebengine-opensource-src's Architecture: field accordingly. Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#864326: qtwebengine-opensource-src: FTBFS on non-Linux: Unknown platform.
Source: qtwebengine-opensource-src Version: 5.7.1+dfsg-6.1 Severity: important Tags: upstream Justification: fails to build from source Builds of qtwebengine-opensource-src for kFreeBSD (admittedly not a release architecture) have been failing: Unknown platform. Qt WebEngine only supports Linux, Windows, and OS X. I suppose you could try disabling this sanity check, but I suspect you'll then have non-trivial porting to do, so you may simply need to limit qtwebengine-opensource-src's Architecture: field accordingly. (That said, treating kFreeBSD and, potentially, the Hurd like Linux may be worth a shot here.) Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#864324: qtwebengine-opensource-src: FTBFS on big-endian archs -- skia errors
Sandro Knauß writes: > https://anonscm.debian.org/cgit/pkg-kde/qt/qtwebengine.git/tree/debian/ > patches/add_mips_support.patch I suspect there's no easy fix here, so you might just have to report an upstream bug and meanwhile restrict the package's Architecture setting. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#864323: qtwebengine-opensource-src: FTBFS on armel: gnu/stubs-hard.h missing
Sandro Knauß writes: > I really would like to get qtwebengine building on more architectures, but > I'm > not very familiar with other architectures, so I'm simply very lost in how to > fix those issues. Can you help here? I already started with on a patch, but > it > was not working at the moment ( see comment in the file): > https://anonscm.debian.org/cgit/pkg-kde/qt/qtwebengine.git/tree/debian/ > patches/unsused-add_armel_support.patch Thanks for looking into this bug. I'm not very familiar with gyp, but can try to help out when I get a chance. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#864325: qtwebengine-opensource-src: FTBFS on ppc64el: architecture officially unsupported
Sandro Knauß writes: > I'm quite new a DD, so I have no idea of the best practise in this case. I > have hardly knowledge about other archs, so I thought, I leave the archs > failing, so others can start working on it seeing, why it it failing etc. That's fair, but means that the autobuilders spend time attempting to run builds that will definitely not succeed. I would report an upstream bug and meanwhile restrict the Architecture setting. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#719339: qttools-opensource-src: FTBFS on i386: symbols not quite as expected
Source: qttools-opensource-src Version: 5.1.0-2 Severity: serious Justification: fails to build from source The i386 build of of qttools-opensource-src failed due to .symbols discrepancies; could you please update the expected results? Thanks! -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130811041140.5700.65049.report...@ghostwheel.internal.ucko.debian.net
Bug#719339: No meed to make bugs for this
Lisandro Damián Nicanor Pérez Meyer writes: > Hi Aaron! When you see a new upstream release of our packages, there is no > need to fill bugs because it FTBFS because of symbols mismatches: we know of > them (and actually, we normally expect them in the first upload of a new > version). Great, thanks. Sorry for the noise; I try to err somewhat on the side of overreporting for the FTBFS bugs I track (for binary packages showing up on amd64 but not i386 or vice versa) to help ensure that nothing slips through the cracks, but will bear your diligence (which I certainly appreciate) in mind. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/udlli477f1z@dr-wily.mit.edu
Bug#721580: qtcreator: FTBFS on kfreebsd-*: dh_install: missing files, aborting
Source: qtcreator Version: 2.8.1-1 Severity: serious Justification: fails to build from source Builds of qtcreator on kfreebsd-amd64 and kfreebsd-i386 have been failing: dh_install --fail-missing dh_install: usr/lib/x86_64-kfreebsd-gnu/qtcreator/libqbscore.so.1.0.0 exists in debian/tmp but is not installed to anywhere dh_install: usr/lib/x86_64-kfreebsd-gnu/qtcreator/libqbscore.so exists in debian/tmp but is not installed to anywhere dh_install: usr/lib/x86_64-kfreebsd-gnu/qtcreator/libqbscore.so.1 exists in debian/tmp but is not installed to anywhere dh_install: usr/lib/x86_64-kfreebsd-gnu/qtcreator/libqbscore.so.1.0 exists in debian/tmp but is not installed to anywhere dh_install: usr/lib/x86_64-kfreebsd-gnu/qtcreator/plugins/QtProject/libPythonEditor.so exists in debian/tmp but is not installed to anywhere dh_install: usr/lib/x86_64-kfreebsd-gnu/qtcreator/plugins/QtProject/PythonEditor.pluginspec exists in debian/tmp but is not installed to anywhere dh_install: usr/lib/x86_64-kfreebsd-gnu/qtcreator/plugins/QtProject/libQbsProjectManager.so exists in debian/tmp but is not installed to anywhere dh_install: usr/lib/x86_64-kfreebsd-gnu/qtcreator/plugins/QtProject/QbsProjectManager.pluginspec exists in debian/tmp but is not installed to anywhere dh_install: missing files, aborting make[1]: *** [override_dh_install] Error 2 A quick look at your packaging suggests that you may need to move a few entries from qtcreator.install.linux to the general qtcreator.install. Could you please look into the matter? Thanks! -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130902020253.32614.39014.report...@ghostwheel.internal.ucko.debian.net
Bug#730033: okteta: FTBFS: 'QDir().mkpath(path)' returned FALSE.
Source: okteta Version: 4:4.11.3-1 Severity: serious Justification: fails to build from source Automatic builds of okteta for most architectures failed with test suite errors: * Start testing of TestDocumentFileSynchronizerTest * Config: Using QTest library 4.8.6, Qt 4.8.6 FAIL! : TestDocumentFileSynchronizerTest::initTestCase() 'QDir().mkpath(path)' returned FALSE. () Loc: [../../../../../libs/kasten/core/tests/util/filesystem.cpp(71)] PASS : TestDocumentFileSynchronizerTest::cleanupTestCase() Totals: 1 passed, 1 failed, 0 skipped * Finished testing of TestDocumentFileSynchronizerTest * [...] The following tests FAILED: 2 - libkasten-core-testdocumentfilesynchronizertest (Failed) 3 - libkasten-core-testdocumentfilesynchronizerfactorytest (Failed) 40 - oktetakasten-io-bytearrayrawfilesynchronizertest (Failed) 41 - oktetakasten-io-bytearrayrawfilesynchronizerfactorytest (Failed) I suspect these tests were relying on a writable HOME, which Debian's autobuilders don't provide. At any rate, could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131120150848.24633.68922.report...@ghostwheel.internal.ucko.debian.net
Bug#730035: okteta: FTBFS on hurd-i386: symbols not quite as expected
Source: okteta Version: 4:4.11.3-1 Severity: important The hurd-i386 build of okteta failed with symbols mismatches: dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libokteta1core1/DEBIAN/symbols doesn't match completely debian/libokteta1core1.symbols --- debian/libokteta1core1.symbols (libokteta1core1_4:4.11.3-1_hurd-i386) +++ dpkg-gensymbolspKxCbk 2013-11-11 21:52:51.0 + @@ -37,8 +37,8 @@ _ZN6Okteta14ByteArrayModelD0Ev@ABI_1_0 4:4.8.4 _ZN6Okteta14ByteArrayModelD1Ev@ABI_1_0 4:4.8.4 _ZN6Okteta14ByteArrayModelD2Ev@ABI_1_0 4:4.8.4 - (arch=!amd64)_ZN6Okteta15ByteArrayChangeD1Ev@ABI_1_0 4:4.8.4 - (arch=!amd64)_ZN6Okteta15ByteArrayChangeD2Ev@ABI_1_0 4:4.8.4 +#MISSING: 4:4.11.3-1# (arch=!amd64)_ZN6Okteta15ByteArrayChangeD1Ev@ABI_1_0 4:4.8.4 +#MISSING: 4:4.11.3-1# (arch=!amd64)_ZN6Okteta15ByteArrayChangeD2Ev@ABI_1_0 4:4.8.4 _ZN6Okteta18FileByteArrayModel11setModifiedEb@ABI_1_0 4:4.8.4 _ZN6Okteta18FileByteArrayModel11setReadOnlyEb@ABI_1_0 4:4.8.4 _ZN6Okteta18FileByteArrayModel4fillEhii@ABI_1_0 4:4.8.4 dh_makeshlibs: dpkg-gensymbols -plibokteta1core1 -Idebian/libokteta1core1.symbols -Pdebian/libokteta1core1 -edebian/libokteta1core1/usr/lib/libokteta1core.so.0.8.1 returned exit code 1 Could you please adjust libokteta1core1.symbols to reflect reality? Thanks! -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131120151251.25985.98844.report...@ghostwheel.internal.ucko.debian.net
Bug#730037: okteta: FTBFS on mips: structures-common-parser test times out
Source: okteta Version: 4:4.11.3-1 Severity: serious Justification: fails to build from source (but built successfully in the past) The okteta build for mips timed out, apparently when running the structures-common-parser test: Start 51: structures-common-parser Start 52: structures-js-parser Start 53: structures-custom-to-string 46/54 Test #49: structures-scriptvalue-converter . Passed1.46 sec 47/54 Test #46: structures-script-classes Passed2.20 sec Start 54: structures-lock-to-offset 48/54 Test #45: structures-primitive-datainformation . Passed2.72 sec 49/54 Test #53: structures-custom-to-string .. Passed1.41 sec 50/54 Test #50: structures-osd-parser Passed2.05 sec 51/54 Test #52: structures-js-parser . Passed1.73 sec 52/54 Test #54: structures-lock-to-offset Passed1.41 sec 53/54 Test #26: libokteta-core-charcodectest . Passed 10.50 sec E: Caught signal ‘Terminated’: terminating immediately make[2]: *** [test] Terminatedmake[1]: *** [pre_build_dh_auto_test] Terminated make: *** [debian/dhmk_build] Terminated Build killed with signal TERM after 300 minutes of inactivity Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131120152032.26135.11627.report...@ghostwheel.internal.ucko.debian.net
Bug#730036: okteta: FTBFS on ia64: several structures tests fail
Source: okteta Version: 4:4.11.3-1 Severity: important Builds of okteta on ia64 run into several test suite failures on top of #730033, as detailed at https://buildd.debian.org/status/fetch.php?pkg=okteta&arch=ia64&ver=4%3A4.11.3-1&stamp=1384191210: The following tests FAILED: 2 - libkasten-core-testdocumentfilesynchronizertest (Failed) 3 - libkasten-core-testdocumentfilesynchronizerfactorytest (Failed) 40 - oktetakasten-io-bytearrayrawfilesynchronizertest (Failed) 41 - oktetakasten-io-bytearrayrawfilesynchronizerfactorytest (Failed) 46 - structures-script-classes (Failed) 49 - structures-scriptvalue-converter (Failed) 50 - structures-osd-parser (Failed) 52 - structures-js-parser (Failed) 53 - structures-custom-to-string (Failed) Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131120151704.26056.40235.report...@ghostwheel.internal.ucko.debian.net
Bug#730327: kstars: FTBFS w/o writable HOME: tests fail
Source: kstars Version: 4:4.11.3-2 Severity: serious Justification: fails to build from source (but built successfully in the past) Builds of kstars in environments without writable HOME directories (as on nearly all autobuilders) have been failing: 1/2 Test #2: FixedWidthParserTest .***Failed0.06 sec trying to create local folder /sbuild-nonexistent: Permission denied trying to create local folder /sbuild-nonexistent: Permission denied testfwparser(896) TestFWParser::TestFWParser: "Couldn't open(/sbuild-nonexistent/.kde/share/apps/kde/TestFW.txt)" testfwparser(896) KSParser::KSParser: Unable to open file: "/sbuild-nonexistent/.kde/share/apps/kde/TestFW.txt" Please try running the test suite with HOME set to a directory within the build tree created for that purpose. Thanks! -- To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131124041047.25226.12036.report...@ghostwheel.internal.ucko.debian.net
Bug#868993: qtvirtualkeyboard-opensource-src: FTBFS: test crashes
Source: qtvirtualkeyboard-opensource-src Version: 5.7.1+dfsg-2 Severity: important Justification: fails to build from source Builds of qtvirtualkeyboard-opensource-src failed on several architectures because tst_inputpanel crashed, with "Illegal instruction" on armhf and "Segmentation fault" on mips, mips64el, and the non-release architecture sparc64. (The mipsel build succeeded, though.) Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#873461: krita: FTBFS on armel: OpenGL/EGL-related errors
Source: krita Version: 1:3.2.1+dfsg-1 Severity: important Justification: fails to build from source Builds of krita for armel have been failing with OpenGL-related compilation errors, as detailed at https://buildd.debian.org/status/fetch.php?pkg=krita&arch=armel&ver=1%3A3.2.1%2Bdfsg-1&stamp=1503696867&raw=0 and (very partially) excerpted below. It may be relevant that Qt here appears to be using EGL rather than traditional OpenGL. Could you please take a look? Thanks! /<>/krita-3.2.1+dfsg/libs/ui/opengl/kis_opengl_canvas2.cpp:106:5: error: 'QOpenGLFunctions_2_1' does not name a type; did you mean 'QOpenGLFunctions'? QOpenGLFunctions_2_1 *glFn201; [...] /<>/krita-3.2.1+dfsg/libs/ui/opengl/kis_opengl_canvas2.cpp:398:12: error: 'GL_LINE_SMOOTH_HINT' was not declared in this scope glHint(GL_LINE_SMOOTH_HINT, GL_NICEST); ^~~ /<>/krita-3.2.1+dfsg/libs/ui/opengl/kis_opengl_canvas2.cpp:398:12: note: suggested alternative: 'GL_LINE_STRIP' glHint(GL_LINE_SMOOTH_HINT, GL_NICEST); ^~~ GL_LINE_STRIP /<>/krita-3.2.1+dfsg/libs/ui/opengl/kis_opengl_canvas2.cpp:400:14: error: 'GL_COLOR_LOGIC_OP' was not declared in this scope glEnable(GL_COLOR_LOGIC_OP); ^ /<>/krita-3.2.1+dfsg/libs/ui/opengl/kis_opengl_canvas2.cpp:400:14: note: suggested alternative: 'GL_COLORDODGE_NV' glEnable(GL_COLOR_LOGIC_OP); ^ [...] -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (300, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386, x32 Kernel: Linux 4.12.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Bug#879964: qtgraphicaleffects-opensource-src: FTBFS on sparc64: tst_qtgraphicaleffects segfault at startup
Source: qtgraphicaleffects-opensource-src Version: 5.9.2-2 Severity: important Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-sp...@lists.debian.org Builds of qtgraphicaleffects-opensource-src for sparc64 (admittedly not a release architecture) have been failing lately, with tst_qtgraphicaleffects segfaulting before it can even print the usual "Start testing" banner: /<>/tests/auto/target_wrapper.sh ./tst_qtgraphicaleffects JIT is disabled for QML. Property bindings and animations will be very slow. Visit https://wiki.qt.io/V4 to learn about possible solutions for your platform. Makefile:308: recipe for target 'check' failed make[4]: *** [check] Segmentation fault I don't have additional details, but perhaps you can reproduce the problem on a porter box (though the project-wide one is currently out of service, alas). Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#879966: qtgraphicaleffects-opensource-src: FTBFS on x32: tst_qtgraphicaleffects::blend() Received signal 11
Source: qtgraphicaleffects-opensource-src Version: 5.9.1-2 Severity: important Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-am...@lists.debian.org Builds of qtgraphicaleffects-opensource-src for x32 (admittedly not a release architecture) have been failing lately: /<>/tests/auto/target_wrapper.sh ./tst_qtgraphicaleffects * Start testing of tst_qtgraphicaleffects * Config: Using QtTest library 5.9.2, Qt 5.9.2 (x86_64-little_endian-ilp32 shared (dynamic) release build; by GCC 7.2.0) PASS : tst_qtgraphicaleffects::initTestCase() = Received signal, dumping stack == = End of stack trace == QFATAL : tst_qtgraphicaleffects::blend() Received signal 11 Function time: 5ms Total time: 5ms FAIL! : tst_qtgraphicaleffects::blend() Received a fatal error. Loc: [Unknown file(0)] Totals: 1 passed, 1 failed, 0 skipped, 0 blacklisted, 6ms * Finished testing of tst_qtgraphicaleffects * Makefile:308: recipe for target 'check' failed make[4]: *** [check] Aborted Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#879967: qtmultimedia-opensource-src: FTBFS on sparc64: tst_qdeclarativemultimediaglobal segfault at startup
Source: qtmultimedia-opensource-src Version: 5.9.2-1 Severity: important Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-sp...@lists.debian.org Builds of qtmultimedia-opensource-src for sparc64 (admittedly not a release architecture) have been failing lately, with tst_qdeclarativemultimediaglobal segfaulting before it can even print the usual "Start testing" banner: /<>/tests/auto/unit/qdeclarativemultimediaglobal/target_wrapper.sh ./tst_qdeclarativemultimediaglobal QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/108', please create it with 0700 permissions. JIT is disabled for QML. Property bindings and animations will be very slow. Visit https://wiki.qt.io/V4 to learn about possible solutions for your platform. Makefile:460: recipe for target 'check' failed make[4]: *** [check] Segmentation fault I don't have additional details, but perhaps you can reproduce the problem on a porter box (though the project-wide one is currently out of service, alas). Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#879970: qtwebsockets-opensource-src: FTBFS on sparc64 and x32: tst_qmlwebsockets segfault at startup
Source: qtwebsockets-opensource-src Version: 5.9.2-2 Severity: important Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-sp...@lists.debian.org Builds of qtwebsockets-opensource-src for sparc64 and x32 (admittedly not release architectures) have been failing lately, with tst_qmlwebsockets segfaulting before even printing the usual "Start testing" banner, per the following excerpts from (respectively) https://buildd.debian.org/status/fetch.php?pkg=qtwebsockets-opensource-src&arch=sparc64&ver=5.9.2-2&stamp=1509065867&raw=0 https://buildd.debian.org/status/fetch.php?pkg=qtwebsockets-opensource-src&arch=x32&ver=5.9.2-2&stamp=1509120783&raw=0 /<>/tests/auto/qml/qmlwebsockets/target_wrapper.sh ./tst_qmlwebsockets QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/112', please create it with 0700 permissions. JIT is disabled for QML. Property bindings and animations will be very slow. Visit https://wiki.qt.io/V4 to learn about possible solutions for your platform. Makefile:323: recipe for target 'check' failed make[4]: *** [check] Segmentation fault /<>/tests/auto/qml/qmlwebsockets/target_wrapper.sh ./tst_qmlwebsockets QStandardPaths: XDG_RUNTIME_DIR points to non-existing path '/run/user/114', please create it with 0700 permissions. Makefile:323: recipe for target 'check' failed make[4]: *** [check] Segmentation fault Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#879967: qtmultimedia-opensource-src: FTBFS on sparc64: tst_qdeclarativemultimediaglobal segfault at startup
"Aaron M. Ucko" writes: > Builds of qtmultimedia-opensource-src for sparc64 (admittedly not a > release architecture) have been failing lately, with > tst_qdeclarativemultimediaglobal segfaulting before it can even print > the usual "Start testing" banner: I see the same behavior (albeit without the JIT warning) on x32, just obscured by running tests in parallel. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#882039: kdevelop: FTBFS on x32: CXType_Elaborated not declared
Source: kdevelop Version: 4:5.2.0-2 Severity: important Tags: upstream Justification: fails to build from source (but built successfully in the past) User: debian-am...@lists.debian.org Usertags: x32 Builds of kdevelop for x32 (admittedly not a release architecture) have been failing lately, with a cascade of errors starting with /<>/plugins/clang/duchain/builder.cpp:687:44: error: 'CXType_Elaborated' was not declared in this scope You can find the full log at https://buildd.debian.org/status/fetch.php?pkg=kdevelop&arch=x32&ver=4%3A5.2.0-2&stamp=1510940763&raw=0 Could you please take a look? Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#836412: qtwebchannel-opensource-src: FTBFS (big-endian): qtbug46548_overriddenProperties() Received signal 11
Source: qtwebchannel-opensource-src Version: 5.6.1-1 Severity: important Justification: fails to build from source Builds of qtwebchannel-opensource-src on big-endian architectures (so far, mips, and powerpc, plus the non-release architectures hppa and sparc64) have been failing: = Received signal, dumping stack == = End of stack trace == QFATAL : TestWebChannel::qtbug46548_overriddenProperties() Received signal 11 Function time: 21ms Total time: 1282ms FAIL! : TestWebChannel::qtbug46548_overriddenProperties() Received a fatal error. Loc: [Unknown file(0)] Totals: 12 passed, 1 failed, 0 skipped, 0 blacklisted * Finished testing of TestWebChannel * Could you please take a look? Thanks!
Bug#836412: qtwebchannel-opensource-src: FTBFS (big-endian): qtbug46548_overriddenProperties() Received signal 11
= 0x100047e0
,
relatedMetaObjects = 0x0,
extradata = 0x0}}, m_transport = 0x100fca20,
m_logger = 0x1011c240}
spy = { = {}, >> =
{ >> = {}, {p = {
static shared_null = {ref = {atomic = {
_q_value = {> = {
static _S_alignment = 4,
_M_i = -1}, }}}, alloc = 0,
begin = 0, end = 0, array = {0x0}}, d = 0x0}, d = 0x0}},
sig = {d = 0xffa186c0}, args = {d = 0xffa17ff8},
m_loop = , m_waiting = false}
subclassedTestObject = {d = 4288773300}
#18 0x10012984 in TestWebChannel::qt_static_metacall (_o=,
_id=, _a=, _c=)
at .moc/moc_tst_webchannel.cpp:1137
_t =
#19 0x0f840ea0 in QMetaMethod::invoke(QObject*, Qt::ConnectionType,
QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument) const ()
from /usr/lib/powerpc-linux-gnu/libQt5Core.so.5
No symbol table info available.
#20 0x0f847480 in QMetaObject::invokeMethod(QObject*, char const*,
Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument,
QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) ()
from /usr/lib/powerpc-linux-gnu/libQt5Core.so.5
No symbol table info available.
#21 0x0fb23540 in ?? () from /usr/lib/powerpc-linux-gnu/libQt5Test.so.5
No symbol table info available.
#22 0x0fb24434 in QTest::qExec(QObject*, int, char**) ()
from /usr/lib/powerpc-linux-gnu/libQt5Test.so.5
No symbol table info available.
#23 0x10004014 in main (argc=, argv=0xffa18964)
at tst_webchannel.cpp:615
app =
tc = { = {}, static staticMetaObject = {d = {
superdata = 0xfae6970 ,
stringdata = 0x10015c34 ,
data = 0x10015eac ,
static_metacall = 0x100129a0
,
relatedMetaObjects = 0x0,
extradata = 0x0}}, m_dummyTransport = 0x100e2640,
m_lastInt = 1000, m_lastDouble = 1000, m_lastVariant = {d = {data = {
c = 64 '@', uc = 64 '@', s = 16527, sc = 64 '@', us = 16527,
i = 1083129856, u = 1083129856, l = 1083129856,
ul = 1083129856, b = 64, d = 1000, f = 4.4765625, real = 1000,
ll = 4652007308841189376, ull = 4652007308841189376,
o = 0x408f4000, ptr = 0x408f4000, shared = 0x408f4000},
type = 6, is_shared = 0, is_null = 0}}}
Detaching from program:
/home/ucko/qtwebchannel-opensource-src/tests/auto/webchannel/tst_webchannel,
process 16526
= End of stack trace ==
QFATAL : TestWebChannel::qtbug46548_overriddenProperties() Received signal 11
Function time: 75ms Total time: 1277ms
FAIL! : TestWebChannel::qtbug46548_overriddenProperties() Received a fatal
error.
Loc: [Unknown file(0)]
Totals: 12 passed, 1 failed, 0 skipped, 0 blacklisted
* Finished testing of TestWebChannel *
-- Aaron
Sandro Knauß writes:
> Hey,
>
> I'm currently not a DD so I don't know how to run such big-endian platforms
> to
> get a backtrace (gdb, valgrind). Because I'm at QtCon I can actually talk to
> upstream persons you wrote qtwebchannel - but therefore I need more
> informations to fix. Can you do that for me?
>
> Regards,
>
> sandro
>
> Am Freitag, 2. September 2016, 13:52:38 CEST schrieb Aaron M. Ucko:
>> Source: qtwebchannel-opensource-src
>> Version: 5.6.1-1
>> Severity: important
>> Justification: fails to build from source
>>
>> Builds of qtwebchannel-opensource-src on big-endian architectures (so
>> far, mips, and powerpc, plus the non-release architectures hppa and
>> sparc64) have been failing:
>>
>> = Received signal, dumping stack ==
>> = End of stack trace ==
>> QFATAL : TestWebChannel::qtbug46548_overriddenProperties() Received signal
>> 11 Function time: 21ms Total time: 1282ms
>> FAIL! : TestWebChannel::qtbug46548_overriddenProperties() Received a
>> fatal error. Loc: [Unknown file(0)]
>> Totals: 12 passed, 1 failed, 0 skipped, 0 blacklisted
>> * Finished testing of TestWebChannel *
>>
>> Could you please take a look?
>>
>> Thanks!
Bug#541539: libkde4-ruby: binNMU-unsafe dependencies on libsmokeqt4-2 and libqtruby4shared2
Package: libkde4-ruby
Version: 4:4.3.0-1
Severity: important
libkde4-ruby has tight dependencies on libqtruby4shared2 and
libsmokeqt4-2; however, because those packages are
architecture-dependent but libkde4-ruby itself is not, binary-only
NMUs (as recently occurred to work around a glitch resulting in
unversioned dependencies on libc6) render them unsatsfiable. I see
three general options:
- Move the dependencies to libkde4-ruby1.8 rather than imposing extra
constraints from what should be a simple metapackage, or perhaps
eliminate them altogether.
- Loosen them to account for possible rebuilds:
libqtruby4shared2 (>= ${source:Version}),
libqtruby4shared2 (<< ${source:Version}+c)
libsmokeqt4-2 (>= ${source:Version}), libsmokeqt4-2 (<< ${source:Version}+c)
- Make libkde4-ruby nominally architecture-dependent.
At any rate, could you please correct the situation?
Thanks!
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libkde4-ruby depends on:
ii libkde4-ruby1.8 4:4.3.0-1 KDE 4 bindings for Ruby
ii libqtruby4shared2 4:4.3.0-1 internal library for Qt 4 Ruby bin
ii libsmokeqt4-2 4:4.3.0-1 Qt 4 Smoke libraries
libkde4-ruby recommends no packages.
libkde4-ruby suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to debian-qt-kde-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#350297: kdeedu-doc-html: ships obsolete doc-base file for kmessedwords
Package: kdeedu-doc-html Version: 4:3.5.0-4 Severity: important I've found that kdeedu-doc-html lacks a proper doc-base file for kanagram, instead continuing to ship one that refers to the obsolete kmessedwords package. On systems with dhelp installed and kmessedwords garbage-collected (or never installed in the first place), this resuls in an installation/upgrade error: Setting up kdeedu-doc-html (3.5.0-4) ... cannot create dhelp file '/usr/share/doc/kde/HTML/en/kmessedwords/.dhelp': No such file or directory dpkg: error processing kdeedu-doc-html (--configure): subprocess post-installation script returned error exit status 2 Could you please fix this? I imagine it should be pretty straightforward. BTW, I've also noticed that the kdeedu metapackage lacks a dependency on kgeography; please let me know if you'd like a separate report for that. Thanks! -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[P-a-s] Please enable %firebird2/amd64 to help unblock qt-x11-free.
Greetings. As an amd64 user (though admittedly not an official porter), I have been following the new official buildd's progress with some interest, and observed a problem with the potential to block quite a few packages: although the firebird2 source package rightly claims to support amd64 (I just verified that 1.5.3.4870-3 builds without errors on my system), Packages-arch-specific lists it as specific to (hurd-)i386. Could you please bless it for amd64 as well? Thanks! [Ordinarily, this wouldn't necessarily be a big deal; however, the old unofficial buildd built a few versions of firebird2 despite the P-a-s entry, so qt-x11-free wound up adding a build-dependency on firebird2-dev on November 29. As such, it will now be in perpetual dep-wait unless something is done to free it, and in turn hold back quite a few other packages -- particularly given gnome-vfs2's counterintuitive indirect build-dependency on qt-x11-free by way of avahi.] -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) Finger [EMAIL PROTECTED] (NOT a valid e-mail address) for more info. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
