kdepim-runtime_4.14.2-4_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 21 Aug 2015 15:01:40 -0700 Source: kdepim-runtime Binary: kdepim-runtime kdepim-runtime-dbg Architecture: source amd64 Version: 4:4.14.2-4 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Diane Trout Description: kdepim-runtime - runtime components for Akonadi KDE kdepim-runtime-dbg - debugging files for Akonadi KDE runtime components Changes: kdepim-runtime (4:4.14.2-4) unstable; urgency=medium . * Team upload * Update build depends of libkolab to 0.6 and libkolabxml to 1.1.0 to help pick up versions rebuilt for gcc-5 transition * Add libsoprano-dev to build-depds. It was apparently being pulled in transitively earlier. * Add Diane Trout to uploaders. * remove forced libkolab0v5 dependency, it appears to be unneeded. Checksums-Sha1: d4a2077bfc413b5d5cd46f247ef35f21f7017b37 2632 kdepim-runtime_4.14.2-4.dsc 216a52c7537fae9789f365339c9faba1461813d3 11000 kdepim-runtime_4.14.2-4.debian.tar.xz 6cb138df2d95022f44d63f63e30a51ce7263497c 51772626 kdepim-runtime-dbg_4.14.2-4_amd64.deb 408288f827c0c99c020eb9aad93d34fb0ef5bae6 2742158 kdepim-runtime_4.14.2-4_amd64.deb Checksums-Sha256: 9dca77bce13c2b586cde01cacc2fb3b47997317220d1c1024838ff20b49dce63 2632 kdepim-runtime_4.14.2-4.dsc fbc8251e92b34a026398bf1ab25335c27ffc874f63709e03576d5bacc19caf78 11000 kdepim-runtime_4.14.2-4.debian.tar.xz 3ef52a7cf11a5b260088c13aaeb78246cfd314ab086647d7cb03ec877f905e9c 51772626 kdepim-runtime-dbg_4.14.2-4_amd64.deb f6ed89de04d0b440568b42cf11272929462c5c5f192f3864d0f2bdc91576d258 2742158 kdepim-runtime_4.14.2-4_amd64.deb Files: 70a99b3fc92762435e35d85fbb84ad03 2632 x11 optional kdepim-runtime_4.14.2-4.dsc 25589676d60182d84e1dbdfa533e20f5 11000 x11 optional kdepim-runtime_4.14.2-4.debian.tar.xz 999df047ddc9aab46478b33c2c6409b3 51772626 debug extra kdepim-runtime-dbg_4.14.2-4_amd64.deb 31e5385693a7198124fce2aa44dd9022 2742158 x11 optional kdepim-runtime_4.14.2-4_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCgAGBQJV17wAAAoJEJkNODZzNNdwgnkP/A2eCTSdl1yQOomGOmyfej2E DNwN2j1sf+L9MZCOM1Vj7+ikYtlvZioXJGPKXw8DUhQCBWPY5G4wEq8WLIH0fNpe mcDappWzx8ZKMG+rpUlIzCCtpDYBRChGos1dDGOkgFO+IS43xpVTZ0rBbzyBxZ3r p5ENboyGH1V6DhhUWo09HWozk/nFLHhrhKXMIVJBFILQu6HSkzNbekt8qKMiBYJB f719JzFtRlFR8SVSVBWErH7w2b8k5uTbzhmXVaP8XVuS277SmzhVKkPJ+zWk4xN/ HqB7jZnp7dJMSEiIpOXK5Ww7X1/WJ6jjec6XBIpXy+/CTKTi9BcBpoUpAFA2vhpd K7+nH+WBSUOCrxpAVnGHBwroId6GxTYsoMpnMgis2MsTkjoK6tzQOkBKpfxbyctN gE1Bwqa3xpHZJO1UY1GoklwUFDnzJrm3cMkDmuLt08ZFY6XFbYfqmgf9b3ruRnV1 ycB2Ry7gpQGMnFDYUKBI9+/EU1en4lW7Jtg5LazWlAYAPihkfX02oFQT2J6aHTiz M/aaSATjI2KKdVS4rxLr9/L3le+AhV6WY/C0SyUJUThr/BHMLAMucCMcY2YF4fJS ke5MNFajmxg0S/UcZGrbZHuoq7pdWbuCWvi1ezimxO7REagLZsCXRjxEWga5+Hv3 nsX7Pmz4ZC5JrUuY+8NI =Hy4t -END PGP SIGNATURE- Thank you for your contribution to Debian.
Processing of kdepim-runtime_4.14.2-4_amd64.changes
kdepim-runtime_4.14.2-4_amd64.changes uploaded successfully to localhost along with the files: kdepim-runtime_4.14.2-4.dsc kdepim-runtime_4.14.2-4.debian.tar.xz kdepim-runtime-dbg_4.14.2-4_amd64.deb kdepim-runtime_4.14.2-4_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)
oxygen-fonts_5.3.2-2_amd64.changes ACCEPTED into unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 21 Aug 2015 17:55:47 -0400 Source: oxygen-fonts Binary: fonts-oxygen ttf-oxygen-font-family Architecture: source all Version: 4:5.3.2-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Scott Kitterman Description: fonts-oxygen - Oxygen font family ttf-oxygen-font-family - transitional package Closes: 796447 Changes: oxygen-fonts (4:5.3.2-2) unstable; urgency=medium . * Team upload. * Add qtbase5-dev to build-depends to fix FTBFS (Closes: #796447) Checksums-Sha1: cf9fceffdcdb43c6805c5674819add56acdcb61c 2157 oxygen-fonts_5.3.2-2.dsc 37fb91c748a760e8ab37d737794716136827e6c5 4664 oxygen-fonts_5.3.2-2.debian.tar.xz 5b3363750f038cf1b91c4732c2af514b05cbd8bd 49304 fonts-oxygen_5.3.2-2_all.deb fa3c06e0cdfc2ff34905c3f57596d70e62ed2efe 4814 ttf-oxygen-font-family_5.3.2-2_all.deb Checksums-Sha256: 2c8d63f240bf782831fcbc4b09c14a33f6935deddb1c1b560d6050880e02a44b 2157 oxygen-fonts_5.3.2-2.dsc c150f09aed95167c78509ed9744de49ad2032d2d4a156647a9b33f8e439bc666 4664 oxygen-fonts_5.3.2-2.debian.tar.xz 3e48e4a4f0750be1fc61954073e87eeae11254796f8eb575f4ac96bfc51b7c10 49304 fonts-oxygen_5.3.2-2_all.deb 9b21df241812393b844dc3448f52f622f361f60d0fbfb93e61b7fe7c0e1ec26a 4814 ttf-oxygen-font-family_5.3.2-2_all.deb Files: c3ae5c89657c1bd481c3e2475b218155 2157 fonts optional oxygen-fonts_5.3.2-2.dsc 7e3d8f6505d3a0d9b1832510988bee7c 4664 fonts optional oxygen-fonts_5.3.2-2.debian.tar.xz 6239e615adae06e11776a445c38fbb2c 49304 fonts optional fonts-oxygen_5.3.2-2_all.deb e87c5f06d9f41f3bc3a21987c56a66ab 4814 oldlibs extra ttf-oxygen-font-family_5.3.2-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJV16ADAAoJEHjX3vua1Zrx/D0P/0nYpdRUhLasJtvWTNwcDxj8 lcJ+puECbLbCrqUjRRO/7HrSj033PSYRsQtzinHR5PffZoRnT49FNflM+SZj7sP3 kS9TJ7ajJqHOzXX4v91DvXC08LxUNEN3zeXXIz4wSQ6u2jD8NNTLGe1X12OisiwS btRMlS1/7ze7sm6ycfvBuv0TISUajoTxR3yp2TkT14h/vwHIV3K8do6CBIJzw6Kt oQbmToS4rCERSgfVHutPP4zzBS1HobLUTjxSSH3uxmgMQ1k1YUVCT5NC4oHO9sXn 8YnbTu8qLzRhbo0fYtXE3tUhfa05fL5YaMNBYkvW2ccyVmtEdnlKs5Y+vX9eipPk ax3cVyzVp8rfpcfmeNsBfVzPIiM2Yl3P4C5hqGoue+cz7T3sCsZuwhK8eg/uhdip dPjMV9SoaIfyOPsTxpFN0xeWaawmYk25z/cG5w25IdgsiEIzF8kvFsVqlUh/v/1J XA+49aFBishWmevgy+bnX0ykXVdZFeaRYdqlpyFvYPUdF1Q+iXg3L2BYTX7sBGIm L5xL4pVB7RgLInauSagnSg0ZL4quJLh44a2sSdDS7ej/+wpxzg2iR6qczldXOzRc bqgJc0yGbIYYovUW7oG324ZyNNl2zY4pg1oZCixIIICKzxFE3MJzkqPDNLMoI2iO nnXsVNHQ58lPtMPhdrHK =jcO1 -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#796447: marked as done (oxygen-fonts: FTBFS: cmake: Failed call: qmake-qt5 -query "QT_INSTALL_PLUGINS")
Your message dated Fri, 21 Aug 2015 22:23:33 + with message-id and subject line Bug#796447: fixed in oxygen-fonts 4:5.3.2-2 has caused the Debian Bug report #796447, regarding oxygen-fonts: FTBFS: cmake: Failed call: qmake-qt5 -query "QT_INSTALL_PLUGINS" 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.) -- 796447: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=796447 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: oxygen-fonts Version: 4:5.3.2-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Warning at /usr/share/ECM/modules/ECMQueryQmake.cmake:22 (message): Failed call: qmake-qt5 -query "QT_INSTALL_PLUGINS" Call Stack (most recent call first): /usr/share/ECM/kde-modules/KDEInstallDirs.cmake:430 (query_qmake) CMakeLists.txt:9 (include) CMake Error at /usr/share/ECM/modules/ECMQueryQmake.cmake:23 (message): QMake call failed: No such file or directory Call Stack (most recent call first): /usr/share/ECM/kde-modules/KDEInstallDirs.cmake:430 (query_qmake) CMakeLists.txt:9 (include) -- Configuring incomplete, errors occurred! Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/oxygen-fonts.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (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 Init: systemd (via /run/systemd/system) --- End Message --- --- Begin Message --- Source: oxygen-fonts Source-Version: 4:5.3.2-2 We believe that the bug you reported is fixed in the latest version of oxygen-fonts, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 796...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman (supplier of updated oxygen-fonts package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 21 Aug 2015 17:55:47 -0400 Source: oxygen-fonts Binary: fonts-oxygen ttf-oxygen-font-family Architecture: source all Version: 4:5.3.2-2 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Scott Kitterman Description: fonts-oxygen - Oxygen font family ttf-oxygen-font-family - transitional package Closes: 796447 Changes: oxygen-fonts (4:5.3.2-2) unstable; urgency=medium . * Team upload. * Add qtbase5-dev to build-depends to fix FTBFS (Closes: #796447) Checksums-Sha1: cf9fceffdcdb43c6805c5674819add56acdcb61c 2157 oxygen-fonts_5.3.2-2.dsc 37fb91c748a760e8ab37d737794716136827e6c5 4664 oxygen-fonts_5.3.2-2.debian.tar.xz 5b3363750f038cf1b91c4732c2af514b05cbd8bd 49304 fonts-oxygen_5.3.2-2_all.deb fa3c06e0cdfc2ff34905c3f57596d70e62ed2efe 4814 ttf-oxygen-font-family_5.3.2-2_all.deb Checksums-Sha256: 2c8d63f240bf782831fcbc4b09c14a33f6935deddb1c1b560d6050880e02a44b 2157 oxygen-fonts_5.3.2-2.dsc c150f09aed95167c78509ed9744de49ad2032d2d4a156647a9b33f8e439bc666 4664 oxygen-fonts_5.3.2-2.debian.tar.xz 3e48e4a4f0750be1fc61954073e87eeae11254796f8eb575f4ac96bfc51b7c10 49304 fonts-oxygen_5.3.2-2_all.deb 9b21df241812393b844dc3448f52f622f361f60d0fbfb93e61b7fe7c0e1ec26a 4814 ttf-oxygen-font-family_5.3.2-2_all.deb Files: c3ae5c89657c1bd481c3e2475b218155 2157 fonts optional oxygen-fonts_5.3.2-2.dsc 7e3d8f6505d3a0d9b1832510988bee7c 4664 fonts optional oxygen-fonts_5.3.2-2.debian.tar.xz 6239e615adae06e11776a445c38fbb2c 49304 fonts optional fonts-oxygen_5.3.2-2_all.deb e87c5f06d9f41f3bc3a21987c56a66ab 4814 oldlibs extra ttf-oxygen-font-family_5.3.2-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJV16ADAAoJEHjX3vua1Zrx/D0P/0nYpdRUhLasJtvWTNwcDxj8 lcJ+puECbLbCrqUjRRO/7HrSj033PSYRsQtzinHR5PffZoRnT49FNflM+SZj7sP3 kS9TJ7ajJqHOzXX4v91DvXC08LxUNEN3
Processing of oxygen-fonts_5.3.2-2_amd64.changes
oxygen-fonts_5.3.2-2_amd64.changes uploaded successfully to localhost along with the files: oxygen-fonts_5.3.2-2.dsc oxygen-fonts_5.3.2-2.debian.tar.xz fonts-oxygen_5.3.2-2_all.deb ttf-oxygen-font-family_5.3.2-2_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)
Bug#796447: oxygen-fonts: FTBFS: cmake: Failed call: qmake-qt5 -query "QT_INSTALL_PLUGINS"
Source: oxygen-fonts Version: 4:5.3.2-1 Severity: serious Justification: fails to build from source Tags: sid stretch User: reproducible-bui...@lists.alioth.debian.org Usertags: ftbfs X-Debbugs-CC: reproducible-bui...@lists.alioth.debian.org Dear Maintainer, The package fails to build: -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Detecting CXX compile features -- Detecting CXX compile features - done CMake Warning at /usr/share/ECM/modules/ECMQueryQmake.cmake:22 (message): Failed call: qmake-qt5 -query "QT_INSTALL_PLUGINS" Call Stack (most recent call first): /usr/share/ECM/kde-modules/KDEInstallDirs.cmake:430 (query_qmake) CMakeLists.txt:9 (include) CMake Error at /usr/share/ECM/modules/ECMQueryQmake.cmake:23 (message): QMake call failed: No such file or directory Call Stack (most recent call first): /usr/share/ECM/kde-modules/KDEInstallDirs.cmake:430 (query_qmake) CMakeLists.txt:9 (include) -- Configuring incomplete, errors occurred! Full build log: https://reproducible.debian.net/rb-pkg/unstable/amd64/oxygen-fonts.html -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.19.0-23-generic (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 Init: systemd (via /run/systemd/system)
Bug#796399:
Probably this bug is related to another bug #796399. After I had edited kwinrc file to change window decoration to breeze, kwin-x11 started crashing when I tried to open any window.
Bug#796411: breeze: Mouse cursors are lacking due to packaging problems
Source: breeze Version: 4:5.3.2-2 Severity: normal https://lists.debian.org/debian-kde/2015/08/msg00101.html and more up to the point https://lists.debian.org/debian-kde/2015/08/msg00112.html and https://lists.debian.org/debian-kde/2015/08/msg00130.html Seems a packaging problem that got fixed in Ubuntu. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'buildd-unstable'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information
Bug#796399: systemsettings: Crash when try to access Window Decorations settings
Package: systemsettings Version: 4:5.3.2-2 Severity: normal Dear Maintainer, Always crashes when I try to go to Apperance / Window Decorations settings. Now there is no possibility to change window decorations. Probably it I started happen after lastest update of libkdecoration2-5 package. This is output from terminal: Plugin changed to: "org.kde.breeze" Constructing a KPluginInfo object from old style JSON. Please use kcoreaddons_desktop_to_json() for "/usr/lib/x86_64-linux- gnu/qt5/plugins/org.kde.kdecoration2/breezedecoration.so" instead of kservice_desktop_to_json() in your CMake code. Constructing a KPluginInfo object from old style JSON. Please use kcoreaddons_desktop_to_json() for "/usr/lib/x86_64-linux- gnu/qt5/plugins/org.kde.kdecoration2/kwin5_aurorae.so" instead of kservice_desktop_to_json() in your CMake code. Constructing a KPluginInfo object from old style JSON. Please use kcoreaddons_desktop_to_json() for "/usr/lib/x86_64-linux- gnu/qt5/plugins/org.kde.kdecoration2/oxygendecoration.so" instead of kservice_desktop_to_json() in your CMake code. Factory: true Setting active : false Setting providesContextHelp : true KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = systemsettings5 path = /usr/bin pid = 32467 KCrash: Arguments: /usr/bin/systemsettings5 KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 [1]+ Kod wyjścia 253systemsettings5 Debug output from KCrash: Application: Ustawienia systemowe (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f73ebb64780 (LWP 31673))] Thread 4 (Thread 0x7f73daeaa700 (LWP 31674)): #0 0x7f73e833f53d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f73e5e0f252 in () at /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f73e5e10ddf in xcb_wait_for_event () at /usr/lib/x86_64-linux- gnu/libxcb.so.1 #3 0x7f73dd402aa9 in QXcbEventReader::run() (this=0xeafe30) at qxcbconnection.cpp:1105 #4 0x7f73e89ba87e in QThreadPrivate::start(void*) (arg=0xeafe30) at thread/qthread_unix.cpp:337 #5 0x7f73e55990a4 in start_thread (arg=0x7f73daeaa700) at pthread_create.c:309 #6 0x7f73e834807d in clone () at .../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f73ce0e8700 (LWP 31675)): #0 0x7f73e559d08f in pthread_cond_wait@@GLIBC_2.3.2 () at .../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x7f73d10e5f3b in radeon_drm_cs_emit_ioctl (mtx=0x10bd650, cond=0x10bd678) at ../../../../../../../include/c11/threads_posix.h:154 #2 0x7f73d10e5f3b in radeon_drm_cs_emit_ioctl (sema=0x10bd650) at .../../../../../../../src/gallium/auxiliary/os/os_thread.h:259 #3 0x7f73d10e5f3b in radeon_drm_cs_emit_ioctl (param=param@entry=0x10bd320) at .../../../../../../../src/gallium/winsys/radeon/drm/radeon_drm_winsys.c:636 #4 0x7f73d10e55b7 in impl_thrd_routine (p=) at .../../../../../../../include/c11/threads_posix.h:87 #5 0x7f73e55990a4 in start_thread (arg=0x7f73ce0e8700) at pthread_create.c:309 #6 0x7f73e834807d in clone () at .../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f73c9efd700 (LWP 31688)): #0 0x7f73e833f53d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f73e5079ebc in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0x7f73c4003070, timeout=-1, context=0x7f73c4000990) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:4103 #2 0x7f73e5079ebc in g_main_context_iterate (context=context@entry=0x7f73c4000990, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3803 #3 0x7f73e5079fcc in g_main_context_iteration (context=0x7f73c4000990, may_block=1) at /tmp/buildd/glib2.0-2.44.1/./glib/gmain.c:3869 #4 0x7f73e8c0335c in QEventDispatcherGlib::processEvents(QFlags) (this=0x7f73c40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #5 0x7f73e8ba7b62 in QEventLoop::exec(QFlags) (this=this@entry=0x7f73c9efce20, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #6 0x7f73e89b58b4 in QThread::exec() (this=) at thread/qthread.cpp:503 #7 0x7f73e73a4f05 in () at /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f73e89ba87e in QThreadPrivate::start(void*) (arg=0x13d01c0) at thread/qthread_unix.cpp:337 #9 0x7f73e55990a4 in start_thread (arg=0x7f73c9efd700) at pthread_create.c:309 #10 0x7f73e834807d in clone () at .../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f73ebb64780 (LWP 31673)): [KCrash Handler] #6 0x7f73c3624d90 in vtable for Breeze::Decoration () at /usr/lib/x86_64 -linux-gnu/qt5/plugins/org.kde.kdecoration2/breezedecoration.so #7 0x7f73e8bb1da9 in QMetaObject::cast(QObject*) const (this=0x7f73c3625b60 , obj=0x7ffdab9b65c8) at kernel/qmetaobject.cpp:331 #8 0x7f73c33f5bb1 in Breeze::Button::c
kdecoration_5.3.2-3_amd64.changes ACCEPTED into unstable, unstable
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Thu, 20 Aug 2015 22:56:47 +0200 Source: kdecoration Binary: libkdecorations2-dev libkdecorations2-5v5 libkdecorations2private5v5 libkdecorations2-dbg Architecture: source amd64 Version: 4:5.3.2-3 Distribution: unstable Urgency: medium Maintainer: Debian/Kubuntu Qt/KDE Maintainers Changed-By: Maximiliano Curia Description: libkdecorations2-5v5 - library to create window decorations libkdecorations2-dbg - library to create window decorations - debug info libkdecorations2-dev - library to create window decorations - development files libkdecorations2private5v5 - library to create window decorations - private library Changes: kdecoration (4:5.3.2-3) unstable; urgency=medium . * Rename library to it's v5 version. Checksums-Sha1: fe891ac2e5b67af8863922a6712cfb62018e00a6 2344 kdecoration_5.3.2-3.dsc 1f1d48b737e345d0c8a5a51dc9b6e157c7117169 6000 kdecoration_5.3.2-3.debian.tar.xz 8ec552d12cba098fc0a22956b98c538e6ce203e3 41700 libkdecorations2-5v5_5.3.2-3_amd64.deb e95ffe7c7051af58b94f5391da93509841630527 892084 libkdecorations2-dbg_5.3.2-3_amd64.deb e36afb22603bdeffdb4fdc3e5fd3665c8c4b5ad6 15554 libkdecorations2-dev_5.3.2-3_amd64.deb f137f338934f6f7899882bd3f07392b07fc9a654 7822 libkdecorations2private5v5_5.3.2-3_amd64.deb Checksums-Sha256: 36ca7099df187e56b0022ec78c26afd4ac9a48e28767d1a038f1ccd1b77b30fe 2344 kdecoration_5.3.2-3.dsc c91a9ce4b005aadc547d5fc3a17655bde3196455390305fe20348618d7a43471 6000 kdecoration_5.3.2-3.debian.tar.xz 483f1bf71cf96976e45509f0d33631c96147e712ba40003589ee69df4941f367 41700 libkdecorations2-5v5_5.3.2-3_amd64.deb 1edced3e3edce3e58e7dcff382de0137559f00e30eb123935a60d617f26c2533 892084 libkdecorations2-dbg_5.3.2-3_amd64.deb f8016804ce2bc0907c419eb25a588f18abd9e3dd1cbdcfbf8b0e949a3d5196ab 15554 libkdecorations2-dev_5.3.2-3_amd64.deb 832c056927c3549681feca474f0b844dfb5807e749a235174ee827b55e8e9c0e 7822 libkdecorations2private5v5_5.3.2-3_amd64.deb Files: 4bab33e0c864ef28e08c2ef8697ab4b6 2344 libs optional kdecoration_5.3.2-3.dsc cac46322cf3a82e6f68fbfbdbaa40008 6000 libs optional kdecoration_5.3.2-3.debian.tar.xz dbfe20dfad35544050cc13c5493fdcfc 41700 libs optional libkdecorations2-5v5_5.3.2-3_amd64.deb 9d4b4950d5d42c9a41e407920291f486 892084 debug extra libkdecorations2-dbg_5.3.2-3_amd64.deb 23bc4714061163925fbdcec23b37c2c0 15554 libdevel optional libkdecorations2-dev_5.3.2-3_amd64.deb e8615123720ccbb056ce294f5b7ecd0b 7822 libs optional libkdecorations2private5v5_5.3.2-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJV1uy8AAoJEMcZdpmymyMqEqgQAKOKs2fUQ7M4mlEcH4vqCI1T sse1KpfZ4yhPz+5bRif86tDlCzXvR4Ffscp0gXAus6xfOljhJ4IY+lDGYIR7NcYN PVYdGK5E6/3wTeGQBuy0f9vkqxWAqexmvw701B4p2Ar9lsZPBkMNlb9vt12+tDEL MSgsKEzQ2vAMLeKEXHyP0kKDKa2egjsmQ0EO0koIR7aERj5HYGCeMMoXv0tks2wt T1VVPbbgTG4O4yjbSbCPRUOrFGgV0RCJMGE6GnnQdSamEjVVyViz965Qv2tdVF1Q YPpTdhrTQKc01cyMeTRHZxF94JA3axIVfKGmGea41xeLR/n30DnEFNfMaIn6kRzw hoiomNS41dyLOoRbWJom11B7n35PuypWMPOffiKgIIWiAKyyiXax7NKz+MMny4Yu jl+nHQOIeOAKlvl/mkgZG0L9TsdtIPba0LEbNnA80u6L0PB8/eouWCtdt+Y/BpfW LBNn1auOEPNE+vBne1NaCJICoRSE2jP0ig1UJ5EiPOk4dFqVem40Psnic3H+AnGa obRWliSKrac8x1+XvQIfRgG3DY0nzGdwLxNbN43lfVnYNFYS8UqDyNiX1Jw4uCLu yvyHr7KKpHOVr4CKuM/Kpb/5L1qQsoSlBJdrdvwOfR8tDwKdbF/C7CHfwxWLrRy1 tC0FWkABvrF9cGYxFRjQ =nF3y -END PGP SIGNATURE- Thank you for your contribution to Debian.
Bug#794581: /usr/bin/kwin_x11: crashes when starting first window
Package: breeze Version: 4:5.3.2-2 Followup-For: Bug #794581 Dear Maintainer, This is the backtrace trying to open the window decoration KCM: Application: System Settings (systemsettings5), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5045e68780 (LWP 16166))] Thread 4 (Thread 0x7f5035359700 (LWP 16167)): #0 0x7f504264553d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7f5040357252 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f5040358ddf in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f50378b1aa9 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so #4 0x7f5042cc087e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f503fae10a4 in start_thread (arg=0x7f5035359700) at pthread_create.c:309 #6 0x7f504264e07d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 3 (Thread 0x7f5027f28700 (LWP 16178)): #0 0x7f5042d76a76 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #1 0x7f5042f06d29 in QTimerInfoList::updateCurrentTime() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7f5042f07295 in QTimerInfoList::timerWait(timespec&) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7f5042f0872e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f503f5c13fd in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f503f5c1de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7f503f5c1fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7f5042f0935c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f5042eadb62 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f5042cbb8b4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7f50416d2055 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #11 0x7f5042cc087e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f503fae10a4 in start_thread (arg=0x7f5027f28700) at pthread_create.c:309 #13 0x7f504264e07d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 2 (Thread 0x7f501b927700 (LWP 19132)): #0 0x7f503f596109 in g_ptr_array_set_size () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f503f5c1351 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f503f5c1de8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f503f5c1fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f5042f0935c in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5042eadb62 in QEventLoop::exec(QFlags) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5042cbb8b4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f50416d2055 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7f5042cc087e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f503fae10a4 in start_thread (arg=0x7f501b927700) at pthread_create.c:309 #10 0x7f504264e07d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111 Thread 1 (Thread 0x7f5045e68780 (LWP 16166)): [KCrash Handler] #6 0x7f501a6f3d90 in vtable for Breeze::Decoration () from /usr/lib/x86_64-linux-gnu/qt5/plugins/org.kde.kdecoration2/breezedecoration.so #7 0x7f5042eb7da9 in QMetaObject::cast(QObject*) const () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f501a4c4bb1 in qobject_cast (object=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobject.h:520 #9 Breeze::Button::create (type=3513564380, decoration=, parent=0x7ffcd16cbd00) at ../../kdecoration/breezebutton.cpp:68 #10 0x7f501bdef917 in KDecoration2::DecorationButtonGroup::DecorationButtonGroup(KDecoration2::DecorationButtonGroup::Position, KDecoration2::Decoration*, std::function) () from /usr/lib/x86_64-linux-gnu/libkdecorations2.so.5 #11 0x7f501a4cbba0 in Breeze::Decoration::createButtons (this=this@entry=0x33c8bf0) at ../../kdecoration/breezedecoration.cpp:344 #12 0x7f501a4cd40a in Breeze::Decoration::init (this=0x33c8bf0) at ../../kdecoration/breezedecoration.cpp:192 #13 0x7f501a703489 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kwin/private/kdecoration/libkdecorationprivatedeclarative.so #14 0x7f50416c9e32 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #15 0x7f5041656cda in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #16 0x7f504165758f in QQmlEnginePrivate::incubate(QQmlIncubator&, QQmlContextData*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #17 0x7f504171bfc7 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #18 0x7f504171c285 in QQmlDelegateModel::object(in
Bug#794581: /usr/bin/kwin_x11: crashes when starting first window
Package: breeze Version: 4:5.3.2-2 Followup-For: Bug #794581 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Same as most people: upgraded to 4:5.3.2-4, stopped working. * What exactly did you do (or not do) that was effective (or ineffective)? Downgraded, first to -3, then to -2. * What was the outcome of this action? Same as before, still crashes, same backtrace as the rest. *** End of the template - remove these template lines *** -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.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 Init: systemd (via /run/systemd/system) Versions of packages breeze depends on: ii breeze-cursor-theme4:5.3.2-2 ii breeze-icon-theme 4:5.3.2-2 ii kde-style-breeze 4:5.3.2-2 ii kde-style-breeze-qt4 4:5.3.2-2 ii kwin-style-breeze 4:5.3.2-2 ii libc6 2.19-19 ii libkf5configcore5 5.13.0-1 ii libkf5coreaddons5 5.13.0-1 ii libkf5i18n55.13.0-1 ii libkf5kcmutils55.12.0-1 ii libqt5core5a 5.4.2+dfsg-5 ii libqt5gui5 5.4.2+dfsg-5 ii libqt5widgets5 5.4.2+dfsg-5 ii libstdc++6 5.1.1-14 ii qml-module-qtquick-controls-styles-breeze 4:5.3.2-2 Versions of packages breeze recommends: pn kde-style-qtcurve Versions of packages breeze suggests: pn orion-gtk-theme -- no debconf information
Bug#792875: fixed in plasma-workspace 4:5.3.2-4
On Thu, 20 Aug 2015 15:12:36 +0200 Christian Hilberg wrote: > Hi, > > I'm seeing the same (or, at least, very similar) crash > with plasma-workspace 5.3.2-4 as of stretch, dist-upgraded > today from jessie. See attached GDB trace. Let me know whether > you're missing debug symbols for one or the other package, I'll be > happy to install the respective symbols and re-create the > trace. > [...] Looks like a packaging issue. The dist-upgrade from jessie to stretch did not install plasma-desktop for me. Installing plasma-desktop and its dependencies fixed the issue for me. Regards, Christian signature.asc Description: This is a digitally signed message part.
kdecoration_5.3.2-3_amd64.changes is NEW
binary:libkdecorations2-5v5 is NEW. binary:libkdecorations2private5v5 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will recieve an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html
Processing of kdecoration_5.3.2-3_amd64.changes
kdecoration_5.3.2-3_amd64.changes uploaded successfully to localhost along with the files: kdecoration_5.3.2-3.dsc kdecoration_5.3.2-3.debian.tar.xz libkdecorations2-5v5_5.3.2-3_amd64.deb libkdecorations2-dbg_5.3.2-3_amd64.deb libkdecorations2-dev_5.3.2-3_amd64.deb libkdecorations2private5v5_5.3.2-3_amd64.deb Greetings, Your Debian queue daemon (running on host franck.debian.org)
Re: kwindowsystem_5.13.0-2_amd64.changes ACCEPTED into unstable
On 2015-08-21 11:20, Mario Fux wrote: Am Freitag, 21. August 2015, 10.48:08 schrieb Pino Toscano: >> >> and given that you're not changed much your modus >> >> operandi wrt that, they *will* happen again. A one-shot issue could >> >> be understandable (everybody makes mistakes, I'm the first to do >> >> them), but >> >> the same issue repeating over time (after being told about) is not. >> > >> > So please be concrete. What do you expect Maxy to do now? Change the >> > past? >> > Most probably not? Apologize? That he did? Change his way of working? >> > As I see >> > it he wrote that he will try hard not to do it again. What else do you >> > expect? >> >> Honestly? I don't expect anything from now on. > > So honestly, what did you want to achieve with these emails then? I can > see > (but of course might be wrong) two things: > - Bringing up this problem (IMHO not in a very constructive way) The constructive way has not worked for years, otherwise we wouldn't be at this point. Do we agree on this? No, we don't agree. Then please do tell me: telling about *the very same issues* to Maxy (= constructive way, right?) lead to... the very same issue happening again and again. What's your stance on this? >> I've been already hit >> by these issues a number of times in the last 3 years (and lately >> I've reducing my contributions to places where Maxy works on too, >> *exactly* to not being hit by that), see also a+b+c+d in [1]. >> >> Look, I understand you are seeing me right now as the "complaining guy >> throwing accusation that random" (which is not), but do you really >> think I would say this if not because I think there *is* a problem >> with this? > > No, I don't think so. But I just don't understand your intentions with > these > emails. I just don't get it and you didn't answer my questions above: > "Be > concrete, what do you expect Maxy to do?" I did answer you: at this point, I expect nothing anymore from him. Ok, then this discussion makes no sense for me anymore and thus is useless. You are right: this discussion with people not having dealt with actual packaging work with Maxy cannot understand all the issues involved in this. As such, I didn't expect you to see anything past the "bad Pino is ranting", and you did not disappoint me in that. And honestly with this it looks really just like a rant from your side. Sorry to say that but that's my perspective and how I (and probably others too) perseive it. Ranting just for the case of ranting and not with the intention to make it somehow better is just destructive and not worth spending more time on it. I told about that I *tried* to have Maxy behave more cooperatively, to make things better. This "rant" is just the last point in a list of other events, and you honestly are looking *only* at it. Pity. -- Pino Toscano
Re: kwindowsystem_5.13.0-2_amd64.changes ACCEPTED into unstable
Am Freitag, 21. August 2015, 10.48:08 schrieb Pino Toscano: Morning Pino [snip] > >> >> and given that you're not changed much your modus > >> >> operandi wrt that, they *will* happen again. A one-shot issue could > >> >> be understandable (everybody makes mistakes, I'm the first to do > >> >> them), but > >> >> the same issue repeating over time (after being told about) is not. > >> > > >> > So please be concrete. What do you expect Maxy to do now? Change the > >> > past? > >> > Most probably not? Apologize? That he did? Change his way of working? > >> > As I see > >> > it he wrote that he will try hard not to do it again. What else do you > >> > expect? > >> > >> Honestly? I don't expect anything from now on. > > > > So honestly, what did you want to achieve with these emails then? I can > > see > > (but of course might be wrong) two things: > > - Bringing up this problem (IMHO not in a very constructive way) > > The constructive way has not worked for years, otherwise we wouldn't > be at this point. Do we agree on this? No, we don't agree. > > - Getting your frustration out (if it helped you, ok, but why public > > then?) > > Considering that the packaging work (git, uploads, etc) are public, > I don't see why I should hide the fact that he's stomping on other > people's public work. > > Also, do you really think this is all about frustration? Seems so for me. But I might be wrong. > >> I've been already hit > >> by these issues a number of times in the last 3 years (and lately > >> I've reducing my contributions to places where Maxy works on too, > >> *exactly* to not being hit by that), see also a+b+c+d in [1]. > >> > >> Look, I understand you are seeing me right now as the "complaining guy > >> throwing accusation that random" (which is not), but do you really > >> think I would say this if not because I think there *is* a problem > >> with this? > > > > No, I don't think so. But I just don't understand your intentions with > > these > > emails. I just don't get it and you didn't answer my questions above: > > "Be > > concrete, what do you expect Maxy to do?" > > I did answer you: at this point, I expect nothing anymore from him. Ok, then this discussion makes no sense for me anymore and thus is useless. And honestly with this it looks really just like a rant from your side. Sorry to say that but that's my perspective and how I (and probably others too) perseive it. Ranting just for the case of ranting and not with the intention to make it somehow better is just destructive and not worth spending more time on it. griits Mario
Re: kwindowsystem_5.13.0-2_amd64.changes ACCEPTED into unstable
Am Freitag, 21. August 2015, 11:01:39 schrieb Pino Toscano: > (Martin: apologies for double email, forgot to send to the list) np > On 2015-08-21 10:57, Pino Toscano wrote: > > On 2015-08-21 10:33, Martin Steigerwald wrote: > >> Hello Pino, > >> > >> Am Freitag, 21. August 2015, 09:45:59 schrieb Pino Toscano: > >>> > Honestly as far as I see it Maxy agreed to your accusations, > >>> > apologize, > >>> > has > >>> > giving as reasonable explanation why this happened, > >>> > >>> Please do read the other reply I wrote yesterday, This is not the > >>> first > >>> time such things happened, it's a cyclic issue that keeps repeating. > >> > >> From your wording I gather that you think Maxy will never change his > >> behavior > >> – driven by your reception of the past experiences you had with him. > >> But he > >> just promised he will try hard to. > > > > Yes, he promised, just like the time before, and the time before that, > > and so on. Every time in the same way, no change. > > > >>> On my side, I actually don't care about this anymore. > >> > >> which is your free decision to do even though I think you actually do > >> care a > >> lot, cause from what I perceive you put a lot of your emotional energy > >> into > >> your last mail. > > > > I'm replying not because I care about the actual issue, but because > > it seems like, because the way I wrote, the issue seems to be shifting > > into "bad Pino rants again good Maxy". As if diplomacy helped with > > Maxy in the past... Pino, thank you for bringing your issue with Maxy up here. No one is bad here. Other than that I intend to leave it as is for now. I shared my point of view. I don´t think reacting further will bring any benefit right now. Ciao, -- Martin
Re: kwindowsystem_5.13.0-2_amd64.changes ACCEPTED into unstable
(Martin: apologies for double email, forgot to send to the list) On 2015-08-21 10:57, Pino Toscano wrote: On 2015-08-21 10:33, Martin Steigerwald wrote: Hello Pino, Am Freitag, 21. August 2015, 09:45:59 schrieb Pino Toscano: > Honestly as far as I see it Maxy agreed to your accusations, apologize, > has > giving as reasonable explanation why this happened, Please do read the other reply I wrote yesterday, This is not the first time such things happened, it's a cyclic issue that keeps repeating. From your wording I gather that you think Maxy will never change his behavior – driven by your reception of the past experiences you had with him. But he just promised he will try hard to. Yes, he promised, just like the time before, and the time before that, and so on. Every time in the same way, no change. On my side, I actually don't care about this anymore. which is your free decision to do even though I think you actually do care a lot, cause from what I perceive you put a lot of your emotional energy into your last mail. I'm replying not because I care about the actual issue, but because it seems like, because the way I wrote, the issue seems to be shifting into "bad Pino rants again good Maxy". As if diplomacy helped with Maxy in the past... As I understand things I can never ever sustainably and directly change someone else´s behavior as we are all free will beings. Yet, you can invite and allow for change to happen, model behavior that you think is good and change your way you deal with behaviors of others. From knowing Maxy a bit from DebConf I fully assume good intentions. As much as I understand that you seem to be frustrated with his past behavior for which he said sorry. So are you willing to set yourself free and forgive him (at least after some time) and probably even assist him in changing? This was *exactly* what I thought myself when committing a couple of changes to kwindowsystem.git, and we all see the result... So no, I don't care what/how he does from now on. Ah, small side note: I know other people were somehow frustrated/hit by his behaviour. -- Pino Toscano
Re: kwindowsystem_5.13.0-2_amd64.changes ACCEPTED into unstable
On 2015-08-21 10:30, Mario Fux wrote: Am Freitag, 21. August 2015, 09.45:59 schrieb Pino Toscano: On 2015-08-21 09:06, Mario Fux wrote: Morning Pino [snip] > Honestly as far as I see it Maxy agreed to your accusations, apologize, > has > giving as reasonable explanation why this happened, Please do read the other reply I wrote yesterday, This is not the first time such things happened, it's a cyclic issue that keeps repeating. I read it. Honestly it looks not, since you are writing as if this would be an isolated case, when Maxy would behave good otherwise. There's lot more to add to this case, so many issues on the packaging side, pointed out to him when I was on IRC ad nauseam, and the net effect of this is that these issues keeps repeating like nothing was said. > is doing a lot of work, > really a lot of work for KDE software packaging in Debian, is (as far > as I see > it) bringing in new people and helping them and seems to be quite > patient. Please note that "does a lot of work" is not a carte blanche to keep doing mistakes on other people's work, despite that being pointed out. And if you read my sentence above again this was not my conclusion at all. There was a listing of tiems and "does a lot of work" was just one item and even then I didn't imply this. >> and given that you're not changed much your modus >> operandi wrt that, they *will* happen again. A one-shot issue could be >> understandable (everybody makes mistakes, I'm the first to do them), >> but >> the same issue repeating over time (after being told about) is not. > > So please be concrete. What do you expect Maxy to do now? Change the > past? > Most probably not? Apologize? That he did? Change his way of working? > As I see > it he wrote that he will try hard not to do it again. What else do you > expect? Honestly? I don't expect anything from now on. So honestly, what did you want to achieve with these emails then? I can see (but of course might be wrong) two things: - Bringing up this problem (IMHO not in a very constructive way) The constructive way has not worked for years, otherwise we wouldn't be at this point. Do we agree on this? - Getting your frustration out (if it helped you, ok, but why public then?) Considering that the packaging work (git, uploads, etc) are public, I don't see why I should hide the fact that he's stomping on other people's public work. Also, do you really think this is all about frustration? I've been already hit by these issues a number of times in the last 3 years (and lately I've reducing my contributions to places where Maxy works on too, *exactly* to not being hit by that), see also a+b+c+d in [1]. Look, I understand you are seeing me right now as the "complaining guy throwing accusation that random" (which is not), but do you really think I would say this if not because I think there *is* a problem with this? No, I don't think so. But I just don't understand your intentions with these emails. I just don't get it and you didn't answer my questions above: "Be concrete, what do you expect Maxy to do?" I did answer you: at this point, I expect nothing anymore from him. -- Pino Toscano
Re: kwindowsystem_5.13.0-2_amd64.changes ACCEPTED into unstable
Hello Pino, Am Freitag, 21. August 2015, 09:45:59 schrieb Pino Toscano: > > Honestly as far as I see it Maxy agreed to your accusations, apologize, > > has > > giving as reasonable explanation why this happened, > > Please do read the other reply I wrote yesterday, This is not the first > time such things happened, it's a cyclic issue that keeps repeating. >From your wording I gather that you think Maxy will never change his behavior – driven by your reception of the past experiences you had with him. But he just promised he will try hard to. > On my side, I actually don't care about this anymore. which is your free decision to do even though I think you actually do care a lot, cause from what I perceive you put a lot of your emotional energy into your last mail. As I understand things I can never ever sustainably and directly change someone else´s behavior as we are all free will beings. Yet, you can invite and allow for change to happen, model behavior that you think is good and change your way you deal with behaviors of others. >From knowing Maxy a bit from DebConf I fully assume good intentions. As much as I understand that you seem to be frustrated with his past behavior for which he said sorry. So are you willing to set yourself free and forgive him (at least after some time) and probably even assist him in changing? Thank you, -- Martin
Re: kwindowsystem_5.13.0-2_amd64.changes ACCEPTED into unstable
Am Freitag, 21. August 2015, 09.45:59 schrieb Pino Toscano: > On 2015-08-21 09:06, Mario Fux wrote: Morning Pino [snip] > > Honestly as far as I see it Maxy agreed to your accusations, apologize, > > has > > giving as reasonable explanation why this happened, > > Please do read the other reply I wrote yesterday, This is not the first > time such things happened, it's a cyclic issue that keeps repeating. I read it. > > is doing a lot of work, > > really a lot of work for KDE software packaging in Debian, is (as far > > as I see > > it) bringing in new people and helping them and seems to be quite > > patient. > > Please note that "does a lot of work" is not a carte blanche to keep > doing mistakes on other people's work, despite that being pointed out. And if you read my sentence above again this was not my conclusion at all. There was a listing of tiems and "does a lot of work" was just one item and even then I didn't imply this. > >> and given that you're not changed much your modus > >> operandi wrt that, they *will* happen again. A one-shot issue could be > >> understandable (everybody makes mistakes, I'm the first to do them), > >> but > >> the same issue repeating over time (after being told about) is not. > > > > So please be concrete. What do you expect Maxy to do now? Change the > > past? > > Most probably not? Apologize? That he did? Change his way of working? > > As I see > > it he wrote that he will try hard not to do it again. What else do you > > expect? > > Honestly? I don't expect anything from now on. So honestly, what did you want to achieve with these emails then? I can see (but of course might be wrong) two things: - Bringing up this problem (IMHO not in a very constructive way) - Getting your frustration out (if it helped you, ok, but why public then?) > I've been already hit > by these issues a number of times in the last 3 years (and lately > I've reducing my contributions to places where Maxy works on too, > *exactly* to not being hit by that), see also a+b+c+d in [1]. > > Look, I understand you are seeing me right now as the "complaining guy > throwing accusation that random" (which is not), but do you really > think I would say this if not because I think there *is* a problem > with this? No, I don't think so. But I just don't understand your intentions with these emails. I just don't get it and you didn't answer my questions above: "Be concrete, what do you expect Maxy to do?" > Feel free to think whatever you want, that keep apologising > for the same issues happening again and again and again is fine. > On my side, I actually don't care about this anymore. > > [1] https://lists.debian.org/debian-qt-kde/2015/08/msg00462.html griits Mario
Bug#794581: 5.13.0 crashes for me
On Thu, 20 Aug 2015 06:32:08 -0700 Zhitao Li wrote: > Or upgrade breeze package to Sid's version. > Really don't see why breeze is not migrated to testing after 16 days. This worked for me, thanks Zhitao. Yes, I'm not entirely sure why they did this. I mean, I know that they're piecemealing the kf5 transition, but aren't these sorts of grave dependency issues supposed to be anticipated _before_ going to testing?
Re: kwindowsystem_5.13.0-2_amd64.changes ACCEPTED into unstable
On 2015-08-21 09:06, Mario Fux wrote: Am Freitag, 21. August 2015, 07.59:55 schrieb Pino Toscano: Morning Pino In data giovedì 20 agosto 2015 13:52:04, Maximiliano Curia ha scritto: > ¡Hola Pino! > > El 2015-08-20 a las 10:11 +0200, Maximiliano Curia escribió: > > ¡Hola Pino! > > > > El 2015-08-20 a las 00:23 +0200, Pino Toscano escribió: > >> Maxy, many thanks for having - once again - stomped over what me > >> and > >> Felix committed on the packaging git repository. > >> > >> This is my last commit to some packaging repository where you work > >> on as well, since you are clearly unable to work on repositories > >> where other people can work too. > > Let's try this again, now that I'm properly awake. > > I'm sorry that I stomped over your changes. I was doing several things > at the same time, Sune pointed me that we hadn't fixed this issue > that was a critical one, while I was helping someone to start working > with the team, helping helios and doing some more scheduling tasks > for DebConf. > > So I thought I had already updated the git repository, but obviously I > hadn't. > > I'm sorry, this is by no means a disrepect towards the work done by > you, but simply a human mistake caused by trying to do too many > things at the same time. I'll try harder to avoid these situations in > the future. As I said, this is not about "my changes" nor about "what happened this time", but something that happened few times already, even after I told you different times about this; see also my previous email with more details. Dismissing the issue with a "sorry, it happened, don't take it personally" will *not* change the fact that such issues have happened at times in the past, Seriouly? So you want the past changed? I don't see where I'm implying that. Honestly as far as I see it Maxy agreed to your accusations, apologize, has giving as reasonable explanation why this happened, Please do read the other reply I wrote yesterday, This is not the first time such things happened, it's a cyclic issue that keeps repeating. is doing a lot of work, really a lot of work for KDE software packaging in Debian, is (as far as I see it) bringing in new people and helping them and seems to be quite patient. Please note that "does a lot of work" is not a carte blanche to keep doing mistakes on other people's work, despite that being pointed out. and given that you're not changed much your modus operandi wrt that, they *will* happen again. A one-shot issue could be understandable (everybody makes mistakes, I'm the first to do them), but the same issue repeating over time (after being told about) is not. So please be concrete. What do you expect Maxy to do now? Change the past? Most probably not? Apologize? That he did? Change his way of working? As I see it he wrote that he will try hard not to do it again. What else do you expect? Honestly? I don't expect anything from now on. I've been already hit by these issues a number of times in the last 3 years (and lately I've reducing my contributions to places where Maxy works on too, *exactly* to not being hit by that), see also a+b+c+d in [1]. Look, I understand you are seeing me right now as the "complaining guy throwing accusation that random" (which is not), but do you really think I would say this if not because I think there *is* a problem with this? Feel free to think whatever you want, that keep apologising for the same issues happening again and again and again is fine. On my side, I actually don't care about this anymore. [1] https://lists.debian.org/debian-qt-kde/2015/08/msg00462.html -- Pino Toscano
Re: kwindowsystem_5.13.0-2_amd64.changes ACCEPTED into unstable
Am Freitag, 21. August 2015, 07.59:55 schrieb Pino Toscano: Morning Pino > In data giovedì 20 agosto 2015 13:52:04, Maximiliano Curia ha scritto: > > ¡Hola Pino! > > > > El 2015-08-20 a las 10:11 +0200, Maximiliano Curia escribió: > > > ¡Hola Pino! > > > > > > El 2015-08-20 a las 00:23 +0200, Pino Toscano escribió: > > >> Maxy, many thanks for having - once again - stomped over what me > > >> and > > >> Felix committed on the packaging git repository. > > >> > > >> This is my last commit to some packaging repository where you work > > >> on as well, since you are clearly unable to work on repositories > > >> where other people can work too. > > > > Let's try this again, now that I'm properly awake. > > > > I'm sorry that I stomped over your changes. I was doing several things > > at the same time, Sune pointed me that we hadn't fixed this issue > > that was a critical one, while I was helping someone to start working > > with the team, helping helios and doing some more scheduling tasks > > for DebConf. > > > > So I thought I had already updated the git repository, but obviously I > > hadn't. > > > > I'm sorry, this is by no means a disrepect towards the work done by > > you, but simply a human mistake caused by trying to do too many > > things at the same time. I'll try harder to avoid these situations in > > the future. > > As I said, this is not about "my changes" nor about "what happened this > time", but something that happened few times already, even after I told > you different times about this; see also my previous email with more > details. > > Dismissing the issue with a "sorry, it happened, don't take it > personally" will *not* change the fact that such issues have happened at > times in the past, Seriouly? So you want the past changed? Honestly as far as I see it Maxy agreed to your accusations, apologize, has giving as reasonable explanation why this happened, is doing a lot of work, really a lot of work for KDE software packaging in Debian, is (as far as I see it) bringing in new people and helping them and seems to be quite patient. > and given that you're not changed much your modus > operandi wrt that, they *will* happen again. A one-shot issue could be > understandable (everybody makes mistakes, I'm the first to do them), but > the same issue repeating over time (after being told about) is not. So please be concrete. What do you expect Maxy to do now? Change the past? Most probably not? Apologize? That he did? Change his way of working? As I see it he wrote that he will try hard not to do it again. What else do you expect? Best regards Mario
