Bug#972768: marked as done (kissplice ftpfs with python3.9)
Your message dated Mon, 26 Oct 2020 05:18:26 + with message-id and subject line Bug#972768: fixed in kissplice 2.5.3-3 has caused the Debian Bug report #972768, regarding kissplice ftpfs with python3.9 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.) -- 972768: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972768 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kissplice Version: 2.5.3-2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 Not sure if that's python 3.9 specific (python3-defaults from experimental was used). this ends up with a link error: https://people.debian.org/~ginggs/python3.9-default/kissplice_2.5.3-2build1_amd64-2020-10-21T09:34:38Z.build usr/bin/ld: CMakeFiles/ks_kissreadsSplice.dir/tree.c.o:./obj-x86_64-linux-gnu/thirdparty/kissreads/src/./thirdparty/kissreads/include/commons.h:56: multiple definition of `quality'; CMakeFiles/ks_kissreadsSplice.dir/commons.c.o:./obj-x86_64-linux-gnu/thirdparty/kissreads/src/./thirdparty/kissreads/include/commons.h:56: first defined here /usr/bin/ld: CMakeFiles/ks_kissreadsSplice.dir/tree.c.o:./obj-x86_64-linux-gnu/thirdparty/kissreads/src/./thirdparty/kissreads/include/commons.h:55: multiple definition of `silent'; CMakeFiles/ks_kissreadsSplice.dir/commons.c.o:./obj-x86_64-linux-gnu/thirdparty/kissreads/src/./thirdparty/kissreads/include/commons.h:55: first defined here /usr/bin/ld: CMakeFiles/ks_kissreadsSplice.dir/tree.c.o:./obj-x86_64-linux-gnu/thirdparty/kissreads/src/./thirdparty/kissreads/include/commons.h:54: multiple definition of `standard_fasta'; CMakeFiles/ks_kissreadsSplice.dir/commons.c.o:./obj-x86_64-linux-gnu/thirdparty/kissreads/src/./thirdparty/kissreads/include/commons.h:54: first defined here /usr/bin/ld: CMakeFiles/ks_kissreadsSplice.dir/tree.c.o:./obj-x86_64-linux-gnu/thirdparty/kissreads/src/./thirdparty/kissreads/include/commons.h:53: multiple definition of `nuc'; CMakeFiles/ks_kissreadsSplice.dir/commons.c.o:./obj-x86_64-linux-gnu/thirdparty/kissreads/src/./thirdparty/kissreads/include/commons.h:53: first defined here /usr/bin/ldcd /<>/obj-x86_64-linux-gnu/modules && /usr/bin/c++ -I/<>/modules -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wno-unused-result -Wno-parentheses -Wno-error=format-security -std=c++11 -o CMakeFiles/ks_clean_duplicates.dir/LabelledCEdge.cpp.o -c /<>/modules/LabelledCEdge.cpp : CMakeFiles/ks_kissreadsSplice.dir/tree.c.o:./obj-x86_64-linux-gnu/thirdparty/kissreads/src/./thirdparty/kissreads/include/commons.h:52: multiple definition of `comp'; CMakeFiles/ks_kissreadsSplice.dir/commons.c.o:./obj-x86_64-linux-gnu/thirdparty/kissreads/src/./thirdparty/kissreads/include/commons.h:52: first defined here collect2: error: ld returned 1 exit status make[3]: *** [thirdparty/kissreads/src/CMakeFiles/ks_kissreadsSplice.dir/build.make:257: lib/kissplice/ks_kissreadsSplice] Error 1 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' --- End Message --- --- Begin Message --- Source: kissplice Source-Version: 2.5.3-3 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of kissplice, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated kissplice 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: SHA512 Format: 1.8 Date: Mon, 26 Oct 2020 04:00:37 +0530 Source: kissplice Architecture: source Version: 2.5.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 972768 Changes: kissplice (2.5.3-3) unstable; urgency=medium . * Team Upload. * Fix gcc-10 FTBFS (Closes: #972768) Checksums-Sha1: fbc142022b1ba9f118ac0f44fa50bf26cc9f5c9e 2243 kissplice_2.5.3-3.dsc e9b893dd5484d63408d78392e608ad2d114b2eb3 13528 kissplice_2.5.3-3.debian.tar.xz 31d0aaa181029813fb53ef4667ef3c618b2ec985 7418 kissplice_2.5.3-3_amd64.buildinfo Checksums-Sha256: 2d64a36266164fb91f88969685c5bfe0b757968822c17187dabe11de7b968f66 2243
Bug#972775: marked as done (ros-rospack ftbfs)
Your message dated Mon, 26 Oct 2020 05:03:26 + with message-id and subject line Bug#972618: fixed in googletest 1.10.0.20201025-1 has caused the Debian Bug report #972618, regarding ros-rospack ftbfs 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.) -- 972618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ros-rospack Version: 2.6.2-1 Severity: serious Tags: sid bullseye ftbfs ros-rospack ftbfs with python3.9 (python3-defaults from experimental), not yet convinced if that's related to python3.9, looks more like a googletest issue. https://people.debian.org/~ginggs/python3.9-default/ros-rospack_2.6.2-2build1_amd64-2020-10-22T14:07:50Z.build [...] CMake Warning at CMakeLists.txt:43 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- The CXX compiler identification is GNU 10.2.0 -- The C compiler identification is GNU 10.2.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done CMake Warning at /usr/src/googletest/googletest/CMakeLists.txt:54 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- Found PythonInterp: /usr/bin/python3.9 (found version "3.9") -- Looking for pthread.h -- Looking for pthread.h - found -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:129 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:132 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:103 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:106 (set_target_properties): set_target_properties called with incorrect number of arguments. -- Configuring incomplete, errors occurred! See also "/<>/obj-x86_64-linux-gnu/core/mk/gmock/CMakeFiles/CMakeOutput.log". See also "/<>/obj-x86_64-linux-gnu/core/mk/gmock/CMakeFiles/CMakeError.log". --- End Message --- --- Begin Message --- Source: googletest Source-Version: 1.10.0.20201025-1 Done: s...@debian.org (Steve M. Robbins) We believe that the bug you reported is fixed in the latest version of googletest, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated googletest 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: Sun, 25 Oct 2020 23:32:56 -0500 Source: googletest Architecture: source Version: 1.10.0.20201025-1 Distribution: unstable Urgency: medium Maintainer: Steve M. Robbins Changed-By: Steve M. Robbins Closes: 972618 972774 972775 Changes: googletest (1.10.0.20201025-1) unstable; urgency=medium . [ Steve Robbins ] * [9ce1377] New upstream version 1.10.0.20201025 * [2e546ca] New 0005-Add-GoogleTest-version-to-each-sub-project-to-allow-.patch to allow builds using /usr/src/googletest/googletest. The recommended method is to build using /usr/src/googletest, however. Closes: #972618, #972774, #972775. Checksums-Sha1: 1f7626afe447a05612942f45c160621e0f75c57f 2255 googletest_1.10.0.20201025-1.dsc 640513405524addd979073eb0e8cd62017f655e4 872653 googletest_1.10.0.20201025.orig.tar.gz 8f3aeb1f08bb513b5aaef5d550e061aad3e97f46 10700
Bug#972774: marked as done (ros-ros ftbfs)
Your message dated Mon, 26 Oct 2020 05:03:26 + with message-id and subject line Bug#972774: fixed in googletest 1.10.0.20201025-1 has caused the Debian Bug report #972774, regarding ros-ros ftbfs 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.) -- 972774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ros-ros Version: 1.15.7-1 Severity: serious Tags: sid bullseye ftbfs ros-ros ftbfs with python3.9 (python3-defaults from experimental), not yet convinced if that's related to python3.9, looks more like a googletest issue. https://people.debian.org/~ginggs/python3.9-default/ros-ros_1.15.7-1build1_amd64-2020-10-22T14:06:27Z.build [...] CMake Warning at CMakeLists.txt:43 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- The CXX compiler identification is GNU 10.2.0 -- The C compiler identification is GNU 10.2.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done CMake Warning at /usr/src/googletest/googletest/CMakeLists.txt:54 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- Found PythonInterp: /usr/bin/python3.9 (found version "3.9") -- Looking for pthread.h -- Looking for pthread.h - found -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:129 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:132 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:103 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:106 (set_target_properties): set_target_properties called with incorrect number of arguments. -- Configuring incomplete, errors occurred! See also "/<>/obj-x86_64-linux-gnu/core/mk/gmock/CMakeFiles/CMakeOutput.log". See also "/<>/obj-x86_64-linux-gnu/core/mk/gmock/CMakeFiles/CMakeError.log". --- End Message --- --- Begin Message --- Source: googletest Source-Version: 1.10.0.20201025-1 Done: s...@debian.org (Steve M. Robbins) We believe that the bug you reported is fixed in the latest version of googletest, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated googletest 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: Sun, 25 Oct 2020 23:32:56 -0500 Source: googletest Architecture: source Version: 1.10.0.20201025-1 Distribution: unstable Urgency: medium Maintainer: Steve M. Robbins Changed-By: Steve M. Robbins Closes: 972618 972774 972775 Changes: googletest (1.10.0.20201025-1) unstable; urgency=medium . [ Steve Robbins ] * [9ce1377] New upstream version 1.10.0.20201025 * [2e546ca] New 0005-Add-GoogleTest-version-to-each-sub-project-to-allow-.patch to allow builds using /usr/src/googletest/googletest. The recommended method is to build using /usr/src/googletest, however. Closes: #972618, #972774, #972775. Checksums-Sha1: 1f7626afe447a05612942f45c160621e0f75c57f 2255 googletest_1.10.0.20201025-1.dsc 640513405524addd979073eb0e8cd62017f655e4 872653 googletest_1.10.0.20201025.orig.tar.gz 8f3aeb1f08bb513b5aaef5d550e061aad3e97f46 10700 googletest_1.10.0.20201025-1.debian.tar.xz
Bug#972618: marked as done (googletest: Breaks apt build)
Your message dated Mon, 26 Oct 2020 05:03:26 + with message-id and subject line Bug#972774: fixed in googletest 1.10.0.20201025-1 has caused the Debian Bug report #972774, regarding googletest: Breaks apt build 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.) -- 972774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: googletest Version: 1.10.0.20201018-1 Severity: serious Control: affects -1 apt The apt build, which has been working fine with the previous version, now fails to build: cd /builds/apt-team/apt/build/test/libapt/gtest/src/gtest-build && /usr/bin/cmake -GNinja /usr/src/googletest/googletest && /usr/bin/cmake -E touch /builds/apt-team/apt/build/test/libapt/gtest/src/gtest-stamp/gtest-configure CMake Warning at CMakeLists.txt:54 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- The CXX compiler identification is GNU 10.2.0 -- The C compiler identification is GNU 10.2.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Found PythonInterp: /usr/bin/python3.8 (found version "3.8.6") -- Looking for pthread.h -- Looking for pthread.h - found -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE CMake Error at CMakeLists.txt:129 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:132 (set_target_properties): set_target_properties called with incorrect number of arguments. -- Configuring incomplete, errors occurred! See also "/builds/apt-team/apt/build/test/libapt/g Are we using googletest wrong? I don't know, but it's gotta stop breaking our build every few uploads. -- System Information: Debian Release: bullseye/sid APT prefers groovy APT policy: (500, 'groovy'), (500, 'focal-updates'), (500, 'focal-security') Architecture: amd64 (x86_64) Kernel: Linux 5.9.1-050901-generic (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en --- End Message --- --- Begin Message --- Source: googletest Source-Version: 1.10.0.20201025-1 Done: s...@debian.org (Steve M. Robbins) We believe that the bug you reported is fixed in the latest version of googletest, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated googletest 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: Sun, 25 Oct 2020 23:32:56 -0500 Source: googletest Architecture: source Version: 1.10.0.20201025-1 Distribution: unstable Urgency: medium Maintainer: Steve M. Robbins Changed-By: Steve M. Robbins Closes: 972618 972774 972775 Changes: googletest (1.10.0.20201025-1) unstable; urgency=medium . [ Steve Robbins ] * [9ce1377] New upstream version 1.10.0.20201025 * [2e546ca] New 0005-Add-GoogleTest-version-to-each-sub-project-to-allow-.patch to allow builds using /usr/src/googletest/googletest. The recommended method is to
Bug#972775: marked as done (ros-rospack ftbfs)
Your message dated Mon, 26 Oct 2020 05:03:26 + with message-id and subject line Bug#972775: fixed in googletest 1.10.0.20201025-1 has caused the Debian Bug report #972775, regarding ros-rospack ftbfs 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.) -- 972775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ros-rospack Version: 2.6.2-1 Severity: serious Tags: sid bullseye ftbfs ros-rospack ftbfs with python3.9 (python3-defaults from experimental), not yet convinced if that's related to python3.9, looks more like a googletest issue. https://people.debian.org/~ginggs/python3.9-default/ros-rospack_2.6.2-2build1_amd64-2020-10-22T14:07:50Z.build [...] CMake Warning at CMakeLists.txt:43 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- The CXX compiler identification is GNU 10.2.0 -- The C compiler identification is GNU 10.2.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done CMake Warning at /usr/src/googletest/googletest/CMakeLists.txt:54 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- Found PythonInterp: /usr/bin/python3.9 (found version "3.9") -- Looking for pthread.h -- Looking for pthread.h - found -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:129 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:132 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:103 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:106 (set_target_properties): set_target_properties called with incorrect number of arguments. -- Configuring incomplete, errors occurred! See also "/<>/obj-x86_64-linux-gnu/core/mk/gmock/CMakeFiles/CMakeOutput.log". See also "/<>/obj-x86_64-linux-gnu/core/mk/gmock/CMakeFiles/CMakeError.log". --- End Message --- --- Begin Message --- Source: googletest Source-Version: 1.10.0.20201025-1 Done: s...@debian.org (Steve M. Robbins) We believe that the bug you reported is fixed in the latest version of googletest, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated googletest 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: Sun, 25 Oct 2020 23:32:56 -0500 Source: googletest Architecture: source Version: 1.10.0.20201025-1 Distribution: unstable Urgency: medium Maintainer: Steve M. Robbins Changed-By: Steve M. Robbins Closes: 972618 972774 972775 Changes: googletest (1.10.0.20201025-1) unstable; urgency=medium . [ Steve Robbins ] * [9ce1377] New upstream version 1.10.0.20201025 * [2e546ca] New 0005-Add-GoogleTest-version-to-each-sub-project-to-allow-.patch to allow builds using /usr/src/googletest/googletest. The recommended method is to build using /usr/src/googletest, however. Closes: #972618, #972774, #972775. Checksums-Sha1: 1f7626afe447a05612942f45c160621e0f75c57f 2255 googletest_1.10.0.20201025-1.dsc 640513405524addd979073eb0e8cd62017f655e4 872653 googletest_1.10.0.20201025.orig.tar.gz 8f3aeb1f08bb513b5aaef5d550e061aad3e97f46 10700
Bug#972618: marked as done (googletest: Breaks apt build)
Your message dated Mon, 26 Oct 2020 05:03:26 + with message-id and subject line Bug#972775: fixed in googletest 1.10.0.20201025-1 has caused the Debian Bug report #972775, regarding googletest: Breaks apt build 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.) -- 972775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: googletest Version: 1.10.0.20201018-1 Severity: serious Control: affects -1 apt The apt build, which has been working fine with the previous version, now fails to build: cd /builds/apt-team/apt/build/test/libapt/gtest/src/gtest-build && /usr/bin/cmake -GNinja /usr/src/googletest/googletest && /usr/bin/cmake -E touch /builds/apt-team/apt/build/test/libapt/gtest/src/gtest-stamp/gtest-configure CMake Warning at CMakeLists.txt:54 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- The CXX compiler identification is GNU 10.2.0 -- The C compiler identification is GNU 10.2.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Found PythonInterp: /usr/bin/python3.8 (found version "3.8.6") -- Looking for pthread.h -- Looking for pthread.h - found -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE CMake Error at CMakeLists.txt:129 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:132 (set_target_properties): set_target_properties called with incorrect number of arguments. -- Configuring incomplete, errors occurred! See also "/builds/apt-team/apt/build/test/libapt/g Are we using googletest wrong? I don't know, but it's gotta stop breaking our build every few uploads. -- System Information: Debian Release: bullseye/sid APT prefers groovy APT policy: (500, 'groovy'), (500, 'focal-updates'), (500, 'focal-security') Architecture: amd64 (x86_64) Kernel: Linux 5.9.1-050901-generic (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en --- End Message --- --- Begin Message --- Source: googletest Source-Version: 1.10.0.20201025-1 Done: s...@debian.org (Steve M. Robbins) We believe that the bug you reported is fixed in the latest version of googletest, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated googletest 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: Sun, 25 Oct 2020 23:32:56 -0500 Source: googletest Architecture: source Version: 1.10.0.20201025-1 Distribution: unstable Urgency: medium Maintainer: Steve M. Robbins Changed-By: Steve M. Robbins Closes: 972618 972774 972775 Changes: googletest (1.10.0.20201025-1) unstable; urgency=medium . [ Steve Robbins ] * [9ce1377] New upstream version 1.10.0.20201025 * [2e546ca] New 0005-Add-GoogleTest-version-to-each-sub-project-to-allow-.patch to allow builds using /usr/src/googletest/googletest. The recommended method is to
Bug#972775: marked as done (ros-rospack ftbfs)
Your message dated Mon, 26 Oct 2020 05:03:26 + with message-id and subject line Bug#972774: fixed in googletest 1.10.0.20201025-1 has caused the Debian Bug report #972774, regarding ros-rospack ftbfs 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.) -- 972774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972774 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ros-rospack Version: 2.6.2-1 Severity: serious Tags: sid bullseye ftbfs ros-rospack ftbfs with python3.9 (python3-defaults from experimental), not yet convinced if that's related to python3.9, looks more like a googletest issue. https://people.debian.org/~ginggs/python3.9-default/ros-rospack_2.6.2-2build1_amd64-2020-10-22T14:07:50Z.build [...] CMake Warning at CMakeLists.txt:43 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- The CXX compiler identification is GNU 10.2.0 -- The C compiler identification is GNU 10.2.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done CMake Warning at /usr/src/googletest/googletest/CMakeLists.txt:54 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- Found PythonInterp: /usr/bin/python3.9 (found version "3.9") -- Looking for pthread.h -- Looking for pthread.h - found -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:129 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:132 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:103 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:106 (set_target_properties): set_target_properties called with incorrect number of arguments. -- Configuring incomplete, errors occurred! See also "/<>/obj-x86_64-linux-gnu/core/mk/gmock/CMakeFiles/CMakeOutput.log". See also "/<>/obj-x86_64-linux-gnu/core/mk/gmock/CMakeFiles/CMakeError.log". --- End Message --- --- Begin Message --- Source: googletest Source-Version: 1.10.0.20201025-1 Done: s...@debian.org (Steve M. Robbins) We believe that the bug you reported is fixed in the latest version of googletest, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated googletest 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: Sun, 25 Oct 2020 23:32:56 -0500 Source: googletest Architecture: source Version: 1.10.0.20201025-1 Distribution: unstable Urgency: medium Maintainer: Steve M. Robbins Changed-By: Steve M. Robbins Closes: 972618 972774 972775 Changes: googletest (1.10.0.20201025-1) unstable; urgency=medium . [ Steve Robbins ] * [9ce1377] New upstream version 1.10.0.20201025 * [2e546ca] New 0005-Add-GoogleTest-version-to-each-sub-project-to-allow-.patch to allow builds using /usr/src/googletest/googletest. The recommended method is to build using /usr/src/googletest, however. Closes: #972618, #972774, #972775. Checksums-Sha1: 1f7626afe447a05612942f45c160621e0f75c57f 2255 googletest_1.10.0.20201025-1.dsc 640513405524addd979073eb0e8cd62017f655e4 872653 googletest_1.10.0.20201025.orig.tar.gz 8f3aeb1f08bb513b5aaef5d550e061aad3e97f46 10700
Bug#972774: marked as done (ros-ros ftbfs)
Your message dated Mon, 26 Oct 2020 05:03:26 + with message-id and subject line Bug#972775: fixed in googletest 1.10.0.20201025-1 has caused the Debian Bug report #972775, regarding ros-ros ftbfs 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.) -- 972775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ros-ros Version: 1.15.7-1 Severity: serious Tags: sid bullseye ftbfs ros-ros ftbfs with python3.9 (python3-defaults from experimental), not yet convinced if that's related to python3.9, looks more like a googletest issue. https://people.debian.org/~ginggs/python3.9-default/ros-ros_1.15.7-1build1_amd64-2020-10-22T14:06:27Z.build [...] CMake Warning at CMakeLists.txt:43 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- The CXX compiler identification is GNU 10.2.0 -- The C compiler identification is GNU 10.2.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done CMake Warning at /usr/src/googletest/googletest/CMakeLists.txt:54 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- Found PythonInterp: /usr/bin/python3.9 (found version "3.9") -- Looking for pthread.h -- Looking for pthread.h - found -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:129 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:132 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:103 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:106 (set_target_properties): set_target_properties called with incorrect number of arguments. -- Configuring incomplete, errors occurred! See also "/<>/obj-x86_64-linux-gnu/core/mk/gmock/CMakeFiles/CMakeOutput.log". See also "/<>/obj-x86_64-linux-gnu/core/mk/gmock/CMakeFiles/CMakeError.log". --- End Message --- --- Begin Message --- Source: googletest Source-Version: 1.10.0.20201025-1 Done: s...@debian.org (Steve M. Robbins) We believe that the bug you reported is fixed in the latest version of googletest, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated googletest 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: Sun, 25 Oct 2020 23:32:56 -0500 Source: googletest Architecture: source Version: 1.10.0.20201025-1 Distribution: unstable Urgency: medium Maintainer: Steve M. Robbins Changed-By: Steve M. Robbins Closes: 972618 972774 972775 Changes: googletest (1.10.0.20201025-1) unstable; urgency=medium . [ Steve Robbins ] * [9ce1377] New upstream version 1.10.0.20201025 * [2e546ca] New 0005-Add-GoogleTest-version-to-each-sub-project-to-allow-.patch to allow builds using /usr/src/googletest/googletest. The recommended method is to build using /usr/src/googletest, however. Closes: #972618, #972774, #972775. Checksums-Sha1: 1f7626afe447a05612942f45c160621e0f75c57f 2255 googletest_1.10.0.20201025-1.dsc 640513405524addd979073eb0e8cd62017f655e4 872653 googletest_1.10.0.20201025.orig.tar.gz 8f3aeb1f08bb513b5aaef5d550e061aad3e97f46 10700 googletest_1.10.0.20201025-1.debian.tar.xz
Bug#972774: marked as done (ros-ros ftbfs)
Your message dated Mon, 26 Oct 2020 05:03:26 + with message-id and subject line Bug#972618: fixed in googletest 1.10.0.20201025-1 has caused the Debian Bug report #972618, regarding ros-ros ftbfs 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.) -- 972618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ros-ros Version: 1.15.7-1 Severity: serious Tags: sid bullseye ftbfs ros-ros ftbfs with python3.9 (python3-defaults from experimental), not yet convinced if that's related to python3.9, looks more like a googletest issue. https://people.debian.org/~ginggs/python3.9-default/ros-ros_1.15.7-1build1_amd64-2020-10-22T14:06:27Z.build [...] CMake Warning at CMakeLists.txt:43 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- The CXX compiler identification is GNU 10.2.0 -- The C compiler identification is GNU 10.2.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done CMake Warning at /usr/src/googletest/googletest/CMakeLists.txt:54 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- Found PythonInterp: /usr/bin/python3.9 (found version "3.9") -- Looking for pthread.h -- Looking for pthread.h - found -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:129 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at /usr/src/googletest/googletest/CMakeLists.txt:132 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:103 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:106 (set_target_properties): set_target_properties called with incorrect number of arguments. -- Configuring incomplete, errors occurred! See also "/<>/obj-x86_64-linux-gnu/core/mk/gmock/CMakeFiles/CMakeOutput.log". See also "/<>/obj-x86_64-linux-gnu/core/mk/gmock/CMakeFiles/CMakeError.log". --- End Message --- --- Begin Message --- Source: googletest Source-Version: 1.10.0.20201025-1 Done: s...@debian.org (Steve M. Robbins) We believe that the bug you reported is fixed in the latest version of googletest, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated googletest 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: Sun, 25 Oct 2020 23:32:56 -0500 Source: googletest Architecture: source Version: 1.10.0.20201025-1 Distribution: unstable Urgency: medium Maintainer: Steve M. Robbins Changed-By: Steve M. Robbins Closes: 972618 972774 972775 Changes: googletest (1.10.0.20201025-1) unstable; urgency=medium . [ Steve Robbins ] * [9ce1377] New upstream version 1.10.0.20201025 * [2e546ca] New 0005-Add-GoogleTest-version-to-each-sub-project-to-allow-.patch to allow builds using /usr/src/googletest/googletest. The recommended method is to build using /usr/src/googletest, however. Closes: #972618, #972774, #972775. Checksums-Sha1: 1f7626afe447a05612942f45c160621e0f75c57f 2255 googletest_1.10.0.20201025-1.dsc 640513405524addd979073eb0e8cd62017f655e4 872653 googletest_1.10.0.20201025.orig.tar.gz 8f3aeb1f08bb513b5aaef5d550e061aad3e97f46 10700 googletest_1.10.0.20201025-1.debian.tar.xz
Bug#972618: marked as done (googletest: Breaks apt build)
Your message dated Mon, 26 Oct 2020 05:03:26 + with message-id and subject line Bug#972618: fixed in googletest 1.10.0.20201025-1 has caused the Debian Bug report #972618, regarding googletest: Breaks apt build 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.) -- 972618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972618 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: googletest Version: 1.10.0.20201018-1 Severity: serious Control: affects -1 apt The apt build, which has been working fine with the previous version, now fails to build: cd /builds/apt-team/apt/build/test/libapt/gtest/src/gtest-build && /usr/bin/cmake -GNinja /usr/src/googletest/googletest && /usr/bin/cmake -E touch /builds/apt-team/apt/build/test/libapt/gtest/src/gtest-stamp/gtest-configure CMake Warning at CMakeLists.txt:54 (project): VERSION keyword not followed by a value or was followed by a value that expanded to nothing. -- The CXX compiler identification is GNU 10.2.0 -- The C compiler identification is GNU 10.2.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working C compiler: /usr/bin/cc - skipped -- Detecting C compile features -- Detecting C compile features - done -- Found PythonInterp: /usr/bin/python3.8 (found version "3.8.6") -- Looking for pthread.h -- Looking for pthread.h - found -- Performing Test CMAKE_HAVE_LIBC_PTHREAD -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE CMake Error at CMakeLists.txt:129 (set_target_properties): set_target_properties called with incorrect number of arguments. CMake Error at CMakeLists.txt:132 (set_target_properties): set_target_properties called with incorrect number of arguments. -- Configuring incomplete, errors occurred! See also "/builds/apt-team/apt/build/test/libapt/g Are we using googletest wrong? I don't know, but it's gotta stop breaking our build every few uploads. -- System Information: Debian Release: bullseye/sid APT prefers groovy APT policy: (500, 'groovy'), (500, 'focal-updates'), (500, 'focal-security') Architecture: amd64 (x86_64) Kernel: Linux 5.9.1-050901-generic (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to C.UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en --- End Message --- --- Begin Message --- Source: googletest Source-Version: 1.10.0.20201025-1 Done: s...@debian.org (Steve M. Robbins) We believe that the bug you reported is fixed in the latest version of googletest, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Steve M. Robbins (supplier of updated googletest 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: Sun, 25 Oct 2020 23:32:56 -0500 Source: googletest Architecture: source Version: 1.10.0.20201025-1 Distribution: unstable Urgency: medium Maintainer: Steve M. Robbins Changed-By: Steve M. Robbins Closes: 972618 972774 972775 Changes: googletest (1.10.0.20201025-1) unstable; urgency=medium . [ Steve Robbins ] * [9ce1377] New upstream version 1.10.0.20201025 * [2e546ca] New 0005-Add-GoogleTest-version-to-each-sub-project-to-allow-.patch to allow builds using /usr/src/googletest/googletest. The recommended method is to
Processed: bug 972618 is forwarded to https://github.com/google/googletest/issues/2950
Processing commands for cont...@bugs.debian.org: > forwarded 972618 https://github.com/google/googletest/issues/2950 Bug #972618 [googletest] googletest: Breaks apt build Bug #972774 [googletest] ros-ros ftbfs Bug #972775 [googletest] ros-rospack ftbfs Set Bug forwarded-to-address to 'https://github.com/google/googletest/issues/2950'. Set Bug forwarded-to-address to 'https://github.com/google/googletest/issues/2950'. Set Bug forwarded-to-address to 'https://github.com/google/googletest/issues/2950'. > thanks Stopping processing here. Please contact me if you need assistance. -- 972618: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972618 972774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972774 972775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972775 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 885043
Processing commands for cont...@bugs.debian.org: > close 885043 0.7.11+git20200916.46e7ade-2 Bug #885043 [src:gtetrinet] gtetrinet: Don't depend on obsolete GNOME libraries Marked as fixed in versions gtetrinet/0.7.11+git20200916.46e7ade-2. Bug #885043 [src:gtetrinet] gtetrinet: Don't depend on obsolete GNOME libraries Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 885043: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885043 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 742111
Processing commands for cont...@bugs.debian.org: > close 742111 1.6.2-1 Bug #742111 [mp3gain] mp3gain: ancient and probably insecure embedded code copy: mpglib Marked as fixed in versions mp3gain/1.6.2-1. Bug #742111 [mp3gain] mp3gain: ancient and probably insecure embedded code copy: mpglib Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 742111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 749259
Processing commands for cont...@bugs.debian.org: > close 749259 2.20+ds-1 Bug #749259 [rednotebook] rednotebook: depends on python-webkit which is deprecated Marked as fixed in versions rednotebook/2.20+ds-1. Bug #749259 [rednotebook] rednotebook: depends on python-webkit which is deprecated Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 749259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 917494
Processing commands for cont...@bugs.debian.org: > close 917494 0.0~git20200412.3577fbd-2 Bug #917494 [src:golang-github-jaytaylor-html2text] golang-github-jaytaylor-html2text: FTBFS (failing tests) Marked as fixed in versions golang-github-jaytaylor-html2text/0.0~git20200412.3577fbd-2. Bug #917494 [src:golang-github-jaytaylor-html2text] golang-github-jaytaylor-html2text: FTBFS (failing tests) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 917494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917494 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: closing 899686
Processing commands for cont...@bugs.debian.org: > close 899686 0.3.10-2 Bug #899686 [src:ruby-timeliness] ruby-timeliness: Invalid maintainer address pkg-azure-t...@lists.alioth.debian.org Marked as fixed in versions ruby-timeliness/0.3.10-2. Bug #899686 [src:ruby-timeliness] ruby-timeliness: Invalid maintainer address pkg-azure-t...@lists.alioth.debian.org Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 899686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899686 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchiving 899686, reopening 899686
Processing commands for cont...@bugs.debian.org:
> # src:ruby-timeliness was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 899686
Bug #899686 {Done: Debian FTP Masters }
[src:ruby-timeliness] ruby-timeliness: Invalid maintainer address
pkg-azure-t...@lists.alioth.debian.org
Unarchived Bug 899686
> reopen 899686
Bug #899686 {Done: Debian FTP Masters }
[src:ruby-timeliness] ruby-timeliness: Invalid maintainer address
pkg-azure-t...@lists.alioth.debian.org
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.3.8-1+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
899686: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899686
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unarchiving 917494, reopening 917494
Processing commands for cont...@bugs.debian.org:
> # src:golang-github-jaytaylor-html2text was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 917494
Bug #917494 {Done: Debian FTP Masters }
[src:golang-github-jaytaylor-html2text] golang-github-jaytaylor-html2text:
FTBFS (failing tests)
Unarchived Bug 917494
> reopen 917494
Bug #917494 {Done: Debian FTP Masters }
[src:golang-github-jaytaylor-html2text] golang-github-jaytaylor-html2text:
FTBFS (failing tests)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.0~git20170918.0.0ee88d3-4+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
917494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unarchiving 749259, reopening 749259, unarchiving 700765, reopening 700765, unarchiving 788797 ...
Processing commands for cont...@bugs.debian.org:
> # src:rednotebook was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 749259
Bug #749259 {Done: Debian FTP Masters }
[rednotebook] rednotebook: depends on python-webkit which is deprecated
Unarchived Bug 749259
> reopen 749259
Bug #749259 {Done: Debian FTP Masters }
[rednotebook] rednotebook: depends on python-webkit which is deprecated
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.10.1-1+rm.
> unarchive 700765
Bug #700765 {Done: Debian FTP Masters }
[rednotebook] rednotebook: Crashes when holding down ctrl-pgup or ctrl-pgdn to
move through dates
Unarchived Bug 700765
> reopen 700765
Bug #700765 {Done: Debian FTP Masters }
[rednotebook] rednotebook: Crashes when holding down ctrl-pgup or ctrl-pgdn to
move through dates
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.10.1-1+rm.
> unarchive 788797
Bug #788797 {Done: Debian FTP Masters }
[rednotebook] rednotebook: crashing at startup with segmentation fault
Unarchived Bug 788797
> reopen 788797
Bug #788797 {Done: Debian FTP Masters }
[rednotebook] rednotebook: crashing at startup with segmentation fault
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.10.1-1+rm.
> unarchive 555415
Bug #555415 {Done: Debian FTP Masters }
[rednotebook] rednotebook: Embedded copy of msgfmt.py script
Unarchived Bug 555415
> reopen 555415
Bug #555415 {Done: Debian FTP Masters }
[rednotebook] rednotebook: Embedded copy of msgfmt.py script
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.10.1-1+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
555415: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555415
700765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700765
749259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749259
788797: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788797
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unarchiving 742111, reopening 742111, unarchiving 703656, reopening 703656, unarchiving 761834 ...
Processing commands for cont...@bugs.debian.org:
> # src:mp3gain was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 742111
Bug #742111 {Done: Debian FTP Masters }
[mp3gain] mp3gain: ancient and probably insecure embedded code copy: mpglib
Unarchived Bug 742111
> reopen 742111
Bug #742111 {Done: Debian FTP Masters }
[mp3gain] mp3gain: ancient and probably insecure embedded code copy: mpglib
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.2-r2-6+rm.
> unarchive 703656
Bug #703656 {Done: Debian FTP Masters }
[mp3gain] mp3gain: Segfault in III_dequantize_sample
Unarchived Bug 703656
> reopen 703656
Bug #703656 {Done: Debian FTP Masters }
[mp3gain] mp3gain: Segfault in III_dequantize_sample
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.2-r2-6+rm.
> unarchive 761834
Bug #761834 {Done: Debian FTP Masters }
[mp3gain] Updating the mp3gain Uploaders list
Unarchived Bug 761834
> reopen 761834
Bug #761834 {Done: Debian FTP Masters }
[mp3gain] Updating the mp3gain Uploaders list
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.2-r2-6+rm.
> unarchive 467146
Bug #467146 {Done: Debian FTP Masters }
[mp3gain] Provide a wrapper script to apply mp3gain recursively
Unarchived Bug 467146
> reopen 467146
Bug #467146 {Done: Debian FTP Masters }
[mp3gain] Provide a wrapper script to apply mp3gain recursively
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.2-r2-6+rm.
> unarchive 731503
Bug #731503 {Done: Debian FTP Masters }
[mp3gain] mp3gain: Please Add Support for Videos
Unarchived Bug 731503
> reopen 731503
Bug #731503 {Done: Debian FTP Masters }
[mp3gain] mp3gain: Please Add Support for Videos
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.2-r2-6+rm.
> unarchive 731504
Bug #731504 {Done: Debian FTP Masters }
[mp3gain] mp3gain: Please Add Normalization for a Single Track
Unarchived Bug 731504
> reopen 731504
Bug #731504 {Done: Debian FTP Masters }
[mp3gain] mp3gain: Please Add Normalization for a Single Track
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 1.5.2-r2-6+rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
467146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=467146
703656: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=703656
731503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731503
731504: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731504
742111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742111
761834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761834
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: unarchiving 885043, reopening 885043, unarchiving 653443, reopening 653443, unarchiving 209015 ...
Processing commands for cont...@bugs.debian.org:
> # src:gtetrinet was reintroduced:
> https://lists.debian.org/msgid-search/546c2c3d77eaef6dc2b26c7ed7663f16df847bda.ca...@debian.org
> unarchive 885043
Bug #885043 {Done: Debian FTP Masters }
[src:gtetrinet] gtetrinet: Don't depend on obsolete GNOME libraries
Unarchived Bug 885043
> reopen 885043
Bug #885043 {Done: Debian FTP Masters }
[src:gtetrinet] gtetrinet: Don't depend on obsolete GNOME libraries
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.7.11-3+rm.
> unarchive 653443
Bug #653443 {Done: Debian FTP Masters }
[gtetrinet] Hardening options incomplete
Unarchived Bug 653443
> reopen 653443
Bug #653443 {Done: Debian FTP Masters }
[gtetrinet] Hardening options incomplete
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.7.11-3+rm.
> unarchive 209015
Bug #209015 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: gtetrinet can't quit if a connection was aborted
Unarchived Bug 209015
> reopen 209015
Bug #209015 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: gtetrinet can't quit if a connection was aborted
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.7.11-3+rm.
> unarchive 255647
Bug #255647 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: Doesn't renter right with large fonts
Unarchived Bug 255647
> reopen 255647
Bug #255647 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: Doesn't renter right with large fonts
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.7.11-3+rm.
> unarchive 273723
Bug #273723 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: unhelpful connection establishing error
Unarchived Bug 273723
> reopen 273723
Bug #273723 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: unhelpful connection establishing error
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.7.11-3+rm.
> unarchive 361699
Bug #361699 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: crashed at game end
Unarchived Bug 361699
> reopen 361699
Bug #361699 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: crashed at game end
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.7.11-3+rm.
> unarchive 343973
Bug #343973 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: can easily disassociate the "connect, disconnect" tab
Unarchived Bug 343973
> reopen 343973
Bug #343973 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: can easily disassociate the "connect, disconnect" tab
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.7.11-3+rm.
> unarchive 666034
Bug #666034 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: should be in Section: games
Unarchived Bug 666034
> reopen 666034
Bug #666034 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: should be in Section: games
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.7.11-3+rm.
> unarchive 175620
Bug #175620 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet lost it's config
Unarchived Bug 175620
> reopen 175620
Bug #175620 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet lost it's config
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.7.11-3+rm.
> unarchive 291844
Bug #291844 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: have key for "send special to self"
Unarchived Bug 291844
> reopen 291844
Bug #291844 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: have key for "send special to self"
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 0.7.11-3+rm.
> unarchive 358209
Bug #358209 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: 't'ext isn't apable
Unarchived Bug 358209
> reopen 358209
Bug #358209 {Done: Debian FTP Masters }
[gtetrinet] gtetrinet: 't'ext
Bug#972166: marked as done (odin: Depends on package qt5-default which is about to be removed)
Your message dated Mon, 26 Oct 2020 00:18:58 + with message-id and subject line Bug#972166: fixed in odin 2.0.4-0.2 has caused the Debian Bug report #972166, regarding odin: Depends on package qt5-default which is about to be removed 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.) -- 972166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: odin Version: 2.0.4-0.1 Severity: important User: debian-qt-...@lists.debian.org Usertags: qt5-default-removal X-Debbugs-Cc: debian-qt-...@lists.debian.org Hi! Your package currently depends upon qt5-default. This package was not intended to be used neither as a build dpeendency nor as a package dependency. Moreover it has created more issues that it solved, so now that Qt 4 is gone and Qt 5 is the default we are retiring it. Anyways you can always check https://qt-kde-team.pages.debian.net/packagingqtbasedstuff.html for more information. Feel free to ping me if you need help. Kinds regards, Lisandro. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64, armhf Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: odin Source-Version: 2.0.4-0.2 Done: =?utf-8?q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?= We believe that the bug you reported is fixed in the latest version of odin, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lisandro Damián Nicanor Pérez Meyer (supplier of updated odin 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: Sun, 25 Oct 2020 14:58:22 -0300 Source: odin Architecture: source Version: 2.0.4-0.2 Distribution: unstable Urgency: medium Maintainer: NeuroDebian Team Changed-By: Lisandro Damián Nicanor Pérez Meyer Closes: 972166 Changes: odin (2.0.4-0.2) unstable; urgency=medium . * Non-maintainer upload. * Remove qt5-default from build depends (Closes: #972166). - Export QT_SELECT := qt5 in order to let qtchooser use the right Qt version. Checksums-Sha1: 6b4847033d4eb65ec2686444e734b4959070d08e 2216 odin_2.0.4-0.2.dsc 00bef7a0fedf5944eff7bec2ae7e0436f48a9bfa 6984 odin_2.0.4-0.2.debian.tar.xz 9067887fa1294f36fc015f58cea6c8625bb75c17 10521 odin_2.0.4-0.2_source.buildinfo Checksums-Sha256: 14f753fe47f426473609f5c13b194d4e4ac3425b00a4ad2bcbb6b413a5831196 2216 odin_2.0.4-0.2.dsc 65376e127abcc82f56c4464a3f9c3cc88ad3749467bb7db7a99052edad11e191 6984 odin_2.0.4-0.2.debian.tar.xz 38c46530300b14b675300eef349753bf618b9dabba86d8c61d3acfdc736bf05b 10521 odin_2.0.4-0.2_source.buildinfo Files: a876fe2ca04362ae6e6f73f61f961cb5 2216 science optional odin_2.0.4-0.2.dsc f600ed456d0a6ed8cbf13b9119cdc8dd 6984 science optional odin_2.0.4-0.2.debian.tar.xz 856e848a422391cbecec2ce58b5b4fda 10521 science optional odin_2.0.4-0.2_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAl+VwmgUHGxpc2FuZHJv QGRlYmlhbi5vcmcACgkQq2RfQGKGp9AoAxAAua28FEfwuXnmzqYKUqqXGjOpRFf1 GgyzfNI1jqOM6u5nXxn7ZuztLbjDQmni+3mNWfcvzTOoIyE2RMB7RqqXKTG6SBeX NR0wz7qOxWYJ/4UMgHqF1d68t+5XykyFX4RuNs/5C2CTRZKSsyzsH6LUOvQPMITT 0ZpHNuIzBf8pdaFHJ609RHxrQS/MsL2zTSyanPEKqCOMA0X6lVmOfWDCJogGSHXX fR82s8cR6kK3XPwc8AaO9rgI38gcfDYMDrQ3Bb3QWZVTfqTVaDgsvtGHzhfKkDXa mePgWVCYviaAQA/GecPzLQ0ts92ChU4EZZuHZKykISDkzWG0tloqR1DlPtKaAic0 0CAMWBaENnF41q6zSCdgX8HhQtPniJF81iGazqC13mBzc8bw0ktKjL0i3HR4bIFg BQXODj6zks0BLwVswkJfSZZljD6J6TNX9hfFkQOlGoZfx+yykObYaz4zo9wzEf0t pLOoyXKkKP3t9oxD8fIDlk6seYaOjFSeTS/jAkzqvgnXcd4E23ALOwMmTNMaLV8g DFCIGAe75363oEqNndpD95ur35KCd+44lbmhzeRnLX5KK64Ks2xxaxYKAHyOo40j
Bug#972166: Rising severities
Hi! On Sun, 25 Oct 2020 at 20:34, Yaroslav Halchenko wrote: > > Feel welcome to NMU without delay. Sorry for being slow etc. > > Thank you! Thanks to you!!! -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Bug#972163: Bug#972166: Rising severities
Feel welcome to NMU without delay. Sorry for being slow etc. Thank you! On Sun, 25 Oct 2020, Lisandro Damián Nicanor Pérez Meyer wrote: > severity 972163 serious > severity 972166 serious > block 972176 by 972163 > block 972176 by 972166 > thanks > Hi! We are close to begin the Qt transition that will remove > qt5-default, so I'm raising the severities. If everything goes well > I'll be NMUing your package today with an upload to delayed/5. Of > course feel free to ping me if needed. > Thanks, Lisandro. -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 WWW: http://www.linkedin.com/in/yarik signature.asc Description: PGP signature
Bug#972849: marked as done (useful-clojure FTBFS: Could not locate clojure/tools/macro__init.class, clojure/tools/macro.clj or clojure/tools/macro.cljc on classpath)
Your message dated Sun, 25 Oct 2020 23:34:12 + with message-id and subject line Bug#972849: fixed in useful-clojure 0.11.6-3 has caused the Debian Bug report #972849, regarding useful-clojure FTBFS: Could not locate clojure/tools/macro__init.class, clojure/tools/macro.clj or clojure/tools/macro.cljc on classpath 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.) -- 972849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: useful-clojure Version: 0.11.6-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=useful-clojure=all=0.11.6-2=1603520988=0 ... dh_auto_test (cd test && find . -name "*.clj" | \ xargs clojure -cp /<>/useful.jar:/usr/share/java/clojure.jar:/usr/share/java/useful.jar) Syntax error (FileNotFoundException) compiling at (flatland/useful/utils.clj:1:1). Could not locate clojure/tools/macro__init.class, clojure/tools/macro.clj or clojure/tools/macro.cljc on classpath. Full report at: /tmp/clojure-11069530683106326717.edn make[1]: *** [debian/rules:23: override_dh_auto_test] Error 123 --- End Message --- --- Begin Message --- Source: useful-clojure Source-Version: 0.11.6-3 Done: =?utf-8?q?Louis-Philippe_V=C3=A9ronneau?= We believe that the bug you reported is fixed in the latest version of useful-clojure, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Louis-Philippe Véronneau (supplier of updated useful-clojure 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: SHA512 Format: 1.8 Date: Sun, 25 Oct 2020 18:56:55 -0400 Source: useful-clojure Architecture: source Version: 0.11.6-3 Distribution: unstable Urgency: medium Maintainer: Debian Clojure Maintainers Changed-By: Louis-Philippe Véronneau Closes: 972849 Changes: useful-clojure (0.11.6-3) unstable; urgency=medium . * Fix testsuite failure at build by explicitly including missing libs. Closes: #972849 Checksums-Sha1: c551ce11f2f7117541cb109ce9c6ac4d4359c51a 2218 useful-clojure_0.11.6-3.dsc b73ba0dcba3e8c71bff771328779c89865c9a483 6768 useful-clojure_0.11.6-3.debian.tar.xz 1ef7d4c92090c1ff2335b1efa9860950c78e1d61 11007 useful-clojure_0.11.6-3_amd64.buildinfo Checksums-Sha256: 4bbf78c986de2e58bead799409fd9e13b8cd2fb8e2928a636377a1d566d2fdf5 2218 useful-clojure_0.11.6-3.dsc 5982d8b9e2e52dd8ebf1ad4da27b2ee0c013724c5441ffd40809fc91ed92cc93 6768 useful-clojure_0.11.6-3.debian.tar.xz 70e80bb3c24126a9a228f29c5c5a2b5a0c3b9c195bcdcfb0c5bcc41ac747643a 11007 useful-clojure_0.11.6-3_amd64.buildinfo Files: dce05e018c6f025e864390a8b8954344 2218 java optional useful-clojure_0.11.6-3.dsc 6fb747d72afe7a0b266f4912adfb3bbc 6768 java optional useful-clojure_0.11.6-3.debian.tar.xz 780e38fe550c649717738d95458b84fc 11007 java optional useful-clojure_0.11.6-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEZ39U8fqGga2OwLzmeurE7GqqCpcFAl+WB1oACgkQeurE7Gqq Cpdr4w//QnMVs8iEeW/er6K9Xc4f7sgWss3ke9L/fVi6f+C1xYeYkaRW/NK6XCd7 PbtdkogrBegZ0ula+WmZZSCRBAABKPDWWLDYzq8Fhgk7FJuDoRPks8EA+sXs0UdK yokZuK4aV5GuO2nkgbNj42vB0eTAKBLbKVirh9xEOU1oq4bNYeNQZ7PFdIf6SDNs jC8akyi3DoyRQ+EZxTb88CF55t4MSvhU+cjKyBLkd3v34mT38JpuTic1rfy0FyVT LEeI9wXT8hHTJys+Iy8jOJ8CCzAIhBWJhxnhZSbSaJUutrsFNgPL7Fq/F7vZiRdh OwKRRLMPiVMqWBC42mwPBZbilkr8h25Vgg9fmAWsKnYqDf7DAWij6J90okm+O+eO GkC1laKWzs7oNDjWQmPVdeMShFVY8U2myKU52H0zzwmjfvwXqspVRJGVG7LnVQDH O+TbXPR9my2J8dqGfhTFmpvPg8ME25ZRfdcBTQHOP1YJJTY/FRwZs3jargd0ckJf OnsJ3j8cjoG0SytaU8IcSrwHY7KUSZG8prnkHTz1Lfoi8JDoWwecVWnZ3DVTYezZ xKVp2fy57FKbr5b90ItYKzLndEixJmM5CEfLhvi0Zz7xdh92qtywKauOiVQ1M3Ez TyJZw6vKBA/ONoWuwOssk5LW3v9ri4lz8RfzE3grWGL7ad0Sr+A= =m5Co -END PGP SIGNATURE End Message ---
Processed: tagging 970806
Processing commands for cont...@bugs.debian.org: > tags 970806 + confirmed pending Bug #970806 [yubikey-manager] python3-venv is gone Added tag(s) confirmed and pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 970806: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970806 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#963069: marked as done (cloudkitty FTBFS with mock 4.x)
Your message dated Mon, 26 Oct 2020 00:05:03 +0100
with message-id <85e8ec97-da88-bb74-1b1c-da887d960...@debian.org>
and subject line Fixed
has caused the Debian Bug report #963069,
regarding cloudkitty FTBFS with mock 4.x
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.)
--
963069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963069
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: cloudkitty
Version: 12.0.0-3
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=cloudkitty=all=12.0.0-3=1592315217=0
...
==
FAIL:
cloudkitty.tests.api.v2.test_utils.AddInputSchemaTest.test_paginated(sqlite)
cloudkitty.tests.api.v2.test_utils.AddInputSchemaTest.test_paginated(sqlite)
--
testtools.testresult.real._StringException: Traceback (most recent call last):
File "/<>/cloudkitty/tests/api/v2/test_utils.py", line 198, in
test_paginated
with mock.patch('flask.request') as m:
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1460, in __enter__
if spec is None and _is_async_obj(original):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 52, in _is_async_obj
if hasattr(obj, '__func__'):
File "/usr/lib/python3/dist-packages/werkzeug/local.py", line 348, in
__getattr__
return getattr(self._get_current_object(), name)
File "/usr/lib/python3/dist-packages/werkzeug/local.py", line 307, in
_get_current_object
return self.__local()
File "/usr/lib/python3/dist-packages/flask/globals.py", line 38, in
_lookup_req_object
raise RuntimeError(_request_ctx_err_msg)
RuntimeError: Working outside of request context.
This typically means that you attempted to use functionality that needed
an active HTTP request. Consult the documentation on testing for
information about how to avoid this problem.
==
FAIL:
cloudkitty.tests.api.v2.dataframes.test_dataframes.TestDataframeListEndpoint.test_non_admin_request_is_filtered_on_project_id
cloudkitty.tests.api.v2.dataframes.test_dataframes.TestDataframeListEndpoint.test_non_admin_request_is_filtered_on_project_id
--
testtools.testresult.real._StringException: Traceback (most recent call last):
File
"/<>/cloudkitty/tests/api/v2/dataframes/test_dataframes.py", line
32, in test_non_admin_request_is_filtered_on_project_id
with policy_mock, mock.patch('flask.request') as fmock:
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1460, in __enter__
if spec is None and _is_async_obj(original):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 52, in _is_async_obj
if hasattr(obj, '__func__'):
File "/usr/lib/python3/dist-packages/werkzeug/local.py", line 348, in
__getattr__
return getattr(self._get_current_object(), name)
File "/usr/lib/python3/dist-packages/werkzeug/local.py", line 307, in
_get_current_object
return self.__local()
File "/usr/lib/python3/dist-packages/flask/globals.py", line 38, in
_lookup_req_object
raise RuntimeError(_request_ctx_err_msg)
RuntimeError: Working outside of request context.
This typically means that you attempted to use functionality that needed
an active HTTP request. Consult the documentation on testing for
information about how to avoid this problem.
==
FAIL:
cloudkitty.tests.api.v2.test_utils.AddInputSchemaTest.test_simple_add_input_schema_body(sqlite)
cloudkitty.tests.api.v2.test_utils.AddInputSchemaTest.test_simple_add_input_schema_body(sqlite)
--
testtools.testresult.real._StringException: Traceback (most recent call last):
File "/<>/cloudkitty/tests/api/v2/test_utils.py", line 245, in
test_simple_add_input_schema_body
with mock.patch('flask.request') as m:
File "/usr/lib/python3/dist-packages/mock/mock.py", line 1460, in __enter__
if spec is None and _is_async_obj(original):
File "/usr/lib/python3/dist-packages/mock/mock.py", line 52, in _is_async_obj
if hasattr(obj, '__func__'):
File "/usr/lib/python3/dist-packages/werkzeug/local.py", line 348, in
__getattr__
return getattr(self._get_current_object(), name)
File "/usr/lib/python3/dist-packages/werkzeug/local.py", line 307, in
_get_current_object
return self.__local()
File
Bug#972859: marked as done (libsejda-java FTBFS: cannot find symbol)
Your message dated Sun, 25 Oct 2020 23:03:35 + with message-id and subject line Bug#972859: fixed in libsejda-java 4.1.1-2 has caused the Debian Bug report #972859, regarding libsejda-java FTBFS: cannot find symbol 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.) -- 972859: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972859 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libsejda-java Version: 4.1.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libsejda-java=all=4.1.1-1=1603575235=0 ... [INFO] [INFO] Reactor Summary for sejda 4.1.1: [INFO] [INFO] sejda .. SUCCESS [ 0.007 s] [INFO] sejda model SUCCESS [ 3.005 s] [INFO] sejda core . SUCCESS [ 0.385 s] [INFO] sejda fonts SUCCESS [ 0.211 s] [INFO] sejda image writers SUCCESS [ 0.234 s] [INFO] sejda sambox ... FAILURE [ 0.927 s] [INFO] sejda conversion ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 4.949 s [INFO] Finished at: 2020-10-24T21:33:50Z [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sejda-sambox: Compilation failure: Compilation failure: [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PDDocumentHandler.java:[258,48] cannot find symbol [ERROR] symbol: variable ASYNC_BODY_WRITE [ERROR] location: class org.sejda.sambox.output.WriteOption [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PDDocumentHandler.java:[301,17] cannot find symbol [ERROR] symbol: method sanitizeDictionary() [ERROR] location: variable imported of type org.sejda.sambox.pdmodel.PDPage [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/split/PageCopier.java:[101,13] cannot find symbol [ERROR] symbol: method sanitizeDictionary() [ERROR] location: variable copy of type org.sejda.sambox.pdmodel.PDPage [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[131,34] cannot find symbol [ERROR] symbol: method createFromSeekableSource(org.sejda.io.SeekableSource,java.lang.String) [ERROR] location: class org.sejda.sambox.pdmodel.graphics.image.PDImageXObject [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[136,38] cannot find symbol [ERROR] symbol: method createFromSeekableSource(org.sejda.io.SeekableSource,java.lang.String) [ERROR] location: class org.sejda.sambox.pdmodel.graphics.image.PDImageXObject [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[140,42] cannot find symbol [ERROR] symbol: method createFromSeekableSource(org.sejda.io.SeekableSource,java.lang.String) [ERROR] location: class org.sejda.sambox.pdmodel.graphics.image.PDImageXObject [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[157,52] incompatible types: org.sejda.io.SeekableSource cannot be converted to java.io.File [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[164,50] cannot find symbol [ERROR] symbol: method asNewInputStream() [ERROR] location: variable source of type org.sejda.io.SeekableSource [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[191,82] cannot find symbol [ERROR] symbol: method asNewInputStream() [ERROR] location: variable source of type org.sejda.io.SeekableSource [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[237,82] cannot find symbol [ERROR] symbol: method asNewInputStream() [ERROR] location: variable source of type org.sejda.io.SeekableSource [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/SetMetadataTask.java:[79,50] cannot find symbol [ERROR] symbol: class OnBeforeWrite [ERROR] location: class org.sejda.sambox.pdmodel.PDDocument [ERROR]
Processed: fixed 971636 in 2.0.6+1.1.0-1
Processing commands for cont...@bugs.debian.org: > fixed 971636 2.0.6+1.1.0-1 Bug #971636 [php-lua] undefined symbol: ZEND_HASH_GET_APPLY_COUNT Marked as fixed in versions php-lua/2.0.6+1.1.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 971636: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972843: marked as done (kdenlive: abort on start)
Your message dated Mon, 26 Oct 2020 08:50:15 +1100 with message-id <873622rn54@canidae.wired.pri> and subject line Re: Bug#972843: kdenlive: abort on start has caused the Debian Bug report #972843, regarding kdenlive: abort on start 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.) -- 972843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972843 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: kdenlive Version: 20.08.2-1 Severity: grave Justification: renders package unusable If I try to start kdenlive on a new system that has never run kdenlive before, it aborts with an error. $ kdenlive Using modified system locale without group separator for numbers NEW LC_ALL en_AU.UTF-8 Metadata for "glsl.manager" is invalid. WARNING : Fails to parse "glsl.manager" Metadata for "movit.convert" is invalid. WARNING : Fails to parse "movit.convert" Metadata for "movit.crop" is invalid. WARNING : Fails to parse "movit.crop" Metadata for "movit.resample" is invalid. WARNING : Fails to parse "movit.resample" Metadata for "movit.resize" is invalid. WARNING : Fails to parse "movit.resize" "resample" is blacklisted Metadata for "deinterlace" is invalid. WARNING : Fails to parse "deinterlace" "rgblut" is blacklisted "spot_remover" is blacklisted "text" is blacklisted "timer" is blacklisted "qtext" is blacklisted "motion_est" is blacklisted Invalid title/identifier for "crop_detect" / WARNING : Fails to parse "crop_detect" "gtkrescale" is blacklisted "videostab" is blacklisted "videostab2" is blacklisted Metadata for "audiochannels" is invalid. WARNING : Fails to parse "audiochannels" Metadata for "audioconvert" is invalid. WARNING : Fails to parse "audioconvert" Metadata for "data_feed" is invalid. WARNING : Fails to parse "data_feed" "data_show" is blacklisted Metadata for "imageconvert" is invalid. WARNING : Fails to parse "imageconvert" "mask_apply" is blacklisted "mask_start" is blacklisted "mono" is blacklisted "region" is blacklisted "resize" is blacklisted "transition" is blacklisted "watermark" is blacklisted "frei0r.3dflippo" is blacklisted "frei0r.bluescreen0r" is blacklisted "frei0r.bw0r" is blacklisted "frei0r.gamma" is blacklisted "frei0r.invert0r" is blacklisted "frei0r.rgbsplit0r" is blacklisted "frei0r.transparency" is blacklisted "frei0r.vertigo" is blacklisted "burningtv" is blacklisted Metadata for "telecide" is invalid. WARNING : Fails to parse "telecide" Metadata for "jack" is invalid. WARNING : Fails to parse "jack" "jackrack" is blacklisted Metadata for "avcolour_space" is invalid. WARNING : Fails to parse "avcolour_space" Metadata for "avcolor_space" is invalid. WARNING : Fails to parse "avcolor_space" Metadata for "avdeinterlace" is invalid. WARNING : Fails to parse "avdeinterlace" Metadata for "swscale" is invalid. WARNING : Fails to parse "swscale" "avfilter.abench" is blacklisted "avfilter.acompressor" is blacklisted "avfilter.adelay" is blacklisted "avfilter.aecho" is blacklisted "avfilter.aemphasis" is blacklisted "avfilter.aeval" is blacklisted "avfilter.afade" is blacklisted "avfilter.afftfilt" is blacklisted "avfilter.agate" is blacklisted "avfilter.ametadata" is blacklisted "avfilter.arealtime" is blacklisted "avfilter.ashowinfo" is blacklisted "avfilter.channelmap" is blacklisted "avfilter.chorus" is blacklisted "avfilter.earwax" is blacklisted "avfilter.volume" is blacklisted "avfilter.volumedetect" is blacklisted "avfilter.ass" is blacklisted "avfilter.atadenoise" is blacklisted "avfilter.avgblur" is blacklisted "avfilter.bbox" is blacklisted "avfilter.bench" is blacklisted "avfilter.blackdetect" is blacklisted "avfilter.blackframe" is blacklisted "avfilter.boxblur" is blacklisted "avfilter.bwdif" is blacklisted "avfilter.chromakey" is blacklisted "avfilter.colorkey" is blacklisted "avfilter.colormatrix" is blacklisted "avfilter.colorspace" is blacklisted "avfilter.convolution" is blacklisted "avfilter.crop" is blacklisted "avfilter.cropdetect" is blacklisted "avfilter.curves" is blacklisted "avfilter.datascope" is blacklisted "avfilter.dctdnoiz" is blacklisted "avfilter.deband" is blacklisted "avfilter.deflate" is blacklisted "avfilter.deinterlace_vaapi" is blacklisted "avfilter.deshake" is blacklisted "avfilter.despill" is blacklisted "avfilter.doubleweave" is blacklisted "avfilter.drawbox" is blacklisted "avfilter.drawgraph" is blacklisted "avfilter.drawgrid" is blacklisted "avfilter.drawtext" is blacklisted "avfilter.elbg" is blacklisted "avfilter.eq" is blacklisted "avfilter.fade" is blacklisted "avfilter.field" is blacklisted
Processed: bug 972481 is forwarded to https://github.com/tmm1/pygments.rb/issues/195
Processing commands for cont...@bugs.debian.org: > forwarded 972481 https://github.com/tmm1/pygments.rb/issues/195 Bug #972481 [src:ruby-pygments.rb] ruby-pygments.rb: FTBFS, tests failure (due to new pygments) Set Bug forwarded-to-address to 'https://github.com/tmm1/pygments.rb/issues/195'. > thanks Stopping processing here. Please contact me if you need assistance. -- 972481: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972481 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972394: likely cause: Python.h not found because of version mismatch 3.8 vs 3.9
On Sun, Oct 25, 2020 at 10:22:47PM +0100, Stephen Sinclair wrote: > On Wed, Oct 21, 2020 at 10:39 AM Adrian Bunk wrote: > > > > Control: retitle -1 siconos FTBFS with more than one supported python3 > > version > > > > On Mon, Oct 19, 2020 at 11:38:42PM +0200, Markus Koschany wrote: > > > > > > I built siconos in a clean chroot environment. The recent rebuild of > > > siconos also shows build failures > > > > > > https://buildd.debian.org/status/package.php?p=siconos > > > > > > I don't think it's specific to my environment. > > > > You need something like python3-dev -> python3-all-dev in the build > > dependencies. > > I can confirm that making this change allows the package to build. > However, some Python-related tests in autopkgtest fail when trying to > import the Siconos python modules, so something still needs to be > fixed. I will investigate. > As for this change, however, is it the correct one to make? Or should > I wait for more information in #972551? > > > The next problem is what it builds - it then builds for the highest > > version only, not for the default version. > > Can I ask how you determined this? >... I ran debdiff between the package in the archive and the package I built myself. The lack of 3.8 modules in the package also explains your problem. > regards, > Steve cu Adrian
Bug#972394: likely cause: Python.h not found because of version mismatch 3.8 vs 3.9
On Wed, Oct 21, 2020 at 10:39 AM Adrian Bunk wrote: > > Control: retitle -1 siconos FTBFS with more than one supported python3 version > > On Mon, Oct 19, 2020 at 11:38:42PM +0200, Markus Koschany wrote: > > > > I built siconos in a clean chroot environment. The recent rebuild of > > siconos also shows build failures > > > > https://buildd.debian.org/status/package.php?p=siconos > > > > I don't think it's specific to my environment. > > You need something like python3-dev -> python3-all-dev in the build > dependencies. I can confirm that making this change allows the package to build. However, some Python-related tests in autopkgtest fail when trying to import the Siconos python modules, so something still needs to be fixed. I will investigate. As for this change, however, is it the correct one to make? Or should I wait for more information in #972551? > The next problem is what it builds - it then builds for the highest > version only, not for the default version. Can I ask how you determined this? It is not surprising that something could be wrong, as the CMake configuration is very complicated in this package. However, the configure step includes the line, -DPYTHON_EXECUTABLE=$(shell which python3)" which should specify the path to the default Python interpreter. Is there a better way to determine this path? > This bug could be solved by either adjusting the build dependencies > and the build to build for all supported python3 versions, or by fixing > whatever in the build system does not use the default version. I would prefer the latter as the package is already quite complicated and does not play well with multiple pythons. regards, Steve
Bug#972773: marked as done (python-ciso8601 ftbfs with python3.9)
Your message dated Sun, 25 Oct 2020 20:48:56 + with message-id and subject line Bug#972773: fixed in python-ciso8601 2.1.3-3 has caused the Debian Bug report #972773, regarding python-ciso8601 ftbfs with python3.9 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.) -- 972773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-ciso8601 Version: 2.1.3-2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: python3.9 https://people.debian.org/~ginggs/python3.9-default/python-ciso8601_2.1.3-2build1_amd64-2020-10-22T13:38:30Z.build packaging error, you are mixing b-d's python3-all and python3-dev, which cannot work. to support all python3 version, b-d on python3-all-dev, if supporting a single version, b-d on python-dev. Nothing else. --- End Message --- --- Begin Message --- Source: python-ciso8601 Source-Version: 2.1.3-3 Done: Nilesh Patra We believe that the bug you reported is fixed in the latest version of python-ciso8601, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Nilesh Patra (supplier of updated python-ciso8601 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: SHA512 Format: 1.8 Date: Mon, 26 Oct 2020 00:07:25 +0530 Source: python-ciso8601 Architecture: source Version: 2.1.3-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Nilesh Patra Closes: 972773 Changes: python-ciso8601 (2.1.3-3) unstable; urgency=medium . * Team Upload. * Fix Build-Depends (Closes: #972773) * Add hardening options * Add upstream/metadata * Bump compat: version to 13 Checksums-Sha1: 2ccbac93b6602ae57ea7ddf703fca9ceb1c27ae0 2155 python-ciso8601_2.1.3-3.dsc 434780d721de5010177b7736bd33ab9dca8350d4 2384 python-ciso8601_2.1.3-3.debian.tar.xz cda2cc927587637bdc74232a2e55248eec1c7a5b 7370 python-ciso8601_2.1.3-3_amd64.buildinfo Checksums-Sha256: eb71b7f8b2aae387c201a8b28fe48a2a7f05f1704b0ce5bf4d5c359eafd8c364 2155 python-ciso8601_2.1.3-3.dsc 4c3d0afadf18f4fb14d68c1a58319754cfc2477a24b40569ec7f03f1f04abe4a 2384 python-ciso8601_2.1.3-3.debian.tar.xz acd77d4b36accadc0d071fef56d9a8c45e3472997a5e280ba96d6f76e74f51d5 7370 python-ciso8601_2.1.3-3_amd64.buildinfo Files: 42873fc0a2ab99b80d7867a105c5c77a 2155 python optional python-ciso8601_2.1.3-3.dsc 43d281a6e8b7dd4757e14c9235bf703b 2384 python optional python-ciso8601_2.1.3-3.debian.tar.xz e667d7698ae61717b3b13ae8941b47b6 7370 python optional python-ciso8601_2.1.3-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAl+V4IQUHG5wYXRyYTk3 NEBnbWFpbC5jb20ACgkQALrnSzQzafF+Hw/+OHXAO3ybAm3dIA7T8RmjpWsJ9Mmc Y8NZfrVuwyIIwDNVY0ZTr+jFahrWd4xKoZHZOAZ387CoLhQY+dD8S35qbPe1reFH 7Ya9d0oXkYUt3KTIKzBYP+p/E1A6+H33fpPW82obaHtP+RT2zdBsH5dsqUUwHOBR gbXe7KPdynF7xM23pTAj8PRP+uGBGgsLaM9OnHKdj39kUieoAq+tGHDd25M3Ug9a l1kPq/tgSS4UGsx95qS+rlcC4QOwIHmg9HmjLYXBUiJweJnte5EvA5BXYUBYb+cH uEq+kcZJWdEpCP7bCMAR8ag3ISPY2GZOitXta/Biu2sqRs8sEJKWrm+zVDQ9QywS EZRD/pQqceJJTmSrxc4ql+e1H64IeFcjw5uMBbjaSaPOblLvkWDvqs9O++C6+Gbe StLbhRYRZcVtmCqxoKXZCcKUy2PyxpIcUDVhFl3SU22ELO+I/AYYYH+MvkVKlPMR PdsL7f4rOhYRlgalNMdXHD1iq26ZdNJFVWp2YjU9tUmuByf+fzBkv2YNYAPegpNe MyuCxNkK4Q7YlMy23CcCsayjh0E9luApwZ5B8SFHAajXE357TAf7hK6mrXFcJvOQ kyy4SaRiS/w1zPu9zysntJQLCJ/7cVwWSUPffhtwJm/Z3y4inxJ2mMEUSdQTXmAh 42S2Wmk9lyhzzok= =UDpt -END PGP SIGNATURE End Message ---
Bug#972874: marked as done (django-ldapdb 1.5.1-1 fails its autopkgtest)
Your message dated Sun, 25 Oct 2020 20:22:44 + with message-id and subject line Bug#972874: fixed in django-ldapdb 1.5.1-2 has caused the Debian Bug report #972874, regarding django-ldapdb 1.5.1-1 fails its autopkgtest 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.) -- 972874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: django-ldapdb Version: 1.5.1-1 Severity: serious Dear Maintainer, The autopkgtest of django-ldapdb 1.5.1-1 fails in testing and unstable. https://ci.debian.net/data/autopkgtest/testing/amd64/d/django-ldapdb/7719338/log.gz django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. I see the same failure in a pure unstable chroot without any packages from testing. Could you please take a look? This is blocking openldap from migrating to testing. (https://qa.debian.org/excuses.php?package=openldap) Thank you, Ryan --- End Message --- --- Begin Message --- Source: django-ldapdb Source-Version: 1.5.1-2 Done: Michael Fladischer We believe that the bug you reported is fixed in the latest version of django-ldapdb, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Fladischer (supplier of updated django-ldapdb 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: SHA512 Format: 1.8 Date: Sun, 25 Oct 2020 20:43:12 +0100 Source: django-ldapdb Architecture: source Version: 1.5.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Michael Fladischer Closes: 972874 Changes: django-ldapdb (1.5.1-2) unstable; urgency=medium . * Run manage_dev.py for CI tests (Closes: #972874). Checksums-Sha1: 4d06f5fed8fa5e01cb1b04c3f0f83ae9b2e9a216 1898 django-ldapdb_1.5.1-2.dsc e4309a2439230bd6ba76e9a7d519fef6c6c7cf64 3304 django-ldapdb_1.5.1-2.debian.tar.xz 2c8a75c9fb70c62ef447c5c9f96c85bad6e53f32 7674 django-ldapdb_1.5.1-2_amd64.buildinfo Checksums-Sha256: 397e664d1c8d1e7d72bcbe20acb37c97674541685b9000c4f2b48fdf8b502ad7 1898 django-ldapdb_1.5.1-2.dsc 28babba73dd984738333d25a223b2631af614da28b5af781074cecd6588a6d82 3304 django-ldapdb_1.5.1-2.debian.tar.xz cbc7e67a9d3bb1c7141cf4d39c12e86099ca3a4945308e75e91fe29bcf41327a 7674 django-ldapdb_1.5.1-2_amd64.buildinfo Files: 6bf9a39e64fa015e1ff41469a9da3e83 1898 python optional django-ldapdb_1.5.1-2.dsc 5a02fd4c5aa77ad382593e1f39727781 3304 python optional django-ldapdb_1.5.1-2.debian.tar.xz f8675ebd5558dcf8840699a785c7a57d 7674 python optional django-ldapdb_1.5.1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQEzBAEBCgAdFiEEqVSlRXW87UkkCnJc/9PIi5l90WoFAl+V1p4ACgkQ/9PIi5l9 0Wq9CAf+K+JIfuwJ1ATxvsjAiDPE+/Vt74z+wah/WPy75BI0ascjpnPcVw7loob9 NtP0gS+2GVDhdrgRQaLwQDdxyoaWIbrUdQvME//NdCIrYdLF1nOvdN0rWZNTbNem wT7HWfXLMrwiZHD9kROGfAKx92GJRazT/2KcgoCaa8yAUXYYEhcEeo6CD3KuCDh9 vNeHjVWtFaLOgUxZ/qChXAgTeYJK59TFsDcfbYtpP3+g/fvi7JhbcLzmtwMbmJIf Oii0W5nuTjFtSEU6aF9RCOervMYMlMeNpBFZSaMMUJrJvyudKPUkblNY84/EtIFi HMZqRpr8Y5VvtBGh9uNAb2nn2Qogig== =72OK -END PGP SIGNATURE End Message ---
Bug#972888: libclutter-perl: Deprecated upstream
Source: libclutter-perl Severity: serious User: debian-p...@lists.debian.org Usertags: rm-candidate Hi, upstream announced¹ that the Clutter Perl module would be deprecated in December 2020. It is actually already archived on their GitLab, so: - The module will no longer be updated with security patches, bug fixes, or when changes are made in the Perl ABI. - It will no longer be possible to submit new issues or pull requests for these modules, or push new changes to their Git repos. Therefore, I don't think we should ship this package in Bullseye. Any objection to removing the package from testing & sid? This is a leaf package and popcon is 0/9 (vote/inst). [1] https://mail.gnome.org/archives/gtk-perl-list/2020-October/msg2.html
Bug#972887: libgstreamer1-perl: Deprecated upstream
Source: libgstreamer1-perl Severity: serious X-Debbugs-Cc: Mike Gabriel User: debian-p...@lists.debian.org Usertags: rm-candidate Hi, upstream announced¹ that the GStreamer Perl module would be deprecated and archived in December 2020: - The module will no longer be updated with security patches, bug fixes, or when changes are made in the Perl ABI. - It will no longer be possible to submit new issues or pull requests for these modules, or push new changes to their Git repos. Therefore, I don't think we should ship this package in Bullseye. Any objection to removing the package from testing & sid? This is a leaf package and popcon is 4/19 (vote/inst). [1] https://mail.gnome.org/archives/gtk-perl-list/2020-October/msg2.html
Processed: Move where the bug was
Processing commands for cont...@bugs.debian.org: > reassign 967105 libosgi-core-java 7.0.0-1 Bug #967105 [src:libgpars-groovy-java] libgpars-groovy-java: FTBFS: The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead. Bug reassigned from package 'src:libgpars-groovy-java' to 'libosgi-core-java'. No longer marked as found in versions libgpars-groovy-java/1.2.1-10. Ignoring request to alter fixed versions of bug #967105 to the same values previously set Bug #967105 [libosgi-core-java] libgpars-groovy-java: FTBFS: The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead. Marked as found in versions osgi-core/7.0.0-1. > affects 967105 src:libgpars-groovy-java Bug #967105 [libosgi-core-java] libgpars-groovy-java: FTBFS: The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead. Added indication that 967105 affects src:libgpars-groovy-java > close 967105 7.0.0-2 Bug #967105 [libosgi-core-java] libgpars-groovy-java: FTBFS: The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead. Marked as fixed in versions osgi-core/7.0.0-2. Bug #967105 [libosgi-core-java] libgpars-groovy-java: FTBFS: The Task.leftShift(Closure) method has been deprecated and is scheduled to be removed in Gradle 5.0. Please use Task.doLast(Action) instead. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 967105: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967105 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#972874 marked as pending in django-ldapdb
Processing control commands: > tag -1 pending Bug #972874 [src:django-ldapdb] django-ldapdb 1.5.1-1 fails its autopkgtest Added tag(s) pending. -- 972874: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972874 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972874: marked as pending in django-ldapdb
Control: tag -1 pending Hello, Bug #972874 in django-ldapdb reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/django-ldapdb/-/commit/420ff4bba0eb135d1441ad0befdf690070842eaa Run manage_dev.py for CI tests (Closes: #972874). (this message was generated automatically) -- Greetings https://bugs.debian.org/972874
Processed: swi-prolog, add forward tag
Processing commands for cont...@bugs.debian.org: > forwarded 972862 https://github.com/SWI-Prolog/packages-ssl/issues/158 Bug #972862 [swi-prolog] swi-prolog: FTBFS with OpenSSL 1.1.1h Set Bug forwarded-to-address to 'https://github.com/SWI-Prolog/packages-ssl/issues/158'. > End of message, stopping processing here. Please contact me if you need assistance. -- 972862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972862 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972858: zim FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/run/user/2952'
FWIW, this is really a bug in the build daemon that should not set XDG_RUNTIME_DIR to some incorrect value: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842565 But I'll work around it in the mean time. Cheers, -- ⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋The Debian Handbook: https://debian-handbook.info/get/ ⠈⠳⣄ Debian Long Term Support: https://deb.li/LTS
Bug#972163: marked as done (fwbuilder: Depends on package qt5-default which is about to be removed)
Your message dated Sun, 25 Oct 2020 18:48:53 + with message-id and subject line Bug#972163: fixed in fwbuilder 5.3.7-4.1 has caused the Debian Bug report #972163, regarding fwbuilder: Depends on package qt5-default which is about to be removed 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.) -- 972163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972163 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fwbuilder Version: 5.3.7-4 Severity: important User: debian-qt-...@lists.debian.org Usertags: qt5-default-removal X-Debbugs-Cc: pkg-kde-t...@alioth-lists.debian.net Hi! Your package currently depends upon qt5-default. This package was not intended to be used neither as a build dpeendency nor as a package dependency. Moreover it has created more issues that it solved, so now that Qt 4 is gone and Qt 5 is the default we are retiring it. Anyways you can always check https://qt-kde-team.pages.debian.net/packagingqtbasedstuff.html for more information. Feel free to ping me if you need help. Kinds regards, Lisandro. -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386, arm64, armhf Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), LANGUAGE=es_AR:es Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled --- End Message --- --- Begin Message --- Source: fwbuilder Source-Version: 5.3.7-4.1 Done: =?utf-8?q?Lisandro_Dami=C3=A1n_Nicanor_P=C3=A9rez_Meyer?= We believe that the bug you reported is fixed in the latest version of fwbuilder, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Lisandro Damián Nicanor Pérez Meyer (supplier of updated fwbuilder 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: Sun, 25 Oct 2020 15:27:07 -0300 Source: fwbuilder Architecture: source Version: 5.3.7-4.1 Distribution: unstable Urgency: medium Maintainer: Sylvestre Ledru Changed-By: Lisandro Damián Nicanor Pérez Meyer Closes: 972163 Changes: fwbuilder (5.3.7-4.1) unstable; urgency=medium . * Non-maintainer upload. * Remove qt5-default from build dependencies (Closes: #972163). - Export QT_SELECT in order to let qtchooser select the right version. Checksums-Sha1: 6f576686cc8697bc7c0117aaac62516b809d12d6 2143 fwbuilder_5.3.7-4.1.dsc ee156d87ed61f7aad6356e3ce7da8ac04013784e 12376 fwbuilder_5.3.7-4.1.debian.tar.xz 69e09dc4c15797bcbd0e8d9e89668938eec45b31 10461 fwbuilder_5.3.7-4.1_source.buildinfo Checksums-Sha256: df15152e3140452190627766227498d9f90f2d82d603cfff985db50c5863bd39 2143 fwbuilder_5.3.7-4.1.dsc 59941ef399fe8957b444dc57880aab295d291619bd7f912000a3410b388be11c 12376 fwbuilder_5.3.7-4.1.debian.tar.xz afe39689720da9058c28621500e357b919e3c036c17f4c892ba88b8ed174d08e 10461 fwbuilder_5.3.7-4.1_source.buildinfo Files: 2cbf0e038cbed145e3ed2a770758857e 2143 net optional fwbuilder_5.3.7-4.1.dsc 884dd872764cf8dd5fbb67a1662fe07f 12376 net optional fwbuilder_5.3.7-4.1.debian.tar.xz d6ef702d6a562f2bdcc7fa2b565ec010 10461 net optional fwbuilder_5.3.7-4.1_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAl+Vw5IUHGxpc2FuZHJv QGRlYmlhbi5vcmcACgkQq2RfQGKGp9CSzxAAk6sUXhJUiUyPvhWTxJLtIQK5PfmW GicmDSK04qb/Uq+MIVp05Jhpem0HVPbCgv7rStvJnVUsBt95k5jcWhaxH3CCReZz oZ6sWsw0r6lzwZ3SXcuFJxZGVuUQXOy5zdNOZrbOsQkZbwMJ3aThBGQ/z4KgusdJ FgTRe9CqlZdIRN+vpP2pBHVv6oBltvmthSln+1Y+M2Gd8njX3V4880pdAaUsMlpu fhocE8aQrtAyKO5jfpi6OpHcsxg6tj30aJIVPr/NkNomMdXbG1Amn+3ud6eOIesD MIyoMSgm4feLMBeFQeIBBjEsg9H5p40agHU7N8EmNqe6Z5MxbpjLh/oTDY9fSOzh 4gigHyEGs1tG3eGBhbdlmoAp5UF3MMX6ML3mivz3dcSI3gM51koNV0w8UDuNkQum v3q46tjWP3eH10/zPC5/rrgWStw+XD9aGmbe7VBcYajZK/1r6+qCy0Kw5phoxRIG LMJ97L79N0L1DkESoR45o0f1jlliEiJ/YaoR2IK2zs2HSErT/thfqSJ5pJPyr8uE
Bug#947533: marked as done (kupfer: build-depends on deprecated gnome-doc-utils)
Your message dated Sun, 25 Oct 2020 18:49:07 + with message-id and subject line Bug#947533: fixed in kupfer 0+v320-1 has caused the Debian Bug report #947533, regarding kupfer: build-depends on deprecated gnome-doc-utils 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.) -- 947533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kupfer Version: 0+v319-5 Severity: important Control: block 936625 by -1 Control: block 889019 by -1 User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gnome-doc-utils This package Build-Depends on gnome-doc-utils. gnome-doc-utils is a deprecated package of documentation utilities. Its most recent upstream release was in 2012, with most changes in its git repository since then being translation updates. The GNOME team do not consider gnome-doc-utils to be suitable for release in Debian 11 'bullseye'. The supported replacement is yelp.m4 in yelp-tools, as used in many GNOME 3 packages. A porting guide is available: https://wiki.gnome.org/Initiatives/GnomeGoals/NewDocumentationInfrastructure gnome-doc-utils relies on Python 2 code that seems unlikely to be converted to Python 3, so bug #936625 (part of the effort to remove Python 2 from Debian for Debian 11 'bullseye') has its severity set to serious. This means that this bug is highly likely to be elevated to serious severity at some point in future. Please convert this package to use yelp-tools, or if necessary remove the documentation processing entirely. Thanks, smcv --- End Message --- --- Begin Message --- Source: kupfer Source-Version: 0+v320-1 Done: Hugo Lefeuvre We believe that the bug you reported is fixed in the latest version of kupfer, 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 947...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Hugo Lefeuvre (supplier of updated kupfer 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: SHA512 Format: 1.8 Date: Sun, 25 Oct 2020 14:50:07 + Source: kupfer Architecture: source Version: 0+v320-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Hugo Lefeuvre Closes: 947533 Changes: kupfer (0+v320-1) unstable; urgency=medium . [ Ondřej Nový ] * Bump Standards-Version to 4.4.1. * d/control: Update Maintainer field with new Debian Python Team contact address. * d/control: Update Vcs-* fields with new Debian Python Team Salsa layout. . [ Debian Janitor ] * Add missing build dependency on dh addon. * Set upstream metadata fields: Bug-Database, Bug-Submit. . [ Hugo Lefeuvre ] * New upstream release. - Use itstool instead of xml2po. * debian/watch: Point to new upstream repo, use version=4. * debian/control: Build-Depend on itstool and not deprecated gnome-doc-utils (Closes: #947533). * debian/rules: use --no-hooks Checksums-Sha1: e0edf1981ab48876007e18b4acd422eba0ef 1846 kupfer_0+v320-1.dsc 0e305696f96ea1ec4ddfb38ea624cd076c55f64d 1143805 kupfer_0+v320.orig.tar.gz 1547ae393fc383886f23f0aa164de1f4099121d7 9168 kupfer_0+v320-1.debian.tar.xz e95fc086d3eb204b05a96aba6c19673fe710e6c5 7140 kupfer_0+v320-1_amd64.buildinfo Checksums-Sha256: a4fa459d231e3c0e751688a173280c48582c504756572b966b9ac9c92b14d28b 1846 kupfer_0+v320-1.dsc 4423fb6b422fbb3ed383008839b69896c60cb732ee97e51db351705877f6 1143805 kupfer_0+v320.orig.tar.gz e18bf8ffe181f0d08f8b8f678a5b6cd6a16fbd471e4eb8ad6d38b24b608af8aa 9168 kupfer_0+v320-1.debian.tar.xz f7ccb6d9a482196c013446bc542534520af1f22c701351aaae9af93afdc43048 7140 kupfer_0+v320-1_amd64.buildinfo Files: bce65a2401df03e07b687686f91897ba 1846 utils optional kupfer_0+v320-1.dsc 72fd4d135d32555c3530dfdfac3cab52 1143805 utils optional kupfer_0+v320.orig.tar.gz 4b32c907419a03e9575fe1f65288970a 9168 utils optional kupfer_0+v320-1.debian.tar.xz 32de0fed3fa2ed52351fe1f3f945790c 7140 utils optional kupfer_0+v320-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQHDBAEBCgAtFiEEeDb9QWtkMa2LX4zREeMFjl5EGkIFAl+VxBkPHGhsZUBkZWJp
Processed: Bug#972773 marked as pending in python-ciso8601
Processing control commands: > tag -1 pending Bug #972773 [src:python-ciso8601] python-ciso8601 ftbfs with python3.9 Added tag(s) pending. -- 972773: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972773 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972773: marked as pending in python-ciso8601
Control: tag -1 pending Hello, Bug #972773 in python-ciso8601 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/python-ciso8601/-/commit/82579f4393b324e334e2ef48b7e276eb09489264 Fix Build-Depends (Closes: #972773) (this message was generated automatically) -- Greetings https://bugs.debian.org/972773
Bug#972163: Rising severities
Hi! On Sun, 25 Oct 2020 at 15:00, Sylvestre Ledru wrote: [snip] > Please upload your version, it is fine :) Done! Of course I'll keep an eye on the buildds in case something goes wrong. Thanks!!! -- Lisandro Damián Nicanor Pérez Meyer http://perezmeyer.com.ar/ http://perezmeyer.blogspot.com/
Bug#947533: marked as pending in kupfer
Control: tag -1 pending Hello, Bug #947533 in kupfer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/kupfer/-/commit/6ede52261a379e73640e7249223e0d502fcf6464 New upstream release. * New upstream release. - Use itstool instead of xml2po. * debian/watch: Point to new upstream repo, use version=4. * debian/control: Build-Depend on itstool and not deprecated gnome-doc-utils (Closes: #947533). (this message was generated automatically) -- Greetings https://bugs.debian.org/947533
Processed: Bug#947533 marked as pending in kupfer
Processing control commands: > tag -1 pending Bug #947533 [src:kupfer] kupfer: build-depends on deprecated gnome-doc-utils Added tag(s) pending. -- 947533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971150: marked as done (ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(output.size).to eq(0))
Your message dated Sun, 25 Oct 2020 18:19:19 + with message-id and subject line Bug#971150: fixed in ruby-puppet-syntax 2.6.1-3 has caused the Debian Bug report #971150, regarding ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(output.size).to eq(0) 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.) -- 971150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-puppet-syntax Version: 2.6.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > Failure/Error: expect(output.size).to eq(0) > >expected: 0 > got: 1 > >(compared using ==) > # ./spec/puppet-syntax/manifests_spec.rb:165:in `block (4 levels) in > ' > > 2) PuppetSyntax::Templates on Puppet >= 3.7 should return nothing from a > valid file FIXED > Expected pending 'puppet is causing a ruby warning and fails the purpose > of this test' to fail. No error was raised. > # ./spec/puppet-syntax/templates_spec.rb:99 > > 3) PuppetSyntax::Templates on Puppet >= 3.7 should catch SyntaxError FIXED > Expected pending 'puppet is causing a ruby warning and fails the purpose > of this test' to fail. No error was raised. > # ./spec/puppet-syntax/templates_spec.rb:107 > > 4) PuppetSyntax::Templates on Puppet >= 3.7 should read more than one valid > file FIXED > Expected pending 'puppet is causing a ruby warning and fails the purpose > of this test' to fail. No error was raised. > # ./spec/puppet-syntax/templates_spec.rb:116 > > 5) PuppetSyntax::Templates on Puppet >= 3.7 should continue after finding > an error in the first file FIXED > Expected pending 'puppet is causing a ruby warning and fails the purpose > of this test' to fail. No error was raised. > # ./spec/puppet-syntax/templates_spec.rb:124 > > 6) PuppetSyntax::Templates on Puppet >= 3.7 when the 'epp_only' options is > set should process an ERB as EPP and find an error FIXED > Expected pending 'puppet is causing a ruby warning and fails the purpose > of this test' to fail. No error was raised. > # ./spec/puppet-syntax/templates_spec.rb:139 > > Finished in 0.12527 seconds (files took 0.75656 seconds to load) > 43 examples, 6 failures > > Failed examples: > > rspec ./spec/puppet-syntax/manifests_spec.rb:159 # PuppetSyntax::Manifests > app_management app_management = true should successfully parse an application > manifest on Puppet >= 4.3.0 > rspec ./spec/puppet-syntax/templates_spec.rb:99 # PuppetSyntax::Templates on > Puppet >= 3.7 should return nothing from a valid file > rspec ./spec/puppet-syntax/templates_spec.rb:107 # PuppetSyntax::Templates on > Puppet >= 3.7 should catch SyntaxError > rspec ./spec/puppet-syntax/templates_spec.rb:116 # PuppetSyntax::Templates on > Puppet >= 3.7 should read more than one valid file > rspec ./spec/puppet-syntax/templates_spec.rb:124 # PuppetSyntax::Templates on > Puppet >= 3.7 should continue after finding an error in the first file > rspec ./spec/puppet-syntax/templates_spec.rb:139 # PuppetSyntax::Templates on > Puppet >= 3.7 when the 'epp_only' options is set should process an ERB as EPP > and find an error > > /usr/bin/ruby2.7 > -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib > /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec > --pattern ./spec/\*\*/\*_spec.rb --format documentation failed > ERROR: Test "ruby2.7" failed: The full build log is available from: http://qa-logs.debian.net/2020/09/26/ruby-puppet-syntax_2.6.1-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: ruby-puppet-syntax Source-Version: 2.6.1-3 Done: Apollon Oikonomopoulos We believe that the bug you reported is fixed in the latest version of ruby-puppet-syntax, 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
Processed: Bug#971150 marked as pending in ruby-puppet-syntax
Processing control commands: > tag -1 pending Bug #971150 [src:ruby-puppet-syntax] ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: expect(output.size).to eq(0) Added tag(s) pending. -- 971150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#971150: marked as pending in ruby-puppet-syntax
Control: tag -1 pending Hello, Bug #971150 in ruby-puppet-syntax reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-puppet-syntax/-/commit/fd4a0e39db2bd64e1004348437c4cd9b3b4ceb5d Tolerate Puppet >=5.5.21 deprecation warnings Puppet 5.5.21 has deprecated the application orchestration primitives and the relevant deprecation warnings broke the tests. Fix this by making sure the warnings are tolerated. Closes: #971150 (this message was generated automatically) -- Greetings https://bugs.debian.org/971150
Bug#972163: Rising severities
Le 25/10/2020 à 18:54, Lisandro Damián Nicanor Pérez Meyer a écrit : Hi Sylvestre! On Sun, 25 Oct 2020 at 11:20, Lisandro Damián Nicanor Pérez Meyer wrote: Hi! El dom., 25 oct. 2020 11:07, Sylvestre Ledru escribió: Hello, [snip] I tried to upload it with your fix but the build failed for me. If it works for you, please upload (without delay) many thanks tl;dr: I could build the package with just my changes, but only using the uploaded debian source package. # Building using the salsa repo I cloned the repo and noticed that apart from the merge of the MR I created there are other changes to the packaging. I tried building master's HEAD but autoconf fails almost immediately. I'm afraid I don't know a thing about it, so I switched to commit 673f53defb054873e40860ba11937860b3266863 (the one in which you accept my MR) and the build failed with missing installation files more on this below. I then switched to tag 5.3.7-4 (which should be "the same thing" as the last upload to the archive) and got the same error. See buildlog.xz attached to this mail for the full build log of this last two cases. The builds where done in an schroot-managed chroot which is not exactly clean: it also has git and a few more packages installed in it, I normally use it for development. # Building with the package uploaded to the archive I then tried to build the latest uploaded version to the archive, fwbuilder_5.3.7-4 using an sbuild chroot. It just went fine. I then added my changes on top of it and the build succeeded again. So it's either a difference in my build environment or the packaging and what's in salsa. In order to fix this bug I could upload an NMU containing just my changes, but I don't think I'll be able to also add the ones you added in the repo. Please upload your version, it is fine :) Thanks S
Processed: Re: Bug#972677: deepin-image-viewer: FTBFS with Qt 5.15: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined
Processing control commands: > tags -1 + pending Bug #972677 [src:deepin-image-viewer] deepin-image-viewer: FTBFS with Qt 5.15: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined Added tag(s) pending. -- 972677: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972677 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972677: deepin-image-viewer: FTBFS with Qt 5.15: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined
Control: tags -1 + pending On Thu, Oct 22, 2020 at 02:05:20PM +0300, Dmitry Shachnev wrote: > Dear Maintainer, > > deepin-image-viewer fails to build with Qt 5.15, currently available in > experimental. > > After rebuilding dde-qt-dbus-factory and libqtxdg, and building a fixed > version of dtkwidget (see #972155), I get this error: > > widgets/popupmenustyle.cpp: In member function ‘virtual void > PopupMenuStyle::drawPrimitive(QStyle::PrimitiveElement, const QStyleOption*, > QPainter*, const QWidget*) const’: > widgets/popupmenustyle.cpp:117:22: error: aggregate ‘QPainterPath path’ has > incomplete type and cannot be defined > 117 | QPainterPath path; > | ^~~~ > widgets/popupmenustyle.cpp:133:13: error: ‘QPainterPathStroker’ was not > declared in this scope; did you mean ‘QPainterPath’? > 133 | QPainterPathStroker stroker; > | ^~~ > | QPainterPath > widgets/popupmenustyle.cpp:134:13: error: ‘stroker’ was not declared in > this scope; did you mean ‘strtok_r’? > 134 | stroker.setWidth(FRAME_BORDER_WIDTH); > | ^~~ > | strtok_r > widgets/popupmenustyle.cpp:136:26: error: variable ‘QPainterPath > borderPath’ has initializer but incomplete type > 136 | QPainterPath borderPath = stroker.createStroke(path); > | ^~ > > widgets/thumbnaillistview.cpp: In member function ‘virtual void > ThumbnailListView::paintEvent(QPaintEvent*)’: > widgets/thumbnaillistview.cpp:301:18: error: aggregate ‘QPainterPath bp’ > has incomplete type and cannot be defined > 301 | QPainterPath bp; > | ^~ > > This is fixed upstream, see the linked commit. I have just uploaded the NMU fixing this to DELAYED/5. The debdiff is attached. -- Dmitry Shachnev diff -Nru deepin-image-viewer-5.0.0/debian/changelog deepin-image-viewer-5.0.0/debian/changelog --- deepin-image-viewer-5.0.0/debian/changelog 2019-10-04 18:08:11.0 +0300 +++ deepin-image-viewer-5.0.0/debian/changelog 2020-10-25 20:33:15.0 +0300 @@ -1,3 +1,10 @@ +deepin-image-viewer (5.0.0-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Backport upstream patch to fix build with Qt 5.15 (closes: #972677). + + -- Dmitry Shachnev Sun, 25 Oct 2020 20:33:15 +0300 + deepin-image-viewer (5.0.0-1) unstable; urgency=medium * New upstream release 5.0.0. diff -Nru deepin-image-viewer-5.0.0/debian/patches/fix-build-failed-under-Qt-5.15.0.patch deepin-image-viewer-5.0.0/debian/patches/fix-build-failed-under-Qt-5.15.0.patch --- deepin-image-viewer-5.0.0/debian/patches/fix-build-failed-under-Qt-5.15.0.patch 1970-01-01 03:00:00.0 +0300 +++ deepin-image-viewer-5.0.0/debian/patches/fix-build-failed-under-Qt-5.15.0.patch 2020-10-25 20:33:15.0 +0300 @@ -0,0 +1,60 @@ +From: zhangjinqiang +Date: Mon, 14 Sep 2020 02:54:58 + +Subject: fix: build failed under Qt 5.15.0 + +(cherry picked from commit b11d7cbdcdd99c82e3feff2aac21e28c6a81f7e7) +--- + viewer/widgets/dspinner.cpp | 1 + + viewer/widgets/popupmenustyle.cpp| 1 + + viewer/widgets/thumbnaildelegate.cpp | 1 + + viewer/widgets/thumbnaillistview.cpp | 1 + + 4 files changed, 4 insertions(+) + +diff --git a/viewer/widgets/dspinner.cpp b/viewer/widgets/dspinner.cpp +index 2931f3e..ccfae88 100644 +--- a/viewer/widgets/dspinner.cpp b/viewer/widgets/dspinner.cpp +@@ -2,6 +2,7 @@ + + #include + #include ++#include + #include + + #include +diff --git a/viewer/widgets/popupmenustyle.cpp b/viewer/widgets/popupmenustyle.cpp +index ddb509c..0fd91f7 100644 +--- a/viewer/widgets/popupmenustyle.cpp b/viewer/widgets/popupmenustyle.cpp +@@ -19,6 +19,7 @@ + #include + #include + #include ++#include + #include + #include + +diff --git a/viewer/widgets/thumbnaildelegate.cpp b/viewer/widgets/thumbnaildelegate.cpp +index 64bd65e..1a09702 100644 +--- a/viewer/widgets/thumbnaildelegate.cpp b/viewer/widgets/thumbnaildelegate.cpp +@@ -23,6 +23,7 @@ + #include + #include + #include ++#include + #include + #include + #include +diff --git a/viewer/widgets/thumbnaillistview.cpp b/viewer/widgets/thumbnaillistview.cpp +index f27fa22..cb7e015 100644 +--- a/viewer/widgets/thumbnaillistview.cpp b/viewer/widgets/thumbnaillistview.cpp +@@ -30,6 +30,7 @@ + #include + #include + #include ++#include + #include + #include + #include diff -Nru deepin-image-viewer-5.0.0/debian/patches/series deepin-image-viewer-5.0.0/debian/patches/series --- deepin-image-viewer-5.0.0/debian/patches/series 1970-01-01 03:00:00.0 +0300 +++ deepin-image-viewer-5.0.0/debian/patches/series 2020-10-25 20:33:15.0 +0300 @@ -0,0 +1 @@ +fix-build-failed-under-Qt-5.15.0.patch signature.asc Description: PGP signature
Processed: Re: Raising severities
Processing commands for cont...@bugs.debian.org: > unblock 972176 by 972163 972166 Bug #972176 [src:shotcut] shotcut: FTBFS with Qt 5.15: error: aggregate 'QPainterPath histPath' has incomplete type and cannot be defined 972176 was blocked by: 972163 972166 972176 was blocking: 972278 Removed blocking bug(s) of 972176: 972166 and 972163 > block 972278 by 972163 972166 Bug #972278 [release.debian.org] transition: qtbase-opensource-src 972278 was blocked by: 972676 972160 972178 972179 972677 972158 972156 972175 972155 972176 972355 957436 972354 972154 972177 972157 972278 was not blocking any bugs. Added blocking bug(s) of 972278: 972163 and 972166 > thanks Stopping processing here. Please contact me if you need assistance. -- 972176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972176 972278: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972278 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972867: CharLS should have changed its SOVERSION
Control: tags -1 upstream For details: https://github.com/team-charls/charls/issues/81
Processed: CharLS should have changed its SOVERSION
Processing control commands: > tags -1 upstream Bug #972867 [src:charls] gdcm: FTBFS in testing and unstable Added tag(s) upstream. -- 972867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972867 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: your mail
Processing commands for cont...@bugs.debian.org: > reassign 972867 src:charls 2.1.0+dfsg-1 Bug #972867 [src:gdcm] gdcm: FTBFS in testing and unstable Bug reassigned from package 'src:gdcm' to 'src:charls'. No longer marked as found in versions gdcm/3.0.7-3. Ignoring request to alter fixed versions of bug #972867 to the same values previously set Bug #972867 [src:charls] gdcm: FTBFS in testing and unstable Marked as found in versions charls/2.1.0+dfsg-1. > affects 972867 src:gdcm Bug #972867 [src:charls] gdcm: FTBFS in testing and unstable Added indication that 972867 affects src:gdcm > End of message, stopping processing here. Please contact me if you need assistance. -- 972867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972867 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972874: django-ldapdb 1.5.1-1 fails its autopkgtest
Source: django-ldapdb Version: 1.5.1-1 Severity: serious Dear Maintainer, The autopkgtest of django-ldapdb 1.5.1-1 fails in testing and unstable. https://ci.debian.net/data/autopkgtest/testing/amd64/d/django-ldapdb/7719338/log.gz django.core.exceptions.ImproperlyConfigured: Requested setting INSTALLED_APPS, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings. I see the same failure in a pure unstable chroot without any packages from testing. Could you please take a look? This is blocking openldap from migrating to testing. (https://qa.debian.org/excuses.php?package=openldap) Thank you, Ryan
Bug#971816: marked as done (gnome-shell-timer: fails to load with GNOME shell 3.38: TypeError: meta is null)
Your message dated Sun, 25 Oct 2020 15:48:41 + with message-id and subject line Bug#971816: fixed in gnome-shell-timer 0.3.20+20190726-1 has caused the Debian Bug report #971816, regarding gnome-shell-timer: fails to load with GNOME shell 3.38: TypeError: meta is null 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.) -- 971816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-shell-timer Version: 0.3.20+20171025-4 Severity: serious Usertags: crash The GNOME shell timer extension fails to load with GNOME shell 3.38 and I see the following message in the systemd journal: Oct 03 12:18:06 gnome-shell[2523]: JS ERROR: Extension ti...@olebowle.gmx.com: TypeError: meta is null _patchContainerClass/containerClass.prototype.child_set@resource:///org/gnome/shell/ui/environment.js:43:13 _patchContainerClass/containerClass.prototype.add@resource:///org/gnome/shell/ui/environment.js:52:18 _init@/usr/share/gnome-shell/extensions/ti...@olebowle.gmx.com/extension.js:103:19 wrapper@resource:///org/gnome/gjs/modules/script/_legacy.js:82:27 enable@/usr/share/gnome-shell/extensions/ti...@olebowle.gmx.com/extension.js:418:17 _callExtensionEnable@resource:///org/gnome/shell/ui/extensionSystem.js:167:32 loadExtension@resource:///org/gnome/shell/ui/extensionSystem.js:348:26 _loadExtensions/<@resource:///org/gnome/shell/ui/extensionSystem.js:586:18 collectFromDatadirs@resource:///org/gnome/shell/misc/fileUtils.js:27:28 _loadExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:565:19 _enableAllExtensions@resource:///org/gnome/shell/ui/extensionSystem.js:595:18 _sessionUpdated@resource:///org/gnome/shell/ui/extensionSystem.js:626:18 init@resource:///org/gnome/shell/ui/extensionSystem.js:56:14 _initializeUI@resource:///org/gnome/shell/ui/main.js:269:22 start@resource:///org/gnome/shell/ui/main.js:159:5 @:1:47 -- System Information: Debian Release: bullseye/sid APT prefers testing-debug APT policy: (900, 'testing-debug'), (900, 'testing'), (800, 'unstable-debug'), (800, 'unstable'), (790, 'buildd-unstable'), (700, 'experimental-debug'), (700, 'experimental'), (690, 'buildd-experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.8.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=en_AU.utf8, LC_CTYPE=en_AU.utf8 (charmap=UTF-8), LANGUAGE=en_AU:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gnome-shell-timer depends on: ii dconf-gsettings-backend [gsettings-backend] 0.38.0-1 ii gnome-shell 3.38.0-2 ii python3 3.8.2-3 gnome-shell-timer recommends no packages. gnome-shell-timer suggests no packages. -- no debconf information -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part --- End Message --- --- Begin Message --- Source: gnome-shell-timer Source-Version: 0.3.20+20190726-1 Done: =?utf-8?q?Rapha=C3=ABl_Hertzog?= We believe that the bug you reported is fixed in the latest version of gnome-shell-timer, 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 971...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Raphaël Hertzog (supplier of updated gnome-shell-timer 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: SHA512 Format: 1.8 Date: Sun, 25
Bug#972871: git-el: .el files not installed / byte-compiled
Package: git-el
Version: 1:2.28.0-1
Severity: grave
Justification: renders package unusable
While updating my emacs configuration for 27.1 (now in unstable)
I noticed that /etc/emacs/site-start.d/50git-core.el prints
git removed but not purged, skipping setup
and does not autoload either git.el or git-blame.el. This appears to
be because /usr/lib/emacsen-common/packages/install/git does nothing
when $FLAVOR is “emacs”:
| # The emacs startup file looks for these files in
| # /usr/share/${debian-emacs-flavor}/site-lisp/git.
| # Installing to the generic /usr/share/emacs/site-list/git would be
| # pointless.
| [ "$FLAVOR" != emacs ] || exit 0
This has been incorrect for quite some time - I’m not sure how long
ago it was that (symbol-name debian-emacs-flavor) was changed to
evaluate to “emacs” for the ordinary packages of GNU Emacs, but
probably more than one release by now.
I think a sufficient fix is to remove the above quoted lines from
/usr/lib/emacsen-common/packages/install/git.
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.0-1-amd64 (SMP w/32 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages git-el depends on:
ii emacs1:27.1+1-2
ii emacs-gtk [emacsen] 1:27.1+1-2
ii git 1:2.28.0-1
Versions of packages git-el recommends:
ii elpa-magit 2.99.0.git0957.ge8c7bd03-1
git-el suggests no packages.
-- no debconf information
Bug#972870: Should libhal1-flash be shipped in bullseye?
Package: libhal1-flash Version: 0.3.3-3 Severity: serious Tags: bullseye sid This package was needed for older versions of Flash, which itself is both EOL before the release of bullseye and already no longer supported by any major browser.
Bug#972862: swi-prolog: FTBFS with OpenSSL 1.1.1h
Hi Kurt, Вс 25 окт 2020 @ 13:30 Kurt Roeckx : > Package: swi-prolog > Version: 8.2.1+dfsg-2 > Severity: serious > > Hi, > > swi-prolog fails to build using OpenSSL 1.1.1h. See > https://ci.debian.net/data/autopkgtest/testing/amd64/s/swi-prolog/7715788/log.gz > for a log. > > I've filed an upstream bug about this at: > https://github.com/SWI-Prolog/packages-ssl/issues/158 Thanks for your report and for submitting it upstream too. Cheers! Lev
Bug#972858: marked as done (zim FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/run/user/2952')
Your message dated Sun, 25 Oct 2020 14:38:19 +
with message-id
and subject line Bug#972858: fixed in zim 0.73.3-2
has caused the Debian Bug report #972858,
regarding zim FTBFS: FileNotFoundError: [Errno 2] No such file or directory:
'/run/user/2952'
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.)
--
972858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972858
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: zim
Version: 0.73.3-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=zim=all=0.73.3-1=1603610569=0
...
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.8 setup.py clean
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
(setup.py:32456): Gdk-CRITICAL **: 07:22:44.197: gdk_keymap_get_for_display:
assertion 'GDK_IS_DISPLAY (display)' failed
(setup.py:32456): Gdk-CRITICAL **: 07:22:44.197: gdk_keymap_get_modifier_mask:
assertion 'GDK_IS_KEYMAP (keymap)' failed
(setup.py:32456): Gdk-CRITICAL **: 07:22:44.197: gdk_keymap_get_for_display:
assertion 'GDK_IS_DISPLAY (display)' failed
(setup.py:32456): Gtk-CRITICAL **: 07:22:44.197:
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
Traceback (most recent call last):
File "/<>/zim/main/ipc.py", line 82, in
os.mkdir(runtime_dir, mode=0o700)
FileNotFoundError: [Errno 2] No such file or directory: '/run/user/2952'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "setup.py", line 25, in
import makeman # helper script
File "/<>/makeman.py", line 13, in
from zim.main import HelpCommand
File "/<>/zim/main/__init__.py", line 39, in
from .ipc import dispatch as _ipc_dispatch
File "/<>/zim/main/ipc.py", line 90, in
raise AssertionError('Either you are not the owner of "%s" or the
permissions are un-safe.\n'
AssertionError: Either you are not the owner of "/run/user/2952" or the
permissions are un-safe.
If you can not resolve this, try setting $XDG_RUNTIME_DIR or set $TMP to a
different location.
E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1:
python3.8 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.8 returned exit
code 13
make: *** [debian/rules:12: clean] Error 25
--- End Message ---
--- Begin Message ---
Source: zim
Source-Version: 0.73.3-2
Done: =?utf-8?q?Rapha=C3=ABl_Hertzog?=
We believe that the bug you reported is fixed in the latest version of
zim, 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 972...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Raphaël Hertzog (supplier of updated zim 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: SHA512
Format: 1.8
Date: Sun, 25 Oct 2020 14:59:08 +0100
Source: zim
Architecture: source
Version: 0.73.3-2
Distribution: unstable
Urgency: medium
Maintainer: Zim Package Maintainers
Changed-By: Raphaël Hertzog
Closes: 972858
Changes:
zim (0.73.3-2) unstable; urgency=medium
.
* Override XDG_RUNTIME_DIR to an existing path (Closes: #972858)
Checksums-Sha1:
18a1f9dcb78a93573556a30dce395fe351b8867e 1580 zim_0.73.3-2.dsc
c9e7e670ada1d57053a1092f55d689d5b649cc1b 10032 zim_0.73.3-2.debian.tar.xz
a88fb8b77bcbe742d7e2fba06f9fc7a63ba8d299 10280 zim_0.73.3-2_source.buildinfo
Checksums-Sha256:
626e4ffe71492efe8e1637a19c9cea85a232bd075e8eb23ae11265fa2dd56256 1580
zim_0.73.3-2.dsc
aec23e882bbefa1bc1bf36a51a9121e02653da7b896f79db16441d6487ae74e5 10032
zim_0.73.3-2.debian.tar.xz
de125c3f5be87376db5eb0f400dbf67ad3b39b4ebaf8daadfd6427cdc1a8fd33 10280
zim_0.73.3-2_source.buildinfo
Files:
07c7ee3eff66a9192941c4b9e9f60eca 1580 x11 optional zim_0.73.3-2.dsc
950dfe66e4b05a73a1ee5d58266ec104 10032 x11 optional zim_0.73.3-2.debian.tar.xz
5c38008b71c7df7231b2d6705cc4c020 10280 x11 optional
zim_0.73.3-2_source.buildinfo
-BEGIN PGP SIGNATURE-
Comment: Signed by Raphael Hertzog
iQEzBAEBCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAl+VhfUACgkQA4gdq+vC
mrmC4wf/TtQ45/1L1sfbSMLAiA53dMgCgRhuNSKFhdcJSi30c3EBO7dFJgUF9nsQ
Bug#972867: gdcm: FTBFS in testing and unstable
Source: gdcm Version: 3.0.7-3 Severity: serious Tags: ftbfs bullseye sid Hi Maintainer As per reproducible builds [1], gdcm recently started failing to build in testing and unstable. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/gdcm.html /usr/bin/c++ -DgdcmMSFF_EXPORTS -I../Source/Common -ISource/Common -I../Source/DataStructureAndEncodingDefinition -I../Source/DataDictionary -I../Source/InformationObjectDefinition -I../Source/MediaStorageAndFileFormat -I../Utilities -IUtilities -I/usr/include/openjpeg-2.3 -I/usr/include/json-c -I/usr/include/json -g -O2 -ffile-prefix-map=/build/1st/gdcm-3.0.7=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DCHARLS_DLL -MD -MT Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEGLSCodec.cxx.o -MF Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEGLSCodec.cxx.o.d -o Source/MediaStorageAndFileFormat/CMakeFiles/gdcmMSFF.dir/gdcmJPEGLSCodec.cxx.o -c ../Source/MediaStorageAndFileFormat/gdcmJPEGLSCodec.cxx In file included from ../Source/MediaStorageAndFileFormat/gdcmJPEGLSCodec.cxx:24: ../Utilities/gdcm_charls.h:21:11: fatal error: CharLS/charls.h: No such file or directory 21 | # include | ^ compilation terminated.
Bug#972163: Rising severities
Hi! El dom., 25 oct. 2020 11:07, Sylvestre Ledru escribió: > Hello, > > Le 25/10/2020 à 14:57, Lisandro Damián Nicanor Pérez Meyer a écrit : > > severity 972163 serious > > severity 972166 serious > > block 972176 by 972163 > > block 972176 by 972166 > > thanks > > > > Hi! We are close to begin the Qt transition that will remove > > qt5-default, so I'm raising the severities. If everything goes well > > I'll be NMUing your package today with an upload to delayed/5. Of > > course feel free to ping me if needed. > > > > Thanks, Lisandro. > > > I tried to upload it with your fix but the build failed for me. > > If it works for you, please upload (without delay) > > many thanks > Great, I'll check the build then! Thanks to you too! >
Bug#972858: marked as pending in zim
Control: tag -1 pending Hello, Bug #972858 in zim reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/zim/-/commit/add9be012d00c3ccdc91d40354a29e4b2352ee2a Override XDG_RUNTIME_DIR to an existing path The value of that variable is not reliable on build daemons: see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842565 Closes: #972858 (this message was generated automatically) -- Greetings https://bugs.debian.org/972858
Bug#972163: Rising severities
Hello, Le 25/10/2020 à 14:57, Lisandro Damián Nicanor Pérez Meyer a écrit : severity 972163 serious severity 972166 serious block 972176 by 972163 block 972176 by 972166 thanks Hi! We are close to begin the Qt transition that will remove qt5-default, so I'm raising the severities. If everything goes well I'll be NMUing your package today with an upload to delayed/5. Of course feel free to ping me if needed. Thanks, Lisandro. I tried to upload it with your fix but the build failed for me. If it works for you, please upload (without delay) many thanks S
Processed: Bug#972858 marked as pending in zim
Processing control commands: > tag -1 pending Bug #972858 [src:zim] zim FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/run/user/2952' Added tag(s) pending. -- 972858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972858 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Rising severities
Processing commands for cont...@bugs.debian.org: > severity 972163 serious Bug #972163 [src:fwbuilder] fwbuilder: Depends on package qt5-default which is about to be removed Severity set to 'serious' from 'important' > severity 972166 serious Bug #972166 [src:odin] odin: Depends on package qt5-default which is about to be removed Severity set to 'serious' from 'important' > block 972176 by 972163 Bug #972176 [src:shotcut] shotcut: FTBFS with Qt 5.15: error: aggregate 'QPainterPath histPath' has incomplete type and cannot be defined 972176 was not blocked by any bugs. 972176 was blocking: 972278 Added blocking bug(s) of 972176: 972163 > block 972176 by 972166 Bug #972176 [src:shotcut] shotcut: FTBFS with Qt 5.15: error: aggregate 'QPainterPath histPath' has incomplete type and cannot be defined 972176 was blocked by: 972163 972176 was blocking: 972278 Added blocking bug(s) of 972176: 972166 > thanks Stopping processing here. Please contact me if you need assistance. -- 972163: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972163 972166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972166 972176: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972176 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: unarchiving 921704, reopening 921704, unarchiving 922565, reopening 922565, block 921704 with 922565
Processing commands for cont...@bugs.debian.org:
> unarchive 921704
Bug #921704 {Done: Andreas Beckmann } [src:tortoisehg]
tortoisehg: uninstallable with mercurial 4.9
Unarchived Bug 921704
> reopen 921704
Bug #921704 {Done: Andreas Beckmann } [src:tortoisehg]
tortoisehg: uninstallable with mercurial 4.9
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4.8.1-0.1+rm.
> unarchive 922565
Bug #922565 {Done: Andreas Beckmann } [wnpp] ITA: tortoisehg
-- Graphical tool for working with Mercurial
Unarchived Bug 922565
> reopen 922565
Bug #922565 {Done: Andreas Beckmann } [wnpp] ITA: tortoisehg
-- Graphical tool for working with Mercurial
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 4.8.1-0.1+rm.
> block 921704 with 922565
Bug #921704 [src:tortoisehg] tortoisehg: uninstallable with mercurial 4.9
921704 was not blocked by any bugs.
921704 was not blocking any bugs.
Added blocking bug(s) of 921704: 922565
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921704
922565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#934747: Info received ()
در تاریخ یکشنبه ۲۵ اکتبر ۲۰۲۰، ۱۵:۵۷ Debian Bug Tracking System < ow...@bugs.debian.org> نوشت: > Thank you for the additional information you have supplied regarding > this Bug report. > > This is an automatically generated reply to let you know your message > has been received. > > Your message is being forwarded to the package maintainers and other > interested parties for their attention; they will reply in due course. > > Your message has been sent to the package maintainer(s): > Alessandro Ghedini > > If you wish to submit further information on this problem, please > send it to 934...@bugs.debian.org. > > Please do not send mail to ow...@bugs.debian.org unless you wish > to report a problem with the Bug-tracking system. > > -- > 934747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934747 > Debian Bug Tracking System > Contact ow...@bugs.debian.org with problems >
Bug#972862: swi-prolog: FTBFS with OpenSSL 1.1.1h
Package: swi-prolog Version: 8.2.1+dfsg-2 Severity: serious Hi, swi-prolog fails to build using OpenSSL 1.1.1h. See https://ci.debian.net/data/autopkgtest/testing/amd64/s/swi-prolog/7715788/log.gz for a log. I've filed an upstream bug about this at: https://github.com/SWI-Prolog/packages-ssl/issues/158 Kurt
Bug#934747:
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 972808 https://github.com/Ultimaker/CuraEngine/issues/1318 Bug #972808 [src:cura-engine] cura-engine FTBFS: error: ‘find_if’ is not a member of ‘std’ Set Bug forwarded-to-address to 'https://github.com/Ultimaker/CuraEngine/issues/1318'. > thanks Stopping processing here. Please contact me if you need assistance. -- 972808: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972808 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972808: [3dprinter-general] Bug#972808: cura-engine FTBFS: error: ‘find_if’ is not a member of ‘std’
> A native build of cura-engine on unstable amd64 ends with:
>
> | In file included from /usr/include/gtest/gtest.h:387,
> | from /<>/tests/utils/SparseGridTest.cpp:4:
> | /<>/tests/utils/SparseGridTest.cpp: In member function
> ‘virtual void cura::GetNearbyTest_GetNearby_Test::TestBody()’:
> | /<>/tests/utils/SparseGridTest.cpp:48:38: error: ‘find_if’ is
> not a member of ‘std’; did you mean ‘find’?
> |48 | EXPECT_NE(result.end(), std::find_if(result.begin(),
> result.end(), [](const typename SparsePointGridInclusive::Elem
> ) { return elem.val == point; }))
> | | ^~~
This has been fixed upstream:
https://github.com/Ultimaker/CuraEngine/issues/1318
> This must be a very recent issue as neither crossqa (10 days ago) nor
> reproducible builds (6 days ago) have run into this issue. It's reliably
> reproducible anyhow. I'm unsure what might cause it. Neither gcc-10 nor
> cura-engine were uploaded in that time. It would be a good idea to add
> the missing #include any how.
Not sure, perhaps it was a change in one of the dependent libraries
(such as gtest).
Anyway, the fix should be in the next CuraEngine release (4.8), but we
can adopt the trivial patch from here in the meantime:
https://github.com/Ultimaker/CuraEngine/commit/ae354d80b25d90576f37222b6500f0e7ac45405b
Bug#970606: [Openjdk] Bug#970606: Bug#970606: Bug#970606: Bug#970606: src:openjdk-*: autopkgtest times out on Debian/Ubuntu infrastructure
On 10/25/20 12:22 PM, Matthias Klose wrote: > On 10/24/20 10:18 PM, Paul Gevers wrote: >> Hi Matthias >> >> On 23-10-2020 13:31, Matthias Klose wrote: >>> On 10/7/20 10:33 PM, Paul Gevers wrote: Hi Matthias, On 21-09-2020 17:52, Paul Gevers wrote: >> Apparently >> the very same tests don't time out on the buildds. > > I don't know what timeouts apply to buildds, but indeed I think they are > much higher to cope with *building* some extremely big packages. Do you know how much time these tests would take? If so, I wonder if we should make it possible for individual packages to have a longer timeout. It would be work on the debci/ci.d.n side of things, but not impossible of course. >>> >>> For an upper bound, use the build time: The very same tests are run during >>> the >>> build. >> >> Ack. Side note: I see a hell load of errors and failures in the build >> log, is that expected? And some builds took more than a day, is that >> reasonable to do for these tests (if they're ignored anyways, your tests >> are marked flaky)? >> >>> The other question is, if it's sensible to run the upstream test suite as an >>> autopkg test, if it's already run during the build. Ideally it should only >>> run >>> the autopkg tests which test on integration issues with run time >>> dependencies, >>> but this would require analyzing some 1 tests and >>> >>> For now I just disabled the jdk tests as an autopkg test. So please clear >>> the >>> test results, to run it again, and let it migrate. >> >> Also the hotpot test times out, so only having the jdk tests disabled >> doesn't really help at this stage. > > where can I see this? > https://ci.debian.net/data/autopkgtest/testing/amd64/o/openjdk-15/7738063/log.gz > doesn't point to anywhere instead I see https://ci.debian.net/data/autopkgtest/unstable/amd64/o/openjdk-15/7725394/log.gz which doesn't look like a timeout. > and it doesn't really help to not let openjdk-15 migrate, so that we finally > can > remove openjdk-14.
Bug#970606: [Openjdk] Bug#970606: Bug#970606: Bug#970606: src:openjdk-*: autopkgtest times out on Debian/Ubuntu infrastructure
On 10/24/20 10:18 PM, Paul Gevers wrote: > Hi Matthias > > On 23-10-2020 13:31, Matthias Klose wrote: >> On 10/7/20 10:33 PM, Paul Gevers wrote: >>> Hi Matthias, >>> >>> On 21-09-2020 17:52, Paul Gevers wrote: > Apparently > the very same tests don't time out on the buildds. I don't know what timeouts apply to buildds, but indeed I think they are much higher to cope with *building* some extremely big packages. >>> >>> Do you know how much time these tests would take? If so, I wonder if we >>> should make it possible for individual packages to have a longer >>> timeout. It would be work on the debci/ci.d.n side of things, but not >>> impossible of course. >> >> For an upper bound, use the build time: The very same tests are run during >> the >> build. > > Ack. Side note: I see a hell load of errors and failures in the build > log, is that expected? And some builds took more than a day, is that > reasonable to do for these tests (if they're ignored anyways, your tests > are marked flaky)? > >> The other question is, if it's sensible to run the upstream test suite as an >> autopkg test, if it's already run during the build. Ideally it should only >> run >> the autopkg tests which test on integration issues with run time >> dependencies, >> but this would require analyzing some 1 tests and >> >> For now I just disabled the jdk tests as an autopkg test. So please clear the >> test results, to run it again, and let it migrate. > > Also the hotpot test times out, so only having the jdk tests disabled > doesn't really help at this stage. where can I see this? https://ci.debian.net/data/autopkgtest/testing/amd64/o/openjdk-15/7738063/log.gz doesn't point to anywhere and it doesn't really help to not let openjdk-15 migrate, so that we finally can remove openjdk-14. Matthias
Processed: Re: Bug#972177: zeal: FTBFS with Qt 5.15: error: aggregate 'QPainterPath path' has incomplete type and cannot be defined
Processing control commands: > tags -1 + pending Bug #972177 [src:zeal] zeal: FTBFS with Qt 5.15: error: aggregate 'QPainterPath path' has incomplete type and cannot be defined Added tag(s) pending. -- 972177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972177: zeal: FTBFS with Qt 5.15: error: aggregate 'QPainterPath path' has incomplete type and cannot be defined
Control: tags -1 + pending On Tue, Oct 13, 2020 at 08:44:41PM +0300, Dmitry Shachnev wrote: > Dear Maintainer, > > zeal fails to build with Qt 5.15, currently available in experimental: > > /build/zeal-0.6.1/src/libs/ui/searchitemdelegate.cpp: In member function > 'virtual void Zeal::WidgetUi::SearchItemDelegate::paint(QPainter*, const > QStyleOptionViewItem&, const QModelIndex&) const': > [...] > /build/zeal-0.6.1/src/libs/ui/searchitemdelegate.cpp:143:26: error: > aggregate 'QPainterPath path' has incomplete type and cannot be defined > 143 | QPainterPath path; > | ^~~~ > > The full build log is attached. I have just uploaded the NMU fixing this to DELAYED/5. The debdiff is attached, and I have also pushed the change to salsa. -- Dmitry Shachnev diff -Nru zeal-0.6.1/debian/changelog zeal-0.6.1/debian/changelog --- zeal-0.6.1/debian/changelog 2018-10-31 09:44:09.0 +0300 +++ zeal-0.6.1/debian/changelog 2020-10-25 13:29:32.0 +0300 @@ -1,3 +1,10 @@ +zeal (1:0.6.1-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Backport upstream patch to fix build with Qt 5.15 (closes: #972177). + + -- Dmitry Shachnev Sun, 25 Oct 2020 13:29:32 +0300 + zeal (1:0.6.1-1) unstable; urgency=medium * New upstream release. diff -Nru zeal-0.6.1/debian/patches/0002-Fix-compilation-error-with-Qt-5.15.patch zeal-0.6.1/debian/patches/0002-Fix-compilation-error-with-Qt-5.15.patch --- zeal-0.6.1/debian/patches/0002-Fix-compilation-error-with-Qt-5.15.patch 1970-01-01 03:00:00.0 +0300 +++ zeal-0.6.1/debian/patches/0002-Fix-compilation-error-with-Qt-5.15.patch 2020-10-25 13:29:32.0 +0300 @@ -0,0 +1,21 @@ +From: Dmitry Atamanov +Date: Sun, 26 Apr 2020 02:26:53 +0500 +Subject: fix(ui): fix compilation error with Qt 5.15 (#1218) + +(cherry picked from commit 064aaa05d6a3ba4ba3cf648199a3109aba2f41fe) +--- + src/libs/ui/searchitemdelegate.cpp | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/src/libs/ui/searchitemdelegate.cpp b/src/libs/ui/searchitemdelegate.cpp +index 4bd6d0a..d8ad79b 100644 +--- a/src/libs/ui/searchitemdelegate.cpp b/src/libs/ui/searchitemdelegate.cpp +@@ -27,6 +27,7 @@ + #include + #include + #include ++#include + #include + + using namespace Zeal::WidgetUi; diff -Nru zeal-0.6.1/debian/patches/series zeal-0.6.1/debian/patches/series --- zeal-0.6.1/debian/patches/series 2018-10-12 13:20:53.0 +0300 +++ zeal-0.6.1/debian/patches/series 2020-10-25 13:29:32.0 +0300 @@ -1 +1,2 @@ 0001-Disable-ad-by-default.patch +0002-Fix-compilation-error-with-Qt-5.15.patch signature.asc Description: PGP signature
Bug#971114: marked as done (wordgrinder: FTBFS: src/c/arch/unix/cursesw/dpy.c:219:8: error: ‘KEY_EVENT’ undeclared (first use in this function); did you mean ‘KEY_SLEFT’?)
Your message dated Sun, 25 Oct 2020 10:39:34 + with message-id and subject line Bug#971114: fixed in wordgrinder 0.8-1 has caused the Debian Bug report #971114, regarding wordgrinder: FTBFS: src/c/arch/unix/cursesw/dpy.c:219:8: error: ‘KEY_EVENT’ undeclared (first use in this function); did you mean ‘KEY_SLEFT’? 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.) -- 971114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: wordgrinder Version: 0.7.2-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200926 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -MMD -MF .obj/lua-5.3-curses-release/src/c/arch/unix/cursesw/dpy.o.d > -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -g > -DVERSION='"0.7.2"' -DFILEFORMAT=7 -DNOUNCRYPT -DNOCRYPT -Isrc/c -Wall > -Wno-unused-function -ffunction-sections -fdata-sections > -Werror=implicit-function-declaration --std=gnu99 -D_DEFAULT_SOURCE > -D_XOPEN_SOURCE=600 -Os -I/usr/include/lua5.3 -I/usr/include/lua5.3 > -DARCH='"unix"' -D_XOPEN_SOURCE_EXTENDED -D_XOPEN_SOURCE -D_GNU_SOURCE > -I/usr/include/minizip -c src/c/arch/unix/cursesw/dpy.c -o > .obj/lua-5.3-curses-release/src/c/arch/unix/cursesw/dpy.o > : warning: "_XOPEN_SOURCE" redefined > : note: this is the location of the previous definition > src/c/arch/unix/cursesw/dpy.c: In function ‘dpy_getkeyname’: > src/c/arch/unix/cursesw/dpy.c:219:8: error: ‘KEY_EVENT’ undeclared (first use > in this function); did you mean ‘KEY_SLEFT’? > 219 | case KEY_EVENT: return "KEY_EVENT"; > |^ > |KEY_SLEFT > src/c/arch/unix/cursesw/dpy.c:219:8: note: each undeclared identifier is > reported only once for each function it appears in > [14/82] cc -MMD -MF .obj/lua-5.3-curses-release/src/c/main.o.d -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -g > -DVERSION='"0.7.2"' -DFILEFORMAT=7 -DNOUNCRYPT -DNOCRYPT -Isrc/c -Wall > -Wno-unused-function -ffunction-sections -fdata-sections > -Werror=implicit-function-declaration --std=gnu99 -D_DEFAULT_SOURCE > -D_XOPEN_SOURCE=600 -Os -I/usr/include/lua5.3 -I/usr/include/lua5.3 > -DARCH='"unix"' -D_XOPEN_SOURCE_EXTENDED -D_XOPEN_SOURCE -D_GNU_SOURCE > -I/usr/include/minizip -c src/c/main.c -o > .obj/lua-5.3-curses-release/src/c/main.o > : warning: "_XOPEN_SOURCE" redefined > : note: this is the location of the previous definition > [15/82] cc -MMD -MF .obj/lua-5.3-curses-release/src/c/lua.o.d -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -g > -DVERSION='"0.7.2"' -DFILEFORMAT=7 -DNOUNCRYPT -DNOCRYPT -Isrc/c -Wall > -Wno-unused-function -ffunction-sections -fdata-sections > -Werror=implicit-function-declaration --std=gnu99 -D_DEFAULT_SOURCE > -D_XOPEN_SOURCE=600 -Os -I/usr/include/lua5.3 -I/usr/include/lua5.3 > -DARCH='"unix"' -D_XOPEN_SOURCE_EXTENDED -D_XOPEN_SOURCE -D_GNU_SOURCE > -I/usr/include/minizip -c src/c/lua.c -o > .obj/lua-5.3-curses-release/src/c/lua.o > : warning: "_XOPEN_SOURCE" redefined > : note: this is the location of the previous definition > [16/82] cc -MMD -MF .obj/lua-5.3-curses-release/src/c/screen.o.d -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -g > -DVERSION='"0.7.2"' -DFILEFORMAT=7 -DNOUNCRYPT -DNOCRYPT -Isrc/c -Wall > -Wno-unused-function -ffunction-sections -fdata-sections > -Werror=implicit-function-declaration --std=gnu99 -D_DEFAULT_SOURCE > -D_XOPEN_SOURCE=600 -Os -I/usr/include/lua5.3 -I/usr/include/lua5.3 > -DARCH='"unix"' -D_XOPEN_SOURCE_EXTENDED -D_XOPEN_SOURCE -D_GNU_SOURCE > -I/usr/include/minizip -c src/c/screen.c -o > .obj/lua-5.3-curses-release/src/c/screen.o > : warning: "_XOPEN_SOURCE" redefined > : note: this is the location of the previous definition > [17/82] cc -MMD -MF .obj/lua-5.3-x11-release/.obj/luascripts.o.d -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -g > -DVERSION='"0.7.2"' -DFILEFORMAT=7 -DNOUNCRYPT -DNOCRYPT -Isrc/c -Wall > -Wno-unused-function -ffunction-sections -fdata-sections > -Werror=implicit-function-declaration --std=gnu99 -I/usr/include/freetype2 >
Processed: Re: Bug#972676: dde-qt5integration: FTBFS with Qt 5.15: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined
Processing control commands: > tags -1 + pending Bug #972676 [src:dde-qt5integration] dde-qt5integration: FTBFS with Qt 5.15: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined Added tag(s) pending. -- 972676: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972676 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972676: dde-qt5integration: FTBFS with Qt 5.15: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined
Control: tags -1 + pending
On Thu, Oct 22, 2020 at 01:55:09PM +0300, Dmitry Shachnev wrote:
> Dear Maintainer,
>
> dde-qt5integration fails to build with Qt 5.15, currently available in
> experimental.
>
> After rebuilding dde-qt-dbus-factory, dtkcore and libqtxdg, and building a
> fixed version of dtkwidget (see #972155), I get this error:
>
> pushbuttonhelper.cpp: In member function ‘bool
> dstyle::Style::drawPushButtonFrame(QPainter*, const QRect&, const QBrush&,
> const QBrush&, const QColor&, const QWidget*) const’:
> pushbuttonhelper.cpp:221:18: error: aggregate ‘QPainterPath path’ has
> incomplete type and cannot be defined
> 221 | QPainterPath path;
> | ^~~~
> pushbuttonhelper.cpp:231:26: error: aggregate ‘QPainterPath rightHalf’ has
> incomplete type and cannot be defined
> 231 | QPainterPath rightHalf;
> | ^
> pushbuttonhelper.cpp:235:26: error: aggregate ‘QPainterPath leftHalf’ has
> incomplete type and cannot be defined
> 235 | QPainterPath leftHalf;
> | ^~~~
>
> This is fixed upstream, see the linked pull request.
I have just uploaded the NMU fixing this to DELAYED/5.
The debdiff is attached.
This change is also available in qt-5.15 branch on my fork on salsa:
https://salsa.debian.org/mitya57/dde-qt5integration/-/commits/qt-5.15
(I couldn't make a merge request because there is no branch for unstable
version.)
--
Dmitry Shachnev
diff -Nru dde-qt5integration-5.0.0/debian/changelog dde-qt5integration-5.0.0/debian/changelog
--- dde-qt5integration-5.0.0/debian/changelog 2020-06-06 18:27:34.0 +0300
+++ dde-qt5integration-5.0.0/debian/changelog 2020-10-25 13:21:15.0 +0300
@@ -1,3 +1,10 @@
+dde-qt5integration (5.0.0-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Backport upstream patch to fix build with Qt 5.15 (closes: #972676).
+
+ -- Dmitry Shachnev Sun, 25 Oct 2020 13:21:15 +0300
+
dde-qt5integration (5.0.0-2) unstable; urgency=medium
[ Dmitry Shachnev ]
diff -Nru dde-qt5integration-5.0.0/debian/patches/qt-5.15.patch dde-qt5integration-5.0.0/debian/patches/qt-5.15.patch
--- dde-qt5integration-5.0.0/debian/patches/qt-5.15.patch 1970-01-01 03:00:00.0 +0300
+++ dde-qt5integration-5.0.0/debian/patches/qt-5.15.patch 2020-10-25 13:21:15.0 +0300
@@ -0,0 +1,60 @@
+From: Felix Yan
+Date: Thu, 11 Jun 2020 16:19:53 +0800
+Subject: Fix build failures under Qt 5.15+
+
+(cherry picked from commit 5d2fbe972f495ec5ddadf9062612e042cf0ea07a)
+---
+ dstyleplugin/painterhelper.cpp| 1 +
+ dstyleplugin/pushbuttonhelper.cpp | 1 +
+ dstyleplugin/tabbarhelper.cpp | 1 +
+ dstyleplugin/tabwidgethelper.cpp | 1 +
+ 4 files changed, 4 insertions(+)
+
+diff --git a/dstyleplugin/painterhelper.cpp b/dstyleplugin/painterhelper.cpp
+index 3db216d..66d548f 100644
+--- a/dstyleplugin/painterhelper.cpp
b/dstyleplugin/painterhelper.cpp
+@@ -18,6 +18,7 @@
+ #include "painterhelper.h"
+
+ #include
++#include
+ #include
+
+ namespace dstyle {
+diff --git a/dstyleplugin/pushbuttonhelper.cpp b/dstyleplugin/pushbuttonhelper.cpp
+index 8069070..168b009 100644
+--- a/dstyleplugin/pushbuttonhelper.cpp
b/dstyleplugin/pushbuttonhelper.cpp
+@@ -30,6 +30,7 @@
+
+ #include
+ #include
++#include
+
+ DWIDGET_USE_NAMESPACE
+
+diff --git a/dstyleplugin/tabbarhelper.cpp b/dstyleplugin/tabbarhelper.cpp
+index 51f677b..e0ef36c 100644
+--- a/dstyleplugin/tabbarhelper.cpp
b/dstyleplugin/tabbarhelper.cpp
+@@ -33,6 +33,7 @@ DWIDGET_USE_NAMESPACE
+ #include
+ #include
+ #include
++#include
+ #include
+ #include
+ #include
+diff --git a/dstyleplugin/tabwidgethelper.cpp b/dstyleplugin/tabwidgethelper.cpp
+index a2b6756..f51d43d 100644
+--- a/dstyleplugin/tabwidgethelper.cpp
b/dstyleplugin/tabwidgethelper.cpp
+@@ -20,6 +20,7 @@
+ #include "painterhelper.h"
+
+ #include
++#include
+ #include
+ #include
+
diff -Nru dde-qt5integration-5.0.0/debian/patches/series dde-qt5integration-5.0.0/debian/patches/series
--- dde-qt5integration-5.0.0/debian/patches/series 2020-06-06 18:27:34.0 +0300
+++ dde-qt5integration-5.0.0/debian/patches/series 2020-10-25 13:21:15.0 +0300
@@ -1 +1,2 @@
qt-5.14.patch
+qt-5.15.patch
signature.asc
Description: PGP signature
Processed: Re: Bug#972556: ffmpeg: Fails to build from source with newer src:srt
Processing control commands: > severity -1 wishlist Bug #972556 [src:ffmpeg] ffmpeg: Fails to build from source with newer src:srt Severity set to 'wishlist' from 'serious' > retitle -1 ffmpeg: re-enable support for libsrt Bug #972556 [src:ffmpeg] ffmpeg: Fails to build from source with newer src:srt Changed Bug title to 'ffmpeg: re-enable support for libsrt' from 'ffmpeg: Fails to build from source with newer src:srt'. -- 972556: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972556 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972556: ffmpeg: Fails to build from source with newer src:srt
Control: severity -1 wishlist Control: retitle -1 ffmpeg: re-enable support for libsrt On 2020-10-20 12:05:10 +0200, Sebastian Ramacher wrote: > Control: block -1 by 971754 > > On 2020-10-20 11:42:47, John Paul Adrian Glaubitz wrote: > > Control: tags -1 +patch > > > > Hello! > > > > This FTBFS is fixed by the following upstream patch [1]: > > > > From: Jun Zhao > > Date: Sun, 12 Jul 2020 05:48:48 + (+0800) > > Subject: lavf/srt: fix build fail when used the libsrt 1.4.1 > > X-Git-Url: > > http://git.ffmpeg.org/gitweb/ffmpeg.git/commitdiff_plain/7c59e1b0f285cd7c7b35fcd71f49c5fd52cf9315 > > > > lavf/srt: fix build fail when used the libsrt 1.4.1 > > > > libsrt changed the: > > SRTO_SMOOTHER -> SRTO_CONGESTION > > SRTO_STRICTENC -> SRTO_ENFORCEDENCRYPTION > > and removed the front of deprecated options (SRTO_SMOOTHER/SRTO_STRICTENC) > > in the header, it's lead to build fail > > > > fix #8760 > > > > Signed-off-by: Jun Zhao > > FWIW, srt broke its ABI (see the blocking bug). Unless this situation is > sorted out soon, we'd have a ffmpeg that is stuck in unstable. So I'd > consider dropping srt support until the srt situation has been fixed. I have now temporarily disabled support for libsrt. Once libsrt gets unbroken, it can be renabled again. Cheers > > > So, this patch and the patch from #968574 would be great! > > Has the patch from #968574 been merged upstream in the meantime? > > Cheers > > > > > Thanks, > > Adrian > > > > > [1] > > > https://git.ffmpeg.org/gitweb/ffmpeg.git/commitdiff/7c59e1b0f285cd7c7b35fcd71f49c5fd52cf9315 > > > > -- > > .''`. John Paul Adrian Glaubitz > > : :' : Debian Developer - glaub...@debian.org > > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 > > > > -- > Sebastian Ramacher > -- Sebastian Ramacher signature.asc Description: PGP signature
Bug#972859: libsejda-java FTBFS: cannot find symbol
Source: libsejda-java Version: 4.1.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=libsejda-java=all=4.1.1-1=1603575235=0 ... [INFO] [INFO] Reactor Summary for sejda 4.1.1: [INFO] [INFO] sejda .. SUCCESS [ 0.007 s] [INFO] sejda model SUCCESS [ 3.005 s] [INFO] sejda core . SUCCESS [ 0.385 s] [INFO] sejda fonts SUCCESS [ 0.211 s] [INFO] sejda image writers SUCCESS [ 0.234 s] [INFO] sejda sambox ... FAILURE [ 0.927 s] [INFO] sejda conversion ... SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 4.949 s [INFO] Finished at: 2020-10-24T21:33:50Z [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sejda-sambox: Compilation failure: Compilation failure: [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PDDocumentHandler.java:[258,48] cannot find symbol [ERROR] symbol: variable ASYNC_BODY_WRITE [ERROR] location: class org.sejda.sambox.output.WriteOption [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PDDocumentHandler.java:[301,17] cannot find symbol [ERROR] symbol: method sanitizeDictionary() [ERROR] location: variable imported of type org.sejda.sambox.pdmodel.PDPage [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/split/PageCopier.java:[101,13] cannot find symbol [ERROR] symbol: method sanitizeDictionary() [ERROR] location: variable copy of type org.sejda.sambox.pdmodel.PDPage [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[131,34] cannot find symbol [ERROR] symbol: method createFromSeekableSource(org.sejda.io.SeekableSource,java.lang.String) [ERROR] location: class org.sejda.sambox.pdmodel.graphics.image.PDImageXObject [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[136,38] cannot find symbol [ERROR] symbol: method createFromSeekableSource(org.sejda.io.SeekableSource,java.lang.String) [ERROR] location: class org.sejda.sambox.pdmodel.graphics.image.PDImageXObject [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[140,42] cannot find symbol [ERROR] symbol: method createFromSeekableSource(org.sejda.io.SeekableSource,java.lang.String) [ERROR] location: class org.sejda.sambox.pdmodel.graphics.image.PDImageXObject [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[157,52] incompatible types: org.sejda.io.SeekableSource cannot be converted to java.io.File [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[164,50] cannot find symbol [ERROR] symbol: method asNewInputStream() [ERROR] location: variable source of type org.sejda.io.SeekableSource [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[191,82] cannot find symbol [ERROR] symbol: method asNewInputStream() [ERROR] location: variable source of type org.sejda.io.SeekableSource [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/PageImageWriter.java:[237,82] cannot find symbol [ERROR] symbol: method asNewInputStream() [ERROR] location: variable source of type org.sejda.io.SeekableSource [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/SetMetadataTask.java:[79,50] cannot find symbol [ERROR] symbol: class OnBeforeWrite [ERROR] location: class org.sejda.sambox.pdmodel.PDDocument [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/SetMetadataTask.java:[80,13] method does not override or implement a method from a supertype [ERROR] /<>/sejda-sambox/src/main/java/org/sejda/impl/sambox/component/image/ExifHelper.java:[41,110] cannot find symbol [ERROR] symbol: method asNewInputStream() [ERROR] location: interface org.sejda.io.SeekableSource [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn -rf :sejda-sambox
Bug#972858: zim FTBFS: FileNotFoundError: [Errno 2] No such file or directory: '/run/user/2952'
Source: zim
Version: 0.73.3-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=zim=all=0.73.3-1=1603610569=0
...
dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.8 setup.py clean
Unable to init server: Could not connect: Connection refused
Unable to init server: Could not connect: Connection refused
(setup.py:32456): Gdk-CRITICAL **: 07:22:44.197: gdk_keymap_get_for_display:
assertion 'GDK_IS_DISPLAY (display)' failed
(setup.py:32456): Gdk-CRITICAL **: 07:22:44.197: gdk_keymap_get_modifier_mask:
assertion 'GDK_IS_KEYMAP (keymap)' failed
(setup.py:32456): Gdk-CRITICAL **: 07:22:44.197: gdk_keymap_get_for_display:
assertion 'GDK_IS_DISPLAY (display)' failed
(setup.py:32456): Gtk-CRITICAL **: 07:22:44.197:
_gtk_replace_virtual_modifiers: assertion 'GDK_IS_KEYMAP (keymap)' failed
Traceback (most recent call last):
File "/<>/zim/main/ipc.py", line 82, in
os.mkdir(runtime_dir, mode=0o700)
FileNotFoundError: [Errno 2] No such file or directory: '/run/user/2952'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "setup.py", line 25, in
import makeman # helper script
File "/<>/makeman.py", line 13, in
from zim.main import HelpCommand
File "/<>/zim/main/__init__.py", line 39, in
from .ipc import dispatch as _ipc_dispatch
File "/<>/zim/main/ipc.py", line 90, in
raise AssertionError('Either you are not the owner of "%s" or the
permissions are un-safe.\n'
AssertionError: Either you are not the owner of "/run/user/2952" or the
permissions are un-safe.
If you can not resolve this, try setting $XDG_RUNTIME_DIR or set $TMP to a
different location.
E: pybuild pybuild:352: clean: plugin distutils failed with: exit code=1:
python3.8 setup.py clean
dh_auto_clean: error: pybuild --clean -i python{version} -p 3.8 returned exit
code 13
make: *** [debian/rules:12: clean] Error 25
Processed: severity of 938492 is serious
Processing commands for cont...@bugs.debian.org: > severity 938492 serious Bug #938492 [src:six] six: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 938492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 938443 is serious
Processing commands for cont...@bugs.debian.org: > severity 938443 serious Bug #938443 [src:scid] scid: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 938443: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938443 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 938198 is serious
Processing commands for cont...@bugs.debian.org: > severity 938198 serious Bug #938198 [src:python-stdlib-extensions] python-stdlib-extensions: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 938198: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938198 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 936268 is serious
Processing commands for cont...@bugs.debian.org: > severity 936268 serious Bug #936268 [src:caldav-tester] caldav-tester: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 936268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 936809 is serious
Processing commands for cont...@bugs.debian.org: > severity 936809 serious Bug #936809 [src:kross-interpreters] kross-interpreters: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 936809: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 937996 is serious
Processing commands for cont...@bugs.debian.org: > severity 937996 serious Bug #937996 [src:python-pam] python-pam: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 937996: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937996 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 937831 is serious
Processing commands for cont...@bugs.debian.org: > severity 937831 serious Bug #937831 [src:python-imaplib2] python-imaplib2: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 937831: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937831 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#972852: gdm3: Gdm3 comes to invoke gdm-x-session at the beginning of the user session
Package: gdm3 Version: 3.38.1-2 Severity: grave Dear Maintainer, After I upgraded my Debian box using the command of "apt upgrade" on 17th Oct 2020, I always get an "Oops! A problem occurred!" screen after login. According to system logs, I seem gdm3 come to invoke gdm-x-session always at the beginning of the user session, even though gdm3 is running in Wayland on the login screen. Therefore gnome-shell of the user session seems to fail. Does anyone fix this problem? Thanks, Takahide Nojima -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gdm3 depends on: ii accountsservice 0.6.55-3 ii adduser 3.118 ii dbus 1.12.20-1 ii dconf-cli 0.38.0-1 ii dconf-gsettings-backend 0.38.0-1 ii debconf [debconf-2.0] 1.5.74 ii gir1.2-gdm-1.03.38.1-2 ii gnome-session-bin 3.38.0-2 ii gnome-session-common 3.38.0-2 ii gnome-settings-daemon 3.38.0-2 ii gnome-shell 3.38.1-1 ii gnome-terminal [x-terminal-emulator] 3.38.0-1 ii gsettings-desktop-schemas 3.38.0-2 ii libaccountsservice0 0.6.55-3 ii libaudit1 1:2.8.5-3.1 ii libc6 2.31-4 ii libcanberra-gtk3-00.30-7 ii libcanberra0 0.30-7 ii libgdk-pixbuf2.0-02.40.0+dfsg-5 ii libgdm1 3.38.1-2 ii libglib2.0-0 2.66.1-2 ii libglib2.0-bin2.66.1-2 ii libgtk-3-03.24.23-2 ii libkeyutils1 1.6.1-2 ii libpam-modules1.3.1-5 ii libpam-runtime1.3.1-5 ii libpam-systemd246.6-2 ii libpam0g 1.3.1-5 ii librsvg2-common 2.50.1+dfsg-1 ii libselinux1 3.1-2+b1 ii libsystemd0 246.6-2 ii libx11-6 2:1.6.12-1 ii libxau6 1:1.0.8-1+b2 ii libxcb1 1.14-2 ii libxdmcp6 1:1.1.2-3 ii lsb-base 11.1.0 ii policykit-1 0.105-29 ii procps2:3.3.16-5 ii ucf 3.0043 ii x11-common1:7.7+21 ii x11-xserver-utils 7.7+8 Versions of packages gdm3 recommends: ii at-spi2-core2.38.0-2 ii desktop-base10.0.3 ii x11-xkb-utils 7.7+5 ii xserver-xephyr 2:1.20.9-2 ii xserver-xorg1:7.7+21 ii zenity 3.32.0-6 Versions of packages gdm3 suggests: ii gnome-orca3.38.0-1 pn libpam-fprintd ii libpam-gnome-keyring 3.36.0-1 -- debconf information: gdm3/daemon_name: /usr/sbin/gdm3 * shared/default-x-display-manager: gdm3
Bug#972848: marked as done (kdevelop: FTBFS - dh_install: error: missing files, aborting)
Your message dated Sun, 25 Oct 2020 07:33:50 + with message-id and subject line Bug#972848: fixed in kdevelop 4:5.6.0-3 has caused the Debian Bug report #972848, regarding kdevelop: FTBFS - dh_install: error: missing files, aborting 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.) -- 972848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: kdevelop Severity: serious Justification: FTBFS Hi! kdevelop fails to build from source due to dh_install missing files: make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' debian/rules override_dh_install make[1]: Entering directory '/<>' # create this directory if not existing, so kdevelop-data.install # is the same, no matter whether clang is built mkdir -p debian/tmp/usr/share/kdevclangsupport/ dh_install dh_install: warning: Cannot find (any matches for) "usr/share/kservices5/kdevelopsessions.desktop" (tried in ., debian/tmp) dh_install: warning: plasma-kdevelop missing files: usr/share/kservices5/kdevelopsessions.desktop dh_install: error: missing files, aborting make[1]: *** [debian/rules:18: override_dh_install] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:9: binary-arch] Error 2 dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit status 2 Thanks, Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 --- End Message --- --- Begin Message --- Source: kdevelop Source-Version: 4:5.6.0-3 Done: Pino Toscano We believe that the bug you reported is fixed in the latest version of kdevelop, 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 972...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Pino Toscano (supplier of updated kdevelop 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: SHA512 Format: 1.8 Date: Sun, 25 Oct 2020 08:23:16 +0100 Source: kdevelop Architecture: source Version: 4:5.6.0-3 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Closes: 972848 Changes: kdevelop (4:5.6.0-3) unstable; urgency=medium . * Team upload. * Adapt to krunner 5.72.0: (Closes: #972848) - stop installing file no more needed for it - bump libkf5runner-dev build dependency * Fix day-of-week for changelog entries 4:3.1.2-4, 4:3.1.2-3, 4:3.1.0-3, 1:2.999-0cvs20030905, 1:2.999-0cvs20030815, 1:2.999-1. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Update lintian overrides. Checksums-Sha1: bb70c4c490458ff8a5552b8898263c590be70a1e 4281 kdevelop_5.6.0-3.dsc 5e237318a63ac195c90f186811193d0d7e4c1b47 27128 kdevelop_5.6.0-3.debian.tar.xz 3bff27ae1380cc759412518703cace71cdae2859 24327 kdevelop_5.6.0-3_source.buildinfo Checksums-Sha256: 5b6d9b7f22c97742c35305d00775965de8cf392eaca1e40ce210f39cfc6c94ba 4281 kdevelop_5.6.0-3.dsc 3c75a46962aaf4db1ac9b820b01aac4c778f3a718abbd97421474047a7988e25 27128 kdevelop_5.6.0-3.debian.tar.xz 5a2dcdce0d1138382e82f17fd44b7dfd98d06335a377c1ab5903b2a9cb456131 24327 kdevelop_5.6.0-3_source.buildinfo Files: 2be851e0c9d66dae866a5285c1f25bc1 4281 devel optional kdevelop_5.6.0-3.dsc d6fd574a233dc2c7fc37757adc2ffb96 27128 devel optional kdevelop_5.6.0-3.debian.tar.xz 19fee3b7540b5df8a5e04baf8cb94ed3 24327 devel optional kdevelop_5.6.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAl+VKA4ACgkQLRkciEOx P00nlg//fRMXilX9OwGtNjFsfTRgQjOyGkIzhq798P4k45uuqCVykjJrZ3EBY+W8 td2G2igoPTWOonEqfdzjY2cfBDTMAjliuYjPn/GrQ54ecH/sA68oRxtYK5z0+EIg x9fKYaApr0wXAAoyHxWFD0YwKLMWfngILb1xH81icVvI6iVq02kcv6yymdIzhx5S R8pwF7ZjzL2LPq6yWvVe3MGzJaPXq0zDYsM4CPG/FfrwRV7UDLx9G/csppGTn2+l fUdoBf2oBA2ritXrHFoigN3i/MiLaUyInL9rw3aw97XZlqM+YSrthe7Fci/7chCP T5pObbGnT/sDrKleXThwRaxNnPumyjR+av1iX/yP/xoyu2LeY1SnRgRfmCoZrZxW iJoYwzCsy+ZaVSNbeU8S/EN5e6xZf4/96/PSiH0mQ4R8U/llLC5qhpti2XtrwILm
Bug#972849: useful-clojure FTBFS: Could not locate clojure/tools/macro__init.class, clojure/tools/macro.clj or clojure/tools/macro.cljc on classpath
Source: useful-clojure Version: 0.11.6-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=useful-clojure=all=0.11.6-2=1603520988=0 ... dh_auto_test (cd test && find . -name "*.clj" | \ xargs clojure -cp /<>/useful.jar:/usr/share/java/clojure.jar:/usr/share/java/useful.jar) Syntax error (FileNotFoundException) compiling at (flatland/useful/utils.clj:1:1). Could not locate clojure/tools/macro__init.class, clojure/tools/macro.clj or clojure/tools/macro.cljc on classpath. Full report at: /tmp/clojure-11069530683106326717.edn make[1]: *** [debian/rules:23: override_dh_auto_test] Error 123
Processed: tagging 972848
Processing commands for cont...@bugs.debian.org: > tags 972848 + pending Bug #972848 [src:kdevelop] kdevelop: FTBFS - dh_install: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 972848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#970550: marked as done (diaspora installation fails with ExecJS::ProgramError: TypeError: Cannot read property 'list' of undefined)
Your message dated Sun, 25 Oct 2020 06:33:28 + with message-id and subject line Bug#970550: fixed in node-autoprefixer 10.0.0-1 has caused the Debian Bug report #970550, regarding diaspora installation fails with ExecJS::ProgramError: TypeError: Cannot read property 'list' of undefined 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.) -- 970550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970550 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: diaspora Version: 0.7.14.0-2 Severity: grave Using packages from https://wiki.debian.org/Diaspora#Buster_Fasttrack.2Fpersonal_repo (as rails 5 in not available in unstable/experimental) installation fails with Bundle complete! 101 Gemfile dependencies, 223 gems now installed. Use `bundle info [gemname]` to see where a bundled gem is installed. Setting up secret_token... Checking if the database is empty... diaspora_production database is not empty, skipping database setup Running migrations... Precompiling assets... rake aborted! ExecJS::ProgramError: TypeError: Cannot read property 'list' of undefined /usr/share/diaspora/app/assets/config/manifest.js:9 (execjs):150:23 (execjs):76:3 (execjs):77:2 (execjs):8643:14 (execjs):1:40 Object. ((execjs):1:58) Module._compile (internal/modules/cjs/loader.js:778:30) Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10) Module.load (internal/modules/cjs/loader.js:653:32) tryModuleLoad (internal/modules/cjs/loader.js:593:12) /usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/lib/autoprefixer-rails/processor.rb:153:in `runtime' /usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/lib/autoprefixer-rails/processor.rb:37:in `process' /usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/lib/autoprefixer-rails/sprockets.rb:20:in `run' /usr/share/rubygems-integration/all/gems/autoprefixer-rails-8.6.5/lib/autoprefixer-rails/sprockets.rb:14:in `call' /usr/share/rubygems-integration/all/gems/rake-13.0.1/exe/rake:27:in `' Tasks: TOP => assets:precompile (See full trace by running task with --trace) dpkg: error processing package diaspora (--configure): installed diaspora package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: diaspora E: Sub-process /usr/bin/dpkg returned an error code (1) --- End Message --- --- Begin Message --- Source: node-autoprefixer Source-Version: 10.0.0-1 Done: Xavier Guimard We believe that the bug you reported is fixed in the latest version of node-autoprefixer, 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 970...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Xavier Guimard (supplier of updated node-autoprefixer 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: SHA512 Format: 1.8 Date: Sun, 25 Oct 2020 07:16:34 +0100 Source: node-autoprefixer Architecture: source Version: 10.0.0-1 Distribution: experimental Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Xavier Guimard Closes: 970550 Changes: node-autoprefixer (10.0.0-1) experimental; urgency=medium . * Team upload . [ Pirate Praveen ] * Add custom paths to node-resolve plugin * Add colorette as a component * New upstream version 10.0.0 * Node module no longer require build with gulp or babel * Take build configuration from autoprefixer-rails gem (Closes: #970550) . [ Xavier Guimard ] * Bump debhelper compatibility level to 13 * Use dh-sequence-nodejs * Drop unneeded version constraints from (build) dependencies * Apply multi-arch hints Checksums-Sha1: 1070b351efa8ff161314853dd8b02dd980b4d567 3112 node-autoprefixer_10.0.0-1.dsc 8ca341864bc05880cd4d77edbf08fc03a83481b7 5717 node-autoprefixer_10.0.0.orig-colorette.tar.gz cb4c307f8423a23f5c803ba0265e15499c3269e6 2743 node-autoprefixer_10.0.0.orig-num2fraction.tar.gz a374e4c5abac6820608bf404ee2eb69d80cb4487 243743 node-autoprefixer_10.0.0.orig.tar.gz f3250a4049ba696dcd6e172cbf78bc12a6dd2d07 14944 node-autoprefixer_10.0.0-1.debian.tar.xz Checksums-Sha256:
