Bug#984209: libsynthesis: ftbfs with GCC-11
Control: reopen -1 Control: severity -1 important Matthias Klose wrote: > GCC 11 defaults to the GNU++17 standard. If your package installs > header files in /usr/include, please don't work around C++17 issues by > choosing a lower C++ standard for the package build, but fix these > issues to build with the C++17 standard. Reopen but lower severity, as above described workaround is applied making this issue no longer a FTBFS. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: Re: libsynthesis: ftbfs with GCC-11
Processing control commands: > reopen -1 Bug #984209 [src:libsynthesis] libsynthesis: ftbfs with GCC-11 Bug 984209 is not marked as done; doing nothing. > severity -1 important Bug #984209 [src:libsynthesis] libsynthesis: ftbfs with GCC-11 Severity set to 'important' from 'serious' -- 984209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#983963: aiksaurus: ftbfs with GCC-11
Control: reopen -1 Control: severity -1 important Matthias Klose wrote: > GCC 11 defaults to the GNU++17 standard. If your package installs > header files in /usr/include, please don't work around C++17 issues by > choosing a lower C++ standard for the package build, but fix these > issues to build with the C++17 standard. Reopen but lower severity, as above described workaround is applied making this issue no longer a FTBFS. - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: signature
Processed: Re: aiksaurus: ftbfs with GCC-11
Processing control commands:
> reopen -1
Bug #983963 {Done: Jonas Smedegaard } [src:aiksaurus] aiksaurus:
ftbfs with GCC-11
'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 aiksaurus/1.2.1+dev-0.12-7.
> severity -1 important
Bug #983963 [src:aiksaurus] aiksaurus: ftbfs with GCC-11
Severity set to 'important' from 'serious'
--
983963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983963
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#983963: marked as done (aiksaurus: ftbfs with GCC-11)
Your message dated Sun, 07 Nov 2021 03:18:27 + with message-id and subject line Bug#983963: fixed in aiksaurus 1.2.1+dev-0.12-7 has caused the Debian Bug report #983963, regarding aiksaurus: ftbfs with GCC-11 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.) -- 983963: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983963 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:aiksaurus Version: 1.2.1+dev-0.12-6.3 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/aiksaurus_1.2.1+dev-0.12-6.3_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] make[1]: Leaving directory '/<>' dh_auto_build dh_auto_build: warning: Compatibility levels before 10 are deprecated (level 9 in use) make -j1 make[1]: Entering directory '/<>' make all-recursive make[2]: Entering directory '/<>' Making all in base make[3]: Entering directory '/<>/base' g++ -DHAVE_CONFIG_H -I. -I.. -I.. -DAIK_DATA_DIR=\"/usr/share/aiksaurus/\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o aiksaurus.t.o aiksaurus.t.cpp /bin/bash ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. -I.. -DAIK_DATA_DIR=\"/usr/share/aiksaurus/\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o Aiksaurus.lo Aiksaurus.cpp libtool: compile: g++ -DHAVE_CONFIG_H -I. -I.. -I.. -DAIK_DATA_DIR=\"/usr/share/aiksaurus/\" -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c Aiksaurus.cpp -fPIC -DPIC -o .libs/Aiksaurus.o In file included from Aiksaurus.cpp:28: MeaningsFile.h:49:17: error: ISO C++17 does not allow dynamic exception specifications 49 | throw(AiksaurusException); | ^ MeaningsFile.h:54:45: error: ISO C++17 does not allow dynamic exception specifications 54 | MeaningsFile(const char* fname) throw(AiksaurusException); | ^ MeaningsFile.h:58:35: error: ISO C++17 does not allow dynamic exception specifications 58 | int* getWords(int id) throw(AiksaurusException); | ^ In file included from Aiksaurus.cpp:29: WordsFile.h:58:42: error: ISO C++17 does not allow dynamic exception specifications 58 | WordsFile(const char* fname) throw(AiksaurusException); | ^ WordsFile.h:62:35: error: ISO C++17 does not allow dynamic exception specifications 62 | void loadWord(int id) throw(AiksaurusException); | ^ WordsFile.h:63:56: error: ISO C++17 does not allow dynamic exception specifications 63 | bool findWord(const char* str, int& index) throw(AiksaurusException); |^ In file included from Aiksaurus.cpp:30: WordStream.h:41:36: error: ISO C++17 does not allow dynamic exception specifications
Bug#998564: marked as done (ncmpc: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "artist_screen")
Your message dated Sun, 07 Nov 2021 03:04:26 + with message-id and subject line Bug#998564: fixed in ncmpc 0.45-2 has caused the Debian Bug report #998564, regarding ncmpc: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "artist_screen" 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.) -- 998564: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ncmpc Version: 0.45-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- \ > -Dartist_screen=true \ > -Dasync_connect=true \ > -Dcolors=true \ > -Dchat_screen=true \ > -Dcurses=ncursesw \ > -Ddocumentation=auto \ > -Dkey_screen=true \ > -Dhelp_screen=true \ > -Dhtml_manual=false \ > -Dlibrary_screen=true \ > -Dlyrics_screen=true \ > -Dlyrics_plugin_dir="/usr/lib/ncmpc/lyrics/" \ > -Dlirc=enabled \ > -Dlocale=enabled \ > -Dmanual=true \ > -Dmini=false \ > -Dmouse=enabled \ > -Dmultibyte=true \ > -Dnls=enabled \ > -Doutputs_screen=true \ > -Dregex=enabled \ > -Dsearch_screen=true \ > -Dsong_screen=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dartist_screen=true > -Dasync_connect=true -Dcolors=true -Dchat_screen=true -Dcurses=ncursesw > -Ddocumentation=auto -Dkey_screen=true -Dhelp_screen=true -Dhtml_manual=false > -Dlibrary_screen=true -Dlyrics_screen=true > -Dlyrics_plugin_dir=/usr/lib/ncmpc/lyrics/ -Dlirc=enabled -Dlocale=enabled > -Dmanual=true -Dmini=false -Dmouse=enabled -Dmultibyte=true -Dnls=enabled > -Doutputs_screen=true -Dregex=enabled -Dsearch_screen=true -Dsong_screen=true > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "artist_screen" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:47:18.142091 > Main binary: /usr/bin/python3 > Build Options: -Dartist_screen=true -Dasync_connect=true -Dcolors=true > -Dchat_screen=true -Dcurses=ncursesw -Ddocumentation=auto -Dkey_screen=true > -Dhelp_screen=true -Dhtml_manual=false -Dlibrary_screen=true > -Dlyrics_screen=true -Dlyrics_plugin_dir=/usr/lib/ncmpc/lyrics/ > -Dlirc=enabled -Dlocale=enabled -Dmanual=true -Dmini=false -Dmouse=enabled > -Dmultibyte=true -Dnls=enabled -Doutputs_screen=true -Dregex=enabled > -Dsearch_screen=true -Dsong_screen=true -Dprefix=/usr > -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc > -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "artist_screen" > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dartist_screen=true > -Dasync_connect=true -Dcolors=true -Dchat_screen=true -Dcurses=ncursesw > -Ddocumentation=auto -Dkey_screen=true -Dhelp_screen=true -Dhtml_manual=false > -Dlibrary_screen=true -Dlyrics_screen=true > -Dlyrics_plugin_dir=/usr/lib/ncmpc/lyrics/ -Dlirc=enabled -Dlocale=enabled > -Dmanual=true -Dmini=false -Dmouse=enabled -Dmultibyte=true -Dnls=enabled > -Doutputs_screen=true -Dregex=enabled -Dsearch_screen=true -Dsong_screen=true > returned exit code 1 > make[1]: *** [debian/rules:10: override_dh_auto_configure] Error 25 The full build log is available from:
Bug#998535: marked as done (shell-utils-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded
Your message dated Sat, 6 Nov 2021 23:06:05 -0400 with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org> and subject line Mass closing clojure FTBFS bugs has caused the Debian Bug report #998535, regarding shell-utils-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded from it before. 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.) -- 998535: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: shell-utils-clojure Version: 1.0.2-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein pom debian/pom.xml > Wrote /<>/debian/pom.xml > lein jar > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:18: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/11/04/shell-utils-clojure_1.0.2-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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Closing these FTBFS bugs, as it seems the failures were caused by some transition on the Java side. Everything now builds properly in unstable and those bugs can no longer be reproduced. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#998523: marked as done (bidi-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded from it
Your message dated Sat, 6 Nov 2021 23:06:05 -0400 with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org> and subject line Mass closing clojure FTBFS bugs has caused the Debian Bug report #998523, regarding bidi-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded from it before. 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.) -- 998523: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998523 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: bidi-clojure Version: 2.1.6-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein pom debian/pom.xml > Wrote /<>/debian/pom.xml > lein jar > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:18: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/11/04/bidi-clojure_2.1.6-1_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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Closing these FTBFS bugs, as it seems the failures were caused by some transition on the Java side. Everything now builds properly in unstable and those bugs can no longer be reproduced. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#997784: marked as done (rbac-client-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded
Your message dated Sat, 6 Nov 2021 23:06:05 -0400 with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org> and subject line Mass closing clojure FTBFS bugs has caused the Debian Bug report #997784, regarding rbac-client-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded from it before. 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.) -- 997784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997784 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rbac-client-clojure Version: 0.9.4-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein test > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:25: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/rbac-client-clojure_0.9.4-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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Closing these FTBFS bugs, as it seems the failures were caused by some transition on the Java side. Everything now builds properly in unstable and those bugs can no longer be reproduced. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#997753: marked as done (puppetlabs-ring-middleware-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not b
Your message dated Sat, 6 Nov 2021 23:06:05 -0400 with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org> and subject line Mass closing clojure FTBFS bugs has caused the Debian Bug report #997753, regarding puppetlabs-ring-middleware-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded from it before. 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.) -- 997753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997753 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: puppetlabs-ring-middleware-clojure Version: 1.3.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein test > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/puppetlabs-ring-middleware-clojure_1.3.0-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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Closing these FTBFS bugs, as it seems the failures were caused by some transition on the Java side. Everything now builds properly in unstable and those bugs can no longer be reproduced. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#997731: marked as done (trapperkeeper-webserver-jetty9-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has n
Your message dated Sat, 6 Nov 2021 23:06:05 -0400 with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org> and subject line Mass closing clojure FTBFS bugs has caused the Debian Bug report #997731, regarding trapperkeeper-webserver-jetty9-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded from it before. 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.) -- 997731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: trapperkeeper-webserver-jetty9-clojure Version: 4.1.0-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein pom debian/pom.xml > Wrote /<>/debian/pom.xml > lein i18n make > Running 'make i18n' > lein jar > Warning: specified :main without including it in :aot. > Implicit AOT of :main will be removed in Leiningen 3.0.0. > If you only need AOT for your uberjar, consider adding :aot :all into your > :uberjar profile instead. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/trapperkeeper-webserver-jetty9-clojure_4.1.0-4_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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Closing these FTBFS bugs, as it seems the failures were caused by some transition on the Java side. Everything now builds properly in unstable and those bugs can no longer be reproduced. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#997734: marked as done (trapperkeeper-authorization-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not
Your message dated Sat, 6 Nov 2021 23:06:05 -0400 with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org> and subject line Mass closing clojure FTBFS bugs has caused the Debian Bug report #997734, regarding trapperkeeper-authorization-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded from it before. 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.) -- 997734: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997734 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: trapperkeeper-authorization-clojure Version: 1.0.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein test > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:25: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/trapperkeeper-authorization-clojure_1.0.0-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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Closing these FTBFS bugs, as it seems the failures were caused by some transition on the Java side. Everything now builds properly in unstable and those bugs can no longer be reproduced. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#997711: marked as done (puppetlabs-http-client-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been
Your message dated Sat, 6 Nov 2021 23:06:05 -0400 with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org> and subject line Mass closing clojure FTBFS bugs has caused the Debian Bug report #997711, regarding puppetlabs-http-client-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded from it before. 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.) -- 997711: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: puppetlabs-http-client-clojure Version: 1.2.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein test > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/puppetlabs-http-client-clojure_1.2.0-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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Closing these FTBFS bugs, as it seems the failures were caused by some transition on the Java side. Everything now builds properly in unstable and those bugs can no longer be reproduced. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#997705: marked as done (trapperkeeper-metrics-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been d
Your message dated Sat, 6 Nov 2021 23:06:05 -0400 with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org> and subject line Mass closing clojure FTBFS bugs has caused the Debian Bug report #997705, regarding trapperkeeper-metrics-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded from it before. 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.) -- 997705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997705 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: trapperkeeper-metrics-clojure Version: 1.3.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein test > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:28: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/trapperkeeper-metrics-clojure_1.3.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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Closing these FTBFS bugs, as it seems the failures were caused by some transition on the Java side. Everything now builds properly in unstable and those bugs can no longer be reproduced. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#997714: marked as done (trapperkeeper-status-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been do
Your message dated Sat, 6 Nov 2021 23:06:05 -0400 with message-id <6f52ad4d-7c0a-5754-3b42-46d95ffc0...@debian.org> and subject line Mass closing clojure FTBFS bugs has caused the Debian Bug report #997714, regarding trapperkeeper-status-clojure: FTBFS: Cannot access central (https://repo1.maven.org/maven2/) in offline mode and the artifact org.junit:junit-bom:pom:debian has not been downloaded from it before. 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.) -- 997714: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: trapperkeeper-status-clojure Version: 1.1.1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > lein test > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > Cannot access central (https://repo1.maven.org/maven2/) in offline mode and > the artifact org.junit:junit-bom:pom:debian has not been downloaded from it > before. > This could be due to a typo in :dependencies, file system permissions, or > network issues. > If you are behind a proxy, try setting the 'http_proxy' environment variable. > make[1]: *** [debian/rules:24: override_dh_auto_test] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/trapperkeeper-status-clojure_1.1.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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Closing these FTBFS bugs, as it seems the failures were caused by some transition on the Java side. Everything now builds properly in unstable and those bugs can no longer be reproduced. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Louis-Philippe Véronneau ⢿⡄⠘⠷⠚⠋ po...@debian.org / veronneau.org ⠈⠳⣄ OpenPGP_signature Description: OpenPGP digital signature --- End Message ---
Bug#998503: marked as done (ruby-twitter-stream: FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError:)
Your message dated Sun, 07 Nov 2021 01:33:58 +
with message-id
and subject line Bug#998503: fixed in ruby-twitter-stream 0.1.16-4
has caused the Debian Bug report #998503,
regarding ruby-twitter-stream: FTBFS: ERROR: Test "ruby3.0" failed:
NoMethodError:
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.)
--
998503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998503
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-twitter-stream
Version: 0.1.16-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> NoMethodError:
>undefined method `escape' for URI:Module
> # ./lib/twitter/json_stream.rb:361:in `escape'
> # ./lib/twitter/json_stream.rb:357:in `block in query'
> # ./lib/twitter/json_stream.rb:357:in `each'
> # ./lib/twitter/json_stream.rb:357:in `map'
> # ./lib/twitter/json_stream.rb:357:in `query'
> # ./lib/twitter/json_stream.rb:249:in `send_request'
> # ./lib/twitter/json_stream.rb:134:in `connection_completed'
> # ./spec/spec_helper.rb:15:in `connect_stream'
> # ./spec/twitter/json_stream_spec.rb:96:in `block (3 levels) in (required)>'
>
> Finished in 23.56 seconds (files took 0.17203 seconds to load)
> 38 examples, 1 failure
>
> Failed examples:
>
> rspec ./spec/twitter/json_stream_spec.rb:95 # Twitter::JSONStream on valid
> stream should add custom params
>
> /usr/bin/ruby3.0
> -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 failed
> ERROR: Test "ruby3.0" failed:
The full build log is available from:
http://qa-logs.debian.net/2021/11/04/ruby-twitter-stream_0.1.16-3_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!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: ruby-twitter-stream
Source-Version: 0.1.16-4
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-twitter-stream, 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 998...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-twitter-stream
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, 07 Nov 2021 01:59:57 +0100
Source: ruby-twitter-stream
Architecture: source
Version: 0.1.16-4
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 998503
Changes:
ruby-twitter-stream (0.1.16-4) unstable; urgency=medium
.
* Team upload.
.
[ Debian Janitor ]
* Trim trailing whitespace.
* Use secure copyright file specification URI.
* Use secure URI in Homepage field.
* Bump debhelper from deprecated 9 to 13.
* Set debhelper-compat version in Build-Depends.
* Update Vcs-* headers from URL redirect.
* Use canonical URL in Vcs-Git.
* Set upstream metadata fields: Bug-Database, Bug-Submit.
* Update watch file format version to 4.
* Remove constraints unnecessary since buster:
+ Build-Depends: Drop versioned constraint on ruby-eventmachine,
ruby-http-parser.rb and ruby-simple-oauth.
.
[ Daniel Leidert ]
* d/control: Add Testsuite and Rules-Requires-Root fields.
(Standards-Version): Bump to 4.6.0.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/rules: Use gem installation layout and remove fixtures from installation.
* d/watch: Use gemwatch URL.
*
Processed: Re: hplip: HPLIP incorrectly links to obsolete or missing libhpdiscovery.so
Processing control commands: > tag -1 moreinfo Bug #998224 [hplip] hplip: HPLIP incorrectly links to obsolete or missing libhpdiscovery.so Added tag(s) moreinfo. -- 998224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998224: hplip: HPLIP incorrectly links to obsolete or missing libhpdiscovery.so
Control: tag -1 moreinfo Hi Troy, thanks for your bugreport. Unfortunately I have problems understanding what is going on. How can HPLIP link to a missing libhpdiscovery.so. I assume you are building the package in a minimal chroot. How can there be an old version of libhpdiscovery.so available? Can you please be a bit more verbose about what you are doing and what fails? Best regards, Thorsten
Bug#952616: marked as done (ruby-concurrent-ext: FTBFS: ERROR: Test "ruby2.5" failed.)
Your message dated Sun, 07 Nov 2021 02:23:08 +0100 with message-id <6f10ab4efe3b65cb28db30c05baf0f7a7453a6fc.ca...@debian.org> and subject line Bug report does not apply anymore has caused the Debian Bug report #952616, regarding ruby-concurrent-ext: FTBFS: ERROR: Test "ruby2.5" failed. 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.) -- 952616: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952616 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-concurrent-ext Version: 1.0.5-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200225 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules). Relevant part (hopefully): > /usr/bin/ruby2.5 /usr/bin/gem2deb-test-runner > > ┌──┐ > │ Checking Rubygems dependency resolution on ruby2.5 > │ > └──┘ > > GEM_PATH=/<>/debian/ruby-concurrent-ext/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0 > ruby2.5 -e gem\ \"concurrent-ruby-ext\" > /usr/lib/ruby/2.5.0/rubygems/dependency.rb:312:in `to_specs': Could not find > 'concurrent-ruby' (= 1.0.5) - did find: [concurrent-ruby-1.1.6] > (Gem::MissingSpecVersionError) > Checked in > 'GEM_PATH=/<>/debian/ruby-concurrent-ext/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0:/var/lib/gems/2.5.0:/usr/lib/ruby/gems/2.5.0:/usr/share/rubygems-integration/2.5.0:/usr/share/rubygems-integration/all:/usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0', > execute `gem env` for more information > from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1469:in `block in > activate_dependencies' > from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1458:in `each' > from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1458:in > `activate_dependencies' > from /usr/lib/ruby/2.5.0/rubygems/specification.rb:1440:in `activate' > from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:68:in `block > in gem' > from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in > `synchronize' > from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `gem' > from -e:1:in `' > bigdecimal (default: 1.3.4) > cmath (default: 1.0.0) > concurrent-ruby (1.1.6) > csv (default: 1.0.0) > date (default: 1.0.0) > dbm (default: 1.0.0) > did_you_mean (1.2.1) > etc (default: 1.0.0) > fcntl (default: 1.0.0) > fiddle (default: 1.0.0) > fileutils (default: 1.0.2) > gdbm (default: 2.0.0) > io-console (default: 0.4.6) > ipaddr (default: 1.2.0) > json (default: 2.1.0) > minitest (5.13.0) > net-telnet (0.1.1) > openssl (default: 2.1.2) > power_assert (1.1.5) > psych (default: 3.0.2) > rake (13.0.1) > rdoc (default: 6.0.1.1) > scanf (default: 1.0.0) > sdbm (default: 1.0.0) > stringio (default: 0.0.1) > strscan (default: 1.0.0) > test-unit (3.3.4) > webrick (default: 1.4.2) > xmlrpc (0.3.0) > zlib (default: 1.0.0) > ERROR: Test "ruby2.5" failed. The full build log is available from: http://qa-logs.debian.net/2020/02/25/ruby-concurrent-ext_1.0.5-1_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 --- Hi, the build log shows that ruby2.5-dev has been installed into the build environment. This package has been removed from Testing before the bullseye release and is not part of any Debian release except for Buster (and this one has the correct gem version of concurrent-ruby). The package actually builds just fine and the report does not apply anymore. Closing this report. Regards, Daniel -- Regards, Daniel Leidert | https://www.wgdd.de/ GPG-Key RSA4096 / BEED4DED5544A4C03E283DC74BCD0567C296D05D GPG-Key ED25519 / BD3C132D8B3805D1808123AB7ACE00941E338C78 https://www.fiverr.com/dleidert https://www.patreon.com/join/dleidert signature.asc Description: This is a digitally signed message part ---
Bug#998503: marked as pending in ruby-twitter-stream
Control: tag -1 pending Hello, Bug #998503 in ruby-twitter-stream 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-twitter-stream/-/commit/54093d0a8551e1cdf30b9e6d65b5620a19fe9813 Add patch to fix FTBFS with Ruby 3 * d/patches/998503-replace-uri-escape.patch: Add patch. - Replace obsolete URI.escape and fix FTBFS with Ruby 3 (closes: #998503). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/998503
Processed: Bug#998503 marked as pending in ruby-twitter-stream
Processing control commands: > tag -1 pending Bug #998503 [src:ruby-twitter-stream] ruby-twitter-stream: FTBFS: ERROR: Test "ruby3.0" failed: NoMethodError: Added tag(s) pending. -- 998503: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998503 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998712: irrlicht: invalid Uploaders field: missing comma between Vincent Cheng and Julien Puydt
Source: irrlicht Version: 1.8.4+dfsg1-2 Severity: serious Justification: Policy 5.6.3 irrlicht 1.8.4+dfsg1-2 introduced an invalid uploaders field, that is missing a comma between Vincent Cheng and Julien Puydt. $ apt-cache showsrc irrlicht | grep -E '^$|^Version|^Uploaders' Version: 1.8.4+dfsg1-1.1 Uploaders: Christoph Egger , Vincent Cheng Version: 1.8.4+dfsg1-2 Uploaders: Vincent Cheng Julien Puydt According to Debian policy 5.6.3 the Uploaders field must separate individual uploaders using commas: List of the names and email addresses of co-maintainers of the package, if any. ... The format of each entry is the same as that of the Maintainer field, and multiple entries must be comma separated. This is causing the DDPO and BLS cron jobs to send error mails. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: reassign 997638 to xutils-dev
Processing commands for cont...@bugs.debian.org: > reassign 997638 xutils-dev Bug #997638 [imake] nas: FTBFS: ar: libdeps specified more than once Warning: Unknown package 'imake' Bug reassigned from package 'imake' to 'xutils-dev'. Ignoring request to alter found versions of bug #997638 to the same values previously set Ignoring request to alter fixed versions of bug #997638 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 997638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2
I was advised a week ago that the app I maintain is not building in unstable as the compiler (fpc) has been updated. However, Testing still has the 'older' compiler and it builds fine with that. How do I test my build against tools only available in sid ? Background - --- tomboy-ng is built using Free Pascal Compiler and Lazarus. Testing has FPC3.2.0 but apparently sid has FPC3.2.2. Obviously, I can get (have already got) FPC direct from its source but I have found the need to test, for Debian, using Debian supplied tools. I obtained my Testing from https://cdimage.debian.org/cdimage/weekly-builds/amd64/iso-cd/, its dated 1st November. Should I be using something else ? My fix is trivial, my scripts (stupidly) includes a test that accepts only FPC 3.2.0. But I would prefer to update the release anyway, the version of tomboy- ng in Bullseye has issues that flowed from Debian's decision to drop libappindicator3 in favour of libayana (and, not surprisingly, they have different file names!). Davo On Wed, 2021-10-27 at 14:11 +0200, Graham Inggs wrote: > Source: tomboy-ng > Version: 0.32-2 > Severity: serious > Tags: ftbfs bookworm sid > > Hi Maintainer > > tomboy-ng fails to build from source since fpc 3.2.2 was uploaded to > unstable. I've copied what I hope is the relevant part of the log > below. > > Regards > Graham > > > make[1]: Entering directory '/build/1st/tomboy-ng-0.32' > == We have compiled [tomboy-ng] > == $BIN_DIR is [/usr/bin] > bash ./buildit.bash > /usr/bin/which: this version of `which' is deprecated; use `command > -v' in scripts instead. > /usr/bin/which: this version of `which' is deprecated; use `command > -v' in scripts instead. > Compiler reported [3.2.2] > Unclear about your compiler, maybe edit script to support new one, > exiting ... > make[1]: *** [Makefile:36: tomboy-ngx86_64] Error 1
Processed (with 1 error): Re: Bug#997638: nas: FTBFS: ar: libdeps specified more than once
Processing control commands: > reassign -1 imake Bug #997638 [src:nas] nas: FTBFS: ar: libdeps specified more than once Bug reassigned from package 'src:nas' to 'imake'. Warning: Unknown package 'imake' Warning: Unknown package 'imake' No longer marked as found in versions nas/1.9.4-7. Warning: Unknown package 'imake' Warning: Unknown package 'imake' Ignoring request to alter fixed versions of bug #997638 to the same values previously set Warning: Unknown package 'imake' > forcemerge -1 997628 Bug #997638 [imake] nas: FTBFS: ar: libdeps specified more than once Warning: Unknown package 'imake' Unable to merge bugs because: package of #997628 is 'xutils-dev' not 'imake' Warning: Unknown package 'imake' Failed to forcibly merge 997638: Did not alter merged bugs. > affects 997628 src:nas Bug #997628 [xutils-dev] imake: uses “ar clq” by default, which recent binutils broke in an incompatible way Added indication that 997628 affects src:nas -- 997628: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997628 997638: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997638 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997638: nas: FTBFS: ar: libdeps specified more than once
Control: reassign -1 imake Control: forcemerge -1 997628 Control: affects 997628 src:nas So I've looked into this and I can see that this is not a bug in nas directly, but a disagreement between imake and binutils. Assigning to imake for now, in the same fashion as #997628 On Sat, Oct 23, 2021 at 11:18:44PM +0200, Lucas Nussbaum wrote: >Source: nas >Version: 1.9.4-7 >Severity: serious >Justification: FTBFS >Tags: bookworm sid ftbfs >User: lu...@debian.org >Usertags: ftbfs-20211023 ftbfs-bookworm > >Hi, > >During a rebuild of all packages in sid, your package failed to build >on amd64. > > >Relevant part (hopefully): >> make[4]: Entering directory '/<>/server/dia' >> rm -f dispatch.o >> gcc -c -g -O2 -fno-strict-aliasing -g -O2 >> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat >> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon -I. >> -I../include -I../../include -I../../lib/audio -I../../include-Dlinux >> -D__amd64__ -D_POSIX_C_SOURCE=199309L >> -D_POSIX_SOURCE -D_XOPEN_SOURCE >> -D_BSD_SOURCE -D_SVID_SOURCE >> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 >> -DFUNCPROTO=15 -DNARROWPROTO >> -DNASCONFSEARCHPATH=\"/etc/nas/\" dispatch.c >> In file included from >> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, >> from /usr/include/string.h:26, >> from ../include/os.h:124, >> from ../include/misc.h:57, >> from dispatch.c:52: >> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and >> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] >> 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use >> _DEFAULT_SOURCE" >> | ^~~ >> rm -f dixutils.o >> gcc -c -g -O2 -fno-strict-aliasing -g -O2 >> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat >> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon -I. >> -I../include -I../../include -I../../lib/audio -I../../include-Dlinux >> -D__amd64__ -D_POSIX_C_SOURCE=199309L >> -D_POSIX_SOURCE -D_XOPEN_SOURCE >> -D_BSD_SOURCE -D_SVID_SOURCE >> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 >> -DFUNCPROTO=15 -DNARROWPROTO >> -DNASCONFSEARCHPATH=\"/etc/nas/\" dixutils.c >> In file included from >> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, >> from /usr/include/string.h:26, >> from ../include/os.h:124, >> from ../include/misc.h:57, >> from dixutils.c:52: >> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and >> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] >> 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use >> _DEFAULT_SOURCE" >> | ^~~ >> rm -f events.o >> gcc -c -g -O2 -fno-strict-aliasing -g -O2 >> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat >> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon -I. >> -I../include -I../../include -I../../lib/audio -I../../include-Dlinux >> -D__amd64__ -D_POSIX_C_SOURCE=199309L >> -D_POSIX_SOURCE -D_XOPEN_SOURCE >> -D_BSD_SOURCE -D_SVID_SOURCE >> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 >> -DFUNCPROTO=15 -DNARROWPROTO >> -DNASCONFSEARCHPATH=\"/etc/nas/\" events.c >> In file included from >> /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, >> from /usr/include/string.h:26, >> from ../include/os.h:124, >> from ../include/misc.h:57, >> from events.c:52: >> /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and >> _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] >> 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use >> _DEFAULT_SOURCE" >> | ^~~ >> rm -f globals.o >> gcc -c -g -O2 -fno-strict-aliasing -g -O2 >> -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat >> -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fcommon -I. >> -I../include -I../../include -I../../lib/audio -I../../include-Dlinux >> -D__amd64__ -D_POSIX_C_SOURCE=199309L >> -D_POSIX_SOURCE -D_XOPEN_SOURCE >> -D_BSD_SOURCE -D_SVID_SOURCE >> -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 >> -DFUNCPROTO=15 -DNARROWPROTO >> -DNASCONFSEARCHPATH=\"/etc/nas/\" globals.c >> In file included from >>
Bug#983229: marked as done (survex: FTBFS with PROJ 8.0.0)
Your message dated Sun, 07 Nov 2021 00:06:15 +
with message-id
and subject line Bug#983229: fixed in survex 1.4.0-1
has caused the Debian Bug report #983229,
regarding survex: FTBFS with PROJ 8.0.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.)
--
983229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983229
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: survex
Version: 1.2.44-1
Severity: important
Tags: upstream ftbfs
User: debian-...@lists.debian.org
Usertags: proj-8.0
Control: forwarded -1 https://trac.survex.com/ticket/102
Dear Maintainer,
Your package FTBFS with PROJ 8.0.0:
In file included from listpos.c:29:
cavern.h:45:10: fatal error: proj_api.h: No such file or directory
45 | #include
| ^~~~
It needs to be ported to use proj.h instead of proj_api.h which has been
removed.
Kind Regards,
Bas
dpkg-checkbuilddeps: error: Unmet build dependencies: libavcodec-dev
libavformat-dev libswscale-dev libwxgtk3.0-gtk3-dev
[1;33mW: Unmet build-dependency in source[0m
dh clean
dh_clean
dpkg-source: info: using source format '3.0 (quilt)'
dpkg-source: info: building survex using existing ./survex_1.2.44.orig.tar.gz
dpkg-source: info: building survex using existing
./survex_1.2.44.orig.tar.gz.asc
dpkg-source: info: building survex in survex_1.2.44-1.1.debian.tar.xz
dpkg-source: info: building survex in survex_1.2.44-1.1.dsc
[0mI: Generating source changes file for original dsc[0m
dpkg-genchanges: info: not including original source code in upload
[0mI: Copying COW directory[0m
[0mI: forking: rm -rf /var/cache/pbuilder/build/cow.25725[0m
[0mI: forking: cp -al /var/cache/pbuilder/base-sid+rebuild.cow
/var/cache/pbuilder/build/cow.25725[0m
[0mI: removed stale ilistfile /var/cache/pbuilder/build/cow.25725/.ilist[0m
[0mI: forking: chroot /var/cache/pbuilder/build/cow.25725
cowdancer-ilistcreate /.ilist 'find . -xdev -path ./home -prune -o \( \( -type
l -o -type f \) -a -links +1 -print0 \) | xargs -0 stat --format '%d %i ''[0m
[0mI: Invoking pbuilder[0m
[0mI: forking: pbuilder build --debbuildopts --debbuildopts --buildplace
/var/cache/pbuilder/build/cow.25725 --buildresult /var/cache/pbuilder/result/
--mirror http://ftp.nl.debian.org/debian/ --distribution sid --no-targz
--internal-chrootexec 'chroot /var/cache/pbuilder/build/cow.25725 cow-shell'
/home/bas/tmp/debian/survex_1.2.44-1.1.dsc[0m
[0mI: Running in no-targz mode[0m
[0mI: pbuilder: network access will be disabled during build[0m
[0mI: Current time: Sun Feb 21 11:29:42 CET 2021[0m
[0mI: pbuilder-time-stamp: 1613903382[0m
[0mI: copying local configuration[0m
[1;33mW: --override-config is not set; not updating apt.conf Read the manpage
for details.[0m
[0mI: mounting /proc filesystem[0m
[0mI: mounting /sys filesystem[0m
[0mI: creating /{dev,run}/shm[0m
[0mI: mounting /dev/pts filesystem[0m
[0mI: redirecting /dev/ptmx to /dev/pts/ptmx[0m
[0mI: policy-rc.d already exists[0m
[0mI: Obtaining the cached apt archive contents[0m
[0mI: Copying source file[0m
[0mI: copying [/home/bas/tmp/debian/survex_1.2.44-1.1.dsc][0m
[0mI: copying [/home/bas/tmp/debian/survex_1.2.44.orig.tar.gz][0m
[0mI: copying [/home/bas/tmp/debian/survex_1.2.44.orig.tar.gz.asc][0m
[0mI: copying [/home/bas/tmp/debian/survex_1.2.44-1.1.debian.tar.xz][0m
[0mI: Extracting source[0m
dpkg-source: warning: extracting unsigned source package (survex_1.2.44-1.1.dsc)
dpkg-source: info: extracting survex in survex-1.2.44
dpkg-source: info: unpacking survex_1.2.44.orig.tar.gz
dpkg-source: info: unpacking survex_1.2.44-1.1.debian.tar.xz
[0mI: Not using root during the build.[0m
[0mI: Installing the build-deps[0m
-> Attempting to satisfy build-dependencies
-> Creating pbuilder-satisfydepends-dummy package
Package: pbuilder-satisfydepends-dummy
Version: 0.invalid.0
Architecture: amd64
Maintainer: Debian Pbuilder Team
Description: Dummy package to satisfy dependencies with aptitude - created by
pbuilder
This package was created automatically by pbuilder to satisfy the
build-dependencies of the package being currently built.
Depends: debhelper (>= 10), libx11-dev, libxext-dev, x11proto-core-dev,
libavcodec-dev, libavformat-dev, libproj-dev, libswscale-dev,
libwxgtk3.0-gtk3-dev, mesa-common-dev, libglu1-mesa-dev, pkg-config
dpkg-deb: building package 'pbuilder-satisfydepends-dummy' in
'/tmp/satisfydepends-aptitude/pbuilder-satisfydepends-dummy.deb'.
Selecting previously unselected package pbuilder-satisfydepends-dummy.
(Reading database ... 14463 files and
Bug#997799: marked as done (feynmf: Use disappeared /bin/tempfile in debian patch)
Your message dated Sun, 07 Nov 2021 00:04:28 + with message-id and subject line Bug#997799: fixed in feynmf 1.08-13 has caused the Debian Bug report #997799, regarding feynmf: Use disappeared /bin/tempfile in debian patch 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.) -- 997799: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997799 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: feynmf Severity: grave Version: 1.08-12 Tags: sid bookworm X-Debbugs-CC: alteh...@debian.org Dear Debian feynmf package maintainer, The custom patch introduced by Debian at https://sources.debian.org/src/feynmf/1.08-12/debian/patches/docu.patch/ uses /bin/tempfile, which has disappeared in newer Debian systems. This will likely cause the program to crash. Please consider replacing it with "/bin/mktemp" from coreutils instead. Thanks, Boyuan Yang --- End Message --- --- Begin Message --- Source: feynmf Source-Version: 1.08-13 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of feynmf, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated feynmf 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, 07 Nov 2021 00:10:57 +0100 Source: feynmf Architecture: source Version: 1.08-13 Distribution: unstable Urgency: low Maintainer: Thorsten Alteholz Changed-By: Thorsten Alteholz Closes: 997799 Changes: feynmf (1.08-13) unstable; urgency=low . * debian/control: use dh13 * debian/control: standard changed to 4.6.0 (no changes) * adapt docu.patch to use mktemp instead of tempfile (Closes: #997799) Checksums-Sha1: daeaf2e839e863b42e266c788f3b34df5c410dd5 2129 feynmf_1.08-13.dsc 06858897c692c45d469b9113d201b74a38f5e63c 7792 feynmf_1.08-13.debian.tar.xz 3aed1326ecb9810b7d4a01459daa840e01e64d68 8148 feynmf_1.08-13_amd64.buildinfo Checksums-Sha256: de4daf27f42f65e9db13d1a2309ba86da3ec47995f2647b91832f53c6e7421d5 2129 feynmf_1.08-13.dsc 7f5aa144099d6fd168879f86662b9d096f0f73114f7ca19978093fa174306568 7792 feynmf_1.08-13.debian.tar.xz 103c7a94ac6eabf5845de020e4ee355ef6da55c205007289cf6e338f7d411abb 8148 feynmf_1.08-13_amd64.buildinfo Files: f9019072ab9ca23faba1f1640d48ba6a 2129 tex optional feynmf_1.08-13.dsc 857c823d583936d32a94639f0cf3aecd 7792 tex optional feynmf_1.08-13.debian.tar.xz c80b10d4cbd1c8817ad60f7246da9cbf 8148 tex optional feynmf_1.08-13_amd64.buildinfo -BEGIN PGP SIGNATURE- iQKnBAEBCgCRFiEEYgH7/9u94Hgi6ruWlvysDTh7WEcFAmGHEkJfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYy MDFGQkZGREJCREUwNzgyMkVBQkI5Njk2RkNBQzBEMzg3QjU4NDcTHGRlYmlhbkBh bHRlaG9sei5kZQAKCRCW/KwNOHtYRyU+D/9wXqptvUV9zy3UCVWBZJMXNBsiirbK aTk2bmuSpklRIsPg0QEGBMTZ1+KgEMxHCEQ5O6nTqhYEJrGFtz98pyHvu0a9Fd6W tOweTzo30Z+Uqj1IbEqa9dhTtQ8O/uWdTceizdV3NTtb9+4KIT/g/lumW15LnQ+i UWPMJBtwpbbDCTgpnUIUsUjemz4ZLOm1w3y6PARKteYz6aD+OTJ4sLm8U43f2U2Z suuB9Sf8xHayD6dnv/eFuimTVgEKIwLHtIV2oKyIqStQ0Jys6ghEdMPZB0xQshE8 chXrX0n5gV7BXTSbsKuo/tZ48VFqDXeaNpJOISy+7HIhcJeT8AreSuzfZjlMBixZ 1j90o+S6q3fJ8m6U7/nFyittOU2u/90hgNdjA3/ysFydfWhi54ps85oXvGJrnTo6 NeR4PJPr6occogEPBRktNXRpsPe4HI+1qpVHey3UZ7Y0u10KUo3rclNxpXeQzzVP 28RTfLj/3hLuLSgMDli6gtquY7n+dgFI4a/Rr7MOHz9+PXIg4NR5farT2dkWGukm pq0wDSemWIjsvWr2xL3u/8JGJBbG5IQ97ifriAmHx23mMWoROl9IDhbeR/pzdFFK 8tQ0n/ap6qJbopx5vUuJLpL+XEvkT5JxtvmfRQFpSD0QCk8gSAlnKKbs1oaYDdyz 419Xke0B4QqRxg== =J1nm -END PGP SIGNATURE End Message ---
Bug#998359: marked as done (age fails reading passphrase-protected key files)
Your message dated Sat, 06 Nov 2021 23:33:32 + with message-id and subject line Bug#998359: fixed in age 1.0.0-1 has caused the Debian Bug report #998359, regarding age fails reading passphrase-protected key files 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.) -- 998359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998359 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: age Version: 1.0.0~rc1-2+b3 Severity: grave Justification: renders package unusable Dear Maintainer, this is how you can reproduce the bug: $ age-keygen | age -p > tmp/key.age Public key: age17sxjygr9yuvv7s5yd657gfw6v2c9597938ur2smug4u9fysrxdms2p9h0y Enter passphrase (leave empty to autogenerate a secure one): Using the autogenerated passphrase "dolphin-coffee-erase-table-denial-remain-orphan-gym-debris-episode". $ age -r age17sxjygr9yuvv7s5yd657gfw6v2c9597938ur2smug4u9fysrxdms2p9h0y -o /tmp/passwd.age /etc/passwd $ age -d -i tmp/key.age -o /tmp/passwd /tmp/passwd.age Error reading "tmp/key.age": failed to read "tmp/key.age": error at line 1: malformed secret key: separator '1' at invalid position: pos=20, len=21 [ Did age not do what you expected? Could an error be more useful? Tell us: https://filippo.io/age/report ] Being unable to use passphrase-protected key files renders this package unusable. This bug is not present in upstream v1.0.0. -- System Information: Debian Release: 11.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'proposed-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-9-amd64 (SMP w/1 CPU thread) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 age depends on: ii libc6 2.31-13+deb11u2 age recommends no packages. age suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: age Source-Version: 1.0.0-1 Done: Johan Fleury We believe that the bug you reported is fixed in the latest version of age, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Johan Fleury (supplier of updated age 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, 07 Nov 2021 00:09:19 +0100 Source: age Architecture: source Version: 1.0.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Go Packaging Team Changed-By: Johan Fleury Closes: 994069 998359 Changes: age (1.0.0-1) unstable; urgency=medium . [ Johan Fleury ] * New upstream version 1.0.0 (Closes: #994069, #998359) * d/control: reintroduce dependency to filippo.io/edwards25519 * d/control: declare compliance with policy v4.6.0 . [ Aloïs Micard ] * Install upstream manpage. Checksums-Sha1: f948397b50da405f49db379cffd4192ddb500d56 2023 age_1.0.0-1.dsc 954c2c492d0c4c859ac8f17c829f4b6bc79ba44d 59682 age_1.0.0.orig.tar.gz f02c39dd889ccb43e7803d14d66f088110be79fb 4228 age_1.0.0-1.debian.tar.xz 2e5e49f628687890372ef6a627dfc83d97beb155 6475 age_1.0.0-1_amd64.buildinfo Checksums-Sha256: fbe984eafa5abceb245fcac1d2ab0e8ee66a8f521e62e68af222481ece2b4f07 2023 age_1.0.0-1.dsc 8d27684f62f9dc74014035e31619e2e07f8b56257b1075560456cbf05ddbcfce 59682 age_1.0.0.orig.tar.gz 32590c4e9dcea570021e0945364bbe6157ab54ff35beaf9498f7937d5be26198 4228 age_1.0.0-1.debian.tar.xz 44210fb02ca32a764f05efcbe22a651ca0285071122ef054dad3819a809ad835 6475 age_1.0.0-1_amd64.buildinfo Files: 789aafaa3375693b0a8d94e942928bc8 2023 utils optional age_1.0.0-1.dsc f0c33cd6ed36890496ae6617fb523037 59682 utils optional age_1.0.0.orig.tar.gz 8d68bc49c07308f8b552d44e8dc272b7 4228 utils optional age_1.0.0-1.debian.tar.xz 8234daf9620a0ce6016598ebbddbef18 6475 utils optional age_1.0.0-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJEBAEBCgAuFiEECYc16JDXWgmzZBaOGg64LwcfXv4FAmGHDK4QHGFsb2lzQG1p Y2FyZC5sdQAKCRAaDrgvBx9e/oHfD/wKfcchpIk0EdzRshpZM3HPXJSye8lYLZG1 JtSfn5aNI9WsxObJntSjJzzAJIdYgD+3sdTMFRRDuPv7zUi/N+hv4XIFlje4N6ka
Bug#997230: marked as done (dateutils: FTBFS: yuck.c:68:10: fatal error: sys/sysctl.h: No such file or directory)
Your message dated Sat, 06 Nov 2021 23:33:45 + with message-id and subject line Bug#997230: fixed in dateutils 0.4.5-2 has caused the Debian Bug report #997230, regarding dateutils: FTBFS: yuck.c:68:10: fatal error: sys/sysctl.h: No such file or directory 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.) -- 997230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dateutils Version: 0.4.5-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -std=gnu11 -DHAVE_CONFIG_H -I. -I../src -D_POSIX_C_SOURCE=200809L > -D_XOPEN_SOURCE=700 -D_BSD_SOURCE -D_ALL_SOURCE -D_DARWIN_C_SOURCE > -D_NETBSD_SOURCE -DYUCK_TEMPLATE_PATH='"/<>/build-aux"' > -DWITH_SCMVER -DBOOTSTRAP -DWITH_SCMVER -Wdate-time -D_FORTIFY_SOURCE=2 -g > -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security-Wall -Wextra -Wsign-compare -Wno-char-subscripts > -Wundef -Wpacked -Wpointer-arith -Wshadow -Wmissing-declarations > -Wmissing-prototypes -Wbad-function-cast -Wcast-qual -Wcast-align -Wno-switch > -Wunused-function -Wunused-variable -Wunused-parameter -Wunused-value > -Wunused -Wmaybe-uninitialized -fdiagnostics-show-option -Wunknown-pragmas > -Wuninitialized -Wdeprecated -Wno-parentheses -Wstrict-aliasing > -Wunsuffixed-float-constants -static-libgcc -c -o yuck_bootstrap-yuck.o > `test -f 'yuck.c' || echo './'`yuck.c > In file included from /usr/include/unistd.h:25, > from yuck.c:53: > /usr/include/features.h:187:3: warning: #warning "_BSD_SOURCE and > _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] > 187 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use > _DEFAULT_SOURCE" > | ^~~ > yuck.c:68:10: fatal error: sys/sysctl.h: No such file or directory >68 | #include > | ^~ > compilation terminated. > make[3]: *** [Makefile:505: yuck_bootstrap-yuck.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/dateutils_0.4.5-1.1_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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: dateutils Source-Version: 0.4.5-2 Done: Thorsten Alteholz We believe that the bug you reported is fixed in the latest version of dateutils, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thorsten Alteholz (supplier of updated dateutils 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: Sat, 06 Nov 2021 22:59:01 +0200 Source: dateutils Architecture: source Version: 0.4.5-2 Distribution: unstable Urgency: medium Maintainer: Thorsten Alteholz Changed-By: Thorsten Alteholz Closes: 967979 997230 Changes: dateutils (0.4.5-2) unstable; urgency=medium . * debian/control: use dh13 * debian/control: bump standard to 4.6.0 (no changes) * debian/control: add Rules-Requires-Root: * debian/control: add build dependency for autoconf-archive * don't include sysctl.h anymore (Closes: #997230, #967979) (it is only needed on *BSD* anyway) Checksums-Sha1: 871cc040d0a24f5792931670384a083035f223af 2122 dateutils_0.4.5-2.dsc 8f194699d5ecddfed3fd3bae1f6d6bd8f77ea175 6612 dateutils_0.4.5-2.debian.tar.xz fd41c2cda8ae8b80ae307be4b001e087c26ee5ad 6798 dateutils_0.4.5-2_amd64.buildinfo Checksums-Sha256: 892b26a22f369d5ac042da109d374397def95e8dff4cc60a3bec9b42620b57da 2122 dateutils_0.4.5-2.dsc c6dcde2b7007ceb14036dafe9ffd28ea7a1ca9210738fe72e6987edc4db5a790 6612
Bug#997514: ctpl: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2
On Sat, 23 Oct 2021 22:42:41 +0200 Lucas Nussbaum wrote: > […] > > FAIL: tests.sh > > == > > > > ./tests.sh: 35: tempfile: not found Looks like it's breaking because `tempfile` is gone, but that's an easy fix I just committed upstream, see https://git.tuxfamily.org/ctpl/ctpl.git/commit/?id=932f7767af15592fc36137a868187e45dea80068 Regards, Colomban
Bug#998489: marked as done (xastir: FTBFS: configure.ac:35: error: AM_INIT_AUTOMAKE expanded multiple times)
Your message dated Sat, 06 Nov 2021 22:18:53 + with message-id and subject line Bug#998489: fixed in xastir 2.1.6-4 has caused the Debian Bug report #998489, regarding xastir: FTBFS: configure.ac:35: error: AM_INIT_AUTOMAKE expanded multiple times 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.) -- 998489: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998489 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: xastir Version: 2.1.6-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules binary > dh binary >dh_update_autotools_config >dh_autoreconf > aclocal: warning: couldn't open directory 'm4': No such file or directory > configure.ac:35: error: AM_INIT_AUTOMAKE expanded multiple times > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:26: the top level > /usr/share/aclocal-1.16/init.m4:29: AM_INIT_AUTOMAKE is expanded from... > configure.ac:35: the top level > autom4te: error: /usr/bin/m4 failed with exit status: 1 > aclocal: error: /usr/bin/autom4te failed with exit status: 1 > autoreconf: error: aclocal failed with exit status: 1 > dh_autoreconf: error: autoreconf -f -i returned exit code 1 > make: *** [debian/rules:6: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/xastir_2.1.6-3_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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: xastir Source-Version: 2.1.6-4 Done: tony mancill We believe that the bug you reported is fixed in the latest version of xastir, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated xastir 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: Sat, 06 Nov 2021 14:48:13 -0700 Source: xastir Architecture: source Version: 2.1.6-4 Distribution: unstable Urgency: medium Maintainer: Debian Hamradio Maintainers Changed-By: tony mancill Closes: 998489 Changes: xastir (2.1.6-4) unstable; urgency=medium . * Team upload . [ Debian Janitor ] * Remove constraints unnecessary since buster: + xastir-data: Drop versioned constraint on xastir in Replaces. + xastir-data: Drop versioned constraint on xastir in Breaks. . [ Daniele Forsi ] * d/patches: - Adapt upstream commit 60f90440 to our older version (Closes: #998489) . [ tony mancill ] * Bump Standards-Version to 4.6.0 * Use debhelper-compat 13 - Amend paths in d/xastir.docs and add d/not-installed * Remove outdated filespec from d/copyright Checksums-Sha1: c9794da3f20f4c1d7e26b14f3d6c010ed149c318 2330 xastir_2.1.6-4.dsc 3fa8267c41c7613eb7eace4ed25c8b50a684631e 21624 xastir_2.1.6-4.debian.tar.xz 72b55db55167a52b247fc2c69790865e43097636 10963 xastir_2.1.6-4_amd64.buildinfo Checksums-Sha256: 86445eb05e8f713543ca62c3fdc151e4bba8aaaedbfcd8720ebecbfbd8863998 2330 xastir_2.1.6-4.dsc 5ff136c81b09a6ac19405427ad07fb130b9be437ca5a8bad6743814e7ccb27b9 21624 xastir_2.1.6-4.debian.tar.xz 4d4cce2deb1eef8a24e189377f1333cfa787b47afea35007eafd45ede9f6c46b 10963 xastir_2.1.6-4_amd64.buildinfo Files: c5d15ee9bb985cc825ce6611e44c54ae 2330 hamradio optional xastir_2.1.6-4.dsc 283296442584f04ae3a64b244966d6ca 21624 hamradio optional xastir_2.1.6-4.debian.tar.xz e0ff451bd9a5eb068558e1210dec9994 10963 hamradio optional xastir_2.1.6-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAmGG+g4UHHRtYW5jaWxs
Bug#998605: marked as done (krita: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error)
Your message dated Sat, 06 Nov 2021 21:48:48 + with message-id and subject line Bug#998561: fixed in sip4 4.19.25+dfsg-3 has caused the Debian Bug report #998561, regarding krita: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error 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.) -- 998561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: krita Version: 1:4.4.8+dfsg-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' > [ 90%] Generating krita/sipkritapart0.cpp > cd /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip && > /usr/bin/cmake -E echo > > cd /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip && > /usr/bin/cmake -E touch > /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip/./krita/sipkritapart0.cpp > cd /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip && > /usr/bin/sip -t ALL -t WS_X11 -t Qt_5_15_0 -g -o -x PyKDE_QVector -n > PyQt5.sip -j 1 -c > /<>/obj-x86_64-linux-gnu/plugins/extensions/pykrita/sip/./krita > -I /usr/share/sip -I /usr/lib/python3/dist-packages/PyQt5/bindings -I > /<>/plugins/extensions/pykrita/sip/krita > /<>/plugins/extensions/pykrita/sip/krita/kritamod.sip > sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: > syntax error > make[3]: *** > [plugins/extensions/pykrita/sip/CMakeFiles/python_module_PyKrita_krita.dir/build.make:113: > plugins/extensions/pykrita/sip/krita/sipkritapart0.cpp] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/11/04/krita_4.4.8+dfsg-1_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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: sip4 Source-Version: 4.19.25+dfsg-3 Done: Dmitry Shachnev We believe that the bug you reported is fixed in the latest version of sip4, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Shachnev (supplier of updated sip4 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, 07 Nov 2021 00:17:25 +0300 Source: sip4 Architecture: source Version: 4.19.25+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Dmitry Shachnev Closes: 998561 Changes: sip4 (4.19.25+dfsg-3) unstable; urgency=medium . [ Jochen Sprickerhof ] * Add Provides: dh-sequence-sip3 to python3-sip-dev. . [ Dmitry Shachnev ] * Add a patch to make the parser not break on py_ssize_t_clean directive from SIP v6.4 (closes: #998561). Thanks Jochen Sprickerhof! Checksums-Sha1: 97230b2ddec4dcf509ad1e5ffeae033c42dae22e 2348 sip4_4.19.25+dfsg-3.dsc d7bd19efc2b5a81de0456b39c95079064763435a 17000 sip4_4.19.25+dfsg-3.debian.tar.xz 308b727000cc6b315d62a94d55eb0eab8a292717 6978 sip4_4.19.25+dfsg-3_source.buildinfo Checksums-Sha256: 10d34be9464877c0d7b531edb734a2295435107082da6eb168bd6dd9b2b2857e 2348 sip4_4.19.25+dfsg-3.dsc 1f80fc07743d031a0f4cc440ebe8b5469520b7b8e3e3d1e8aaa21f483db1c7c9 17000 sip4_4.19.25+dfsg-3.debian.tar.xz 695f1377d7eaddd22af4b4b55b407336822ed7737c6beeb62be804a4c8978aae 6978 sip4_4.19.25+dfsg-3_source.buildinfo Files: 23c1bd7bd0e9cd2ed6e99d46803f1c22 2348 devel optional sip4_4.19.25+dfsg-3.dsc eb509fdfade8364fa71c08aa0efe8845 17000 devel optional sip4_4.19.25+dfsg-3.debian.tar.xz 0729c975a7e4cfefc41250c2618cfb29 6978 devel optional
Bug#998595: marked as done (pyqwt3d: FTBFS: SIP failed to generate the C++ code.)
Your message dated Sat, 06 Nov 2021 21:48:48 +
with message-id
and subject line Bug#998561: fixed in sip4 4.19.25+dfsg-3
has caused the Debian Bug report #998561,
regarding pyqwt3d: FTBFS: SIP failed to generate the C++ code.
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.)
--
998561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998561
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyqwt3d
Version: 0.1.8-6
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211104 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> debian/rules build
> dh_testdir
> export QTDIR=/usr/share/qt5
> set -e ;\
> for py in 3.9 ; do \
> mkdir -p build/py$py-qt5; \
> cp -Rl `ls . |grep -v build|grep -v debian` build/py$py-qt5; \
> (cd build/py$py-qt5/configure;\
> python$py configure-qt5.py -5 -I /usr/include/qwtplot3d
> --extra-libs=qwtplot3d-qt5 \
>
> --sip-include-dirs=/usr/lib/python3/dist-packages/PyQt5/bindings/ \
> -D GL2PS_HAVE_ZLIB); \
> done
> sip: Deprecation warning: ../sip/OpenGL_Qt5_Module.sip:31: %Module version
> number should be specified using the 'version' argument
> sip: Deprecation warning: ../sip/Qwt3D_Qt5_Module.sip:31: %Module version
> number should be specified using the 'version' argument
> sip: /usr/lib/python3/dist-packages/PyQt5/bindings//QtCore/QtCoremod.sip:23:
> syntax error
> Command line options:
> {'debug': False,
> 'disable_numarray': False,
> 'disable_numeric': False,
> 'disable_numpy': False,
> 'excluded_features': [],
> 'extra_cflags': [],
> 'extra_cxxflags': [],
> 'extra_defines': ['GL2PS_HAVE_ZLIB'],
> 'extra_include_dirs': ['/usr/include/qwtplot3d'],
> 'extra_lflags': [],
> 'extra_lib_dirs': [],
> 'extra_libs': ['qwtplot3d-qt5'],
> 'jobs': '',
> 'module_install_path': '',
> 'modules': [],
> 'qt': 5,
> 'qwtplot3d_sources': '',
> 'sip_include_dirs': ['-I ../sip',
> '-I /usr/lib/python3/dist-packages/PyQt5/bindings/'],
> 'subdirs': [],
> 'timelines': [],
> 'trace': '',
> 'zlib_sources': ''}
>
> Found SIP-4.19.25.
>
> Found 'posix' operating system:
> 3.9.7 (default, Sep 24 2021, 09:43:00)
> [GCC 10.3.0]
>
> Found NumPy-1.19.5.
>
> Setup the OpenGL package build.
> -n PyQt5.sip -t Qt_5_15_0 -t WS_X11
> sip invokation:
> ('/usr/bin/sip -I /usr/share/sip/PyQt5 -n PyQt5.sip -t Qt_5_15_0 -t WS_X11 -b
> '
> 'tmp-OpenGL_Qt5/OpenGL_Qt5.sbf -c tmp-OpenGL_Qt5 '
> '../sip/OpenGL_Qt5_Module.sip')
> Copy tmp-OpenGL_Qt5/sipOpenGLcmodule.cpp -> OpenGL_Qt5/sipOpenGLcmodule.cpp.
> Copy tmp-OpenGL_Qt5/sipAPIOpenGL.h -> OpenGL_Qt5/sipAPIOpenGL.h.
> Copy tmp-OpenGL_Qt5/OpenGL_Qt5.sbf -> OpenGL_Qt5/OpenGL_Qt5.sbf.
> 3 file(s) lazily copied.
> Setup the Qwt3D package build.
> Extended options:
> {'debug': False,
> 'disable_numarray': False,
> 'disable_numeric': False,
> 'disable_numpy': False,
> 'excluded_features': ['-x HAS_QT3 -x HAS_QT4'],
> 'extra_cflags': [],
> 'extra_cxxflags': [],
> 'extra_defines': ['GL2PS_HAVE_ZLIB', 'HAS_NUMPY'],
> 'extra_include_dirs': ['/usr/include/qwtplot3d',
> '/usr/include/python3.9',
> '/usr/lib/python3/dist-packages/numpy/core/include',
> '/usr/include/x86_64-linux-gnu/qt5/Qt',
> '/usr/include/x86_64-linux-gnu/qt5/QtCore',
> '/usr/include/x86_64-linux-gnu/qt5/QtGui',
> '/usr/include/x86_64-linux-gnu/qt5/QtWidgets',
> '/usr/include/x86_64-linux-gnu/qt5/QtOpenGL',
> '/usr/include/x86_64-linux-gnu/qt5'],
> 'extra_lflags': [],
> 'extra_lib_dirs': [],
> 'extra_libs': ['qwtplot3d-qt5'],
> 'jobs': '',
> 'module_install_path': '/usr/lib/python3.9/dist-packages/PyQt5/Qwt3D',
> 'modules': [],
> 'opengl': 'OpenGL_Qt5',
> 'qt': 5,
> 'qwt3d': 'Qwt3D_Qt5',
> 'qwtplot3d_sources': '',
> 'sip_include_dirs': ['-I ../sip',
> '-I /usr/lib/python3/dist-packages/PyQt5/bindings/'],
> 'subdirs': ['Qwt3D_Qt5', 'OpenGL_Qt5'],
> 'timelines': [],
> 'trace': '',
> 'zlib_sources': ''}
>
> sip invokation:
> ('/usr/bin/sip -I /usr/share/sip/PyQt5 -n PyQt5.sip -t Qt_5_15_0 -t WS_X11 -b
> '
> 'tmp-Qwt3D_Qt5/qwt3d.sbf -c tmp-Qwt3D_Qt5 -I ../sip -I '
> '/usr/lib/python3/dist-packages/PyQt5/bindings/ -x HAS_QT3 -x HAS_QT4 '
> '../sip/Qwt3D_Qt5_Module.sip')
>
> SIP failed to generate the C++ code.
>
Bug#998561: marked as done (ros-rviz: FTBFS: call to 'sip' fails)
Your message dated Sat, 06 Nov 2021 21:48:48 + with message-id and subject line Bug#998561: fixed in sip4 4.19.25+dfsg-3 has caused the Debian Bug report #998561, regarding ros-rviz: FTBFS: call to 'sip' fails 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.) -- 998561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ros-rviz Version: 1.14.10+dfsg-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[3]: Entering directory '/<>/.pybuild/cpython3_3.9/build' > cd /<>/.pybuild/cpython3_3.9/build && /usr/bin/cmake -E > cmake_depends "Unix Makefiles" /<> > /<>/src/image_view /<>/.pybuild/cpython3_3.9/build > /<>/.pybuild/cpython3_3.9/build/src/image_view > /<>/.pybuild/cpython3_3.9/build/src/image_view/CMakeFiles/rviz_image_view.dir/DependInfo.cmake > --color= > [ 60%] Building CXX object > src/rviz/CMakeFiles/executable.dir/executable_autogen/mocs_compilation.cpp.o > cd /<>/.pybuild/cpython3_3.9/build/src/rviz && /usr/bin/c++ > -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK > -DBOOST_PROGRAM_OPTIONS_DYN_LINK -DBOOST_SYSTEM_DYN_LINK > -DBOOST_THREAD_DYN_LINK -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG > -DQT_NO_KEYWORDS -DQT_WIDGETS_LIB -DROSCONSOLE_BACKEND_LOG4CXX > -DROS_BUILD_SHARED_LIBS=1 -DROS_PACKAGE_NAME=\"rviz\" > -I/<>/.pybuild/cpython3_3.9/build/src/rviz/executable_autogen/include > -I/<>/.pybuild/cpython3_3.9/build/devel/include > -I/<>/src -I/<>/src/rviz/include -isystem > /usr/include/eigen3 -isystem /usr/include/OGRE -isystem > /usr/include/python3.9 -isystem /usr/include/xmlrpcpp -isystem > /usr/include/x86_64-linux-gnu/qt5 -isystem > /usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem > /usr/include/x86_64-linux-gnu/qt5/QtGui -isystem > /usr/include/x86_64-linux-gnu/qt5/QtCore -isystem > /usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -isystem > /usr/include/OGRE/Bites -isystem /usr/include/OGRE/Overlay -isystem > /usr/include/OGRE/RTShaderSystem -isystem /usr/include/OGRE/MeshLodGenerator > -isystem /usr/include/OGRE/Paging -isystem /usr/include/OGRE/Property > -isystem /usr/include/OGRE/Terrain -isystem /usr/include/OGRE/Volume -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++11 > -Wno-deprecated-declarations -fPIC -std=c++14 -MD -MT > src/rviz/CMakeFiles/executable.dir/executable_autogen/mocs_compilation.cpp.o > -MF CMakeFiles/executable.dir/executable_autogen/mocs_compilation.cpp.o.d -o > CMakeFiles/executable.dir/executable_autogen/mocs_compilation.cpp.o -c > /<>/.pybuild/cpython3_3.9/build/src/rviz/executable_autogen/mocs_compilation.cpp > make[3]: Leaving directory '/<>/.pybuild/cpython3_3.9/build' > make -f src/image_view/CMakeFiles/rviz_image_view.dir/build.make > src/image_view/CMakeFiles/rviz_image_view.dir/build > sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: > syntax error > Traceback (most recent call last): > File "/usr/share/python_qt_binding/cmake/sip_configure.py", line 127, in > > subprocess.check_call(cmd) > File "/usr/lib/python3.9/subprocess.py", line 373, in check_call > raise CalledProcessError(retcode, cmd) > subprocess.CalledProcessError: Command '['/usr/bin/sip', '-c', > '/<>/.pybuild/cpython3_3.9/build/sip/rviz_sip', '-b', > '/<>/.pybuild/cpython3_3.9/build/sip/rviz_sip/pyqtscripting.sbf', > '-I', '/usr/lib/python3/dist-packages/PyQt5/bindings', '-w', '-n', > 'PyQt5.sip', '-t', 'Qt_5_15_0', '-t', 'WS_X11', 'rviz.sip']' returned > non-zero exit status 1. > make[3]: Entering directory '/<>/.pybuild/cpython3_3.9/build' > make[3]: *** > [src/python_bindings/sip/CMakeFiles/librviz_sip.dir/build.make:111: > sip/rviz_sip/Makefile] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/11/04/ros-rviz_1.14.10+dfsg-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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message
Bug#998567: marked as done (qgis: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error)
Your message dated Sat, 06 Nov 2021 21:48:48 + with message-id and subject line Bug#998561: fixed in sip4 4.19.25+dfsg-3 has caused the Debian Bug report #998561, regarding qgis: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error 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.) -- 998561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: qgis Version: 3.16.12+dfsg-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > If this sounds wrong, possibly the target language is not set or recognized. > [4601/4714 97%]cd /<>/debian/build/i18n && > /usr/lib/qt5/bin/lrelease -silent /<>/i18n/qgis_uk.ts -qm > /<>/debian/build/output/i18n/qgis_uk.qm > Removed plural forms as the target language has less forms. > If this sounds wrong, possibly the target language is not set or recognized. > [4602/4714 97%]cd /<>/debian/build/i18n && > /usr/lib/qt5/bin/lrelease -silent /<>/i18n/qgis_sv.ts -qm > /<>/debian/build/output/i18n/qgis_sv.qm > [4603/4714 97%]cd /<>/python && /usr/bin/cmake -E > make_directory /<>/debian/build/output/python/qgis && > /usr/bin/cmake -E copy __init__.py > /<>/debian/build/output/python/qgis && cd > /<>/python && /usr/bin/cmake -E make_directory > /<>/debian/build/output/python/qgis && /usr/bin/cmake -E copy > utils.py /<>/debian/build/output/python/qgis && cd > /<>/python && /usr/bin/cmake -E make_directory > /<>/debian/build/output/python/qgis && /usr/bin/cmake -E copy > user.py /<>/debian/build/output/python/qgis > [4604/4714 97%]cd /<>/debian/build/python && /usr/bin/cmake -E > echo && /usr/bin/cmake -E touch > /<>/debian/build/python/core/sip_corepart0.cpp > /<>/debian/build/python/core/sip_corepart1.cpp > /<>/debian/build/python/core/sip_corepart2.cpp > /<>/debian/build/python/core/sip_corepart3.cpp > /<>/debian/build/python/core/sip_corepart4.cpp > /<>/debian/build/python/core/sip_corepart5.cpp > /<>/debian/build/python/core/sip_corepart6.cpp > /<>/debian/build/python/core/sip_corepart7.cpp > /<>/debian/build/python/core/sip_corepart8.cpp > /<>/debian/build/python/core/sip_corepart9.cpp > /<>/debian/build/python/core/sip_corepart10.cpp && /usr/bin/sip > -w -e -x TESTS -x ANDROID -x ARM -x MOBILITY_LOCATION -x VECTOR_MAPPED_TYPE > -n PyQt5.sip -t Qt_5_15_0 -t WS_X11 -g -o -a > /<>/debian/build/python/qgis.core.api -n PyQt5.sip -y > /<>/debian/build/output/python/qgis/_core.pyi -j 11 -c > /<>/debian/build/python/core -I > /<>/debian/build/python/core -I > /usr/lib/python3/dist-packages/PyQt5/bindings -I /<>/python > /<>/debian/build/python/core/core.sip > FAILED: python/core/sip_corepart0.cpp python/core/sip_corepart1.cpp > python/core/sip_corepart2.cpp python/core/sip_corepart3.cpp > python/core/sip_corepart4.cpp python/core/sip_corepart5.cpp > python/core/sip_corepart6.cpp python/core/sip_corepart7.cpp > python/core/sip_corepart8.cpp python/core/sip_corepart9.cpp > python/core/sip_corepart10.cpp > /<>/debian/build/python/core/sip_corepart0.cpp > /<>/debian/build/python/core/sip_corepart1.cpp > /<>/debian/build/python/core/sip_corepart2.cpp > /<>/debian/build/python/core/sip_corepart3.cpp > /<>/debian/build/python/core/sip_corepart4.cpp > /<>/debian/build/python/core/sip_corepart5.cpp > /<>/debian/build/python/core/sip_corepart6.cpp > /<>/debian/build/python/core/sip_corepart7.cpp > /<>/debian/build/python/core/sip_corepart8.cpp > /<>/debian/build/python/core/sip_corepart9.cpp > /<>/debian/build/python/core/sip_corepart10.cpp > cd /<>/debian/build/python && /usr/bin/cmake -E echo && > /usr/bin/cmake -E touch > /<>/debian/build/python/core/sip_corepart0.cpp > /<>/debian/build/python/core/sip_corepart1.cpp > /<>/debian/build/python/core/sip_corepart2.cpp > /<>/debian/build/python/core/sip_corepart3.cpp > /<>/debian/build/python/core/sip_corepart4.cpp > /<>/debian/build/python/core/sip_corepart5.cpp > /<>/debian/build/python/core/sip_corepart6.cpp > /<>/debian/build/python/core/sip_corepart7.cpp > /<>/debian/build/python/core/sip_corepart8.cpp > /<>/debian/build/python/core/sip_corepart9.cpp > /<>/debian/build/python/core/sip_corepart10.cpp && /usr/bin/sip > -w -e -x TESTS -x ANDROID -x ARM -x MOBILITY_LOCATION -x VECTOR_MAPPED_TYPE > -n PyQt5.sip -t Qt_5_15_0 -t WS_X11 -g -o -a >
Processed: Reassigning #998561, #998567, #998595 and #998605 to sip4
Processing commands for cont...@bugs.debian.org: > reassign 998561 sip-dev 4.19.25+dfsg-2 Bug #998561 [src:ros-rviz] ros-rviz: FTBFS: call to 'sip' fails Bug reassigned from package 'src:ros-rviz' to 'sip-dev'. No longer marked as found in versions ros-rviz/1.14.10+dfsg-2. Ignoring request to alter fixed versions of bug #998561 to the same values previously set Bug #998561 [sip-dev] ros-rviz: FTBFS: call to 'sip' fails Marked as found in versions sip4/4.19.25+dfsg-2. > reassign 998567 sip-dev 4.19.25+dfsg-2 Bug #998567 [src:qgis] qgis: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error Bug reassigned from package 'src:qgis' to 'sip-dev'. No longer marked as found in versions qgis/3.16.12+dfsg-1. Ignoring request to alter fixed versions of bug #998567 to the same values previously set Bug #998567 [sip-dev] qgis: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error Marked as found in versions sip4/4.19.25+dfsg-2. > reassign 998595 sip-dev 4.19.25+dfsg-2 Bug #998595 [src:pyqwt3d] pyqwt3d: FTBFS: SIP failed to generate the C++ code. Bug reassigned from package 'src:pyqwt3d' to 'sip-dev'. No longer marked as found in versions pyqwt3d/0.1.8-6. Ignoring request to alter fixed versions of bug #998595 to the same values previously set Bug #998595 [sip-dev] pyqwt3d: FTBFS: SIP failed to generate the C++ code. Marked as found in versions sip4/4.19.25+dfsg-2. > reassign 998605 sip-dev 4.19.25+dfsg-2 Bug #998605 [src:krita] krita: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error Bug reassigned from package 'src:krita' to 'sip-dev'. No longer marked as found in versions krita/1:4.4.8+dfsg-1. Ignoring request to alter fixed versions of bug #998605 to the same values previously set Bug #998605 [sip-dev] krita: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error Marked as found in versions sip4/4.19.25+dfsg-2. > merge 998561 998567 998595 998605 Bug #998561 [sip-dev] ros-rviz: FTBFS: call to 'sip' fails Bug #998595 [sip-dev] pyqwt3d: FTBFS: SIP failed to generate the C++ code. Added tag(s) upstream and pending. Bug #998567 [sip-dev] qgis: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error Added tag(s) pending. Bug #998561 [sip-dev] ros-rviz: FTBFS: call to 'sip' fails Added tag(s) upstream. Bug #998605 [sip-dev] krita: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error Added tag(s) upstream and pending. Merged 998561 998567 998595 998605 > affects 998561 + src:krita src:pyqwt3d src:qgis src:ros-rviz Bug #998561 [sip-dev] ros-rviz: FTBFS: call to 'sip' fails Bug #998567 [sip-dev] qgis: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error Bug #998595 [sip-dev] pyqwt3d: FTBFS: SIP failed to generate the C++ code. Bug #998605 [sip-dev] krita: FTBFS: sip: /usr/lib/python3/dist-packages/PyQt5/bindings/QtCore/QtCoremod.sip:23: syntax error Added indication that 998561 affects src:krita, src:pyqwt3d, src:qgis, and src:ros-rviz Added indication that 998567 affects src:krita, src:pyqwt3d, src:qgis, and src:ros-rviz Added indication that 998595 affects src:krita, src:pyqwt3d, src:qgis, and src:ros-rviz Added indication that 998605 affects src:krita, src:pyqwt3d, src:qgis, and src:ros-rviz > thanks Stopping processing here. Please contact me if you need assistance. -- 998561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998561 998567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998567 998595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998595 998605: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998605 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#998561 marked as pending in sip4
Processing control commands: > tag -1 pending Bug #998561 [src:ros-rviz] ros-rviz: FTBFS: call to 'sip' fails Added tag(s) pending. -- 998561: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998561 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998561: marked as pending in sip4
Control: tag -1 pending Hello, Bug #998561 in sip4 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/sip4/-/commit/c4fba96da08000fad9479f05afa548c4550b85da Add a patch to make the parser not break on py_ssize_t_clean directive. Closes: #998561. Thanks Jochen Sprickerhof! (this message was generated automatically) -- Greetings https://bugs.debian.org/998561
Bug#995021: marked as done (osmnx: autopkgtest regression on armhf: iteration over a 0-d array)
Your message dated Sat, 6 Nov 2021 22:08:53 +0100
with message-id <302c150e-bb8a-f226-ba1c-312a14eae...@debian.org>
and subject line Re: osmnx: autopkgtest regression on armhf: iteration over a
0-d array
has caused the Debian Bug report #995021,
regarding osmnx: autopkgtest regression on armhf: iteration over a 0-d array
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.)
--
995021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995021
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: osmnx
Version: 1.1.1+ds-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
With a recent upload of osmnx the autopkgtest of osmnx fails in testing
on armhf when that autopkgtest is run with the binary packages of osmnx
from unstable. It passes when run with only packages from testing. In
tabular form:
passfail
osmnx from testing1.1.1+ds-2
all others from testingfrom testing
I copied some of the output at the bottom of this report. On top of the
failure, you test seems to be sending requests to the internet, please
use the needs-internet restriction [0] to mark is as such.
Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?
More information about this bug and the reason for filing it can be found on
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
Paul
[0]
https://salsa.debian.org/ci-team/autopkgtest/-/blob/master/doc/README.package-tests.rst
[1] https://qa.debian.org/excuses.php?package=osmnx
https://ci.debian.net/data/autopkgtest/testing/armhf/o/osmnx/15474259/log.gz
=== FAILURES
===
test_elevation
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "/usr/lib/python3.9/multiprocessing/pool.py", line 125, in worker
result = (True, func(*args, **kwds))
File "/usr/lib/python3.9/multiprocessing/pool.py", line 51, in starmapstar
return list(itertools.starmap(args[0], args[1]))
File
"/tmp/autopkgtest-lxc.2hzrzn35/downtmp/build.elV/src/osmnx/elevation.py", line
49, in _query_raster
return zip(nodes.index, values)
TypeError: iteration over a 0-d array
"""
The above exception was the direct cause of the following exception:
def test_elevation():
G = ox.graph_from_address(address=address, dist=500,
dist_type="bbox", network_type="bike")
rasters = list(Path("tests/input_data").glob("elevation*.tif"))
# add node elevations from a single raster file (some nodes will
be null)
G = ox.elevation.add_node_elevations_raster(G, rasters[0], cpus=1)
# add node elevations from multiple raster files
> G = ox.elevation.add_node_elevations_raster(G, rasters)
/usr/share/doc/python-osmnx-doc/examples/tests/test_osmnx.py:201:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
osmnx/elevation.py:98: in add_node_elevations_raster
results = sma.get()
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
_ _ _ _
self = , timeout = None
def get(self, timeout=None):
self.wait(timeout)
if not self.ready():
raise TimeoutError
if self._success:
return self._value
else:
> raise self._value
E TypeError: iteration over a 0-d array
/usr/lib/python3.9/multiprocessing/pool.py:771: TypeError
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Version: 1.1.1+ds-5
Hi,
On Wed, 3 Nov 2021 20:46:03 +0100 Paul Gevers wrote:
> Hi Jerome,
>
> On 03-11-2021 19:11, Jerome BENOIT wrote:
> > On Mon, 1 Nov 2021 20:49:58 +0100 Paul Gevers wrote:
> >> Is this run on all cores? Our armhf worker has 160 cores, so you may be
> >> running into limits you didn't expect.
> >
> > The upstream maintainer would like to know the number of cpus
> > from a Python shell.
> >
> import multiprocessing as mp; print(mp.cpu_count());
> >
> > Can you get this information ?
> > In fact, I am curious to know it as well.
>
> >>> import multiprocessing as mp; print(mp.cpu_count())
> 160
The latest version seems to be all right.
Paul
OpenPGP_signature
Description: OpenPGP digital signature
--- End Message ---
Bug#998703: src:gnuastro: fails to migrate to testing for too long: ftbfs on mips64el
Dear Paul, Thank you very much for noticing this and marking the bug as fixed. Also, I really appreciate the great explanation of the significance of such situations, I completely agree. The delay originated from the Debian version freezing: version 0.15 of Gnuastro came in that time slot (so it couldn't be updated in Debian). By the time the freeze was lifted, Gnuastro had significantly grown (and almost ready for version 0.16). But we pushed version 0.15 only to keep continuity. It was only after uploading version 0.15 that we noticed the bug in 'mips64el'. So we fixed it and pushed it with all the other bug fixes that had been found as version 0.15.54. Because the library had changed in this time, the new upload went to the NEW stack (on September 22nd). However, it was stuck in the NEW list for about 1.5 months (with one rejection due to bad copyright statement that was immediately fixed and re-submitted). Ultimately it was approved this morning! Version 0.16 of Gnuastro is already released upstream [1], so as soon as Gnuastro 0.15.54 passes on all CPU architectures in the experimental branch [2], we will upload version 0.16 to 'testing'. Thanks again, Mohammad [1] https://lists.gnu.org/archive/html/info-gnuastro/2021-10/msg0.html [2] https://buildd.debian.org/status/package.php?p=gnuastro=experimental
Bug#998707: pcs: autopkgtest needs update for new version of pacemaker: error and warning message text changed
Source: pcs Version: 0.10.8-1 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, pacema...@packages.debian.org Tags: sid bookworm User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:pacemaker Dear maintainer(s), With a recent upload of pacemaker the autopkgtest of pcs fails in testing when that autopkgtest is run with the binary packages of pacemaker from unstable. It passes when run with only packages from testing. In tabular form: passfail pacemaker from testing2.1.1-2 pcsfrom testing0.10.8-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of pacemaker to testing [1]. Of course, pacemaker shouldn't just break your autopkgtest (or even worse, your package), but it seems to me that the change in pacemaker was intended and your package needs to update to the new situation. If this is a real problem in your package (and not only in your autopkgtest), the right binary package(s) from pacemaker should really add a versioned Breaks on the unfixed version of (one of your) package(s). Note: the Breaks is nice even if the issue is only in the autopkgtest as it helps the migration software to figure out the right versions to combine in the tests. More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=pacemaker https://ci.debian.net/data/autopkgtest/testing/amd64/p/pcs/16475622/log.gz == FAIL: test_fail_when_nonexisting_agent (pcs_test.tier1.cib_resource.test_create.FailOrWarn) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tier1/cib_resource/test_create.py", line 934, in test_fail_when_nonexisting_agent self.assert_pcs_fail( File "/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tools/assertions.py", line 93, in assert_pcs_fail self.assert_pcs_result( File "/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tools/assertions.py", line 162, in assert_pcs_result self.fail( AssertionError: Stdout does not match the expected regexp command: ['resource', 'create', 'R', 'ocf:heartbeat:NoExisting'] regexp: ^Error: Agent 'ocf:heartbeat:NoExisting' is not installed or does not provide valid metadata:( crm_resource:)? Metadata query for ocf:heartbeat:NoExisting failed: (-5|Input/output error)(, Error performing operation: Input/output error)?, use --force to override $ (flags: MULTILINE, UNICODE) Full stdout: Error: Agent 'ocf:heartbeat:NoExisting' is not installed or does not provide valid metadata: crm_resource: Metadata query for ocf:heartbeat:NoExisting failed: No such device or address, Error performing operation: No such object, use --force to override == FAIL: test_warn_when_forcing_noexistent_agent (pcs_test.tier1.cib_resource.test_create.FailOrWarn) -- Traceback (most recent call last): File "/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tier1/cib_resource/test_create.py", line 952, in test_warn_when_forcing_noexistent_agent self.assert_effect( File "/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tools/cib.py", line 91, in assert_effect self.assert_effect_single( File "/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tools/cib.py", line 60, in assert_effect_single self.assert_pcs_success( File "/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tools/assertions.py", line 81, in assert_pcs_success self.assert_pcs_result( File "/tmp/autopkgtest-lxc.pw0aw2ju/downtmp/build.FKF/src/pcs_test/tools/assertions.py", line 162, in assert_pcs_result self.fail( AssertionError: Stdout does not match the expected regexp command: ['resource', 'create', 'R', 'ocf:heartbeat:NoExisting', '--force'] regexp: ^Warning: Agent 'ocf:heartbeat:NoExisting' is not installed or does not provide valid metadata:( crm_resource:)? Metadata query for ocf:heartbeat:NoExisting failed: (-5|Input/output error)(, Error performing operation: Input/output error)? $ (flags: MULTILINE, UNICODE) Full stdout: Warning: Agent 'ocf:heartbeat:NoExisting' is not installed or does not provide valid metadata: crm_resource: Metadata query for ocf:heartbeat:NoExisting failed: No such device or address, Error performing operation: No such object == FAIL: test_error_when_not_valid_agent (pcs_test.tier1.cib_resource.test_stonith_create.PlainStonith)
Processed: pcs: autopkgtest needs update for new version of pacemaker: error and warning message text changed
Processing control commands: > affects -1 src:pacemaker Bug #998707 [src:pcs] pcs: autopkgtest needs update for new version of pacemaker: error and warning message text changed Added indication that 998707 affects src:pacemaker -- 998707: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998707 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998706: git breaks mercurial autopkgtest: Failed test-convert-git.t: output changed
Source: git, mercurial Control: found -1 git/1:2.33.1-1 Control: found -1 mercurial/5.9.3-1 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of git the autopkgtest of mercurial fails in testing when that autopkgtest is run with the binary packages of git from unstable. It passes when run with only packages from testing. In tabular form: passfail gitfrom testing1:2.33.1-1 mercurial from testing5.9.3-1 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of git to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=git https://ci.debian.net/data/autopkgtest/testing/amd64/m/mercurial/16479536/log.gz --- /tmp/autopkgtest-lxc.z9mlql5c/downtmp/build.H05/src/tests/test-convert-git.t +++ /tmp/autopkgtest-lxc.z9mlql5c/downtmp/build.H05/src/tests/test-convert-git.t.err @@ -51,43 +51,40 @@ $ commit -a -m t4.2 $ git checkout master >/dev/null 2>/dev/null $ git pull --no-commit . other > /dev/null 2>/dev/null + [128] $ commit -m 'Merge branch other' + git commit error $ cd .. $ hg convert --config extensions.progress= --config progress.assume-tty=1 \ > --config progress.delay=0 --config progress.changedelay=0 \ > --config progress.refresh=0 --config progress.width=60 \ > --config progress.format='topic, bar, number' --datesort git-repo \r (no-eol) (esc) - scanning [==> ] 1/6\r (no-eol) (esc) - scanning [=> ] 2/6\r (no-eol) (esc) - scanning [=> ] 3/6\r (no-eol) (esc) - scanning [> ] 4/6\r (no-eol) (esc) - scanning [===>] 5/6\r (no-eol) (esc) - scanning [===>] 6/6\r (no-eol) (esc) - \r (no-eol) (esc) - \r (no-eol) (esc) - converting [ ] 0/6\r (no-eol) (esc) + scanning [===>] 1/5\r (no-eol) (esc) + scanning [> ] 2/5\r (no-eol) (esc) + scanning [=> ] 3/5\r (no-eol) (esc) + scanning [==> ] 4/5\r (no-eol) (esc) + scanning [===>] 5/5\r (no-eol) (esc) + \r (no-eol) (esc) + \r (no-eol) (esc) + converting [ ] 0/5\r (no-eol) (esc) getting files [==>] 1/2\r (no-eol) (esc) getting files [==>] 2/2\r (no-eol) (esc) \r (no-eol) (esc) \r (no-eol) (esc) - converting [==> ] 1/6\r (no-eol) (esc) + converting [===> ] 1/5\r (no-eol) (esc) getting files [==>] 1/1\r (no-eol) (esc) \r (no-eol) (esc) \r (no-eol) (esc) - converting [=>] 2/6\r (no-eol) (esc) + converting [===> ] 2/5\r (no-eol) (esc) getting files [==>] 1/1\r (no-eol) (esc) \r (no-eol) (esc) \r (no-eol) (esc) - converting [> ] 3/6\r (no-eol) (esc) + converting [> ] 3/5\r (no-eol) (esc) getting files [==>] 1/1\r (no-eol) (esc) \r (no-eol) (esc) \r (no-eol) (esc) - converting [===> ] 4/6\r (no-eol) (esc) - getting files [==>] 1/1\r (no-eol) (esc) - \r (no-eol) (esc) - \r (no-eol) (esc) - converting [==> ] 5/6\r (no-eol) (esc) + converting [> ] 4/5\r (no-eol) (esc) getting files [==>] 1/1\r (no-eol) (esc)
Processed: git breaks mercurial autopkgtest: Failed test-convert-git.t: output changed
Processing control commands: > found -1 git/1:2.33.1-1 Bug #998706 [src:git, src:mercurial] git breaks mercurial autopkgtest: Failed test-convert-git.t: output changed Marked as found in versions git/1:2.33.1-1. > found -1 mercurial/5.9.3-1 Bug #998706 [src:git, src:mercurial] git breaks mercurial autopkgtest: Failed test-convert-git.t: output changed Marked as found in versions mercurial/5.9.3-1. -- 998706: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998706 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998704: src:lintian-brush: fails to migrate to testing for too long: blocked by breezy
Source: lintian-brush Version: 0.109 Severity: serious Control: close -1 0.114 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:lintian-brush has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=lintian-brush OpenPGP_signature Description: OpenPGP digital signature
Processed: src:lintian-brush: fails to migrate to testing for too long: blocked by breezy
Processing control commands: > close -1 0.114 Bug #998704 [src:lintian-brush] src:lintian-brush: fails to migrate to testing for too long: blocked by breezy Marked as fixed in versions lintian-brush/0.114. Bug #998704 [src:lintian-brush] src:lintian-brush: fails to migrate to testing for too long: blocked by breezy Marked Bug as done -- 998704: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998704 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:gnuastro: fails to migrate to testing for too long: ftbfs on mips64el
Processing control commands: > close -1 0.15-1 Bug #998703 [src:gnuastro] src:gnuastro: fails to migrate to testing for too long: ftbfs on mips64el Marked as fixed in versions gnuastro/0.15-1. Bug #998703 [src:gnuastro] src:gnuastro: fails to migrate to testing for too long: ftbfs on mips64el Marked Bug as done -- 998703: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998703 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998703: src:gnuastro: fails to migrate to testing for too long: ftbfs on mips64el
Source: gnuastro Version: 0.14-1 Severity: serious Control: close -1 0.15-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:gnuastro has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=gnuastro OpenPGP_signature Description: OpenPGP digital signature
Processed: update the bts with the correct meta info
Processing commands for cont...@bugs.debian.org:
> reassign 994257 src:django-ldapdb 1.5.1-2
Bug #994257 {Done: Carsten Schoenert }
[src:python-django, src:django-ldapdb] python-django breaks django-ldapdb
autopkgtest: 'Field' object has no attribute 'attname'
Bug reassigned from package 'src:python-django, src:django-ldapdb' to
'src:django-ldapdb'.
No longer marked as found in versions django-ldapdb/1.5.1-2 and
python-django/2:3.2.7-4.
No longer marked as fixed in versions django-ldapdb/1.5.1-3.
Bug #994257 {Done: Carsten Schoenert }
[src:django-ldapdb] python-django breaks django-ldapdb autopkgtest: 'Field'
object has no attribute 'attname'
Marked as found in versions django-ldapdb/1.5.1-2.
> fixed 994257 1.5.1-3
Bug #994257 {Done: Carsten Schoenert }
[src:django-ldapdb] python-django breaks django-ldapdb autopkgtest: 'Field'
object has no attribute 'attname'
Marked as fixed in versions django-ldapdb/1.5.1-3.
> affects 994257 src:python-django
Bug #994257 {Done: Carsten Schoenert }
[src:django-ldapdb] python-django breaks django-ldapdb autopkgtest: 'Field'
object has no attribute 'attname'
Added indication that 994257 affects src:python-django
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
994257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994257
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#994266 closed by Debian FTP Masters (reply to Luca Boccassi ) (Bug#994266: fixed in azure-cli 2.30.0-1)
Processing commands for cont...@bugs.debian.org:
> reassign 994266 src:azure-cli 2.18.0-2
Bug #994266 {Done: Luca Boccassi } [src:pyjwt, src:azure-cli]
pyjwt breaks azure-cli autopkgtest: Could not deserialize key data. The data
may be in an incorrect format or it may be encrypted with an unsupported
algorithm.
Bug reassigned from package 'src:pyjwt, src:azure-cli' to 'src:azure-cli'.
No longer marked as found in versions pyjwt/2.1.0-1 and azure-cli/2.18.0-2.
No longer marked as fixed in versions azure-cli/2.30.0-1.
Bug #994266 {Done: Luca Boccassi } [src:azure-cli] pyjwt
breaks azure-cli autopkgtest: Could not deserialize key data. The data may be
in an incorrect format or it may be encrypted with an unsupported algorithm.
Marked as found in versions azure-cli/2.18.0-2.
> fixed 994266 2.30.0-1
Bug #994266 {Done: Luca Boccassi } [src:azure-cli] pyjwt
breaks azure-cli autopkgtest: Could not deserialize key data. The data may be
in an incorrect format or it may be encrypted with an unsupported algorithm.
Marked as fixed in versions azure-cli/2.30.0-1.
> affects 994266 src:pyjwt
Bug #994266 {Done: Luca Boccassi } [src:azure-cli] pyjwt
breaks azure-cli autopkgtest: Could not deserialize key data. The data may be
in an incorrect format or it may be encrypted with an unsupported algorithm.
Added indication that 994266 affects src:pyjwt
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
994266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#998415: [Pkg-rust-maintainers] Bug#998415: With a recent upload of rust-serde the autopkgtest of rust-debcargo, fails in testing when that autopkgtest is run with the binary packages, of rust-serd
Hi Ximin, On 05-11-2021 21:43, Ximin Luo wrote: > In other words, I don't see what value these bug reports are adding. Most maintainers appreciate them. I'll try to remember to *not* file them for rust packages anymore. Please remember to resolve these issues in a timely fashion thou. Being out-of-sync between unstable and testing for more than 60 days *is* considered an RC (serious) bug [1]. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html OpenPGP_signature Description: OpenPGP digital signature
Bug#992973: marked as done (plib: CVE-2021-38714)
Your message dated Sat, 06 Nov 2021 19:32:22 + with message-id and subject line Bug#992973: fixed in plib 1.8.5-8+deb10u1 has caused the Debian Bug report #992973, regarding plib: CVE-2021-38714 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.) -- 992973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: plib Version: 1.8.5-8 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://sourceforge.net/p/plib/bugs/55/ X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for plib. CVE-2021-38714[0]: | In Plib through 1.85, there is an integer overflow vulnerability that | could result in arbitrary code execution. The vulnerability is found | in ssgLoadTGA() function in src/ssg/ssgLoadTGA.cxx file. The severity of the this bug is set op purpose higher as it is probably warranted. There is the following reason for that: plib is orphaned in Debian for a while, it is obsoleted and unmaintained upstream as well. Ideally it get's removed from Debian from the next release, but thee would be some revers dependencies issues to be solved, making it imposssible for now to remove the package: | Checking reverse dependencies... | # Broken Depends: | crrcsim: crrcsim [amd64 arm64 armhf i386 mips64el mipsel ppc64el s390x] | flightgear: flightgear | openuniverse: openuniverse | stormbaancoureur: stormbaancoureur | torcs: torcs | | # Broken Build-Depends: | crrcsim: libplib-dev | flightgear: libplib-dev | torcs: libplib-dev | | Dependency problem found. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-38714 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38714 [1] https://sourceforge.net/p/plib/bugs/55/ Regards, Salvatore --- End Message --- --- Begin Message --- Source: plib Source-Version: 1.8.5-8+deb10u1 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of plib, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated plib 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, 17 Oct 2021 14:56:13 +0200 Source: plib Architecture: source Version: 1.8.5-8+deb10u1 Distribution: buster Urgency: medium Maintainer: Debian QA Group Changed-By: Anton Gladky Closes: 992973 Changes: plib (1.8.5-8+deb10u1) buster; urgency=medium . * Prevent integer overflow in ssgLoadTGA() function. CVE-2021-38714 (Closes: #992973) Checksums-Sha1: ad89f666cb479e05049f7dc29aadfbb5de52d3d3 2009 plib_1.8.5-8+deb10u1.dsc c2cf7e3e1e58f7b63dae4bb21e4fa82c3e4d4cfc 779133 plib_1.8.5.orig.tar.gz 404b0fcb0fe7baa1b9153c688648cd9ee63e4552 11392 plib_1.8.5-8+deb10u1.debian.tar.xz 71635ac173ab2097e9c5879ceefd00330e2302fc 8297 plib_1.8.5-8+deb10u1_source.buildinfo Checksums-Sha256: 36ca02c4ede8fbf8c42a3d9b957cb29080acb4db76dd00cf4cf2123092f8c3bb 2009 plib_1.8.5-8+deb10u1.dsc 485b22bf6fdc0da067e34ead5e26f002b76326f6371e2ae006415dea6a380a32 779133 plib_1.8.5.orig.tar.gz c6c89fda43270ddd4dff1a7a4510fe3c91ef7b82a7f55ca80a198c8f882382cd 11392 plib_1.8.5-8+deb10u1.debian.tar.xz 084aef954ef296373fa62a431d61811a9b0748d3044360fcf010319c230b73d0 8297 plib_1.8.5-8+deb10u1_source.buildinfo Files: b10f61b9cafb3f36df74705acd284402 2009 devel extra plib_1.8.5-8+deb10u1.dsc 47a6fbf63668c1eed631024038b2ea90 779133 devel extra plib_1.8.5.orig.tar.gz 6c16bd3d10233ff478c8df5999e91e24 11392 devel extra plib_1.8.5-8+deb10u1.debian.tar.xz 0874ed3408018f706118ea4e71868952 8297 devel extra plib_1.8.5-8+deb10u1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmFsIBAACgkQ0+Fzg8+n /wbotQ/+PNW/WJuVANbDKMRInV0kYS3eMJ+Uyz0Y1j43geTjjzwnkw4c0wr6VR93 zfh9K6HhvBY+c0EDhIIJvwBZJAwuUvB9jkk0qmvdccy6BJ7V3bNNJIyOYAm+I+3T
Bug#993622: marked as done (python3-open3d: Missing dependency on python3-numpy)
Your message dated Sat, 06 Nov 2021 19:17:31 + with message-id and subject line Bug#993622: fixed in open3d 0.9.0+ds-5+deb11u1 has caused the Debian Bug report #993622, regarding python3-open3d: Missing dependency on python3-numpy 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.) -- 993622: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-open3d Version: 0.9.0+ds-5+b2 Severity: normal X-Debbugs-Cc: slor...@openrobotics.org Dear Maintainer, It appears python3-open3d is missing a dependency on python3-numpy. The module can't be imported until it's manually installed. On a fresh bullseye container I installed python3-open3d bullseye:root> apt install libopen3d-dev/stable libopen3d0d/stable python3-open3d/stable Reading package lists... Done Building dependency tree... Done Reading state information... Done Selected version '0.9.0+ds-5+b2' (Debian:11.0/stable [amd64]) for 'libopen3d-dev' Selected version '0.9.0+ds-5+b2' (Debian:11.0/stable [amd64]) for 'libopen3d0d' Selected version '0.9.0+ds-5+b2' (Debian:11.0/stable [amd64]) for 'python3-open3d' ... But I encountered an ImportError: >>> import open3d Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3/dist-packages/open3d/__init__.py", line 3, in from .open3d import * ImportError: ModuleNotFoundError: No module named 'numpy' So I installed python3-numpy, and afterwards I was able to import open3d. >>> import open3d >>> Would you be willing to add this dependency to the Debian package? Cheers, Shane -- System Information: Debian Release: 11.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 5.11.0-27-generic (SMP w/24 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: unable to detect Versions of packages python3-open3d depends on: ii libc62.31-13 ii libgcc-s110.2.1-6 ii libopen3d0d 0.9.0+ds-5+b2 ii libstdc++6 10.2.1-6 ii python3 3.9.2-3 python3-open3d recommends no packages. Versions of packages python3-open3d suggests: pn open3d-doc -- no debconf information --- End Message --- --- Begin Message --- Source: open3d Source-Version: 0.9.0+ds-5+deb11u1 Done: Timo Röhling We believe that the bug you reported is fixed in the latest version of open3d, 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 993...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Timo Röhling (supplier of updated open3d 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: Tue, 12 Oct 2021 22:23:10 +0200 Source: open3d Architecture: source Version: 0.9.0+ds-5+deb11u1 Distribution: bullseye Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Timo Röhling Closes: 993622 Changes: open3d (0.9.0+ds-5+deb11u1) bullseye; urgency=medium . * Ensure that python3-open3d depends on python3-numpy (Closes: #993622) Checksums-Sha1: 7cc11f3cba640fb37b77030e75c121c453703957 2829 open3d_0.9.0+ds-5+deb11u1.dsc 75d35de6f968f45acc6d7cda76b3ec2c4ccf8133 1006148 open3d_0.9.0+ds-5+deb11u1.debian.tar.xz af439250034d78d9bfe48ecb5ce0febb90b2d2d0 15108 open3d_0.9.0+ds-5+deb11u1_amd64.buildinfo Checksums-Sha256: c83d6c40c4cc711e8630d25b737847141cfb54d41aeec492b0550491da83432f 2829 open3d_0.9.0+ds-5+deb11u1.dsc 90b6ac3818fce485223d1caf91957588988fc8f09a5d1b96393e1ede5cf0b2a3 1006148 open3d_0.9.0+ds-5+deb11u1.debian.tar.xz 82dcdefff85bf7ace728922251cc96bfc7069c65f5bf95757913bb6d0162d941 15108 open3d_0.9.0+ds-5+deb11u1_amd64.buildinfo Files: 16d745c540323d79bdd46a6d6d9dd8a6 2829 libs optional open3d_0.9.0+ds-5+deb11u1.dsc 95d8580882a46971d099b110c3b8c699 1006148 libs optional open3d_0.9.0+ds-5+deb11u1.debian.tar.xz
Bug#992973: marked as done (plib: CVE-2021-38714)
Your message dated Sat, 06 Nov 2021 19:17:31 + with message-id and subject line Bug#992973: fixed in plib 1.8.5-8+deb11u1 has caused the Debian Bug report #992973, regarding plib: CVE-2021-38714 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.) -- 992973: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992973 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: plib Version: 1.8.5-8 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://sourceforge.net/p/plib/bugs/55/ X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for plib. CVE-2021-38714[0]: | In Plib through 1.85, there is an integer overflow vulnerability that | could result in arbitrary code execution. The vulnerability is found | in ssgLoadTGA() function in src/ssg/ssgLoadTGA.cxx file. The severity of the this bug is set op purpose higher as it is probably warranted. There is the following reason for that: plib is orphaned in Debian for a while, it is obsoleted and unmaintained upstream as well. Ideally it get's removed from Debian from the next release, but thee would be some revers dependencies issues to be solved, making it imposssible for now to remove the package: | Checking reverse dependencies... | # Broken Depends: | crrcsim: crrcsim [amd64 arm64 armhf i386 mips64el mipsel ppc64el s390x] | flightgear: flightgear | openuniverse: openuniverse | stormbaancoureur: stormbaancoureur | torcs: torcs | | # Broken Build-Depends: | crrcsim: libplib-dev | flightgear: libplib-dev | torcs: libplib-dev | | Dependency problem found. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-38714 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38714 [1] https://sourceforge.net/p/plib/bugs/55/ Regards, Salvatore --- End Message --- --- Begin Message --- Source: plib Source-Version: 1.8.5-8+deb11u1 Done: Anton Gladky We believe that the bug you reported is fixed in the latest version of plib, 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 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky (supplier of updated plib 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, 17 Oct 2021 14:56:13 +0200 Source: plib Architecture: source Version: 1.8.5-8+deb11u1 Distribution: bullseye Urgency: medium Maintainer: Debian QA Group Changed-By: Anton Gladky Closes: 992973 Changes: plib (1.8.5-8+deb11u1) bullseye; urgency=medium . * Prevent integer overflow in ssgLoadTGA() function. CVE-2021-38714 (Closes: #992973) Checksums-Sha1: 5ed00a405191a2f6f361c6032f3d12b71c8db5ad 2009 plib_1.8.5-8+deb11u1.dsc c2cf7e3e1e58f7b63dae4bb21e4fa82c3e4d4cfc 779133 plib_1.8.5.orig.tar.gz 2500862838fb7f619653084a1448fcca2b6be180 11396 plib_1.8.5-8+deb11u1.debian.tar.xz 5b110cd2674ae4b7fc06df4786bf6c79e1b8261e 8297 plib_1.8.5-8+deb11u1_source.buildinfo Checksums-Sha256: a006a9fb967b799e05191df106da8f816c8d150c6a46ffb7517be8680dabd173 2009 plib_1.8.5-8+deb11u1.dsc 485b22bf6fdc0da067e34ead5e26f002b76326f6371e2ae006415dea6a380a32 779133 plib_1.8.5.orig.tar.gz e50148877cebe2fcffb5f4fdf7e2b23b4447fe3e36b7aad74d1a219930b99baf 11396 plib_1.8.5-8+deb11u1.debian.tar.xz 3b607ac360ecf93df395d23cc6116789ce9c772fbbe8f63fd9ebd053cf55e593 8297 plib_1.8.5-8+deb11u1_source.buildinfo Files: 989268b6e57368ae4884265b6e2a5b7d 2009 devel extra plib_1.8.5-8+deb11u1.dsc 47a6fbf63668c1eed631024038b2ea90 779133 devel extra plib_1.8.5.orig.tar.gz 03e682e78e83da411ea0c8d04eeb4497 11396 devel extra plib_1.8.5-8+deb11u1.debian.tar.xz 108d2bb08c93ad5aa27ff09ce82f6acf 8297 devel extra plib_1.8.5-8+deb11u1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEu71F6oGKuG/2fnKF0+Fzg8+n/wYFAmFsIAUACgkQ0+Fzg8+n /warjw/+N1naIFcDrfNqR6XzT8GW9uR4FafTxlQSMgti3rzCCQe5ltyKY38bmHqJ ga49uABrOTWqj0uQ0XxZEXLGOxCzfs8RrXTuqXAdipm0g5J5VFBJ+jTm31F+Qsmi
Bug#983981: marked as done (bamtools: ftbfs with GCC-11)
Your message dated Sat, 06 Nov 2021 19:03:47 + with message-id and subject line Bug#983981: fixed in bamtools 2.5.1+dfsg-10 has caused the Debian Bug report #983981, regarding bamtools: ftbfs with GCC-11 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.) -- 983981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:bamtools Version: 2.5.1+dfsg-8 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/bamtools_2.5.1+dfsg-8_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] /usr/include/c++/11/bits/stl_multiset.h:503:36: required from ‘std::multiset<_Key, _Compare, _Alloc>::iterator std::multiset<_Key, _Compare, _Alloc>::insert(const value_type&) [with _Key = BamTools::Internal::MergeItem; _Compare = BamTools::Internal::MergeItemSorter; _Alloc = std::allocator; std::multiset<_Key, _Compare, _Alloc>::iterator = std::_Rb_tree, BamTools::Internal::MergeItemSorter, std::allocator >::const_iterator; std::multiset<_Key, _Compare, _Alloc>::value_type = BamTools::Internal::MergeItem]’ /<>/src/api/internal/bam/BamMultiMerger_p.h:135:18: required from ‘void BamTools::Internal::MultiMerger::Add(BamTools::Internal::MergeItem) [with Compare = BamTools::Algorithms::Sort::ByName]’ /<>/src/api/internal/bam/BamMultiMerger_p.h:128:13: required from here /usr/include/c++/11/bits/stl_tree.h:770:15: error: static assertion failed: comparison object must be invocable as const 770 | is_invocable_v, | ^ /usr/include/c++/11/bits/stl_tree.h:770:15: note: ‘std::is_invocable_v&, const BamTools::Internal::MergeItem&, const BamTools::Internal::MergeItem&>’ evaluates to false /usr/include/c++/11/bits/stl_tree.h: In instantiation of ‘static const _Key& std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_S_key(std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_Const_Link_type) [with _Key = BamTools::Internal::MergeItem; _Val = BamTools::Internal::MergeItem; _KeyOfValue = std::_Identity; _Compare = BamTools::Internal::MergeItemSorter; _Alloc = std::allocator; std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_Const_Link_type = const std::_Rb_tree_node*]’: /usr/include/c++/11/bits/stl_tree.h:2100:44: required from ‘std::pair std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_M_get_insert_equal_pos(const key_type&) [with _Key = BamTools::Internal::MergeItem; _Val = BamTools::Internal::MergeItem; _KeyOfValue = std::_Identity; _Compare = BamTools::Internal::MergeItemSorter; _Alloc = std::allocator; std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::key_type = BamTools::Internal::MergeItem]’ /usr/include/c++/11/bits/stl_tree.h:2149:4: required from ‘std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::iterator std::_Rb_tree<_Key, _Val, _KeyOfValue, _Compare, _Alloc>::_M_insert_equal(_Arg&&) [with _Arg = const BamTools::Internal::MergeItem&; _Key = BamTools::Internal::MergeItem; _Val = BamTools::Internal::MergeItem; _KeyOfValue = std::_Identity; _Compare =
Processed: Re: Further comment on #983981 marked as pending in bamtools
Processing control commands: > tags -1 + pending Bug #983981 [src:bamtools] bamtools: ftbfs with GCC-11 Ignoring request to alter tags of bug #983981 to the same tags previously set -- 983981: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983981 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996922: marked as done (firefox exits with SIGFPE on startup (no user interaction))
Your message dated Sat, 6 Nov 2021 19:15:57 +0100 with message-id and subject line Re: firefox exits with SIGFPE on startup (no user interaction) has caused the Debian Bug report #996922, regarding firefox exits with SIGFPE on startup (no user interaction) 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.) -- 996922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: firefox Version: 92.0-1 Severity: grave Dear Maintainer, * What led up to the situation? Starting firefox or firefox-esr (or even chromium). I guess it is caused by a common dependency only on i386. * What exactly did you do (or not do) that was effective (or ineffective)? No user interaction. * What was the outcome of this action? The browser exits after showing a crashed tab panel with SIGFPE. * What outcome did you expect instead? Running the browser normally. -- Package-specific info: Starting program: /usr/bin/firefox.real [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [New Thread 0xb77ffac0 (LWP 11257)] [Thread 0xb77ffac0 (LWP 11257) exited] [Detaching after fork from child process 11258] [Detaching after fork from child process 11259] [New Thread 0xab86aac0 (LWP 11260)] [New Thread 0xa73f1ac0 (LWP 11261)] [New Thread 0xa73b0ac0 (LWP 11262)] [New Thread 0xa736fac0 (LWP 11263)] [New Thread 0xa70ffac0 (LWP 11264)] [New Thread 0xb77ffac0 (LWP 11265)] [New Thread 0xa6effac0 (LWP 11266)] [New Thread 0xa64ffac0 (LWP 11269)] [Detaching after fork from child process 11270] [New Thread 0xabdb2ac0 (LWP 11271)] [New Thread 0xa66b8ac0 (LWP 11272)] [New Thread 0xa732eac0 (LWP 11273)] [New Thread 0xa6677ac0 (LWP 11274)] [New Thread 0xa52ffac0 (LWP 11277)] [New Thread 0xa5100ac0 (LWP 11278)] [New Thread 0xa5cfeac0 (LWP 11279)] [New Thread 0xa5cbdac0 (LWP 11280)] [New Thread 0xa5c7cac0 (LWP 11281)] [New Thread 0xa4ab9ac0 (LWP 11282)] [Thread 0xa64ffac0 (LWP 11269) exited] [Thread 0xa4ab9ac0 (LWP 11282) exited] [New Thread 0xa4ab9ac0 (LWP 11283)] [New Thread 0xa64ffac0 (LWP 11284)] [New Thread 0xa4258ac0 (LWP 11285)] [Thread 0xa64ffac0 (LWP 11284) exited] [New Thread 0xa64ffac0 (LWP 11286)] [Thread 0xa4258ac0 (LWP 11285) exited] [Thread 0xa4ab9ac0 (LWP 11283) exited] [Thread 0xa64ffac0 (LWP 11286) exited] [New Thread 0xa64ffac0 (LWP 11287)] [New Thread 0xa4ab9ac0 (LWP 11288)] [New Thread 0xa4258ac0 (LWP 11289)] [Thread 0xa4ab9ac0 (LWP 11288) exited] [Thread 0xa4258ac0 (LWP 11289) exited] [New Thread 0xa3a4aac0 (LWP 11290)] [New Thread 0xa38ffac0 (LWP 11291)] [New Thread 0xa4258ac0 (LWP 11292)] [New Thread 0xa4ab9ac0 (LWP 11293)] [New Thread 0xa36ffac0 (LWP 11294)] [New Thread 0xa32ffac0 (LWP 11295)] [New Thread 0xa38beac0 (LWP 11296)] [New Thread 0xa386dac0 (LWP 11297)] [New Thread 0xa2a4cac0 (LWP 11298)] [New Thread 0xa23ffac0 (LWP 11299)] [Thread 0xa66b8ac0 (LWP 11272) exited] [New Thread 0xa2250ac0 (LWP 11300)] [New Thread 0xa66b8ac0 (LWP 11301)] [New Thread 0xa16ffac0 (LWP 11302)] [New Thread 0xa16beac0 (LWP 11303)] [New Thread 0xa167dac0 (LWP 11304)] [New Thread 0xa163cac0 (LWP 11305)] [New Thread 0xa15fbac0 (LWP 11306)] [New Thread 0xa15baac0 (LWP 11307)] [New Thread 0xa1579ac0 (LWP 11308)] [New Thread 0xa13ffac0 (LWP 11309)] [Thread 0xa13ffac0 (LWP 11309) exited] [Thread 0xa5cfeac0 (LWP 11279) exited] [New Thread 0xa13beac0 (LWP 11310)] [New Thread 0xa137dac0 (LWP 11311)] [New Thread 0xa0effac0 (LWP 11312)] [Thread 0xa13beac0 (LWP 11310) exited] [Thread 0xa137dac0 (LWP 11311) exited] [Thread 0xa0effac0 (LWP 11312) exited] [New Thread 0xa0effac0 (LWP 11313)] [New Thread 0xa137dac0 (LWP 11314)] [New Thread 0xa3827ac0 (LWP 11315)] [New Thread 0xa04ffac0 (LWP 11316)] [New Thread 0xa02feac0 (LWP 11317)] [New Thread 0xa00fdac0 (LWP 11318)] [New Thread 0x9fcffac0 (LWP 11319)] [New Thread 0xa13beac0 (LWP 11320)] [New Thread 0xa5cfeac0 (LWP 11321)] [Detaching after fork from child process 11322] [New Thread 0xa13ffac0 (LWP 11324)] [New Thread 0xa0e55ac0 (LWP 11326)] [New Thread 0xa07ffac0 (LWP 11327)] [New Thread 0x9efffac0 (LWP 11339)] [New Thread 0x9edfeac0 (LWP 11340)] [New Thread 0xa07beac0 (LWP 11341)] [New Thread 0xa077dac0 (LWP 11342)] [New Thread 0x9e9ffac0 (LWP 11343)] [New Thread 0x9fe88ac0 (LWP 11344)] [New Thread 0x9fe47ac0 (LWP 11345)] [Thread 0xa5cbdac0 (LWP 11280) exited] [New Thread 0x98cffac0 (LWP 11346)] [New Thread 0xa5cbdac0 (LWP 11347)] [Detaching after fork from child process 11348] [New Thread 0xa0ea5ac0 (LWP 11349)] [New Thread 0x9e09bac0 (LWP 11358)]
Bug#984260: marked as done (nut: ftbfs with GCC-11)
Your message dated Sat, 06 Nov 2021 18:03:53 + with message-id and subject line Bug#984260: fixed in nut 2.7.4-14 has caused the Debian Bug report #984260, regarding nut: ftbfs with GCC-11 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.) -- 984260: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984260 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nut Version: 2.7.4-13 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/nut_2.7.4-13_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] nutclient.cpp:974:49: error: ISO C++17 does not allow dynamic exception specifications 974 | std::set Device::getVariableNames()throw(NutException) | ^ nutclient.cpp:979:51: error: ISO C++17 does not allow dynamic exception specifications 979 | std::set Device::getRWVariableNames()throw(NutException) | ^ nutclient.cpp:984:76: error: ISO C++17 does not allow dynamic exception specifications 984 | void Device::setVariable(const std::string& name, const std::string& value)throw(NutException) | ^ nutclient.cpp:990:9: error: ISO C++17 does not allow dynamic exception specifications 990 | throw(NutException) | ^ nutclient.cpp:997:54: error: ISO C++17 does not allow dynamic exception specifications 997 | Variable Device::getVariable(const std::string& name)throw(NutException) | ^ nutclient.cpp:1005:42: error: ISO C++17 does not allow dynamic exception specifications 1005 | std::set Device::getVariables()throw(NutException) | ^ nutclient.cpp:1018:44: error: ISO C++17 does not allow dynamic exception specifications 1018 | std::set Device::getRWVariables()throw(NutException) |^ nutclient.cpp:1031:48: error: ISO C++17 does not allow dynamic exception specifications 1031 | std::set Device::getCommandNames()throw(NutException) |^ nutclient.cpp:1036:40: error: ISO C++17 does not allow dynamic exception specifications 1036 | std::set Device::getCommands()throw(NutException) |^ nutclient.cpp:1049:52: error: ISO C++17 does not allow dynamic exception specifications 1049 | Command Device::getCommand(const std::string& name)throw(NutException) |^ nutclient.cpp:1057:53: error: ISO C++17 does not allow dynamic exception specifications 1057 | void Device::executeCommand(const std::string& name)throw(NutException) | ^ nutclient.cpp:1062:21: error: ISO C++17 does not allow dynamic exception specifications 1062 | void Device::login()throw(NutException) | ^ nutclient.cpp:1067:22: error: ISO C++17 does not allow
Bug#998108: firefox freezes shortly after start
On Nov 06, dirdi wrote: > As a first step it would be good to have a method - e.g. a crafted > HTML page - to crash firefox instantly and reproducible. This would > enable us to bisect the changes between 93.0-1 and 93.0-1+b1. I do not think that this would be possible because after restarting Firefox and opening again the link which made it freeze the first time then it works again. -- ciao, Marco signature.asc Description: PGP signature
Bug#998108: firefox: still broken
Package: firefox Version: 94.0-1 Followup-For: Bug #998108 Problem is still here after dist-upgrade on sid. Firefox hangs and becomes unresponsive. Had to downgrade to verison 93.0-1
Bug#997328: marked as done (shaarli: FTBFS: jinja2.exceptions.UndefinedError: list object has no element 0)
Your message dated Sat, 06 Nov 2021 16:49:29 +
with message-id
and subject line Bug#997328: fixed in shaarli 0.12.0+dfsg-4
has caused the Debian Bug report #997328,
regarding shaarli: FTBFS: jinja2.exceptions.UndefinedError: list object has no
element 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.)
--
997328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997328
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: shaarli
Version: 0.12.0+dfsg-3
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[2]: Entering directory '/<>'
> mkdocs build --clean
> WARNING - Config value: 'pages'. Warning: The 'pages' configuration option
> has been deprecated and will be removed in a future release of MkDocs. Use
> 'nav' instead.
> INFO- Cleaning site directory
> INFO- Building documentation to directory: /<>/doc/html
> Traceback (most recent call last):
> File "/usr/bin/mkdocs", line 6, in
> cli()
> File "/usr/lib/python3/dist-packages/click/core.py", line 1126, in __call__
> return self.main(*args, **kwargs)
> File "/usr/lib/python3/dist-packages/click/core.py", line 1051, in main
> rv = self.invoke(ctx)
> File "/usr/lib/python3/dist-packages/click/core.py", line 1657, in invoke
> return _process_result(sub_ctx.command.invoke(sub_ctx))
> File "/usr/lib/python3/dist-packages/click/core.py", line 1393, in invoke
> return ctx.invoke(self.callback, **ctx.params)
> File "/usr/lib/python3/dist-packages/click/core.py", line 752, in invoke
> return __callback(*args, **kwargs)
> File "/usr/lib/python3/dist-packages/mkdocs/__main__.py", line 152, in
> build_command
> build.build(config.load_config(**kwargs), dirty=not clean)
> File "/usr/lib/python3/dist-packages/mkdocs/commands/build.py", line 285,
> in build
> _build_theme_template(template, env, files, config, nav)
> File "/usr/lib/python3/dist-packages/mkdocs/commands/build.py", line 108,
> in _build_theme_template
> output = _build_template(template_name, template, files, config, nav)
> File "/usr/lib/python3/dist-packages/mkdocs/commands/build.py", line 87, in
> _build_template
> output = template.render(context)
> File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1304, in
> render
> self.environment.handle_exception()
> File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 925, in
> handle_exception
> raise rewrite_traceback_stack(source=source)
> File
> "/usr/lib/python3/dist-packages/mkdocs/themes/readthedocs/search.html", line
> 1, in top-level template code
> {% extends "main.html" %}
> File "/<>/doc/custom_theme/main.html", line 1, in top-level
> template code
> {% extends "base.html" %}
> File "/usr/lib/python3/dist-packages/mkdocs/themes/readthedocs/base.html",
> line 5, in top-level template code
> {%- block site_meta %}
> File "/<>/doc/custom_theme/main.html", line 17, in block
> 'site_meta'
> {%- if 'media.readthedocs.org' not in config.extra_css[0] %}
> jinja2.exceptions.UndefinedError: list object has no element 0
> make[2]: *** [Makefile:157: htmldoc] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/shaarli_0.12.0+dfsg-3_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!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: shaarli
Source-Version: 0.12.0+dfsg-4
Done: James Valleroy
We believe that the bug you reported is fixed in the latest version of
shaarli, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
James Valleroy (supplier of updated shaarli package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact
Bug#936535: flup: Python2 removal in sid/bullseye
On Fri, Jan 10, 2020 at 07:28:01PM -0300, Emmanuel Arias wrote: > Hi, > > The last upstream release version was on 2009 [1]. Seems to be not longer > supported. > > And there is not python3 version. > > I believe that should be use the forks mentioned on: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873492 > > [1] https://www.saddi.com/software/flup/dist/ChangeLog Hello Arias Emmanuel, As noted in the bug report for https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=873492, I intend to request removal of this package from unstable on November 14th if the Debian Python Team (or some other maintainer) doesn't decide to take the package and update it. Cheers, tony signature.asc Description: PGP signature
Bug#998108: Acknowledgement (firefox freezes shortly after start)
I guess I just got lucky then. I can't think of anything that I've changed. For the record, I still have not re-experienced this problem. Adon On Sat, Nov 06, 2021 at 03:43:09AM +0100, Christoph Anton Mitterer wrote: > > I was also experiencing this problem and was monitoring this bug > > report for potential solutions, but the problem seems to have > > recently disappeared. > > I cannot confirm this.
Bug#998108: firefox freezes shortly after start
Package: firefox Version: 94.0-1 Followup-For: Bug #998108 X-Debbugs-Cc: deb...@dirdi.name As a first step it would be good to have a method - e.g. a crafted HTML page - to crash firefox instantly and reproducible. This would enable us to bisect the changes between 93.0-1 and 93.0-1+b1. Package-specific info: -- Addons package information -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (50, 'unstable'), (5, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-2-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages firefox depends on: ii debianutils 4.11.2 ii fontconfig 2.13.1-4.2 ii libatk1.0-0 2.36.0-2 ii libc62.32-4 ii libcairo-gobject21.16.0-5 ii libcairo21.16.0-5 ii libdbus-1-3 1.12.20-3 ii libdbus-glib-1-2 0.112-2 ii libevent-2.1-7 2.1.12-stable-1 ii libffi8 3.4.2-3 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.11.0+dfsg-1 ii libgcc-s111.2.0-10 ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2 ii libglib2.0-0 2.70.0-3 ii libgtk-3-0 3.24.30-3 ii libnspr4 2:4.32-1 ii libnss3 2:3.72-1 ii libpango-1.0-0 1.48.10+ds1-1 ii libstdc++6 11.2.0-10 ii libvpx7 1.11.0-2 ii libx11-6 2:1.7.2-2+b1 ii libx11-xcb1 2:1.7.2-2+b1 ii libxcb-shm0 1.14-3 ii libxcb1 1.14-3 ii libxcomposite1 1:0.4.5-1 ii libxdamage1 1:1.1.5-2 ii libxext6 2:1.3.4-1 ii libxfixes3 1:5.0.3-2 ii libxrandr2 2:1.5.2-1 ii procps 2:3.3.17-5 ii zlib1g 1:1.2.11.dfsg-2 Versions of packages firefox recommends: ii libavcodec58 7:4.4.1-1+b1 Versions of packages firefox suggests: pn fonts-lmodern pn fonts-stix | otf-stix ii libcanberra0 0.30-8 ii libgssapi-krb5-2 1.18.3-7 ii pulseaudio 15.0+dfsg1-2 -- no debconf information
Processed: gap-float: failed to build on i386 arch: object must be an MPFR, not a integer
Processing commands for cont...@bugs.debian.org: > retitle 998413 gap-float: failed to build on i386 arch: object must be an > MPFR, not a integer Bug #998413 [src:gap-float] gap-float: autopkgtest regression: object must be an MPFR, not a integer Changed Bug title to 'gap-float: failed to build on i386 arch: object must be an MPFR, not a integer' from 'gap-float: autopkgtest regression: object must be an MPFR, not a integer'. > thanks Stopping processing here. Please contact me if you need assistance. -- 998413: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997384: wslay: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
Control: tags -1 + upstream fixed-upstream patch
Control: forwarded -1
https://github.com/tatsuhiro-t/wslay/commit/43fda1207ea5977043630500e0c8e77b98b35320
Hi Anton, Lucas,
* Lucas Nussbaum [211106 12:55]:
> Source: wslay
> > File "/<>/doc/sphinx/conf.py", line 305, in setup
> > app.add_stylesheet('default2.css')
> > AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
Upstream fixed this here:
https://github.com/tatsuhiro-t/wslay/commit/43fda1207ea5977043630500e0c8e77b98b35320
Adding this patch makes the Debian package build. There seem to be
minor issues with the HTML doc, but not caused by this patch at
least.
I'm attaching a trivial patch to add the upstream patch to the
Debian package.
Best,
Chris
>From a212f471623d2c5211f28219da2e472450e345cc Mon Sep 17 00:00:00 2001
From: Chris Hofstaedtler
Date: Sat, 6 Nov 2021 12:52:05 +
Subject: [PATCH] Fix building with sphinx 3.3, from upstream
---
debian/patches/series | 1 +
.../upstream-Fix-sphinx-33-errors.patch | 147 ++
2 files changed, 148 insertions(+)
create mode 100644 debian/patches/upstream-Fix-sphinx-33-errors.patch
diff --git a/debian/patches/series b/debian/patches/series
index 11fae01..4736f92 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -1,2 +1,3 @@
10_update_cmake.patch
20_cmake_casing.patch
+upstream-Fix-sphinx-33-errors.patch
diff --git a/debian/patches/upstream-Fix-sphinx-33-errors.patch b/debian/patches/upstream-Fix-sphinx-33-errors.patch
new file mode 100644
index 000..fdcfc01
--- /dev/null
+++ b/debian/patches/upstream-Fix-sphinx-33-errors.patch
@@ -0,0 +1,147 @@
+From 43fda1207ea5977043630500e0c8e77b98b35320 Mon Sep 17 00:00:00 2001
+From: Tatsuhiro Tsujikawa
+Date: Thu, 14 Jan 2021 20:44:36 +0900
+Subject: [PATCH] Fix sphinx 3.3 errors
+
+---
+ doc/sphinx/conf.py.in | 2 +-
+ .../man/wslay_event_context_server_init.rst | 44 +++
+ .../man/wslay_event_queue_fragmented_msg.rst | 2 +-
+ 3 files changed, 17 insertions(+), 31 deletions(-)
+
+diff --git a/doc/sphinx/conf.py.in b/doc/sphinx/conf.py.in
+index 1eaeee1..2ee5f21 100644
+--- a/doc/sphinx/conf.py.in
b/doc/sphinx/conf.py.in
+@@ -304,4 +304,4 @@ man_pages = [
+ ]
+
+ def setup(app):
+-app.add_stylesheet('default2.css')
++app.add_css_file('default2.css')
+diff --git a/doc/sphinx/man/wslay_event_context_server_init.rst b/doc/sphinx/man/wslay_event_context_server_init.rst
+index f549d79..dbf44d3 100644
+--- a/doc/sphinx/man/wslay_event_context_server_init.rst
b/doc/sphinx/man/wslay_event_context_server_init.rst
+@@ -16,13 +16,13 @@ DESCRIPTION
+ ---
+
+ :c:func:`wslay_event_context_server_init` function initializes an
+-:c:event-based API context for WebSocket server use.
++event-based API context for WebSocket server use.
+ :c:func:`wslay_event_context_client_init` function initializes an
+-:c:event-based API context for WebSocket client use. If they return
+-:c:successfully, `ctx` will point to a structure which holds any
+-:c:necessary resources needed to process WebSocket protocol transfers.
++event-based API context for WebSocket client use. If they return
++successfully, `ctx` will point to a structure which holds any
++necessary resources needed to process WebSocket protocol transfers.
+
+-*callbacks* is a pointer to :c:type:`struct wslay_event_callbacks`,
++*callbacks* is a pointer to :c:type:`wslay_event_callbacks`,
+ which is defined as follows::
+
+ struct wslay_event_callbacks {
+@@ -35,9 +35,7 @@ which is defined as follows::
+ wslay_event_on_msg_recv_callback on_msg_recv_callback;
+ };
+
+-**recv_callback**
+-
+- .. c:type:: typedef ssize_t (*wslay_event_recv_callback)(wslay_event_context_ptr ctx, uint8_t *buf, size_t len, int flags, void *user_data)
++.. c:type:: ssize_t (*wslay_event_recv_callback)(wslay_event_context_ptr ctx, uint8_t *buf, size_t len, int flags, void *user_data)
+
+*recv_callback* is invoked by :c:func:`wslay_event_recv` when it
+wants to receive more data from peer.
+@@ -53,9 +51,7 @@ which is defined as follows::
+set ``WSLAY_ERR_WOULDBLOCK`` instead. This is important because it tells
+:c:func:`wslay_event_recv` to stop receiving further data and return.
+
+-**send_callback**
+-
+- .. c:type:: typedef ssize_t (*wslay_event_send_callback)(wslay_event_context_ptr ctx, const uint8_t *data, size_t len, int flags, void *user_data)
++.. c:type:: ssize_t (*wslay_event_send_callback)(wslay_event_context_ptr ctx, const uint8_t *data, size_t len, int flags, void *user_data)
+
+*send_callback* is invoked by :c:func:`wslay_event_send` when it
+wants to send more data to peer.
+@@ -76,9 +72,7 @@ which is defined as follows::
+set ``WSLAY_ERR_WOULDBLOCK`` instead. This is important because it tells
+:c:func:`wslay_event_send` to stop sending data and return.
+
+-**genmask_callback**
+-
+- .. c:type:: typedef int
Processed: Re: Bug#997384: wslay: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet'
Processing control commands: > tags -1 + upstream fixed-upstream patch Bug #997384 [src:wslay] wslay: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' Added tag(s) upstream, patch, and fixed-upstream. > forwarded -1 > https://github.com/tatsuhiro-t/wslay/commit/43fda1207ea5977043630500e0c8e77b98b35320 Bug #997384 [src:wslay] wslay: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' Set Bug forwarded-to-address to 'https://github.com/tatsuhiro-t/wslay/commit/43fda1207ea5977043630500e0c8e77b98b35320'. -- 997384: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997384 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996726: Some other questions
Hi Bob, hi Jérôme, On Fri, 05 Nov 2021, Jérôme Pouiller wrote: > Is there a way to avoid this problem happen in the future? Yes of course: * take a VM * for each package in the set of Plasma, that is about 150 or so, do - upgrade the package and all necessary dependencies - reboot the vm - test whether Plasma works properly Unfortunately, none of us has the time to do this. On Fri, 05 Nov 2021, Bob Wong wrote: > Probably the best way is to do the rolling release. Another solution is Not in Debian. Different discussion. > to make each package synced downstream at the same time, but it's too hard > to achieve. ??? Not sure what you want to say here ... Best Norbert -- PREINING Norbert https://www.preining.info Fujitsu Research + IFMGA Guide + TU Wien + TeX Live + Debian Dev GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
Processed: Bug#997607 marked as pending in python-fudge
Processing control commands:
> tag -1 pending
Bug #997607 {Done: Carsten Schoenert }
[src:python-fudge] python-fudge: FTBFS: error in fudge setup command: use_2to3
is invalid.
Added tag(s) pending.
--
997607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#997607: marked as pending in python-fudge
Control: tag -1 pending Hello, Bug #997607 in python-fudge 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/python-fudge/-/commit/9a97eccd0436fe6456f8d5c6401ea78962133057 Add a patch queue from a patchqueue branch Added patches: Porting-existing-code-over-to-Python3-by-using-2to3.patch Remove-version-check-in-setup.py.patch These patches are needed to get the source into Python3 compatible syntax. Closes: #997607 (this message was generated automatically) -- Greetings https://bugs.debian.org/997607
Bug#997607: marked as done (python-fudge: FTBFS: error in fudge setup command: use_2to3 is invalid.)
Your message dated Sat, 06 Nov 2021 12:35:02 +
with message-id
and subject line Bug#997607: fixed in python-fudge 1.1.1-1
has caused the Debian Bug report #997607,
regarding python-fudge: FTBFS: error in fudge setup command: use_2to3 is
invalid.
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.)
--
997607: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997607
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-fudge
Version: 1.1.0-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3,sphinxdoc --buildsystem=pybuild
> dh: warning: Compatibility levels before 10 are deprecated (level 9 in use)
>debian/rules override_dh_auto_clean
> make[1]: Entering directory '/<>'
> dh_auto_clean
> dh_auto_clean: warning: Compatibility levels before 10 are deprecated (level
> 9 in use)
> I: pybuild base:232: python3.9 setup.py clean
> error in fudge setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean --test-nose -i python{version} -p 3.9
> returned exit code 13
> make[1]: *** [debian/rules:13: override_dh_auto_clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-fudge_1.1.0-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!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-fudge
Source-Version: 1.1.1-1
Done: Carsten Schoenert
We believe that the bug you reported is fixed in the latest version of
python-fudge, 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 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Carsten Schoenert (supplier of updated python-fudge
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: Sat, 06 Nov 2021 11:22:50 +0100
Source: python-fudge
Architecture: source
Version: 1.1.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Carsten Schoenert
Closes: 997607
Changes:
python-fudge (1.1.1-1) unstable; urgency=medium
.
* Team upload
.
[ Debian Janitor ]
* Bump debhelper from old 9 to 12.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Apply multi-arch hints.
+ python-fudge-doc: Add Multi-Arch: foreign.
.
[ Ondřej Nový ]
* 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 ]
* Bump debhelper from old 12 to 13.
.
[ Carsten Schoenert ]
* d/gbp.conf: Adding helper file for git-buildpackage
* New upstream version 1.1.1
* Add a patch queue from a patchqueue branch
Added patches:
Porting-existing-code-over-to-Python3-by-using-2to3.patch
Remove-version-check-in-setup.py.patch
(Closes: #997607)
* d/control: Update Homepage field to new URL
* d/watch: Mark watch file as version 4
* d/control: Update Standards-Version to 4.6.0
No further changes needed.
* d/control: Running wrap-and-sort -ast
* d/control: Adding entry Rules-Requires-Root: no
This package needs no root rights while building.
* d/rules: Using SOURCE_DATE_EPOCH to build timestamp
* d/copyright: Small update to the project data
Checksums-Sha1:
c82036be0a58ad5920f263c05bfd4f02f4d35bcb 2090 python-fudge_1.1.1-1.dsc
8604713d242b8a147b30196677f92846057427ee 87604
Bug#998580: marked as done (mako-notifier: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "apparmor")
Your message dated Sat, 06 Nov 2021 11:19:11 + with message-id and subject line Bug#998580: fixed in mako-notifier 1.6-2 has caused the Debian Bug report #998580, regarding mako-notifier: FTBFS: ../meson.build:1:0: ERROR: Unknown options: "apparmor" 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.) -- 998580: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998580 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mako-notifier Version: 1.6-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_configure -- -Dzsh-completions=true -Dapparmor=true > cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dzsh-completions=true > -Dapparmor=true > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "apparmor" > > A full log can be found at > /<>/obj-x86_64-linux-gnu/meson-logs/meson-log.txt > cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/meson-log.txt > ==> meson-logs/meson-log.txt <== > Build started at 2021-11-04T09:57:41.714983 > Main binary: /usr/bin/python3 > Build Options: -Dzsh-completions=true -Dapparmor=true -Dprefix=/usr > -Dlibdir=lib/x86_64-linux-gnu -Dlocalstatedir=/var -Dsysconfdir=/etc > -Dbuildtype=plain -Dwrap_mode=nodownload > Python system: Linux > The Meson build system > Version: 0.60.1 > Source dir: /<> > Build dir: /<>/obj-x86_64-linux-gnu > Build type: native build > > ../meson.build:1:0: ERROR: Unknown options: "apparmor" > dh_auto_configure: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 meson .. > --wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc > --localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dzsh-completions=true > -Dapparmor=true returned exit code 1 > make[1]: *** [debian/rules:9: override_dh_auto_configure] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/11/04/mako-notifier_1.6-1_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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: mako-notifier Source-Version: 1.6-2 Done: Birger Schacht We believe that the bug you reported is fixed in the latest version of mako-notifier, 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 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Birger Schacht (supplier of updated mako-notifier 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: Sat, 06 Nov 2021 11:29:37 +0100 Source: mako-notifier Architecture: source Version: 1.6-2 Distribution: unstable Urgency: medium Maintainer: Sway and related packages team Changed-By: Birger Schacht Closes: 998580 Changes: mako-notifier (1.6-2) unstable; urgency=medium . * Drop -Dapparmor from d/rules file (Closes: #998580) * Enable build and installation of fish shell completion files * Install systemd service file and apparmor rules file using debhelper * Update standards-version to 4.6.0.1 (no changes required) Checksums-Sha1: 2ee33bb9655cdc29c0f9caaf21899bef87ba3180 2081 mako-notifier_1.6-2.dsc b70006cc2ec429ae998f99140448319627b596b3 3016 mako-notifier_1.6-2.debian.tar.xz 96f4b4af1a931802f78f8cdb139e908259996a89 10417 mako-notifier_1.6-2_amd64.buildinfo Checksums-Sha256: 238ba42de1a39ab98f5b00b3fce2933a6fa6f8c8b74d99039c1aa34a50c60a0a 2081
Bug#970870: marked as done (postgresql-autodoc: incompatible with PostgreSQL >= 12)
Your message dated Sat, 06 Nov 2021 11:03:53 + with message-id and subject line Bug#970870: fixed in postgresql-autodoc 1.41+20200921-1 has caused the Debian Bug report #970870, regarding postgresql-autodoc: incompatible with PostgreSQL >= 12 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.) -- 970870: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970870 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: postgresql-autodoc Version: 1.40-3 Severity: grave Tags: upstream sid bullseye Dear maintainer, postgresql-autodoc, as currently packaged in Debian, doesn't work with PostgreSQL 12, which is the current default version of PostgreSQL in testing and sid (it works fine with PostgreSQL 11 which is shipped with buster). The failure mode is the following (excuse my French): $ postgresql_autodoc -d softwareheritage-dev -f autodoc/db-schema DBD::Pg::st execute failed: ERREUR: la colonne � adsrc � n'existe pas LIGNE 40 : adsrc ^ at /usr/bin/postgresql_autodoc line 687. DBD::Pg::st fetchrow_hashref failed: no statement executing at /usr/bin/postgresql_autodoc line 689. [...] Use of uninitialized value in numeric comparison (<=>) at /usr/bin/postgresql_autodoc line 991. [...] Use of uninitialized value in numeric comparison (<=>) at /usr/bin/postgresql_autodoc line 1466. [...] This generates dot files with a lot of column missings. Upstream seems to have picked up development on GitHub at https://github.com/cbbrowne/autodoc. This repository shows a bunch of commits on top of the current Debian version which should fix at least this bug. Thank you, Nicolas -- System Information: Debian Release: bullseye/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-1-amd64 (SMP w/8 CPU threads) Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.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 postgresql-autodoc depends on: ii libdbd-pg-perl 3.14.2-1 ii libhtml-template-perl 2.97-1 ii libterm-readkey-perl 2.38-1+b1 ii perl 5.30.3-4 Versions of packages postgresql-autodoc recommends: ii dia 0.97.3+git20160930-9 ii docbook-defguide [docbook-book] 2.0.17+svn9912-2 ii firefox [www-browser] 80.0.1-1 ii firefox-esr [www-browser] 78.2.0esr-1 ii google-chrome-stable [www-browser] 85.0.4183.102-1 ii graphviz2.42.2-4 postgresql-autodoc suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: postgresql-autodoc Source-Version: 1.41+20200921-1 Done: Willi Mann We believe that the bug you reported is fixed in the latest version of postgresql-autodoc, 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. Willi Mann (supplier of updated postgresql-autodoc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 05 Nov 2021 14:45:17 +0100 Source: postgresql-autodoc Architecture: source Version: 1.41+20200921-1 Distribution: unstable Urgency: medium Maintainer: Willi Mann Changed-By: Willi Mann Closes: 970870 Changes: postgresql-autodoc (1.41+20200921-1) unstable; urgency=medium . * Repackaged newest version from GitHub (Closes: #970870) * New maintainer with permission from old maintainer. Checksums-Sha1: db54ab23fe86e5e372fbea4ac254c7fc2e7ad182 1985 postgresql-autodoc_1.41+20200921-1.dsc 4e3453a198dd5a6cf9008ff14c12aaae8012f05c 34004 postgresql-autodoc_1.41+20200921.orig.tar.gz 9f7708964926ab281ba13a4181c176280271 4524 postgresql-autodoc_1.41+20200921-1.debian.tar.xz 086db352f7b723993009821ee0c1ac28d7a309ec 6923 postgresql-autodoc_1.41+20200921-1_source.buildinfo Checksums-Sha256:
Bug#997206: marked as done (irrlicht: FTBFS: COSOperator.cpp:17:10: fatal error: sys/sysctl.h: No such file or directory)
Your message dated Sat, 06 Nov 2021 09:49:31 + with message-id and subject line Bug#997206: fixed in irrlicht 1.8.4+dfsg1-2 has caused the Debian Bug report #997206, regarding irrlicht: FTBFS: COSOperator.cpp:17:10: fatal error: sys/sysctl.h: No such file or directory 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.) -- 997206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997206 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: irrlicht Version: 1.8.4+dfsg1-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > g++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wall -pipe -fno-exceptions > -fstrict-aliasing -fexpensive-optimizations -O3 -fPIC -Wdate-time > -D_FORTIFY_SOURCE=2 -I../../include -I/usr/X11R6/include > -DIRRLICHT_EXPORTS=1 -c -o COSOperator.o COSOperator.cpp > COSOperator.cpp:17:10: fatal error: sys/sysctl.h: No such file or directory >17 | #include > | ^~ > compilation terminated. > make[2]: *** [: COSOperator.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/irrlicht_1.8.4+dfsg1-1.1_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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: irrlicht Source-Version: 1.8.4+dfsg1-2 Done: Julien Puydt We believe that the bug you reported is fixed in the latest version of irrlicht, 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 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Puydt (supplier of updated irrlicht 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: Sat, 06 Nov 2021 09:49:22 +0100 Source: irrlicht Architecture: source Version: 1.8.4+dfsg1-2 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Julien Puydt Closes: 997206 Changes: irrlicht (1.8.4+dfsg1-2) unstable; urgency=medium . [ Christoph Egger ] * Remove myself from uploaders . [ Julien Puydt ] * Shuffle patches around: - remove a hurd-specific patch - replace it by a generic one (sysctl.patch) (Closes: #997206) * Update packaging: - point Vcs-* fields to salsa - clean d/watch - move to b-dep on dh-compat instead of d/compat - bump standards-version to 4.6.0. - declare usr/lib/include as not-installed (they really are!) - add lintian override for non-missing missing sources * Add myself as uploader. Checksums-Sha1: 2c373d39206fa83652f74fdc6d81552bd4533e10 2390 irrlicht_1.8.4+dfsg1-2.dsc ce0570283e154dc744f36641be28958b47645818 41488 irrlicht_1.8.4+dfsg1-2.debian.tar.xz 3a007d2b9ec000f476816ade93520b020ce1395d 10260 irrlicht_1.8.4+dfsg1-2_source.buildinfo Checksums-Sha256: 7be8c1e5e2e9ebee6e0ad00125249cbbc2b83f5072effe1c69e077fe09e1f8e3 2390 irrlicht_1.8.4+dfsg1-2.dsc d7a8f541c28d52ea372bde31804ff7332bba49be412b32f3c1fb8d479454ec1b 41488 irrlicht_1.8.4+dfsg1-2.debian.tar.xz c7fd7119bd8f6307793eb9e1b13e6b426250afb64d1490fda1a00c6c2e2d7b30 10260 irrlicht_1.8.4+dfsg1-2_source.buildinfo Files: 6c42c03f73639d6b84cfb986d06d2a1a 2390 libs optional irrlicht_1.8.4+dfsg1-2.dsc 0cbeb453145557b8b37d7e436deb625a 41488 libs optional irrlicht_1.8.4+dfsg1-2.debian.tar.xz 7c4894a937e558384b5df2bd321ec3b4 10260 libs optional irrlicht_1.8.4+dfsg1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEgS7v2KP7pKzk3xFLBMU71/4DBVEFAmGGQcASHGpwdXlkdEBk ZWJpYW4ub3JnAAoJEATFO9f+AwVRqhsP/jRrNlC5TLahi3sFYWYvJVYS1B9BaWgp 3guStMrz7o1X0oFSui/DvNK9lGhBdn0s6RmSo2XtCbPm1R+nv2UJtvnfAL8qNkkM
Bug#998679: firefox-esr freezes shortly after start
Package: firefox-esr
Version: 91.3.0esr-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
after upgrading to esr91 I'm experiencing the same symptoms as
described in bug #998108 for firefox.
Regards,
GLG
-- Package-specific info:
-- Extensions information
Name: Amazon.co.uk
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Amazon.com
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Bing
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Dark theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: DoH Roll-Out
Location: /usr/lib/firefox-esr/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Don't track me Google
Location: ${PROFILE_EXTENSIONS}/dont-track-me-goo...@robwu.nl.xpi
Status: enabled
Name: DuckDuckGo
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Firefox Alpenglow theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: Firefox Screenshots
Location: /usr/lib/firefox-esr/browser/features/screensh...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Form Autofill
Location: /usr/lib/firefox-esr/browser/features/formautof...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Google
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
Name: Light theme
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: user-disabled
Name: Picture-In-Picture
Location: /usr/lib/firefox-esr/browser/features/pictureinpict...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: Proxy Failover
Location:
/home/gragnani/.mozilla/firefox/4k5qr2p9.default/features/{19dd109a-c7f4-40c6--790288660e5e}/proxy-failo...@mozilla.com.xpi
Status: enabled
Name: System theme theme
Location: /usr/lib/firefox-esr/omni.ja
Package: firefox-esr
Status: enabled
Name: User-Agent Switcher and Manager
Location: ${PROFILE_EXTENSIONS}/{a6c4a591-f1b2-4f03-b3ff-767e5bedf4e7}.xpi
Status: enabled
Name: Web Compatibility Interventions
Location: /usr/lib/firefox-esr/browser/features/webcom...@mozilla.org.xpi
Package: firefox-esr
Status: enabled
Name: WebCompat Reporter
Location:
/usr/lib/firefox-esr/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox-esr
Status: user-disabled
Name: Wikipedia (en)
Location: /usr/lib/firefox-esr/browser/omni.ja
Package: firefox-esr
Status: enabled
-- Addons package information
ii firefox-esr91.3.0esr-1 amd64Mozilla Firefox web browser -
Extended Support Release (ESR)
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.14.0-3-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages firefox-esr depends on:
ii debianutils 5.5-1
ii fontconfig 2.13.1-4.2
ii libatk1.0-0 2.36.0-2
ii libc62.32-4
ii libcairo-gobject21.16.0-5
ii libcairo21.16.0-5
ii libdbus-1-3 1.12.20-3
ii libdbus-glib-1-2 0.112-2
ii libevent-2.1-7 2.1.12-stable-1
ii libffi8 3.4.2-3
ii libfontconfig1 2.13.1-4.2
ii libfreetype6 2.11.0+dfsg-1
ii libgcc-s111.2.0-10
ii libgdk-pixbuf-2.0-0 2.42.6+dfsg-2
ii libglib2.0-0 2.70.1-1
ii libgtk-3-0 3.24.30-3
ii libnspr4 2:4.32-1
ii libnss3 2:3.72-1
ii libpango-1.0-0 1.48.10+ds1-1
ii libstdc++6 11.2.0-10
ii libvpx7 1.11.0-2
ii libx11-6 2:1.7.2-2+b1
ii libx11-xcb1 2:1.7.2-2+b1
ii libxcb-shm0 1.14-3
ii libxcb1 1.14-3
ii libxcomposite1 1:0.4.5-1
ii libxdamage1 1:1.1.5-2
ii libxext6 2:1.3.4-1
ii libxfixes3 1:5.0.3-2
ii libxrender1 1:0.9.10-1
ii procps 2:3.3.17-5
ii zlib1g 1:1.2.11.dfsg-2
Versions of packages firefox-esr recommends:
ii libavcodec57 7:3.4.3-1
ii libavcodec58 7:4.4.1-1+b1
Versions of packages firefox-esr suggests:
ii fonts-lmodern 2.004.5-6.1
ii fonts-stix [otf-stix] 1.1.1-4.1
ii libcanberra0 0.30-8
ii libgssapi-krb5-2 1.18.3-7
ii pulseaudio 15.0+dfsg1-2
-- no debconf information
Bug#997206: marked as pending in irrlicht
Control: tag -1 pending Hello, Bug #997206 in irrlicht 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/games-team/irrlicht/-/commit/a865607c5f63448aa7f6c9e88f87ca17450b5627 Shuffle patches around (closes: #997206) and update packaging (this message was generated automatically) -- Greetings https://bugs.debian.org/997206
Processed: Bug#997206 marked as pending in irrlicht
Processing control commands: > tag -1 pending Bug #997206 [src:irrlicht] irrlicht: FTBFS: COSOperator.cpp:17:10: fatal error: sys/sysctl.h: No such file or directory Added tag(s) pending. -- 997206: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997206 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
