Bug#969227: FTBFS with new runc 1.0.0~rc92 and libcap2 2.43
On Sunday, 30 August 2020 3:01:34 AM AEST Shengjing Zhu wrote: > Please see the patches attached. Thank you very much! > BTW, is there any instruction to work with the docker.io git repo? > It seems `gbp buildpackage` or `gbp pq` are hard to use with it. Something like the following: https://salsa.debian.org/onlyjob/notes/-/wikis/bp Start with "debian" directory, obtain and extract orig tarballs with 'origtargz' then build with your preferred method (e.g. pbuilder). MUT and complex Golang packages are ridiculously difficult to maintain with GBP... See also https://salsa.debian.org/onlyjob/notes/-/wikis/no-gbp -- Best wishes, Dmitry Smirnov. --- Truth — Something somehow discreditable to someone. -- H. L. Mencken, 1949 --- A study on infectivity of asymptomatic SARS-CoV-2 carriers, concludes weak transmission. "The median contact time for patients was four days and that for family members was five days." -- https://pubmed.ncbi.nlm.nih.gov/32513410/ signature.asc Description: This is a digitally signed message part.
Bug#966189: marked as done (cuneiform: FTBFS with GCC 10: multiple definition of ... due to -fno-common)
Your message dated Sat, 29 Aug 2020 23:48:34 + with message-id and subject line Bug#966189: fixed in cuneiform 1.1.0+dfsg-8 has caused the Debian Bug report #966189, regarding cuneiform: FTBFS with GCC 10: multiple definition of ... due to -fno-common 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.) -- 966189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966189 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cuneiform Version: 1.1.0+dfsg-7.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Hi, cuneiform started to FTBFS when GCC 10 was made the default compiler: [ 31%] Linking CXX shared library librlings.so cd /build/cuneiform-1.1.0+dfsg/obj/cuneiform_src/Kern/rling/sources && /usr/bin/cmake -E cmake_link_script CMakeFiles/rlings.dir/link.txt --verbose=1 /usr/bin/c++ -fPIC -g -O2 -fdebug-prefix-map=/build/cuneiform-1.1.0+dfsg=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++98 -Wno-error -Wl,-Bsymbolic -Wl,-z,relro -Wl,--as-needed -shared -Wl,-soname,librli ngs.so.0 -o librlings.so.1.1.0 CMakeFiles/rlings.dir/cpp/crled.cpp.o CMakeFiles/rlings.dir/cpp/crling.cpp.o CMakeFiles/rlings.dir/cpp/crlmemory.cpp.o CMakeFiles/rlings.dir/cpp/dll.cpp.o CMakeFiles/rlings.dir/cpp/rlcontrol.cpp.o CMakeFiles/rlings.dir/c/rling_m a.c.o CMakeFiles/rlings.dir/c/spel2dic.c.o CMakeFiles/rlings.dir/c/spel2voc.c.o CMakeFiles/rlings.dir/c/spelabc.c.o CMakeFiles/rlings.dir/c/spelart.c.o CMakeFiles/rlings.dir/c/spelbuf.c.o CMakeFiles/rlings.dir/c/spelchk.c.o CMakeFiles/rlings.dir/c/speldat1.c. o CMakeFiles/rlings.dir/c/speldat2.c.o CMakeFiles/rlings.dir/c/speldici.c.o CMakeFiles/rlings.dir/c/speldict.c.o CMakeFiles/rlings.dir/c/speldvoc.c.o CMakeFiles/rlings.dir/c/speledf1.c.o CMakeFiles/rlings.dir/c/speledf2.c.o CMakeFiles/rlings.dir/c/speledio.c. o CMakeFiles/rlings.dir/c/spelfun.c.o CMakeFiles/rlings.dir/c/spelloop.c.o CMakeFiles/rlings.dir/c/spelout.c.o CMakeFiles/rlings.dir/c/spelq.c.o CMakeFiles/rlings.dir/c/spelset.c.o CMakeFiles/rlings.dir/c/spelspec.c.o CMakeFiles/rlings.dir/c/udictini.c.o CMak eFiles/rlings.dir/c/udictuti.c.o -Wl,-rpath,/build/cuneiform-1.1.0+dfsg/obj/cuneiform_src/Kern/cstr:/build/cuneiform-1.1.0+dfsg/obj/cuneiform_src/Kern/cfcompat:/build/cuneiform-1.1.0+dfsg/obj/cuneiform_src/Kern/ccom: ../../cstr/libcstr.so.1.1.0 ../../cfcompa t/libcfcompat.so.1.1.0 ../../ccom/libccom.so.1.1.0 -ldl /usr/bin/ld: CMakeFiles/rlings.dir/c/speldici.c.o:./obj/cuneiform_src/Kern/rling/sources/./cuneiform_src/Kern/rling/sources/c/speldici.c:123: multiple definition of `my_free'; CMakeFiles/rlings.dir/c/rling_ma.c.o:./obj/cuneiform_src/Kern/rling/sources/./cunei form_src/Kern/rling/sources/c/rling_ma.c:110: first defined here /usr/bin/ld: CMakeFiles/rlings.dir/c/speldici.c.o:./obj/cuneiform_src/Kern/rling/sources/./cuneiform_src/Kern/rling/sources/c/speldici.c:122: multiple definition of `my_alloc'; CMakeFiles/rlings.dir/c/rling_ma.c.o:./obj/cuneiform_src/Kern/rling/sources/./cune iform_src/Kern/rling/sources/c/rling_ma.c:109: first defined here More information about the corresponding GCC change can be found here: https://gcc.gnu.org/gcc-10/porting_to.html "Default to -fno-common" Andreas --- End Message --- --- Begin Message --- Source: cuneiform Source-Version: 1.1.0+dfsg-8 Done: Sudip Mukherjee We believe that the bug you reported is fixed in the latest version of cuneiform, 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. Sudip Mukherjee (supplier of updated cuneiform package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Aug 2020 23:41:29 +0100 Source: cuneiform Architecture: source Version: 1.1.0+dfsg-8 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Sudip Mukherjee Closes: 966189 Changes: cuneiform (1.1.0+dfsg-8) unstable; urgency=medium . * QA upload. * Use debhelper-compat. - Update
Bug#957720: marked as done (pyparted: ftbfs with GCC-10)
Your message dated Sat, 29 Aug 2020 23:34:43 + with message-id and subject line Bug#957720: fixed in pyparted 3.11.6-0.1 has caused the Debian Bug report #957720, regarding pyparted: 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.) -- 957720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pyparted Version: 3.11.2-11.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/pyparted_3.11.2-11.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: build/temp.linux-amd64-3.8/src/pyfilesys.o:./include/exceptions.h:33: multiple definition of `DeviceException'; build/temp.linux-amd64-3.8/src/_pedmodule.o:./include/exceptions.h:33: first defined here /usr/bin/ld: build/temp.linux-amd64-3.8/src/pyfilesys.o:./include/exceptions.h:32: multiple definition of `ConstraintException'; build/temp.linux-amd64-3.8/src/_pedmodule.o:./include/exceptions.h:32: first defined here /usr/bin/ld: build/temp.linux-amd64-3.8/src/pyfilesys.o:./include/exceptions.h:31: multiple definition of `CreateException'; build/temp.linux-amd64-3.8/src/_pedmodule.o:./include/exceptions.h:31: first defined here /usr/bin/ld: build/temp.linux-amd64-3.8/src/pyfilesys.o:./include/exceptions.h:30: multiple definition of `AlignmentException'; build/temp.linux-amd64-3.8/src/_pedmodule.o:./include/exceptions.h:30: first defined here /usr/bin/ld: build/temp.linux-amd64-3.8/src/pygeom.o:./include/exceptions.h:31: multiple definition of `CreateException'; build/temp.linux-amd64-3.8/src/_pedmodule.o:./include/exceptions.h:31: first defined here /usr/bin/ld: build/temp.linux-amd64-3.8/src/pygeom.o:./include/exceptions.h:40: multiple definition of `PartedException'; build/temp.linux-amd64-3.8/src/_pedmodule.o:./include/exceptions.h:40: first defined here /usr/bin/ld: build/temp.linux-amd64-3.8/src/pygeom.o:./include/exceptions.h:38: multiple definition of `IOException'; build/temp.linux-amd64-3.8/src/_pedmodule.o:./include/exceptions.h:38: first defined here /usr/bin/ld: build/temp.linux-amd64-3.8/src/pygeom.o:./include/exceptions.h:44: multiple definition of `UnknownTypeException'; build/temp.linux-amd64-3.8/src/_pedmodule.o:./include/exceptions.h:44: first defined here /usr/bin/ld: build/temp.linux-amd64-3.8/src/pygeom.o:./include/exceptions.h:43: multiple definition of `UnknownDeviceException'; build/temp.linux-amd64-3.8/src/_pedmodule.o:./include/exceptions.h:43: first defined here /usr/bin/ld: build/temp.linux-amd64-3.8/src/pygeom.o:./include/exceptions.h:42: multiple definition of `TimerException'; build/temp.linux-amd64-3.8/src/_pedmodule.o:./include/exceptions.h:42: first defined here /usr/bin/ld: build/temp.linux-amd64-3.8/src/pygeom.o:./include/exceptions.h:41: multiple definition of `PartitionException'; build/temp.linux-amd64-3.8/src/_pedmodule.o:./include/exceptions.h:41: first defined here /usr/bin/ld: build/temp.linux-amd64-3.8/src/pygeom.o:./include/exceptions.h:39: multiple definition of `NotNeededException'; build/temp.linux-amd64-3.8/src/_pedmodule.o:./include/exceptions.h:39: first defined here /usr/bin/ld: build/temp.linux-amd64-3.8/src/pygeom.o:./include/exceptions.h:37: multiple definition of `GeometryException'; build/temp.linux-amd64-3.8/src/_pedmodule.o:./include/exceptions.h:37: first defined here /usr/bin/ld:
Bug#956876: marked as done (dulwich: FTBFS on s390x)
Your message dated Sat, 29 Aug 2020 22:33:38 + with message-id and subject line Bug#956876: fixed in dulwich 0.20.6-1 has caused the Debian Bug report #956876, regarding dulwich: FTBFS on s390x 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.) -- 956876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dulwich Version: 0.19.15-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) dulwich failed to build on s390x: https://buildd.debian.org/status/fetch.php?pkg=dulwich=s390x=0.19.15-1%2Bb1=1586776167=0 Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Source: dulwich Source-Version: 0.20.6-1 Done: =?utf-8?q?Jelmer_Vernoo=C4=B3?= We believe that the bug you reported is fixed in the latest version of dulwich, 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 956...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated dulwich package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Aug 2020 22:13:38 + Source: dulwich Architecture: source Version: 0.20.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Python Modules Team Changed-By: Jelmer Vernooij Closes: 956876 Changes: dulwich (0.20.6-1) unstable; urgency=medium . * New upstream release. + Fixes broken branch removal test. Closes: #956876 * Bump standards version to 4.5.0. Checksums-Sha1: 35c0f4b1c721e17aa18a892b4f34df046b272051 2158 dulwich_0.20.6-1.dsc 8b18f12df1e265da3a388bda65f25ebcfd0a08f3 388660 dulwich_0.20.6.orig.tar.gz d84b81f13bdd17dc9df6e0bf88a5a6fb966751a2 629692 dulwich_0.20.6-1.debian.tar.xz d8178bac4c72ff266097fe39b4b7e179a635 7549 dulwich_0.20.6-1_amd64.buildinfo Checksums-Sha256: 133b0ab33352bc91ebeee4a9e66b11b0f62ce7abb16f4e4dc736e1ef8b264d16 2158 dulwich_0.20.6-1.dsc e593f514b8ac740b4ceeb047745b4719bfc9f334904245c6edcb3a9d002f577b 388660 dulwich_0.20.6.orig.tar.gz 74f5dae8d83645a5959319d3760c851bdce0de77bf9ff30a5a75f9a3b88f0f72 629692 dulwich_0.20.6-1.debian.tar.xz cba4126cbee20e6a65b6f6987fdd33301e25131e76f630c2e498db9252ec22da 7549 dulwich_0.20.6-1_amd64.buildinfo Files: 49e8d0d618be388a3486908b64ca994e 2158 python optional dulwich_0.20.6-1.dsc e7f11a8e35db3fd16e848db2899c8ef9 388660 python optional dulwich_0.20.6.orig.tar.gz 88e73609a3a11bec6f0fc3f12187e75d 629692 python optional dulwich_0.20.6-1.debian.tar.xz 5597b80a087f2f7d2ce2476a53b20c95 7549 python optional dulwich_0.20.6-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAl9K1RsACgkQV5wWDUye I+hpQhAAxHc+lcO+my9IBERSE4kext7imnCtkBjGx79YST5qrULonza9j9UtxS5o 3oiE3rtJDWKPJGgXZGnMWfVPOSppGd4OMa/9DC1awofdCImaPJAnnJ8vnjgIAGRt /DPgFUOtnDPT5oKxfZLFc4y6l1hTv9c59Tpu5JtEOSsgC8CYK+I+wlp7IIcnRVgx NKMnMKjR3zelV5EwJELp5bje1R2XY4/m/DvC+BYZUZuI2RFxZShSVgmseKajbn8W Nzqq65R7F8GnDFk3V83EivuEoWQFiio9YVO9cgM7Qsn8dmRMUGYy3BETB5xM2xqY DPYWe5yqnOur+a6HiFNQ6BoPLzYzqstnSf/PH22HSEoFIkD06N9lIf0XaXTIXQzQ RhxisjIx4ElKSJRY6g9E+hk1i6aQxlie3vqPfwQc0o9/1iDzlMGNnSwM+VwSXVUU 9wwERrn3Kx4UA5dwSBelEm3XzCXQH/9tj42ro2LTI78E1gPBS1Crh6/4fZJRFFEZ +YiS2phrr92VImt/az/XIdQespRX5ZJSY3ixpemZMFESLupW43S2WYmilgbRTF7d i2fG9GDC76JBn/I9eq44FZf2N4KNeQUeuBb0sfTSuPxV84yKlhN82XCinKLmWFtQ +ruw1w8sYe2j6lCdF7E/Hn9XA1aBeJow/ffbuBtPYWnS4XVjSGw= =766b -END PGP SIGNATURE End Message ---
Bug#968883: marked as done (mame FTBFS on !x86)
Your message dated Sat, 29 Aug 2020 22:04:43 + with message-id and subject line Bug#968883: fixed in mame 0.224+dfsg.1-1 has caused the Debian Bug report #968883, regarding mame FTBFS on !x86 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.) -- 968883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mame Version: 0.223+dfsg.1-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/logs.php?pkg=mame=0.223%2Bdfsg.1-1=sid Errors look quite different on different architectures. --- End Message --- --- Begin Message --- Source: mame Source-Version: 0.224+dfsg.1-1 Done: Jordi Mallach We believe that the bug you reported is fixed in the latest version of mame, 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 968...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jordi Mallach (supplier of updated mame package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Aug 2020 21:43:12 +0200 Source: mame Architecture: source Version: 0.224+dfsg.1-1 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Jordi Mallach Closes: 968883 Changes: mame (0.224+dfsg.1-1) unstable; urgency=medium . [ Cesare Falco ] * New upstream release. * Updated patches. . [ Jordi Mallach ] * Let the build system figure out FORCE_DRC_C_BACKEND and NOASM (hopefully closes: #968883). Checksums-Sha1: 76ce3336971d11f781b4ba8f04da557479c327e3 2527 mame_0.224+dfsg.1-1.dsc 9ed46fc69f7ef520988aa85e3720f7ade34d3972 138738328 mame_0.224+dfsg.1.orig.tar.xz a2215ab4d31b299033482f205a42433834bccefa 6 mame_0.224+dfsg.1-1.debian.tar.xz b00363d30b3901ab672cb9905f037959c3058076 15718 mame_0.224+dfsg.1-1_amd64.buildinfo Checksums-Sha256: cfddaa23184aa8f46275d74301f758a23092f10aad15fe7dd6d8571f8307a2c3 2527 mame_0.224+dfsg.1-1.dsc 1b3afe7b13d538c44e80a17a0bada0f47a4e2ebbe1b2441cccfc24fe7bef97e9 138738328 mame_0.224+dfsg.1.orig.tar.xz 62df4e8a07794f8b43fc8f2ec8a21011539ce479ec8e096c05655d50a31b87e4 6 mame_0.224+dfsg.1-1.debian.tar.xz 50ff0b47b0981819b9c18d8a93d3380d6684d3a8675249294f7b95b7c7695f6e 15718 mame_0.224+dfsg.1-1_amd64.buildinfo Files: 5e790fb48d4182de612f4860cb3c1431 2527 games optional mame_0.224+dfsg.1-1.dsc 5adbf5b358927a7163ed0f64e0cb1465 138738328 games optional mame_0.224+dfsg.1.orig.tar.xz 85d0661f70f1735f7e9b026127ae49ed 6 games optional mame_0.224+dfsg.1-1.debian.tar.xz bc04765328a15d35c1fc03b647a0632f 15718 games optional mame_0.224+dfsg.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE6BdUhsApKYN8KGoWJVAvb8vjywQFAl9KxkYACgkQJVAvb8vj ywSjwxAAjWQ/JclXnLm8YWrEvtIrWQ8L4/UPwlVOfu4c79QJMH3gF7wpN7IOWvsV 1vz2LG4Sq5gI3HJ56sr4a4hQmMW3HSrSfIv7XCnXWPodl7sHWD4Ce9LTqdm6yyt4 c0+iKs8WdmiI574iebxQMd1JF+OEPTdR2kGzLz/J4Wwn6m4uwRVrxTPWF5HI6LYA Q0agaXkJ1SlRM5mBy8l27GZ4iURNaHOXbSce0m3+7K/X1ovV4plxTXsPlaPWz1kC ajUlx7N7i7APy3Nkr2F8HhF78bYGCRnRBe5ZvOkUGh9JPGccaFbHY2DlSVYQW4uf opjR1J1n0LCVKtQKhJoi2ppbeJZHob8GLBXKW8QtiRfA//0Ovdyeo1CquIylXtqy OYLyRRsmFR4Ihu+oByKd3lErYNsSVEgzAS2AIPClKAqpREmxbIVTySO6o47ShqkM bWCGgMvyhyjH7m6JOkmDE779McPlH8TooiCXyI6C9KeQk0B0GPaLmxy0m9OxgkCw t6qYm2q0tFopvWJ3XGyD+MkpLBKHi+SYcKkkM0zUBLBzGpPjRNDxYq0jaKzTpWgH leKK4LjIa0xcin4QzO30jRh8kUi/J++A/ioN1dxuRRBamtCdLq1TQNwsfK2WkVAY vMTawp8rxG4hmugta8wIFkLc3JSi3F83LP4IXPavHc9Sekt0Hl8= =b8oi -END PGP SIGNATURE End Message ---
Processed: Re: opensc: Fails to build due to missing bash_completion files
Processing commands for cont...@bugs.debian.org: > severity 953533 normal Bug #953533 [src:opensc] opensc: Fails to build due to missing bash_completion files Severity set to 'normal' from 'serious' > thank Stopping processing here. Please contact me if you need assistance. -- 953533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957827: marked as done (spacenavd: ftbfs with GCC-10)
Your message dated Sat, 29 Aug 2020 21:34:49 + with message-id and subject line Bug#957827: fixed in spacenavd 0.7.1-1 has caused the Debian Bug report #957827, regarding spacenavd: 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.) -- 957827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:spacenavd Version: 0.6-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/spacenavd_0.6-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 [...] 93 | read(hotplug_fd, buf, sizeof buf); | ^ gcc -pedantic -Wall -g -O2 -fno-strict-aliasing -I./src -I/usr/local/include `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS` -c src/hotplug_darwin.c -o src/hotplug_darwin.o src/hotplug_darwin.c:44: warning: ISO C forbids an empty translation unit [-Wpedantic] 44 | #endif /* __APPLE__ && __MACH__ */ | gcc -pedantic -Wall -g -O2 -fno-strict-aliasing -I./src -I/usr/local/include `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS` -c src/client.c -o src/client.o gcc -pedantic -Wall -g -O2 -fno-strict-aliasing -I./src -I/usr/local/include `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS` -c src/dev_usb.c -o src/dev_usb.o gcc -pedantic -Wall -g -O2 -fno-strict-aliasing -I./src -I/usr/local/include `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS` -c src/proto_unix.c -o src/proto_unix.o gcc -pedantic -Wall -g -O2 -fno-strict-aliasing -I./src -I/usr/local/include `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS` -c src/kbemu.c -o src/kbemu.o gcc -pedantic -Wall -g -O2 -fno-strict-aliasing -I./src -I/usr/local/include `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS` -c src/proto_x11.c -o src/proto_x11.o gcc -pedantic -Wall -g -O2 -fno-strict-aliasing -I./src -I/usr/local/include `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS` -c src/cfgfile.c -o src/cfgfile.o In file included from /usr/include/string.h:495, from src/cfgfile.c:21: In function ‘strncpy’, inlined from ‘read_cfg’ at src/cfgfile.c:296:4: /usr/include/x86_64-linux-gnu/bits/string_fortified.h:106:10: warning: ‘__builtin_strncpy’ specified bound 4096 equals destination size [-Wstringop-truncation] 106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos (__dest)); | ^~ gcc -pedantic -Wall -g -O2 -fno-strict-aliasing -I./src -I/usr/local/include `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS` -c src/dev_serial.c -o src/dev_serial.o gcc -pedantic -Wall -g -O2 -fno-strict-aliasing -I./src -I/usr/local/include `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS` -c src/xdetect_linux.c -o src/xdetect_linux.o gcc -pedantic -Wall -g -O2 -fno-strict-aliasing -I./src -I/usr/local/include `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS` -c src/dummy_usb.c -o src/dummy_usb.o gcc -pedantic -Wall -g -O2 -fno-strict-aliasing -I./src -I/usr/local/include `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS` -c src/event.c -o src/event.o gcc -pedantic -Wall -g -O2 -fno-strict-aliasing -I./src -I/usr/local/include `dpkg-buildflags --get CFLAGS` `dpkg-buildflags --get CPPFLAGS` -c src/dev_usb_darwin.c -o src/dev_usb_darwin.o gcc -pedantic
Bug#958617: marked as done (spacenavd: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Sat, 29 Aug 2020 21:34:49 + with message-id and subject line Bug#958617: fixed in spacenavd 0.7.1-1 has caused the Debian Bug report #958617, regarding spacenavd: Build-Depends on deprecated dh-systemd which is going away 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.) -- 958617: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958617 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spacenavd Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: dh-systemd-removal Hi, your package spacenavd declares a build dependency on dh-systemd. dh-systemd was merged into debhelper in version 9.20160709 [1] and since stretch, dh-systemd is an empty transitional package. For bullseye we intend to drop this empty transitional package. Once we drop dh-systemd, this bug report will become RC. Please update your package accordingly. The change should be as simple as replacing the build dependency on dh-systemd with a build dependency on debhelper (>= 9.20160709). Regards, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670 --- End Message --- --- Begin Message --- Source: spacenavd Source-Version: 0.7.1-1 Done: Rodolphe Pelloux-Prayer We believe that the bug you reported is fixed in the latest version of spacenavd, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Rodolphe Pelloux-Prayer (supplier of updated spacenavd 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: Wed, 19 Aug 2020 21:14:29 +0200 Source: spacenavd Architecture: source Version: 0.7.1-1 Distribution: unstable Urgency: medium Maintainer: Rodolphe Pelloux-Prayer Changed-By: Rodolphe Pelloux-Prayer Closes: 843097 957827 958617 959833 Changes: spacenavd (0.7.1-1) unstable; urgency=medium . * Make the build reproducible (Thanks Reiner Herrmann). Closes: #843097. * Update Standards-Version to 3.9.8. * Add missing lsb-base dependency. * New upstream version 0.7.1. Closes: #959833. * Fix FTBFS with GCC10. Refs: #957827. - Fixed upstream in 081182f1675bb69eec58d92698f1ba2f23466d3f * Upgrade patches for 0.7.1 release. * Remove dh-systemd dependency. Closes: #958617. * Update docs and compat files. * Bump standards version to 4.5.0. * Move Vcs-* fields to point salsa page. * Add documentation field to systemd service file. * Use https for copyright-format (insecure-copyright-format-uri). Checksums-Sha1: 8512793d8109c6ec90e607783d5bda4c8a87a455 1897 spacenavd_0.7.1-1.dsc 2375dea072be7e805d1a0257e0f22978bbb27ff0 56703 spacenavd_0.7.1.orig.tar.gz 3d23ab63475a98ac41da7fd2094ff5eedf364fd0 6672 spacenavd_0.7.1-1.debian.tar.xz c8b51f82cd939626307fd29e1db54b2a123455c7 6898 spacenavd_0.7.1-1_source.buildinfo Checksums-Sha256: 2f88342d98fefec8c665a5be64e31fccabda375bfd9aaa516328b6f22a5c8bdd 1897 spacenavd_0.7.1-1.dsc 9266e19b847dabc79bac0f16984e6104338021f83c784780e2fb569c41529d2b 56703 spacenavd_0.7.1.orig.tar.gz 8e3d5144f692523181166aa47f507a1bbcf5b8ab816b3623109ea654a62b861b 6672 spacenavd_0.7.1-1.debian.tar.xz 3447ac3a2e346fa3c78289db3652cd6c737bafc874f5abb456dc0fdb3db1efe0 6898 spacenavd_0.7.1-1_source.buildinfo Files: 8840d0e4f27fed7c0032153742b08b41 1897 utils optional spacenavd_0.7.1-1.dsc d88c72a37145fe0011dcb8cbb207cd37 56703 utils optional spacenavd_0.7.1.orig.tar.gz adc28ef5a8961032dd0ed92a7b70d822 6672 utils optional spacenavd_0.7.1-1.debian.tar.xz aacb443e4df33c6057660853b673058d 6898 utils optional spacenavd_0.7.1-1_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEe/X2rDZDH11A3BN6TPKyGPVNrj0FAl9KxcIRHHN1cjVyQGRl Ymlhbi5vcmcACgkQTPKyGPVNrj0R6A//d+nH+/lQdZm2jOTxQiVXJj1CMs9hOKKu ShiRw+dsnuZiD33NDlotmKLrtx5dQbWXkMkCYgLT5YfDKiRk0IlmrJtCW/nYj0of A9SnJ3IRGNV9a7taLeLNll/YEkONP62DntqhLvjaxuSnO/z5uE+mqJkOtPB8K4LX Hiin61dCRuOy9XTcrGS+L+oBWg/A88jmP8YEkYa8x4e+SA70s0vp4AdpOr18NBxp tI0vnq4X/1VQPKUmAl/QWSx1ZMjGWMBJgx9IFMKreVA8/lOF0/ORC4nmEU7tOY4W riZkADQ/+jS7pYVon9vb4ZHcUHm77FlJ+lj4ydsVU5WeyXQe5O7/38I+gr5dw4gC
Bug#953533: opensc: Fails to build due to missing bash_completion files
severity 953533 normal
thank
On Tue, 10 Mar 2020 08:10:06 + "Cirujano Cuesta, Silvano"
wrote:
> Package: opensc
> Version: 0.20.0-3
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
> Tags: ftbfs
>
> Trying to build fails. I've tried following two ways.
>
> I've tried
> apt-get source opensc ; debuild -b -uc -us
> and
> apt-get --build source opensc
>
>
> The error message is:
>
> dh_install: warning: Cannot find (any matches for)
> "debian/tmp/etc/bash_completion.d/*"
> (tried in ., debian/tmp)
> dh_install: warning: opensc missing files:
> debian/tmp/etc/bash_completion.d/*
> dh_install: error: missing files,aborting
> make: *** [debian/rules:4: binary] Error 25
I can reproduce your problem using "debuild" in testing.
But I can't reproduce it using "gbp buildpackage" and cowbuilder
When the package is built with debuild I have:
" OpenSC has been configured with the following options:
[...]
Bash completion: /usr/share/bash-completion/completions
[...] "
But when the package is built with gbp (or the Debian builders) I find:
" OpenSC has been configured with the following options:
[...]
Bash completion: /etc/bash_completion.d
[...] "
The problem is this piece of code in configure.ac:
if test "${completiondir}" = "detect"; then
echo completion ${completiondir}
PKG_CHECK_MODULES([BASH_COMPLETION], [bash-completion >= 2.0],
[completiondir="`pkg-config --variable=completionsdir
bash-completion`"],
[completiondir="${sysconfdir}/bash_completion.d"])
fi
If bash-completion package is installed then the scipt uses:
$ pkg-config --variable=completionsdir bash-completion
that returns:
/usr/share/bash-completion/completions
But if bash-completion is NOT installed then
${sysconfdir}/bash_completion.d i.e. /etc/bash_completion.d is used instead.
If you remove the package bash-completion then the build will succeed.
I changed the priority of this bug since it fails to build only in some
cases.
I wanted to push my patch to https://salsa.debian.org/opensc-team/opensc
but I am not a member of the "opensc-team" group on Salsa.
https://salsa.debian.org/opensc-team
My patch is attached so Eric can apply it.
>From ee128132d5ea8644151d7aa180fe580847de3c28 Mon Sep 17 00:00:00 2001
From: Ludovic Rousseau
Date: Sat, 29 Aug 2020 22:26:24 +0200
Subject: [PATCH] Fix "Fails to build due to missing bash_completion files"
Fix bash_completion path (Closes: #953533)
---
debian/changelog | 9 +
debian/control| 3 ++-
debian/opensc.install | 2 +-
3 files changed, 12 insertions(+), 2 deletions(-)
diff --git a/debian/changelog b/debian/changelog
index 404cedf5..6b72f71e 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,12 @@
+opensc (0.20.0-3.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix "Fails to build due to missing bash_completion files"
+Build-Depends: bash-completion so the correct path is found
+(Closes: #953533)
+
+ -- Ludovic Rousseau Sat, 29 Aug 2020 22:25:43 +0200
+
opensc (0.20.0-3) unstable; urgency=medium
* Fix patch to use /etc/opensc for opensc.conf (Closes: 949229)
diff --git a/debian/control b/debian/control
index 374a55f2..03c11d73 100644
--- a/debian/control
+++ b/debian/control
@@ -3,7 +3,8 @@ Priority: optional
Section: utils
Maintainer: Debian OpenSC Maintainers
Uploaders: Eric Dorland
-Build-Depends: debhelper-compat (= 12),
+Build-Depends: bash-completion,
+ debhelper-compat (= 12),
docbook-xsl,
flex,
help2man,
diff --git a/debian/opensc.install b/debian/opensc.install
index 6213ab66..753806cb 100644
--- a/debian/opensc.install
+++ b/debian/opensc.install
@@ -1,5 +1,5 @@
debian/tmp/usr/bin/*
-debian/tmp/etc/bash_completion.d/* usr/share/bash-completion/completions
+debian/tmp/usr/share/bash-completion/completions
debian/tmp/usr/share/man/man1/*
debian/tmp/usr/share/man/man5/*
--
2.28.0
Bug#952536: Drop support for architectures not supported by upstream?
I can see two options here: 1) drop support for architectures not supported by upstream 2) disable the unsupported architecture check somehow * either by setting the environment variable * by patching out the check in the source code I'm not entirely sure what the right thing is for our users; does etcd actually work on the other platforms and/or do we have the bandwidth to get it to work there, or would it be safer to just exclude them for the moment? Since one can either way set the ETC_UNSUPPORTED_ARCH environment variable, does this warrant severity serious rather than e.g. important? Jelmer
Bug#941175: marked as done (lp-shell: invalid syntax error on start)
Your message dated Sat, 29 Aug 2020 21:03:53 + with message-id and subject line Bug#941175: fixed in lptools 0.2.0-7 has caused the Debian Bug report #941175, regarding lp-shell: invalid syntax error on start to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 941175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: lptools Version: 0.2.0-5 Severity: normal $ lp-shell File "/usr/bin/lp-shell", line 55 except ValueError, err: ^ SyntaxError: invalid syntax Perhaps more python3ing to do :) -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lptools depends on: ii python3 3.7.3-1 ii python3-breezy3.0.1-6 ii python3-launchpadlib 1.10.7-1 ii python3-xdg 0.25-5 ii sensible-utils0.0.12 Versions of packages lptools recommends: ii python3-chameleon 3.6.2-2 pn python3-gtk2 pn python3-indicate Versions of packages lptools suggests: pn python3-tdb -- no debconf information --- End Message --- --- Begin Message --- Source: lptools Source-Version: 0.2.0-7 Done: =?utf-8?q?Jelmer_Vernoo=C4=B3?= We believe that the bug you reported is fixed in the latest version of lptools, 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 941...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jelmer Vernooij (supplier of updated lptools package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Aug 2020 20:36:32 + Source: lptools Architecture: source Version: 0.2.0-7 Distribution: unstable Urgency: medium Maintainer: Nathan Handler Changed-By: Jelmer Vernooij Closes: 941175 Changes: lptools (0.2.0-7) unstable; urgency=medium . [ dann frazier ] * Update patch 02_python3: Also convert /usr/bin/lp-* to Python 3. Conversion performed using 2to3-2.7 with visual inspection and spot testing. Closes: #941175 Checksums-Sha1: 5438e44fc59ef9121cd7c8093996ee074fff8374 1929 lptools_0.2.0-7.dsc c1f831f0bacb3adca6aa65a70333fb4321391a24 15148 lptools_0.2.0-7.debian.tar.xz 9c5de589f9d30e4d41cdbea1e6bccd590a6b6262 5883 lptools_0.2.0-7_amd64.buildinfo Checksums-Sha256: 42145750fe57286af91c92d0e0b87cd34cceac207a743b210a924e2df2b6e570 1929 lptools_0.2.0-7.dsc f01a56fe71304a6bc58072d6f5c85a38d7395ddd5ca69171a9f70853ebf0d928 15148 lptools_0.2.0-7.debian.tar.xz f6db5f9ea01c85033e5fc10e71e0853330646702cd5d8b765d189f1c9c02e0cb 5883 lptools_0.2.0-7_amd64.buildinfo Files: 4a7d3edb4c6674ee80c6413dd2eb9c73 1929 python optional lptools_0.2.0-7.dsc 5fee9abbd6420859d22c6e059f661449 15148 python optional lptools_0.2.0-7.debian.tar.xz 8d2b26cb6d9730f439de5a5ac0e364a8 5883 python optional lptools_0.2.0-7_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEsjhixBXWVlpOhsvXV5wWDUyeI+gFAl9KvSoACgkQV5wWDUye I+gQgw/+PU/Vtgw0GUMuDqKHaoH9YQ2lThNBt57h4KkiKiSVgWQS/4BI2H14fi2M OGTv+MyQrbZlK7Z95qV11EuonkVRrOsi/4uTjmFNeqeCOe60oKYCQWOl8YaVf95h ipn301nXrY00E6XcAdcblg+SYBv706OLARHFmv9aZTR9J5lvTHmKgmZ/7oIk5SfQ NSHnnGTiEClTya2IY2KSN6MvKv2xnmqI2vTnjXC8yYxEgQeSII0lVnQsCXgtODPO ZxDKAudjXs2YDece4ku1rraTDjXM/4KFWC8+nBoMRE/nohoAUg52cbUK+B6AzsO5 uVGyctZf3ZBIiNsSbHeQT0TxLXYjpiqzhKNzQwR58vSyGPM0M92aArGqni0LX6Fn kznZPcM5obwn3JN8dSjUCqez2jkpav7sEc/t4I6VZBrVRHhA5jOqRW8cVveSbjWN /G/s0e6BtKQZZMIcTo+V8+51HfmTkgFeVf9MVAnAn711x5fuyTAatL4zOO0reHMu ZZpZm84UH8hLzdqTeYVhTXMw0A5j7IIvVmfBhCIkSp6pcj4qoKBBRPzzlYcTC7TT Dhkb4Dv+nOFeRLHGBZNsYadzapMcq2+wWPkOWkf3ox7FnCKez9OU4qm1MAjBazev xYFEJSEhswWESAB56HpTwLgkksUq63R1D9zmKgSmBsGQE52uams= =Ms+o -END PGP SIGNATURE End Message ---
Bug#957224: fped: diff for NMU version 0.1+201210-1.2
Control: tags 957224 + patch
Control: tags 957224 + pending
Dear maintainer,
I've prepared an NMU for fped (versioned as 0.1+201210-1.2) and
uploaded it to DELAYED/2. Please feel free to tell me if I
should cancel it.
--
Regards
Sudip
diff -Nru fped-0.1+201210/debian/changelog fped-0.1+201210/debian/changelog
--- fped-0.1+201210/debian/changelog2017-04-04 17:17:39.0 +0100
+++ fped-0.1+201210/debian/changelog2020-08-29 21:32:55.0 +0100
@@ -1,3 +1,10 @@
+fped (0.1+201210-1.2) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix ftbfs with GCC-10. (Closes: #957224)
+
+ -- Sudip Mukherjee Sat, 29 Aug 2020 21:32:55
+0100
+
fped (0.1+201210-1.1) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru fped-0.1+201210/debian/patches/gcc-10.patch
fped-0.1+201210/debian/patches/gcc-10.patch
--- fped-0.1+201210/debian/patches/gcc-10.patch 1970-01-01 01:00:00.0
+0100
+++ fped-0.1+201210/debian/patches/gcc-10.patch 2020-08-29 21:27:13.0
+0100
@@ -0,0 +1,20 @@
+Description: Fix ftbfs with GCC-10
+
+Author: Sudip Mukherjee
+Bug-Debian: https://bugs.debian.org/957224
+Forwarded: no
+
+---
+
+--- fped-0.1+201210.orig/postscript.h
fped-0.1+201210/postscript.h
+@@ -26,7 +26,8 @@ struct postscript_params {
+ int label_vecs;
+ int show_meas;
+ int show_key;
+-} postscript_params;
++};
++extern struct postscript_params postscript_params;
+
+
+ int postscript(FILE *file, const char *one);
diff -Nru fped-0.1+201210/debian/patches/series
fped-0.1+201210/debian/patches/series
--- fped-0.1+201210/debian/patches/series 1970-01-01 01:00:00.0
+0100
+++ fped-0.1+201210/debian/patches/series 2020-08-29 21:26:18.0
+0100
@@ -0,0 +1 @@
+gcc-10.patch
Processed: fped: diff for NMU version 0.1+201210-1.2
Processing control commands: > tags 957224 + patch Bug #957224 [src:fped] fped: ftbfs with GCC-10 Added tag(s) patch. > tags 957224 + pending Bug #957224 [src:fped] fped: ftbfs with GCC-10 Added tag(s) pending. -- 957224: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957224 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 957039
Processing commands for cont...@bugs.debian.org: > # just checked this patch doesn't work > tags 957039 - patch Bug #957039 [src:biloba] biloba: ftbfs with GCC-10 Removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 957039: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957039 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966671: coturn: unlimited number of /var/log/turn_*.log are created
Hi Not the maintainer here, but given coturn is going to be removed from testing otherwise I quickly looked at this. In default install this does not seem to be a problem, turnserver uses the syslog option and logfile settings are commented out. So while there is probably some room of improvement (e.g. introducing a logrotate file, when logfile, vebose and single-log are enabled) the severity of RC might not be warranted. Regards, Salvatore
Processed: severity of 961926 is normal
Processing commands for cont...@bugs.debian.org: > severity 961926 normal Bug #961926 [rr] rr: record fails on i386 Severity set to 'normal' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 961926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961926 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969228: glaurung: Segmentation fault caused by out of bounds access
Package: glaurung
Version: 2.2-3
Severity: grave
Tags: patch
X-Debbugs-Cc: Asher Gordon
Dear Maintainer,
Glaurung segfaults when the 'go' command is used, making it
unusable. For example:
$ glaurung
Glaurung 2.2. Copyright (C) 2004-2008 Tord Romstad.
go
Segmentation fault
This is because of an out of bounds access, fixed by the following
patch:
From 62017d29d816d07513805500d498d8779343e074 Mon Sep 17 00:00:00 2001
From: Asher Gordon
Date: Sat, 29 Aug 2020 12:53:56 -0400
Subject: [PATCH 1/3] Fix buffer overrun, causing a segfault
---
src/evaluate.cpp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/evaluate.cpp b/src/evaluate.cpp
index 72032f0..ac303fa 100644
--- a/src/evaluate.cpp
+++ b/src/evaluate.cpp
@@ -1243,7 +1243,7 @@ namespace {
SafetyTable[i] = Value((int)(100 * a * (i - b)));
}
-for(i = 0; i < 100; i++)
+for(i = 0; i < 99; i++)
if(SafetyTable[i+1] - SafetyTable[i] > maxSlope) {
for(j = i + 1; j < 100; j++)
SafetyTable[j] = SafetyTable[j-1] + Value(maxSlope);
--
2.28.0
I also attempted to send this patch upstream, but I don't know Tord's
current email address (it's not t...@glaurungchess.com; I tried). So I
sent it to Matthew Purland, since he had made the last commit on
https://github.com/phenri/glaurung.
So hopefully, he will be able to apply it upstream, but until then,
please apply this patch in Debian.
Thanks,
Asher
-- System Information:
Debian Release: bullseye/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.7.0-2-amd64 (SMP w/2 CPU threads)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages glaurung depends on:
ii libc6 2.31-3
ii libstdc++6 10.1.0-6
Versions of packages glaurung recommends:
ii polyglot 2.0.4-2+b1
ii xboard4.9.1-2
glaurung suggests no packages.
-- no debconf information
--
One picture is worth 128K words.
I prefer to send and receive mail encrypted. Please send me your
public key, and if you do not have my public key, please let me
know. Thanks.
GPG fingerprint: 38F3 975C D173 4037 B397 8095 D4C9 C4FC 5460 8E68
signature.asc
Description: PGP signature
Bug#966863: marked as done (gmap: FTBFS: ld: gmap_nosimd-dynprog_end.o:./src/dynprog_end.c:112: multiple definition of `homopolymerp'; gmap_nosimd-dynprog_single.o:./src/dynprog_single.c:94: first def
Your message dated Sat, 29 Aug 2020 17:19:03 + with message-id and subject line Bug#966863: fixed in gmap 2020-06-30+ds-2 has caused the Debian Bug report #966863, regarding gmap: FTBFS: ld: gmap_nosimd-dynprog_end.o:./src/dynprog_end.c:112: multiple definition of `homopolymerp'; gmap_nosimd-dynprog_single.o:./src/dynprog_single.c:94: first defined here 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.) -- 966863: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966863 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gmap Version: 2020-06-30+ds-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc -pthread -DTARGET=\"x86_64-pc-linux-gnu\" -DGMAPDB=\"/var/cache/gmap\" > -DLARGE_GENOMES=1 -mpopcnt -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro > -Wl,-z,now -o gmapl.nosimd gmapl_nosimd-except.o gmapl_nosimd-assert.o > gmapl_nosimd-mem.o gmapl_nosimd-intlist.o gmapl_nosimd-uintlist.o > gmapl_nosimd-uint8list.o gmapl_nosimd-list.o gmapl_nosimd-littleendian.o > gmapl_nosimd-bigendian.o gmapl_nosimd-univinterval.o gmapl_nosimd-interval.o > gmapl_nosimd-stopwatch.o gmapl_nosimd-semaphore.o gmapl_nosimd-access.o > gmapl_nosimd-filestring.o gmapl_nosimd-iit-read-univ.o > gmapl_nosimd-iit-read.o gmapl_nosimd-md5.o gmapl_nosimd-bzip2.o > gmapl_nosimd-fopen.o gmapl_nosimd-sequence.o gmapl_nosimd-reader.o > gmapl_nosimd-genomicpos.o gmapl_nosimd-compress.o > gmapl_nosimd-compress-write.o gmapl_nosimd-gbuffer.o gmapl_nosimd-genome.o > gmapl_nosimd-popcount.o gmapl_nosimd-genome_sites.o > gmapl_nosimd-genome-write.o gmapl_nosimd-bitpack64-read.o > gmapl_nosimd-bitpack64-readtwo.o gmapl_nosimd-indexdb.o gmapl_nosimd-oligo.o > gmapl_nosimd-block.o gmapl_nosimd-chrom.o gmapl_nosimd-segmentpos.o > gmapl_nosimd-chrnum.o gmapl_nosimd-uinttable_rh.o gmapl_nosimd-gregion.o > gmapl_nosimd-match.o gmapl_nosimd-matchpool.o gmapl_nosimd-diagnostic.o > gmapl_nosimd-stage1.o gmapl_nosimd-diag.o gmapl_nosimd-diagpool.o > gmapl_nosimd-cmet.o gmapl_nosimd-atoi.o gmapl_nosimd-orderstat.o > gmapl_nosimd-oligoindex_hr.o gmapl_nosimd-transcript.o gmapl_nosimd-intron.o > gmapl_nosimd-maxent.o gmapl_nosimd-maxent_hr.o gmapl_nosimd-pair.o > gmapl_nosimd-pairpool.o gmapl_nosimd-cellpool.o gmapl_nosimd-stage2.o > gmapl_nosimd-doublelist.o gmapl_nosimd-smooth.o > gmapl_nosimd-splicestringpool.o gmapl_nosimd-splicetrie_build.o > gmapl_nosimd-splicetrie.o gmapl_nosimd-boyer-moore.o gmapl_nosimd-dynprog.o > gmapl_nosimd-dynprog_simd.o gmapl_nosimd-dynprog_single.o > gmapl_nosimd-dynprog_genome.o gmapl_nosimd-dynprog_cdna.o > gmapl_nosimd-dynprog_end.o gmapl_nosimd-translation.o gmapl_nosimd-pbinom.o > gmapl_nosimd-changepoint.o gmapl_nosimd-stage3.o gmapl_nosimd-request.o > gmapl_nosimd-result.o gmapl_nosimd-output.o gmapl_nosimd-inbuffer.o > gmapl_nosimd-samheader.o gmapl_nosimd-outbuffer.o gmapl_nosimd-chimera.o > gmapl_nosimd-datadir.o gmapl_nosimd-parserange.o gmapl_nosimd-getline.o > gmapl_nosimd-gmap.o -lz -lbz2 -lm > /usr/bin/ld: gmap_nosimd-dynprog_end.o:./src/dynprog_end.c:112: multiple > definition of `homopolymerp'; > gmap_nosimd-dynprog_single.o:./src/dynprog_single.c:94: first defined here > /usr/bin/ld: gmapl_nosimd-dynprog_end.o:./src/dynprog_end.c:112: multiple > definition of `homopolymerp'; > gmapl_nosimd-dynprog_single.o:./src/dynprog_single.c:94: first defined here > gcc -pthread -DTARGET=\"x86_64-pc-linux-gnu\" -DGMAPDB=\"/var/cache/gmap\" > -DMAX_STACK_READLENGTH=300 -DGSNAP=1 -mpopcnt -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wl,-z,relro -Wl,-z,now -o gsnap.nosimd > gsnap_nosimd-except.o gsnap_nosimd-assert.o gsnap_nosimd-mem.o > gsnap_nosimd-intlist.o gsnap_nosimd-uintlist.o gsnap_nosimd-list.o > gsnap_nosimd-littleendian.o gsnap_nosimd-bigendian.o > gsnap_nosimd-univinterval.o gsnap_nosimd-interval.o gsnap_nosimd-stopwatch.o > gsnap_nosimd-semaphore.o gsnap_nosimd-access.o gsnap_nosimd-filestring.o > gsnap_nosimd-iit-read-univ.o gsnap_nosimd-iit-read.o gsnap_nosimd-bzip2.o > gsnap_nosimd-reader.o gsnap_nosimd-genomicpos.o gsnap_nosimd-compress.o > gsnap_nosimd-genome.o gsnap_nosimd-transcriptome.o gsnap_nosimd-popcount.o > gsnap_nosimd-genome128_hr.o gsnap_nosimd-genome128_consec.o > gsnap_nosimd-genome_sites.o gsnap_nosimd-bitpack64-read.o >
Bug#969227: FTBFS with new runc 1.0.0~rc92 and libcap2 2.43
Package: docker.io
Version: 19.03.12+dfsg1-3
Severity: serious
Please see the patches attached.
BTW, is there any instruction to work with the docker.io git repo?
It seems `gbp buildpackage` or `gbp pq` are hard to use with it.
Description: Fix build with runc 1.0.0~rc92
Author: Shengjing Zhu
Forwarded: not-needed
Last-Update: 2020-08-29
--- docker.io-19.03.12+dfsg1.orig/containerd/vendor/github.com/containerd/cri/pkg/containerd/opts/spec.go
+++ docker.io-19.03.12+dfsg1/containerd/vendor/github.com/containerd/cri/pkg/containerd/opts/spec.go
@@ -421,7 +421,7 @@ func WithDevices(osi osinterface.OS, con
Type: string(dev.Type),
Major: ,
Minor: ,
-Access: dev.Permissions,
+Access: string(dev.Permissions),
})
}
return nil
--- docker.io-19.03.12+dfsg1.orig/engine/daemon/stats/collector_unix.go
+++ docker.io-19.03.12+dfsg1/engine/daemon/stats/collector_unix.go
@@ -8,14 +8,14 @@ import (
"strconv"
"strings"
- "github.com/opencontainers/runc/libcontainer/system"
"golang.org/x/sys/unix"
)
// platformNewStatsCollector performs platform specific initialisation of the
// Collector structure.
func platformNewStatsCollector(s *Collector) {
- s.clockTicksPerSecond = uint64(system.GetClockTicks())
+ // modified from https://github.com/moby/moby/pull/41186
+ s.clockTicksPerSecond = 100
}
const nanoSecondsPerSecond = 1e9
--- docker.io-19.03.12+dfsg1.orig/engine/oci/devices_linux.go
+++ docker.io-19.03.12+dfsg1/engine/oci/devices_linux.go
@@ -31,7 +31,7 @@ func deviceCgroup(d *configs.Device) spe
Type: t,
Major: ,
Minor: ,
- Access: d.Permissions,
+ Access: string(d.Permissions),
}
}
--- docker.io-19.03.12+dfsg1.orig/containerd/sys/proc.go
+++ /dev/null
@@ -1,80 +0,0 @@
-// +build linux
-
-/*
- Copyright The containerd Authors.
-
- Licensed under the Apache License, Version 2.0 (the "License");
- you may not use this file except in compliance with the License.
- You may obtain a copy of the License at
-
- http://www.apache.org/licenses/LICENSE-2.0
-
- Unless required by applicable law or agreed to in writing, software
- distributed under the License is distributed on an "AS IS" BASIS,
- WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- See the License for the specific language governing permissions and
- limitations under the License.
-*/
-
-package sys
-
-import (
- "bufio"
- "fmt"
- "os"
- "strconv"
- "strings"
-
- "github.com/opencontainers/runc/libcontainer/system"
-)
-
-const nanoSecondsPerSecond = 1e9
-
-var clockTicksPerSecond = uint64(system.GetClockTicks())
-
-// GetSystemCPUUsage returns the host system's cpu usage in
-// nanoseconds. An error is returned if the format of the underlying
-// file does not match.
-//
-// Uses /proc/stat defined by POSIX. Looks for the cpu
-// statistics line and then sums up the first seven fields
-// provided. See `man 5 proc` for details on specific field
-// information.
-func GetSystemCPUUsage() (uint64, error) {
- var line string
- f, err := os.Open("/proc/stat")
- if err != nil {
- return 0, err
- }
- bufReader := bufio.NewReaderSize(nil, 128)
- defer func() {
- bufReader.Reset(nil)
- f.Close()
- }()
- bufReader.Reset(f)
- err = nil
- for err == nil {
- line, err = bufReader.ReadString('\n')
- if err != nil {
- break
- }
- parts := strings.Fields(line)
- switch parts[0] {
- case "cpu":
- if len(parts) < 8 {
-return 0, fmt.Errorf("bad format of cpu stats")
- }
- var totalClockTicks uint64
- for _, i := range parts[1:8] {
-v, err := strconv.ParseUint(i, 10, 64)
-if err != nil {
- return 0, fmt.Errorf("error parsing cpu stats")
-}
-totalClockTicks += v
- }
- return (totalClockTicks * nanoSecondsPerSecond) /
-clockTicksPerSecond, nil
- }
- }
- return 0, fmt.Errorf("bad stats format")
-}
Description: Fix build against libcap2 2.43
Author: Shengjing Zhu
Bug: https://github.com/moby/moby/issues/41398
Forwarded: no
Last-Update: 2020-08-29
--- docker.io-19.03.12+dfsg1.orig/engine/pkg/archive/archive_unix_test.go
+++ docker.io-19.03.12+dfsg1/engine/pkg/archive/archive_unix_test.go
@@ -264,7 +264,7 @@ func TestTarUntarWithXattr(t *testing.T)
}
out, err := exec.Command("getcap", filepath.Join(origin, "2")).CombinedOutput()
assert.NilError(t, err, string(out))
- assert.Check(t, is.Contains(string(out), "= cap_block_suspend+ep"), "untar should have kept the 'security.capability' xattr")
+ assert.Check(t, is.Contains(string(out), "cap_block_suspend=ep"), "untar should have kept the 'security.capability' xattr")
}
}
Processed: lowering severity
Processing commands for cont...@bugs.debian.org: > severity 969226 serious Bug #969226 [cryptsetup-suspend] cryptsetup-suspend: missing dependency on /bin/openvt (kbd) Severity set to 'serious' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 969226: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969226 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969226: [pkg-cryptsetup-devel] Bug#969226: cryptsetup-suspend: missing dependency on /bin/openvt (kbd)
Control: -1 severity -1 serious Hi Jochen, On Sat, 29 Aug 2020 at 18:24:44 +0200, Jochen Sprickerhof wrote: > Severity: grave > Justification: renders package unusable > […r > /lib/systemd/system/systemd-suspend.service.d/systemd_cryptsetup-suspend.conf > tries to call /bin/openvt which is in the optional package kbd. cryptsetup-initramfs has ‘Recommends: kbd’ so while the missing dependency in cryptsetup-suspend is a policy violation, in practice it'll work just fine on systems without --no-install-recommends (the default). :-P Cheers, -- Guilhem. signature.asc Description: PGP signature
Bug#969226: cryptsetup-suspend: missing dependency on /bin/openvt (kbd)
Package: cryptsetup-suspend Version: 2:2.3.3-3+exp1 Severity: grave Justification: renders package unusable Hi, /lib/systemd/system/systemd-suspend.service.d/systemd_cryptsetup-suspend.conf tries to call /bin/openvt which is in the optional package kbd. Please add a dependency to make sure it's installed. Thanks for working on this :). Cheers Jochen -- Package-specific info: -- /proc/cmdline root=LABEL=root rw quiet mitigations=off systemd.unified_cgroup_hierarchy=1 add_efi_memmap initrd=\EFI\debian\initrd.img -- /etc/crypttab # -- lsmod Module Size Used by fuse 139264 3 dm_crypt 49152 1 dm_mod163840 3 dm_crypt ctr16384 1 ccm20480 3 uvcvideo 114688 0 algif_aead 16384 0 videobuf2_vmalloc 20480 1 uvcvideo videobuf2_memops 20480 1 videobuf2_vmalloc videobuf2_v4l2 28672 1 uvcvideo videobuf2_common 57344 2 videobuf2_v4l2,uvcvideo cbc16384 0 videodev 266240 3 videobuf2_v4l2,uvcvideo,videobuf2_common des_generic16384 0 libdes 24576 1 des_generic ecb16384 0 mc 57344 4 videodev,videobuf2_v4l2,uvcvideo,videobuf2_common arc4 16384 0 algif_skcipher 16384 0 cmac 16384 0 sha512_ssse3 45056 0 sha512_generic 16384 1 sha512_ssse3 md416384 0 algif_hash 16384 0 af_alg 32768 3 algif_hash,algif_skcipher,algif_aead snd_soc_skl_hda_dsp24576 1 snd_soc_hdac_hdmi 40960 1 snd_soc_skl_hda_dsp snd_soc_dmic 16384 1 snd_hda_codec_hdmi 73728 1 snd_hda_codec_realtek 139264 1 snd_hda_codec_generic94208 1 snd_hda_codec_realtek snd_sof_pci20480 0 snd_sof_intel_hda_common90112 1 snd_sof_pci x86_pkg_temp_thermal20480 0 intel_powerclamp 20480 0 snd_sof_intel_hda 20480 1 snd_sof_intel_hda_common snd_sof_intel_byt 20480 1 snd_sof_pci coretemp 20480 0 snd_sof_intel_ipc 20480 1 snd_sof_intel_byt snd_sof 126976 4 snd_sof_pci,snd_sof_intel_hda_common,snd_sof_intel_byt,snd_sof_intel_ipc snd_sof_xtensa_dsp 16384 2 snd_sof_intel_hda_common,snd_sof_intel_byt intel_rapl_msr 20480 0 snd_soc_skl 184320 0 iwlmvm319488 0 kvm_intel 323584 0 kvm 811008 1 kvm_intel snd_soc_hdac_hda 24576 2 snd_sof_intel_hda_common,snd_soc_skl snd_hda_ext_core 36864 5 snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_soc_skl,snd_sof_intel_hda snd_soc_sst_ipc20480 1 snd_soc_skl snd_soc_sst_dsp40960 1 snd_soc_skl snd_soc_acpi_intel_match45056 3 snd_sof_pci,snd_sof_intel_hda_common,snd_soc_skl snd_soc_acpi 16384 4 snd_soc_acpi_intel_match,snd_sof_intel_hda_common,snd_sof_intel_byt,snd_soc_skl mac80211 909312 1 iwlmvm snd_soc_core 278528 7 snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_soc_skl,snd_soc_dmic,snd_soc_skl_hda_dsp irqbypass 16384 1 kvm snd_compress 32768 1 snd_soc_core joydev 28672 0 rapl 16384 0 i915 2592768 4 intel_cstate 16384 0 binfmt_misc24576 1 libarc416384 2 mac80211,arc4 snd_hda_intel 57344 0 snd_intel_dspcfg 24576 4 snd_hda_intel,snd_sof_pci,snd_sof_intel_hda_common,snd_soc_skl snd_hda_codec 163840 6 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek,snd_soc_hdac_hda,snd_soc_skl_hda_dsp iwlwifi 274432 1 iwlmvm intel_uncore 163840 0 snd_hda_core 106496 12 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_ext_core,snd_hda_codec,snd_hda_codec_realtek,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_soc_hdac_hda,snd_soc_skl,snd_sof_intel_hda,snd_soc_skl_hda_dsp nls_ascii 16384 1 nls_cp437 20480 1 pcspkr 16384 0 efi_pstore 16384 0 snd_hwdep 16384 1 snd_hda_codec evdev 28672 16 snd_pcm 131072 10 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_sof,snd_sof_intel_hda_common,snd_soc_hdac_hdmi,snd_compress,snd_soc_core,snd_soc_skl,snd_hda_core drm_kms_helper249856 1 i915 vfat 20480 1 serio_raw 20480 0 iTCO_wdt 16384 0 mei_me 45056 0 processor_thermal_device20480 0 cfg80211 872448 3 iwlmvm,iwlwifi,mac80211 fat86016 1 vfat iTCO_vendor_support16384 1 iTCO_wdt efivars20480 1 efi_pstore wmi_bmof 16384 0 intel_rapl_common 32768 2 intel_rapl_msr,processor_thermal_device intel_wmi_thunderbolt
Bug#969152: teckit FTBFS on most architectures: symbol differences
Am 28.08.2020 um 10:42 teilte Adrian Bunk mit: Hi all, > ... > 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/libteckit0/DEBIAN/symbols doesn't match > completely debian/libteckit0.symbols > ... > dh_makeshlibs: error: failing due to earlier errors > make: *** [debian/rules:7: binary-arch] Error 25 > I changed the symbols file according to [1]. Now the build is fine on i386, but fails on amd64. It was not that easy, sorry! Hilmar [1] https://www.eyrie.org/~eagle/journal/2012-01/008.html -- sigfault #206401 http://counter.li.org signature.asc Description: OpenPGP digital signature
Bug#965951: marked as done (twms fails to start)
Your message dated Sat, 29 Aug 2020 16:04:56 +
with message-id
and subject line Bug#965951: fixed in twms 0.07z+git20200829+cb7d39a-1
has caused the Debian Bug report #965951,
regarding twms fails to start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
965951: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965951
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: twms
Version: 0.07z-1
Severity: grave
Justification: renders package unusable
Dear sir/madam,
I have installed twms as I would like to server some maps following the wms
standard.
The twms package install flawlessly, but I cannot start the server.
I start the server with:
>systemctl start twms
without messages, but when I check the processes running in the system twms is
not there and also there is no new port open. Checking it status with:
> systemctl status twms
I get the following information:
---
twms.service - twms web map service
Loaded: loaded (/lib/systemd/system/twms.service; enabled; vendor preset:
enabled)
Active: failed (Result: exit-code) since Tue 2020-07-21 13:01:51 CEST; 1s
ago
Process: 3647 ExecStart=/usr/bin/twms $PORT (code=exited, status=1/FAILURE)
Main PID: 3647 (code=exited, status=1/FAILURE)
jul 21 13:01:51 twms[3647]: from twms import *
jul 21 13:01:51 twms[3647]: File "/usr/lib/python3/dist-
packages/twms/twms.py", line 30, in
jul 21 13:01:51 twms[3647]: config = imp.load_source("config",
config_path)
jul 21 13:01:51 twms[3647]: File "/usr/lib/python3.7/imp.py", line 171,
in load_source
jul 21 13:01:51 twms[3647]: module = _load(spec)
jul 21 13:01:51 twms[3647]: File "/etc/twms/twms.conf", line 8, in
jul 21 13:01:51 twms[3647]: import fetchers
jul 21 13:01:51 twms[3647]: ModuleNotFoundError: No module named
'fetchers'
jul 21 13:01:51 systemd[1]: twms.service: Main process exited,
code=exited, status=1/FAILURE
jul 21 13:01:51 systemd[1]: twms.service: Failed with result 'exit-code'.
--
(I have replaced the name of my system with ""
The file fetchers.py is located at
/usr/lib/python3/dist-packages/twms
I have not programmed in python since 10 years ago, I have forgotten a lot of
things, but I think it is a problem with the path where twms is looking for
modules.
I would appreciate all help to fix this problem and have twms working.
I am very happy to perform all the necessary tests to locate and fix the
problem.
Thanks for your great work !!!
Jose
-- System Information:
Debian Release: 10.4
APT prefers stable
APT policy: (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.19.0-9-amd64 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND,
TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=es_ES.utf8, LC_CTYPE=es_ES.utf8 (charmap=UTF-8),
LANGUAGE=es_ES.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages twms depends on:
ii adduser3.118
ii python33.7.3-1
ii python3-pil5.4.1-2+deb10u1
ii python3-webpy 1:0.39+20181101-1
Versions of packages twms recommends:
ii python3-cairo 1.16.2-1+b1
ii python3-pyproj 1.9.6-1
twms suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: twms
Source-Version: 0.07z+git20200829+cb7d39a-1
Done: Andrej Shadura
We believe that the bug you reported is fixed in the latest version of
twms, 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.
Andrej Shadura (supplier of updated twms 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: Sat, 29 Aug 2020 17:42:11 +0200
Source: twms
Architecture: source
Version: 0.07z+git20200829+cb7d39a-1
Distribution: unstable
Urgency: medium
Maintainer: Andrej Shadura
Changed-By: Andrej Shadura
Closes: 958601 965951
Changes:
twms (0.07z+git20200829+cb7d39a-1) unstable;
Bug#958601: marked as done (twms: Build-Depends on deprecated dh-systemd which is going away)
Your message dated Sat, 29 Aug 2020 16:04:56 + with message-id and subject line Bug#958601: fixed in twms 0.07z+git20200829+cb7d39a-1 has caused the Debian Bug report #958601, regarding twms: Build-Depends on deprecated dh-systemd which is going away 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.) -- 958601: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: twms Severity: normal User: pkg-systemd-maintain...@lists.alioth.debian.org Usertags: dh-systemd-removal Hi, your package twms declares a build dependency on dh-systemd. dh-systemd was merged into debhelper in version 9.20160709 [1] and since stretch, dh-systemd is an empty transitional package. For bullseye we intend to drop this empty transitional package. Once we drop dh-systemd, this bug report will become RC. Please update your package accordingly. The change should be as simple as replacing the build dependency on dh-systemd with a build dependency on debhelper (>= 9.20160709). Regards, Michael [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822670 --- End Message --- --- Begin Message --- Source: twms Source-Version: 0.07z+git20200829+cb7d39a-1 Done: Andrej Shadura We believe that the bug you reported is fixed in the latest version of twms, 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 958...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrej Shadura (supplier of updated twms 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: Sat, 29 Aug 2020 17:42:11 +0200 Source: twms Architecture: source Version: 0.07z+git20200829+cb7d39a-1 Distribution: unstable Urgency: medium Maintainer: Andrej Shadura Changed-By: Andrej Shadura Closes: 958601 965951 Changes: twms (0.07z+git20200829+cb7d39a-1) unstable; urgency=medium . * New upstream snapshot. * Watch the upstream Git. * Drop no longer relevant patch (Closes: #965951). * Switch to dh 12 and stop using dh-systemd (Closes: #958601). * Promote cairo and pyproj to dependencies. Checksums-Sha1: 158142fe33a35e070f28d7f4635a715813278197 1754 twms_0.07z+git20200829+cb7d39a-1.dsc f10a52bbcff37ce70a6b285b3018980841737556 26720 twms_0.07z+git20200829+cb7d39a.orig.tar.xz 71b7936416a450acc546b65d3404bd5d46bf94e6 5204 twms_0.07z+git20200829+cb7d39a-1.debian.tar.xz Checksums-Sha256: 37fcfd22de39c4970832cb6a901b72a5576104e0058d9eb0bcbb80afa528ecd4 1754 twms_0.07z+git20200829+cb7d39a-1.dsc e32aa4e11ac90a90771d60d84203a8fe5006b411deadc76a489b9e151eb3a7f1 26720 twms_0.07z+git20200829+cb7d39a.orig.tar.xz 638a8b5fe7a92b80c4289855c824e2b886f3d73b351b4bf78b61c9ebbe9ac3e8 5204 twms_0.07z+git20200829+cb7d39a-1.debian.tar.xz Files: 74095adb61772b262a5bfe1d73b9ca98 1754 science optional twms_0.07z+git20200829+cb7d39a-1.dsc b7e3d2fe333b55ac0bc2bd8a01aa2362 26720 science optional twms_0.07z+git20200829+cb7d39a.orig.tar.xz b7615c5bb4a68b0c17b90446769e3a6f 5204 science optional twms_0.07z+git20200829+cb7d39a-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEeuS9ZL8A0js0NGiOXkCM2RzYOdIFAl9Kd7IACgkQXkCM2RzY OdKeJQf9GY0cn8Es0uYevwxuFWTteujBmYjfSLtl/B5sEuqFoQx0dsx1fN5O09w6 pa3HMeMM1yDjrgdrfawUgSNgL1rphHwyFv00/06Eaq+NnCOwSIzoRr9VCFKNW5wS fZ25HdVaxgetBu9f1V+3krcfzdxByIeWi09bjR474BN2YdhSQVlcI5LvFqmksWMr XHXhaqy1QCYeVcgKpFo/jO+APVujGMGoG1bvmLpYR46gBA+6KE212gknG2kvt6i4 EwGDxfKvqqV3wenIuXsSh9K5ROP5bfxQidycWKZl/a9K3n1I648c5qmj5q8iLbO/ sjnlyK1ENALLdbCGph8oERQUYxXrSQ== =653S -END PGP SIGNATURE End Message ---
Bug#959828: Summing up our IRC discussion on #959828
On 2020-08-16, the Technical Committee was informally (by the means of a single IRC message) notified that we should probably look into bug #959828. We thus discussed it in our monthly meeting, that was held three days later. During our last meeting, we all thought sharing the points we all agreed upon in the meeting would be helpful at this point in the disagreement; if it's not, that's fine, but hopefully it can help make some progress. What follows is not a formal Technical Committee ruling or opinion; full meeting logs can be followed at: http://meetbot.debian.net/debian-ctte/2020/debian-ctte.2020-08-19-17.59.log.html#l-186 First of all, there was consensus amongst all tech-ctte members that the 'systemctl' package (to which we will, for clarity, refer using its full project name, 'docker-systemctl-replacement') declaring "Provides: systemd" is not correct, as the interfaces that define systemd clearly far exceed docker-systemctl-replacement. Several amongst us also showed concern that the package name "systemctl" might be misleading for some users; the package could probably be renamed. For reference, upstream's project name is "docker-systemctl-replacement". Some ideas have been floated, although they might not be complete nor fully discussed, regarding how systemd's functionality could be expressed not only monolithically, but referring to its main interfaces. An example can be found at: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959828#129 The use case for docker-systemctl-replacement is quite legitimate and common; containers will often not need to support a full-fledged init system. And given that php-fpm, the package in quesiton, closely fits the container use case, we feel important to urge the php-fpm maintainers to work constructively to find a suitable way to describe the needed dependencies so that php-fpm can be installed in a containerized system without a full init system. For fullness of references, the bug report tracking the conflict between the systemctl and php-fpm packages is #959174. - Gunnar Wolf Debian Technical Committee member signature.asc Description: PGP signature
Bug#969224: cdimage.debian.org: Error installing Debian 10.5 from flash stick with Extlinux
Please see the installation instructions: https://www.debian.org/releases/stable/installmanual It is not correct to pre-format your install media, and pre-copy other files onto it, before copying the installation .iso The correct instructions for writing a USB (or other) installation medium are in section 4.3 of that installmanual. In particular, the destination target of your dd command should be something similar to /dev/sdb_NOT_ something like /dev/sdb1 --- and don't forget to `sync` after the dd. If you still have trouble, seek help at the #debian IRC channel at oftc.net. On Sat, 2020-08-29 at 17:10 +0300, Сергей Фёдоров wrote: > Package: cdimage.debian.org > Severity: critical > Justification: breaks the whole system > > > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads) > Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), LANGUAGE not set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Created a USB flach stick using the" gparted " MBR-partition table. > GPT-partition table failed to get a working version of the Debian > installation. > Created an Ext4-partition and its label. Set the partition "boot" attribute. > > Created a bootable flash drive: > > # dd conv=notrunc bs=440 count=1 if=/usr/lib/EXTLINUX/mbr. bin of=/dev/xxx > where xxx is the name of the u-VA, for example, sdf. > # extlinux --install "folder path" (for example " /media/u1/UP1/"), where" > UP1 " is partition name > > For Debian 10.4 copied from a folder: > > http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/ > or from (for GTK) > http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/gtk/ > > vmlinuz > initrd.gz > > and copied "debian-10.4.0-amd64-DVD-1.iso" > > or > > For Debian 10.5 copied from the folder: > > http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/ > or from (for GTK) > http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/gtk/ > > vmlinuz > initrd.gz > > and copied "debian-10.5.0-amd64-DVD-1.iso» > > In both cases, when installing Debian from a flash drive, I received the > message: > > Load installer components from an ISO installer. > > No modules were found. This pfobably is due to a mismatch between the kernel > by this version of the installer and the kernel version available in the > archieve. > > and the installation had to be stopped. > > For Debian 10.3 copied from the folder: > > http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/ > or from (for GTK) > http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/gtk/ > > vmlinuz > initrd.gz > > and copied "debian-10.3.0-amd64-DVD-1.iso" > > and everything was established without problems. > > Copy Debian 10.3, 10.4, and 10.5 to a USB stick in the device root, download > with it, the installation of Debian passes without problems. > > For example: > > dd if="./debian-10.5.0-amd64-DVD-1.iso" of=/dev/xxx bs=1M status=progress > where xxx is the name of the u-VA, for example, sdf. > > Installing Debian 10.3, 10.4, and 10.5 from a DVD does not cause these > problems. >
Processed: Re: Bug#969177: debmake: cannot create deb for nodejs modeule
Processing control commands: > severity -1 important Bug #969177 [debmake] debmake: cannot create deb for nodejs modeule Severity set to 'important' from 'grave' -- 969177: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969177 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969177: debmake: cannot create deb for nodejs modeule
Control: severity -1 important Hi, Thanks for the log which helps It only breaks for javascript/nodejs. Javascript/nodejs support is new and needs help. Besides (You shouldn't file a grave RC bug without throurough review against policy.) On Fri, 2020-08-28 at 21:39 +0530, Pirate Praveen wrote: > package: debmake > version: 4.3.2-1 > severity: grave > > Using pretty-ms node module as example. debmake 4.3.2-1 worked. I don"t know how people download such nodejs tarball from where. Please tell me how you did it. Please tell me how so I can test. > (debian-sid)pravi@ilvala2:~/packaging/node-pretty-ms-7.0.0$ debmake > I: set parameters > I: sanity check of parameters > I: pkg="node-pretty-ms", ver="7.0.0", rev="1" > I: *** start packaging in "node-pretty-ms-7.0.0". *** > I: provide node-pretty-ms_7.0.0.orig.tar.gz for non-native Debian > package > I: pwd = "/home/pravi/packaging" > I: Use existing "node-pretty-ms_7.0.0.orig.tar.gz" as upstream > tarball ... "debian/control", debmake.control.control(para), > tutorial=para["tutorial"] > File "/usr/lib/python3/dist-packages/debmake/control.py", line 60, > in > control > desc_long_type = debmake.read.read( > File "/usr/lib/python3/dist-packages/debmake/read.py", line 30, in > read > with open(file, mode="r", encoding="utf-8") as f: > FileNotFoundError: [Errno 2] No such file or directory: > '/usr/share/debmake/extra0desc_long/nodejs' Hahaha, that's my mistake. I forgot to add place holder file. Osamu
Bug#966896: marked as done (fatsort: FTBFS: ld: entrylist.o:./src/options.h:38: multiple definition of `OPT_LOCALE'; fatsort.o:./src/options.h:38: first defined here)
Your message dated Sat, 29 Aug 2020 15:18:54 + with message-id and subject line Bug#966896: fixed in fatsort 1.6.3.622-0.1 has caused the Debian Bug report #966896, regarding fatsort: FTBFS: ld: entrylist.o:./src/options.h:38: multiple definition of `OPT_LOCALE'; fatsort.o:./src/options.h:38: first defined here 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.) -- 966896: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966896 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: fatsort Version: 1.6.2.605-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200802 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > gcc fatsort.o FAT_fs.o deviceio.o endianness.o sig.o entrylist.o errors.o > options.o clusterchain.o sort.o misc.o natstrcmp.o stringlist.o regexlist.o > -o fatsort -Wl,-z,relro -Wl,-z,now -s > /usr/bin/ld: entrylist.o:./src/options.h:38: multiple definition of > `OPT_LOCALE'; fatsort.o:./src/options.h:38: first defined here > /usr/bin/ld: options.o:./src/options.h:38: multiple definition of > `OPT_LOCALE'; fatsort.o:./src/options.h:38: first defined here > /usr/bin/ld: sort.o:./src/options.h:38: multiple definition of `OPT_LOCALE'; > fatsort.o:./src/options.h:38: first defined here > /usr/bin/ld: misc.o:./src/options.h:38: multiple definition of `OPT_LOCALE'; > fatsort.o:./src/options.h:38: first defined here > collect2: error: ld returned 1 exit status The full build log is available from: http://qa-logs.debian.net/2020/08/02/fatsort_1.6.2.605-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: fatsort Source-Version: 1.6.3.622-0.1 Done: Alex Muntada We believe that the bug you reported is fixed in the latest version of fatsort, 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. Alex Muntada (supplier of updated fatsort package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Aug 2020 12:58:14 +0200 Source: fatsort Architecture: source Version: 1.6.3.622-0.1 Distribution: unstable Urgency: medium Maintainer: Jordi Sayol Changed-By: Alex Muntada Closes: 966896 Changes: fatsort (1.6.3.622-0.1) unstable; urgency=medium . * Non-maintainer upload. * New upstream release (Closes: #966896). * debian/rules: build man page before install. Checksums-Sha1: 812e97e28ecc01f343713a0ce6754863d5740afb 1851 fatsort_1.6.3.622-0.1.dsc 96388e48556782522113d691f8301727b91b6c5c 123644 fatsort_1.6.3.622.orig.tar.xz dd2fa9e9595f882f535475feac0cb0a29c896f03 2760 fatsort_1.6.3.622-0.1.debian.tar.xz f6a0a212187efcb17c57151aef92503a450ed85c 5712 fatsort_1.6.3.622-0.1_amd64.buildinfo Checksums-Sha256: 2229e9707d0e718b2568bd3c02d4b969200532bc63fe3e8cfd02fba48d476a06 1851 fatsort_1.6.3.622-0.1.dsc 481c94ea08f6faaafe67594726d70fb3e3d5ac9672745f0034e55134ea5256fc 123644 fatsort_1.6.3.622.orig.tar.xz b9243caa33de5857b4112ba1127a4caf1b0c068b2661f2c8f786eacbfc5db24f 2760 fatsort_1.6.3.622-0.1.debian.tar.xz e042e933a0cd5bc9adbebcd2662fe370910082169428b6c3bea65e8a4bccda78 5712 fatsort_1.6.3.622-0.1_amd64.buildinfo Files: 3cca77930e2d65d8491ca06cf16e0a87 1851 utils optional fatsort_1.6.3.622-0.1.dsc 2129c63465eadf1fef3cc4413e3b60e4 123644 utils optional fatsort_1.6.3.622.orig.tar.xz 35286c45f39003b70a330e9f6f4a3c8c 2760 utils optional fatsort_1.6.3.622-0.1.debian.tar.xz 204af9b8e0980012b40cb465e22a47d3 5712 utils optional fatsort_1.6.3.622-0.1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEaUBwKsbetWW2SKTt466XjoNOXn4FAl9KbooACgkQ466XjoNO Xn6Uyg//Y/MOngmpc4as6Fth/6l7lsyoCf33HYnrLNBge52J4sEvMb8GzfaKax4m
Bug#966896: fatsort: FTBFS: ld: entrylist.o:./src/options.h:38: multiple definition of `OPT_LOCALE'; fatsort.o:./src/options.h:38: first defined here
Upstream already fixed this issue in a newer version. After asking Jordi his permission in private, I've prepared a NMU. Cheers, Alex -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Alex Muntada ⢿⡄⠘⠷⠚⠋ Debian Developer log.alexm.org ⠈⠳⣄ signature.asc Description: PGP signature
Bug#969224: cdimage.debian.org: Error installing Debian 10.5 from flash stick with Extlinux
This is not a well supported method. Just use dd to write a netinst or a DVD image straight to the stick and then boot from it directly. dd if=debian-10.5.0-amd64-DVD-1.iso of=/dev/sdX bs=4M oflag=sync status=progress That will put a bootable partition on the stick and then the install will proceed. You may need to use parted / fdisk afterwards to make the USB usable for any other purpose. This method is destructive of any data already on the stick. On Sat, Aug 29, 2020 at 2:18 PM Сергей Фёдоров wrote: > Package: cdimage.debian.org > Severity: critical > Justification: breaks the whole system > > > > -- System Information: > Debian Release: bullseye/sid > APT prefers unstable > APT policy: (500, 'unstable') > Architecture: amd64 (x86_64) > > Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads) > Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), LANGUAGE not > set > Shell: /bin/sh linked to /usr/bin/dash > Init: systemd (via /run/systemd/system) > LSM: AppArmor: enabled > > Created a USB flach stick using the" gparted " MBR-partition table. > GPT-partition table failed to get a working version of the Debian > installation. > Created an Ext4-partition and its label. Set the partition "boot" > attribute. > > Created a bootable flash drive: > > # dd conv=notrunc bs=440 count=1 if=/usr/lib/EXTLINUX/mbr. bin of=/dev/xxx > where xxx is the name of the u-VA, for example, sdf. > # extlinux --install "folder path" (for example " /media/u1/UP1/"), where" > UP1 " is partition name > > For Debian 10.4 copied from a folder: > > > http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/ > or from (for GTK) > > http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/gtk/ > > vmlinuz > initrd.gz > > and copied "debian-10.4.0-amd64-DVD-1.iso" > > or > > For Debian 10.5 copied from the folder: > > > http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/ > or from (for GTK) > > http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/gtk/ > > vmlinuz > initrd.gz > > and copied "debian-10.5.0-amd64-DVD-1.iso» > > In both cases, when installing Debian from a flash drive, I received the > message: > > Load installer components from an ISO installer. > > No modules were found. This pfobably is due to a mismatch between the > kernel > by this version of the installer and the kernel version available in the > archieve. > > and the installation had to be stopped. > > For Debian 10.3 copied from the folder: > > > http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/ > or from (for GTK) > > http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/gtk/ > > vmlinuz > initrd.gz > > and copied "debian-10.3.0-amd64-DVD-1.iso" > > and everything was established without problems. > > Copy Debian 10.3, 10.4, and 10.5 to a USB stick in the device root, > download > with it, the installation of Debian passes without problems. > > For example: > > dd if="./debian-10.5.0-amd64-DVD-1.iso" of=/dev/xxx bs=1M status=progress > where xxx is the name of the u-VA, for example, sdf. > > Installing Debian 10.3, 10.4, and 10.5 from a DVD does not cause these > problems. > >
Bug#968509: Further crashes under linux-image-4.19.0-10-amd64
Hi Richard, On Sat, Aug 22, 2020 at 12:58:47PM +0100, Richard Kettlewell wrote: > I've had further crashes under 4.19.0-10-amd64 on a second machine. > Again, after reverting to 4.19.0-9-amd64 this second machine seems to be > stable. > > The full logs are at http://www.greenend.org.uk/rjk/junk/crashboth.log, > a version without all the iptables clutter is attached. I suspect this is possibly same as #966846. If so this was fixed in 4.19.134 upstream but followup commits were needed as up to commits in 4.19.140 upstream. Would you be able to test 4.19.142? Regards, Salvatore
Bug#969224: cdimage.debian.org: Error installing Debian 10.5 from flash stick with Extlinux
Package: cdimage.debian.org Severity: critical Justification: breaks the whole system -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-3-amd64 (SMP w/8 CPU threads) Locale: LANG=ru_RU.utf8, LC_CTYPE=ru_RU.utf8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Created a USB flach stick using the" gparted " MBR-partition table. GPT-partition table failed to get a working version of the Debian installation. Created an Ext4-partition and its label. Set the partition "boot" attribute. Created a bootable flash drive: # dd conv=notrunc bs=440 count=1 if=/usr/lib/EXTLINUX/mbr. bin of=/dev/xxx where xxx is the name of the u-VA, for example, sdf. # extlinux --install "folder path" (for example " /media/u1/UP1/"), where" UP1 " is partition name For Debian 10.4 copied from a folder: http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/ or from (for GTK) http://ftp.nl.debian.org/debian/dists/Debian10.4/main/installer-amd64/current/images/hd-media/gtk/ vmlinuz initrd.gz and copied "debian-10.4.0-amd64-DVD-1.iso" or For Debian 10.5 copied from the folder: http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/ or from (for GTK) http://ftp.nl.debian.org/debian/dists/Debian10.5/main/installer-amd64/current/images/hd-media/gtk/ vmlinuz initrd.gz and copied "debian-10.5.0-amd64-DVD-1.iso» In both cases, when installing Debian from a flash drive, I received the message: Load installer components from an ISO installer. No modules were found. This pfobably is due to a mismatch between the kernel by this version of the installer and the kernel version available in the archieve. and the installation had to be stopped. For Debian 10.3 copied from the folder: http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/ or from (for GTK) http://ftp.nl.debian.org/debian/dists/Debian10.3/main/installer-amd64/current/images/hd-media/gtk/ vmlinuz initrd.gz and copied "debian-10.3.0-amd64-DVD-1.iso" and everything was established without problems. Copy Debian 10.3, 10.4, and 10.5 to a USB stick in the device root, download with it, the installation of Debian passes without problems. For example: dd if="./debian-10.5.0-amd64-DVD-1.iso" of=/dev/xxx bs=1M status=progress where xxx is the name of the u-VA, for example, sdf. Installing Debian 10.3, 10.4, and 10.5 from a DVD does not cause these problems.
Bug#969222: cyrus-caldav: hhtp keep 100% CPU after access with Thunderbird
Package: cyrus-caldav Version: 3.2.2-1~bpo10+1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installation of cyrus (3.2.2-1~bpo10+1) including cyrus-caldav on (up-to-date) buster and accessing it with Thunderbird 68.11.0 (with build-in support for CalDAV and CardDAV support by Cardbook 45.1). * What exactly did you do (or not do) that was effective (or ineffective)? I created only the default INBOX for e-mail and the default addressbook and default calendar with Thunderbird (by opening the nonexistend address book and calendar with Thunderbird, which triggers an autocreation). Access both address booke and calendar (I tried both empty ones and with one entry each). * What was the outcome of this action? Until Thunderbird was in usage, anything was ok. However, just after quiting it two httpd processes goes to 100% CPU each and stay until /etc/cyrus-imapd restart. This did not happen using iPAD with Apple standard apps. The is no error indication in syslog. Deactivating Cardbook extension resulted in one httpd session with 100% CPU. * What outcome did you expect instead? No httpd processes at all after quitting Thonderbird. Using cyrus 3.0.8.6+deb10u4 works as expected. I wrote this report after installing it, therefore the template may show wrong information regarding cyrus version. *** End of the template - remove these template lines *** -- System Information: Debian Release: 10.5 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.134 (SMP w/8 CPU cores) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages cyrus-caldav depends on: ii cyrus-common 3.0.8-6+deb10u4 ii dpkg 1.19.7 ii libc6 2.28-10 ii libcom-err2 1.44.5-1+deb10u3 ii libical3 3.0.4-3 ii libjansson4 2.12-1 ii libsasl2-22.1.27+dfsg-1+deb10u1 ii libsqlite3-0 3.27.2-3 ii libssl1.1 1.1.1d-0+deb10u3 ii libwrap0 7.6.q-28 ii libxml2 2.9.4+dfsg1-7+b3 ii zlib1g1:1.2.11.dfsg-1 cyrus-caldav recommends no packages. cyrus-caldav suggests no packages. -- no debconf information
Bug#969218: proposed-RM: paxctld -- RoQA; no longer useful
Package: paxctld Severity: serious Version: 1.2.1-1 Tags: bullseye sid Hi, as far as I understand, paxctld is only useful with the semi-proprietary GRsec kernel patches. As these are now more or less proprietary, paxctld doesn't seem useful in Debian. I therefore suggest to remove paxctld from Debian. I'll reassign this removal request to the ftp.debian.org pseudopackage after some time if there are no objections. Ansgar
Processed: severity of 966992 is normal, tagging 966992
Processing commands for cont...@bugs.debian.org: > severity 966992 normal Bug #966992 [fdisk] Regression in sfdisk Severity set to 'normal' from 'serious' > tags 966992 + upstream confirmed Bug #966992 [fdisk] Regression in sfdisk Added tag(s) confirmed and upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 966992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964973: mesa-opencl-icd: Applications using OpenCL crash with ": CommandLine Error: Option 'polly' registered more than once!".
It seems both libMesaOpenCL.so and libLLVM-10.so links llvm-polly statically, so its static constructor called twice.
Processed: cause: sfdisk
Processing control commands: > reassign -1 fdisk 2.36-2 Bug #966992 [src:nbdkit] nbdkit: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2 Bug reassigned from package 'src:nbdkit' to 'fdisk'. No longer marked as found in versions nbdkit/1.20.5-1. Ignoring request to alter fixed versions of bug #966992 to the same values previously set Bug #966992 [fdisk] nbdkit: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2 Marked as found in versions util-linux/2.36-2. > retitle -1 Regression in sfdisk Bug #966992 [fdisk] nbdkit: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2 Changed Bug title to 'Regression in sfdisk' from 'nbdkit: FTBFS: dh_auto_test: error: make -j1 check VERBOSE=1 returned exit code 2'. -- 966992: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966992: cause: sfdisk
control: reassign -1 fdisk 2.36-2 control: retitle -1 Regression in sfdisk I have traced the cause fo the nbdkit build failures (e.g. [1] to what seems to be a regression in sfdisk that manifests itself in a "No space left on device" error when creating some trivial partitioned disk images. , | $ truncate -s 1G diskfile | $ /sbin/sfdisk diskfile <<"EOF" | 2048 1023 L - | 4096 4095 L - | 8192 8191 L - | EOF | Checking that no-one is using this disk right now ... OK | | Disk diskfile: 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 | | >>> Created a new DOS disklabel with disk identifier 0x2ac58cda. | diskfile1: Created a new partition 1 of type 'Linux' and of size 511.5 KiB. | diskfile2: Created a new partition 2 of type 'Linux' and of size 2 MiB. | diskfile3: No free sectors available. | Failed to add #3 partition: No space left on device | Leaving. ` This worked just fine on Debian/buster (fdisk/2.33.1-0.1). I'll be investigating further. Cheers, -Hilko [1] https://buildd.debian.org/status/fetch.php?pkg=nbdkit=amd64=1.20.6-1=1597140669=0
Bug#969212: libcmark-gfm-extensions-dev: cmark-gfm-core-extensions.h depends on missing config.h
Package: libcmark-gfm-extensions-dev Version: 0.29.0.gfm.0-5 Severity: grave Justification: renders package unusable Dear maintainer, Thanks for fixing bug #968709. While trying to use libcmark-gfm-extensions-dev (v0.29.0.gfm.0-5 from unstable) to build haskell-cmark-gfm, it fails with: /usr/include/cmark-gfm-core-extensions.h:10:10: fatal error: config.h: No such file or directory 10 | #include "config.h" // for bool | ^~ compilation terminated. The problem is that cmark-gfm-core-extensions.h tries to include "config.h" which is not available. Best, -- Ilias
Bug#964668: fakechroot: FTBFS: dh_auto_test: error: make -j4 test VERBOSE=1 returned exit code 2
Hi,
On Thu, 9 Jul 2020 13:10:03 +0200 Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
I backported a commit from upstream that fixes this issue:
https://github.com/dex4er/fakechroot/commit/b42d1fb9538f680af2f31e864c555414ccba842a
and prepared an NMU. Debdiff is attached. I uploaded with a delay, so that you
can still cancel it in case I messed up.
Thanks!
cheers, joschdiff -Nru fakechroot-2.19/debian/changelog fakechroot-2.19/debian/changelog
--- fakechroot-2.19/debian/changelog 2019-01-27 16:34:19.0 +0100
+++ fakechroot-2.19/debian/changelog 2020-08-29 13:06:33.0 +0200
@@ -1,3 +1,11 @@
+fakechroot (2.19-3.3) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * Add support for statx call by cherry-picking upstream commit (closes:
+#964668)
+
+ -- Johannes 'josch' Schauer Sat, 29 Aug 2020 13:06:33 +0200
+
fakechroot (2.19-3.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru fakechroot-2.19/debian/patches/0001-New-statx-function.patch fakechroot-2.19/debian/patches/0001-New-statx-function.patch
--- fakechroot-2.19/debian/patches/0001-New-statx-function.patch 1970-01-01 01:00:00.0 +0100
+++ fakechroot-2.19/debian/patches/0001-New-statx-function.patch 2020-08-29 13:01:36.0 +0200
@@ -0,0 +1,80 @@
+From b42d1fb9538f680af2f31e864c555414ccba842a Mon Sep 17 00:00:00 2001
+From: Piotr Roszatycki
+Date: Mon, 10 Feb 2020 13:59:10 -0800
+Subject: [PATCH] New `statx` function
+
+---
+ NEWS.md | 1 +
+ configure.ac| 1 +
+ src/Makefile.am | 1 +
+ src/statx.c | 44
+ 4 files changed, 47 insertions(+)
+ create mode 100644 src/statx.c
+
+--- a/configure.ac
b/configure.ac
+@@ -265,6 +265,7 @@ AC_CHECK_FUNCS(m4_normalize([
+ statfs64
+ statvfs
+ statvfs64
++statx
+ stpcpy
+ strchrnul
+ strlcpy
+--- a/src/Makefile.am
b/src/Makefile.am
+@@ -151,6 +151,7 @@ libfakechroot_la_SOURCES = \
+ statfs64.c \
+ statvfs.c \
+ statvfs64.c \
++statx.c \
+ stpcpy.c \
+ strchrnul.c \
+ strchrnul.h \
+--- /dev/null
b/src/statx.c
+@@ -0,0 +1,44 @@
++/*
++libfakechroot -- fake chroot environment
++Copyright (c) 2010-2020 Piotr Roszatycki
++
++This library is free software; you can redistribute it and/or
++modify it under the terms of the GNU Lesser General Public
++License as published by the Free Software Foundation; either
++version 2.1 of the License, or (at your option) any later version.
++
++This library is distributed in the hope that it will be useful,
++but WITHOUT ANY WARRANTY; without even the implied warranty of
++MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
++Lesser General Public License for more details.
++
++You should have received a copy of the GNU Lesser General Public
++License along with this library; if not, write to the Free Software
++Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA
++*/
++
++
++#include
++
++#ifdef HAVE_STATX
++
++#define _GNU_SOURCE
++#include
++#include
++#include
++
++#include "libfakechroot.h"
++
++
++wrapper(statx, int, (int dirfd, const char * pathname, int flags, unsigned int mask, struct statx * statxbuf))
++{
++char fakechroot_abspath[FAKECHROOT_PATH_MAX];
++char fakechroot_buf[FAKECHROOT_PATH_MAX];
++debug("statx(%d, \"%s\", %d, %u, )", dirfd, pathname, flags, mask);
++expand_chroot_path_at(dirfd, pathname);
++return nextcall(statx)(dirfd, pathname, flags, mask, statxbuf);
++}
++
++#else
++typedef int empty_translation_unit;
++#endif
diff -Nru fakechroot-2.19/debian/patches/series fakechroot-2.19/debian/patches/series
--- fakechroot-2.19/debian/patches/series 2019-01-27 16:28:35.0 +0100
+++ fakechroot-2.19/debian/patches/series 2020-08-29 13:01:07.0 +0200
@@ -1,2 +1,3 @@
renameat2.patch
disable-jemalloc-test
+0001-New-statx-function.patch
signature.asc
Description: signature
Processed: tagging 936129, tagging 969064
Processing commands for cont...@bugs.debian.org: > tags 936129 + pending Bug #936129 [src:apr-util] apr-util: Python2 removal in sid/bullseye Added tag(s) pending. > tags 969064 + pending Bug #969064 [src:apr-util] apr-util: Cannot fulfill the build dependencies Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 936129: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936129 969064: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969064 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969065: marked as done (apr: Cannot fulfill the build dependencies)
Your message dated Sat, 29 Aug 2020 10:48:27 + with message-id and subject line Bug#969065: fixed in apr 1.7.0-1 has caused the Debian Bug report #969065, regarding apr: Cannot fulfill the build dependencies 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.) -- 969065: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969065 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: apr Version: 1.6.5-1 Severity: serious Tags: ftbfs The following packages have unmet dependencies: python : PreDepends: python-minimal (= 2.7.17-2) but it is not going to be installed Depends: libpython-stdlib (= 2.7.17-2) but it is not going to be installed Depends: python2 (= 2.7.17-2) but it is not going to be installed IIUC the package should either: - switch to python3 - build-depend on python2 instead of python --- End Message --- --- Begin Message --- Source: apr Source-Version: 1.7.0-1 Done: Stefan Fritsch We believe that the bug you reported is fixed in the latest version of apr, 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 969...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefan Fritsch (supplier of updated apr package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 29 Aug 2020 11:42:28 +0200 Source: apr Binary: libapr1 libapr1-dbg libapr1-dev Architecture: source amd64 Version: 1.7.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Apache Maintainers Changed-By: Stefan Fritsch Description: libapr1- Apache Portable Runtime Library libapr1-dbg - Apache Portable Runtime Library - Debugging Symbols libapr1-dev - Apache Portable Runtime Library - Development Headers Closes: 936128 969065 Changes: apr (1.7.0-1) unstable; urgency=medium . * New upstream release * Switch build-depends to python3. Closes: #936128, #969065 Make apr1-dev depend on python3, so that apr-util does not have to. See #936129 Checksums-Sha1: 75b43bdafcf85bcd3f2aeae8d1a3e29817388c45 2297 apr_1.7.0-1.dsc 58ebc7b35efaebb211c0b9df594ab16c4d874234 872238 apr_1.7.0.orig.tar.bz2 60147c78d3a732bafaed11359bbf128b9e9fa61a 801 apr_1.7.0.orig.tar.bz2.asc 5fd17851c11995e19180c9d99582640306753a3d 213344 apr_1.7.0-1.debian.tar.xz ef6e31afea5e74746a3b7f831409102ed23e2a57 7197 apr_1.7.0-1_amd64.buildinfo 8a19add55a56799a0e29d87b2740e40d1101ac26 342284 libapr1-dbg_1.7.0-1_amd64.deb 80b5fd6e34878df5cc9fd0d726a23a26fc8414d4 747524 libapr1-dev_1.7.0-1_amd64.deb c8e56701b72afb9d239983160ec0f248eab1a615 105208 libapr1_1.7.0-1_amd64.deb Checksums-Sha256: 1d22623373c873b82365a7968e8264c7d3d3dde4868bed8b47c6d4a1c577ad42 2297 apr_1.7.0-1.dsc e2e148f0b2e99b8e5c6caa09f6d4fb4dd3e83f744aa72a952f94f5a14436f7ea 872238 apr_1.7.0.orig.tar.bz2 5a6c4e721ed82116d7877254ae11c076014040af2ff816ea15ec81e77a4a7d43 801 apr_1.7.0.orig.tar.bz2.asc d2ed09da7e9bd783fb12e555e02f059916ca02c556e895fad6808570fcf5c703 213344 apr_1.7.0-1.debian.tar.xz dd9f35eca6bddde06206dae83c37fb5ce9f8a14c48dd4bdf9d1b6644adef9207 7197 apr_1.7.0-1_amd64.buildinfo e0e3e0c7195386540afe5d473c5fcd17ce8cba33dadad8ceadb4a9ed4a33c8e7 342284 libapr1-dbg_1.7.0-1_amd64.deb bb1fb9374be6b61726dc3f7dc4e0fbec288926b216c8b6e27408679f68cf7393 747524 libapr1-dev_1.7.0-1_amd64.deb b4865afdc2da49b131bb4df415df9bab469b5c17708d8e860e48b45cb2f3e5c5 105208 libapr1_1.7.0-1_amd64.deb Files: 67f5457564d2b3a401c1b9880dcdc202 2297 libs optional apr_1.7.0-1.dsc 7a14a83d664e87599ea25ff4432e48a7 872238 libs optional apr_1.7.0.orig.tar.bz2 48890a94b2002090cf1b2379721b7eea 801 libs optional apr_1.7.0.orig.tar.bz2.asc 7a67e1f7c172ec6d585ca6dad3b06547 213344 libs optional apr_1.7.0-1.debian.tar.xz 18852dd4f01e6f18a8f89d99930cf806 7197 libs optional apr_1.7.0-1_amd64.buildinfo 3a054e187a7a90f8f42c212f92fe5b10 342284 debug optional libapr1-dbg_1.7.0-1_amd64.deb 5df8f0f5b7cd85f4c4062aba620752e2 747524 libdevel optional libapr1-dev_1.7.0-1_amd64.deb d328611c1607f4ac62dee5cddf364c02 105208 libs optional libapr1_1.7.0-1_amd64.deb -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEOpiNza8JqByyYYsxxodfNUHO/eAFAl9KLlcACgkQxodfNUHO
Processed: Re: Bug#969196: zimlib: symbols updates for architectures built with -O3
Processing control commands: > severity -1 important Bug #969196 [src:zimlib] zimlib: symbols updates for architectures built with -O3 Severity set to 'important' from 'serious' -- 969196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#969196: zimlib: symbols updates for architectures built with -O3
Control: severity -1 important On 2020-08-29 09:47:28 +0200, Gianfranco Costamagna wrote: > Source: zimlib > Version: 6.2.0-2 > Severity: serious > tags: patch > > Hello, zimlib symbols file seems to be really difficult to maintain, breaking > on each icu upload, each new gcc upload, > different gcc optimization levels (such as -O2 and -O3) and so on. This doesn't seem to affect the current upload as it built on all release architectures. Why do you think that is a serious issue? Cheers > > Somebody thinks that symbols files for c++ applications are a waste of time, > but I'm sending you another patch that fixes the issue for now, by adding > some symbols, and marking some other as optional > https://wiki.debian.org/UsingSymbolsFiles > > > diff -Nru zimlib-6.2.0/debian/changelog zimlib-6.2.0/debian/changelog > --- zimlib-6.2.0/debian/changelog 2020-08-28 07:35:20.0 + > +++ zimlib-6.2.0/debian/changelog 2020-08-29 07:43:31.0 + > @@ -1,3 +1,9 @@ > +zimlib (6.2.0-2ubuntu1) groovy; urgency=medium > + > + * Refresh symbols > + > + -- Gianfranco Costamagna Sat, 29 Aug 2020 > 09:43:31 +0200 > + > zimlib (6.2.0-2) unstable; urgency=medium > >* Upload to unstable > diff -Nru zimlib-6.2.0/debian/libzim6.symbols > zimlib-6.2.0/debian/libzim6.symbols > --- zimlib-6.2.0/debian/libzim6.symbols 2020-08-28 06:40:45.0 > + > +++ zimlib-6.2.0/debian/libzim6.symbols 2020-08-29 07:43:30.0 > + > @@ -138,7 +138,7 @@ > _ZN3zim14TemplateParser15state_token_endEc@Base 6.0.2 > _ZN3zim14TemplateParser5flushEv@Base 6.0.2 > _ZN3zim14TemplateParser8state_ltEc@Base 6.0.2 > - _ZN3zim15search_iterator12InternalData11get_articleEv@Base 6.2.0 > + > (optional=templinst)_ZN3zim15search_iterator12InternalData11get_articleEv@Base > 6.2.0 > _ZN3zim15search_iteratorC1EOS0_@Base 6.0.2 > _ZN3zim15search_iteratorC1EPNS0_12InternalDataE@Base 6.0.2 > _ZN3zim15search_iteratorC1ERKS0_@Base 6.0.2 > @@ -185,9 +185,9 @@ > > _ZN3zim4unix2FS13makeDirectoryERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 6.0.2 > > _ZN3zim4unix2FS4joinERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base > 6.0.2 > > _ZN3zim4unix2FS6removeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 6.0.2 > - > _ZN3zim4unix2FS6renameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base > 6.0.2 > - > _ZN3zim4unix2FS8openFileERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 6.0.2 > - > _ZN3zim4unix2FS9removeDirERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 6.0.2 > + > (optional=templinst)_ZN3zim4unix2FS6renameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base > 6.0.2 > + > (optional=templinst)_ZN3zim4unix2FS8openFileERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 6.0.2 > + > (optional=templinst)_ZN3zim4unix2FS9removeDirERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 6.0.2 > #MISSING: 6.2.0# > (optional=templinst|arch=!riscv64)_ZN3zim5CacheINS_15article_index_tESt10shared_ptrIKNS_6DirentEEE3putERKS1_RKS5_@Base > 6.0.2 > #MISSING: 6.2.0# > (optional=templinst|arch=!riscv64)_ZN3zim5CacheINS_15cluster_index_tESt10shared_ptrINS_7ClusterEEE3putERKS1_RKS4_@Base > 6.0.2 > > (optional=templinst)_ZN3zim5findxINS_8FileImplEEESt4pairIbNS_15article_index_tEERT_cRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 6.2.0 > @@ -343,6 +343,8 @@ > > _ZN3zim8FileImplC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 6.0.2 > _ZN3zim8FileImplD1Ev@Base 6.0.2 > _ZN3zim8FileImplD2Ev@Base 6.0.2 > + > (optional=templinst)_ZN3zim8FilePartINS_4unix2FSEEC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 6.2.0-2 > + > (optional=templinst)_ZN3zim8FilePartINS_4unix2FSEEC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 6.2.0-2 > #MISSING: 6.1.3# _ZN3zim8ZIP_INFO4nameB5cxx11E@Base 6.0.2 > _ZN3zim8envValueEPKcj@Base 6.0.2 > #MISSING: 6.1.3# _ZN3zim9LZMA_INFO4nameB5cxx11E@Base 6.0.2 > @@ -377,6 +379,8 @@ > (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED0Ev@Base 6.1.3 > (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED1Ev@Base 6.1.3 > (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED2Ev@Base 6.1.3 > + (optional=templinst)_ZN6Xapian13LatLongCoordsC1ERKNS_12LatLongCoordE@Base > 6.2.0-2 > + (optional=templinst)_ZN6Xapian13LatLongCoordsC2ERKNS_12LatLongCoordE@Base > 6.2.0-2 > > (optional=templinst)_ZN6Xapian8Internal13intrusive_ptrINS_5Query8InternalEED1Ev@Base > 6.2.0 > > (optional=templinst)_ZN6Xapian8Internal13intrusive_ptrINS_5Query8InternalEED2Ev@Base > 6.2.0 > #MISSING: 6.1.3# > (optional=templinst|arch=!amd64)_ZN6icu_6314StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIc6AppendEPKci@Base > 6.0.2 > @@ -651,7 +655,7 @@ > (optional=templinst|arch=!armel >
Bug#953533: Additional information
Eric, I do plan to fix this issue and upload a fixed OpenSC to Debian. I will do an delayed upload to you can react if you want. https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#delayed-incoming Bye On Wed, 11 Mar 2020 11:38:58 + "Cirujano Cuesta, Silvano" wrote: Sorry, I attached a wrong patch to my previous e-mail. Attached to this message I send a patch that works for me. -- Dr. Ludovic Rousseau
Bug#969206: redmine: Could not find gem 'rails (~> 5.2.2)' in any of the gem sources listed in your Gemfile
Package: redmine Version: 4.0.7-1 Severity: serious User: pkg-ruby-extras-maintain...@lists.alioth.debian.org Usertags: rails6-transition redmine autopkgtest fails with rails 6. Full log https://ci.debian.net/data/autopkgtest/testing/amd64/r/redmine/6840219/log.gz
Processed: unarchiving 949793, fixed 949793 in shlibs/0.94, notfixed 949793 in shlibs/0.89
Processing commands for cont...@bugs.debian.org:
> unarchive 949793
Bug #949793 {Done: Jonas Smedegaard } [src:d-shlibs] dh-shlibs
fails for Python 3.8 libs
Unarchived Bug 949793
> fixed 949793 shlibs/0.94
Bug #949793 {Done: Jonas Smedegaard } [src:d-shlibs] dh-shlibs
fails for Python 3.8 libs
The source shlibs and version 0.94 do not appear to match any binary packages
Marked as fixed in versions shlibs/0.94.
> notfixed 949793 shlibs/0.89
Bug #949793 {Done: Jonas Smedegaard } [src:d-shlibs] dh-shlibs
fails for Python 3.8 libs
The source shlibs and version 0.89 do not appear to match any binary packages
Ignoring request to alter fixed versions of bug #949793 to the same values
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed (with 1 error): forcibly merging 949793 969199
Processing commands for cont...@bugs.debian.org:
> forcemerge 949793 969199
Bug #949793 {Done: Jonas Smedegaard } [src:d-shlibs] dh-shlibs
fails for Python 3.8 libs
Unable to merge bugs because:
package of #969199 is 'd-shlibs' not 'src:d-shlibs'
Failed to forcibly merge 949793: Did not alter merged bugs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
949793: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949793
969199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#952496: marked as done (python3-whiteboard, depends on package that is not in Debian.)
Your message dated Sat, 29 Aug 2020 07:51:34 + with message-id and subject line Bug#952496: fixed in python-whiteboard 1.0+git20170915-5 has caused the Debian Bug report #952496, regarding python3-whiteboard, depends on package that is not in Debian. 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.) -- 952496: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952496 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-whiteboard Version: 1.0+git20170915-3 Severity: serious python3-whiteboard depends on python3-cwiid, however I can't find any evidence of this package existing, it's not in debian, it doesn't appear to be in new (at least searching new for cwiid doesn't show anything) and my google searches aren't turning anything up either. --- End Message --- --- Begin Message --- Source: python-whiteboard Source-Version: 1.0+git20170915-5 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of python-whiteboard, 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 952...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated python-whiteboard 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: Sat, 29 Aug 2020 09:27:52 +0200 Source: python-whiteboard Architecture: source Version: 1.0+git20170915-5 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Closes: 952496 Changes: python-whiteboard (1.0+git20170915-5) unstable; urgency=medium . * upload the package once more, this Closes: #952496, since the dependency python3-cwiid does exist in debian. Checksums-Sha1: 6a2f76b0a1cd6c655a3743a9b8b02a5afc81dc41 2110 python-whiteboard_1.0+git20170915-5.dsc 6ca5a7c9fd997dfd36347b54e58e002596ee162e 6740 python-whiteboard_1.0+git20170915-5.debian.tar.xz a23574779269b9f1564b91722b737bb3fe9162e6 11401 python-whiteboard_1.0+git20170915-5_source.buildinfo Checksums-Sha256: 6e8054f71c9246ae543dffd76119f5c7a301a75bd0d01c26123396e2e292165f 2110 python-whiteboard_1.0+git20170915-5.dsc 25ad3cc49cdf816d751590c78cca300d0d5bf079be50a0374b27150dfaafec8e 6740 python-whiteboard_1.0+git20170915-5.debian.tar.xz 904c0198648aa72fc9b96478a4a514b74cc8f64f59cca4457b8e136126a75e02 11401 python-whiteboard_1.0+git20170915-5_source.buildinfo Files: 5190b60ccd84f9372931feaa277c1774 2110 python optional python-whiteboard_1.0+git20170915-5.dsc 279fecae350a10bd88bdd4c32ce33379 6740 python optional python-whiteboard_1.0+git20170915-5.debian.tar.xz 47738e120ee74ff9023ff961bff3f15c 11401 python optional python-whiteboard_1.0+git20170915-5_source.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCAAyFiEEM0CzZP9nFT+3zK6FHCgWkHE2rjkFAl9KA8MUHGdlb3JnZXNr QGRlYmlhbi5vcmcACgkQHCgWkHE2rjk4KA//ZbPOAepA2Hfheb3npMT/R2BPAuRq k0k97aLKnAPGmn30ivCPY0QYicXZRpy7+ynuqt5PAL0yxO9nQm9q9UmJLURqvWBT tPDANOMlwWrN1xr1w/rTOOk75KwThdN/iJdfhoIVrpA8oKt5u68nAnb3LZm/YPsL PdPy/IOvQE69RZa73UEaTb1Y80U0A7yReABWxHUgyYyM94EK+mzeBDb8argBwFQG nIuLzTz5CIchj7PbyserzKY7T4/srZw2ZLkDsrAOexAIAfnrbCKhgydHd/9z+OtZ mcPbSkKZSDMlSBvkcdJEJTBZsbslqCPu9AeByTB/BMxB515BusrQ4fw8rqlKb+Pv 8aGJ6thgmfANdeELpSjfcGOEx+SsL1g5WazcKMsqSrC2G/siiHP6xxDuRk7GW7Th qH+GgdLoMw2R+gBDYSyuGBsZpCdn3d287k4ot835sBEljFudLWgVPgBaMITwRxQk 5KSO5cPN+mDIdoVTIJdBRsOo9yLjXzTl06+OptixOxOkINFnpPu4K8C7I1Orw83I njKP32zWVfku2kCgJGClQtdr2RGFNXM4kvgaFK00+oX9fdL1UZEEwcpSErzWKTdq rnxY/EuCnC7h40hsBdj2ugrzdwQ2LNUWJ7+MqPMzY39uNeE2COKfJ+ub2JLrYi+7 OoRHvqOL1i1zY2s= =z3bX -END PGP SIGNATURE End Message ---
Bug#969196: zimlib: symbols updates for architectures built with -O3
Source: zimlib Version: 6.2.0-2 Severity: serious tags: patch Hello, zimlib symbols file seems to be really difficult to maintain, breaking on each icu upload, each new gcc upload, different gcc optimization levels (such as -O2 and -O3) and so on. Somebody thinks that symbols files for c++ applications are a waste of time, but I'm sending you another patch that fixes the issue for now, by adding some symbols, and marking some other as optional https://wiki.debian.org/UsingSymbolsFiles diff -Nru zimlib-6.2.0/debian/changelog zimlib-6.2.0/debian/changelog --- zimlib-6.2.0/debian/changelog 2020-08-28 07:35:20.0 + +++ zimlib-6.2.0/debian/changelog 2020-08-29 07:43:31.0 + @@ -1,3 +1,9 @@ +zimlib (6.2.0-2ubuntu1) groovy; urgency=medium + + * Refresh symbols + + -- Gianfranco Costamagna Sat, 29 Aug 2020 09:43:31 +0200 + zimlib (6.2.0-2) unstable; urgency=medium * Upload to unstable diff -Nru zimlib-6.2.0/debian/libzim6.symbols zimlib-6.2.0/debian/libzim6.symbols --- zimlib-6.2.0/debian/libzim6.symbols 2020-08-28 06:40:45.0 + +++ zimlib-6.2.0/debian/libzim6.symbols 2020-08-29 07:43:30.0 + @@ -138,7 +138,7 @@ _ZN3zim14TemplateParser15state_token_endEc@Base 6.0.2 _ZN3zim14TemplateParser5flushEv@Base 6.0.2 _ZN3zim14TemplateParser8state_ltEc@Base 6.0.2 - _ZN3zim15search_iterator12InternalData11get_articleEv@Base 6.2.0 + (optional=templinst)_ZN3zim15search_iterator12InternalData11get_articleEv@Base 6.2.0 _ZN3zim15search_iteratorC1EOS0_@Base 6.0.2 _ZN3zim15search_iteratorC1EPNS0_12InternalDataE@Base 6.0.2 _ZN3zim15search_iteratorC1ERKS0_@Base 6.0.2 @@ -185,9 +185,9 @@ _ZN3zim4unix2FS13makeDirectoryERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 6.0.2 _ZN3zim4unix2FS4joinERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base 6.0.2 _ZN3zim4unix2FS6removeERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 6.0.2 - _ZN3zim4unix2FS6renameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base 6.0.2 - _ZN3zim4unix2FS8openFileERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 6.0.2 - _ZN3zim4unix2FS9removeDirERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 6.0.2 + (optional=templinst)_ZN3zim4unix2FS6renameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES9_@Base 6.0.2 + (optional=templinst)_ZN3zim4unix2FS8openFileERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 6.0.2 + (optional=templinst)_ZN3zim4unix2FS9removeDirERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 6.0.2 #MISSING: 6.2.0# (optional=templinst|arch=!riscv64)_ZN3zim5CacheINS_15article_index_tESt10shared_ptrIKNS_6DirentEEE3putERKS1_RKS5_@Base 6.0.2 #MISSING: 6.2.0# (optional=templinst|arch=!riscv64)_ZN3zim5CacheINS_15cluster_index_tESt10shared_ptrINS_7ClusterEEE3putERKS1_RKS4_@Base 6.0.2 (optional=templinst)_ZN3zim5findxINS_8FileImplEEESt4pairIbNS_15article_index_tEERT_cRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 6.2.0 @@ -343,6 +343,8 @@ _ZN3zim8FileImplC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 6.0.2 _ZN3zim8FileImplD1Ev@Base 6.0.2 _ZN3zim8FileImplD2Ev@Base 6.0.2 + (optional=templinst)_ZN3zim8FilePartINS_4unix2FSEEC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 6.2.0-2 + (optional=templinst)_ZN3zim8FilePartINS_4unix2FSEEC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 6.2.0-2 #MISSING: 6.1.3# _ZN3zim8ZIP_INFO4nameB5cxx11E@Base 6.0.2 _ZN3zim8envValueEPKcj@Base 6.0.2 #MISSING: 6.1.3# _ZN3zim9LZMA_INFO4nameB5cxx11E@Base 6.0.2 @@ -377,6 +379,8 @@ (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED0Ev@Base 6.1.3 (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED1Ev@Base 6.1.3 (optional=templinst)_ZN5QueueIPN3zim6writer7ClusterEED2Ev@Base 6.1.3 + (optional=templinst)_ZN6Xapian13LatLongCoordsC1ERKNS_12LatLongCoordE@Base 6.2.0-2 + (optional=templinst)_ZN6Xapian13LatLongCoordsC2ERKNS_12LatLongCoordE@Base 6.2.0-2 (optional=templinst)_ZN6Xapian8Internal13intrusive_ptrINS_5Query8InternalEED1Ev@Base 6.2.0 (optional=templinst)_ZN6Xapian8Internal13intrusive_ptrINS_5Query8InternalEED2Ev@Base 6.2.0 #MISSING: 6.1.3# (optional=templinst|arch=!amd64)_ZN6icu_6314StringByteSinkINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIc6AppendEPKci@Base 6.0.2 @@ -651,7 +655,7 @@ (optional=templinst|arch=!armel !riscv64)_ZNSt12__shared_ptrIN3zim12MemoryBufferELN9__gnu_cxx12_Lock_policyE2EEC2ISaIS1_EJRNS0_7zsize_tSt20_Sp_alloc_shared_tagIT_EDpOT0_@Base 6.2.0 _ZNSt12system_errorC1ESt10error_codeRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 6.0.2 _ZNSt12system_errorC2ESt10error_codeRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 6.0.2 - (arch=!amd64 !arm64 !hppa !mipsel !sh4 !x32)_ZNSt13__future_base13_State_baseV216_M_break_promiseESt10unique_ptrINS_12_Result_baseENS2_8_DeleterEE@Base 6.2.0 + (arch=!amd64 !arm64 !hppa !mipsel !ppc64el
