Processed: Re: celery: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13
Processing control commands:
> tags -1 + fixed-upstream patch
Bug #1015028 [src:celery] celery: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.9 3.10" returned exit code 13
Added tag(s) fixed-upstream and patch.
> forwarded -1
> https://github.com/celery/celery/commit/b260860988469ef8ad74f2d4225839c2fa91d590
Bug #1015028 [src:celery] celery: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.9 3.10" returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/celery/celery/commit/b260860988469ef8ad74f2d4225839c2fa91d590'.
> retitle -1 celery: FTBFS: test failures due to billiard upgrade: ImportError:
> cannot import name 'buf_t' from 'billiard.compat'
Bug #1015028 [src:celery] celery: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p "3.9 3.10" returned exit code 13
Changed Bug title to 'celery: FTBFS: test failures due to billiard upgrade:
ImportError: cannot import name 'buf_t' from 'billiard.compat'' from 'celery:
FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p
"3.9 3.10" returned exit code 13'.
--
1015028: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015028
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1015028: celery: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.10" returned exit code 13
Control: tags -1 + fixed-upstream patch Control: forwarded -1 https://github.com/celery/celery/commit/b260860988469ef8ad74f2d4225839c2fa91d590 Control: retitle -1 celery: FTBFS: test failures due to billiard upgrade: ImportError: cannot import name 'buf_t' from 'billiard.compat' On Sat, 16 Jul 2022 15:41:55 +0200 Lucas Nussbaum wrote: > > > from billiard.compat import buf_t, isblocking, setblocking > > E ImportError: cannot import name 'buf_t' from 'billiard.compat' > > (/usr/lib/python3/dist-packages/billiard/compat.py) This issue was caused by the update of python3-billiard to 4.0.0-1 and is fixed in celery upstream alpha version v5.3.0a1. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#984921: marked as done (rust-libsqlite3-sys: depends on multiple unavailable packages)
Your message dated Mon, 25 Jul 2022 00:51:18 -0400 with message-id <877d41re0p@fifthhorseman.net> and subject line Re: Bug#984921: rust-libsqlite3-sys: depends on multiple unavailable packages has caused the Debian Bug report #984921, regarding rust-libsqlite3-sys: depends on multiple unavailable packages 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.) -- 984921: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984921 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-libsqlite3-sys Version: 0.15.0-2 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: affects -1 + librust-libsqlite3-sys+bindgen-dev librust-libsqlite3-sys+buildtime-bindgen-dev Hi, the binary packages built from src:rust-libsqlite3-sys depend on several no longer available packages, e.g. The following packages have unmet dependencies: librust-libsqlite3-sys+bindgen-dev : Depends: librust-bindgen-0.50+default-dev but it is not installable Andreas --- End Message --- --- Begin Message --- Version: 0.25.0-1 On Wed 2021-03-10 10:43:38 +0100, Andreas Beckmann wrote: > the binary packages built from src:rust-libsqlite3-sys depend on several no > longer available packages, e.g. > > The following packages have unmet dependencies: >librust-libsqlite3-sys+bindgen-dev : Depends: > librust-bindgen-0.50+default-dev but it is not installable This has been resolved with rust-libsqlite3-sys 0.25.0-1, as it now Depends: librust-bindgen-0.60+runtime-dev, which is in both testing and unstable. --dkg signature.asc Description: PGP signature --- End Message ---
Bug#984921: rust-libsqlite3-sys: depends on multiple unavailable packages
Version: 0.25.0-1 On Wed 2021-03-10 10:43:38 +0100, Andreas Beckmann wrote: > the binary packages built from src:rust-libsqlite3-sys depend on several no > longer available packages, e.g. > > The following packages have unmet dependencies: >librust-libsqlite3-sys+bindgen-dev : Depends: > librust-bindgen-0.50+default-dev but it is not installable This has been resolved with rust-libsqlite3-sys 0.25.0-1, as it now Depends: librust-bindgen-0.60+runtime-dev, which is in both testing and unstable. --dkg signature.asc Description: PGP signature
Processed: affects 1015925, tagging 1015925
Processing commands for cont...@bugs.debian.org: > affects 1015925 + src:aptitude Bug #1015925 [libcwidget-dev] libcwidget-dev: causes aptitude FTBFS due to missing #include Added indication that 1015925 affects src:aptitude > tags 1015925 + patch Bug #1015925 [libcwidget-dev] libcwidget-dev: causes aptitude FTBFS due to missing #include Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1015925: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015925 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1015029
Processing commands for cont...@bugs.debian.org: > # > https://salsa.debian.org/python-team/packages/python-tldextract/commit/0c3de2413e8759795eafdde4d3662b184832c4eb > tags 1015029 + pending Bug #1015029 [src:tldextract] tldextract: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Ignoring request to alter tags of bug #1015029 to the same tags previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 1015029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012922: marked as done (fcoe-utils: ftbfs with GCC-12)
Your message dated Mon, 25 Jul 2022 03:34:05 + with message-id and subject line Bug#1012922: fixed in fcoe-utils 1.0.34-2 has caused the Debian Bug report #1012922, regarding fcoe-utils: ftbfs with GCC-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.) -- 1012922: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012922 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fcoe-utils Version: 1.0.34-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/fcoe-utils_1.0.34-1_unstable_gcc12.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. [...] checking whether we are cross compiling... no checking for suffix of object files... o checking whether the compiler supports GNU C... yes checking whether gcc accepts -g... yes checking for gcc option to enable C11 features... none needed checking whether gcc understands -c and -o together... yes checking for ar... ar checking the archiver (ar) interface... ar checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a race-free mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking whether make supports the include directive... yes (GNU style) checking whether make supports nested variables... yes checking dependency style of gcc... none checking for gcc... (cached) gcc checking whether the compiler supports GNU C... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to enable C11 features... (cached) none needed checking whether gcc understands -c and -o together... (cached) yes checking for ranlib... ranlib checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for lldpad >= 0.9.46... yes checking for pciaccess... yes checking for pkg-config... (cached) /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking that generated files are newer than configure... done configure: creating ./config.status config.status: creating Makefile config.status: creating fcoe-utils.spec config.status: creating include/fcoe_utils_version.h config.status: executing depfiles commands make[1]: Leaving directory '/<>' dh_auto_build make -j8 make[1]: Entering directory '/<>' gcc -DPACKAGE_NAME=\"fcoe-utils\" -DPACKAGE_TARNAME=\"fcoe-utils\" -DPACKAGE_VERSION=\"1.0.34\" -DPACKAGE_STRING=\"fcoe-utils\ 1.0.34\" -DPACKAGE_BUGREPORT=\"https://github.com/openSUSE/fcoe-utils\"; -DPACKAGE_URL=\"\" -DPACKAGE=\"fcoe-utils\" -DVERSION=\"1.0.34\" -I. -I./include -I./include -DSYSCONFDIR="\"/etc\"" -D_FORTIFY_SOURCE=2 -Wdate-time -D_FORTIFY_SOURCE=2 -Wall -Wformat=2 -Werror -Wextra -Wmissing-prototypes -Wstrict-prototypes -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -c -o fcoeadm-fcoeadm.o `test -f 'fcoeadm.c' || echo './'`fcoeadm.c gcc -DPACKAGE_NAME=\"fcoe-utils\" -DPACKAGE_TARNAME=\"fcoe-utils\" -DPACKAGE_VERSION=\"1.0.34\" -DPACKAGE_STRING=\"fcoe-utils\ 1.0.34\" -DPACKAGE_BUGREPORT=\"https://github.com/openSUSE/fcoe-utils\"; -DPACKAGE_URL=\"\" -DPACKAGE=\"fcoe-utils\" -DVERSION=\"1.0.34\" -I. -I./include -I./include -DSYSC
Processed: Bug#1015029 marked as pending in tldextract
Processing control commands: > tag -1 pending Bug #1015029 [src:tldextract] tldextract: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Added tag(s) pending. -- 1015029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015029: marked as pending in tldextract
Control: tag -1 pending Hello, Bug #1015029 in tldextract 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-tldextract/-/commit/0c3de2413e8759795eafdde4d3662b184832c4eb Manually clean _version.py since pybuild doesn't yet (Closes: #1015029) (this message was generated automatically) -- Greetings https://bugs.debian.org/1015029
Bug#1013008: marked as done (opencc: ftbfs with GCC-12)
Your message dated Mon, 25 Jul 2022 00:48:59 +
with message-id
and subject line Bug#1013008: fixed in opencc 1.1.4+ds1-3
has caused the Debian Bug report #1013008,
regarding opencc: ftbfs with GCC-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.)
--
1013008: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:opencc
Version: 1.1.4+ds1-1
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12
[This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.
The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/opencc_1.1.4+ds1-1_unstable_gcc12.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.
[...]
dh_strip -a -O--buildsystem=cmake -O--no-parallel
dh_makeshlibs -a -O--buildsystem=cmake -O--no-parallel
dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see
diff output below
dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols
file: see diff output below
dpkg-gensymbols: warning: debian/libopencc1.1/DEBIAN/symbols doesn't match
completely debian/libopencc1.1.symbols
--- debian/libopencc1.1.symbols (libopencc1.1_1.1.4+ds1-1_amd64)
+++ dpkg-gensymbolszPa1vw 2022-06-10 08:59:36.473031953 +
@@ -68,7 +68,7 @@
_ZN6opencc15SimpleConverterC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base
1.1.1+git20200624+ds2
_ZN6opencc15SimpleConverterD1Ev@Base 1.1.1+git20200624+ds2
_ZN6opencc15SimpleConverterD2Ev@Base 1.1.1+git20200624+ds2
- (arch=!amd64 !arm64
!x32)_ZN6opencc16DictEntryFactory3NewEPKNS_9DictEntryE@Base 1.1.3+ds1
+ _ZN6opencc16DictEntryFactory3NewEPKNS_9DictEntryE@Base 1.1.3+ds1
_ZN6opencc16NoValueDictEntryD0Ev@Base 1.1.1+git20200624+ds2
_ZN6opencc16NoValueDictEntryD1Ev@Base 1.1.1+git20200624+ds2
_ZN6opencc16NoValueDictEntryD2Ev@Base 1.1.1+git20200624+ds2
@@ -209,6 +209,7 @@
(subst)_ZNK6opencc9DictGroup16MatchAllPrefixesEPKc{size_t}@Base
1.1.1+git20200624+ds2
(subst)_ZNK6opencc9DictGroup5MatchEPKc{size_t}@Base 1.1.1+git20200624+ds2
_ZNK6opencc9Exception4whatEv@Base 1.1.1+git20200624+ds2
+
_ZNSt10_HashtableIN6opencc19UTF8StringSliceBaseIhEESt4pairIKS2_NS0_13PhraseExtract7SignalsEESaIS7_ENSt8__detail10_Select1stESt8equal_toIS2_ENS2_6HasherENS9_18_Mod_range_hashingENS9_20_Default_ranged_hashENS9_20_Prime_rehash_policyENS9_17_Hashtable_traitsILb1ELb0ELb19_M_rehashEmRKm@Base
1.1.4+ds1-1
(subst)_ZNSt10_HashtableIN6opencc19UTF8StringSliceBaseIhEESt4pairIKS2_{size_t}ESaIS5_ENSt8__detail10_Select1stESt8equal_toIS2_ENS2_6HasherENS7_18_Mod_range_hashingENS7_20_Default_ranged_hashENS7_20_Prime_rehash_policyENS7_17_Hashtable_traitsILb1ELb0ELb19_M_rehashE{size_t}RK{size_t}@Base
1.1.1+git20200624+ds2
(subst)_ZNSt10_HashtableIN6opencc19UTF8StringSliceBaseIhEESt4pairIKS2_{size_t}ESaIS5_ENSt8__detail10_Select1stESt8equal_toIS2_ENS2_6HasherENS7_18_Mod_range_hashingENS7_20_Default_ranged_hashENS7_20_Prime_rehash_policyENS7_17_Hashtable_traitsILb1ELb0ELb1D1Ev@Base
1.1.1+git20200624+ds2
(subst)_ZNSt10_HashtableIN6opencc19UTF8StringSliceBaseIhEESt4pairIKS2_{size_t}ESaIS5_ENSt8__detail10_Select1stESt8equal_toIS2_ENS2_6HasherENS7_18_Mod_range_hashingENS7_20_Default_ranged_hashENS7_20_Prime_rehash_policyENS7_17_Hashtable_traitsILb1ELb0ELb1D2Ev@Base
1.1.1+git20200624+ds2
@@ -377,6 +378,7 @@
(optional=templinst|arch
Bug#1015998: boost1.74: shlibs don't generate *-py310 dependencies with Python 3.10
Source: boost1.74
Version: 1.74.0-16.1
Severity: serious
override_dh_makeshlibs:
dh_makeshlibs -plibboost-regex$(SOVERSION) -V '$(regexicuabi)'
dh_makeshlibs --remaining-packages
sed -i -r 's/^(libboost_python([0-9]{2}) \S+ (\S+).*)$$/\1, \3-py\2/'
debian/libboost-python$(SOVERSION)/DEBIAN/shlibs
sed -i -r 's/^(libboost_mpi_python([0-9]{2}) \S+ (\S+).*)$$/\1,
\3-py\2/' debian/libboost-mpi-python$(SOVERSION)/DEBIAN/shlibs
ifeq ($(BUILD_NUMPY), yes)
sed -i -r 's/^(libboost_numpy([0-9]{2}) \S+ (\S+).*)$$/\1, \3-py\2/'
debian/libboost-numpy$(SOVERSION)/DEBIAN/shlibs
endif
These {2} should be {3} to work with Python 3.10.
Bug#1015995: gpgme1.0 FTBFS with 3.10 as only supported Python3 version
Source: gpgme1.0 Version: 1.17.1-4 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=gpgme1.0&ver=1.17.1-4%2Bb1 ... Making check in tests make[5]: Entering directory '/<>/build/lang/python/tests' make all-am make[6]: Entering directory '/<>/build/lang/python/tests' make[6]: Nothing to be done for 'all-am'. make[6]: Leaving directory '/<>/build/lang/python/tests' GNUPGHOME=/<>/build/lang/python/tests LC_ALL=C GPG_AGENT_INFO= top_srcdir=../../../.. srcdir=../../../../lang/python/tests LD_LIBRARY_PATH="../../../src/.libs:" ../../../../lang/python/tests/run-tests.py \ --interpreters="/usr/bin/python3.10 " --srcdir=../../../../lang/python/tests \ initial.py t-wrapper.py t-callbacks.py t-data.py t-encrypt.py t-encrypt-sym.py t-encrypt-sign.py t-sign.py t-signers.py t-decrypt.py t-verify.py t-decrypt-verify.py t-sig-notation.py t-export.py t-import.py t-edit.py t-keylist.py t-keylist-from-data.py t-wait.py t-encrypt-large.py t-file-name.py t-idiomatic.py t-protocol-assuan.py t-quick-key-creation.py t-quick-subkey-creation.py t-quick-key-manipulation.py t-quick-key-signing.py final.py /bin/bash: line 1: ../../../../lang/python/tests/run-tests.py: Permission denied make[5]: *** [Makefile:621: xcheck] Error 126
Bug#1015994: python3-csound depends on python3.9 that will be removed
Package: python3-csound Version: 1:6.17.0~dfsg-3 Severity: serious python3-csound depends on python3.9 that will be removed. A no-change source upload would fix this, but override_dh_python3 forcing a versioned dependency looks bogus and should be dropped.
Processed: pacparser: diff for NMU version 1.3.6-1.3
Processing control commands: > tags 965765 + patch Bug #965765 [src:pacparser] pacparser: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) patch. > tags 965765 + pending Bug #965765 [src:pacparser] pacparser: Removal of obsolete debhelper compat 5 and 6 in bookworm Added tag(s) pending. -- 965765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965765: pacparser: diff for NMU version 1.3.6-1.3
Control: tags 965765 + patch Control: tags 965765 + pending Dear maintainer, I've prepared an NMU for pacparser (versioned as 1.3.6-1.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru pacparser-1.3.6/debian/changelog pacparser-1.3.6/debian/changelog --- pacparser-1.3.6/debian/changelog 2020-03-02 07:22:40.0 +0200 +++ pacparser-1.3.6/debian/changelog 2022-07-25 00:20:17.0 +0300 @@ -1,3 +1,10 @@ +pacparser (1.3.6-1.3) unstable; urgency=low + + * Non-maintainer upload. + * debian/compat: 5 -> 7. (Closes: #965765) + + -- Adrian Bunk Mon, 25 Jul 2022 00:20:17 +0300 + pacparser (1.3.6-1.2) unstable; urgency=medium * Non-maintainer upload. diff -Nru pacparser-1.3.6/debian/compat pacparser-1.3.6/debian/compat --- pacparser-1.3.6/debian/compat 2015-09-04 23:06:41.0 +0300 +++ pacparser-1.3.6/debian/compat 2022-07-25 00:20:17.0 +0300 @@ -1 +1 @@ -5 +7
Bug#1013027: marked as done (qtwebkit-opensource-src: ftbfs with GCC-12)
Your message dated Sun, 24 Jul 2022 21:19:57 + with message-id and subject line Bug#1013027: fixed in qtwebkit-opensource-src 5.212.0~alpha4-20 has caused the Debian Bug report #1013027, regarding qtwebkit-opensource-src: ftbfs with GCC-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.) -- 1013027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:qtwebkit-opensource-src Version: 5.212.0~alpha4-16 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/qtwebkit-opensource-src_5.212.0~alpha4-16_unstable_gcc12.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. [...] -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.212.0 -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5 -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libQt5WebKit.so -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QtWebKit/libqmlwebkitplugin.so -- Set runtime path of "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QtWebKit/libqmlwebkitplugin.so" to "" -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QtWebKit/qmldir -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QtWebKit/plugins.qmltypes -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QtWebKit/experimental/libqmlwebkitexperimentalplugin.so -- Set runtime path of "/<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QtWebKit/experimental/libqmlwebkitexperimentalplugin.so" to "" -- Installing: /<>/debian/tmp/usr/lib/x86_64-linux-gnu/qt5/qml/QtWebKit/experimental/qmldir -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/qt5/QtWebKit/5.212.0/QtWebKit/private/qquicknetworkreply_p.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/qt5/QtWebKit/5.212.0/QtWebKit/private/qquicknetworkrequest_p.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/qt5/QtWebKit/5.212.0/QtWebKit/private/qquickurlschemedelegate_p.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/qt5/QtWebKit/5.212.0/QtWebKit/private/qquickwebpage_p.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/qt5/QtWebKit/5.212.0/QtWebKit/private/qquickwebpage_p_p.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/qt5/QtWebKit/5.212.0/QtWebKit/private/qquickwebview_p.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/qt5/QtWebKit/5.212.0/QtWebKit/private/qquickwebview_p_p.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/qt5/QtWebKit/5.212.0/QtWebKit/private/qtwebsecurityorigin_p.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/qt5/QtWebKit/5.212.0/QtWebKit/private/qwebchannelwebkittransport_p.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/qt5/QtWebKit/5.212.0/QtWebKit/private/qwebdownloaditem_p.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/qt5/QtWebKit/5.212.0/QtWebKit/private/qwebdownloaditem_p_p.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/qt5/QtWebKit/5.212.0/QtWebKit/private/qwebiconimageprovider_p.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-gnu/qt5/QtWebKit/5.212.0/QtWebKit/private/qwebkittest_p.h -- Installing: /<>/debian/tmp/usr/include/x86_64-linux-
Bug#1012899: marked as done (bambootracker: ftbfs with GCC-12)
Your message dated Sun, 24 Jul 2022 21:03:59 + with message-id and subject line Bug#1012899: fixed in bambootracker 0.5.1-1 has caused the Debian Bug report #1012899, regarding bambootracker: ftbfs with GCC-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.) -- 1012899: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:bambootracker Version: 0.5.0-1 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/bambootracker_0.5.0-1_unstable_gcc12.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. [...] g++ -c -pipe -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++1y -pthread -pthread -Wall -Wextra -Wall -Wextra -Werror -pedantic -pedantic-errors -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ -D_REENTRANT -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -Iinstrument -Imodule -I../submodules/emu2149/src -I/usr/include/rtaudio -I/usr/include/rtmidi -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o order_list_common_qt_command.o gui/command/order/order_list_common_qt_command.cpp g++ -c -pipe -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++1y -pthread -pthread -Wall -Wextra -Wall -Wextra -Werror -pedantic -pedantic-errors -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ -D_REENTRANT -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -Iinstrument -Imodule -I../submodules/emu2149/src -I/usr/include/rtaudio -I/usr/include/rtmidi -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o pattern_editor_common_qt_command.o gui/command/pattern/pattern_editor_common_qt_command.cpp g++ -c -pipe -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++1y -pthread -pthread -Wall -Wextra -Wall -Wextra -Werror -pedantic -pedantic-errors -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS -D__LINUX_ALSA__ -D__LINUX_PULSE__ -D__UNIX_JACK__ -D_REENTRANT -DQT_NO_DEBUG -DQT_WIDGETS_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I. -Iinstrument -Imodule -I../submodules/emu2149/src -I/usr/include/rtaudio -I/usr/include/rtmidi -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I. -I. -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -o drop_detect_list_widget.o gui/drop_detect_list_widget.cpp g++ -c -pipe -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++1y -pthread -pthread -Wall -Wextra -Wall -Wextra -Werror -pedantic
Processed: Bug#1013027 marked as pending in qtwebkit-opensource-src
Processing control commands: > tag -1 pending Bug #1013027 [src:qtwebkit-opensource-src] qtwebkit-opensource-src: ftbfs with GCC-12 Added tag(s) pending. -- 1013027: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013027 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013027: marked as pending in qtwebkit-opensource-src
Control: tag -1 pending Hello, Bug #1013027 in qtwebkit-opensource-src 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/qt-kde-team/qt/qt5webkit/-/commit/7944fb5604c95e1edcc7d394ca421d259ab89c55 Update debian/libqt5webkit5.symbols for GCC 12. Closes: #1013027. (this message was generated automatically) -- Greetings https://bugs.debian.org/1013027
Bug#1015992: python-jpype FTBFS with 3.10 as only supported Python3 version
Source: python-jpype Version: 1.4.0-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=python-jpype&ver=1.4.0-1%2Bb1 ... debian/rules override_jh_installlibs make[1]: Entering directory '/<>' jh_installlibs rm /<>/debian/python3-jpype/usr/lib/python3/dist-packages/org.jpype.jar rm /<>/debian/python3-jpype/usr/lib/python3.10/dist-packages/org.jpype.jar rm: cannot remove '/<>/debian/python3-jpype/usr/lib/python3.10/dist-packages/org.jpype.jar': No such file or directory make[1]: *** [debian/rules:17: override_jh_installlibs] Error 1
Processed: retitle 1015990 to libgetdata FTBFS with 3.10 as only supported Python3 version
Processing commands for cont...@bugs.debian.org: > retitle 1015990 libgetdata FTBFS with 3.10 as only supported Python3 version Bug #1015990 [src:libgetdata] libgetdataFTBFS with Python 3.10 as only supported Python3 version Changed Bug title to 'libgetdata FTBFS with 3.10 as only supported Python3 version' from 'libgetdataFTBFS with Python 3.10 as only supported Python3 version'. > thanks Stopping processing here. Please contact me if you need assistance. -- 1015990: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015990 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1015805: marked as done (scikit-learn tries to access network during documentation build)
Your message dated Sun, 24 Jul 2022 20:47:48 + with message-id and subject line Bug#1015805: fixed in scikit-learn 1.1.1-2 has caused the Debian Bug report #1015805, regarding scikit-learn tries to access network during documentation build to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1015805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: scikit-learn Version: 1.1.1-1 Severity: serious Justification: Policy section 4.9 violation There are loads of similar traceback message saying the documentation build has failed to retrieve some URL, like this: ``` generating gallery for auto_examples/decomposition... [ 30%] plot_faces_decomposition.py WARNING: /<>/examples/decomposition/plot_faces_decomposition.py failed to execute correctly: Traceback (most recent ca ll last): File "/<>/examples/decomposition/plot_faces_decomposition.py", line 36, in faces, _ = fetch_olivetti_faces(return_X_y=True, shuffle=True, random_state=rng) File "/<>/.pybuild/cpython3_3.10/build/sklearn/datasets/_olivetti_faces.py", line 117, in fetch_olivetti_faces mat_path = _fetch_remote(FACES, dirname=data_home) File "/<>/.pybuild/cpython3_3.10/build/sklearn/datasets/_base.py", line 1511, in _fetch_remote urlretrieve(remote.url, file_path) File "/usr/lib/python3.10/urllib/request.py", line 241, in urlretrieve with contextlib.closing(urlopen(url, data)) as fp: File "/usr/lib/python3.10/urllib/request.py", line 216, in urlopen return opener.open(url, data, timeout) File "/usr/lib/python3.10/urllib/request.py", line 519, in open response = self._open(req, data) File "/usr/lib/python3.10/urllib/request.py", line 536, in _open result = self._call_chain(self.handle_open, protocol, protocol + File "/usr/lib/python3.10/urllib/request.py", line 496, in _call_chain result = func(*args) File "/usr/lib/python3.10/urllib/request.py", line 1391, in https_open return self.do_open(http.client.HTTPSConnection, req, File "/usr/lib/python3.10/urllib/request.py", line 1351, in do_open raise URLError(err) urllib.error.URLError: ``` This is clearly policy violation and should be patched. This issue is found during the QEMU build on ppc64el machine for the armel architecture, and it extremly slows down the building process likely due to URL access timeout. As a result, the URL access timeout took the whole night and the doc build is not yet finished by a half. Well, I guess I will have to wait for two or three days to see the discussed armel segfault in qemu with this problem unfixed. --- End Message --- --- Begin Message --- Source: scikit-learn Source-Version: 1.1.1-2 Done: Mo Zhou We believe that the bug you reported is fixed in the latest version of scikit-learn, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maint
Bug#1015990: libgetdataFTBFS with Python 3.10 as only supported Python3 version
Source: libgetdata Version: 0.11.0-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=libgetdata&ver=0.11.0-3%2Bb1 ... dh_install -a install -d debian/.debhelper/generated/libgetdata-doc install -d debian/libgetdata-dev//usr/include cp --reflink=auto -a debian/tmp/usr/include/getdata debian/tmp/usr/include/getdata.f debian/tmp/usr/include/getdata.h debian/libgetdata-dev//usr/include/ install -d debian/libgetdata-dev//usr/lib/x86_64-linux-gnu cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.a debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.so debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.a debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.so debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.a debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.so debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.a debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.so debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/ install -d debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/getdata cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatabzip2-0.11.0.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatabzip2.a debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatabzip2.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdataflac-0.11.0.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdataflac.a debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdataflac.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatagzip-0.11.0.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatagzip.a debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatagzip.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatalzma-0.11.0.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatalzma.a debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatalzma.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatazzip-0.11.0.so debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatazzip.a debian/tmp/usr/lib/x86_64-linux-gnu/getdata/libgetdatazzip.so debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/getdata/ install -d debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/pkgconfig cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/getdata.pc debian/libgetdata-dev//usr/lib/x86_64-linux-gnu/pkgconfig/ install -d debian/.debhelper/generated/libgetdata-dev install -d debian/libgetdata8//usr/lib/x86_64-linux-gnu cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.so.8 debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata.so.8.1.0 debian/libgetdata8//usr/lib/x86_64-linux-gnu/ install -d debian/.debhelper/generated/libgetdata8 install -d debian/libgetdata\+\+7//usr/lib/x86_64-linux-gnu cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.so.7 debian/tmp/usr/lib/x86_64-linux-gnu/libgetdata\+\+.so.7.1.0 debian/libgetdata\+\+7//usr/lib/x86_64-linux-gnu/ install -d debian/.debhelper/generated/libgetdata\+\+7 install -d debian/libfgetdata6//usr/lib/x86_64-linux-gnu cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.so.6 debian/tmp/usr/lib/x86_64-linux-gnu/libfgetdata.so.6.1.0 debian/libfgetdata6//usr/lib/x86_64-linux-gnu/ install -d debian/.debhelper/generated/libfgetdata6 install -d debian/libf95getdata7//usr/lib/x86_64-linux-gnu cp --reflink=auto -a debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.so.7 debian/tmp/usr/lib/x86_64-linux-gnu/libf95getdata.so.7.1.0 debian/libf95getdata7//usr/lib/x86_64-linux-gnu/ install -d debian/.debhelper/generated/libf95getdata7 install -d debian/libgetdata-tools//usr/bin cp --reflink=auto -a debian/tmp/usr/bin/checkdirfile debian/tmp/usr/bin/dirfile2ascii debian/libgetdata-tools//usr/bin/ install -d debian/libgetdata-tools//usr/share/man/man1 cp --reflink=auto -a debian/tmp/usr/share/man/man1/checkdirfile.1 debian/tmp/usr/share/man/man1/dirfile2ascii.1 debian/libgetdata-tools//usr/share/man/man1/ dh_install: warning: Cannot find (any matches for) "usr/lib/python3*/site-packages/pygetdata*so" (tried in ., debian/tmp) dh_install: warning: python3-pygetdata missing files: usr/lib/python3*/site-packages/pygetdata*so dh_install: error: missing files, aborting install -d debian/.debhelper/generated/libgetdata-tools install -d debian/.debhelper/generated/python3-pygetdata install -d debian/.debhelper/generated/libgetdata-perl make: *** [debian/rules:28: binary-arch] Error 25
Bug#1015978: Should falcon be removed?
Hi Moritz, thanks for bringing this up. I agree that falcon your point is perfectly valid. On the other hand we have a new upstream version in Git which now depends from Python3 and is a promising candidate to fix the Python3 bug. Unfortunately the package does not build[1] which is probably a gcc issue. If someone would volunteer to fix this issue we might be able to keep the package. If there is no response in say two weeks we should probably remove it since it becomes obvious that there is no interest in this package. Kind regards Andreas. [1] https://salsa.debian.org/med-team/falcon/-/jobs/3033927 Am Sun, Jul 24, 2022 at 08:13:58PM +0200 schrieb Moritz Muehlenhoff: > Source: falcon > Version: 1.8.8-1 > Severity: serious > > Your package came up as a candidate for removal from Debian: > - Still depends on Python 2 > - Dropped from testing in 2018 > - Last upload in 2017 > > If you disagree and want to continue to maintain this package, > please just close this bug (and fix the open issues). > > If you agree with the removal, please reassign to ftp.debian.org > by sending the following commands to cont...@bugs.debian.org: > > -- > severity $BUGNUM normal > reassign $BUGNUM ftp.debian.org > retitle $BUGNUM RM: -- RoM; > thx > -- > > Otherwise I'll move forward and request it's removal in a month. > > Cheers, > Moritz > > ___ > Debian-med-packaging mailing list > debian-med-packag...@alioth-lists.debian.net > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging > -- http://fam-tille.de
Processed: Bug#1013020 marked as pending in qbs
Processing control commands: > tag -1 pending Bug #1013020 [src:qbs] qbs: ftbfs with GCC-12 Added tag(s) pending. -- 1013020: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013020 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1013020: marked as pending in qbs
Control: tag -1 pending Hello, Bug #1013020 in qbs 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/qt-kde-team/qt/qbs/-/commit/99055c82fd9068f551589d421d9486da6f7899df Update debian/libqbscore1.23.symbols for new release and GCC 12. Closes: #1013020. (this message was generated automatically) -- Greetings https://bugs.debian.org/1013020
Bug#1015986: guacamole-client: CVE-2021-41767 CVE-2021-43999 CVE-2020-11997
Source: guacamole-client X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for guacamole-client. CVE-2021-41767[0]: | Apache Guacamole 1.3.0 and older may incorrectly include a private | tunnel identifier in the non-private details of some REST responses. | This may allow an authenticated user who already has permission to | access a particular connection to read from or interact with another | user's active use of that same connection. https://www.openwall.com/lists/oss-security/2022/01/11/6 CVE-2021-43999[1]: | Apache Guacamole 1.2.0 and 1.3.0 do not properly validate responses | received from a SAML identity provider. If SAML support is enabled, | this may allow a malicious user to assume the identity of another | Guacamole user. https://www.openwall.com/lists/oss-security/2022/01/11/7 CVE-2020-11997[2]: | Apache Guacamole 1.2.0 and earlier do not consistently restrict access | to connection history based on user visibility. If multiple users | share access to the same connection, those users may be able to see | which other users have accessed that connection, as well as the IP | addresses from which that connection was accessed, even if those users | do not otherwise have permission to see other users. https://lists.apache.org/thread.html/r1a9ae9d1608c9f846875c4191cd738f95543d1be06b52dc1320e8117%40%3Cannounce.guacamole.apache.org%3E https://issues.apache.org/jira/browse/GUACAMOLE-1123 https://github.com/apache/guacamole-client/pulls?q=is%3Apr+guacamole-1123+is%3Aclosed https://github.com/glyptodon/guacamole-client/pull/453 https://enterprise.glyptodon.com/doc/latest/cve-2020-11997-inconsistent-restriction-of-connection-history-visibility-31424710.html https://enterprise.glyptodon.com/doc/1.x/changelog-950368.html#id-.Changelogv1.x-1.14 If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2021-41767 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41767 [1] https://security-tracker.debian.org/tracker/CVE-2021-43999 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-43999 [2] https://security-tracker.debian.org/tracker/CVE-2020-11997 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11997 Please adjust the affected versions in the BTS as needed.
Bug#1015983: undertow: CVE-2021-3859
Source: undertow X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for undertow. CVE-2021-3859[0]: https://bugzilla.redhat.com/show_bug.cgi?id=2010378 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-3859 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3859 Please adjust the affected versions in the BTS as needed.
Bug#1009281: [Debichem-devel] Bug#1009281: Bug#1009281: Should cinfony be removed?
Am Mon, Apr 11, 2022 at 09:21:25AM +0200 schrieb Michael Banck: > Hi, > > On Mon, Apr 11, 2022 at 08:38:21AM +0300, Andrius Merkys wrote: > > Hi, > > > > On 2022-04-11 01:35, Moritz Muehlenhoff wrote: > > > Source: cinfony > > > Version: 1.2-4 > > > Severity: serious > > > > > > Your package came up as a candidate for removal from Debian: > > > > > > - Still depends on Python 2 and thus removed from testing since 2019 > > > - Dead upstream > > > - No reverse dependencies > > > > Incidentally, I was the last to upload this package. Since 2019 there > > were no uploads, due to aforementioned reasons. I have contemplated > > filing for RM ever since, but did not get to it. I think it is fine to > > remove. If Python 3 port ever happens, we can reintroduce the package then. > > I contacted the author and asked him about it - it seems the master > branch on Github has python3 support, but I didn't look very closely. Did you get any reply? Otherwise let's go ahead with the removal. Cheers, Moritz
Bug#1015980: Should pd-aubio be removed?
Source: pd-aubio Version: 0.4-1 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Last upload in 2014 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015981: Should grokmirror be removed?
Source: grokmirror Version: 1.0.0-1.1 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Last maintainer upload in 2016 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015979: Should python-unshare be removed?
Source: python-unshare Version: 0.2-1 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Last upload in 2016 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.16.0-6-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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
Bug#1015978: Should falcon be removed?
Source: falcon Version: 1.8.8-1 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Dropped from testing in 2018 - Last upload in 2017 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015977: Should vland be removed?
Source: vland Version: 0.8-1 Severity: serious Your package came up as a candidate for removal from Debian, it's one of the few remaining packages still depending on Python 2 and there're no visible upstream activity to port it to vland? If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015976: Should vmm be removed?
Source: vmm Version: 0.6.2-2 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Last upload in 2017, removed from testing since 2019 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015975: Should python-neuroshare be removed?
Source: python-neuroshare Version: 0.9.2-1 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Last upload in 2014 - Dead upstream (last commits from 2016) If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015974: Should gnat-gps be removed?
Source: gnat-gps Version: 19.2-3 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - Removed from testing since 2019 If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015973: Should xdeb be removed?
Source: xdeb Version: 0.6.7 Severity: serious Your package came up as a candidate for removal from Debian: - Still depends on Python 2 - No upload since five years If you disagree and want to continue to maintain this package, please just close this bug (and fix the open issues). If you agree with the removal, please reassign to ftp.debian.org by sending the following commands to cont...@bugs.debian.org: -- severity $BUGNUM normal reassign $BUGNUM ftp.debian.org retitle $BUGNUM RM: -- RoM; thx -- Otherwise I'll move forward and request it's removal in a month. Cheers, Moritz
Bug#1015765: marked as done (openrc: command_user flag in openrc-run does not function properly)
Your message dated Sun, 24 Jul 2022 16:50:24 + with message-id and subject line Bug#1015765: fixed in openrc 0.45.2-1 has caused the Debian Bug report #1015765, regarding openrc: command_user flag in openrc-run does not function properly 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.) -- 1015765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openrc Version: 0.42-2.1 Severity: grave Tags: newcomer security Justification: user security hole Dear Maintainer, I am coming from Devuan and was advised to submit a bug report here as the package is identical. I hope this will not be a problem. In any case, openrc-run's command_user flag does not function properly. If both a user and group are specified, an error is returned: "start-stop-daemon: user '$user:$group' not found", even if that user and group exist. If only the user is specified, the script will run, but as root, rather than as the user specified (which is the intended behavior); the username specified is then passed to the command run as an argument (not intended behavior). I was able to make this option work as intended by editing /lib/rc/sh/start-stop-daemon.sh, and changing --user in line 58 to --chuid. I have not submitted a PR because in upstream, --chuid is being deprecated in favor of --user, which does the same thing and therefore there is no issue. On Debian, however, these flags apparently do different things, which causes this problem. I don't understand very well Debian's package's differences from upstream or why this difference exists, but I assume it may be desirable to increase compatibility with upstream (though again, I don't know what the rationale for the current state of things is). That being said, simply changing --user to --chuid would be a fairly simple fix, and since I understand openrc is no longer maintained, this may be the best option. In case it's helpful, one of the Devuan maintainers found this issue on OpenRC's github, reporting the same issue: https://github.com/OpenRC/openrc/issues/383. I assume this was never reported. Best, Adam --- End Message --- --- Begin Message --- Source: openrc Source-Version: 0.45.2-1 Done: Mark Hindley We believe that the bug you reported is fixed in the latest version of openrc, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Mark Hindley (supplier of updated openrc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 24 Jul 2022 15:32:06 +0100 Source: openrc Architecture: source Version: 0.45.2-1 Distribution: unstable Urgency: medium Maintainer: OpenRC Debian Maintainers Changed-By: Mark Hindley Closes: 973245 1015765 Changes: openrc (0.45.2-1) unstable; urgency=medium . * d/watch: update to version 4 and fix path. * New upstream version 0.45.2 - includes fix for CVE-2018-21269 (Closes: #973245). * d/control: - add myself to uploaders. - bump debhelper compat to 13. - add Build-Depends meson, pkg-config. - bump Standards Version to 4.6.1 (no changes). * debian/patches: - remove obsolete d/p/0001-no-rpath.patch. - delete patches applied upstream. - convert to meson - refresh. * d/rules: - convert to meson - override libexecdir to keep existing non-multiarch path. - cleanup and remove cruft. * Simplify d/rules and multiarch handling with dh-exec. * Install bash and zsh completions. * d/not-installed: add uninstalled files. * .gitignore backup files. * d/openrc.lintian-overrides: - update changed tag name. - update to pointed format. - remove unused override. * sh/start-stop-daemon.sh: use src:dpkg s-s-d compatible --chuid (Closes: #1015765). Checksums-Sha1: 960a37fa530d1e6eea59a7fc3e22a7956e415450 2283 openrc_0.45.2-1.dsc f61b8f40e9b2bd94a09a2ddd834d42c76a45b2d4 192020 openrc_0.45.2.orig.tar.xz 64a6daac79f69a67b41646d156f83a9bf37c2c03 24820 openrc_0.45.2-1.debian.tar.xz 04f4357d0257c144d67a68f1d5aa25695204d4f3 9205 openrc_0
Processed: affects 1011678
Processing commands for cont...@bugs.debian.org:
> affects 1011678 src:libqapt
Bug #1011678 {Done: Julian Andres Klode } [src:apt]
python-apt: FTBFS: deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has not
been declared
Bug #1011720 {Done: Julian Andres Klode } [src:apt] libqapt:
FTBFS: deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has not been declared
Added indication that 1011678 affects src:libqapt
Added indication that 1011720 affects src:libqapt
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1011678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011678
1011720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: fixed 1011678 in apt/2.5.2, forcibly merging 1011678 1011720
Processing commands for cont...@bugs.debian.org:
> fixed 1011678 apt/2.5.2
Bug #1011678 {Done: Julian Andres Klode } [src:apt]
python-apt: FTBFS: deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has not
been declared
The source apt and version 2.5.2 do not appear to match any binary packages
Marked as fixed in versions apt/2.5.2.
> forcemerge 1011678 1011720
Bug #1011678 {Done: Julian Andres Klode } [src:apt]
python-apt: FTBFS: deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has not
been declared
Bug #1011720 [src:apt] libqapt: FTBFS: deblistparser.h:48:65: error:
‘pkgTagSection::Key’ has not been declared
Marked Bug as done
Removed indication that 1011720 affects src:libqapt
Added indication that 1011720 affects src:python-apt
The source apt and version 2.5.2 do not appear to match any binary packages
Marked as fixed in versions apt/2.5.2.
Merged 1011678 1011720
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1011678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011678
1011720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: reassign 1011678 to src:apt, affects 1011678, reassign 1011720 to src:apt, affects 1011720
Processing commands for cont...@bugs.debian.org:
> reassign 1011678 src:apt apt/2.5.0
Bug #1011678 {Done: Julian Andres Klode } [src:python-apt]
python-apt: FTBFS: deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has not
been declared
Bug reassigned from package 'src:python-apt' to 'src:apt'.
No longer marked as found in versions python-apt/2.3.0.
No longer marked as fixed in versions apt/2.5.2.
Bug #1011678 {Done: Julian Andres Klode } [src:apt]
python-apt: FTBFS: deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has not
been declared
Marked as found in versions apt/2.5.0.
> affects 1011678 src:python-apt
Bug #1011678 {Done: Julian Andres Klode } [src:apt]
python-apt: FTBFS: deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has not
been declared
Added indication that 1011678 affects src:python-apt
> reassign 1011720 src:apt apt/2.5.0
Bug #1011720 [src:libqapt] libqapt: FTBFS: deblistparser.h:48:65: error:
‘pkgTagSection::Key’ has not been declared
Bug reassigned from package 'src:libqapt' to 'src:apt'.
No longer marked as found in versions libqapt/3.0.5-1.
Ignoring request to alter fixed versions of bug #1011720 to the same values
previously set
Bug #1011720 [src:apt] libqapt: FTBFS: deblistparser.h:48:65: error:
‘pkgTagSection::Key’ has not been declared
Marked as found in versions apt/2.5.0.
> affects 1011720 src:libqapt
Bug #1011720 [src:apt] libqapt: FTBFS: deblistparser.h:48:65: error:
‘pkgTagSection::Key’ has not been declared
Added indication that 1011720 affects src:libqapt
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1011678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011678
1011720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011720
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1011678: marked as done (python-apt: FTBFS: deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has not been declared)
Your message dated Sun, 24 Jul 2022 16:19:03 + with message-id and subject line Bug#1011678: fixed in apt 2.5.2 has caused the Debian Bug report #1011678, regarding python-apt: FTBFS: deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has not been declared 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.) -- 1011678: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1011678 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-apt Version: 2.3.0 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220525 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g > -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat > -Werror=format-security -g -fwrapv -O2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wno-write-strings -DDATE="Oct 22 2021" > -DTIME="10:21:54" -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -I/usr/include/python3.9 -c python/acquire-item.cc -o > build/temp.linux-x86_64-3.9/python/acquire-item.o -std=c++11 > -Wno-write-strings -DAPT_8_CLEANER_HEADERS -DAPT_9_CLEANER_HEADERS > -DAPT_10_CLEANER_HEADERS -DPY_SSIZE_T_CLEAN > In file included from python/apt_pkgmodule.h:19, > from python/acquire-item.cc:24: > /usr/include/apt-pkg/deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has > not been declared >48 |bool ParseDepends(pkgCache::VerIterator &Ver, pkgTagSection::Key > Key, > | ^~~ > error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 > E: pybuild pybuild:369: build: plugin distutils failed with: exit code=1: > /usr/bin/python3.9 setup.py build > I: pybuild base:239: /usr/bin/python3 setup.py build > running build > running build_py > creating /<>/.pybuild/cpython3_3.10_apt/build/apt > copying apt/__init__.py -> > /<>/.pybuild/cpython3_3.10_apt/build/apt > copying apt/package.py -> > /<>/.pybuild/cpython3_3.10_apt/build/apt > copying apt/cdrom.py -> /<>/.pybuild/cpython3_3.10_apt/build/apt > copying apt/debfile.py -> > /<>/.pybuild/cpython3_3.10_apt/build/apt > copying apt/auth.py -> /<>/.pybuild/cpython3_3.10_apt/build/apt > copying apt/cache.py -> /<>/.pybuild/cpython3_3.10_apt/build/apt > copying apt/utils.py -> /<>/.pybuild/cpython3_3.10_apt/build/apt > creating /<>/.pybuild/cpython3_3.10_apt/build/apt/progress > copying apt/progress/__init__.py -> > /<>/.pybuild/cpython3_3.10_apt/build/apt/progress > copying apt/progress/base.py -> > /<>/.pybuild/cpython3_3.10_apt/build/apt/progress > copying apt/progress/text.py -> > /<>/.pybuild/cpython3_3.10_apt/build/apt/progress > creating /<>/.pybuild/cpython3_3.10_apt/build/aptsources > copying aptsources/__init__.py -> > /<>/.pybuild/cpython3_3.10_apt/build/aptsources > copying aptsources/distinfo.py -> > /<>/.pybuild/cpython3_3.10_apt/build/aptsources > copying aptsources/distro.py -> > /<>/.pybuild/cpython3_3.10_apt/build/aptsources > copying aptsources/sourceslist.py -> > /<>/.pybuild/cpython3_3.10_apt/build/aptsources > copying apt/py.typed -> /<>/.pybuild/cpython3_3.10_apt/build/apt > running build_ext > building 'apt_pkg' extension > creating build/temp.linux-x86_64-3.10 > creating build/temp.linux-x86_64-3.10/python > x86_64-linux-gnu-gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g > -fwrapv -O2 -Wall -g -fstack-protector-strong -Wformat > -Werror=format-security -g -fwrapv -O2 -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wno-write-strings -DDATE="Oct 22 2021" > -DTIME="10:21:54" -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > -I/usr/include/python3.10 -c python/acquire-item.cc -o > build/temp.linux-x86_64-3.10/python/acquire-item.o -std=c++11 > -Wno-write-strings -DAPT_8_CLEANER_HEADERS -DAPT_9_CLEANER_HEADERS > -DAPT_10_CLEANER_HEADERS -DPY_SSIZE_T_CLEAN > In file included from python/apt_pkgmodule.h:19, > from python/acquire-item.cc:24: > /usr/include/apt-pkg/deblistparser.h:48:65: error: ‘pkgTagSection::Key’ has > not been declared >48 |bool ParseDepends(pkgCache::VerIterator &Ver, pkgTagSection::Key > Key, > | ^~~ > error: command '/usr/bin/x86_64-linux-gnu-gcc' failed with exit code 1 > E: pybuild pybuild:369: build: plugin distutils failed with: exit code=1: > /usr/bin/py
Bug#1012900: marked as done (bctoolbox: ftbfs with GCC-12)
Your message dated Sun, 24 Jul 2022 16:04:07 +
with message-id
and subject line Bug#1012900: fixed in bctoolbox 5.0.37-2
has caused the Debian Bug report #1012900,
regarding bctoolbox: ftbfs with GCC-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.)
--
1012900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012900
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:bctoolbox
Version: 4.4.13-3
Severity: normal
Tags: sid bookworm
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-12
[This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The
severity of this report will be raised before the bookworm release.
The full build log can be found at:
http://qa-logs.debian.net/2022/06/09/gcc12/bctoolbox_4.4.13-3_unstable_gcc12.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/mbedtls/sha256.h:276:25: note: declared here
276 | MBEDTLS_DEPRECATED void mbedtls_sha256( const unsigned char *input,
| ^~
/<>/src/crypto/mbedtls.c:470:25: warning: ‘mbedtls_sha512’ is
deprecated [-Wdeprecated-declarations]
470 | mbedtls_sha512(crt->raw.p, crt->raw.len,
buffer, 1); /* last argument is a boolean, indicate to output sha-384 and not
sha-512 */
| ^~
In file included from /usr/include/mbedtls/entropy.h:34,
from /<>/src/crypto/mbedtls.c:34:
/usr/include/mbedtls/sha512.h:293:25: note: declared here
293 | MBEDTLS_DEPRECATED void mbedtls_sha512( const unsigned char *input,
| ^~
/<>/src/crypto/mbedtls.c:476:25: warning: ‘mbedtls_sha512’ is
deprecated [-Wdeprecated-declarations]
476 | mbedtls_sha512(crt->raw.p, crt->raw.len,
buffer, 0); /* last argument is a boolean, indicate to output sha-384 and not
sha-512 */
| ^~
/usr/include/mbedtls/sha512.h:293:25: note: declared here
293 | MBEDTLS_DEPRECATED void mbedtls_sha512( const unsigned char *input,
| ^~
/<>/src/crypto/mbedtls.c: In function ‘bctbx_CreateDHMContext’:
/<>/src/crypto/mbedtls.c:736:25: warning:
‘mbedtls_deprecated_string_constant_t’ is deprecated [-Wdeprecated-declarations]
736 | if
((mbedtls_mpi_read_string(&(mbedtlsDhmContext->P), 16,
MBEDTLS_DHM_RFC3526_MODP_2048_P) != 0) ||
| ^~
/<>/src/crypto/mbedtls.c:737:25: warning:
‘mbedtls_deprecated_string_constant_t’ is deprecated [-Wdeprecated-declarations]
737 |
(mbedtls_mpi_read_string(&(mbedtlsDhmContext->G), 16,
MBEDTLS_DHM_RFC3526_MODP_2048_G) != 0)) {
| ^
/<>/src/crypto/mbedtls.c:745:25: warning:
‘mbedtls_deprecated_string_constant_t’ is deprecated [-Wdeprecated-declarations]
745 | if
((mbedtls_mpi_read_string(&(mbedtlsDhmContext->P), 16,
MBEDTLS_DHM_RFC3526_MODP_3072_P) != 0) ||
| ^~
/<>/src/crypto/mbedtls.c:746:25: warning:
‘mbedtls_deprecated_string_constant_t’ is deprecated [-Wdeprecated-declarations]
746 |
(mbedtls_mpi_read_string(&(mbedtlsDhmContext->G), 16,
MBEDTLS_DHM_RFC3526_MODP_3072_G) != 0)) {
| ^
/<>/src/crypto/mbedtls.c: In function ‘bctbx_sha512’:
/<>/src/crypto/mbedtls.c:1489:9: warning: ‘mbedtls_sha512’ is
deprecated [-Wdeprecated-declarations]
Bug#914935: marked as done (enca: reproducible build (usrmerge): Embeds full path to mktemp found via PATH)
Your message dated Sun, 24 Jul 2022 15:33:56 +
with message-id
and subject line Bug#914935: fixed in enca 1.19-1.1
has caused the Debian Bug report #914935,
regarding enca: reproducible build (usrmerge): Embeds full path to mktemp found
via PATH
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.)
--
914935: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914935
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: enca
Version: 1.19-1
Severity: normal
Tags: patch
User: m...@linux.it
Usertags: usrmerge
Dear Maintainer,
The reproducible build spotted a difference in your package when
built on a usrmerged system vs a non-merged system:
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/enca.html
It seems a few files contains the full path of 'mktemp' found via
AC_PROG_PATH during build.
Since PATH defaults to contain /usr/bin before /bin the found path will
be /usr/bin/mktemp on a usrmerged system, since both paths are
essentially the same thing there. This is however not desirable on
a non-merged system where it needs to be /bin/mktemp.
The attached patch fixes the problem by explicitly specifying
the default path via MKTEMP_PROG environment variable as documented
in AC_PROG_PATH documentation.
(This is likely a good idea either way, since otherwise hypothetical
problems could happen for users building on their system with
/usr/local/bin/... or ~/bin/)
Regards,
Andreas Henriksson
diff -Nru enca-1.19/debian/changelog enca-1.19/debian/changelog
--- enca-1.19/debian/changelog 2016-09-05 16:23:32.0 +0200
+++ enca-1.19/debian/changelog 2018-11-28 21:59:20.0 +0100
@@ -1,3 +1,11 @@
+enca (1.19-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Pass MKTEMP_PROG=/bin/mktemp to configure instead of finding in PATH
+- this fixes reproducible build issue on merged-usr vs non-merged.
+
+ -- Andreas Henriksson Wed, 28 Nov 2018 21:59:20 +0100
+
enca (1.19-1) unstable; urgency=medium
* New upstream release.
diff -Nru enca-1.19/debian/rules enca-1.19/debian/rules
--- enca-1.19/debian/rules 2016-01-07 09:27:18.0 +0100
+++ enca-1.19/debian/rules 2018-11-28 21:59:15.0 +0100
@@ -5,7 +5,8 @@
--libexecdir=\$${prefix}/lib \
--with-librecode \
--with-libiconv \
- --disable-rpath
+ --disable-rpath \
+ MKTEMP_PROG=/bin/mktemp
override_dh_strip:
dh_strip --dbg-package=libenca-dbg
--- End Message ---
--- Begin Message ---
Source: enca
Source-Version: 1.19-1.1
Done: Ansgar
We believe that the bug you reported is fixed in the latest version of
enca, 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 914...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ansgar (supplier of updated enca 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 Jul 2022 16:35:46 +0200
Source: enca
Architecture: source
Version: 1.19-1.1
Distribution: unstable
Urgency: medium
Maintainer: Michal Čihař
Changed-By: Ansgar
Closes: 914935
Changes:
enca (1.19-1.1) unstable; urgency=medium
.
* Non-maintainer upload.
.
[ Andreas Henriksson ]
* Pass MKTEMP_PROG=/bin/mktemp to configure instead of finding in PATH
- this fixes reproducible build issue on merged-usr vs non-merged.
(Closes: #914935)
Checksums-Sha1:
85cc1e90d6157a08e36943c6c4d11204fe37735d 1445 enca_1.19-1.1.dsc
8393942b140fb2950359d7d1f80564efa5d32a3b 4420 enca_1.19-1.1.debian.tar.xz
Checksums-Sha256:
ff50212467871662f78a44a2dfbd8ac890b60ad79c4325c42cab407bd8a50066 1445
enca_1.19-1.1.dsc
d27857b32e36513664dd23ebc626cc8dd2013b4b3588c4abe7304b89db390fa6 4420
enca_1.19-1.1.debian.tar.xz
Files:
ee86d1fb06c1a3954c2d3bd5e09c9e4d 1445 text optional enca_1.19-1.1.dsc
a67e7ab90b2c0a80f563ed86791e8135 4420 text optional enca_1.19-1.1.debian.tar.xz
-BEGIN PGP SIGNATURE-
iIgEARYKADAWIQR3hZU8YXPYylUJRxfDof4h+X+qzwUCYtQe2BIcYW5zZ2FyQGRl
Ymlhbi5vcmcACgkQw6H+Ifl/qs9xuQD/cmQinwQ0jbT+jvcv6vY/VgGzj55I8fKO
PI102J6Cqn8A/3z+6fIPn+vQItGGnkC3ZtwIo7P2hWUT4BxJVjvQWvAH
=dDlH
-END
Bug#1012934: marked as done (gatb-core: ftbfs with GCC-12)
Your message dated Sun, 24 Jul 2022 15:34:16 + with message-id and subject line Bug#1012934: fixed in gatb-core 1.4.2+dfsg-9 has caused the Debian Bug report #1012934, regarding gatb-core: ftbfs with GCC-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.) -- 1012934: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012934 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:gatb-core Version: 1.4.2+dfsg-8 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/gatb-core_1.4.2+dfsg-8_unstable_gcc12.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. [...] +#MISSING: 1.4.2+dfsg-8# _ZTSSt23_Sp_counted_ptr_inplaceIPKN4gatb4core5tools4math8LargeIntILi3EEESaIS7_ELN9__gnu_cxx12_Lock_policyE2EE@Base 1.4.2 + _ZTSSt23_Sp_counted_ptr_inplaceIPKN4gatb4core5tools4math8LargeIntILi3EEESaIvELN9__gnu_cxx12_Lock_policyE2EE@Base 1.4.2+dfsg-8 +#MISSING: 1.4.2+dfsg-8# _ZTSSt23_Sp_counted_ptr_inplaceIPKN4gatb4core5tools4math8LargeIntILi4EEESaIS7_ELN9__gnu_cxx12_Lock_policyE2EE@Base 1.4.2 + _ZTSSt23_Sp_counted_ptr_inplaceIPKN4gatb4core5tools4math8LargeIntILi4EEESaIvELN9__gnu_cxx12_Lock_policyE2EE@Base 1.4.2+dfsg-8 +#MISSING: 1.4.2+dfsg-8# _ZTSSt23_Sp_counted_ptr_inplaceIPKmSaIS1_ELN9__gnu_cxx12_Lock_policyE2EE@Base 1.4.2 + _ZTSSt23_Sp_counted_ptr_inplaceIPKmSaIvELN9__gnu_cxx12_Lock_policyE2EE@Base 1.4.2+dfsg-8 +#MISSING: 1.4.2+dfsg-8# _ZTSSt23_Sp_counted_ptr_inplaceISt13packaged_taskIFviEESaIS2_ELN9__gnu_cxx12_Lock_policyE2EE@Base 1.4.2 + _ZTSSt23_Sp_counted_ptr_inplaceISt13packaged_taskIFviEESaIvELN9__gnu_cxx12_Lock_policyE2EE@Base 1.4.2+dfsg-8 _ZTSZN10ThreadPool7enqueueIRZN4gatb4core8debruijn4impl10prepare_ufILi128EEEvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPNS2_4bank5IBankEiRiiiRmmEUliE_JEEESt6futureINSt9result_ofIFT_iDpT0_EE4typeEEOSL_DpOSM_EUliE_@Base 1.4.2 _ZTSZN10ThreadPool7enqueueIRZN4gatb4core8debruijn4impl10prepare_ufILi32EEEvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPNS2_4bank5IBankEiRiiiRmmEUliE_JEEESt6futureINSt9result_ofIFT_iDpT0_EE4typeEEOSL_DpOSM_EUliE_@Base 1.4.2 _ZTSZN10ThreadPool7enqueueIRZN4gatb4core8debruijn4impl10prepare_ufILi64EEEvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPNS2_4bank5IBankEiRiiiRmmEUliE_JEEESt6futureINSt9result_ofIFT_iDpT0_EE4typeEEOSL_DpOSM_EUliE_@Base 1.4.2 @@ -13345,11 +13484,16 @@ _ZTVNSt13__future_base16_Task_state_baseIFviEEE@Base 1.4.2 _ZTVNSt13__future_base7_ResultIvEE@Base 1.4.2 _ZTVNSt6thread11_State_implINS_8_InvokerISt5tupleIJZN10ThreadPoolC4EmEUlvE_EE@Base 1.4.2 - _ZTVSt23_Sp_counted_ptr_inplaceIN4gatb4core5tools11collections4impl6BooPHFINS2_4math8LargeIntILi1EEENS4_16AdaptatorDefaultIS8_EENS2_4misc4impl12ProgressNoneEE18iterator_adaptatorESaISF_ELN9__gnu_cxx12_Lock_policyE2EE@Base 1.4.2 - _ZTVSt23_Sp_counted_ptr_inplaceIN4gatb4core5tools11collections4impl6BooPHFINS2_4math8LargeIntILi2EEENS4_16AdaptatorDefaultIS8_EENS2_4misc4impl12ProgressNoneEE18iterator_adaptatorESaISF_ELN9__gnu_cxx12_Lock_policyE2EE@Base 1.4.2 - _ZTVSt23_Sp_counted_ptr_inplaceIN4gatb4core5tools11collections4impl6BooPHFINS2_4math8LargeIntILi3EEENS4_16AdaptatorDefaultIS8_EENS2_4misc4impl12ProgressNoneEE18iterator_adaptatorESaISF_ELN9__gnu_cxx12_Lock_policyE2EE@Base 1.4.2 - _ZTV
Bug#1015923: marked as done (Unnecessary package splits)
Your message dated Sun, 24 Jul 2022 15:34:06 + with message-id and subject line Bug#1015923: fixed in fcitx5-configtool 5.0.14-4 has caused the Debian Bug report #1015923, regarding Unnecessary package splits 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.) -- 1015923: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015923 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fcitx5-configtool Version: 5.0.14-2 Severity: serious X-Debbugs-Cc: z...@debian.org The package splits too fragmentarily. There's already kde-config-fcitx5, fcitx5-plasma-theme-generator should be there. As for the po files, upstream already confirms it will be in org.fcitx.fcitx5.kcm. --- End Message --- --- Begin Message --- Source: fcitx5-configtool Source-Version: 5.0.14-4 Done: Boyuan Yang We believe that the bug you reported is fixed in the latest version of fcitx5-configtool, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Boyuan Yang (supplier of updated fcitx5-configtool 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, 24 Jul 2022 11:02:44 -0400 Source: fcitx5-configtool Architecture: source Version: 5.0.14-4 Distribution: unstable Urgency: medium Maintainer: Debian Input Method Team Changed-By: Boyuan Yang Closes: 1015923 Changes: fcitx5-configtool (5.0.14-4) unstable; urgency=medium . * Undo package split (Closes: #1015923) + Install fcitx5-plasma-theme-generator into kde-config-fcitx5. + Install fcitx5-configtool translation files into fcitx5-config-qt. + Still let fcitx5-config-qt provides fcitx5-configtool. + No longer mark kde-config-fcitx5 as Multi-Arch: same. + Properly add Breaks+Provides relationship. Checksums-Sha1: 67f55cbb95da7e2b7ab729730d9f41928b695712 2822 fcitx5-configtool_5.0.14-4.dsc 40d9ce3229343b64dae9a786000920d2d1a99813 112716 fcitx5-configtool_5.0.14.orig.tar.xz 7c01d40355eb1080d821509dae833345075b36fb 488 fcitx5-configtool_5.0.14.orig.tar.xz.asc 4253f77e4ade6cfcb4183e317d5a4fbab2979d11 6672 fcitx5-configtool_5.0.14-4.debian.tar.xz ecb970b198509b4e4a99029029af6f52a110f564 18914 fcitx5-configtool_5.0.14-4_amd64.buildinfo Checksums-Sha256: 2f65a641479ddeffcde2f254ea1f366b7a3a6081e7b3054162c86d22897f30d6 2822 fcitx5-configtool_5.0.14-4.dsc 2f16c6a100c890496c8757a220a84fe2b9fd0df2e99e0ba4fb65d20700f76e88 112716 fcitx5-configtool_5.0.14.orig.tar.xz 55b9346b732905da63eaf0825f7cbb0c7fdb437b812e474f4bfc5452d84b5f63 488 fcitx5-configtool_5.0.14.orig.tar.xz.asc 07c6fbb0ad35ee1570d174ccb9611f434855c7000422920bd9da0704fe0801a6 6672 fcitx5-configtool_5.0.14-4.debian.tar.xz 7b1224450de17d9fd952146dd21074267e7a85acd841016cbeae7fc53fe5f7c2 18914 fcitx5-configtool_5.0.14-4_amd64.buildinfo Files: 932028483257ca1296508b55b71263a0 2822 kde optional fcitx5-configtool_5.0.14-4.dsc d6da1a07c057f967c0a0fcedad7a1fc5 112716 kde optional fcitx5-configtool_5.0.14.orig.tar.xz 1594ce7b5ed630804f20323843cb1e28 488 kde optional fcitx5-configtool_5.0.14.orig.tar.xz.asc 649c735bff833c9e624f4cc662fded0d 6672 kde optional fcitx5-configtool_5.0.14-4.debian.tar.xz bed8b2dd1140612d2f1823b8579c36f2 18914 kde optional fcitx5-configtool_5.0.14-4_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmLdYFYACgkQwpPntGGC Ws5D1hAApDL7qkUW38hBrpM4aV5ahNPfDumo7KdOWZAV+ugNbgC4D+GDroNgmNMh W8ZvX81W9Ik3Ztl/P3eVb/cM+qX1kKOTuh2LPOTyb9UbUEgBcxKJkUuZaUkIo3AV JUjVnuewaD4rr96mh1iKpQF6jp5IaupRP2g5YhfxofqINQ3Ok+I1rRdyR28GHivR w8vQG/uz3+6dwb5miw2m7jrHiLti8ORyKyFjgFzwzO3nnhYiIo2LDMmWs/U+StLW /4Y+AwF6DJijUX8DSXQuRtFbOVCbgumUxqvLU3qi1c1elL2PfCdvlGAVxCVNj8Ko UqiHJCZ7SNTFlCa9X5K1T1WY0+QOidtJJglRu4z/UBGNUEnWTAcbgju+EmDszgUc pDOL/epxhriEh9/wgBn8knD+e6EaKKm47jvxel3FrFu8csydlf3TtGh5pU2XR5Hi s5sMl309wutjwpDxTVIJpUNHmcg8qkcv5Ey3kzI+NzFw6pk71dz5D46lQdyNnhsj KLJCB7kQWl5be7VSa8beQRUl6YKbQDXPgq6enw35Sw/9Byy872HxogHYdgXIHCnv 3EjxAS0HMxyc2BiCW3KXT2Y7KstQrFkrnoLyE3ulNmefbIgQTM4yaHoVFrg4Jt6x t+4RFKmTR61PuBiNe8VHrO8fhF5LHMU0CIGuNlE9gk5hceOD8UY= =ETBy -END PGP SIGNATURE End Message ---
Bug#1009474: marked as done (micropython: FTBFS: dh_auto_test: error: cd ports/unix && make -j8 test STRIP=true MICROPY_PY_BTREE=0 MICROPY_SSL_AXTLS=0 MICROPY_SSL_MBEDTLS=1 MICROPY_PY_JNI=1 "TESTS_ARG
Your message dated Sun, 24 Jul 2022 15:12:41 + with message-id and subject line Bug#1007090: fixed in micropython 1.19.1+ds-1 has caused the Debian Bug report #1007090, regarding micropython: FTBFS: dh_auto_test: error: cd ports/unix && make -j8 test STRIP=true MICROPY_PY_BTREE=0 MICROPY_SSL_AXTLS=0 MICROPY_SSL_MBEDTLS=1 MICROPY_PY_JNI=1 "TESTS_ARGS=-e '(?:ussl_basic|urandom_basic|import_pkg7)'" returned exit code 2 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.) -- 1007090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: micropython Version: 1.17+ds-1.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220412 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/ports/unix' > ../../debian/config/makedebversionhdr build-standard/genhdr/mpversion.h > ../../debian/changelog > GEN build-standard/genhdr/mpversion.h > python3 ../../tools/makemanifest.py -o build-standard/frozen_content.c -v > "MPY_DIR=../.." -v "MPY_LIB_DIR=../../../micropython-lib" -v > "PORT_DIR=/<>/ports/unix" -v "BOARD_DIR=" -b "build-standard" > -f"-mcache-lookup-bc" --mpy-tool-flags="" variants/manifest.py > CC main.c > gcc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wno-error=maybe-uninitialized -I. -I../.. > -Ibuild-standard -I../../shared/readline -Wall -Werror -Wextra > -Wno-unused-parameter -Wpointer-arith -Wdouble-promotion -Wfloat-conversion > -std=gnu99 -DUNIX -DFFCONF_H=\"lib/oofatfs/ffconf.h\" -DMICROPY_PY_USSL=1 > -DMICROPY_SSL_MBEDTLS=1 -DMICROPY_USE_READLINE=1 -DMICROPY_PY_TERMIOS=1 > -DMICROPY_PY_SOCKET=1 -DMICROPY_PY_THREAD=1 -DMICROPY_PY_THREAD_GIL=0 > -DMICROPY_PY_FFI=1 -I/usr/lib/jvm/default-java/include > -I/usr/lib/jvm/default-java/include/linux -DMICROPY_PY_JNI=1 -Os -DNDEBUG > -fdata-sections -ffunction-sections -Ivariants/standard -Wdate-time > -D_FORTIFY_SOURCE=2 -g -O2 -ffile-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security > -Wno-error=maybe-uninitialized -g -U _FORTIFY_SOURCE > -DMICROPY_QSTR_EXTRA_POOL=mp_qstr_frozen_const_pool > -DMICROPY_MODULE_FROZEN_MPY -DMPZ_DIG_SIZE=16 -DMICROPY_MODULE_FROZEN_STR -c > -MD -o build-standard/main.o main.c > LINK micropython > gcc -o micropython build-standard/py/mpstate.o build-standard/py/nlr.o > build-standard/py/nlrx86.o build-standard/py/nlrx64.o > build-standard/py/nlrthumb.o build-standard/py/nlraarch64.o > build-standard/py/nlrpowerpc.o build-standard/py/nlrxtensa.o > build-standard/py/nlrsetjmp.o build-standard/py/malloc.o > build-standard/py/gc.o build-standard/py/pystack.o build-standard/py/qstr.o > build-standard/py/vstr.o build-standard/py/mpprint.o > build-standard/py/unicode.o build-standard/py/mpz.o > build-standard/py/reader.o build-standard/py/lexer.o > build-standard/py/parse.o build-standard/py/scope.o > build-standard/py/compile.o build-standard/py/emitcommon.o > build-standard/py/emitbc.o build-standard/py/asmbase.o > build-standard/py/asmx64.o build-standard/py/emitnx64.o > build-standard/py/asmx86.o build-standard/py/emitnx86.o > build-standard/py/asmthumb.o build-standard/py/emitnthumb.o > build-standard/py/emitinlinethumb.o build-standard/py/asmarm.o > build-standard/py/emitnarm.o build-standard/py/asmxtensa.o > build-standard/py/emitnxtensa.o build-standard/py/emitinlinextensa.o > build-standard/py/emitnxtensawin.o build-standard/py/formatfloat.o > build-standard/py/parsenumbase.o build-standard/py/parsenum.o > build-standard/py/emitglue.o build-standard/py/persistentcode.o > build-standard/py/runtime.o build-standard/py/runtime_utils.o > build-standard/py/scheduler.o build-standard/py/nativeglue.o > build-standard/py/pairheap.o build-standard/py/ringbuf.o > build-standard/py/stackctrl.o build-standard/py/argcheck.o > build-standard/py/warning.o build-standard/py/profile.o > build-standard/py/map.o build-standard/py/obj.o build-standard/py/objarray.o > build-standard/py/objattrtuple.o build-standard/py/objbool.o > build-standard/py/objboundmeth.o build-standard/py/objcell.o > build-standard/py/objclosure.o build-standard/py/objcomplex.o > build-standard/py/objdeque.o build-standard/py/objdict.o > build-standard/py/objenumerate.o build-standard/py/objexcept.o > build-standard/py/objfilter.o build-standard/py/objfloat.o > build-standard/py/objfun.o build-standard/py/obj
Bug#1007090: marked as done (micropython: fails tests if python3 is python3.10)
Your message dated Sun, 24 Jul 2022 15:12:41 + with message-id and subject line Bug#1007090: fixed in micropython 1.19.1+ds-1 has caused the Debian Bug report #1007090, regarding micropython: fails tests if python3 is python3.10 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.) -- 1007090: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007090 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: micropython Version: 1.17+ds-1.1 Severity: normal Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu jammy ubuntu-patch Dear maintainer, In Ubuntu, micropython is failing to build from source because of an additional test failure. The cause of the failure is that the reference output has changed between python3.9 and python3.10. Since this doesn't make micropython incorrect, I have uploaded the attached change to Ubuntu to skip this particular test. You may wish to consider applying this or a similar change in Debian, since python3.10 will become the default there soon. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org diff -Nru micropython-1.17+ds/debian/rules micropython-1.17+ds/debian/rules --- micropython-1.17+ds/debian/rules2021-11-10 12:51:19.0 -0800 +++ micropython-1.17+ds/debian/rules2022-03-10 13:40:29.0 -0800 @@ -21,7 +21,7 @@ endif # https://github.com/micropython/micropython/issues/6750 -SKIP_TESTS := ussl_basic urandom_basic import_pkg7 +SKIP_TESTS := ussl_basic urandom_basic import_pkg7 string_format_error ifneq ($(DEB_HOST_ARCH),amd64) SKIP_TESTS += mpy_native endif --- End Message --- --- Begin Message --- Source: micropython Source-Version: 1.19.1+ds-1 Done: Yangfl We believe that the bug you reported is fixed in the latest version of micropython, 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 1007...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yangfl (supplier of updated micropython 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, 23 Jul 2022 12:35:20 +0800 Source: micropython Architecture: source Version: 1.19.1+ds-1 Distribution: unstable Urgency: medium Maintainer: Yangfl Changed-By: Yangfl Closes: 1007090 Changes: micropython (1.19.1+ds-1) unstable; urgency=medium . * New upstream release * Fix test fails with Python 3.10 (Closes: #1007090) * Bump Standards-Version to 4.6.1 Checksums-Sha1: e0a5d3a8024c03bcaef4ae789fff6d170f487179 2144 micropython_1.19.1+ds-1.dsc d644376c9621423a115d146233a51c58a17d4bc5 5466816 micropython_1.19.1+ds.orig.tar.xz 5391910871f71ff6d191b3fa9bae6c0bcfbbfcac 14688 micropython_1.19.1+ds-1.debian.tar.xz 57df3bf6a5dbe09406f0a42d332894773c710272 9317 micropython_1.19.1+ds-1_amd64.buildinfo Checksums-Sha256: 84ab1a87ff455fb8b752e1bcdd1840dd857982a89ebbc1ab6d9d04face7f84cd 2144 micropython_1.19.1+ds-1.dsc 8866e43f376efc0c6cc425dd7e4e7a1d0f43ed2d169c70c3ca4a8a5aebc35620 5466816 micropython_1.19.1+ds.orig.tar.xz 0e39db491aa3d573124d324d966e86646f8d18193504853b3a16bed5e9cebce6 14688 micropython_1.19.1+ds-1.debian.tar.xz ea90e957cd32d3ce7afa5d95a40c312cd4de1f2beb193496683d7b2335c72d98 9317 micropython_1.19.1+ds-1_amd64.buildinfo Files: d01cdac28164b029dee9d6823d79a728 2144 python optional micropython_1.19.1+ds-1.dsc b415b52478f0d013e1b595574ad28692 5466816 python optional micropython_1.19.1+ds.orig.tar.xz 6aeae452f733df3729d20d822bcd6691 14688 python optional micropython_1.19.1+ds-1.debian.tar.xz e494df58a20f22ee547844c618801d91 9317 python optional micropython_1.19.1+ds-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmLdWiEACgkQwpPntGGC Ws6+nA//aEiWFSJqdwxe9JSXtAMkMCcXyGoysNmlgdTcGr/wQIoUrmwwS9NpsG2y PfLwwbLHWa5YnbzOxLATZmm72zMJ9FQdIC5fcKp+u/n+cdcytHu452+7wjqAV4Z5 bJKPtC12XSWlieB3m7EC7Bpwgq4r40gTMctC2vT6Im87zC1v5ioswQC5k3kcIS7T E+bzVTx2bWYm1r/B6
Bug#1012972: marked as done (libbpp-seq-omics: ftbfs with GCC-12)
Your message dated Sun, 24 Jul 2022 15:07:36 + with message-id and subject line Bug#1012972: fixed in libbpp-seq-omics 2.4.1-8 has caused the Debian Bug report #1012972, regarding libbpp-seq-omics: ftbfs with GCC-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.) -- 1012972: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012972 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-seq-omics Version: 2.4.1-7 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/libbpp-seq-omics_2.4.1-7_unstable_gcc12.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. [...] +#MISSING: 2.4.1-7# _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N3bpp8RangeSetImEEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp10BppNumberIEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp10BppNumberIEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp10BppNumberIEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE4findERS7_@Base 2.4.1 - _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp10BppNumberIEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 2.4.1 - _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp18SequenceFeatureSetEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 2.4.1 +#MISSING: 2.4.1-7# _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp10BppNumberIEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 2.4.1 +#MISSING: 2.4.1-7# _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp18SequenceFeatureSetEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8ClonableEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8ClonableEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS7_@Base 2.4.1 - _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8ClonableEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 2.4.1 +#MISSING: 2.4.1-7# _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8ClonableEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8
Bug#1012971: marked as done (libbpp-seq: ftbfs with GCC-12)
Your message dated Sun, 24 Jul 2022 14:39:26 + with message-id and subject line Bug#1012971: fixed in libbpp-seq 2.4.1-8 has caused the Debian Bug report #1012971, regarding libbpp-seq: ftbfs with GCC-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.) -- 1012971: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012971 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-seq Version: 2.4.1-7 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/libbpp-seq_2.4.1-7_unstable_gcc12.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. [...] - (optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE17_M_emplace_uniqueIJS6_IS5_SA_S6_ISt17_Rb_tree_iteratorISB_EbEDpOT_@Base 2.4.1 +#MISSING: 2.4.1-7# (optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE17_M_emplace_uniqueIJS6_IS5_SA_S6_ISt17_Rb_tree_iteratorISB_EbEDpOT_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE4findERS7_@Base 2.4.1 - _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 2.4.1 +#MISSING: 2.4.1-7# _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8SequenceEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE8_M_eraseEPSt13_Rb_tree_nodeISB_E@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE4findERS7_@Base 2.4.1 - _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base 2.4.1 +#MISSING: 2.4.1-7# _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_St4fposI11__mbstate_tEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_St4fposI11__mbstate_tEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE29_M_get_in
Bug#1012970: marked as done (libbpp-qt: ftbfs with GCC-12)
Your message dated Sun, 24 Jul 2022 14:39:20 + with message-id and subject line Bug#1012970: fixed in libbpp-qt 2.4.1-7 has caused the Debian Bug report #1012970, regarding libbpp-qt: ftbfs with GCC-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.) -- 1012970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012970 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-qt Version: 2.4.1-6 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/libbpp-qt_2.4.1-6_unstable_gcc12.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. [...] dh_missing dh_dwz -a dh_strip -a dh_makeshlibs -a dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libbpp-qt2/DEBIAN/symbols doesn't match completely debian/libbpp-qt2.symbols.amd64 --- debian/libbpp-qt2.symbols.amd64 (libbpp-qt2_2.4.1-6_amd64) +++ dpkg-gensymbolsMhkX30 2022-06-10 09:04:17.823083234 + @@ -184,7 +184,7 @@ _ZN3bpp21AbstractGraphicDevice25setCurrentForegroundColorERKNS_8RGBColorE@Base 2.4.1 _ZN3bpp21AbstractGraphicDevice8setXUnitEd@Base 2.4.1 _ZN3bpp21AbstractGraphicDevice8setYUnitEd@Base 2.4.1 - _ZN3bpp21AbstractGraphicDeviceC2Ev@Base 2.4.1 +#MISSING: 2.4.1-6# _ZN3bpp21AbstractGraphicDeviceC2Ev@Base 2.4.1 _ZN3bpp21AbstractGraphicDeviceD2Ev@Base 2.4.1 _ZN3bpp21NodeNotFoundExceptionD0Ev@Base 2.4.1 _ZN3bpp21NodeNotFoundExceptionD1Ev@Base 2.4.1 @@ -373,6 +373,7 @@ _ZNK3bpp7Point2DIdEeqERKS1_@Base 2.4.1 _ZNK3bpp7Point2DIdEneERKS1_@Base 2.4.1 _ZNK3bpp8RGBColor5cloneEv@Base 2.4.1 + _ZNKSt5ctypeIcE8do_widenEc@Base 2.4.1-6 _ZNSt10unique_ptrI14QGraphicsSceneSt14default_deleteIS0_EED1Ev@Base 2.4.1 _ZNSt10unique_ptrI14QGraphicsSceneSt14default_deleteIS0_EED2Ev@Base 2.4.1 _ZNSt10unique_ptrIN3bpp14NodeMouseEventESt14default_deleteIS1_EED1Ev@Base 2.4.1 @@ -396,7 +397,7 @@ _ZNSt6vectorIPN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS4_EE17_M_realloc_insertIJS4_EEEvN9__gnu_cxx17__normal_iteratorIPS4_S6_EEDpOT_@Base 2.4.1 _ZNSt6vectorIPN3bpp4NodeESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 2.4.1 _ZNSt6vectorIPN3bpp4NodeESaIS2_EE17_M_realloc_insertIJS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 2.4.1 - _ZNSt6vectorIPN3bpp4NodeESaIS2_EE8_M_eraseEN9__gnu_cxx17__normal_iteratorIPS2_S4_EE@Base 2.4.1 +#MISSING: 2.4.1-6# _ZNSt6vectorIPN3bpp4NodeESaIS2_EE8_M_eraseEN9__gnu_cxx17__normal_iteratorIPS2_S4_EE@Base 2.4.1 _ZNSt6vectorIdSaIdEE17_M_realloc_insertIJRKdEEEvN9__gnu_cxx17__normal_iteratorIPdS1_EEDpOT_@Base 2.4.1 _ZNSt6vectorIiSaIiEE17_M_realloc_insertIJiEEEvN9__gnu_cxx17__normal_iteratorIPiS1_EEDpOT_@Base 2.4.1 _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC1IS3_EEPKcRKS3_@Base 2.4.1 @@ -410,15 +411,17 @@ _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8ClonableEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE24_M_get_insert_unique_posERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8ClonableEESt10_Select1stIS
Bug#1015958: haskell-http-client FTBFS on IPV6-only buildds
Source: haskell-http-client
Version: 0.7.11-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/fetch.php?pkg=haskell-http-client&arch=i386&ver=0.7.11-1&stamp=1658667307&raw=0
...
Failures:
test-nonet/Network/HTTP/ClientSpec.hs:241:18:
1) Network.HTTP.Client.Client withResponseHistory and redirect
uncaught exception: IOException of type InvalidArgument
threadWait: invalid argument (Bad file descriptor)
To rerun use: --match "/Network.HTTP.Client/Client/withResponseHistory and
redirect/"
Randomized with seed 1906044238
Finished in 2.0400 seconds
82 examples, 1 failure
Test suite spec-nonet: FAIL
Test suite logged to: dist-ghc/test/http-client-0.7.11-spec-nonet.log
1 of 2 test suites (1 of 2 test cases) passed.
at /usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 107.
Debian::Debhelper::Buildsystem::Haskell::Recipes::run_quiet("debian/hlibrary.setup",
"test", "--builddir=dist-ghc", "--show-details=direct") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 131
Debian::Debhelper::Buildsystem::Haskell::Recipes::run("debian/hlibrary.setup",
"test", "--builddir=dist-ghc", "--show-details=direct") called at
/usr/share/perl5/Debian/Debhelper/Buildsystem/Haskell/Recipes.pm line 678
Debian::Debhelper::Buildsystem::Haskell::Recipes::check_recipe() called
at -e line 1
make: *** [/usr/share/cdbs/1/class/hlibrary.mk:165: check-ghc-stamp] Error 25
Bug#1015085: texworks-manual: FTBFS: make[4]: *** [Makefile:66: index.ind] Error 1
Hi Hilmar, On 22/07/22 at 14:55 +0200, Hilmar Preuße wrote: > Am 21.07.2022 um 00:20 teilte Hilmar Preuße mit: > > Am 16.07.2022 um 15:56 teilte Lucas Nussbaum mit: > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build > > > on amd64. > > > > > For now there is an MWE, which compiles fine using LaTeX but can't be > > processed using htlatex (that's what we try to do). I'll try to contact > > TeX people soon: > > > > I got a heads up from "Michal Hoftich", so I'll start packaging next round > of texlive-base, -lang, -extra in the hope to solve the issue. > > https://tex.stackexchange.com/questions/651631/htlatex-fails-to-convert-file > > @Lucas: are there more packages affected using htlatex? No, only that one Lucas
Bug#1012903: marked as done (bladerf: ftbfs with GCC-12)
Your message dated Sun, 24 Jul 2022 12:20:08 + with message-id and subject line Bug#1012903: fixed in bladerf 0.2021.10-3 has caused the Debian Bug report #1012903, regarding bladerf: ftbfs with GCC-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.) -- 1012903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:bladerf Version: 0.2021.10-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/bladerf_0.2021.10-2_unstable_gcc12.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[3]: *** [CMakeFiles/Makefile2:1293: host/libraries/libbladeRF_test/test_repeater/CMakeFiles/libbladeRF_test_repeater.dir/all] Error 2 make[3]: *** Waiting for unfinished jobs [ 47%] Building C object host/libraries/libbladeRF_test/test_rx_discont/CMakeFiles/libbladeRF_test_rx_discont.dir/__/__/__/common/src/conversions.c.o cd /<>/obj-x86_64-linux-gnu/host/libraries/libbladeRF_test/test_rx_discont && /usr/bin/cc -DLOG_INCLUDE_FILE_INFO -I/<>/host/libraries/libbladeRF/include -I/<>/host/common/include -I/<>/obj-x86_64-linux-gnu/host/common/include -I/<>/host/common/thirdparty/ad936x/../../../../thirdparty/analogdevicesinc/no-OS_local/platform_bladerf2 -I/<>/obj-x86_64-linux-gnu/host/common/thirdparty/ad936x -I/<>/host/common/thirdparty/ad936x/../../../../host/libraries/libbladeRF/src -I/<>/host/common/thirdparty/ad936x/../../../../host/libraries/libbladeRF/include -I/<>/host/common/thirdparty/ad936x/../../../../host/common/include -I/<>/host/common/thirdparty/ad936x/../../../../firmware_common -I/<>/obj-x86_64-linux-gnu/host/common/thirdparty/ad936x/../../../host/common/include -I/<>/obj-x86_64-linux-gnu/host/common/thirdparty/ad936x/../../../common/i nclude -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -O2 -g -DNDEBUG -Wall -Wextra -Wno-unused-parameter -Werror -MD -MT host/libraries/libbladeRF_test/test_rx_discont/CMakeFiles/libbladeRF_test_rx_discont.dir/__/__/__/common/src/conversions.c.o -MF CMakeFiles/libbladeRF_test_rx_discont.dir/__/__/__/common/src/conversions.c.o.d -o CMakeFiles/libbladeRF_test_rx_discont.dir/__/__/__/common/src/conversions.c.o -c /<>/host/common/src/conversions.c [ 47%] Linking C executable ../../../output/libbladeRF_test_peripheral_timing cd /<>/obj-x86_64-linux-gnu/host/libraries/libbladeRF_test/test_peripheral_timing && /usr/bin/cmake -E cmake_link_script CMakeFiles/libbladeRF_test_peripheral_timing.dir/link.txt --verbose=1 [ 47%] Building C object host/libraries/libbladeRF_test/test_repeated_stream/CMakeFiles/libbladeRF_test_repeated_stream.dir/__/__/__/common/src/conversions.c.o cd /<>/obj-x86_64-linux-gnu/host/libraries/libbladeRF_test/test_repeated_stream && /usr/bin/cc -DLOG_INCLUDE_FILE_INFO -I/<>/host/libraries/libbladeRF/include -I/<>/host/common/include -I/<>/obj-x86_64-linux-gnu/host/common/include -I/<>/host/common/thirdparty/ad936x/../../../../thirdparty/analogdevicesinc/no-OS_local/platform_bladerf2 -I/<>/obj-x86_64-linux-gnu/host/common/thirdparty/ad936x -I/<>/host/common/thirdparty/ad936x/../../../../host/libraries/libbladeRF/src -I/<>/host/c
Processed: Re: [Pkg-utopia-maintainers] Bug#1015886: Bug: kodi-data conflicts firewalld on file kodi-eventserver.xml
Processing control commands:
> reopen -1
Bug #1015886 {Done: Michael Biebl } [firewalld] firewalld
conflicts kodi-data on file kodi-eventserver.xml
Bug reopened
Ignoring request to alter fixed versions of bug #1015886 to the same values
previously set
> severity -1 important
Bug #1015886 [firewalld] firewalld conflicts kodi-data on file
kodi-eventserver.xml
Severity set to 'important' from 'grave'
> clone -1 -2
Bug #1015886 [firewalld] firewalld conflicts kodi-data on file
kodi-eventserver.xml
Bug 1015886 cloned as bug 1015956
> reassign -2 kodi
Bug #1015956 [firewalld] firewalld conflicts kodi-data on file
kodi-eventserver.xml
Bug reassigned from package 'firewalld' to 'kodi'.
No longer marked as found in versions firewalld/1.1.1-1.
Ignoring request to alter fixed versions of bug #1015956 to the same values
previously set
> retitle -2 please ship firewalld service files
Bug #1015956 [kodi] firewalld conflicts kodi-data on file kodi-eventserver.xml
Changed Bug title to 'please ship firewalld service files' from 'firewalld
conflicts kodi-data on file kodi-eventserver.xml'.
> block -1 by -2
Bug #1015886 [firewalld] firewalld conflicts kodi-data on file
kodi-eventserver.xml
1015886 was not blocked by any bugs.
1015886 was not blocking any bugs.
Added blocking bug(s) of 1015886: 1015956
--
1015886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015886
1015956: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015956
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1015886: [Pkg-utopia-maintainers] Bug#1015886: Bug: kodi-data conflicts firewalld on file kodi-eventserver.xml
Control: reopen -1 Control: severity -1 important Control: clone -1 -2 Control: reassign -2 kodi Control: retitle -2 please ship firewalld service files Control: block -1 by -2 Am 24.07.22 um 08:12 schrieb Christian Marillat: > But why firewalld install services for packages not installed ? > > firewalld services must be managed as systemd does. firewalld uses a hybrid approach. As you can see, it provides a lot of service definitions in /usr/lib/firewalld/services out of the box. But individual packages can those ship service definitions as well. I think firewalld upstream actually prefers if those service definitions are shipped by the respective packages themselves. Am 24.07.22 um 08:57 schrieb Christian Marillat: On 24 juil. 2022 09:39, Andy wrote: I have come across a bug in the deb-multimedia package kodi-data. The debian maintainer of firewalld recommended to file a bug with debian- multimedia. firewalld will remove these files. https://github.com/firewalld/firewalld/pull/552 The official debian kodi package does not ship those files. Looking closer, I found https://salsa.debian.org/multimedia-team/kodi-media-center/kodi/-/blob/master/debian/not-installed#L1 debian/not-installed:# firewalld is present only on RHEL / CentOS debian/not-installed:usr/lib/firewalld/services/kodi-jsonrpc.xml debian/not-installed:usr/lib/firewalld/services/kodi-http.xml debian/not-installed:usr/lib/firewalld/services/kodi-eventserver.xml This is apparently an outdated remark. I can remove the kodi service files from firewalld and upload as 1.2.0-2 but I'd like the Debian kodi package to take over and ship those files first before. Dear kodi maintainers: Please ship the above firewalld service files in either kodi or kodi-data and add a versioned Breaks: firewalld (<< 1.2.0-2) Replaces: firewalld (<< 1.2.0-2) Regards, Michael OpenPGP_signature Description: OpenPGP digital signature
Processed: Bug#1012903 marked as pending in bladerf
Processing control commands: > tag -1 pending Bug #1012903 [src:bladerf] bladerf: ftbfs with GCC-12 Added tag(s) pending. -- 1012903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012903: marked as pending in bladerf
Control: tag -1 pending Hello, Bug #1012903 in bladerf reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian-hamradio-team/bladerf/-/commit/bf52043433e9e6fea378861cf1d42f3464f1c528 Fix build failure with gcc-12. (Closes: #1012903) (this message was generated automatically) -- Greetings https://bugs.debian.org/1012903
Bug#1015129: marked as done (sphinx-automodapi: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 24 Jul 2022 11:35:25 + with message-id and subject line Bug#1015129: fixed in sphinx-automodapi 0.14.1-2 has caused the Debian Bug report #1015129, regarding sphinx-automodapi: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 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.) -- 1015129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015129 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sphinx-automodapi Version: 0.14.1-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:239: python3.9 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.9_sphinx-automodapi/build' > (and everything under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.9' does not exist -- can't clean it > I: pybuild base:239: python3.10 setup.py clean > running clean > removing '/<>/.pybuild/cpython3_3.10_sphinx-automodapi/build' > (and everything under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.10' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using options from > sphinx-automodapi-0.14.1/debian/source/options: > --extend-diff-ignore=^[^/]+.egg-info/ > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building sphinx-automodapi using existing > ./sphinx-automodapi_0.14.1.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > sphinx-automodapi-0.14.1/sphinx_automodapi/version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/sphinx-automodapi_0.14.1-1.diff.0IDueX > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T06:05:00Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/sphinx-automodapi_0.14.1-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results 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: sphinx-automodapi Source-Version: 0.14.1-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of sphinx-automodapi, 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 1015...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ole Streicher (supplier of updated sphinx-automodapi 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 Jul 2022 11:21:08 +0200 Source: sphinx-automodapi Architecture: source Version: 0.14.1-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Ole Streicher Closes: 1015129 Changes: sphinx-auto
Bug#1015074: marked as done (pytest-qt: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Sun, 24 Jul 2022 12:01:02 +0100 with message-id and subject line Re: Bug#1015074: pytest-qt: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 has caused the Debian Bug report #1015074, regarding pytest-qt: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 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.) -- 1015074: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015074 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pytest-qt Version: 4.0.2-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[2]: Entering directory '/<>/docs' > rm -rf _build/* > make[2]: Leaving directory '/<>/docs' > make[1]: Leaving directory '/<>' >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using options from pytest-qt-4.0.2/debian/source/options: > --extend-diff-ignore=^[^/]+\.egg-info/ > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building pytest-qt using existing > ./pytest-qt_4.0.2.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > pytest-qt-4.0.2/src/pytestqt/_version.py > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/pytest-qt_4.0.2-1.diff.AoIdix > dpkg-source: info: Hint: make sure the version in debian/changelog matches > the unpacked source tree > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2022-07-16T05:59:10Z The full build log is available from: http://qa-logs.debian.net/2022/07/16/pytest-qt_4.0.2-1_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20220716;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20220716&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=1#results 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: pytest-qt Version: 4.0.2-1 On Sat, Jul 16, 2022 at 03:39:20PM +0200, Lucas Nussbaum wrote: > Source: pytest-qt > Version: 4.0.2-1 > Severity: serious > Justification: FTBFS > Tags: bookworm sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20220716 ftbfs-bookworm > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. This seems like a transient error; I rebuilt it with a local sbuild with no difficulty (and no dpkg-source error). Best wishes, Julian--- End Message ---
Processed: src:inkscape: fails to migrate to testing for too long: ftbfs on arm64, ppc64el, s390x
Processing control commands:
> close -1 1.2.1+ds-1
Bug #1015932 [src:inkscape] src:inkscape: fails to migrate to testing for too
long: ftbfs on arm64, ppc64el, s390x
Marked as fixed in versions inkscape/1.2.1+ds-1.
Bug #1015932 [src:inkscape] src:inkscape: fails to migrate to testing for too
long: ftbfs on arm64, ppc64el, s390x
Marked Bug as done
> block -1 by 1012496
Bug #1015932 {Done: Paul Gevers } [src:inkscape]
src:inkscape: fails to migrate to testing for too long: ftbfs on arm64,
ppc64el, s390x
1015932 was not blocked by any bugs.
1015932 was not blocking any bugs.
Added blocking bug(s) of 1015932: 1012496
--
1015932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015932
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1015932: src:inkscape: fails to migrate to testing for too long: ftbfs on arm64, ppc64el, s390x
Source: inkscape Version: 1.1.2-3 Severity: serious Control: close -1 1.2.1+ds-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1012496 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:inkscape has been trying to migrate for 62 days [2]. Hence, I am filing this bug. Your package fails to build from source as reported in bug #1012496. 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=inkscape OpenPGP_signature Description: OpenPGP digital signature
Bug#1014306: crun - seriously out of date
On Fri, 22 Jul 2022 15:43:56 +0200 Faidon Liambotis wrote: > On Sun, Jul 03, 2022 at 09:20:37PM +0200, Bastian Blank wrote: > > crun was not uploaded since before the release of Debian 11. It is now > > seriously out of date and even fails hard as root, see #1012053. > > I built 1.4.5 using the existing Debian packaging and with no changes > other than dropping all d/patches as they are now merged upstream. The > package is fully functional with my testing. > > 1.5 was released 2 days ago as well, but I haven't tried to build that > yet. > > Dmitry, are you still working on this package? I noticed that it's under > the debian group in Salsa -- would you be OK if someone else made an > upload? CC'ing @Dmitry explicitly in case that helps. @Faidon, I suppose it would be fine to NMU and put it into DELAYED/10 atleast till we have time for an ACK. This is triggering a bunch of auto-rm and hence it is prudent. Do consider doing so if you agree. -- Best, Nilesh signature.asc Description: PGP signature
Processed: tagging ftbfs
Processing commands for cont...@bugs.debian.org: > tags 1013019 + ftbfs Bug #1013019 [src:pyferret] pyferret: ftbfs with GCC-12 Added tag(s) ftbfs. > tags 1013069 + ftbfs Bug #1013069 [src:wreport] wreport: ftbfs with GCC-12 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 1013019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013019 1013069: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1013069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1014741: marked as done (libgd-perl: GD and GD2 image formats are disabled in libgd3 package)
Your message dated Sun, 24 Jul 2022 09:49:39 + with message-id and subject line Bug#1014741: fixed in libgd-graph-perl 1.54~ds-4 has caused the Debian Bug report #1014741, regarding libgd-perl: GD and GD2 image formats are disabled in libgd3 package 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.) -- 1014741: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1014741 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libgd-perl Version: 2.76-2+b1 Severity: grave Justification: renders package unusable Graph.pm contains code that specifies file formats "gd" and "gd2" which are currently disabled in Debian's libgd3 package (these are actually obsolete formats, apparently, and only used in testing scenarios according to cursory googling). Attempting to use libgd-perl will always result in an error at line 515 in Graph.pm and likely elsewhere. Removing gd and gd2 as options from line 515 (and elsewhere as needed) renders client uses of this library functional again. Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines *** -- System Information: Debian Release: bookworm/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-6-amd64 (SMP w/4 CPU threads) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libgd-perl depends on: ii libc6 2.33-8 ii libgd3 2.3.3-3 ii perl5.34.0-5 ii perl-base [perlapi-5.34.0] 5.34.0-5 libgd-perl recommends no packages. libgd-perl suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: libgd-graph-perl Source-Version: 1.54~ds-4 Done: gregor herrmann We believe that the bug you reported is fixed in the latest version of libgd-graph-perl, 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 1014...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. gregor herrmann (supplier of updated libgd-graph-perl 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, 24 Jul 2022 11:26:30 +0200 Source: libgd-graph-perl Architecture: source Version: 1.54~ds-4 Distribution: unstable Urgency: medium Maintainer: Debian Perl Group Changed-By: gregor herrmann Closes: 1014741 Changes: libgd-graph-perl (1.54~ds-4) unstable; urgency=medium . * Team upload. * Make build and runtime dependency on libgd-perl versioned. This also indirectly ensures a versioned dependency on libgd3. (Hopefully closes: #1014741) * Declare compliance with Debian Policy 4.6.1. Checksums-Sha1: d71b56e373fb15aafe961d925224d6b7e61763b9 2522 libgd-graph-perl_1.54~ds-4.dsc 591bdb59e350b829f53987f998ffe05860789ec3 9828 libgd-graph-perl_1.54~ds-4.debian.tar.xz Checksums-Sha256: 4456118d776ecaa80115047b6dd7b7f3c14a7c005fa1bc893b2cda250e5ec348 2522 libgd-graph-perl_1.54~ds-4.dsc a2c3ac77faa92f2855e41a114fdb9ee08f33e1ecf47a096699b1da685f013f51 9828 libgd-graph-perl_1.54~ds-4.debian.tar.xz Files: e50a4c6134a66e1e1170bc6bf08e861e 2522 perl optional libgd-graph-perl_1.54~ds-4.dsc 358ef68b5cbf33efe277fe7d0b4ac04b 9828 perl optional libgd-graph-perl_1.54~ds-4.debian.tar.xz -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEE0eExbpOnYKgQTYX6uzpoAYZJqgYFAmLdEOlfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEQx RTEzMTZFOTNBNzYwQTgxMDREODVGQUJCM0E2ODAxODY0OUFBMDYACgkQuzpoAYZJ qgbeFQ/8Cih6326mTZ6f7yyJOWmpR2FSNDp2xeXf2GRFoj/ltq0IP28d/IEdqIl7 z5ITLr56DWuh83MrsYHw9bf1B/htdFhP8dh71NVfqvSTSXi8EDEz1sM6UaaQJ2k3 H+oRVudE3tYhvifMeRVerTN8jftqZ++kssce6QKJX/zDHBsXWuAFQOPDPbjBloxD 5aY5U0gU27c0uIezhnGbA+C2jKA3Tt7dZgdnthuM7leg3B+U0lx/r3YR3fbf7Vk2 KF8DQHFNAhXvpevjPAX07R34gKChz
Bug#1012917: marked as done (dynare: ftbfs with GCC-12)
Your message dated Sun, 24 Jul 2022 09:05:07 + with message-id and subject line Bug#1012917: fixed in dynare 5.1-3 has caused the Debian Bug report #1012917, regarding dynare: ftbfs with GCC-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.) -- 1012917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dynare Version: 5.1-2 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-12 [This bug is targeted to the upcoming bookworm 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-12/g++-12, but succeeds to build with gcc-11/g++-11. The severity of this report will be raised before the bookworm release. The full build log can be found at: http://qa-logs.debian.net/2022/06/09/gcc12/dynare_5.1-2_unstable_gcc12.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[4]: Leaving directory '/<>/mex/build/octave/block_kalman_filter' Making pdf in sobol make[4]: Entering directory '/<>/mex/build/octave/sobol' make[4]: Nothing to be done for 'pdf'. make[4]: Leaving directory '/<>/mex/build/octave/sobol' Making pdf in perfect_foresight_problem make[4]: Entering directory '/<>/mex/build/octave/perfect_foresight_problem' make[4]: Nothing to be done for 'pdf'. make[4]: Leaving directory '/<>/mex/build/octave/perfect_foresight_problem' Making pdf in num_procs make[4]: Entering directory '/<>/mex/build/octave/num_procs' make[4]: Nothing to be done for 'pdf'. make[4]: Leaving directory '/<>/mex/build/octave/num_procs' Making pdf in block_trust_region make[4]: Entering directory '/<>/mex/build/octave/block_trust_region' make[4]: Nothing to be done for 'pdf'. make[4]: Leaving directory '/<>/mex/build/octave/block_trust_region' Making pdf in disclyap_fast make[4]: Entering directory '/<>/mex/build/octave/disclyap_fast' make[4]: Nothing to be done for 'pdf'. make[4]: Leaving directory '/<>/mex/build/octave/disclyap_fast' Making pdf in libdynare++ make[4]: Entering directory '/<>/mex/build/octave/libdynare++' make[4]: Nothing to be done for 'pdf'. make[4]: Leaving directory '/<>/mex/build/octave/libdynare++' Making pdf in gensylv make[4]: Entering directory '/<>/mex/build/octave/gensylv' make[4]: Nothing to be done for 'pdf'. make[4]: Leaving directory '/<>/mex/build/octave/gensylv' Making pdf in libkorder make[4]: Entering directory '/<>/mex/build/octave/libkorder' make[4]: Nothing to be done for 'pdf'. make[4]: Leaving directory '/<>/mex/build/octave/libkorder' Making pdf in dynare_simul_ make[4]: Entering directory '/<>/mex/build/octave/dynare_simul_' make[4]: Nothing to be done for 'pdf'. make[4]: Leaving directory '/<>/mex/build/octave/dynare_simul_' Making pdf in k_order_perturbation make[4]: Entering directory '/<>/mex/build/octave/k_order_perturbation' make[4]: Nothing to be done for 'pdf'. make[4]: Leaving directory '/<>/mex/build/octave/k_order_perturbation' Making pdf in k_order_welfare make[4]: Entering directory '/<>/mex/build/octave/k_order_welfare' make[4]: Nothing to be done for 'pdf'. make[4]: Leaving directory '/<>/mex/build/octave/k_order_welfare' Making pdf in local_state_space_iterations make[4]: Entering directory '/<>/mex/build/octave/local_state_space_iterations' make[4]: Nothing to be done for 'pdf'. make[4]: Leaving directory '/<>/mex/build/octave/local_state_space_iterations' Making pdf in ms_sbvar make[4]: Entering directory '/<>/mex/build/octave/ms_sbvar' make[4]: Nothing to be done for 'pdf'. make[4]: Leaving directory '/<>/mex/build/octave/ms_sbvar' Making pdf in kal
Bug#1015929: python3-fast-histogram: Installation of the C extension might be incorrect
Package: python3-fast-histogram Version: 0.11-1 Severity: serious Package: python3-fast-histogram Version: 0.9-2+b1 /usr/lib/python3/dist-packages/fast_histogram/_histogram_core.cpython-310-x86_64-linux-gnu.so /usr/lib/python3/dist-packages/fast_histogram/_histogram_core.cpython-39-x86_64-linux-gnu.so Package: python3-fast-histogram Version: 0.11-1+b1 /usr/lib/python3/dist-packages/fast_histogram/_histogram_core.abi3.so
Bug#1012895: aptitude: ftbfs with GCC-12
Control: tags -1 + patch On Thu, 16 Jun 2022 12:07:38 + Matthias Klose wrote: > The package fails to build in a test rebuild on at least amd64 with > gcc-12/g++-12, but succeeds to build with gcc-11/g++-11. The > severity of this report will be raised before the bookworm release. I tried to build aptitude, found it fails due to cwidget bug #1015925. I tried to look at this failure, which also happens after fixing that. I don't know enough C++ but seems that the operator<< function in the test_parsers.cc file taking std::optional as a parameter is not being found by GCC 12 even though it should be found. The g++ output was verbose but the clang++ output was very clear. The issue is that the operator<< functions are not declared before the call site, so forward declarations before HelperMacros.h are needed: #include template std::ostream &operator<<(std::ostream &out, const std::optional o); template std::ostream &operator<<(std::ostream &out, const std::vector v); #include I'm not sure how to contribute this change to the package because this should be a native package but isn't and has debian/patches/ but also an upstream master branch that seems to be unused. I suggest merging the contents of debian/patches/ to the upstream master branch and then cherry-picking the FTBFS patches to a new minor release branch instead of using debian/patches/. I've filed two merge requests with two different approaches, one is a commit for the master branch and one a patch for the debian-sid branch. https://salsa.debian.org/apt-team/aptitude/-/merge_requests/14 https://salsa.debian.org/apt-team/aptitude/-/merge_requests/13 -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed: Re: aptitude: ftbfs with GCC-12
Processing control commands: > tags -1 + patch Bug #1012895 [src:aptitude] aptitude: ftbfs with GCC-12 Added tag(s) patch. -- 1012895: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012895 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1012917: marked as pending in dynare
Control: tag -1 pending Hello, Bug #1012917 in dynare 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/pkg-octave-team/dynare/-/commit/7579336bd207f6cdbe9923e57c47ace5f7942050 gcc-12.patch: new patch, fixes FTBFS against GCC 12 Closes: #1012917 (this message was generated automatically) -- Greetings https://bugs.debian.org/1012917
Processed: Bug#1012917 marked as pending in dynare
Processing control commands: > tag -1 pending Bug #1012917 [src:dynare] dynare: ftbfs with GCC-12 Added tag(s) pending. -- 1012917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012917 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1000932: marked as done (doxygen: Please upgrade to llvm-toolchain-13 or 14)
Your message dated Sun, 24 Jul 2022 07:34:00 + with message-id and subject line Bug#1000932: fixed in doxygen 1.9.4-1 has caused the Debian Bug report #1000932, regarding doxygen: Please upgrade to llvm-toolchain-13 or 14 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.) -- 1000932: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1000932 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: doxygen Severity: important Dear Maintainer, As part of the effort to limit the number of llvm packages in the archive, it would be great if you could upgrade to -13 (or -12). Bookworm won't ship with llvm-toolchain-11 llvm-defaults is now pointing to -13. Thanks, Sylvestre --- End Message --- --- Begin Message --- Source: doxygen Source-Version: 1.9.4-1 Done: Paolo Greppi We believe that the bug you reported is fixed in the latest version of doxygen, 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 1000...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paolo Greppi (supplier of updated doxygen 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, 24 Jul 2022 09:14:42 +0200 Source: doxygen Architecture: source Version: 1.9.4-1 Distribution: unstable Urgency: medium Maintainer: Paolo Greppi Changed-By: Paolo Greppi Closes: 882037 983059 1000932 1013636 Changes: doxygen (1.9.4-1) unstable; urgency=medium . [ Debian Janitor ] * Use secure URI in Homepage field. * Bump debhelper from old 12 to 13. * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository, Repository-Browse. * Update standards version to 4.6.0, no changes needed. . [ Paolo Greppi ] * New upstream version. Closes: #1013636, #983059, #882037 and #482986. * Update copyright and dependencies * Upgrade to llvm-toolchain-13. Closes: #1000932. * Refresh descriptions and fix lintian I: duplicate-short-description * Update standards version to 4.6.1, no changes needed. * Remove obsolete Conflicts clause Checksums-Sha1: 6b90846950abc6f1e5ee375b79805b022537145f 2782 doxygen_1.9.4-1.dsc 730025e0976e4408e2a972703d40f725172cd316 5135672 doxygen_1.9.4.orig.tar.gz 2ded991bd7eb41f1f6b7ce52556a1f929e499501 25616 doxygen_1.9.4-1.debian.tar.xz 8723e7e032182b51540a373aa04edc264b06a1fe 12807 doxygen_1.9.4-1_source.buildinfo Checksums-Sha256: 51841062614ef61127eb2f82c1beb376f1fb0412232b3484bcc05ca3672b10f5 2782 doxygen_1.9.4-1.dsc 1b083d15b29817463129ae1ae73b930d883030eeec090ea7a99b3a04fdb51c76 5135672 doxygen_1.9.4.orig.tar.gz add0b944c9b3d77d7cd9b7bb8f09cce89b36a8d305cf2b3fb3b32eb5e625a352 25616 doxygen_1.9.4-1.debian.tar.xz 952c5d3386b5a7b302e9c8fa33c46d79c3be8303f406685eccc89ed1b968c3d6 12807 doxygen_1.9.4-1_source.buildinfo Files: 63eecea974e1894ff1eea831416a6457 2782 devel optional doxygen_1.9.4-1.dsc 5b5ba8ff65433c4473259989f14eaf37 5135672 devel optional doxygen_1.9.4.orig.tar.gz ae2be57e023cae13e9de8ce16a4cc282 25616 devel optional doxygen_1.9.4-1.debian.tar.xz 8a97a2e698d1c41b6c127920b4642d23 12807 devel optional doxygen_1.9.4-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJLBAEBCgA1FiEEyTpTRBhTUv5T0mHqIjkMJVxGBPQFAmLc8YoXHHBhb2xvLmdy ZXBwaUBsaWJwZi5jb20ACgkQIjkMJVxGBPRXkxAAqdk3kZjDVIQQuiy2WfjzFBiG lRcBPR8Hgyfe08e1UxhpSZWZsIjq9I2uROrsYoEKfmzwcCBDODQGfPpZlE697dME 7gIlNs4rmvJZ+EYPtPJbx2pWeNiAeQD7kEKULhahMmvkALSVpPvdrequuiHvIfxU nenX0iNah2MVtT1wgdgzirT9+Km/PGW9ws9hDcheJATdu03NsdWpWCaNCM+dfjF3 9/rdObR+m3ohWJqaoVqoSe7joWHJe7rbmvNKxhfwJmstG99tfJ/4UnQPNHplzFW9 R/o1CX7lzcMnX+WIpy/Lz3v5CkpixP72slWQPKrz31vKe10NFNU8Tb424W61SxEt 4W/6pCsNQ6OMxr/QkRci7CH9QwQu2wrAGS/C/3VFL8535eo1ssX+R6sWdPjSOEJb b3OjvSHYhDT6ItWDH45xWa+0nAwQg6hSeq3m9RL/7toCXJziCqaqzUTlYWKzGwrb iZDeANxfQ9aYh6/UrDgkxmaKhFLBMrXnDRhxbBOlThKvXbRtasQXpS5ctagStK3u +gBsPe+YDXHRqkC9HOhNbO6xpGEJ92XcScWvDXlBJbmGG3O7ZuOKWdKn/c2jJTtJ eKak09NkObOuYBElTLjnA2hS3oFNUBqx8jxazYd/ETYSwsHHsee0YBpok2hZWY8z rnZlYpzaJOloMZTWUKQ= =wdfq -END PGP SIGNATURE End Message ---
Bug#1015886: Bug: kodi-data conflicts firewalld on file kodi-eventserver.xml
On 24 juil. 2022 09:39, Andy wrote: > Hi Christian Hi again, > I have come across a bug in the deb-multimedia package kodi-data. The > debian maintainer of firewalld recommended to file a bug with debian- > multimedia. firewalld will remove these files. https://github.com/firewalld/firewalld/pull/552 Christian
