Bug#957412: marked as done (kylin-burner: ftbfs with GCC-10)
Your message dated Sat, 01 Aug 2020 04:34:17 + with message-id and subject line Bug#957412: fixed in kylin-burner 3.0.8-1 has caused the Debian Bug report #957412, regarding kylin-burner: ftbfs with GCC-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.) -- 957412: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957412 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kylin-burner Version: 3.0.7-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/kylin-burner_3.0.7-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] /usr/bin/ld: burner-audio-disc.o:./src/burner-app.h:47: multiple definition of `maximize_bt'; main.o:./src/burner-app.h:47: first defined here /usr/bin/ld: burner-audio-disc.o:./src/burner-app.h:46: multiple definition of `statusbarbox'; main.o:./src/burner-app.h:46: first defined here /usr/bin/ld: burner-audio-disc.o:./src/burner-app.h:45: multiple definition of `widget'; main.o:./src/burner-app.h:45: first defined here /usr/bin/ld: burner-audio-disc.o:./src/burner-app.h:44: multiple definition of `nb_items'; main.o:./src/burner-app.h:44: first defined here /usr/bin/ld: burner-project.o:./src/burner-app.h:48: multiple definition of `unmaximize_bt'; main.o:./src/burner-app.h:48: first defined here /usr/bin/ld: burner-project.o:./src/burner-app.h:47: multiple definition of `maximize_bt'; main.o:./src/burner-app.h:47: first defined here /usr/bin/ld: burner-project.o:./src/burner-app.h:46: multiple definition of `statusbarbox'; main.o:./src/burner-app.h:46: first defined here /usr/bin/ld: burner-project.o:./src/burner-app.h:45: multiple definition of `widget'; main.o:./src/burner-app.h:45: first defined here /usr/bin/ld: burner-project.o:./src/burner-app.h:44: multiple definition of `nb_items'; main.o:./src/burner-app.h:44: first defined here /usr/bin/ld: burner-project-type-chooser.o:./src/burner-app.h:45: multiple definition of `widget'; main.o:./src/burner-app.h:45: first defined here /usr/bin/ld: burner-project-type-chooser.o:./src/burner-app.h:44: multiple definition of `nb_items'; main.o:./src/burner-app.h:44: first defined here /usr/bin/ld: burner-project-type-chooser.o:./src/burner-app.h:48: multiple definition of `unmaximize_bt'; main.o:./src/burner-app.h:48: first defined here /usr/bin/ld: burner-project-type-chooser.o:./src/burner-app.h:47: multiple definition of `maximize_bt'; main.o:./src/burner-app.h:47: first defined here /usr/bin/ld: burner-project-type-chooser.o:./src/burner-app.h:46: multiple definition of `statusbarbox'; main.o:./src/burner-app.h:46: first defined here /usr/bin/ld: burner-project-manager.o:./src/burner-project-manager.h:79: multiple definition of `manager_chooser'; burner-project-type-chooser.o:./src/burner-project-manager.h:79: first defined here /usr/bin/ld: burner-project-manager.o:./src/burner-project-manager.h:80: multiple definition of `type'; burner-project-type-chooser.o:./src/burner-project-manager.h:80: first defined here /usr/bin/ld: burner-project-manager.o:./src/burner-app.h:46: multiple definition of `statusbarbox'; main.o:./src/burner-app.h:46: first defined here /usr/bin/ld: burner-project-manager.o:./src/burner-app.h:44: multiple definition of `nb_items'; main.o:./src/burner-app.h:44: first defined here /usr/bin/ld: burner-project-manager.o:./src/burner-app.h:45: multiple definition of `widget'; main.o:./src/burner-app.h:45: first defined here /usr/bin/ld: burner-project-manager
Bug#966409: libjpeg-turbo: versions in debian/*.symbols files are missing the epochs
Control: clone -1 -2 Control: reassign -2 lintian Control: severity -2 wishlist Control: retitle -2 lintian: detect mismatches between symbols files and changelog versions On Tue, 28 Jul 2020 15:04:08 +0800 Paul Wise wrote: > The versions in the debian/*.symbols files are missing the epochs. This > means that packages using symbols newer than buster will not upgrade > libjpeg62-turbo and libturbojpeg0 when being upgraded to bullseye. It would be great if lintian could detect when a version number in the symbols files does not match one of the upstream or Debian versions in the Debian changelog files. Versions older than the oldest version in the Debian changelog file can be ignored of course. I'd suggest structuring this as two complaints with two severities: * At error level, probably ftp-master rejected, for when a symbols version is just missing the epoch. So a check that any of the versions in the Debian changelog file would match the symbol versions if the epoch were present in the symbols version. * At warning or info level, for when symbols version just doesn't match any of the versions in the Debian changelog file. Both of these need to take into account that the versions in the symbols file might be missing the Debian revision or they might have a tilde appended to the Debian revision in order to allow backports. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Processed (with 4 errors): Re: libjpeg-turbo: versions in debian/*.symbols files are missing the epochs
Processing control commands:
> clone -1 -2
Bug #966409 [src:libjpeg-turbo] libjpeg-turbo: versions in debian/*.symbols
files are missing the epochs
Bug #966419 [src:libjpeg-turbo] libjpeg-turbo: versions in debian/*.symbols
files are missing the epochs
Failed to clone 966409: Bug is marked as being merged with others. Use an
existing clone.
> reassign -2 lintian
Failed to clear fixed versions and reopen on -2: The 'bug' parameter ("-2") to
Debbugs::Control::set_package did not pass regex check
.
> severity -2 wishlist
Failed to set severity of Bug -2 to wishlist: The 'bug' parameter ("-2") to
Debbugs::Control::set_severity did not pass regex check
.
> retitle -2 lintian: detect mismatches between symbols files and changelog
> versions
Failed to set the title of -2: The 'bug' parameter ("-2") to
Debbugs::Control::set_title did not pass regex check
.
--
966409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966409
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#966409: libjpeg-turbo: versions in debian/*.symbols files are missing the epochs
On Tue, 28 Jul 2020 11:55:02 + Mike Gabriel wrote: > Please NMU (ideally with commits to the packaging Git). > Also coordinate with Adrian Bunk. FTR I won't be uploading but Adrian will be. -- bye, pabs https://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#957531: marked as done (mercator: ftbfs with GCC-10)
Your message dated Sat, 01 Aug 2020 01:48:35 + with message-id and subject line Bug#957531: fixed in mercator 0.3.3-6 has caused the Debian Bug report #957531, regarding mercator: ftbfs with GCC-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.) -- 957531: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957531 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mercator Version: 0.3.3-5 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/mercator_0.3.3-5_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] +#MISSING: 0.3.3-5# (optional=templinst)_ZNSt8_Rb_treeIiSt4pairIKiPN8Mercator7SurfaceEESt10_Select1stIS5_ESt4lessIiESaIS5_EE22_M_emplace_hint_uniqueIIRKSt21piecewise_construct_tSt5tupleIIRS1_EESG_IIESt17_Rb_tree_iteratorIS5_ESt23_Rb_tree_const_iteratorIS5_EDpOT_@Base 0.3.3 +#MISSING: 0.3.3-5# (optional=certain_32b_arches)_ZNSt8_Rb_treeIiSt4pairIKiPN8Mercator7SurfaceEESt10_Select1stIS5_ESt4lessIiESaIS5_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOiEESG_IJESt17_Rb_tree_iteratorIS5_ESt23_Rb_tree_const_iteratorIS5_EDpOT_@Base 0.3.2 +#MISSING: 0.3.3-5# (optional=templinst)_ZNSt8_Rb_treeIiSt4pairIKiPN8Mercator7SurfaceEESt10_Select1stIS5_ESt4lessIiESaIS5_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESG_IJESt17_Rb_tree_iteratorIS5_ESt23_Rb_tree_const_iteratorIS5_EDpOT_@Base 0.3.3 +#MISSING: 0.3.3-5# (optional=certain_32b_arches)_ZNSt8_Rb_treeIiSt4pairIKiSt3mapIiN8Mercator9BasePointESt4lessIiESaIS0_IS1_S4_St10_Select1stISA_ES6_SaISA_EE22_M_emplace_hint_uniqueIIRKSt21piecewise_construct_tSt5tupleIIRS1_EESJ_IIESt17_Rb_tree_iteratorISA_ESt23_Rb_tree_const_iteratorISA_EDpOT_@Base 0.3.2 +#MISSING: 0.3.3-5# (optional=certain_32b_arches)_ZNSt8_Rb_treeIiSt4pairIKiSt3mapIiN8Mercator9BasePointESt4lessIiESaIS0_IS1_S4_St10_Select1stISA_ES6_SaISA_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESJ_IJESt17_Rb_tree_iteratorISA_ESt23_Rb_tree_const_iteratorISA_EDpOT_@Base 0.3.2 (arch-bits=32)_ZSt13__adjust_heapIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_iS3_NS0_5__ops15_Iter_comp_iterINS2_7EdgeAtYvT_T0_SE_T1_T2_@Base 0.3.2 + _ZSt13__heap_selectIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_NS0_5__ops15_Iter_comp_iterINS2_7EdgeAtYvT_SD_SD_T0_@Base 0.3.3-5 (arch-bits=32)_ZSt16__introsort_loopIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_iNS0_5__ops15_Iter_comp_iterINS2_7EdgeAtYvT_SD_T0_T1_@Base 0.3.2 - (c++)"std::_Rb_tree >, std::_Select1st > >, std::less, std::allocator > > >::_M_erase(std::_Rb_tree_node > >*)@Base" 0.3.0 - (c++)"std::_Rb_tree >, std::_Select1st > >, std::less, std::allocator > > >::erase(Mercator::Effector const* const&)@Base" 0.3.0 - (c++)"std::_Rb_tree, std::less, std::allocator >::_M_erase(std::_Rb_tree_node*)@Base" 0.3.0 - (c++)"std::_Rb_tree, std::less, std::allocator >::_M_erase(std::_Rb_tree_node*)@Base" 0.3.0 - (c++)"std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_erase(std::_Rb_tree_node >*)@Base" 0.3.0 - (c++)"std::_Rb_tree, std::_Select1st >, std::less, std::allocator > >::_M_erase(std::_Rb_tree_node >*)@Base" 0.3.0 + _ZSt22__move_median_to_firstIN9__gnu_cxx17__normal_iteratorIPN8Mercator4EdgeESt6vectorIS3_SaIS3_NS0_5__ops15_Iter_comp_iterINS2_7EdgeAtYvT_SD_SD_SD_T0_@Base 0.3.3-5 +#MISSING: 0.3.3-5# (c++)"std::_R
Bug#966575: same error message here
Dear Debian maintainers, On Fri, 31 Jul 2020 22:39:22 +0200 cacat...@tuxfamily.org wrote: > Package: grub-pc > Version: 2.02+dfsg1-20+deb10u2 > > Dear Maintainers, > > Don't know if it's useful but contributing infos I collected on this, > since I ran into the same error message on a Lenovo Thinkpad T510 > running Debian Stable. The same here. You should be more careful when upgrading or fixing a security issue in the boot loader. It currently breaks a Debian Buster system, which is production. The suggested grub reinstall method did _not_ work for me. I booted from a USB stick into rescue mode and had to downgrade grub-common package (I don’t have grub2 on my system) and reinstall all dependent packages again. After downgrading grub-common/grub2-common to version 2.02+dfsg1-20, my system boots and works fine. Downgrade grub-common/grub2-common: from: 2.02+dfsg1-20+deb10u2 to:2.02+dfsg1-20 and it did work after reboot. See my APT history log for details. “ Start-Date: 2020-07-31 22:52:35 Commandline: apt install grub-common=2.02+dfsg1-20 Downgrade: grub-common:amd64 (2.02+dfsg1-20+deb10u2, 2.02+dfsg1-20) Remove: grub2-common:amd64 (2.02+dfsg1-20+deb10u2), grub-efi-amd64-bin:amd64 (2.02+dfsg1-20+deb10u2), grub-efi-amd64:amd64 (2.02+dfsg1-20+deb10u2), shim-signed:amd64 (1.33+15+1533136590.3beb971-7), grub-efi-amd64-signed:amd64 (1+2.02+dfsg1+20+deb10u2) End-Date: 2020-07-31 22:53:28 Start-Date: 2020-07-31 22:55:36 Commandline: apt install grub2-common=2.02+dfsg1-20 Install: grub2-common:amd64 (2.02+dfsg1-20) End-Date: 2020-07-31 22:55:41 Start-Date: 2020-07-31 22:56:39 Commandline: apt install grub-efi-amd64-bin=2.02+dfsg1-20 Install: grub-efi-amd64-bin:amd64 (2.02+dfsg1-20) End-Date: 2020-07-31 22:56:53 Start-Date: 2020-07-31 22:57:09 Commandline: apt install grub-efi-amd64=2.02+dfsg1-20 Install: grub-efi-amd64:amd64 (2.02+dfsg1-20) End-Date: 2020-07-31 22:57:33 Start-Date: 2020-07-31 22:58:43 Commandline: apt install grub-efi-amd64-signed=1+2.02+dfsg1+20 Install: shim-signed:amd64 (1.33+15+1533136590.3beb971-7, automatic), grub-efi-amd64-signed:amd64 (1+2.02+dfsg1+20) End-Date: 2020-07-31 22:58:50 “ My kernel is: 4.19.0-9-amd64 No grub2. grub-common, grub2-common is now at v2.02+dfsg1-20. Debian Buster latest v10.4. Linux package: linux-image-4.19.0-9-amd64-signed v4.19.118-2+deb10u1 I have working UEFI booting system, w/o secure boot and amd64 grub package UEFI signed by Debian. Kind regards, -- Miklós Quartus q...@foresthacker.hu signature.asc Description: Message signed with OpenPGP
Bug#957017: marked as done (atlas-cpp: ftbfs with GCC-10)
Your message dated Sat, 01 Aug 2020 01:33:30 + with message-id and subject line Bug#957017: fixed in atlas-cpp 0.6.4-3 has caused the Debian Bug report #957017, regarding atlas-cpp: ftbfs with GCC-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.) -- 957017: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957017 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:atlas-cpp Version: 0.6.4-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/atlas-cpp_0.6.4-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] - (optional=templinst)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_N5Atlas7Objects8SmartPtrINS9_8RootDataSt10_Select1stISD_ESt4lessIS6_ESaISD_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS6_EESO_IJESt17_Rb_tree_iteratorISD_ESt23_Rb_tree_const_iteratorISD_EDpOT_@Base 0.6.3 +#MISSING: 0.6.4-2# (optional=inline)_ZNSt7__cxx114listINS_12basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EEaSERKS7_@Base 0.6.2 +#MISSING: 0.6.4-2# (optional=templinst)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_N5Atlas7Objects8SmartPtrINS9_8RootDataSt10_Select1stISD_ESt4lessIS6_ESaISD_EE22_M_emplace_hint_uniqueIIRKSt21piecewise_construct_tSt5tupleIIRS6_EESO_IIESt17_Rb_tree_iteratorISD_ESt23_Rb_tree_const_iteratorISD_EDpOT_@Base 0.6.3 +#MISSING: 0.6.4-2# (optional=templinst)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_N5Atlas7Objects8SmartPtrINS9_8RootDataSt10_Select1stISD_ESt4lessIS6_ESaISD_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS6_EESO_IJESt17_Rb_tree_iteratorISD_ESt23_Rb_tree_const_iteratorISD_EDpOT_@Base 0.6.3 _ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_N5Atlas7Objects8SmartPtrINS9_8RootDataSt10_Select1stISD_ESt4lessIS6_ESaISD_EE24_M_get_insert_unique_posERS6_@Base 0.6.2 (optional=inline)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_N5Atlas7Objects8SmartPtrINS9_8RootDataSt10_Select1stISD_ESt4lessIS6_ESaISD_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISD_ERS6_@Base 0.6.2 - _ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_N5Atlas7Objects8SmartPtrINS9_8RootDataSt10_Select1stISD_ESt4lessIS6_ESaISD_EE8_M_eraseEPSt13_Rb_tree_nodeISD_E@Base 0.6.2 - (optional=templinst)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_S7_IPFN5Atlas7Objects8SmartPtrINS9_8RootDataEEERS6_iEiEESt10_Select1stISH_ESt4lessIS6_ESaISH_EE22_M_emplace_hint_uniqueIIRKSt21piecewise_construct_tSt5tupleIISD_EESS_IIESt17_Rb_tree_iteratorISH_ESt23_Rb_tree_const_iteratorISH_EDpOT_@Base 0.6.3 - (optional=templinst)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_S7_IPFN5Atlas7Objects8SmartPtrINS9_8RootDataEEERS6_iEiEESt10_Select1stISH_ESt4lessIS6_ESaISH_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJSD_EESS_IJESt17_Rb_tree_iteratorISH_ESt23_Rb_tree_const_iteratorISH_EDpOT_@Base 0.6.3 +#MISSING: 0.6.4-2# _ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_N5Atlas7Objects8SmartPtrINS9_8RootDataSt10_Select1stISD_ESt4lessIS6_ESaISD_EE8_M_eraseEPSt13_Rb_tree_nodeISD_E@Base 0.6.2 +#MISSING: 0.6.4-2# (optional=templinst)_ZNSt8_Rb_treeIKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIS6_S7_IPFN5
Bug#966575: grub-pc: error: symbol `grub_calloc' not found.
On Sat, Aug 01, 2020 at 01:23:30AM +0200, MichaIng wrote: > we face the same issue whenever a ready-to-run image has been created and > booted from a different device. > > From what we found, the Debian installer (or the grub install/config > scripts) stores the hardware ID of the drive to debconf database, if one is > available. Of course on a different machine this identifier and the related > /dev/disk/by-id/ path is invalid. On VirtualBox and non-virtual PCs this is > usually the case, on VMware on the other hand, ho hardware identifier > exists, hence /dev/sda is stored there which is still valid when importing > the same image to other VMware machines. Indeed. > I suggest to do the grub target check on `preinst` and skip/fail with error > code if the debconf entry is invalid. It is better to skip or break the > package upgrade and force admins to check/run manually then letting them > running into a unbootable system. That's fairly close to one of my suggestions in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966575#102. It's not necessary to move things to the preinst to make this work; it just needs to be checked a bit more thoroughly before the postinst runs grub-install. > Otherwise elegant would be a scan to find the matching grub instance, but > not sure how easy this is. At least the bootloader locations are fixed? In principle it's impossible. In practice it may be possible to do some degree of guesswork; that's one of my other suggestions in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966575#102. :-) We do have to be pretty conservative though, as going overboard is likely to break some multiboot setups. -- Colin Watson (he/him) [cjwat...@debian.org]
Processed: Re: Bug#966575: same error message here
Processing control commands: > severity -1 grave Bug #966575 [grub-pc] grub-pc: error: symbol `grub_calloc' not found. Severity set to 'grave' from 'important' -- 966575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957282: marked as done (gnarwl: ftbfs with GCC-10)
Your message dated Fri, 31 Jul 2020 23:03:37 +
with message-id
and subject line Bug#957282: fixed in gnarwl 3.6.dfsg-13
has caused the Debian Bug report #957282,
regarding gnarwl: ftbfs with GCC-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.)
--
957282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:gnarwl
Version: 3.6.dfsg-12
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/gnarwl_3.6.dfsg-12_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html
[...]
Command: dpkg-buildpackage -us -uc -b -rfakeroot
dpkg-buildpackage: info: source package gnarwl
dpkg-buildpackage: info: source version 3.6.dfsg-12
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by Bernhard Schmidt
dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
fakeroot debian/rules clean
dh clean #--without autoreconf
dh_clean
debian/rules build
dh build #--without autoreconf
dh_update_autotools_config
dh_autoreconf
debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
dh_auto_configure -- \
--with-docdir=/usr/share/doc/gnarwl \
--with-homedir=/var/lib/gnarwl
./configure --build=x86_64-linux-gnu --prefix=/usr
--includedir=\${prefix}/include --mandir=\${prefix}/share/man
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu
--runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking
--with-docdir=/usr/share/doc/gnarwl --with-homedir=/var/lib/gnarwl
configure: WARNING: unrecognized options: --disable-silent-rules,
--disable-maintainer-mode, --disable-dependency-tracking
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for gdbm_open in -lgdbm... yes
checking for ldap_init in -lldap... yes
checking for ldap_set_option... yes
checking for iconv... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating conf.h
configure: WARNING: unrecognized options: --disable-silent-rules,
--disable-maintainer-mode, --disable-dependency-tracking
make[1]: Leaving directory '/<>'
debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
make CFLAGS="-g -O2 -fdebug-prefix-map=/<>=.
-fstack-protector-strong -Wformat -Werror=format-security -I.."
make[2]: Entering directory '/<>'
make -C src all
make[3]: Entering directory '/<>/src'
rm -f DEADJOE *.o *~ gnarwl damnit
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
config.o config.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
dbaccess.o dbaccess.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -c -o
util.o util.c
gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong
-Wformat -Werror=format-security -I.. -Wdate-time -D
Bug#957403: kexec-tools: diff for NMU version 1:2.0.20-2.1
On 7/31/20 12:03 PM, casca...@debian.org wrote: > Control: tags 957403 + patch > > > Dear maintainer, > > I've prepared an NMU for kexec-tools (versioned as 1:2.0.20-2.1). The diff > is attached to this message. > > Regards. > Thanks! I appreciate it. -- Khalid
Bug#966575: same error message here
Control: severity -1 important On Fri, Jul 31, 2020 at 10:39:22PM +0200, cacat...@tuxfamily.org wrote: > Don't know if it's useful but contributing infos I collected on this, > since I ran into the same error message on a Lenovo Thinkpad T510 > running Debian Stable. For anyone affected by this bug, the workaround is to run "dpkg-reconfigure grub-pc" as root and follow the instructions in the "GRUB install devices" question. If your system has already failed to boot, you can use a rescue image of some kind to get back in: for example, the Debian installer's rescue mode should be suitable. This is a long-standing problem: we get a scattering of reports of the same general kind with every GRUB upgrade that changes the binary interface between GRUB's core image and modules in some way, although the exact details depend on the upgrade in question. The situation certainly needs to be improved. However, the problem is not with the actual changes made in this version of GRUB. Rather, it's a latent configuration problem on your system (and on the systems of other people affected by this) that is triggered by the act of making *any* change to GRUB that causes new modules in /boot/grub not to be compatible with old core images in the boot sector that your firmware jumps to when booting your machine. This problem happens on systems that are configured to run grub-install to a target device that is not actually the one that your firmware uses to boot your computer. This configuration error is normally the result of something like changing disks around without telling the GRUB packaging about it, so it continues to install to an old device without realising it isn't the one that your firmware is configured to boot from any more. Sometimes it's the result of a bug in some kind of installation or cloning process instead. Unfortunately it is rarely possible to tell exactly what caused it from any information that still exists on the systems in question; sometimes the affected users have an idea what might have happened and sometimes they don't. The packaging tries to detect some problems along these lines - I did considerable work on this way back in 2010 to try to improve the situation - and the volume of reports of this kind is much lower than it used to be as a result, but it still happens sometimes. I'm going to downgrade this to non-release-critical. It is absolutely a problem that we need to deal with (somehow ... it may be that in some cases we need to refuse to continue the upgrade instead, which would be a different kind of bug that would tend to be filed as release-critical too!), but given that it's a latent problem that would have been exposed by any change of a similar magnitude, I don't think it makes sense for it to block migration of this new version to testing. -- Colin Watson (he/him) [cjwat...@debian.org]
Processed: Re: Bug#966575: same error message here
Processing control commands: > severity -1 important Bug #966575 [grub-pc] grub-pc: error: symbol `grub_calloc' not found. Severity set to 'important' from 'grave' -- 966575: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966575 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957614: nut: ftbfs with GCC-10
Hi, I submitted a merge request updating the symbols file which will fix the FTBFS with GCC-10: https://salsa.debian.org/debian/nut/-/merge_requests/2 Thanks for considering the patch. -- Lucas Kanashiro
Bug#966575: grub-pc: error: symbol `grub_calloc' not found.
This bug appears to affect a standard Vagrant install of Debian Buster as well. After booting, upgrading, and rebooting, I'm faced with the error. The Vagrant base box is a fairly common one: https://app.vagrantup.com/bento/boxes/debian-10 I'm guessing this is a fairly standard disk layout in their build: # fdisk -l Disk /dev/sda: 64 GiB, 68719476736 bytes, 134217728 sectors Disk model: VBOX HARDDISK Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x1b8eb89d Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048499711497664 243M 83 Linux /dev/sda2 501758 134215679 133713922 63.8G 5 Extended /dev/sda5 501760 134215679 133713920 63.8G 8e Linux LVM Disk /dev/mapper/debian--10--vg-root: 62.8 GiB, 67385688064 bytes, 131612672 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/debian--10--vg-swap_1: 1 GiB, 1073741824 bytes, 2097152 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes I'm using the (admittedly insecure) solution of "sudo apt-mark hold grub*" shown here: https://askubuntu.com/a/1263204 Chad
Bug#966575: same error message here
Package: grub-pc
Version: 2.02+dfsg1-20+deb10u2
Dear Maintainers,
Don't know if it's useful but contributing infos I collected on this,
since I ran into the same error message on a Lenovo Thinkpad T510
running Debian Stable.
Some specifics are :
- I use unattended-upgrades, so it might be I missed something
- Install was made with no root password set, but I set one recently.
- It has a LUKS partition but it's secondary and not a system mount
point.
- It runs a kernel from the backports.
What happened :
Start-Date: 2020-07-30 09:09:13
Commandline: /usr/bin/unattended-upgrade
Upgrade: grub-common:amd64 (2.02+dfsg1-20, 2.02+dfsg1-20+deb10u1),
grub2-common:amd64 (2.02+dfsg1-20, 2.02+dfsg1-20+deb10u1), grub-pc:amd64
(2.02+dfsg1-20, 2.02+dfsg1-20+deb10u1), grub-pc-bin:amd64
(2.02+dfsg1-20, 2.02+dfsg1-20+deb10u1)
End-Date: 2020-07-30 09:09:25
Start-Date: 2020-07-30 09:09:27
Commandline: /usr/bin/unattended-upgrade
Upgrade: firefox-esr-l10n-fr:amd64 (68.10.0esr-1~deb10u1,
68.11.0esr-1~deb10u1), firefox-esr:amd64 (68.10.0esr-1~deb10u1,
68.11.0esr-1~deb10u1)
End-Date: 2020-07-30 09:09:38
Start-Date: 2020-07-31 10:41:26
Commandline: /usr/bin/unattended-upgrade
Upgrade: grub-common:amd64 (2.02+dfsg1-20+deb10u1,
2.02+dfsg1-20+deb10u2), grub2-common:amd64 (2.02+dfsg1-20+deb10u1,
2.02+dfsg1-20+deb10u2), grub-pc:amd64 (2.02+dfsg1-20+deb10u1,
2.02+dfsg1-20+deb10u2), grub-pc-bin:amd64 (2.02+dfsg1-20+deb10u1,
2.02+dfsg1-20+deb10u2)
End-Date: 2020-07-31 10:41:36
Reboot on 2020-07-31 @ 22:00:00, then same error message than OP.
Fixed situation by rebooting on a USB key with Debian installer, rescue
mode, reinstalling grub on /dev/sda.
More system infos in attachment.
-- Package-specific info:
*** BEGIN /proc/mounts
/dev/sda1 / ext4 rw,relatime,errors=remount-ro 0 0
/dev/sda8 /mnt/debiantesting ext4 rw,relatime 0 0
/dev/sda6 /home ext4 rw,relatime 0 0
*** END /proc/mounts
*** BEGIN /boot/grub/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1
ad4ff815-580a-4bad-965f-c66dbd806733
else
search --no-floppy --fs-uuid --set=root ad4ff815-580a-4bad-965f-c66dbd806733
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=fr_FR
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=1
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=1
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1
--hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1
ad4ff815-580a-4bad-965f-c66dbd806733
else
search --no-floppy --fs-uuid --set=root ad4ff815-580a-4bad-965f-c66dbd806733
fi
insmod png
if background_image
/usr/share/desktop-base/futureprototype-theme/grub/grub-4x3.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu
--class os $menuentry_id_option
'gnulinux-simple-ad4ff815-580a-4bad-965f-c66dbd806733' {
load_video
insmod
Bug#966638: gkrellm-cpufreq: Error: /usr/lib/gkrellm2/plugins/cpufreq.so: undefined symbol: cpufreq_cpu_exists
Package: gkrellm-cpufreq Version: 0.6.4-6+b1 Severity: grave Justification: plugin cannot be loaded into gkrellm anymore gkrellm-cpufreq no longer works. The plugin install log says: | Error: /usr/lib/gkrellm2/plugins/cpufreq.so: undefined symbol: cpufreq_cpu_exists Downgrading to 0.6.4-4+b2 makes the plugin work again. I haven't tested any other versions in between. I think libcpufreq0 -> libcpupower1 conversion went wrong here. Helmut
Processed: bug 939658 is forwarded to https://github.com/kliment/Printrun/pull/1048
Processing commands for cont...@bugs.debian.org: > forwarded 939658 https://github.com/kliment/Printrun/pull/1048 Bug #939658 [src:printrun] printrun: Incomplete debian/copyright? Set Bug forwarded-to-address to 'https://github.com/kliment/Printrun/pull/1048'. > thanks Stopping processing here. Please contact me if you need assistance. -- 939658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939658 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964915: Raspi 4 debian image update-initramfs
OK thanks lucas and Gunnar. Sorry for any inconvenience that I does not found this bugreport. Have a nice weekend. Am 31.07.20 um 18:09 schrieb Gunnar Wolf: > [ Adding a Cc: to #964915 ] Lucas Nussbaum dijo [Fri, Jul 31, 2020 at > 02:15:29PM +0200]: >> Hi, Can you confirm that it's not >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964915 > Yes, that's precisely the culprit. Even more - Both basti and me > didn't find it any further because (I guess) we both booted with the > HDMI console. When using a serial console, I found the all too > familiar: Begin: Running /scripts/local-block ... done. Begin: Running > /scripts/local-block ... done. Begin: Running /scripts/local-block ... > done. And of course, after a couple iterations, I got dumped to the > very useful busybox: Begin: Running /scripts/local-block ... done. > Begin: Running /scripts/local-block ... done. done. Gave up waiting > for root file system device. Common problems: - Boot args (cat > /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - > Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/mmcblk0p2 > does not exist. Dropping to a shell! BusyBox v1.30.1 (Debian > 1:1.30.1-4) built-in shell (ash) Enter 'help' for a list of built-in > commands. (initramfs) So, Basti: 1. Try editing cmdline.txt in your > first partition, replacing «/dev/mmcblk0p2» by «LABEL=RASPIROOT» as > the bug report suggests 2. If you don't use a serial console, consider > removing the «console=ttyS1,115200» part, so that the main information > is sent to the HDMI output. Or even better, swap the order, so that > the serial console functionality is preserved, but the main console is > HDMI. So, we should definitively address item 1, as it is a serious > bug (and I'm bumping up severity - It will affect all Raspberry > models, not just the 4). As for 2... well, we can document it and > maybe add some black magic to the initrd generation to allow the user > to specify what the default console should be. But as the preferences > are completely depending on the user and there is no "righter" > value... And, following Lucas' report -- I think his last point > actually makes a lot of sense: 1) setting ROOTPART=`findmnt -n > --output=source /boot/firmware/`, 2) or using the label and doing > ROOTPART=`findmnt -n --output=source /boot/firmware/`; > ROOTLABEL="`lsblk -no label $ROOTPART`", and when overwriting > cmdline.txt using "root=LABEL=$ROOTLABEL", 3) or my personal favorite > - not touching cmdline.txt at all. I don't really see the point of > modifying it during postinst of a kernel package, unless the > pre_cmdline stuff needs to modify console boot settings for some > reason. So that's surely an issue to look into ASAP! (and yes, the bug > is not getting any younger :-| )
Bug#957466: marked as done (libpolyclipping: ftbfs with GCC-10)
Your message dated Fri, 31 Jul 2020 19:18:57 + with message-id and subject line Bug#957466: fixed in libpolyclipping 6.4.2-7 has caused the Debian Bug report #957466, regarding libpolyclipping: ftbfs with GCC-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.) -- 957466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libpolyclipping Version: 6.4.2-6 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/libpolyclipping_6.4.2-6_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] (c++)"std::__cxx11::list >::merge(std::__cxx11::list >&&)@Base" 6.4.2 (c++)"std::__cxx11::list >::sort()@Base" 6.4.2 - (c++|optional)"std::vector >::reserve(unsigned int)@Base" 6.4.2-4~ - (c++|optional)"std::vector >::_M_default_append(unsigned int)@Base" 6.4.2-4~ +#MISSING: 6.4.2-6# (c++|optional)"std::vector >::reserve(unsigned int)@Base" 6.4.2-4~ +#MISSING: 6.4.2-6# (c++|optional)"std::vector >::_M_default_append(unsigned int)@Base" 6.4.2-4~ (c++|optional)"std::vector >::_M_default_append(unsigned long)@Base" 6.4.2 - (c++)"std::vector >::operator=(std::vector > const&)@Base" 6.4.2 - (c++|optional)"std::vector >::reserve(unsigned int)@Base" 6.4.2-4~ +#MISSING: 6.4.2-6# (c++)"std::vector >::operator=(std::vector > const&)@Base" 6.4.2 +#MISSING: 6.4.2-6# (c++|optional)"std::vector >::reserve(unsigned int)@Base" 6.4.2-4~ (c++|optional)"std::vector >::reserve(unsigned long)@Base" 6.4.2 - (c++|optional)"std::vector >::_M_default_append(unsigned int)@Base" 6.4.2-4~ +#MISSING: 6.4.2-6# (c++|optional)"std::vector >::_M_default_append(unsigned int)@Base" 6.4.2-4~ (c++|optional)"std::vector >::_M_default_append(unsigned long)@Base" 6.4.2 - (c++|optional)"std::vector >::_M_default_append(unsigned int)@Base" 6.4.2-4~ +#MISSING: 6.4.2-6# (c++|optional)"std::vector >::_M_default_append(unsigned int)@Base" 6.4.2-4~ (c++|optional)"std::vector >::_M_default_append(unsigned long)@Base" 6.4.2 - (c++|optional)"std::vector >::reserve(unsigned int)@Base" 6.4.2-4~ +#MISSING: 6.4.2-6# (c++|optional)"std::vector >::reserve(unsigned int)@Base" 6.4.2-4~ (c++|optional)"std::vector >::reserve(unsigned long)@Base" 6.4.2 - (c++|optional)"std::vector >, std::allocator > > >::_M_default_append(unsigned int)@Base" 6.4.2-4~ +#MISSING: 6.4.2-6# (c++|optional)"std::vector >, std::allocator > > >::_M_default_append(unsigned int)@Base" 6.4.2-4~ (c++|optional)"std::vector >, std::allocator > > >::_M_default_append(unsigned long)@Base" 6.4.2 - (c++|optional)"std::vector >, std::allocator > > >::reserve(unsigned int)@Base" 6.4.2-4~ +#MISSING: 6.4.2-6# (c++|optional)"std::vector >, std::allocator > > >::reserve(unsigned int)@Base" 6.4.2-4~ (c++|optional)"std::vector >, std::allocator > > >::reserve(unsigned long)@Base" 6.4.2 (c++)"std::vector >, std::allocator > > >::~vector()@Base" 6.4.2 (c++)"typeinfo for ClipperLib::Clipper@Base" 6.4.2 @@ -188,24 +192,24 @@ (c++)"typeinfo name for ClipperLib::PolyNode@Base" 6.4.2 (c++)"typeinfo name for ClipperLib::clipperException@Base" 6.4.2 (c++)"virtual thunk to ClipperLib::Clipper::~Clipper()@Base" 6.4.2 - (c++|optional)"void std::__adjust_heap<__gnu_cxx::__normal_iterator > >, int, ClipperLib::IntersectNode*, __gnu_cxx::__ops::_Iter_comp_iter >(__gnu_cxx::__normal_iterator > >, int, int, ClipperLib::IntersectNode*, __gnu_cxx::__ops::_Iter_comp_iter)@Base" 6.4.2-4~ +#MISSING: 6.4.
Processed: Bug#957466 marked as pending in libpolyclipping
Processing control commands: > tag -1 pending Bug #957466 [src:libpolyclipping] libpolyclipping: ftbfs with GCC-10 Added tag(s) pending. -- 957466: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957466 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957466: marked as pending in libpolyclipping
Control: tag -1 pending Hello, Bug #957466 in libpolyclipping 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/3dprinting-team/libpolyclipping/-/commit/d18e1f32a5f06503fc342a7942de5ec4c0368bec Remove symbols file It costs much more to maintain than it gains in practice. Fixes build failure with GCC 10. (Closes: #957466) (this message was generated automatically) -- Greetings https://bugs.debian.org/957466
Bug#957403: marked as done (kexec-tools: ftbfs with GCC-10)
Your message dated Fri, 31 Jul 2020 18:19:25 + with message-id and subject line Bug#957403: fixed in kexec-tools 1:2.0.20-2.1 has caused the Debian Bug report #957403, regarding kexec-tools: ftbfs with GCC-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.) -- 957403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:kexec-tools Version: 1:2.0.20-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/kexec-tools_2.0.20-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] gcc -fno-zero-initialized-in-bss -mcmodel=large -Os -fno-builtin -ffreestanding -fno-zero-initialized-in-bss -fno-PIC -fno-PIE -fno-stack-protector -mcmodel=large -I./purgatory/include -I./purgatory/arch/x86_64/include -I./util_lib/include -I./include -Iinclude -I/usr/lib/gcc/x86_64-linux-gnu/10/include -c -MD -o purgatory/string.o purgatory/string.c gcc -mcmodel=large -I./purgatory/include -I./purgatory/arch/x86_64/include -I./util_lib/include -I./include -Iinclude -I/usr/lib/gcc/x86_64-linux-gnu/10/include -c -MD -o purgatory/arch/x86_64/entry64-32.o purgatory/arch/x86_64/entry64-32.S gcc -mcmodel=large -I./purgatory/include -I./purgatory/arch/x86_64/include -I./util_lib/include -I./include -Iinclude -I/usr/lib/gcc/x86_64-linux-gnu/10/include -c -MD -o purgatory/arch/x86_64/entry64.o purgatory/arch/x86_64/entry64.S gcc -mcmodel=large -I./purgatory/include -I./purgatory/arch/x86_64/include -I./util_lib/include -I./include -Iinclude -I/usr/lib/gcc/x86_64-linux-gnu/10/include -c -MD -o purgatory/arch/x86_64/setup-x86_64.o purgatory/arch/x86_64/setup-x86_64.S gcc -mcmodel=large -I./purgatory/include -I./purgatory/arch/x86_64/include -I./util_lib/include -I./include -Iinclude -I/usr/lib/gcc/x86_64-linux-gnu/10/include -c -MD -o purgatory/arch/x86_64/stack.o purgatory/arch/x86_64/stack.S gcc -fno-zero-initialized-in-bss -mcmodel=large -Os -fno-builtin -ffreestanding -fno-zero-initialized-in-bss -fno-PIC -fno-PIE -fno-stack-protector -mcmodel=large -I./purgatory/include -I./purgatory/arch/x86_64/include -I./util_lib/include -I./include -Iinclude -I/usr/lib/gcc/x86_64-linux-gnu/10/include -c -MD -o purgatory/arch/x86_64/purgatory-x86_64.o purgatory/arch/x86_64/purgatory-x86_64.c gcc -mcmodel=large -I./purgatory/include -I./purgatory/arch/x86_64/include -I./util_lib/include -I./include -Iinclude -I/usr/lib/gcc/x86_64-linux-gnu/10/include -c -MD -o purgatory/arch/i386/entry32-16.o purgatory/arch/i386/entry32-16.S gcc -mcmodel=large -I./purgatory/include -I./purgatory/arch/x86_64/include -I./util_lib/include -I./include -Iinclude -I/usr/lib/gcc/x86_64-linux-gnu/10/include -c -MD -o purgatory/arch/i386/entry32-16-debug.o purgatory/arch/i386/entry32-16-debug.S gcc -fno-zero-initialized-in-bss -mcmodel=large -Os -fno-builtin -ffreestanding -fno-zero-initialized-in-bss -fno-PIC -fno-PIE -fno-stack-protector -mcmodel=large -I./purgatory/include -I./purgatory/arch/x86_64/include -I./util_lib/include -I./include -Iinclude -I/usr/lib/gcc/x86_64-linux-gnu/10/include -c -MD -o purgatory/arch/i386/crashdump_backup.o purgatory/arch/i386/crashdump_backup.c gcc -fno-zero-initialized-in-bss -mcmodel=large -Os -fno-builtin -ffreestanding -fno-zero-initialized-in-bss -fno-PIC -fno-PIE -fno-stack-protector -mcmodel=large -I./purgatory/include -I./purgatory/arch/x86_64/include -I./util_lib/include -I./include -Iinclude -
Bug#957403: kexec-tools: diff for NMU version 1:2.0.20-2.1
Control: tags 957403 + patch
Dear maintainer,
I've prepared an NMU for kexec-tools (versioned as 1:2.0.20-2.1). The diff
is attached to this message.
Regards.
diff -Nru kexec-tools-2.0.20/debian/changelog kexec-tools-2.0.20/debian/changelog
--- kexec-tools-2.0.20/debian/changelog 2020-03-12 16:31:02.0 -0300
+++ kexec-tools-2.0.20/debian/changelog 2020-07-31 14:27:55.0 -0300
@@ -1,3 +1,10 @@
+kexec-tools (1:2.0.20-2.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix build with GCC 10 (Closes: #957403)
+
+ -- Thadeu Lima de Souza Cascardo Fri, 31 Jul 2020 14:27:55 -0300
+
kexec-tools (1:2.0.20-2) unstable; urgency=medium
* Fix FTBFS issue on x86 (Closes: #942617)
diff -Nru kexec-tools-2.0.20/debian/patches/kexec-tools-remove-duplicated-variable-d.patch kexec-tools-2.0.20/debian/patches/kexec-tools-remove-duplicated-variable-d.patch
--- kexec-tools-2.0.20/debian/patches/kexec-tools-remove-duplicated-variable-d.patch 1969-12-31 21:00:00.0 -0300
+++ kexec-tools-2.0.20/debian/patches/kexec-tools-remove-duplicated-variable-d.patch 2020-07-31 14:27:36.0 -0300
@@ -0,0 +1,86 @@
+From: Kairui Song
+Date: Wed, 29 Jan 2020 13:38:19 +0800
+X-Dgit-Generated: 1:2.0.20-2.1 2bf3cc958fc767a2868b5766a3b6ac73da019ef3
+Subject: kexec-tools: Remove duplicated variable declarations
+
+When building kexec-tools for Fedora 32, following error is observed:
+
+/usr/bin/ld: kexec/arch/x86_64/kexec-bzImage64.o:(.bss+0x0): multiple definition of `bzImage_support_efi_boot';
+kexec/arch/i386/kexec-bzImage.o:(.bss+0x0): first defined here
+
+/builddir/build/BUILD/kexec-tools-2.0.20/kexec/arch/arm/../../fs2dt.h:33: multiple definition of `my_debug';
+kexec/fs2dt.o:/builddir/build/BUILD/kexec-tools-2.0.20/kexec/fs2dt.h:33: first defined here
+
+/builddir/build/BUILD/kexec-tools-2.0.20/kexec/arch/arm64/kexec-arm64.h:68: multiple definition of `arm64_mem';
+kexec/fs2dt.o:/builddir/build/BUILD/kexec-tools-2.0.20/././kexec/arch/arm64/kexec-arm64.h:68: first defined here
+
+/builddir/build/BUILD/kexec-tools-2.0.20/kexec/arch/arm64/kexec-arm64.h:54: multiple definition of `initrd_size';
+kexec/fs2dt.o:/builddir/build/BUILD/kexec-tools-2.0.20/././kexec/arch/arm64/kexec-arm64.h:54: first defined here
+
+/builddir/build/BUILD/kexec-tools-2.0.20/kexec/arch/arm64/kexec-arm64.h:53: multiple definition of `initrd_base';
+kexec/fs2dt.o:/builddir/build/BUILD/kexec-tools-2.0.20/././kexec/arch/arm64/kexec-arm64.h:53: first defined here
+
+And apparently, these variables are wrongly declared multiple times. So
+remove duplicated declaration.
+
+Signed-off-by: Kairui Song
+Signed-off-by: Simon Horman
+(cherry picked from commit cc087b11462af9f971a2c090d07e8d780a867b50)
+Signed-off-by: Thadeu Lima de Souza Cascardo
+
+---
+
+--- kexec-tools-2.0.20.orig/kexec/arch/arm64/kexec-arm64.h
kexec-tools-2.0.20/kexec/arch/arm64/kexec-arm64.h
+@@ -50,8 +50,8 @@ int zImage_arm64_load(int argc, char **a
+ void zImage_arm64_usage(void);
+
+
+-off_t initrd_base;
+-off_t initrd_size;
++extern off_t initrd_base;
++extern off_t initrd_size;
+
+ /**
+ * struct arm64_mem - Memory layout info.
+@@ -65,7 +65,7 @@ struct arm64_mem {
+ };
+
+ #define arm64_mem_ngv UINT64_MAX
+-struct arm64_mem arm64_mem;
++extern struct arm64_mem arm64_mem;
+
+ uint64_t get_phys_offset(void);
+ uint64_t get_vp_offset(void);
+--- kexec-tools-2.0.20.orig/kexec/arch/ppc64/kexec-elf-ppc64.c
kexec-tools-2.0.20/kexec/arch/ppc64/kexec-elf-ppc64.c
+@@ -44,8 +44,6 @@
+ uint64_t initrd_base, initrd_size;
+ unsigned char reuse_initrd = 0;
+ const char *ramdisk;
+-/* Used for enabling printing message from purgatory code */
+-int my_debug = 0;
+
+ int elf_ppc64_probe(const char *buf, off_t len)
+ {
+--- kexec-tools-2.0.20.orig/kexec/arch/x86_64/kexec-bzImage64.c
kexec-tools-2.0.20/kexec/arch/x86_64/kexec-bzImage64.c
+@@ -42,7 +42,6 @@
+ #include
+
+ static const int probe_debug = 0;
+-int bzImage_support_efi_boot;
+
+ int bzImage64_probe(const char *buf, off_t len)
+ {
+--- kexec-tools-2.0.20.orig/kexec/fs2dt.h
kexec-tools-2.0.20/kexec/fs2dt.h
+@@ -30,7 +30,7 @@ extern struct bootblock bb[1];
+
+ /* Used for enabling printing message from purgatory code
+ * Only has implemented for PPC64 */
+-int my_debug;
++extern int my_debug;
+ extern int dt_no_old_root;
+
+ void reserve(unsigned long long where, unsigned long long length);
diff -Nru kexec-tools-2.0.20/debian/patches/series kexec-tools-2.0.20/debian/patches/series
--- kexec-tools-2.0.20/debian/patches/series 2020-03-12 16:31:02.0 -0300
+++ kexec-tools-2.0.20/debian/patches/series 2020-07-31 14:27:36.0 -0300
@@ -6,3 +6,4 @@
linker-option.patch
powerpcspe_support.patch
ftbfs-i386.patch
+kexec-tools-remove-duplicated-variable-d.patch
signature.asc
Description: PGP signature
Processed: kexec-tools: diff for NMU version 1:2.0.20-2.1
Processing control commands: > tags 957403 + patch Bug #957403 [src:kexec-tools] kexec-tools: ftbfs with GCC-10 Added tag(s) patch. -- 957403: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957403 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966417: marked as done (vg: FTBFS in sid, with new elfutils)
Your message dated Fri, 31 Jul 2020 17:50:24 + with message-id and subject line Bug#966417: fixed in vg 1.25.0+ds-3 has caused the Debian Bug report #966417, regarding vg: FTBFS in sid, with new elfutils 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.) -- 966417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vg Version: 1.25.0+ds-2 Severity: serious Hello, looks like elfutils dropped one library used by vg: # We do not provide a libebl anymore, use libdw instead. rm -f debian/tmp/usr/include/elfutils/libebl.h causing now FTBFS in sid: . ./source_me.sh && g++ -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,-z,now -I/usr/include/fastahack -I/<>/vg-1.25.0+ds/include -I. -I/<>/vg-1.25.0+ds/src -I/<>/vg-1.25.0+ds/src/unittest -I/<>/vg-1.25.0+ds/src/subcommand -I/<>/vg-1.25.0+ds/include/dynamic -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/smithwaterman -I/usr/include/vcflib -I/usr/include/smithwaterman -I/usr/include/fastahack -Wdate-time -D_FORTIFY_SOURCE=2 -O3 -Werror=return-type -std=c++14 -ggdb -g -MMD -MP -g -O2 -fdebug-prefix-map=/<>/vg-1.25.0+ds=. -fstack-protector-strong -Wformat -Werror=format-security -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -msse4.1 -fopenmp -o test/build_graph test/build_graph.cpp -lvg -L/<>/vg-1.25.0+ds/lib /<>/vg-1.25.0+ds/lib/libvgio.a -lz -lgssw -lssw -lprotobuf -lsublinearLS -ldeflate -lpthread -ljansson -lncurses -lgcsa2 -lgbwtgraph -lgbwt -ldivsufsort -ldivsufsort64 -lraptor2 -lpinchesandcacti -l3edgeconnected -lsonlib -lfml -llz4 -lstructures -lvw -lboost_program_options -lallreduce -lbdsg -lxg -lsdsl -lhandlegraph -lfastahack -lsmithwaterman -ldisorder -lvcflib -lsmithwaterman -ldisorder -lfastahack -lhts -ltabixpp -lcairo -ljansson -latomic -rdynamic -ldw -lelf -lebl -ldl -llzma -lrocksdb -lbz2 -ljemalloc /usr/bin/ld: cannot find -lebl I don't know if this patch is enough to make it build correctly, it is still building here diff -Nru vg-1.25.0+ds/debian/changelog vg-1.25.0+ds/debian/changelog --- vg-1.25.0+ds/debian/changelog 2020-07-14 15:15:28.0 +0200 +++ vg-1.25.0+ds/debian/changelog 2020-07-28 12:11:33.0 +0200 @@ -1,3 +1,9 @@ +vg (1.25.0+ds-2.1) unstable; urgency=medium + + * Fix build by not linking anymore libebl.a (Closes: #-1) + + -- Gianfranco Costamagna Tue, 28 Jul 2020 12:11:33 +0200 + vg (1.25.0+ds-2) unstable; urgency=medium * Restrict architectures to build for. Closes: #964039. diff -Nru vg-1.25.0+ds/debian/patches/use_packaged_elfutils vg-1.25.0+ds/debian/patches/use_packaged_elfutils --- vg-1.25.0+ds/debian/patches/use_packaged_elfutils 2020-02-03 13:26:00.0 +0100 +++ vg-1.25.0+ds/debian/patches/use_packaged_elfutils 2020-07-28 12:11:25.0 +0200 @@ -7,7 +7,7 @@ # We want to link against the elfutils libraries -LD_LIB_FLAGS += -ldwfl -ldw -ldwelf -lelf -lebl -+LD_LIB_FLAGS += -ldw -lelf -lebl ++LD_LIB_FLAGS += -ldw -lelf # We get OpenMP the normal way, using whatever the compiler knows about CXXFLAGS += -fopenmp --- End Message --- --- Begin Message --- Source: vg Source-Version: 1.25.0+ds-3 Done: cru...@debian.org (Michael R. Crusoe) We believe that the bug you reported is fixed in the latest version of vg, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated vg 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: Fri, 31 Jul 2020 15:09:46 +0200 Source: vg Architecture: source Version: 1.25.0+ds-3 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Michael R. Crusoe Closes: 966417 Changes: vg (1.25.0+ds-3) unstable; urgency=medium . [ Gianfranco Costamagna ] * Fix build by not linking anymore libebl.a (Closes: #966417) Checksums-Sha1: 51fd02ac0d134aed73bf23c72c7
Bug#957474: marked as done (libsavitar: ftbfs with GCC-10)
Your message dated Fri, 31 Jul 2020 17:34:36 + with message-id and subject line Bug#957474: fixed in libsavitar 4.6.2-1 has caused the Debian Bug report #957474, regarding libsavitar: ftbfs with GCC-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.) -- 957474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libsavitar Version: 4.4.1-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/libsavitar_4.4.1-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] chmod 0644 -- debian/.debhelper/python3-savitar/dbgsym-root/usr/lib/debug/.build-id/a7/46fcd336950e85425e3cfe7c87e202ea5f834b.debug chown 0:0 -- debian/.debhelper/python3-savitar/dbgsym-root/usr/lib/debug/.build-id/a7/46fcd336950e85425e3cfe7c87e202ea5f834b.debug strip --remove-section=.comment --remove-section=.note --strip-unneeded debian/python3-savitar/usr/lib/python3/dist-packages/Savitar.cpython-37m-x86_64-linux-gnu.so objcopy --add-gnu-debuglink debian/.debhelper/python3-savitar/dbgsym-root/usr/lib/debug/.build-id/a7/46fcd336950e85425e3cfe7c87e202ea5f834b.debug debian/python3-savitar/usr/lib/python3/dist-packages/Savitar.cpython-37m-x86_64-linux-gnu.so install -d debian/.debhelper/python3-savitar/dbgsym-root/usr/lib/debug/.build-id/71 objcopy --only-keep-debug --compress-debug-sections debian/python3-savitar/usr/lib/python3/dist-packages/Savitar.cpython-38-x86_64-linux-gnu.so debian/.debhelper/python3-savitar/dbgsym-root/usr/lib/debug/.build-id/71/e238172de1e61ce766c198d7023ddb8518a44f.debug chmod 0644 -- debian/.debhelper/python3-savitar/dbgsym-root/usr/lib/debug/.build-id/71/e238172de1e61ce766c198d7023ddb8518a44f.debug chown 0:0 -- debian/.debhelper/python3-savitar/dbgsym-root/usr/lib/debug/.build-id/71/e238172de1e61ce766c198d7023ddb8518a44f.debug strip --remove-section=.comment --remove-section=.note --strip-unneeded debian/python3-savitar/usr/lib/python3/dist-packages/Savitar.cpython-38-x86_64-linux-gnu.so objcopy --add-gnu-debuglink debian/.debhelper/python3-savitar/dbgsym-root/usr/lib/debug/.build-id/71/e238172de1e61ce766c198d7023ddb8518a44f.debug debian/python3-savitar/usr/lib/python3/dist-packages/Savitar.cpython-38-x86_64-linux-gnu.so install -d debian/.debhelper/python3-savitar/dbgsym-root/usr/share/doc ln -s python3-savitar debian/.debhelper/python3-savitar/dbgsym-root/usr/share/doc/python3-savitar-dbgsym dh_makeshlibs -O--buildsystem=pybuild rm -f debian/libsavitar0/DEBIAN/shlibs install -d debian/libsavitar0/DEBIAN echo "libSavitar 0 libsavitar0" >> debian/libsavitar0/DEBIAN/shlibs chmod 0644 -- debian/libsavitar0/DEBIAN/shlibs chown 0:0 -- debian/libsavitar0/DEBIAN/shlibs dpkg-gensymbols -plibsavitar0 -Idebian/libsavitar0.symbols -Pdebian/libsavitar0 -edebian/libsavitar0/usr/lib/x86_64-linux-gnu/libSavitar.so.0.1.1 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/libsavitar0/DEBIAN/symbols doesn't match completely debian/libsavitar0.symbols --- debian/libsavitar0.symbols (libsavitar0_4.4.1-2_amd64) +++ dpkg-gensymbolsn9rOuw 2020-02-26 12:51:16.077802737 + @@ -50,17 +50,18 @@ (c++)"
Processed: Bug#966417 marked as pending in vg
Processing control commands: > tag -1 pending Bug #966417 [src:vg] vg: FTBFS in sid, with new elfutils Added tag(s) pending. -- 966417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966417: marked as pending in vg
Control: tag -1 pending Hello, Bug #966417 in vg reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/vg/-/commit/4a9b7acd5de211bbcb52948d697fbb2617aa0381 Fix build by not linking anymore libebl.a (Closes: #966417) (this message was generated automatically) -- Greetings https://bugs.debian.org/966417
Processed: Bug#957474 marked as pending in libsavitar
Processing control commands: > tag -1 pending Bug #957474 [src:libsavitar] libsavitar: ftbfs with GCC-10 Added tag(s) pending. -- 957474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957474 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957474: marked as pending in libsavitar
Control: tag -1 pending Hello, Bug #957474 in libsavitar 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/3dprinting-team/libsavitar/-/commit/72a86dd8f6b95d975802864fbb7b48a35bd5c30f Remove symbols file. Maintaining symbols for C++ libraries requires much more effort than it helps in solving actual problems. The latest breakage was induced by GCC 10. Also, we don't have any external reverse-dependencies anyway. (Closes: #957474) (this message was generated automatically) -- Greetings https://bugs.debian.org/957474
Processed: Re: raspi-firmware: upgrading kernel or firmware causes system to become unbootable on pi 4
Processing commands for cont...@bugs.debian.org: > tags 964915 + confirmed Bug #964915 [raspi-firmware] raspi-firmware: upgrading kernel or firmware causes system to become unbootable on pi 4 (ROOTPART hardcoded to /dev/mmcblk0p2 instead of /dev/mmcblk1p2) Added tag(s) confirmed. > notfound 964915 1.20190215-1+deb10u4 Bug #964915 [raspi-firmware] raspi-firmware: upgrading kernel or firmware causes system to become unbootable on pi 4 (ROOTPART hardcoded to /dev/mmcblk0p2 instead of /dev/mmcblk1p2) There is no source info for the package 'raspi-firmware' at version '1.20190215-1+deb10u4' with architecture '' Unable to make a source version for version '1.20190215-1+deb10u4' Ignoring request to alter found versions of bug #964915 to the same values previously set > severity 964915 critical Bug #964915 [raspi-firmware] raspi-firmware: upgrading kernel or firmware causes system to become unbootable on pi 4 (ROOTPART hardcoded to /dev/mmcblk0p2 instead of /dev/mmcblk1p2) Severity set to 'critical' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 964915: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964915 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966575: I was affected as well
Yes. I used the boot-repair.iso and that did the trick. Luckily, I still had an old Chromebook which allowed me to create the USB. On Fri, Jul 31, 2020 at 6:25 AM Steve McIntyre <93...@debian.org> wrote: > Hi Norbert, > > On Thu, Jul 30, 2020 at 11:26:15PM -0700, Norbert Kiesel wrote: > >This is a laptop running Debain Unstable with 2 SSD and one spinning > disk. > >After upgrade and install, system stopped with same error message during > boot. > > > >I was able to reactivate using a live boot system. > > ACK. Same thing applies as I suggested to Paul - maybe an inconsistent > set of updates. Have you *fixed* the problem by using the live boot? > > -- > Steve McIntyre, Cambridge, UK. > st...@einval.com > There's no sensation to compare with this > Suspended animation, A state of bliss > >
Bug#966625: gabedit crashes as soon as one opens the molecular editor
Package: gabedit Version: 2.5.0-1 Severity: grave Tags: upstream Justification: renders package unusable dear maintainer, gabedit crashes, backtrace reports halting in libpangox. the problem might be related to gtkglext1, recently dropping function gdk_gl_font_use_pango_font for gl text rendering. In fact, I have recently had a working version from upstream, but I don't know when it will become official. yours Fulvio Ciriaco -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gabedit depends on: ii libc6 2.31-2 ii libcairo2 1.16.0-4 ii libgdk-pixbuf2.0-0 2.40.0+dfsg-5 ii libgl1 1.3.1-1 ii libgl2ps1.4 1.4.2+dfsg1-1 ii libglib2.0-02.64.4-1 ii libglu1-mesa [libglu1] 9.0.1-1 ii libgomp110.1.0-6 ii libgtk2.0-0 2.24.32-4 ii libgtkglext11.2.0-9 ii libpango-1.0-0 1.44.7-4 ii libpangocairo-1.0-0 1.44.7-4 ii openbabel 3.1.1+dfsg-3 Versions of packages gabedit recommends: pn mpqc Versions of packages gabedit suggests: pn a2ps ii cups-bsd [lpr] 2.3.3-1 pn ftp-ssl | ftp ii openssh-client [ssh-client] 1:8.3p1-1 -- no debconf information
Bug#966525: dmagnetic FTBFS on i386: check-sixel failed
Hello Adrian. So, I patched my package, and uploaded to mentors. I got a message with the subject "dmagnetic_0.25-1: ACCEPTED into unstable." It can be found here, https://mentors.debian.net/package/dmagnetic/ but now I am a little bit concerned about the developer information page: https://tracker.debian.org/pkg/dmagnetic it is still complaining about i386 not working. Could you have a look? Thomas On 7/30/20 4:29 PM, Adrian Bunk wrote: On Thu, Jul 30, 2020 at 03:47:49PM +0200, Thomas Dettbarn wrote: ... One last thing... Why did your patch say "ifneq... i386"? ifneq (,$(filter $(DEB_HOST_ARCH), i386)) ^ This compares the empty string with the filter result. ifeq ($(DEB_HOST_ARCH), i386) would to the same in this case. I am used to the filter way of writing it since it allows listing several architectures like ifneq (,$(filter $(DEB_HOST_ARCH), i386 mipsel hppa)) Thomas cu Adrian
Processed: tagging 961798
Processing commands for cont...@bugs.debian.org: > tags 961798 + pending Bug #961798 [src:python-pyaudio] python-pyaudio: FTBFS for doc package Bug #963321 [src:python-pyaudio] python-pyaudio: FTBFS: dh_linktree: error: link destination debian/python-pyaudio-doc/usr/share/doc/python-pyaudio-doc/docs/_static is a directory Added tag(s) pending. Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 961798: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961798 963321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963321 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966126: marked as done (gcc-doc-defaults: need to be updated for GCC 10 being the default compiler)
Your message dated Fri, 31 Jul 2020 15:33:51 + with message-id and subject line Bug#966126: fixed in gcc-doc-defaults 5:21 has caused the Debian Bug report #966126, regarding gcc-doc-defaults: need to be updated for GCC 10 being the default compiler 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.) -- 966126: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966126 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gcc-doc-defaults Version: 5:20 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, gcc-doc-defaults needs to be updated after GCC 10 was made the default compiler. It does currently FTBFS. Andreas --- End Message --- --- Begin Message --- Source: gcc-doc-defaults Source-Version: 5:21 Done: Dmitry Baryshkov We believe that the bug you reported is fixed in the latest version of gcc-doc-defaults, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dmitry Baryshkov (supplier of updated gcc-doc-defaults 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: Fri, 31 Jul 2020 13:54:18 +0300 Source: gcc-doc-defaults Architecture: source Version: 5:21 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Dmitry Baryshkov Closes: 966126 Changes: gcc-doc-defaults (5:21) unstable; urgency=medium . * Build gcc-10 docs (gnat is still using gnat-9) (Closes: #966126) * d/rules: drop remnants of gcj support * d/rules: fix override_dh_installdocs-indep target name Checksums-Sha1: 2f634a8bfe40b64810331abf0fe09caa11a9bb5a 2262 gcc-doc-defaults_21.dsc f64d2bbe4cac634c199cced0bffacc220ffd7084 31500 gcc-doc-defaults_21.tar.xz 8f873b6c4d1162928d0197d133283e99ff5dc139 5770 gcc-doc-defaults_21_source.buildinfo Checksums-Sha256: 435cc93674e72f56f1f5360a95da84d878e68cec7dd13127cc253416d2e1f8db 2262 gcc-doc-defaults_21.dsc f8a8594125d49c3e8d4e8fab21a907ca004666e608da5862a35eb5e612c12f13 31500 gcc-doc-defaults_21.tar.xz 0a7454aaac9aa25a598fda2022431d80dfe09ae5651bee4df61da1d2f7bfa847 5770 gcc-doc-defaults_21_source.buildinfo Files: c45b5a26df26f158fcd53f2d56d26aee 2262 contrib/doc optional gcc-doc-defaults_21.dsc fb71433da24a364310623202436f6fd5 31500 contrib/doc optional gcc-doc-defaults_21.tar.xz af85e9ac4e3a7f43c2eaca1f93d0641a 5770 contrib/doc optional gcc-doc-defaults_21_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl8kNZEACgkQweDZLphv fH4fthAAzUMqRkgMLEag8REhsQOcUSQzl3z4x+K/L5r5tKBxKBxjUkaFbKw63uXI /9GQZ4gGPwf/21zBLYvYJII8PZQiABmfH5GaBFujhDSLidhldkuJZMqEQaRilL2Z nFlERjZJVO48Pj19lfk5Uv5EznqsWAlCu7S0AsqRcHiuzs0F1OoN+i5e1pJ3NFiC ilkAxFbyLNni8MpJkW0RxZNLtoNaCa5LQ2OrKqg2PmMwbteuk0VndgspzDAG7dwC eK0KtV/BCgS6cMl+kvRGGZ6vGTd9JEEyhImZx4kQwgerUQsE4vCPSIvJqwRwkEFw FviTOlQk5xllgTLx9uaSJGQI7+4wmV40nan+UOpKCksV1sTXGo84s/Ui3b7/i7e/ G2GxqxLehvaftTB/EFP0S/IuIQ0H9IZEl2mwmisn0vrUvhvGJUsGp20bgfSjngyF 3x+CcpyYvbopE83IHq7H+AJIa0KCbNeyhc/sZLyttztefxdGLT9s5k7A9IMLd6nz lgABZQ6GlGqL8SI5rIkDa08Wv42nAzbHsdUUbGZCaGpxpm/A0NDuRE/WBag3TM58 7avVyg7P4MoeakdB2ysAjZfiW+dvy4W96dg8YSu8cTXXp7joxF8AkpvkRZq80lHb ORpkgeAbFAoX4+SY8sDs/+/i1sYPS+SkrfYJJBfgfvKLoJSqnmA= =DP1r -END PGP SIGNATURE End Message ---
Processed: tagging 966602
Processing commands for cont...@bugs.debian.org: > tags 966602 + ftbfs Bug #966602 [src:libu2f-host] libu2f-host: patch for newer json-c Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 966602: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 966594
Processing commands for cont...@bugs.debian.org: > tags 966594 + ftbfs Bug #966594 [src:rt-app] rt-app: patch for newer json-c Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 966594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 950404
Processing commands for cont...@bugs.debian.org: > tags 950404 + ftbfs Bug #950404 [src:ndpi] ndpi FTBFS on arm64, i386, ppc64el and s390x due to test failures Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 950404: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950404 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: affects 966131
Processing commands for cont...@bugs.debian.org: > affects 966131 src:syslog-ng Bug #966131 [pylint] pylint: Requires old python3-isort (<<5) which won't be available in Debian Added indication that 966131 affects src:syslog-ng > thanks Stopping processing here. Please contact me if you need assistance. -- 966131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 966131
Processing commands for cont...@bugs.debian.org: > tags 966131 + ftbfs Bug #966131 [pylint] pylint: Requires old python3-isort (<<5) which won't be available in Debian Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 966131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 966600
Processing commands for cont...@bugs.debian.org: > tags 966600 + ftbfs Bug #966600 [src:nfstrace] nfstrace: patch for newer json-c/gcc-10 Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 966600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 966604
Processing commands for cont...@bugs.debian.org: > tags 966604 + ftbfs Bug #966604 [src:libu2f-server] libu2f-server: patch for newer json-c Added tag(s) ftbfs. > thanks Stopping processing here. Please contact me if you need assistance. -- 966604: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966604 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957778: marked as done (scamp: ftbfs with GCC-10)
Your message dated Fri, 31 Jul 2020 14:56:19 + with message-id and subject line Bug#957778: fixed in scamp 2.9.2-2 has caused the Debian Bug report #957778, regarding scamp: ftbfs with GCC-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.) -- 957778: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957778 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:scamp Version: 2.0.4+dfsg-1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/scamp_2.0.4+dfsg-1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] /usr/bin/ld: merge.o:./src/fits/fitscat.h:336: multiple definition of `bswapflag'; astrefcat.o:./src/fits/fitscat.h:336: first defined here /usr/bin/ld: misc.o:./src/globals.h:32: multiple definition of `gstr'; astrefcat.o:./src/globals.h:32: first defined here /usr/bin/ld: mosaic.o:./src/prefs.h:246: multiple definition of `prefs'; astrefcat.o:./src/prefs.h:246: first defined here /usr/bin/ld: mosaic.o:./src/globals.h:32: multiple definition of `gstr'; astrefcat.o:./src/globals.h:32: first defined here /usr/bin/ld: mosaic.o:./src/mosaic.c:69: multiple definition of `pthread_startgate'; astrsolve.o:./src/astrsolve.c:79: first defined here /usr/bin/ld: mosaic.o:./src/mosaic.c:72: multiple definition of `pthread_endflag'; astrsolve.o:./src/astrsolve.c:84: first defined here /usr/bin/ld: mosaic.o:./src/mosaic.c:73: multiple definition of `pthread_sindex'; astrsolve.o:./src/astrsolve.c:85: first defined here /usr/bin/ld: mosaic.o:./src/mosaic.c:72: multiple definition of `pthread_nfield'; field.o:./src/field.c:59: first defined here /usr/bin/ld: mosaic.o:./src/mosaic.c:70: multiple definition of `pthread_fields'; field.o:./src/field.c:57: first defined here /usr/bin/ld: mosaic.o:./src/mosaic.c:69: multiple definition of `pthread_stopgate'; astrsolve.o:./src/astrsolve.c:79: first defined here /usr/bin/ld: mosaic.o:./src/threads.h:132: multiple definition of `nproc'; astrsolve.o:./src/threads.h:132: first defined here /usr/bin/ld: mosaic.o:./src/mosaic.c:67: multiple definition of `thread'; astrsolve.o:./src/astrsolve.c:76: first defined here /usr/bin/ld: mosaic.o:./src/fits/fitscat.h:336: multiple definition of `bswapflag'; astrefcat.o:./src/fits/fitscat.h:336: first defined here /usr/bin/ld: photsolve.o:./src/prefs.h:246: multiple definition of `prefs'; astrefcat.o:./src/prefs.h:246: first defined here /usr/bin/ld: photsolve.o:./src/globals.h:32: multiple definition of `gstr'; astrefcat.o:./src/globals.h:32: first defined here /usr/bin/ld: photsolve.o:./src/fits/fitscat.h:336: multiple definition of `bswapflag'; astrefcat.o:./src/fits/fitscat.h:336: first defined here /usr/bin/ld: prefs.o:./src/globals.h:32: multiple definition of `gstr'; astrefcat.o:./src/globals.h:32: first defined here /usr/bin/ld: prefs.o:./src/prefs.h:246: multiple definition of `prefs'; astrefcat.o:./src/prefs.h:246: first defined here /usr/bin/ld: prefs.o:./src/fits/fitscat.h:336: multiple definition of `bswapflag'; astrefcat.o:./src/fits/fitscat.h:336: first defined here /usr/bin/ld: proper.o:./src/prefs.h:246: multiple definition of `prefs'; astrefcat.o:./src/prefs.h:246: first defined here /usr/bin/ld: proper.o:./src/globals.h:32: multiple definition of `gstr'; astrefcat.o:./src/globals.h:32: first defined here /usr/bin/ld: proper.o:./src/threads.h:132: multiple definition of `nproc'; astrsolve.o:./src/threads.h:132: first defined here /usr/bin/ld: proper.o:./src/fits/fitsc
Bug#966575: Security update can break grub - grub_calloc not found
On Fri, Jul 31, 2020 at 03:07:58PM +0100, Geoff Gibbs wrote: >On Fri, 31 Jul 2020 14:30:14 +0100 >Steve McIntyre wrote: > >> I'm guessing - do you have multiple disks on your system? If so, try >> "grub-install " on each of the bootable disks and that should >> fix your problem. > >As I mentioned, > >mount /dev/sda5 /mnt >grub-install --boot-directory=/mnt /dev/sda > >has fixed the problem for me. Yup. Sorry - I saw that. Trying to respond to lots of people atm... >fdisk -l reports :- > >Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors >Disk model: Corsair Force GS >Units: sectors of 1 * 512 = 512 bytes >Sector size (logical/physical): 512 bytes / 512 bytes >I/O size (minimum/optimal): 512 bytes / 512 bytes >Disklabel type: dos >Disk identifier: 0xc1920bad > >Device Boot Start End Sectors Size Id Type >/dev/sda1 * 2048206847204800 100M 7 HPFS/NTFS/exFAT >/dev/sda2 210942 468860927 468649986 223.5G 5 Extended >/dev/sda5 210944722943512000 250M 83 Linux >/dev/sda6 724992 468860927 468135936 223.2G 8e Linux LVM > > >Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors >Disk model: WDC WD10EZRX-00A >Units: sectors of 1 * 512 = 512 bytes >Sector size (logical/physical): 512 bytes / 4096 bytes >I/O size (minimum/optimal): 4096 bytes / 4096 bytes >Disklabel type: dos >Disk identifier: 0xc1920ba9 > >Device Boot StartEndSectors Size Id Type >/dev/sdb1 * 2048 209717247 209715200 100G 7 HPFS/NTFS/exFAT >/dev/sdb2 209721342 1953523711 1743802370 831.5G 5 Extended >/dev/sdb5 209721344 230201343 2048 9.8G 82 Linux swap / Solaris >/dev/sdb6 230203392 1953523711 1723320320 821.8G 8e Linux LVM > >Partition 2 does not start on physical sector boundary. > >And then there is a list of partitions handled by LVM (many for Xen) >but including :- > >Disk /dev/mapper/SSD0-root: 20 GiB, 21474836480 bytes, 41943040 sectors >Units: sectors of 1 * 512 = 512 bytes >Sector size (logical/physical): 512 bytes / 512 bytes >I/O size (minimum/optimal): 512 bytes / 512 bytes > >Disk /dev/mapper/HDD0-var: 9.3 GiB, 220736 bytes, 19529728 sectors >Units: sectors of 1 * 512 = 512 bytes >Sector size (logical/physical): 512 bytes / 4096 bytes >I/O size (minimum/optimal): 4096 bytes / 4096 bytes > >Disk /dev/mapper/SSD0-home: 38.6 GiB, 41473277952 bytes, 81002496 sectors >Units: sectors of 1 * 512 = 512 bytes >Sector size (logical/physical): 512 bytes / 512 bytes >I/O size (minimum/optimal): 512 bytes / 512 bytes ACK. I tend to do "fdisk -l /dev/sd?" to avoid that behaviour on my md/lvm machine here. :-) -- Steve McIntyre, Cambridge, UK.st...@einval.com You raise the blade, you make the change... You re-arrange me 'til I'm sane...
Bug#966575: Security update can break grub - grub_calloc not found
On Fri, 31 Jul 2020 14:30:14 +0100 Steve McIntyre wrote: > I'm guessing - do you have multiple disks on your system? If so, try > "grub-install " on each of the bootable disks and that should > fix your problem. As I mentioned, mount /dev/sda5 /mnt grub-install --boot-directory=/mnt /dev/sda has fixed the problem for me. fdisk -l reports :- Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors Disk model: Corsair Force GS Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc1920bad Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048206847204800 100M 7 HPFS/NTFS/exFAT /dev/sda2 210942 468860927 468649986 223.5G 5 Extended /dev/sda5 210944722943512000 250M 83 Linux /dev/sda6 724992 468860927 468135936 223.2G 8e Linux LVM Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Disk model: WDC WD10EZRX-00A Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0xc1920ba9 Device Boot StartEndSectors Size Id Type /dev/sdb1 * 2048 209717247 209715200 100G 7 HPFS/NTFS/exFAT /dev/sdb2 209721342 1953523711 1743802370 831.5G 5 Extended /dev/sdb5 209721344 230201343 2048 9.8G 82 Linux swap / Solaris /dev/sdb6 230203392 1953523711 1723320320 821.8G 8e Linux LVM Partition 2 does not start on physical sector boundary. And then there is a list of partitions handled by LVM (many for Xen) but including :- Disk /dev/mapper/SSD0-root: 20 GiB, 21474836480 bytes, 41943040 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/mapper/HDD0-var: 9.3 GiB, 220736 bytes, 19529728 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk /dev/mapper/SSD0-home: 38.6 GiB, 41473277952 bytes, 81002496 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Geoff
Bug#957140: marked as done (dlt-daemon: ftbfs with GCC-10)
Your message dated Fri, 31 Jul 2020 13:33:30 + with message-id and subject line Bug#957140: fixed in dlt-daemon 2.18.5-0.1 has caused the Debian Bug report #957140, regarding dlt-daemon: ftbfs with GCC-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.) -- 957140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:dlt-daemon Version: 2.18.4-0.1 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/dlt-daemon_2.18.4-0.1_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' cd /<>/obj-x86_64-linux-gnu && /usr/bin/cmake -E cmake_depends "Unix Makefiles" /<> /<>/src/examples /<>/obj-x86_64-linux-gnu /<>/obj-x86_64-linux-gnu/src/examples /<>/obj-x86_64-linux-gnu/src/examples/CMakeFiles/dlt-example-user-func.dir/DependInfo.cmake --color= [ 47%] Linking C executable dlt-daemon cd /<>/obj-x86_64-linux-gnu/src/daemon && /usr/bin/cmake -E cmake_link_script CMakeFiles/dlt-daemon.dir/link.txt --verbose=1 Scanning dependencies of target dlt-example-user-func make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make -f src/examples/CMakeFiles/dlt-example-user-func.dir/build.make src/examples/CMakeFiles/dlt-example-user-func.dir/build make[3]: Entering directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -rdynamic CMakeFiles/dlt-daemon.dir/dlt-daemon.c.o CMakeFiles/dlt-daemon.dir/dlt_daemon_client.c.o CMakeFiles/dlt-daemon.dir/dlt_daemon_common.c.o CMakeFiles/dlt-daemon.dir/dlt_daemon_connection.c.o CMakeFiles/dlt-daemon.dir/dlt_daemon_event_handler.c.o CMakeFiles/dlt-daemon.dir/dlt_daemon_offline_logstorage.c.o CMakeFiles/dlt-daemon.dir/dlt_daemon_serial.c.o CMakeFiles/dlt-daemon.dir/dlt_daemon_socket.c.o CMakeFiles/dlt-daemon.dir/dlt_daemon_unix_socket.c.o CMakeFiles/dlt-daemon.dir/__/gateway/dlt_gateway.c.o CMakeFiles/dlt-daemon.dir/__/lib/dlt_client.c.o CMakeFiles/dlt-daemon.dir/__/shared/dlt_common.c.o CMakeFiles/dlt-daemon.dir/__/shared/dlt_config_file_parser.c.o CMakeFiles/dlt-daemon.dir/__/shared/dlt_offline_trace.c.o CMakeFiles/dlt-daemon.dir/__/shared/dlt_protocol.c.o CMakeFiles/dlt-daemon.dir/__/shared/dlt_user_sha red.c.o CMakeFiles/dlt-daemon.dir/__/offlinelogstorage/dlt_offline_logstorage.c.o CMakeFiles/dlt-daemon.dir/__/offlinelogstorage/dlt_offline_logstorage_behavior.c.o CMakeFiles/dlt-daemon.dir/udp_connection/dlt_daemon_udp_socket.c.o CMakeFiles/dlt-daemon.dir/__/__/systemd/3rdparty/sd-daemon.c.o -o dlt-daemon -lrt -lpthread /usr/bin/ld: [ 48%] Building C object src/examples/CMakeFiles/dlt-example-user-func.dir/dlt-example-user-func.c.o CMakeFiles/dlt-daemon.dir/dlt_daemon_client.c.o:./obj-x86_64-linux-gnu/src/daemon/./src/offlinelogstorage/dlt_offline_logstorage.h:118: multiple definition of `g_logstorage_cache_size'; cd /<>/obj-x86_64-linux-gnu/src/examples && /usr/bin/cc -DCONFIGURATION_FILES_DIR=\"/etc\" -DDLT_SYSTEMD_ENABLE -DDLT_SYSTEMD_JOURNAL_ENABLE -DDLT_USER_IPC_PATH=\"/tmp\" -DDLT_USE_IPv6 -D_GNU_SOURCE -I/<> -I/<>/include/dlt -I/<>/obj-x86_64-linux-gnu/include/dlt -I/<>/src/shared -I/<>/src/core_dump_handler -I/<>/src/offlinelogstorage -I/<>/src/lib -I/<>/src/daemon -I/<>/src/console -I/<>/src/gateway -I/<>/systemd/3rdparty -g -O2 -fdebug-prefix-map=/<>=. -fstack-protect
Bug#966575: grub-pc: error: symbol `grub_calloc' not found
Hi John, On Fri, Jul 31, 2020 at 09:29:43AM +0100, John Lines wrote: >I have the same error, on a DNUK Workstar 700, dating back to 2014, so >upgraded from squeeze on up to buster.It is possible this legacy which >has resulted in something unusual in the grub configuration. > >I upgraded grub yesterday, and am working on recovering now. Posting >from another system. ACK. Same thing applies as I suggested to Paul - maybe an inconsistent set of updates. Do you have multiple disks? If so, try "grub-install " on all the bootable disks and that may fix your problem. If not, please get back to us ASAP and we'll try to debug the problem here. -- Steve McIntyre, Cambridge, UK.st...@einval.com Into the distance, a ribbon of black Stretched to the point of no turning back
Bug#966575: Security update can break grub - grub_calloc not found
Hi Geoff, On Fri, Jul 31, 2020 at 11:54:20AM +0100, Geoff Gibbs wrote: >apt update >apt full-upgrade > >grub upgrades > >from 2.02+dfsg1-20 >to 2.02+dfsg1-20+deb10u1 > >no errors were spotted. > >When rebooted :- > >symbol grub_calloc not found >Entering rescue mode >grub rescue> > > >I had to boot off a memory stick and then :- > >sudo -i >mount /dev/sda5 /mnt >grub-install --boot-directory=/mnt /dev/sda >reboot > >This worked and the system now boots. > >/boot is the only ext type file system, the others are all handled by LVM I'm guessing - do you have multiple disks on your system? If so, try "grub-install " on each of the bootable disks and that should fix your problem. I think we need a proper fix for this in the longer term, but that's not going to happen overnight. -- Steve McIntyre, Cambridge, UK.st...@einval.com You lock the door And throw away the key There's someone in my head but it's not me
Processed: Re: dlt-daemon: ftbfs with GCC-10
Processing control commands: > tags -1 patch pending Bug #957140 [src:dlt-daemon] dlt-daemon: ftbfs with GCC-10 Added tag(s) patch and pending. -- 957140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957140 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966575: I was affected as well
Hi Norbert, On Thu, Jul 30, 2020 at 11:26:15PM -0700, Norbert Kiesel wrote: >This is a laptop running Debain Unstable with 2 SSD and one spinning disk. >After upgrade and install, system stopped with same error message during boot. > >I was able to reactivate using a live boot system. ACK. Same thing applies as I suggested to Paul - maybe an inconsistent set of updates. Have you *fixed* the problem by using the live boot? -- Steve McIntyre, Cambridge, UK.st...@einval.com There's no sensation to compare with this Suspended animation, A state of bliss
Bug#966575: grub-pc: error: symbol `grub_calloc' not found.
Hi Paul, On Fri, Jul 31, 2020 at 06:39:20AM +0200, Paul Menzel wrote: >Am 31.07.20 um 06:30 schrieb Paul Menzel: > >> Am 30.07.20 um 23:54 schrieb Paul Menzel: >> > Package: grub-pc >> > Version: 2.04-9 >> > Severity: grave >> >> > On a Acer TravelMate 5735Z with Debian Sid/unstable, upgrading the >> > package `grub-pc` causes GRUB to fail on next boot and drop into a >> > rescue shell. >> > >> > GRUB loading. >> > Welcome to GRUB! >> > >> > error: symbol 'grub_calloc' not found. >> > grub rescue> >> > >> > It only seems to effects MBR installation. >> >> I missed to report, that the system has a separate `/boot` partition and >> a LUKS encrypted root `/`. > >Sorry, please scratch that. I remembered incorrectly. It’s just one >unencrypted F2FS formatted partition. How many disks do you have on your system, please? *If* you have more than one, there's a potential for grub-install to have not been run to install grub to all the MBRs, and then the BIOS finds an old copy of the GRUB first-stage loader but tries to use newer modules. this mis-match can cause all kinds of problems. :-/ -- Steve McIntyre, Cambridge, UK.st...@einval.com Can't keep my eyes from the circling sky, Tongue-tied & twisted, Just an earth-bound misfit, I...
Bug#957558: marked as done (montage: ftbfs with GCC-10)
Your message dated Fri, 31 Jul 2020 13:19:21 + with message-id and subject line Bug#957558: fixed in montage 6.0+dfsg-7 has caused the Debian Bug report #957558, regarding montage: ftbfs with GCC-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.) -- 957558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:montage Version: 6.0+dfsg-6 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/montage_6.0+dfsg-6_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] cp www.h ../../include make[4]: Leaving directory '/<>/lib/src/www' (cd two_plane_v1.1 && make && make install) make[4]: Entering directory '/<>/lib/src/two_plane_v1.1' gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -ansi -I. -I../../include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/wcstools -I/usr/include/freetype2 -c -o two_plane.o two_plane.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -ansi -I. -I../../include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/wcstools -I/usr/include/freetype2 -c -o distort.o distort.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -ansi -I. -I../../include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/wcstools -I/usr/include/freetype2 -c -o initdistdata.o initdistdata.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -ansi -I. -I../../include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/wcstools -I/usr/include/freetype2 -c -o undistort.o undistort.c gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fPIC -ansi -I. -I../../include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -Wdate-time -D_FORTIFY_SOURCE=2 -I/usr/include/wcstools -I/usr/include/freetype2 -c -o redefine_pointing.o redefine_pointing.c In file included from /usr/include/string.h:495, from redefine_pointing.c:3: In function ‘strncpy’, inlined from ‘replace_keyword’ at redefine_pointing.c:307:3: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound depends on the length of the source argument [-Wstringop-overflow=] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ redefine_pointing.c: In function ‘replace_keyword’: redefine_pointing.c:306:18: note: length computed here 306 | total_length = strlen(char_value); | ^~ ar rv libtwoplane.a two_plane.o distort.o initdistdata.o \ undistort.o redefine_pointing.o ar: creating libtwoplane.a a - two_plane.o a - distort.o a - initdistdata.o a - undistort.o a - redefine_pointing.o make[4]: Leaving directory '/<>/lib/src/two_plane_v1.1' make[4]: Entering directory '/<>/lib/src/two_plane_v1.1' cp libtwoplane.a ../.. cp two_plane.h distort.h ../../include make[4]: Leaving directory '/<>/lib/src/two_plane_v1.1' (cd lodepng_20140823 && make && make install) make[4]: Entering directory '/<>/lib/src/lodepng_20140823' gcc -g -O2 -fdebug-prefix-map=/<>=. -
Processed: seqan3 not seqan
Processing commands for cont...@bugs.debian.org: > reassign 966433 seqan3 Bug #966433 [src:seqan] seqan autopkg test failures triggered by gcc-defaults Bug reassigned from package 'src:seqan' to 'seqan3'. No longer marked as found in versions seqan/3.0.1+ds-10. Ignoring request to alter fixed versions of bug #966433 to the same values previously set > -- Stopping processing here. Please contact me if you need assistance. -- 966433: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966433 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 966595 is forwarded to https://github.com/zoggy/lablgtk-extras/issues/1
Processing commands for cont...@bugs.debian.org: > forwarded 966595 https://github.com/zoggy/lablgtk-extras/issues/1 Bug #966595 [src:lablgtk-extras] Please port to lablgtk3 Set Bug forwarded-to-address to 'https://github.com/zoggy/lablgtk-extras/issues/1'. > thanks Stopping processing here. Please contact me if you need assistance. -- 966595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#965288: marked as done (r-cran-findpython: Python2 removal in sid/bullseye)
Your message dated Fri, 31 Jul 2020 15:01:35 +0200 with message-id and subject line Re: Bug#965288: r-cran-findpython: Python2 removal in sid/bullseye has caused the Debian Bug report #965288, regarding r-cran-findpython: Python2 removal in sid/bullseye 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.) -- 965288: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965288 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: r-cran-findpython Version: 1.0.5-2 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests, in details: (binary:r-cran-findpython)Recommends->python Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- On Sun, 19 Jul 2020 09:51:09 +0300 Adrian Bunk wrote: > On Sun, Jul 19, 2020 at 02:45:22AM -0400, Sandro Tosi wrote: > > On Sun, Jul 19, 2020 at 2:41 AM Adrian Bunk wrote: > > > > > > On Sun, Jul 19, 2020 at 02:33:33AM -0400, Sandro Tosi wrote: > > > > > Recommends: r-cran-testthat, python3 | python > > > > > > > > > > Non-default alternative looks OK to me. > > > > > > > > it doesnt really make much sense: either it needs python2 or python3; > > > > if "| python" is not needed, it can be just easily dropped, and avoid > > > > the confusion it causes (special cases are not special enough) > > > > > > As the package name says it does not need python, it finds python: > > > > > > Description-en: GNU R functions to find an acceptable Python binary > > > This GNU R package is designed to find an acceptable Python > > > binary. It is possible to specify a minimum and a maximum Python > > > version as well as specifying needed Python modules. > > > > > > "python3 | python" looks correct to me for that. > > > > the point of these bugs (as the subject says) is to remove python2 > > dependencies, so "| python" has to go. if it doesnt, then this bug > > ought to stay open until it is addressed. > > This would only make sense if the point were to not ship python2 > in bullseye. Since there is only a recommends on python(2), and that is not against policy nor the Python 2 removal process then I am closing this bug. Thanks for checking! -- Michael R. Crusoe signature.asc Description: OpenPGP digital signature --- End Message ---
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forwarded 957941 wmaker-...@googlegroups.com Bug #957941 [src:wmcalclock] wmcalclock: ftbfs with GCC-10 Set Bug forwarded-to-address to 'wmaker-...@googlegroups.com'. > thanks Stopping processing here. Please contact me if you need assistance. -- 957941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957941: wmcalclock: diff for NMU version 1.25-16.1
Control: tags -1 forwarded wmaker-...@googlegroups.com
On 7/31/20 7:25 AM, Sudip Mukherjee wrote:
> I've prepared an NMU for wmcalclock (versioned as 1.25-16.1) and
> uploaded it to DELAYED/5. Please feel free to tell me if I
> should cancel it.
>
> Also added Douglas in Cc as he intends to adopt this package.
>
> --
> Regards
> Sudip
>
> diff -Nru wmcalclock-1.25/debian/changelog wmcalclock-1.25/debian/changelog
> --- wmcalclock-1.25/debian/changelog2016-10-27 01:33:54.0 +0100
> +++ wmcalclock-1.25/debian/changelog2020-07-31 12:11:07.0 +0100
> @@ -1,3 +1,10 @@
> +wmcalclock (1.25-16.1) unstable; urgency=medium
> +
> + * Non-maintainer upload.
> + * Fix ftbfs with GCC-10. (Closes: #957941)
> +
> + -- Sudip Mukherjee Fri, 31 Jul 2020 12:11:07
> +0100
> +
> wmcalclock (1.25-16) unstable; urgency=low
>
> * Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
> diff -Nru wmcalclock-1.25/debian/patches/05-fix-ftbfs.patch
> wmcalclock-1.25/debian/patches/05-fix-ftbfs.patch
> --- wmcalclock-1.25/debian/patches/05-fix-ftbfs.patch 1970-01-01
> 01:00:00.0 +0100
> +++ wmcalclock-1.25/debian/patches/05-fix-ftbfs.patch 2020-07-29
> 21:44:00.0 +0100
> @@ -0,0 +1,41 @@
> +Description: Fix ftbfs with GCC-10
> +
> +Author: Sudip Mukherjee
> +Bug-Debian: https://bugs.debian.org/957941
> +Forwarded: no
> +
> +---
> +
> +--- wmcalclock-1.25.orig/Src/xutils.c
> wmcalclock-1.25/Src/xutils.c
> +@@ -53,6 +53,11 @@ GC NormalGC;
> + XpmIcon wmgen;
> + Pixmappixmask;
> +
> ++Display *display;
> ++WindowRoot;
> ++Windowiconwin, win;
> ++int screen;
> ++int DisplayDepth;
> +
> + /*
> + * Colors for wmCalClock
> +--- wmcalclock-1.25.orig/Src/xutils.h
> wmcalclock-1.25/Src/xutils.h
> +@@ -18,11 +18,11 @@ typedef struct {
> + /*
> + * Global variable
> + */
> +-Display *display;
> +-Window Root;
> +-Window iconwin, win;
> +-int screen;
> +-int DisplayDepth;
> ++extern Display*display;
> ++extern Window Root;
> ++extern Window iconwin, win;
> ++extern intscreen;
> ++extern intDisplayDepth;
> +
> +
> +
> diff -Nru wmcalclock-1.25/debian/patches/series
> wmcalclock-1.25/debian/patches/series
> --- wmcalclock-1.25/debian/patches/series 2016-10-27 01:27:28.0
> +0100
> +++ wmcalclock-1.25/debian/patches/series 2020-07-29 21:42:34.0
> +0100
> @@ -3,3 +3,4 @@
> 02-30hr-patch.patch
> 03-manapge-30hr-patch.patch
> 04-makefile-modifications.patch
> +05-fix-ftbfs.patch
I've forwarded your patch upstream. Thank you!
From 704cd8679f95fca7cce61ae4fe2e7b4ba203da5c Mon Sep 17 00:00:00 2001
From: Sudip Mukherjee
Date: Fri, 31 Jul 2020 08:13:33 -0400
Subject: [PATCH] Description: Fix ftbfs with GCC-10
Bug-Debian: https://bugs.debian.org/957941
Forwarded: no
---
wmCalClock/Src/xutils.c | 5 +
wmCalClock/Src/xutils.h | 10 +-
2 files changed, 10 insertions(+), 5 deletions(-)
diff --git a/wmCalClock/Src/xutils.c b/wmCalClock/Src/xutils.c
index 5426d4f..008afa5 100644
--- a/wmCalClock/Src/xutils.c
+++ b/wmCalClock/Src/xutils.c
@@ -53,6 +53,11 @@ GC NormalGC;
XpmIcon wmgen;
Pixmap pixmask;
+Display *display;
+WindowRoot;
+Windowiconwin, win;
+int screen;
+int DisplayDepth;
/*
* Colors for wmCalClock
diff --git a/wmCalClock/Src/xutils.h b/wmCalClock/Src/xutils.h
index 4ed615f..b8f3f77 100644
--- a/wmCalClock/Src/xutils.h
+++ b/wmCalClock/Src/xutils.h
@@ -18,11 +18,11 @@ typedef struct {
/*
* Global variable
*/
-Display *display;
-Window Root;
-Window iconwin, win;
-int screen;
-int DisplayDepth;
+extern Display*display;
+extern Window Root;
+extern Window iconwin, win;
+extern intscreen;
+extern intDisplayDepth;
--
2.25.1
Processed: Re: tome: FTBFS with GCC 10 due to insufficient #includes
Processing control commands: > tags -1 + patch Bug #966065 [src:tome] tome: FTBFS with GCC 10 due to insufficient #includes Added tag(s) patch. > forwarded -1 https://github.com/tome2/tome2/pull/49 Bug #966065 [src:tome] tome: FTBFS with GCC 10 due to insufficient #includes Set Bug forwarded-to-address to 'https://github.com/tome2/tome2/pull/49'. -- 966065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966065: tome: FTBFS with GCC 10 due to insufficient #includes
Control: tags -1 + patch Control: forwarded -1 https://github.com/tome2/tome2/pull/49 Hi, the attached patch fixes the FTBFS with GCC 10. Regards, Reiner diff --git a/debian/patches/gcc10.patch b/debian/patches/gcc10.patch new file mode 100644 index ..bf9fcf45 --- /dev/null +++ b/debian/patches/gcc10.patch @@ -0,0 +1,16 @@ +Author: Reiner Herrmann +Description: Fix FTBFS with GCC 10 +Bug-Debian: https://bugs.debian.org/966065 +Forwarded: https://github.com/tome2/tome2/pull/49 + +--- a/src/init1.hpp b/src/init1.hpp +@@ -3,6 +3,8 @@ + #include "h-basic.hpp" + #include "dungeon_flag_set.hpp" + ++#include ++ + int color_char_to_attr(char c); + extern byte conv_color[16]; + errr init_player_info_txt(FILE *fp); diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index ..50fb8b62 --- /dev/null +++ b/debian/patches/series @@ -0,0 +1 @@ +gcc10.patch signature.asc Description: PGP signature
Bug#957595: marked as done (netdata: ftbfs with GCC-10)
Your message dated Fri, 31 Jul 2020 12:19:26 + with message-id and subject line Bug#957595: fixed in netdata 1.19.0-4 has caused the Debian Bug report #957595, regarding netdata: ftbfs with GCC-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.) -- 957595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:netdata Version: 1.19.0-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/netdata_1.19.0-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] gcc-I/usr/include/uuid -lcap -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wall -O3 -pthread -flto -I/usr/include/uuid -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o nfacct.plugin collectors/nfacct.plugin/plugin_nfacct.o libnetdata/adaptive_resortable_list/adaptive_resortable_list.o libnetdata/config/appconfig.o libnetdata/avl/avl.o libnetdata/buffer/buffer.o libnetdata/clocks/clocks.o libnetdata/dictionary/dictionary.o libnetdata/eval/eval.o libnetdata/libnetdata.o libnetdata/locks/locks.o libnetdata/log/log.o libnetdata/popen/popen.o libnetdata/procfile/procfile.o libnetdata/os.o libnetdata/simple_pattern/simple_pattern.o libnetdata/socket/socket.o libnetdata/socket/security.o libnetdata/statistical/statistical.o libnetdata/storage_number/storage_number.o libnetdata/threads/threads.o libnetdata/url/url.o libnetdata/json/json.o libnetdata/json/jsmn.o libnetdata/health/health.o -lm -lz -lcrypto -lssl -l uuid -luv -llz4 -lJudy -lcrypto -lssl -ljson-c -lnetfilter_acct -lmnl /usr/bin/ld: libnetdata/adaptive_resortable_list/adaptive_resortable_list.o (symbol from plugin): in function `arl_callback_str2ull': (.text+0x0): multiple definition of `silencers'; collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: libnetdata/config/appconfig.o (symbol from plugin): in function `appconfig_section_compare': (.text+0x0): multiple definition of `silencers'; collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: libnetdata/avl/avl.o (symbol from plugin): in function `avl_search': (.text+0x0): multiple definition of `silencers'; collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: libnetdata/buffer/buffer.o (symbol from plugin): in function `buffer_reset': (.text+0x0): multiple definition of `silencers'; collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: libnetdata/clocks/clocks.o (symbol from plugin): in function `test_clock_boottime': (.text+0x0): multiple definition of `silencers'; collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: libnetdata/dictionary/dictionary.o (symbol from plugin): in function `dictionary_create': (.text+0x0): multiple definition of `silencers'; collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: libnetdata/eval/eval.o (symbol from plugin): in function `eval_and': (.text+0x0): multiple definition of `silencers'; collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: libnetdata/libnetdata.o (symbol from plugin): in function `strdupz': (.text+0x0): multiple definition of `silencers
Processed: Re: cufflinks: FTBFS with GCC 10
Processing control commands: > tags -1 + patch Bug #966191 [src:cufflinks] cufflinks: FTBFS with GCC 10: multiple definition of ... due to -fno-common Added tag(s) patch. -- 966191: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966191 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966191: cufflinks: FTBFS with GCC 10
Control: tags -1 + patch Hi, the attached patch fixes the FTBFS with GCC 10. Regards, Reiner diff --git a/debian/patches/gcc10.patch b/debian/patches/gcc10.patch new file mode 100644 index 000..1a58bd4 --- /dev/null +++ b/debian/patches/gcc10.patch @@ -0,0 +1,17 @@ +Author: Reiner Herrmann +Description: Fix FTBFS with GCC 10 + curwin is declared in different source file. declare it as extern + to fix multiple definition linker error. +Bug-Debian: https://bugs.debian.org/966191 + +--- a/src/locfit/startlf.c b/src/locfit/startlf.c +@@ -233,7 +233,7 @@ + extern lfit lf; + extern design des; + extern plots pl[]; +-int curwin; ++extern int curwin; + vari *vb; + + INT nofit() diff --git a/debian/patches/series b/debian/patches/series index a478e9a..fd3fe0d 100644 --- a/debian/patches/series +++ b/debian/patches/series @@ -8,3 +8,4 @@ fix_gcc-7_ftbfs.patch format-security.patch lib_eigen.patch fix_gcc-6.1_issue_in_liblemon_code_copy.patch +gcc10.patch signature.asc Description: PGP signature
Processed: Re: Bug#966600: nfstrace: patch for newer json-c/gcc-10
Processing control commands: > forwarded -1 https://github.com/epam/nfstrace/pull/42 Bug #966600 [src:nfstrace] nfstrace: patch for newer json-c/gcc-10 Set Bug forwarded-to-address to 'https://github.com/epam/nfstrace/pull/42'. -- 966600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966600: nfstrace: patch for newer json-c/gcc-10
control: forwarded -1 https://github.com/epam/nfstrace/pull/42 G.
Bug#966600: nfstrace: patch for newer json-c/gcc-10
:) https://github.com/epam/nfstrace/pull/42 Il venerdì 31 luglio 2020, 11:41:12 CEST, Andrej Shadura ha scritto: Hi, On Fri, 31 Jul 2020, at 11:23, Gianfranco Costamagna wrote: > Source: nfstrace > Version: 0.4.3.2+git20180104+6561cf6-1 > Severity: serious > tags: patch > > hello, attached a patch that makes it build with newer json-c/gcc-10 Thanks! Could you please also submit it upstream or should I? -- Cheers, Andrej
Bug#966597: multipath-tools: patch for newer json-c
hello, I see lots of various people upstream did sed s/TRUE/1/g sed s/FALSE/0/g :) G. Il venerdì 31 luglio 2020, 11:29:45 CEST, Chris Hofstaedtler ha scritto: Hi Gianfranco, * Gianfranco Costamagna [200731 10:30]: > Source: multipath-tools > Version: 0.8.4-2 > Severity: serious > tags: patch > > hello, attached a patch that makes it build with newer json-c Thanks! I'm considering going with a somewhat different patch given TRUE is used only once at all. Should be done soon. Chris
Bug#957595: netdata: ftbfs with GCC-10
On 7/31/20 1:05 PM, Gianfranco Costamagna wrote: > attached the upstream fix refreshed on top of the current debian version great, thanks a lot for the help; I'll upload within the next couple of hours. Regards, Daniel
Bug#965959: marked as done (openstructure: dng does not start: missing libraries)
Your message dated Fri, 31 Jul 2020 11:39:24 + with message-id and subject line Bug#965959: fixed in openstructure 2.0.0-3 has caused the Debian Bug report #965959, regarding openstructure: dng does not start: missing libraries 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.) -- 965959: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965959 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: openstructure Version: 2.0.0-2 Severity: important attempting to run dng only aborts with the following errors: /usr/bin/dng: line 29: /usr/bin/../lib/openstructure/libexec/ost_config: No such file or directory /usr/bin/dng: line 43: /usr/bin/../lib/openstructure/libexec/gosty: No such file or directory -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU threads) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openstructure depends on: ii libboost-filesystem1.71.0 1.71.0-6+b2 ii libboost-iostreams1.71.01.71.0-6+b2 ii libboost-program-options1.71.0 1.71.0-6+b2 ii libc6 2.31-1 ii libgcc-s1 10.1.0-6 ii libost-base2.0 2.0.0-2 ii libost-conop2.0 2.0.0-2 ii libost-io2.02.0.0-2 ii libost-mol-alg2.0 2.0.0-2 ii libost-mol2.0 2.0.0-2 ii libstdc++6 10.1.0-6 ii python3 3.8.2-3 ii python3-ost 2.0.0-2 openstructure recommends no packages. openstructure suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: openstructure Source-Version: 2.0.0-3 Done: Andrius Merkys We believe that the bug you reported is fixed in the latest version of openstructure, 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 965...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrius Merkys (supplier of updated openstructure 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: Fri, 31 Jul 2020 07:17:40 -0400 Source: openstructure Architecture: source Version: 2.0.0-3 Distribution: unstable Urgency: medium Maintainer: Debichem Team Changed-By: Andrius Merkys Closes: 965959 Changes: openstructure (2.0.0-3) unstable; urgency=medium . * Installing gosty and ost_config. * Cleaning leftover files. * Adjusting paths in Debian installation (Closes: #965959). Checksums-Sha1: 2a676d3f544e81a9ccc0564f47ea6748bf3712fc 3378 openstructure_2.0.0-3.dsc 2e4df0ecd16b1b1628787188f2ce21c11e34efa9 9760 openstructure_2.0.0-3.debian.tar.xz 4bb665fca2fe71c44813ec8e0d614fdcae9d75d6 18265 openstructure_2.0.0-3_source.buildinfo Checksums-Sha256: e1a742fda028ebefbc32d7b8d5ac191cd2372739350a3e5954e99b5ab331869f 3378 openstructure_2.0.0-3.dsc b28006db3e8e19a2a1082a0206f119a3f6ad9e2a42bbf69b881ae5662f412878 9760 openstructure_2.0.0-3.debian.tar.xz ccd2c90c85f6d4c7cdbc13f967cc8695d3b744a8978d6cc175708e75a7ad469a 18265 openstructure_2.0.0-3_source.buildinfo Files: d8ea7123b068317b1c38553ef12a4238 3378 science optional openstructure_2.0.0-3.dsc 95d640e857349f362282da4869f5d5f5 9760 science optional openstructure_2.0.0-3.debian.tar.xz d4365b0d0541bdab566a8e7aab58ac70 18265 science optional openstructure_2.0.0-3_source.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAl8j/lYSHG1lcmt5c0Bk ZWJpYW4ub3JnAAoJEOX0P5wnNPKH1MMP/1xXhazsLPu7JSBRWYesKf/2ABe0kQbr Rvn0du7tHpUCunUvJORJgY/aeKKLoDLTqccE93Tmg3/UFLqWn8nlWJJRW7nB+0DP 9p0i9Mx5RqQWQeanDDCQQxl+lGdDM3apnyMic8r59rOyEbVrab8NZMqNLlefhPUv 5pikQe8DG20QEZjbgxLcE/zWhsRhVjqTzaaQZ/DkQuRSLfl046z+uQM/3dzY4/jd hU6oHfbif6cZRMTEGeai6AjVtqpY6YLM1409h2uSagak+4xTxLBABnWtgT8qDAUW 3x0em6VCqffXuh7kF+66juolYf0ZFLduAD1SFwYRLBROri+0f6UecAmkRlgO9We/ LpDyPxlAK5VDBBIrUYjuiFoJUeEdh1J
Bug#957243: marked as done (g15daemon: ftbfs with GCC-10)
Your message dated Fri, 31 Jul 2020 11:34:47 +
with message-id
and subject line Bug#957243: fixed in g15daemon 1.9.5.3-12
has caused the Debian Bug report #957243,
regarding g15daemon: ftbfs with GCC-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.)
--
957243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957243
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:g15daemon
Version: 1.9.5.3-11
Severity: normal
Tags: sid bullseye
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-10
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-10/g++-10, but succeeds to build with gcc-9/g++-9. The
severity of this report will be raised before the bullseye release,
so nothing has to be done for the buster release.
The full build log can be found at:
http://people.debian.org/~doko/logs/gcc10-20200225/g15daemon_1.9.5.3-11_unstable_gcc10.log
The last lines of the build log are at the end of this report.
To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html
[...]
| ^~
utility_funcs.c: In function ‘uf_create_pidfile’:
utility_funcs.c:164:29: warning: operation on ‘l’ may be undefined
[-Wsequence-point]
164 | if (write(fd, pidtxt, l = strlen(pidtxt)) != l) {
| ~~^~~~
main.c: In function ‘main’:
main.c:411:9: warning: this ‘for’ clause does not guard...
[-Wmisleading-indentation]
411 | for(i=1;i>=. -fstack-protector-strong -Wformat
-Werror=format-security -c -o g15_plugins.o g15_plugins.c
/bin/bash ../libtool --tag=CC --mode=link gcc -DG15DAEMON_BUILD -Wall -g -O2
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -Wl,-z,relro -o g15daemontest lcdclient_test.o
../libg15daemon_client/libg15daemon_client.la -lpthread -lm -lg15render -lg15
g15_plugins.c: In function ‘g15_count_plugins’:
g15_plugins.c:211:17: warning: ‘strncat’ specified bound 1 equals source length
[-Wstringop-overflow=]
211 | strncat(pluginname,"/",1);
| ^
g15_plugins.c: In function ‘g15_open_all_plugins’:
g15_plugins.c:322:17: warning: ‘strncat’ specified bound 1 equals source length
[-Wstringop-overflow=]
322 | strncat(pluginname,"/",1);
| ^
g15_plugins.c:351:9: warning: ‘strncat’ specified bound 1 equals source length
[-Wstringop-overflow=]
351 | strncat(plugin_fname,"/",1);
| ^~~
g15_plugins.c: In function ‘g15_count_plugins’:
g15_plugins.c:212:17: warning: ‘strncat’ output may be truncated copying 200
bytes from a string of length 255 [-Wstringop-truncation]
212 | strncat(pluginname,ep->d_name,200);
| ^~
g15_plugins.c: In function ‘g15_open_all_plugins’:
g15_plugins.c:349:24: warning: ‘sprintf’ may write a terminating nul past the
end of the destination [-Wformat-overflow=]
349 | sprintf(tmp,"%i",i);
|^
g15_plugins.c:349:9: note: ‘sprintf’ output between 2 and 11 bytes into a
destination of size 10
349 | sprintf(tmp,"%i",i);
| ^~~
g15_plugins.c:323:17: warning: ‘strncat’ output may be truncated copying 200
bytes from a string of length 255 [-Wstringop-truncation]
323 | strncat(pluginname,ep->d_name,200);
| ^~
g15_plugins.c:326:34: warning: ‘sprintf’ may write a terminating nul past the
end of the destination [-Wformat-overflow=]
326 | sprintf(tmp,"%i",loadcount);
| ^
g15_plugins.c:326:19: note: ‘sprintf’ output between 2 and 11 bytes into a
destination of size 10
326 | sprintf(tmp,"%i",loadcount);
| ^~~
Processed: block 911166 with 966595
Processing commands for cont...@bugs.debian.org: > block 911166 with 966595 Bug #911166 [src:gtksourceview2] gtksourceview2: Do not release with Bullseye 911166 was blocked by: 890456 885677 885676 885675 885678 885681 911164 885685 911167 911166 was not blocking any bugs. Added blocking bug(s) of 911166: 966595 > thanks Stopping processing here. Please contact me if you need assistance. -- 911166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957941: wmcalclock: diff for NMU version 1.25-16.1
Control: tags 957941 + patch
Control: tags 957941 + pending
Dear maintainer,
I've prepared an NMU for wmcalclock (versioned as 1.25-16.1) and
uploaded it to DELAYED/5. Please feel free to tell me if I
should cancel it.
Also added Douglas in Cc as he intends to adopt this package.
--
Regards
Sudip
diff -Nru wmcalclock-1.25/debian/changelog wmcalclock-1.25/debian/changelog
--- wmcalclock-1.25/debian/changelog2016-10-27 01:33:54.0 +0100
+++ wmcalclock-1.25/debian/changelog2020-07-31 12:11:07.0 +0100
@@ -1,3 +1,10 @@
+wmcalclock (1.25-16.1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix ftbfs with GCC-10. (Closes: #957941)
+
+ -- Sudip Mukherjee Fri, 31 Jul 2020 12:11:07
+0100
+
wmcalclock (1.25-16) unstable; urgency=low
* Remove deprecated dpatch and upgrade to packaging format "3.0 quilt".
diff -Nru wmcalclock-1.25/debian/patches/05-fix-ftbfs.patch
wmcalclock-1.25/debian/patches/05-fix-ftbfs.patch
--- wmcalclock-1.25/debian/patches/05-fix-ftbfs.patch 1970-01-01
01:00:00.0 +0100
+++ wmcalclock-1.25/debian/patches/05-fix-ftbfs.patch 2020-07-29
21:44:00.0 +0100
@@ -0,0 +1,41 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee
+Bug-Debian: https://bugs.debian.org/957941
+Forwarded: no
+
+---
+
+--- wmcalclock-1.25.orig/Src/xutils.c
wmcalclock-1.25/Src/xutils.c
+@@ -53,6 +53,11 @@ GC NormalGC;
+ XpmIcon wmgen;
+ Pixmappixmask;
+
++Display *display;
++WindowRoot;
++Windowiconwin, win;
++int screen;
++int DisplayDepth;
+
+ /*
+ * Colors for wmCalClock
+--- wmcalclock-1.25.orig/Src/xutils.h
wmcalclock-1.25/Src/xutils.h
+@@ -18,11 +18,11 @@ typedef struct {
+ /*
+ * Global variable
+ */
+-Display *display;
+-Window Root;
+-Window iconwin, win;
+-int screen;
+-int DisplayDepth;
++extern Display*display;
++extern Window Root;
++extern Window iconwin, win;
++extern intscreen;
++extern intDisplayDepth;
+
+
+
diff -Nru wmcalclock-1.25/debian/patches/series
wmcalclock-1.25/debian/patches/series
--- wmcalclock-1.25/debian/patches/series 2016-10-27 01:27:28.0
+0100
+++ wmcalclock-1.25/debian/patches/series 2020-07-29 21:42:34.0
+0100
@@ -3,3 +3,4 @@
02-30hr-patch.patch
03-manapge-30hr-patch.patch
04-makefile-modifications.patch
+05-fix-ftbfs.patch
Processed: wmcalclock: diff for NMU version 1.25-16.1
Processing control commands: > tags 957941 + patch Bug #957941 [src:wmcalclock] wmcalclock: ftbfs with GCC-10 Added tag(s) patch. > tags 957941 + pending Bug #957941 [src:wmcalclock] wmcalclock: ftbfs with GCC-10 Added tag(s) pending. -- 957941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957236: frr: ftbfs with GCC-10
control: close -1 thanks G. On Fri, 17 Apr 2020 11:00:39 + Matthias Klose wrote: > Package: src:frr > Version: 7.2.1-1 > Severity: normal > Tags: sid bullseye > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-10 > > 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The > severity of this report will be raised before the bullseye release, > so nothing has to be done for the buster release. > > The full build log can be found at: > http://people.debian.org/~doko/logs/gcc10-20200225/frr_7.2.1-1_unstable_gcc10.log > The last lines of the build log are at the end of this report. > > To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html > > [...] > /bin/bash ./libtool --tag=CC --mode=link gcc -std=gnu11 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -fno-omit-frame-pointer -funwind-tables -Wall -Wextra > -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith > -Wbad-function-cast -Wwrite-strings -Wno-unused-result -Wno-unused-parameter > -Wno-missing-field-initializers -pthread -export-dynamic-Wl,-z,relro > -Wl,-z,now -o ospf6d/ospf6d ospf6d/ospf6_main.o ospf6d/libospf6.a > lib/libfrr.la -lcap -ldl -lcrypt -ljson-c -lsystemd -lrt > libtool: link: gcc -std=gnu11 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security > -fno-omit-frame-pointer -funwind-tables -Wall -Wextra -Wmissing-prototypes > -Wmissing-declarations -Wpointer-arith -Wbad-function-cast -Wwrite-strings > -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers > -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now -o ospfd/.libs/ospfd > ospfd/ospf_main.o -Wl,--export-dynamic ospfd/libfrrospf.a > lib/.libs/libfrr.so -lcap -lm -ldl -lcrypt -ljson-c -lsystemd -lrt -pthread > -Wl,-rpath -Wl,/usr/lib/x86_64-linux-gnu/frr > libtool: link: gcc -std=gnu11 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security > -fno-omit-frame-pointer -funwind-tables -Wall -Wextra -Wmissing-prototypes > -Wmissing-declarations -Wpointer-arith -Wbad-function-cast -Wwrite-strings > -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers > -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now -o ospf6d/.libs/ospf6d > ospf6d/ospf6_main.o -Wl,--export-dynamic ospf6d/libospf6.a > lib/.libs/libfrr.so -lcap -ldl -lcrypt -ljson-c -lsystemd -lrt -pthread > -Wl,-rpath -Wl,/usr/lib/x86_64-linux-gnu/frr > /bin/bash ./libtool --tag=CC --mode=link gcc -std=gnu11 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -fno-omit-frame-pointer -funwind-tables -Wall -Wextra > -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith > -Wbad-function-cast -Wwrite-strings -Wno-unused-result -Wno-unused-parameter > -Wno-missing-field-initializers -pthread -export-dynamic-Wl,-z,relro > -Wl,-z,now -o isisd/isisd isisd/isis_bpf.o isisd/isis_dlpi.o > isisd/isis_main.o isisd/isis_pfpacket.o yang/frr-isisd.yang.o isisd/libisis.a > lib/libfrr.la -lcap -ldl -lcrypt -ljson-c -lsystemd -lrt > /bin/bash ./libtool --tag=CC --mode=link gcc -std=gnu11 -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -fno-omit-frame-pointer -funwind-tables -Wall -Wextra > -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith > -Wbad-function-cast -Wwrite-strings -Wno-unused-result -Wno-unused-parameter > -Wno-missing-field-initializers -pthread -export-dynamic-Wl,-z,relro > -Wl,-z,now -o isisd/fabricd isisd/fabricd-isis_bpf.o > isisd/fabricd-isis_dlpi.o isisd/fabricd-isis_main.o > isisd/fabricd-isis_pfpacket.o isisd/libfabric.a lib/libfrr.la -lcap -ldl > -lcrypt -ljson-c -lsystemd -lrt > libtool: link: gcc -std=gnu11 -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security > -fno-omit-frame-pointer -funwind-tables -Wall -Wextra -Wmissing-prototypes > -Wmissing-declarations -Wpointer-arith -Wbad-function-cast -Wwrite-strings > -Wno-unused-result -Wno-unused-parameter -Wno-missing-field-initializers > -pthread -Wl,-z -Wl,relro -Wl,-z -Wl,now -o isisd/.libs/isisd > isisd/isis_bpf.o isisd/isis_dlpi.o isisd/isis_main.o
Processed: Re: frr: ftbfs with GCC-10
Processing control commands: > close -1 Bug #957236 [src:frr] frr: ftbfs with GCC-10 Marked Bug as done -- 957236: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957236 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: yubikey-personalization: ftbfs with GCC-10
Processing control commands: > tags -1 patch Bug #958010 [src:yubikey-personalization] yubikey-personalization: ftbfs with GCC-10 Added tag(s) patch. -- 958010: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958010 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966599: marked as done (snmpd: Elevation of Privileges due to symlink handling)
Your message dated Fri, 31 Jul 2020 11:10:27 + with message-id and subject line Bug#966599: fixed in net-snmp 5.8+dfsg-5 has caused the Debian Bug report #966599, regarding snmpd: Elevation of Privileges due to symlink handling 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.) -- 966599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: snmpd Version: 5.8+dfsg-4 Severity: grave Tags: security upstream Justification: user security hole -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 CVE-2020-15861 snmpd runs as a low privileged user account. However, in combination with the *snmp-mibs-downloader package* this protection can be bypassed and it is possible for this account to elevate permissions to the root user. This attack happens due to how snmpd handles symlinks. References: https://github.com/net-snmp/net-snmp/issues/145 https://github.com/net-snmp/net-snmp/commit/4fd9a450444a434a993bc72f7c3486ccce41f602 This security vulnerability was found by Tobias Neitzel of usd AG. - -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.4.0-4-amd64 (SMP w/8 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages snmpd depends on: ii adduser3.118 ii debconf [debconf-2.0] 1.5.73 ii init-system-helpers1.57 ii libc6 2.30-2 ii libsnmp-base 5.8+dfsg-2 ii libsnmp35 5.8+dfsg-4 ii lsb-base 11.1.0 snmpd recommends no packages. Versions of packages snmpd suggests: ii snmptrapd 5.8+dfsg-4 - -- Configuration Files: /etc/snmp/snmpd.conf changed [not included] - -- debconf information excluded -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEXT3w9TizJ8CqeneiAiFmwP88hOMFAl8j268SHGNzbWFsbEBk ZWJpYW4ub3JnAAoJEAIhZsD/PITjzj0P/ReencZCeEbL/F2lznh8AhH42fC6tpi9 1McAS/calfYn9wFUTIfqi9JemMVjx8+2m0c6qW0/Yz698CACS45eUY4xTK9ejLEM Lezi2kQDLZwGHLfMIcd4U3DSC3ZNlFomOT0Idl43q2yiqHLYdXzxWaVSfgAHxLB2 ElBHSAS+UYCgp7Jd38oEZ5++rTUw5dKb249IiUee+AMCUToCHMes0abJ4r7D79ow PCIV410f1m1WlPJa5nWD/MioSnjdR2v9gmkuzmTq5Qjl6ShOR2B7Fh2/NWXzegXh Tu7MPeSAa7VnybicwIACzo7M7YvVBsw32CTtJZnOKFFU/Xrg6j/cUvTkpKuB+c+W D3dTgjieMRC0Gfc6aIAGE+nTOP4xMjLGGyhAxgBKp2THlZksO5ZSA4KXGswGLygl N19qe30Xy0ROuAKPMChNRmJXw0M+/pY2AX91QJUqGhvkXPfNBmtiy6LHyFo2RRCk yOlAC/8oQH8uHp1x7SUe02tiogbsLY/Yn6HTuvlo89Bt7UK2ifQXyqUkapySF3nw QDRFDh8+hkCvAubcW2ViEAY2n0Mca0+zeN5FyxK3PINSU6iz1zT2L3NI2HhIrZuZ 3YXCDQJe2jYa/LpeeBaR3TdY6ArDiwrkpzTwsOfltc4BzMyzUt1/7ccnhhNZo9N1 xwiQIxBbfw7b =Rnwp -END PGP SIGNATURE- --- End Message --- --- Begin Message --- Source: net-snmp Source-Version: 5.8+dfsg-5 Done: Craig Small We believe that the bug you reported is fixed in the latest version of net-snmp, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Craig Small (supplier of updated net-snmp 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: Fri, 31 Jul 2020 20:29:41 +1000 Source: net-snmp Architecture: source Version: 5.8+dfsg-5 Distribution: unstable Urgency: medium Maintainer: Net-SNMP Packaging Team Changed-By: Craig Small Closes: 966544 966599 Changes: net-snmp (5.8+dfsg-5) unstable; urgency=medium . * Allow extend to be read-only Closes: #966544 * Stop using mib_index files CVE-2020-15861 Closes: 966599 Checksums-Sha1: c078975bd5c23c1ad903da93dcf13a31baa57c9c 2812 net-snmp_5.8+dfsg-5.dsc abd8867c8751fcf7b25ff4b1a4aae0661352d6ee 77296 net-snmp_5.8+dfsg-5.debian.tar.xz 8067492ac9e2b67ad7ec09268cacb11aa0ed9d8c 9896 net-snmp_5.8+dfsg-5_amd64.buildinfo Checksums-Sha256: 2b46f745b2e321061c45ff6d9039d35addedef236203e386f6be71b18126fb73 2812 net-snmp_5.8+dfsg-5.dsc 3097a16b7538f9d492844a54e4dfea8ab80110f0b0b2b5f17cc95b09da9
Bug#958010: yubikey-personalization: ftbfs with GCC-10
control: tags -1 patch On Sun, 26 Jul 2020 14:58:58 +0100 Shayan Doust wrote: > Hello, > > Any rough timeframe as to when this FTBFS is fixed? > > Kind regards, > Shayan Doust I'm attaching the upstream fix to this bug report. thanks G. ## Description: add some description ## Origin/Author: add some origin or author ## Bug: bug URL >From 09ea16d9e2030e4da6ad00c1e5147e962aa7ff84 Mon Sep 17 00:00:00 2001 From: Klas Lindfors Date: Mon, 17 Feb 2020 08:58:33 +0100 Subject: [PATCH] make header declarations extern fixes #155 --- ykpers-args.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ykpers-args.h b/ykpers-args.h index 2a63268..9ff455a 100644 --- a/ykpers-args.h +++ b/ykpers-args.h @@ -33,8 +33,8 @@ #include "ykpers.h" -const char *usage; -const char *optstring; +extern const char *usage; +extern const char *optstring; int args_to_config(int argc, char **argv, YKP_CONFIG *cfg, char *oathid, size_t oathid_len, const char **infname,
Bug#966606: yubikey-personalization: patch for newer json-c
FYI upstream did something like sed s/FALSE/0 and sed s/TRUE/1 on the code, instead of defining them. G. On Fri, 31 Jul 2020 12:56:16 +0200 Gianfranco Costamagna wrote: > Source: yubikey-personalization > Version: 1.20.0-2 > Severity: serious > tags: patch > > Hello, this is the trivial patch that makes the package build with newer > jsonc. > > Description: Patch to make it build with newer json-c deprecated TRUE/FALSE > defines > > Author: Gianfranco Costamagna > Last-Update: 2020-07-31 > > Index: yubikey-personalization-1.20.0/ykpers-json.c > === > --- yubikey-personalization-1.20.0.orig/ykpers-json.c > +++ yubikey-personalization-1.20.0/ykpers-json.c > @@ -36,6 +36,14 @@ > #include > #include > > +// not exported anymore by new json-c > +#ifndef TRUE > +#define TRUE 1 > +#endif > +#ifndef FALSE > +#define FALSE 0 > +#endif > + > #ifdef HAVE_JSON_OBJECT_OBJECT_GET_EX > #define yk_json_object_object_get(obj, key, value) > json_object_object_get_ex(obj, key, &value) > #else > > > G. > > >
Processed: found 966599 in 5.7.3+dfsg-5
Processing commands for cont...@bugs.debian.org: > found 966599 5.7.3+dfsg-5 Bug #966599 [snmpd] snmpd: Elevation of Privileges due to symlink handling Marked as found in versions net-snmp/5.7.3+dfsg-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 966599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957595: netdata: ftbfs with GCC-10
control: tags -1 patch attached the upstream fix refreshed on top of the current debian version thanks Gianfranco On Fri, 17 Apr 2020 11:07:07 + Matthias Klose wrote: > Package: src:netdata > Version: 1.19.0-2 > Severity: normal > Tags: sid bullseye > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-10 > > 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The > severity of this report will be raised before the bullseye release, > so nothing has to be done for the buster release. > > The full build log can be found at: > http://people.debian.org/~doko/logs/gcc10-20200225/netdata_1.19.0-2_unstable_gcc10.log > The last lines of the build log are at the end of this report. > > To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html > > [...] > gcc-I/usr/include/uuid -lcap -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wall -O3 -pthread -flto -I/usr/include/uuid >-Wl,-z,relro -Wl,-z,now -Wl,--as-needed -o nfacct.plugin > collectors/nfacct.plugin/plugin_nfacct.o > libnetdata/adaptive_resortable_list/adaptive_resortable_list.o > libnetdata/config/appconfig.o libnetdata/avl/avl.o libnetdata/buffer/buffer.o > libnetdata/clocks/clocks.o libnetdata/dictionary/dictionary.o > libnetdata/eval/eval.o libnetdata/libnetdata.o libnetdata/locks/locks.o > libnetdata/log/log.o libnetdata/popen/popen.o libnetdata/procfile/procfile.o > libnetdata/os.o libnetdata/simple_pattern/simple_pattern.o > libnetdata/socket/socket.o libnetdata/socket/security.o > libnetdata/statistical/statistical.o > libnetdata/storage_number/storage_number.o libnetdata/threads/threads.o > libnetdata/url/url.o libnetdata/json/json.o libnetdata/json/jsmn.o > libnetdata/health/health.o -lm -lz -lcrypto -lssl -luuid -luv -llz4 -lJudy > -lcrypto -lssl -ljson-c -lnetfilter_acct -lmnl > /usr/bin/ld: libnetdata/adaptive_resortable_list/adaptive_resortable_list.o > (symbol from plugin): in function `arl_callback_str2ull': > (.text+0x0): multiple definition of `silencers'; > collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): > first defined here > /usr/bin/ld: libnetdata/config/appconfig.o (symbol from plugin): in function > `appconfig_section_compare': > (.text+0x0): multiple definition of `silencers'; > collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): > first defined here > /usr/bin/ld: libnetdata/avl/avl.o (symbol from plugin): in function > `avl_search': > (.text+0x0): multiple definition of `silencers'; > collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): > first defined here > /usr/bin/ld: libnetdata/buffer/buffer.o (symbol from plugin): in function > `buffer_reset': > (.text+0x0): multiple definition of `silencers'; > collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): > first defined here > /usr/bin/ld: libnetdata/clocks/clocks.o (symbol from plugin): in function > `test_clock_boottime': > (.text+0x0): multiple definition of `silencers'; > collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): > first defined here > /usr/bin/ld: libnetdata/dictionary/dictionary.o (symbol from plugin): in > function `dictionary_create': > (.text+0x0): multiple definition of `silencers'; > collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): > first defined here > /usr/bin/ld: libnetdata/eval/eval.o (symbol from plugin): in function > `eval_and': > (.text+0x0): multiple definition of `silencers'; > collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): > first defined here > /usr/bin/ld: libnetdata/libnetdata.o (symbol from plugin): in function > `strdupz': > (.text+0x0): multiple definition of `silencers'; > collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): > first defined here > /usr/bin/ld: libnetdata/locks/locks.o (symbol from plugin): in function > `netdata_thread_disable_cancelability': > (.text+0x0): multiple definition of `silencers'; > collectors/nfacct.plugin/plugin_nfacct.o (symbol from plugin):(.text+0x0): > first defined here > /usr/bin/ld: libnetdata/log/log.o (symbol from plugin): in function
Processed: Re: netdata: ftbfs with GCC-10
Processing control commands: > tags -1 patch Bug #957595 [src:netdata] netdata: ftbfs with GCC-10 Added tag(s) patch. -- 957595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957595 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966575: Security update can break grub - grub_calloc not found
Sorry, I forgot to mention that this occurs with the stable security updates. Geoff
Bug#966606: yubikey-personalization: patch for newer json-c
Source: yubikey-personalization Version: 1.20.0-2 Severity: serious tags: patch Hello, this is the trivial patch that makes the package build with newer jsonc. Description: Patch to make it build with newer json-c deprecated TRUE/FALSE defines Author: Gianfranco Costamagna Last-Update: 2020-07-31 Index: yubikey-personalization-1.20.0/ykpers-json.c === --- yubikey-personalization-1.20.0.orig/ykpers-json.c +++ yubikey-personalization-1.20.0/ykpers-json.c @@ -36,6 +36,14 @@ #include #include +// not exported anymore by new json-c +#ifndef TRUE +#define TRUE 1 +#endif +#ifndef FALSE +#define FALSE 0 +#endif + #ifdef HAVE_JSON_OBJECT_OBJECT_GET_EX #define yk_json_object_object_get(obj, key, value) json_object_object_get_ex(obj, key, &value) #else G.
Bug#966575: Security update can break grub - grub_calloc not found
apt update apt full-upgrade grub upgrades from 2.02+dfsg1-20 to 2.02+dfsg1-20+deb10u1 no errors were spotted. When rebooted :- symbol grub_calloc not found Entering rescue mode grub rescue> I had to boot off a memory stick and then :- sudo -i mount /dev/sda5 /mnt grub-install --boot-directory=/mnt /dev/sda reboot This worked and the system now boots. /boot is the only ext type file system, the others are all handled by LVM Geoff
Bug#966604: libu2f-server: patch for newer json-c
Source: libu2f-server Version: 1.1.10-1 Severity: serious tags: patch Hello, this is the trivial patch that makes the package build with newer jsonc. Description: Patch to make it build with newer json-c deprecated TRUE/FALSE defines Author: Gianfranco Costamagna Last-Update: 2020-07-31 Index: libu2f-server-1.1.0/u2f-server/core.c === --- libu2f-server-1.1.0.orig/u2f-server/core.c +++ libu2f-server-1.1.0/u2f-server/core.c @@ -37,6 +37,14 @@ #include "b64/cdecode.h" #include "sha256.h" +// not exported anymore by new json-c +#ifndef TRUE +#define TRUE 1 +#endif +#ifndef FALSE +#define FALSE 0 +#endif + #ifdef HAVE_JSON_OBJECT_OBJECT_GET_EX #define u2fs_json_object_object_get(obj, key, value) json_object_object_get_ex(obj, key, &value) #else G.
Bug#966602: libu2f-host: patch for newer json-c
Source: libu2f-host Version: 1.1.10-1 Severity: serious tags: patch Hello, this is the trivial patch that makes the package build with newer jsonc Description: Patch to make it build with newer json-c deprecated TRUE/FALSE defines Author: Gianfranco Costamagna Last-Update: 2020-07-31 --- libu2f-host-1.1.10.orig/u2f-host/u2fmisc.c +++ libu2f-host-1.1.10/u2f-host/u2fmisc.c @@ -26,6 +26,14 @@ #define HID_TIMEOUT 2 #define HID_MAX_TIMEOUT 4096 +// not exported anymore by new json-c +#ifndef TRUE +#define TRUE 1 +#endif +#ifndef FALSE +#define FALSE 0 +#endif + #ifdef HAVE_JSON_OBJECT_OBJECT_GET_EX #define u2fh_json_object_object_get(obj, key, value) json_object_object_get_ex(obj, key, &value) #else G.
Bug#966501: 2.0.3 REST API regression: Failed to parse parameters for /v1.12/libpod/events: unexpected end of JSON input
Control: severity -1 important Hi Martin, On Wed, Jul 29, 2020 at 8:42 AM Martin Pitt wrote: > Package: podman > Version: 2.0.3+dfsg1-1 > Severity: serious > Tags: upsteam fixed-upstream > > Version 2.0.3 breaks the REST API really hard, which breaks cockpit-podman > and > any other API user. This is tracked here: > > https://github.com/containers/podman/issues/7078 > > This has been fixed upstream and will be in 2.0.4. I'd like to block this > version from testing to avoid the regression. > > If you disagree and would rather get this in ASAP (given how young the > package > is still), I'm fine with that as well, and disable the cockpit-podman test > on > debian-testing for a while. > > Thank you for your bugreport. I looked into backporting the change and checked in with my contact upstream. It turns out that this is not the only issue with the REST interface, and neither of them are easy to backport to 2.0.3. A new release will come out soon that should be suitable for cockpit-podman. Cockpit looks like a really cool project. I do need to find some time to play with it, in particular with the upcoming cockpit-podman component. Thanks for packaging it! Are you working full time on "cockpit"? Given that the REST interface is not available in testing (the respective systemd units were only introduced in 2.0.3+dfsg1-1), and podman provides a lot of value even without them, I'd rather have the current package migrate to testing at this point. Having said this, I do really appreciate your bug report and will see to a remedy as soon as it becomes available in the form of a new upstream release. For the time being, I'd recommend disabling the cockpit-podman test for the time being and re-enable it when this bug gets closed properly. Thanks for your understanding. -- regards, Reinhard
Processed: Re: Bug#966501: 2.0.3 REST API regression: Failed to parse parameters for /v1.12/libpod/events: unexpected end of JSON input
Processing control commands: > severity -1 important Bug #966501 [podman] 2.0.3 REST API regression: Failed to parse parameters for /v1.12/libpod/events: unexpected end of JSON input Severity set to 'important' from 'serious' -- 966501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: forked-daapd: ftbfs with GCC-10
Processing control commands: > tags -1 patch Bug #957217 [src:forked-daapd] forked-daapd: ftbfs with GCC-10 Added tag(s) patch. -- 957217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957217 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957217: forked-daapd: ftbfs with GCC-10
control: tags -1 patch Description: Fix build with gcc-10 Author: Gianfranco Costamagna Last-Update: 2020-07-31 --- forked-daapd-26.4+dfsg1.orig/src/input.h +++ forked-daapd-26.4+dfsg1/src/input.h @@ -137,7 +137,7 @@ struct input_definition /* * Input modules should use this to test if playback should end */ -int input_loop_break; +static int input_loop_break; /* * Transfer stream data to the player's input buffer. The input evbuf will be I uploaded this patch in Ubuntu, fixing the FTBFS. (upstream heavily refactored that code, so my suggestion is to move to the new upstream release if possible) G.
Bug#957805: marked as done (siril: ftbfs with GCC-10)
Your message dated Fri, 31 Jul 2020 10:21:40 + with message-id and subject line Bug#957805: fixed in siril 0.9.12-3 has caused the Debian Bug report #957805, regarding siril: ftbfs with GCC-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.) -- 957805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:siril Version: 0.9.12-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 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-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/siril_0.9.12-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 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-10/porting_to.html [...] gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR='"/usr/share/siril"' -DPACKAGE_DOC_DIR='"/usr/share/doc/siril"' -DLOCALEDIR='"/usr/share/locale"' -I/usr/include/opencv4/opencv -I/usr/include/opencv4 -I/usr/include/x86_64-linux-gnu -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/x86_64-linux-gnu -I/usr/include/libpng16-I/usr/include/x86_64-linux-gnu -I../deps/kplot -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-p refix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fopenmp -c -o filters/scnr.o filters/scnr.c gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR='"/usr/share/siril"' -DPACKAGE_DOC_DIR='"/usr/share/doc/siril"' -DLOCALEDIR='"/usr/share/locale"' -I/usr/include/opencv4/opencv -I/usr/include/opencv4 -I/usr/include/x86_64-linux-gnu -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/x86_64-linux-gnu -I/usr/include/libpng16-I/usr/include/x86_64-linux-gnu -I../deps/kplot -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -fdebug-p refix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -fopenmp -c -o filters/wavelets.o filters/wavelets.c gcc -DHAVE_CONFIG_H -I. -I.. -DPACKAGE_DATA_DIR='"/usr/share/siril"' -DPACKAGE_DOC_DIR='"/usr/share/doc/siril"' -DLOCALEDIR='"/usr/share/locale"' -I/usr/include/opencv4/opencv -I/usr/include/opencv4 -I/usr/include/x86_64-linux-gnu -pthread -I/usr/include/gtk-3.0 -I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include -I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/
Bug#964594: marked as done (psensor FTBFS with libmicrohttpd 0.9.71)
Your message dated Fri, 31 Jul 2020 10:20:21 +
with message-id
and subject line Bug#964594: fixed in psensor 1.1.5-1.2
has caused the Debian Bug report #964594,
regarding psensor FTBFS with libmicrohttpd 0.9.71
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.)
--
964594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964594
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: psensor
Version: 1.1.5-1.1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/psensor.html
...
server.c: In function 'main':
server.c:430:21: error: passing argument 5 of 'MHD_start_daemon' from
incompatible pointer type [-Werror=incompatible-pointer-types]
430 | NULL, NULL, &cbk_http_request, server_data.sensors,
| ^
| |
| int (*)(void *, struct MHD_Connection *, const char
*, const char *, const char *, const char *, size_t *, void **) {aka int
(*)(void *, struct MHD_Connection *, const char *, const char *, const char *,
const char *, long unsigned int *, void **)}
In file included from server.c:39:
/usr/include/microhttpd.h:2425:1: note: expected 'MHD_AccessHandlerCallback'
{aka 'enum MHD_Result (*)(void *, struct MHD_Connection *, const char *, const
char *, const char *, const char *, long unsigned int *, void **)'} but
argument is of type 'int (*)(void *, struct MHD_Connection *, const char *,
const char *, const char *, const char *, size_t *, void **)' {aka 'int
(*)(void *, struct MHD_Connection *, const char *, const char *, const char *,
const char *, long unsigned int *, void **)'}
2425 | MHD_start_daemon (unsigned int flags,
| ^~~~
cc1: all warnings being treated as errors
make[4]: *** [Makefile:471: server.o] Error 1
--- End Message ---
--- Begin Message ---
Source: psensor
Source-Version: 1.1.5-1.2
Done: Gianfranco Costamagna
We believe that the bug you reported is fixed in the latest version of
psensor, 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 964...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Gianfranco Costamagna (supplier of updated psensor
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Fri, 31 Jul 2020 12:00:39 +0200
Source: psensor
Binary: psensor psensor-server psensor-common
Architecture: source
Version: 1.1.5-1.2
Distribution: unstable
Urgency: medium
Maintainer: Jean-Philippe Orsini
Changed-By: Gianfranco Costamagna
Description:
psensor- display graphs for monitoring hardware temperature
psensor-common - common files for Psensor and Psensor server
psensor-server - Psensor server for monitoring hardware sensors remotely
Closes: 964594
Changes:
psensor (1.1.5-1.2) unstable; urgency=medium
.
* Non-maintainer upload.
* debian/patches/14.patch:
- adapt to new mhd 0.9.71 with upstream (rebased) patch (Closes: #964594)
Checksums-Sha1:
09adca480ff470f61b638011ffb4bdc62c4e33e2 2319 psensor_1.1.5-1.2.dsc
af1f0f474ac41dc93e5def319178e510d23a9556 8772 psensor_1.1.5-1.2.debian.tar.xz
1ad90c49b7f70246ba4184a02c7c4f909dc28106 17582
psensor_1.1.5-1.2_source.buildinfo
Checksums-Sha256:
266ae6d236626896bc20dc7eb7b4e3533aae0942fcb5110462746f017fd6f191 2319
psensor_1.1.5-1.2.dsc
9777e824efe2bfbbf052a7bc8c4813c1fb54a702e66c051437b45218d4008e17 8772
psensor_1.1.5-1.2.debian.tar.xz
bf535ac7817a502f14aad100633c17bc2a73055bb8752e83345a69639b2fd715 17582
psensor_1.1.5-1.2_source.buildinfo
Files:
51d69ade9ce3bf8bc5736609d24888b8 2319 utils optional psensor_1.1.5-1.2.dsc
e990777194daa06bdcb5755fed0e9600 8772 utils optional
psensor_1.1.5-1.2.debian.tar.xz
89ad4c13205508e11063c333fb466bcd 17582 utils optional
psensor_1.1.5-1.2_source.buildinfo
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAl8j6/0ACgkQ808JdE6f
Xdn7jxAAw2KncOH9YTzYtmzfRzbxw/28r6C9mlSmMSvOrj65ZeRstbP/Ijw/OG9n
eXt+5s5SBw/dxgaqI+jKkijMaUJ+A8FgW8lT+vkjh1D4TFwA05YpwCTvfgxLeRfQ
0V99fjQ2cJhtZvd/S2bmdut6nzW02MU5kII8T4Ry//0q+4fSm1xfGaAK7UELyImQ
CSwBi4SZY65s1h2VaGW9BNQVMm5Ur4fydyCDFr+eYF/xMn5VeTxnBZjyIjStZ
Bug#964594: psensor FTBFS with libmicrohttpd 0.9.71
control: tags -1 patch pending
NMU ongoing
G.
On Thu, 09 Jul 2020 13:03:10 +0300 Adrian Bunk wrote:
> Source: psensor
> Version: 1.1.5-1.1
> Severity: serious
> Tags: ftbfs
>
> https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/psensor.html
>
> ...
> server.c: In function 'main':
> server.c:430:21: error: passing argument 5 of 'MHD_start_daemon' from
> incompatible pointer type [-Werror=incompatible-pointer-types]
> 430 | NULL, NULL, &cbk_http_request, server_data.sensors,
> | ^
> | |
> | int (*)(void *, struct MHD_Connection *, const
> char *, const char *, const char *, const char *, size_t *, void **) {aka int
> (*)(void *, struct MHD_Connection *, const char *, const char *, const char
> *, const char *, long unsigned int *, void **)}
> In file included from server.c:39:
> /usr/include/microhttpd.h:2425:1: note: expected 'MHD_AccessHandlerCallback'
> {aka 'enum MHD_Result (*)(void *, struct MHD_Connection *, const char *,
> const char *, const char *, const char *, long unsigned int *, void **)'} but
> argument is of type 'int (*)(void *, struct MHD_Connection *, const char *,
> const char *, const char *, const char *, size_t *, void **)' {aka 'int
> (*)(void *, struct MHD_Connection *, const char *, const char *, const char
> *, const char *, long unsigned int *, void **)'}
> 2425 | MHD_start_daemon (unsigned int flags,
> | ^~~~
> cc1: all warnings being treated as errors
> make[4]: *** [Makefile:471: server.o] Error 1
>
>
diff -Nru psensor-1.1.5/debian/changelog psensor-1.1.5/debian/changelog
--- psensor-1.1.5/debian/changelog 2019-08-12 15:41:22.0 +0200
+++ psensor-1.1.5/debian/changelog 2020-07-31 12:00:39.0 +0200
@@ -1,3 +1,11 @@
+psensor (1.1.5-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches/14.patch:
+- adapt to new mhd 0.9.71 with upstream (rebased) patch (Closes: #964594)
+
+ -- Gianfranco Costamagna Fri, 31 Jul 2020
12:00:39 +0200
+
psensor (1.1.5-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru psensor-1.1.5/debian/patches/14.patch
psensor-1.1.5/debian/patches/14.patch
--- psensor-1.1.5/debian/patches/14.patch 1970-01-01 01:00:00.0
+0100
+++ psensor-1.1.5/debian/patches/14.patch 2020-07-31 11:56:50.0
+0200
@@ -0,0 +1,34 @@
+From 3e8dfe6f2a4317c4cab3d5afec42abdefa3cc2df Mon Sep 17 00:00:00 2001
+From: Jean-Philippe Orsini
+Date: Fri, 17 Jul 2020 00:10:54 +0200
+Subject: [PATCH 1/7] fix compilation with microhttpd since version 0.9.71
+ which changes the return type of the cbk
+
+--- psensor-1.1.5.orig/src/server/server.c
psensor-1.1.5/src/server/server.c
+@@ -281,13 +281,18 @@ create_response(const char *nurl, const
+ MHD_RESPMEM_MUST_FREE);
+ }
+
+-static int cbk_http_request(void *cls,
+- struct MHD_Connection *connection,
+- const char *url,
+- const char *method,
+- const char *version,
+- const char *upload_data,
+- size_t *upload_data_size, void **ptr)
++#if MHD_VERSION < 0x00097002
++static int
++#else
++static enum MHD_Result
++#endif
++cbk_http_request(void *cls,
++ struct MHD_Connection *connection,
++ const char *url,
++ const char *method,
++ const char *version,
++ const char *upload_data,
++ size_t *upload_data_size, void **ptr)
+ {
+ static int dummy;
+ struct MHD_Response *response;
diff -Nru psensor-1.1.5/debian/patches/series
psensor-1.1.5/debian/patches/series
--- psensor-1.1.5/debian/patches/series 2019-06-30 10:33:04.0 +0200
+++ psensor-1.1.5/debian/patches/series 2020-07-31 11:57:13.0 +0200
@@ -1 +1,2 @@
0001-Update-rsensor.c-drop-is_error-macro-definition.patch
+14.patch
Processed: Re: psensor FTBFS with libmicrohttpd 0.9.71
Processing control commands: > tags -1 patch pending Bug #964594 [src:psensor] psensor FTBFS with libmicrohttpd 0.9.71 Added tag(s) patch and pending. -- 964594: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964594 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: severity of 966398 is important, severity of 966399 is important
Processing commands for cont...@bugs.debian.org: > severity 966398 important Bug #966398 [src:jansson] jansson: Exports symbols in json_* namespace without symbol-versioning Severity set to 'important' from 'serious' > severity 966399 important Bug #966399 [src:json-glib] json-glib: Exports symbols in json_* namespace without symbol-versioning Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 966398: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966398 966399: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966399 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966597: marked as done (multipath-tools: patch for newer json-c)
Your message dated Fri, 31 Jul 2020 09:51:12 + with message-id and subject line Bug#966597: fixed in multipath-tools 0.8.4-3 has caused the Debian Bug report #966597, regarding multipath-tools: patch for newer json-c 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.) -- 966597: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966597 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: multipath-tools Version: 0.8.4-2 Severity: serious tags: patch hello, attached a patch that makes it build with newer json-c Description: Patch to make it build with newer json-c deprecated TRUE/FALSE defines Author: Gianfranco Costamagna Last-Update: 2020-07-31 --- multipath-tools-0.8.4.orig/libdmmp/libdmmp_private.h +++ multipath-tools-0.8.4/libdmmp/libdmmp_private.h @@ -32,6 +32,14 @@ #include #include +// not exported anymore by new json-c +#ifndef TRUE +#define TRUE 1 +#endif +#ifndef FALSE +#define FALSE 0 +#endif + #include "libdmmp/libdmmp.h" #ifdef __cplusplus thanks G. --- End Message --- --- Begin Message --- Source: multipath-tools Source-Version: 0.8.4-3 Done: Chris Hofstaedtler We believe that the bug you reported is fixed in the latest version of multipath-tools, 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 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Chris Hofstaedtler (supplier of updated multipath-tools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 31 Jul 2020 09:31:38 + Source: multipath-tools Architecture: source Version: 0.8.4-3 Distribution: unstable Urgency: medium Maintainer: Debian DM Multipath Team Changed-By: Chris Hofstaedtler Closes: 966597 Changes: multipath-tools (0.8.4-3) unstable; urgency=medium . * [c8c0700] Fix build with newer json-c. Thanks to Gianfranco Costamagna (Closes: #966597) Checksums-Sha1: a438b1a2caa760dfdcc05940e0cab2f2f70f7299 2628 multipath-tools_0.8.4-3.dsc 06521572f5f64d6b3b01c0799cf346fb116d0b2a 34340 multipath-tools_0.8.4-3.debian.tar.xz f17b16cf98e567eda3f1ae6111aa898adc5903e9 5998 multipath-tools_0.8.4-3_source.buildinfo Checksums-Sha256: 4bf3226b8a1350b0511adca73383bc5eb33a3181338ed54e73ccadaabe36e246 2628 multipath-tools_0.8.4-3.dsc 15ad27c025e582f949e5345a596004e4f7133b54e0738749b213477c38229080 34340 multipath-tools_0.8.4-3.debian.tar.xz 810dc6ab7cbb2081e37048444e62a53bd58b52700c03ce21b533045ec31e15f3 5998 multipath-tools_0.8.4-3_source.buildinfo Files: 4b21699c20f093f4c10fec9a63008bf9 2628 admin optional multipath-tools_0.8.4-3.dsc 940ccf0ac13a836f9047ebffbf562f4e 34340 admin optional multipath-tools_0.8.4-3.debian.tar.xz ff55100109437a15df4b54e99d59b6a3 5998 admin optional multipath-tools_0.8.4-3_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAl8j5TcACgkQXBPW25MF LgNbzRAAhjWzSBTVHpXkYRJX1mIBeQAdnlCDgFowmiU4irYbGr8xSmxOkXlH3awm ldZERtrXMI355VNJE+bnHj5OzLC2UHoVmkpg52zM6yhyKQnU0ckA393cv35Qd/k5 +Eal7CRDo4826D/0aLjx6aTGn3ekPIbHM9zLJRVj7f6WXJ7gIgg0jiqdoPkLQuMr GDAQLrPDH3/h+n7Dcr5iKv7XPoxKhlv2FgQgxdvpsLu3fbc2mf8wMnHna4dg9ybA mVrcujedK7uqN4HD2XJM5PWMwmfNigqsdPEOSV2wZ5SAgd8g/DSopRM9mScUoSQx i0HEG9O+92jtJChOoES+VafAKJV/NpH4y7ZBNoU7YxxmG+FeEiKfuctvOnlgb92c iz2QBp+4IDWdNaSzcFkdkDI5A9ed4htO0zRhPnZHddK7Bv3xy3Ev2lUKwDrJYM+Y oU27k3AIAURjk1paiUJIpFuT1KCevh4YO043JiTfMUmgPWilTGjqxB/qIRVKbpbn 9RM5HtwQ21utyxEdI7MgHJ1J7Qn/ECWoHxCmw4mbelJ+AZ8qF52jqWHH2vvwHFqF trvzi/4YPc/ItW47RFFrlEfrX+eK8qWSp58OszjU4adqt9Oblqa8YD00j6cg2GQD dFhMmTkToHuu2wB3zFocSv0S7EhqkLAlEv9nz7KqQOnzdecU7Yo= =0nZo -END PGP SIGNATURE End Message ---
Bug#966600: nfstrace: patch for newer json-c/gcc-10
Hi, On Fri, 31 Jul 2020, at 11:23, Gianfranco Costamagna wrote: > Source: nfstrace > Version: 0.4.3.2+git20180104+6561cf6-1 > Severity: serious > tags: patch > > hello, attached a patch that makes it build with newer json-c/gcc-10 Thanks! Could you please also submit it upstream or should I? -- Cheers, Andrej
Bug#966597: multipath-tools: patch for newer json-c
Hi Gianfranco, * Gianfranco Costamagna [200731 10:30]: > Source: multipath-tools > Version: 0.8.4-2 > Severity: serious > tags: patch > > hello, attached a patch that makes it build with newer json-c Thanks! I'm considering going with a somewhat different patch given TRUE is used only once at all. Should be done soon. Chris
