Bug#936873: libhdate: diff for NMU version 1.6.02-2.1
On 2020-08-06 02:13, Lior Kaplan wrote: >We're still alive/here Excellent to hear! >and any help is much appreciated Contact me (off this thread) with details of anything I can be of help. -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
Bug#966692: stunnel4: FTBFS because of test hang
On Thu, Aug 06, 2020 at 03:23:08AM +0200, Michał Mirosław wrote: > On Thu, Aug 06, 2020 at 03:10:55AM +0200, Michał Mirosław wrote: > > On Thu, Aug 06, 2020 at 02:39:42AM +0200, Michał Mirosław wrote: > > > On Thu, Aug 06, 2020 at 03:16:35AM +0300, Peter Pentchev wrote: > > > > On Thu, Aug 06, 2020 at 12:48:10AM +0200, Michał Mirosław wrote: > > > > > On Thu, Aug 06, 2020 at 12:29:36AM +0300, Peter Pentchev wrote: > > > > > > On Wed, Aug 05, 2020 at 10:52:31PM +0200, Michał Mirosław wrote: > > > > > [...] > > > > > > > Using print-debugging, I see that it stops at wait_for_child line > > > > > > > just > > > > > > > after printing the version. It seems that something is reaping > > > > > > > the child > > > > > > > before the main thread has a chance to wait for it. > > > > > > > > > > > > OK, so the only thing that comes to my mind now is that you may be > > > > > > hitting a crazy, crazy race between register_child() and > > > > > > child_reaper(), > > > > > > and I say "a crazy, crazy race", because the test has to (apparently > > > > > > reproducibly) receive the CHLD signal exactly between the check and > > > > > > the creation in register_child()'s first "$children{...} //= ...cv" > > > > > > statement. > > > > > > > > > > Well, there is nothing that prevents SIGCHLD arriving between fork() > > > > > and > > > > > register_child(). You could test this with more confidence (though not > > > > > 100%-reliably) by putting 'exit 1' just at the start of ($pid == 0) > > > > > branch. > > > > > > > > Nah, the problem is not just "between fork() and register_child()". > > > > It really must arrive at a very specific moment in time, because > > > > the //= operations for setting $children{$pid}{cv} try to make sure that > > > > a new value is not set (that is, a new condition variable is not > > > > created) if there already is such an element in the array. So the race > > > > is indeed between the //= in register_child() and the //= in > > > > child_reaper() - that is, child_reaper() must be invoked (SIGCHLD must > > > > arrive) *during* the execution of the //= in register_child(). > > > > > > > > Unless I'm missing something, which is not at all out of the question :) > > > > > > The assignment seems not to be at fault (see last strace). I don't know > > > perl's > > > internals enough to say if this statement can be interrupted visibly by a > > > signal > > > handler (I would guess not a perl handler, though). There are two wait4() > > > calls > > > even before child_reaper has a chance to run. > > > > Another data point: this happens only with anyevent + libev and not with > > anyevent + libevent. The first is preferred and installed by default with > > libanyevent-perl, though. And this is why I could not reproduce it until now - I've always (well, okay, ever since it was introduced, I'm a bit older than that) had apt *not* automatically install recommended packages... And here I thought I was going crazy... thanks, now it's, mm, let's say easier to reproduce! > AnyEvent's doc [1] mentions that the framework installs (or just might?) it's > own SIGCHLD handler. Maybe there are just too many handlers for SIGCHLD? Aaand this is why I should never be let near a keyboard... So how many years have I been doing Perl programming now?... and I managed to forget about AnyEvent installing its own SIGCHLD handler? Great. Just great. Thanks an *awful* lot for your perseverance, your analysis, and basically doing my own debugging work for me! Expect another patch soon. G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#967185: marked as done (openjfx: Unversioned Python removal in sid/bullseye)
Your message dated Thu, 06 Aug 2020 05:48:41 + with message-id and subject line Bug#967185: fixed in openjfx 11.0.7+0-3 has caused the Debian Bug report #967185, regarding openjfx: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967185 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:openjfx Version: 11.0.7+0-2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: openjfx Source-Version: 11.0.7+0-3 Done: tony mancill We believe that the bug you reported is fixed in the latest version of openjfx, 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 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated openjfx 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, 05 Aug 2020 21:47:08 -0700 Source: openjfx Architecture: source Version: 11.0.7+0-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: tony mancill Closes: 937202 967185 Changes: openjfx (11.0.7+0-3) unstable; urgency=medium . * Team upload. * Build-depend on python3 (Closes: #937202, #967185) Checksums-Sha1: 3aa3a8737eaf5fc0381e4650e395c400026096e8 2764 openjfx_11.0.7+0-3.dsc 94452cb7b20539af1a2c9faba01b49728b108a1d 16304 openjfx_11.0.7+0-3.debian.tar.xz 9e2beaf154dda81fe4fd2d9a37c6bb9f4b30d839 24155 openjfx_11.0.7+0-3_amd64.buildinfo Checksums-Sha256: 2b9f38c8d004904b360c9345dff2dacf75f4df690a155a7efdd8a722b5827e07 2764 openjfx_11.0.7+0-3.dsc 0e3dc0df15c595b9bde323314f048823a66066e48b464ced41eb51a77bf92b29 16304 openjfx_11.0.7+0-3.debian.tar.xz 1e31a23d467968439a2882eaffef7c97066ce23847689670e2e998c1ff68ac43 24155 openjfx_11.0.7+0-3_amd64.buildinfo Files: c9530de6f5c3157cc579de422c421088 2764 java optional openjfx_11.0.7+0-3.dsc b76eac8f86c8a1f56eb3a751bf1e0345 16304 java optional openjfx_11.0.7+0-3.debian.tar.xz db9199583014134db360d5de3ffcd545 24155 java optional openjfx_11.0.7+0-3_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl8rlcMUHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpauuRAAkXIoQ586vDQEUrzN1RugDO7zDQtD vlkt6CCxqfidvcqwT+mDey2kgZsGZ1inmy8HOcNy6cLlMAHdGLC8jQWnp7otLMtr 9yDnKLIKkAbYlFeovXg0RSTE+k/tYiELenLz6ptBkSrpCpYn7uLhOKB8lIN42BKT r3S3oF0s9FUbOSkkpx9CkSx9Y4Ua7C5QEWAXvK9trzcb1Y1ruJlHRadmHx43hSlZ VhKa+truh66OdVz6iVQQfBN/ugUo1g6D7ocRSbfV4Qe7+rfh606ARj6S0D2V7QQZ fxbUnDook1ShC8Ni3zXPl+X3t+cLj5yY8KRrKrB4Wx7nZrmPszQx9vgaqyHF3Pjg f1aCEgjKBsrgTJSopla6zDdyDsFNeqwXaVaUeQzcotqPAN+SEwnbLIBVi8nb+Gun y92AhPAI+xUUhmhRcMgKTC6M+YmlzqM0WpTrvMnr/kvF4hDNfPR3T7MuFh2rZWHk UYnVbvEzBhGuYl56P0ySZGKUvjqkyyyqXgXYiyuxa/17FfMnKS1aOLlDW/WRkgWr ecdoiPfRWJGkoN4jUhrKrI6OcMSaTiwfXn7YIzPbcW1eZhcCOyUoLGJjPwMEXReV YVsipbaw5XdScgSvHSMH7uXUHE1Mv5igF3m/aravUskwdTeuuKwcsTKfRsCaD49G GLm2HAXu7tP9mc0= =sNEh -END PGP SIGNATURE End Message ---
Bug#966914: sambamba: FTBFS: collect2: error: ld returned 1 exit status
On Thu, Aug 06, 2020 at 03:49:51AM +0200, Matthias Klumpp wrote: > Where does the > `bgzf.c` file reference come from? I used find on my local disk and several projects do contain bgzf.c. My guess is these are all code copies from htslib - thus I'd assume it comes from htslib. This seems quite probable since cram/htslib.d in sambamba contains the string bgzf several times. Kind regards Andreas. -- http://fam-tille.de
Processed: unarchiving 960326
Processing commands for cont...@bugs.debian.org: > unarchive 960326 Bug #960326 {Done: Gianfranco Costamagna } [src:json-c] json-c: CVE-2020-12762 Unarchived Bug 960326 > thanks Stopping processing here. Please contact me if you need assistance. -- 960326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed (with 1 error): unarchiving 960326, found 960326 in 0.12.1+ds-2, closing 960326
Processing commands for cont...@bugs.debian.org: > unarchive 960326 > found 960326 0.12.1+ds-2 Bug #960326 {Done: Gianfranco Costamagna } [src:json-c] json-c: CVE-2020-12762 Marked as found in versions json-c/0.12.1+ds-2. > close 960326 0.12.1+ds-2+deb10u1 Bug #960326 {Done: Gianfranco Costamagna } [src:json-c] json-c: CVE-2020-12762 Marked as fixed in versions json-c/0.12.1+ds-2+deb10u1. Bug #960326 {Done: Gianfranco Costamagna } [src:json-c] json-c: CVE-2020-12762 Bug 960326 is already marked as done; not doing anything. > thanks Stopping processing here. Please contact me if you need assistance. -- 960326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957020: Fixed already in upstream commit 017e6c6ab95df55f34e339d2139def83e5dada1f
Upstream fixed this via commit https://github.com/linux-audit/audit-userspace/commit/017e6c6ab95df55f34e339d2139def83e5dada1f however this has not yet been released in an official release.
Bug#966914: sambamba: FTBFS: collect2: error: ld returned 1 exit status
Am Di., 4. Aug. 2020 um 11:23 Uhr schrieb Andreas Tille : > > Control: tags -1 help > > Hi, > > On Mon, Aug 03, 2020 at 10:06:32AM +0200, Lucas Nussbaum wrote: > > > lto1: fatal error: bytecode stream in file > > > ‘/usr/lib/x86_64-linux-gnu/libhts.a’ generated with GCC compiler older > > > than 10.0 > > I've uploaded a new htslib that is now build with GCC 10 and used a > versioned Build-Depends inside sambamba. Now the build issue changed > to: > > [38/41] ldc2 -enable-color -O -g -release -wi -I/usr/include/x86_64-linux-gnu > -I/usr/include/d/bio -O3 -release -enable-inlining -boundscheck=off -J../ > -I=.. -I=. -I=sambamba.p -I=sambamba.p > -of=sambamba.p/_build_sambamba-0.7.1_obj-x86_64-linux-gnu_utils_ldc_version_info_.d.o > -c /build/sambamba-0.7.1/obj-x86_64-linux-gnu/utils/ldc_version_info_.d > [39/41] ldc2 -enable-color -O -g -release -wi -I/usr/include/x86_64-linux-gnu > -I/usr/include/d/bio -O3 -release -enable-inlining -boundscheck=off -J../ > -I=.. -I=. -I=sambamba.p -I=sambamba.p > -of=sambamba.p/thirdparty_unstablesort.d.o -c ../thirdparty/unstablesort.d > [40/41] ldc2 -enable-color -O -g -release -wi -I/usr/include/x86_64-linux-gnu > -I/usr/include/d/bio -O3 -release -enable-inlining -boundscheck=off -J../ > -I=.. -I=. -I=sambamba.p -I=sambamba.p -of=sambamba.p/sambamba_view.d.o -c > ../sambamba/view.d > [41/41] ldc2 -of=sambamba sambamba.p/sambamba_main.d.o > sambamba.p/sambamba_depth.d.o sambamba.p/sambamba_fixbins.d.o > sambamba.p/sambamba_flagstat.d.o sambamba.p/sambamba_index.d.o > sambamba.p/sambamba_markdup2.d.o sambamba.p/sambamba_markdup.d.o > sambamba.p/sambamba_merge.d.o sambamba.p/sambamba_pileup.d.o > sambamba.p/sambamba_slice.d.o sambamba.p/sambamba_sort.d.o > sambamba.p/sambamba_subsample.d.o sambamba.p/sambamba_utils_common_bed.d.o > sambamba.p/sambamba_utils_common_file.d.o > sambamba.p/sambamba_utils_common_filtering.d.o > sambamba.p/sambamba_utils_common_intervaltree.d.o > sambamba.p/sambamba_utils_common_ldc_gc_workaround.d.o > sambamba.p/sambamba_utils_common_overwrite.d.o > sambamba.p/sambamba_utils_common_pratt_parser.d.o > sambamba.p/sambamba_utils_common_progressbar.d.o > sambamba.p/sambamba_utils_common_queryparser.d.o > sambamba.p/sambamba_utils_common_readstorage.d.o > sambamba.p/sambamba_utils_common_tmpdir.d.o > sambamba.p/sambamba_utils_view_alignmentrangeprocessor.d.o > sambamba.p/sambamba_utils_view_headerserializer.d.o > sambamba.p/sambamba_validate.d.o sambamba.p/sambamba_view.d.o > sambamba.p/utils_lz4.d.o sambamba.p/utils_strip_bcf_header.d.o > sambamba.p/utils_version_.d.o sambamba.p/cram_exception.d.o > sambamba.p/cram_htslib.d.o sambamba.p/cram_reader.d.o > sambamba.p/cram_reference.d.o sambamba.p/cram_slicereader.d.o > sambamba.p/cram_wrappers.d.o sambamba.p/cram_writer.d.o > sambamba.p/thirdparty_mergesort.d.o sambamba.p/thirdparty_unstablesort.d.o > sambamba.p/_build_sambamba-0.7.1_obj-x86_64-linux-gnu_utils_ldc_version_info_.d.o > -L=--allow-shlib-undefined -link-defaultlib-shared -O -g -release -wi -L=-z > -L=relro -L=/usr/lib/x86_64-linux-gnu/libbiod.a > -L=/usr/lib/x86_64-linux-gnu/libz.a -L=/usr/lib/x86_64-linux-gnu/libhts.a > -L=-z -L=relro -L=-z -L=now -L=-flto -fvisibility=hidden > -L=/usr/lib/x86_64-linux-gnu/libbz2.a > -L=/usr/lib/x86_64-linux-gnu/libdeflate.a -L=-lm -L=-lpthread > -L=/usr/lib/x86_64-linux-gnu/liblzma.a > /usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu/liblz4.so > /usr/lib/x86_64-linux-gnu/libcurl.so /usr/lib/x86_64-linux-gnu/libcrypto.so > /usr/lib/x86_64-linux-gnu/liblzma.so -L=-rpath > -L=/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu:/usr/lib/x86_64-linux-gnu > -L=-rpath-link -L=/usr/lib/gcc/x86_64-linux-gnu/10/../../../x86_64-linux-gnu > -L=-rpath-link -L=/usr/lib/x86_64-linux-gnu > FAILED: sambamba > ldc2 -of=sambamba sambamba.p/sambamba_main.d.o sambamba.p/sambamba_depth.d.o > sambamba.p/sambamba_fixbins.d.o sambamba.p/sambamba_flagstat.d.o > sambamba.p/sambamba_index.d.o sambamba.p/sambamba_markdup2.d.o > sambamba.p/sambamba_markdup.d.o sambamba.p/sambamba_merge.d.o > sambamba.p/sambamba_pileup.d.o sambamba.p/sambamba_slice.d.o > sambamba.p/sambamba_sort.d.o sambamba.p/sambamba_subsample.d.o > sambamba.p/sambamba_utils_common_bed.d.o > sambamba.p/sambamba_utils_common_file.d.o > sambamba.p/sambamba_utils_common_filtering.d.o > sambamba.p/sambamba_utils_common_intervaltree.d.o > sambamba.p/sambamba_utils_common_ldc_gc_workaround.d.o > sambamba.p/sambamba_utils_common_overwrite.d.o > sambamba.p/sambamba_utils_common_pratt_parser.d.o > sambamba.p/sambamba_utils_common_progressbar.d.o > sambamba.p/sambamba_utils_common_queryparser.d.o > sambamba.p/sambamba_utils_common_readstorage.d.o > sambamba.p/sambamba_utils_common_tmpdir.d.o > sambamba.p/sambamba_utils_view_alignmentrangeprocessor.d.o > sambamba.p/sambamba_utils_view_headerserializer.d.o > sambamba.p/sambamba_validate.d.o sambamba.p/sambamba_view.d.o > sambamba.p/util
Bug#957592: marked as done (neovim: ftbfs with GCC-10)
Your message dated Thu, 06 Aug 2020 01:33:27 + with message-id and subject line Bug#957592: fixed in neovim 0.4.4-1 has caused the Debian Bug report #957592, regarding neovim: 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.) -- 957592: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957592 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:neovim Version: 0.4.3-3 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/neovim_0.4.3-3_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: src/nvim/CMakeFiles/nvim.dir/sign.c.o (symbol from plugin): in function `init_signs': (.text+0x0): multiple definition of `ListLenSpecials'; src/nvim/CMakeFiles/nvim.dir/auto/msgpack_lua_c_bindings.generated.c.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: src/nvim/CMakeFiles/nvim.dir/spell.c.o (symbol from plugin): in function `spelltab': (.text+0x0): multiple definition of `RemapValues'; src/nvim/CMakeFiles/nvim.dir/auto/msgpack_lua_c_bindings.generated.c.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: src/nvim/CMakeFiles/nvim.dir/spell.c.o (symbol from plugin): in function `spelltab': (.text+0x0): multiple definition of `ListLenSpecials'; src/nvim/CMakeFiles/nvim.dir/auto/msgpack_lua_c_bindings.generated.c.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: src/nvim/CMakeFiles/nvim.dir/spellfile.c.o (symbol from plugin): in function `spell_load_file': (.text+0x0): multiple definition of `ListLenSpecials'; src/nvim/CMakeFiles/nvim.dir/auto/msgpack_lua_c_bindings.generated.c.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: src/nvim/CMakeFiles/nvim.dir/state.c.o (symbol from plugin): in function `state_enter': (.text+0x0): multiple definition of `RemapValues'; src/nvim/CMakeFiles/nvim.dir/auto/msgpack_lua_c_bindings.generated.c.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: src/nvim/CMakeFiles/nvim.dir/state.c.o (symbol from plugin): in function `state_enter': (.text+0x0): multiple definition of `ListLenSpecials'; src/nvim/CMakeFiles/nvim.dir/auto/msgpack_lua_c_bindings.generated.c.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: src/nvim/CMakeFiles/nvim.dir/strings.c.o (symbol from plugin): in function `vim_strsave': (.text+0x0): multiple definition of `RemapValues'; src/nvim/CMakeFiles/nvim.dir/auto/msgpack_lua_c_bindings.generated.c.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: src/nvim/CMakeFiles/nvim.dir/strings.c.o (symbol from plugin): in function `vim_strsave': (.text+0x0): multiple definition of `ListLenSpecials'; src/nvim/CMakeFiles/nvim.dir/auto/msgpack_lua_c_bindings.generated.c.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: src/nvim/CMakeFiles/nvim.dir/syntax.c.o (symbol from plugin): in function `syn_set_timeout': (.text+0x0): multiple definition of `RemapValues'; src/nvim/CMakeFiles/nvim.dir/auto/msgpack_lua_c_bindings.generated.c.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: src/nvim/CMakeFiles/nvim.dir/syntax.c.o (symbol from plugin): in function `syn_set_timeout': (.text+0x0): multiple definition of `ListLenSpecials'; src/nvim/CMakeFiles/nvim.dir/auto/msgpack_lua_c_bindings.generated.c.o (symbol from plugin):(.text+0x0): first defined here /usr/bin/ld: src/nvim/CMakeFiles/nvim.dir/tag.c.o (symbol from plugin): in function `tag_freematc
Bug#957379: Commit that fix this issue is 129b7e402bd6e7278854e5a8935fce460552b5f4
Issue link: https://gitlab.isc.org/isc-projects/dhcp/-/issues/117 commit/merge request link: https://gitlab.isc.org/isc-projects/dhcp/-/commit/129b7e402bd6e7278854e5a8935fce460552b5f4?merge_request_iid=60 signature.asc Description: This is a digitally signed message part
Bug#966692: stunnel4: FTBFS because of test hang
On Thu, Aug 06, 2020 at 03:10:55AM +0200, Michał Mirosław wrote: > On Thu, Aug 06, 2020 at 02:39:42AM +0200, Michał Mirosław wrote: > > On Thu, Aug 06, 2020 at 03:16:35AM +0300, Peter Pentchev wrote: > > > On Thu, Aug 06, 2020 at 12:48:10AM +0200, Michał Mirosław wrote: > > > > On Thu, Aug 06, 2020 at 12:29:36AM +0300, Peter Pentchev wrote: > > > > > On Wed, Aug 05, 2020 at 10:52:31PM +0200, Michał Mirosław wrote: > > > > [...] > > > > > > Using print-debugging, I see that it stops at wait_for_child line > > > > > > just > > > > > > after printing the version. It seems that something is reaping the > > > > > > child > > > > > > before the main thread has a chance to wait for it. > > > > > > > > > > OK, so the only thing that comes to my mind now is that you may be > > > > > hitting a crazy, crazy race between register_child() and > > > > > child_reaper(), > > > > > and I say "a crazy, crazy race", because the test has to (apparently > > > > > reproducibly) receive the CHLD signal exactly between the check and > > > > > the creation in register_child()'s first "$children{...} //= ...cv" > > > > > statement. > > > > > > > > Well, there is nothing that prevents SIGCHLD arriving between fork() and > > > > register_child(). You could test this with more confidence (though not > > > > 100%-reliably) by putting 'exit 1' just at the start of ($pid == 0) > > > > branch. > > > > > > Nah, the problem is not just "between fork() and register_child()". > > > It really must arrive at a very specific moment in time, because > > > the //= operations for setting $children{$pid}{cv} try to make sure that > > > a new value is not set (that is, a new condition variable is not > > > created) if there already is such an element in the array. So the race > > > is indeed between the //= in register_child() and the //= in > > > child_reaper() - that is, child_reaper() must be invoked (SIGCHLD must > > > arrive) *during* the execution of the //= in register_child(). > > > > > > Unless I'm missing something, which is not at all out of the question :) > > > > The assignment seems not to be at fault (see last strace). I don't know > > perl's > > internals enough to say if this statement can be interrupted visibly by a > > signal > > handler (I would guess not a perl handler, though). There are two wait4() > > calls > > even before child_reaper has a chance to run. > > Another data point: this happens only with anyevent + libev and not with > anyevent + libevent. The first is preferred and installed by default with > libanyevent-perl, though. > > $ dpkg -l libanyevent-perl libev-perl | cat > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version Architecture Description > +++---- > ii libanyevent-perl 7.140-3 amd64event loop framework with > multiple implementations > ii libev-perl 4.25-1 amd64Perl interface to libev, the > high performance event loop AnyEvent's doc [1] mentions that the framework installs (or just might?) it's own SIGCHLD handler. Maybe there are just too many handlers for SIGCHLD? [1] https://metacpan.org/pod/AnyEvent#SIGNALS Best Regards, Michał Mirosław
Bug#966692: stunnel4: FTBFS because of test hang
On Thu, Aug 06, 2020 at 02:39:42AM +0200, Michał Mirosław wrote: > On Thu, Aug 06, 2020 at 03:16:35AM +0300, Peter Pentchev wrote: > > On Thu, Aug 06, 2020 at 12:48:10AM +0200, Michał Mirosław wrote: > > > On Thu, Aug 06, 2020 at 12:29:36AM +0300, Peter Pentchev wrote: > > > > On Wed, Aug 05, 2020 at 10:52:31PM +0200, Michał Mirosław wrote: > > > [...] > > > > > Using print-debugging, I see that it stops at wait_for_child line just > > > > > after printing the version. It seems that something is reaping the > > > > > child > > > > > before the main thread has a chance to wait for it. > > > > > > > > OK, so the only thing that comes to my mind now is that you may be > > > > hitting a crazy, crazy race between register_child() and child_reaper(), > > > > and I say "a crazy, crazy race", because the test has to (apparently > > > > reproducibly) receive the CHLD signal exactly between the check and > > > > the creation in register_child()'s first "$children{...} //= ...cv" > > > > statement. > > > > > > Well, there is nothing that prevents SIGCHLD arriving between fork() and > > > register_child(). You could test this with more confidence (though not > > > 100%-reliably) by putting 'exit 1' just at the start of ($pid == 0) > > > branch. > > > > Nah, the problem is not just "between fork() and register_child()". > > It really must arrive at a very specific moment in time, because > > the //= operations for setting $children{$pid}{cv} try to make sure that > > a new value is not set (that is, a new condition variable is not > > created) if there already is such an element in the array. So the race > > is indeed between the //= in register_child() and the //= in > > child_reaper() - that is, child_reaper() must be invoked (SIGCHLD must > > arrive) *during* the execution of the //= in register_child(). > > > > Unless I'm missing something, which is not at all out of the question :) > > The assignment seems not to be at fault (see last strace). I don't know perl's > internals enough to say if this statement can be interrupted visibly by a > signal > handler (I would guess not a perl handler, though). There are two wait4() > calls > even before child_reaper has a chance to run. Another data point: this happens only with anyevent + libev and not with anyevent + libevent. The first is preferred and installed by default with libanyevent-perl, though. $ dpkg -l libanyevent-perl libev-perl | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++---- ii libanyevent-perl 7.140-3 amd64event loop framework with multiple implementations ii libev-perl 4.25-1 amd64Perl interface to libev, the high performance event loop Best Regards, Michał Mirosław
Bug#963244: Wrong "Bug-Debian" in protobuf_generated_classes_no_inheritance.patch
I think that the wrong "Bug-Debian" tag was inserted in debian/patches/protobuf_generated_classes_no_inheritance.patch: Description: Fix build with latest protobuf Origin: gentoo https://gitweb.gentoo.org/repo/gentoo.git/plain/app-i18n/mozc/files/mozc-2.23.2815.102-protobuf_generated_classes_no_inheritance.patch Bug-Debian: http://bugs.debian.org/265678
Bug#966692: stunnel4: FTBFS because of test hang
On Thu, Aug 06, 2020 at 03:16:35AM +0300, Peter Pentchev wrote: > On Thu, Aug 06, 2020 at 12:48:10AM +0200, Michał Mirosław wrote: > > On Thu, Aug 06, 2020 at 12:29:36AM +0300, Peter Pentchev wrote: > > > On Wed, Aug 05, 2020 at 10:52:31PM +0200, Michał Mirosław wrote: > > [...] > > > > Using print-debugging, I see that it stops at wait_for_child line just > > > > after printing the version. It seems that something is reaping the child > > > > before the main thread has a chance to wait for it. > > > > > > OK, so the only thing that comes to my mind now is that you may be > > > hitting a crazy, crazy race between register_child() and child_reaper(), > > > and I say "a crazy, crazy race", because the test has to (apparently > > > reproducibly) receive the CHLD signal exactly between the check and > > > the creation in register_child()'s first "$children{...} //= ...cv" > > > statement. > > > > Well, there is nothing that prevents SIGCHLD arriving between fork() and > > register_child(). You could test this with more confidence (though not > > 100%-reliably) by putting 'exit 1' just at the start of ($pid == 0) branch. > > Nah, the problem is not just "between fork() and register_child()". > It really must arrive at a very specific moment in time, because > the //= operations for setting $children{$pid}{cv} try to make sure that > a new value is not set (that is, a new condition variable is not > created) if there already is such an element in the array. So the race > is indeed between the //= in register_child() and the //= in > child_reaper() - that is, child_reaper() must be invoked (SIGCHLD must > arrive) *during* the execution of the //= in register_child(). > > Unless I'm missing something, which is not at all out of the question :) The assignment seems not to be at fault (see last strace). I don't know perl's internals enough to say if this statement can be interrupted visibly by a signal handler (I would guess not a perl handler, though). There are two wait4() calls even before child_reaper has a chance to run. > > > Can you apply the following patch and show me the output of running > > > the test? > > > > Sure, but I got no patch. :-) > > Oof. Not my day, is it... Here it is... I hope. [cut patch] With the patch applied: $ TEST_STUNNEL=src/stunnel strace -f -o /tmp/log debian/tests/runtime Found the certificate at debian/tests/certs/certificate.pem and the private key at debian/tests/certs/key.pem Using the /tmp/user/1000/EklzlCzeRO temporary directory About to get the stunnel version information register_child: pid 14943 cv AnyEvent::CondVar=HASH(0x559e0d7572e0) RDBG child_reaper() invoked RDBG - pid -1 status -1 RDBG - done RDBG - out of the child_reaper() loop Got stunnel version 5.56 ^C And in the strace log: 14942 epoll_wait(3, [{EPOLLIN, {u32=5, u64=4294967301}}], 64, 59743) = 1 14942 epoll_wait(3, [{EPOLLIN, {u32=5, u64=4294967301}}], 64, 59743) = 1 14943 exit_group(0 14942 read(5, 14943 <... exit_group resumed>) = ? 14942 <... read resumed> "TIMEOUTconnect = 10 seco"..., 8192) = 105 14942 epoll_wait(3, [{EPOLLHUP, {u32=5, u64=4294967301}}], 64, 59743) = 1 14943 +++ exited with 0 +++ 14942 epoll_ctl(3, EPOLL_CTL_MOD, 5, {EPOLLIN, {u32=5, u64=4294967301}}) = 0 14942 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=14943, si_uid=1000, si_status=0, si_utime=0, si_stime=0} --- 14942 write(4, "\1\0\0\0\0\0\0\0", 8) = 8 14942 rt_sigreturn({mask=[PIPE]}) = 0 14942 epoll_wait(3, [{EPOLLHUP, {u32=5, u64=4294967301}}, {EPOLLIN, {u32=4, u64=4294967300}}], 64, 59743) = 2 14942 epoll_ctl(3, EPOLL_CTL_MOD, 5, {EPOLLIN, {u32=5, u64=4294967301}}) = 0 14942 read(4, "\1\0\0\0\0\0\0\0", 8)= 8 14942 wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], WNOHANG|WSTOPPED|WCONTINUED, NULL) = 14943 14942 wait4(-1, 0x7fffcacfddc4, WNOHANG|WSTOPPED|WCONTINUED, NULL) = -1 ECHILD (No child processes) 14942 write(1, "RDBG child_reaper() invoked\n", 28) = 28 14942 wait4(-1, 0x7fffcacfdb74, WNOHANG, NULL) = -1 ECHILD (No child processes) 14942 write(1, "RDBG - pid -1 status -1\n", 24) = 24 14942 write(1, "RDBG - done\n", 14) = 14 14942 write(1, "RDBG - out of the child_reaper()"..., 38) = 38 14942 epoll_wait(3, [{EPOLLHUP, {u32=5, u64=4294967301}}], 64, 59743) = 1 14942 epoll_ctl(3, EPOLL_CTL_MOD, 5, {EPOLLIN, {u32=5, u64=4294967301}}) = 0 14942 read(5, "", 8192) = 0 14942 write(1, "Got stunnel version 5.56\n", 25) = 25 14942 epoll_wait(3, [{EPOLLHUP, {u32=5, u64=4294967301}}], 64, 59743) = 1 14942 epoll_ctl(3, EPOLL_CTL_DEL, 5, 0x559e0dba9760) = 0 14942 epoll_wait(3, 0x559e0dba9760, 64, 59743) = -1 EINTR (Interrupted system call) 14942 --- SIGINT {si_signo=SIGINT, si_code=SI_KERNEL} --- With 'exit 1' in child branch: $ TEST_STUNNEL=src/stunnel strace -f -o /tmp/log debian/tests/runtime Found the certificate at debian/tests/certs/certificate.pem and the private key at debian/tests/certs/key.pem Using the /tmp/user/1000/MWxDeDDlxS temporary dire
Bug#967965: astropy: FTBFS with scipy 1.5: [doctest] astropy.stats.funcs.binom_conf_interval failed
Source: astropy Version: 4.0.1+post1-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Control: found -1 4.1~rc1-2 Hi, astropy recently started to FTBFS in sid (and experimental, but not yet in bullseye). I could reproduce the failure in bullseye with python3-scipy/sid: === FAILURES === __ [doctest] astropy.stats.funcs.binom_conf_interval ___ 631 632 Integer inputs return an array with shape (2,): 633 634 >>> binom_conf_interval(4, 5, interval='wilson') 635 array([0.57921724, 0.92078259]) 636 637 Arrays of arbitrary dimension are supported. The Wilson and Jeffreys 638 intervals give similar results, even for small k, N: 639 640 >>> binom_conf_interval([0, 1, 2, 5], 5, interval='wilson') Expected: array([[0., 0.07921741, 0.21597328, 0.8304], [0.1696, 0.42078276, 0.61736012, 1.]]) Got: array([[1.38777878e-17, 7.92174125e-02, 2.15973276e-01, 8.3042e-01], [1.6958e-01, 4.20782762e-01, 6.17360116e-01, 1.e+00]]) /build/astropy-4.0.1+post1/.pybuild/cpython3_3.8/build/astropy/stats/funcs.py:640: DocTestFailure = 1 failed, 13907 passed, 412 skipped, 49 xfailed, 12 xpassed in 169.79 seconds = Andreas astropy_bullseye+scipy_sid.build.gz Description: application/gzip
Processed: astropy: FTBFS with scipy 1.5: [doctest] astropy.stats.funcs.binom_conf_interval failed
Processing control commands: > found -1 4.1~rc1-2 Bug #967965 [src:astropy] astropy: FTBFS with scipy 1.5: [doctest] astropy.stats.funcs.binom_conf_interval failed Marked as found in versions astropy/4.1~rc1-2. -- 967965: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967965 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967964: unison-2.48: file conflict with unison -4
Package: unison-2.48 Version: 2.48.4-5+b1 Severity: serious Justification: fails to upgrade Hi! I'm afraid there's no Replaces: stanza, resulting in: Unpacking unison-2.48 (2.48.4-5+b1) ... dpkg: error processing archive /tmp/apt-dpkg-install-Q6eH0z/4-unison-2.48_2.48.4-5+b1_amd64 .deb (--unpack): trying to overwrite '/usr/bin/unison-2.48', which is also in package unison 2.48.4-4 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Obviously: Replaces: unison (<< 2.48.4-5~) -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.8.0-umbar-00027-gfee487f15878 (SMP w/6 CPU threads) Kernel taint flags: TAINT_WARN Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages unison-2.48 depends on: ii libc6 2.31-3 Versions of packages unison-2.48 recommends: ii openssh-client [ssh-client] 1:8.3p1-1 Versions of packages unison-2.48 suggests: pn unison-all -- no debconf information
Bug#966692: stunnel4: FTBFS because of test hang
On Thu, Aug 06, 2020 at 12:48:10AM +0200, Michał Mirosław wrote: > On Thu, Aug 06, 2020 at 12:29:36AM +0300, Peter Pentchev wrote: > > On Wed, Aug 05, 2020 at 10:52:31PM +0200, Michał Mirosław wrote: > [...] > > > Using print-debugging, I see that it stops at wait_for_child line just > > > after printing the version. It seems that something is reaping the child > > > before the main thread has a chance to wait for it. > > > > OK, so the only thing that comes to my mind now is that you may be > > hitting a crazy, crazy race between register_child() and child_reaper(), > > and I say "a crazy, crazy race", because the test has to (apparently > > reproducibly) receive the CHLD signal exactly between the check and > > the creation in register_child()'s first "$children{...} //= ...cv" > > statement. > > Well, there is nothing that prevents SIGCHLD arriving between fork() and > register_child(). You could test this with more confidence (though not > 100%-reliably) by putting 'exit 1' just at the start of ($pid == 0) branch. Nah, the problem is not just "between fork() and register_child()". It really must arrive at a very specific moment in time, because the //= operations for setting $children{$pid}{cv} try to make sure that a new value is not set (that is, a new condition variable is not created) if there already is such an element in the array. So the race is indeed between the //= in register_child() and the //= in child_reaper() - that is, child_reaper() must be invoked (SIGCHLD must arrive) *during* the execution of the //= in register_child(). Unless I'm missing something, which is not at all out of the question :) > > Can you apply the following patch and show me the output of running > > the test? > > Sure, but I got no patch. :-) Oof. Not my day, is it... Here it is... I hope. G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 commit 859acd0603a5bc74620df4949e1450805b7ba151 Author: Peter Pentchev Date: Thu Aug 6 00:26:32 2020 +0300 Diagnostic output for the runtime test's child reaper. diff --git a/debian/tests/runtime b/debian/tests/runtime index f594d9a..81cef23 100755 --- a/debian/tests/runtime +++ b/debian/tests/runtime @@ -55,19 +55,25 @@ sub unregister_child_reaper() sub child_reaper() { + say 'RDBG child_reaper() invoked'; while (1) { my $pid = waitpid -1, WNOHANG; my $status = $?; + say "RDBG - pid $pid status $status"; if (!defined $pid) { die "Could not waitpid() in a SIGCHLD handler: $!\n"; } elsif ($pid == 0 || $pid == -1) { + say 'RDBG - done'; last; } else { + say 'RDBG - '.(exists $children{$pid} ? '' : 'not ').'found in the children hash'; $children{$pid}{cv} //= AnyEvent->condvar; + say 'RDBG - cv '.$children{$pid}{cv}.': '.($children{$pid}{cv}->ready ? '' : 'not ').'ready'; $children{$pid}{cv}->send($status); } } + say 'RDBG - out of the child_reaper() loop'; } sub register_child($ $) @@ -76,6 +82,7 @@ sub register_child($ $) # Weird, but we want it to be at least reasonably atomic-like $children{$pid}{cv} //= AnyEvent->condvar; + say "register_child: pid $pid cv ".$children{$pid}{cv}; my $ch = $children{$pid}; $ch->{pid} = $pid; signature.asc Description: PGP signature
Bug#967150: marked as done (jython: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 05 Aug 2020 23:33:27 + with message-id and subject line Bug#967150: fixed in jython 2.7.2+repack1-2 has caused the Debian Bug report #967150, regarding jython: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:jython Version: 2.7.2+repack1-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: jython Source-Version: 2.7.2+repack1-2 Done: tony mancill We believe that the bug you reported is fixed in the latest version of jython, 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 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. tony mancill (supplier of updated jython 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, 05 Aug 2020 16:01:50 -0700 Source: jython Architecture: source Version: 2.7.2+repack1-2 Distribution: experimental Urgency: medium Maintainer: Debian Java Maintainers Changed-By: tony mancill Closes: 936776 967150 Changes: jython (2.7.2+repack1-2) experimental; urgency=medium . * Team upload * Update build dependencies for python 3 (Closes: #936776, #967150) * Upload to experimental to give users a chance to test. Checksums-Sha1: 6f9cc02a17163dd7eeafde85e44a3ad000d5ea83 2560 jython_2.7.2+repack1-2.dsc 8beed2b738a554a11d88d2eefd6feb069cffa7c8 21212 jython_2.7.2+repack1-2.debian.tar.xz de59d6cbf4fa95bb6714659fb0baa5b643a7bfdc 12221 jython_2.7.2+repack1-2_amd64.buildinfo Checksums-Sha256: 5782d609640776b55ff56cd36e05a009ebb7a2585fea73c7c7815a7091fdbe18 2560 jython_2.7.2+repack1-2.dsc 3472f4d6721f75b5e363482a8479a7b261ecad3ddfc7c8769c33e50ec77b9fe8 21212 jython_2.7.2+repack1-2.debian.tar.xz bb19ce94bbf0d5136c6f4799ee695e111356c782b49c42b4fb2b80f58e9cb7de 12221 jython_2.7.2+repack1-2_amd64.buildinfo Files: f3ef3a072dd12103ee30bc498cb904f9 2560 python optional jython_2.7.2+repack1-2.dsc 3319034a78d0e1d3a274a35a76a15ec0 21212 python optional jython_2.7.2+repack1-2.debian.tar.xz 8f5854029634391d9e474bd7d7fd933b 12221 python optional jython_2.7.2+repack1-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJIBAEBCgAyFiEE5Qr9Va3SequXFjqLIdIFiZdLPpYFAl8rPHYUHHRtYW5jaWxs QGRlYmlhbi5vcmcACgkQIdIFiZdLPpbLmxAA00ZguV/aeTn/7BNvz2NKruaABkEp jo7H7SzgzqWYSOZyfgn+NqkLY69TrGvnUlwgzr8NUpt87QfGOfxh3DaiqPeW2X48 bDDomm3pbmQt3sKUrz8gQHeoi1xakWhZdutjG8PD8Fl7TnGB2GjXjQe5/thzJDHH hR4KIhQpu4KmDE2eZ6kjQQs+UQXogVaINIxcUPlDctTDKZbGerynqMySnmvB5K0V mTgw+HLS29/n1JJGpPUo0vL0Tdm3QJW2l/HvnwcAC6BBP86bMXNdSDFqpxR3jTv4 7xK97yZP0krJFWho3IlSHOqF4PEkT4YhjtkkN+rnm38KJ0g3H+NwE3AtyuBF0fIq G56tWZ0dBf78Tfy7VcK2AuF6sC8Rhc89Al620+uCCWJQRp++pin9D66EnH1831Bh Jt+Fv7XY02SoAXz6bPr1FWGqyf0FVLmL4TraRrFHk8hK97BcStC1SHlvvI6p5S6L 9U+k+cxamJgEadrCa2lrklq5x4LRcyy613lC2c3jMcukRpjQ3mWyA6dsWRHxfIGb hdpp82bkOdXHD+0heVlPPBok2AlPZQFa5Bv4fXUD4v7mknZKQuBNZkQSN3AKUxtK fnjEPzHIGnlSYMUIRnozxranYUkOCpIrL1AJBEu0eBXSDBsF1VG5yZZy5qY0B+ao Oq4cTbsn+pYSYV8= =BWjF -END PGP SIGNATURE End
Processed: tagging 967181
Processing commands for cont...@bugs.debian.org: > tags 967181 + pending Bug #967181 [src:mupdf] mupdf: Unversioned Python removal in sid/bullseye Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 967181: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967181 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#936873: libhdate: diff for NMU version 1.6.02-2.1
Hi Bourch, We're still alive/here, and any help is much appreciated (thanks Moritz, feel free to NMU, no need to wait for us). Most members are busy with Debconf20 (moved from Haifa to an online conference). On Wed, Aug 5, 2020 at 10:42 PM Boruch Baum wrote: > Thanks Moritz for stepping forward and adopting this. I still haven't > heard back from any member of the 'Debian Hebrew Maintainers' team, but > will continue in the future to attempt to use them as a first point of > contact until/unless I hear that they have been disolved / superseded / > replaced. Any word on why the silence from them? > > On 2020-08-05 19:57, Moritz Mühlenhoff wrote: > > The debdiff for my NMU for libhdate (versioned as 1.6.02-2.1) > > > > Cheers, > > Moritz > > -- > hkp://keys.gnupg.net > CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0 > >
Bug#966692: stunnel4: FTBFS because of test hang
On Thu, Aug 06, 2020 at 12:29:36AM +0300, Peter Pentchev wrote: > On Wed, Aug 05, 2020 at 10:52:31PM +0200, Michał Mirosław wrote: [...] > > Using print-debugging, I see that it stops at wait_for_child line just > > after printing the version. It seems that something is reaping the child > > before the main thread has a chance to wait for it. > > OK, so the only thing that comes to my mind now is that you may be > hitting a crazy, crazy race between register_child() and child_reaper(), > and I say "a crazy, crazy race", because the test has to (apparently > reproducibly) receive the CHLD signal exactly between the check and > the creation in register_child()'s first "$children{...} //= ...cv" > statement. Well, there is nothing that prevents SIGCHLD arriving between fork() and register_child(). You could test this with more confidence (though not 100%-reliably) by putting 'exit 1' just at the start of ($pid == 0) branch. > Can you apply the following patch and show me the output of running > the test? Sure, but I got no patch. :-) Best Regards, Michał Mirosław
Processed: reassign 967919 to src:linux, severity of 967919 is important
Processing commands for cont...@bugs.debian.org: > reassign 967919 src:linux 4.19.132-1 Bug #967919 [linux-image-4.19.0-10-amd64] kernel panic at boot Bug reassigned from package 'linux-image-4.19.0-10-amd64' to 'src:linux'. No longer marked as found in versions linux-signed-amd64/4.19.132+1. Ignoring request to alter fixed versions of bug #967919 to the same values previously set Bug #967919 [src:linux] kernel panic at boot Marked as found in versions linux/4.19.132-1. > severity 967919 important Bug #967919 [src:linux] kernel panic at boot Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assistance. -- 967919: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967919 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967953: Package not installable in sid due to missing dependencies python-argcomplete and python-ipaddr
Hi Julian, Thanks for your submission. We've ported ifupdown2 to python3. Our release has been ready for a few months now, unfortunately our usual sponsor is not responding anymore. We are now looking for a new debian sponsor to upload our latest version to the debian repository. Best Julien On Wed, Aug 5, 2020 at 7:57 PM Julian Brost wrote: > > Package: ifupdown2 > Version: 1.2.7-1 > Severity: grave > > The package ifupdown2 currently cannot be installed on systems running > sid as the two of its dependencies, python-argcomplete and > python-ipaddr, are no longer present in sid. > > The suggested packages python-gvgen and python-mako also no longer exist.
Bug#936508: marked as done (fdb: Python2 removal in sid/bullseye)
Your message dated Wed, 05 Aug 2020 22:18:34 + with message-id and subject line Bug#936508: fixed in fdb 2.0.1-2 has caused the Debian Bug report #936508, regarding fdb: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 936508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:fdb Version: 2.0.0-1 Severity: normal Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2removal Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html Your package either build-depends, depends on Python2, or uses Python2 in the autopkg tests. Please stop using Python2, and fix this issue by one of the following actions. - Convert your Package to Python3. This is the preferred option. In case you are providing a Python module foo, please consider dropping the python-foo package, and only build a python3-foo package. Please don't drop Python2 modules, which still have reverse dependencies, just document them. This is the preferred option. - If the package is dead upstream, cannot be converted or maintained in Debian, it should be removed from the distribution. If the package still has reverse dependencies, raise the severity to "serious" and document the reverse dependencies with the BTS affects command. If the package has no reverse dependencies, confirm that the package can be removed, reassign this issue to ftp.debian.org, make sure that the bug priority is set to normal and retitle the issue to "RM: PKG -- removal triggered by the Python2 removal". - If the package has still many users (popcon >= 300), or is needed to build another package which cannot be removed, document that by adding the "py2keep" user tag (not replacing the py2remove tag), using the debian-pyt...@lists.debian.org user. Also any dependencies on an unversioned python package (python, python-dev) must not be used, same with the python shebang. These have to be replaced by python2/python2.7 dependencies and shebang. This is the least preferred option. If the conversion or removal needs action on another package first, please document the blocking by using the BTS affects command, like affects + src:fdb If there is no py2removal bug for that reverse-dependency, please file a bug on this package (similar to this bug report). If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: fdb Source-Version: 2.0.1-2 Done: Moritz Muehlenhoff We believe that the bug you reported is fixed in the latest version of fdb, 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 936...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Moritz Muehlenhoff (supplier of updated fdb 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, 05 Aug 2020 23:30:22 +0200 Source: fdb Architecture: source Version: 2.0.1-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Moritz Muehlenhoff Closes: 936508 Changes: fdb (2.0.1-2) unstable; urgency=medium . * QA upload * Set maintainer to Debian QA group * Drop Python 2 again (was reintroduced in 2.0.1-1) (Closes: #936508) Checksums-Sha1: cb378fd27124da359a9546505e8c22003997ebe9 1918 fdb_2.0.1-2.dsc d2926687c3af2a2e346267ff0c1fafb57bd3dcd0 4896 fdb_2.0.1-2.debian.tar.xz 6fc954d2503100942087b7b02630b6f58c3505e9 7404 fdb_2.0.1-2_amd64.buildinfo Checksums-Sha256: 4824566510e8cb4740d125978c45e6b24a48d9b13a8a866f53430f306736f3c0 1918 fdb_2.0.1-2.dsc 1f40c6678fb280c1298c4930546a1077a627061731e14bfc27f8f4f50c1a9e19 4896 fdb_2.0.1-2.debian.tar.xz f51c889b7fbf00d9f75ae7255f6dfb4d5761c7e0586dbe598af5a876e9246dbd 7404 fdb_2.0.1-2_amd64.buildinfo Files: 57f2c96af4f4cef8b5d3895057c6a5a8 1918 python optional fdb_2.0.1-2.d
Bug#966692: stunnel4: FTBFS because of test hang
On Wed, Aug 05, 2020 at 10:52:31PM +0200, Michał Mirosław wrote: > On Wed, Aug 05, 2020 at 09:28:12PM +0300, Peter Pentchev wrote: > > On Wed, Aug 05, 2020 at 08:01:53PM +0200, Michał Mirosław wrote: > > > On Sun, Aug 02, 2020 at 05:34:40PM +0300, Peter Pentchev wrote: > > > > On Sun, Aug 02, 2020 at 02:02:22AM +0200, Michał Mirosław wrote: > > > [...] > > > > --- a/debian/tests/runtime > > > > +++ b/debian/tests/runtime > > > > @@ -432,6 +432,7 @@ MAIN: > > > > > > > > if (!defined $line) { > > > > $eof->send($got_version); > > > > + undef $f_out; > > > > } elsif (!$got_version) { > > > > if ($line =~ m{^ > > > > stunnel \s+ > > > > > > I believe $f_out will not be defined here, as it only gets set after > > > sub{} is created. Perl confirms this: > > > > > > $ TEST_STUNNEL=src/stunnel strace -f -o /tmp/log debian/tests/runtime > > > Global symbol "$f_out" requires explicit package name (did you forget to > > > declare "my $f_out"?) at debian/tests/runtime line 435. > > > Execution of debian/tests/runtime aborted due to compilation errors. > > > > Of course you're right. Sorry about that! That's what I get for writing > > a patch three minutes before I have to head out and never remembering to > > actually test it later :( > > > > How about the attached one? [snip] > > This stops the endless readings of EOF, but: > > 1. the FD gets leaked (shouldn't matter much, though) > 2. the test hangs anyway > > Using print-debugging, I see that it stops at wait_for_child line just > after printing the version. It seems that something is reaping the child > before the main thread has a chance to wait for it. OK, so the only thing that comes to my mind now is that you may be hitting a crazy, crazy race between register_child() and child_reaper(), and I say "a crazy, crazy race", because the test has to (apparently reproducibly) receive the CHLD signal exactly between the check and the creation in register_child()'s first "$children{...} //= ...cv" statement. Can you apply the following patch and show me the output of running the test? G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Bug#966692: stunnel4: FTBFS because of test hang
On Wed, Aug 05, 2020 at 09:28:12PM +0300, Peter Pentchev wrote: > On Wed, Aug 05, 2020 at 08:01:53PM +0200, Michał Mirosław wrote: > > On Sun, Aug 02, 2020 at 05:34:40PM +0300, Peter Pentchev wrote: > > > On Sun, Aug 02, 2020 at 02:02:22AM +0200, Michał Mirosław wrote: > > [...] > > > --- a/debian/tests/runtime > > > +++ b/debian/tests/runtime > > > @@ -432,6 +432,7 @@ MAIN: > > > > > > if (!defined $line) { > > > $eof->send($got_version); > > > + undef $f_out; > > > } elsif (!$got_version) { > > > if ($line =~ m{^ > > > stunnel \s+ > > > > I believe $f_out will not be defined here, as it only gets set after > > sub{} is created. Perl confirms this: > > > > $ TEST_STUNNEL=src/stunnel strace -f -o /tmp/log debian/tests/runtime > > Global symbol "$f_out" requires explicit package name (did you forget to > > declare "my $f_out"?) at debian/tests/runtime line 435. > > Execution of debian/tests/runtime aborted due to compilation errors. > > Of course you're right. Sorry about that! That's what I get for writing > a patch three minutes before I have to head out and never remembering to > actually test it later :( > > How about the attached one? [...] > --- a/debian/tests/runtime > +++ b/debian/tests/runtime > @@ -424,7 +424,8 @@ MAIN: > > my ($got_version, $before_version) = (undef, ''); > my $eof = AnyEvent->condvar; > - my $f_out = AnyEvent->io( > + my $f_out; > + $f_out = AnyEvent->io( > fh => $s_in, > poll => 'r', > cb => sub { > @@ -432,6 +433,7 @@ MAIN: > > if (!defined $line) { > $eof->send($got_version); > + undef $f_out; > } elsif (!$got_version) { > if ($line =~ m{^ > stunnel \s+ This stops the endless readings of EOF, but: 1. the FD gets leaked (shouldn't matter much, though) 2. the test hangs anyway Using print-debugging, I see that it stops at wait_for_child line just after printing the version. It seems that something is reaping the child before the main thread has a chance to wait for it. >From strace: 4285 +++ exited with 0 +++ 4284 <... epoll_ctl resumed> ) = 0 4284 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=4285, si_uid=1000, si_status=0, si_utime=0, si_stime=0} --- 4284 write(4, "\1\0\0\0\0\0\0\0", 8) = 8 4284 rt_sigreturn({mask=[PIPE]}) = 0 4284 epoll_wait(3, [{EPOLLHUP, {u32=5, u64=4294967301}}, {EPOLLIN, {u32=4, u64=4294967300}}], 64, 59743) = 2 4284 epoll_ctl(3, EPOLL_CTL_MOD, 5, {EPOLLIN, {u32=5, u64=4294967301}}) = 0 4284 read(4, "\1\0\0\0\0\0\0\0", 8)= 8 4284 wait4(-1, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], WNOHANG|WSTOPPED|WCONTINUED, NULL) = 4285 4284 wait4(-1, 0x7ffcd56d5784, WNOHANG|WSTOPPED|WCONTINUED, NULL) = -1 ECHILD (No child processes) 4284 wait4(-1, 0x7ffcd56d5534, WNOHANG, NULL) = -1 ECHILD (No child processes) This is before the 'wait_for_child' a few lines later. 4284 epoll_wait(3, [{EPOLLHUP, {u32=5, u64=4294967301}}], 64, 59743) = 1 4284 epoll_ctl(3, EPOLL_CTL_MOD, 5, {EPOLLIN, {u32=5, u64=4294967301}}) = 0 4284 read(5, "", 8192) = 0 4284 write(1, "Got stunnel version 5.56\n", 25) = 25 4284 write(2, "wait child 4285\n", 16) = 16 This is version printout plus my check. 4284 epoll_wait(3, [{EPOLLHUP, {u32=5, u64=4294967301}}], 64, 59743) = 1 4284 epoll_ctl(3, EPOLL_CTL_DEL, 5, 0x5631c0d44a40) = 0 This clears watcher for the pipe. 4284 epoll_wait(3, 0x5631c0d44a40, 64, 59743) = -1 EINTR (Interrupted system call) And this waits forever. Best Regards Michał Mirosław
Bug#936309: closure-linter: Python2 removal in sid/bullseye
On Fri, Aug 30, 2019 at 07:13:28AM +, Matthias Klose wrote: > Package: src:closure-linter > Version: 2.3.19-1 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html Hi Laszlo, the upstream homepage now states: | Closure Linter is deprecated | | As the syntax of JavaScript has continued to evolve, with ES2015 and | beyond, it has become increasingly difficult to keep Closure Linter | up to date. It is unstaffed, unmaintained, and deprecated. Most | projects at Google have migrated to the new linter. | | For teams using the Closure tools, we recommend they use the new | linter based on the Closure Compiler instead. Given that closure-compiler is already packaged, let's simply remove closure-linter? Cheers, Moritz
Bug#957368: marked as done (ipip: ftbfs with GCC-10)
Your message dated Wed, 05 Aug 2020 20:35:30 + with message-id and subject line Bug#957368: fixed in ipip 1.1.10 has caused the Debian Bug report #957368, regarding ipip: 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.) -- 957368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957368 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ipip Version: 1.1.9 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/ipip_1.1.9_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 [...] | ^~~~ main.c: In function ‘main’: main.c:45:9: warning: variable ‘now’ set but not used [-Wunused-but-set-variable] 45 | time_t now; | ^~~ gcc -DLINUX -DUSE_TERMIOS -g -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o route.o route.c gcc -DLINUX -DUSE_TERMIOS -g -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o run.o run.c gcc -DLINUX -DUSE_TERMIOS -g -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o slip.o slip.c gcc -DLINUX -DUSE_TERMIOS -g -O2 -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -c -o tun.o tun.c gcc -Wl,-z,relro -DLINUX -DUSE_TERMIOS -g -O2 -Wall -o ipip config.o ip.o main.o route.o run.o slip.o tun.o /usr/bin/ld: ip.o:/<>/ipip.h:53: multiple definition of `progname'; config.o:/<>/ipip.h:53: first defined here /usr/bin/ld: ip.o:/<>/ipip.h:132: multiple definition of `ifs_top'; config.o:/<>/ipip.h:132: first defined here /usr/bin/ld: ip.o:/<>/ipip.h:131: multiple definition of `ifs'; config.o:/<>/ipip.h:131: first defined here /usr/bin/ld: ip.o:/<>/ipip.h:129: multiple definition of `rts_top'; config.o:/<>/ipip.h:129: first defined here /usr/bin/ld: ip.o:/<>/ipip.h:125: multiple definition of `rts'; config.o:/<>/ipip.h:125: first defined here /usr/bin/ld: ip.o:/<>/ipip.h:55: multiple definition of `stat_interval'; config.o:/<>/ipip.h:55: first defined here /usr/bin/ld: ip.o:/<>/ipip.h:54: multiple definition of `no_timestamp'; config.o:/<>/ipip.h:54: first defined here /usr/bin/ld: ip.o:/<>/ipip.h:52: multiple definition of `debugt'; config.o:/<>/ipip.h:52: first defined here /usr/bin/ld: ip.o:/<>/ipip.h:51: multiple definition of `debugd'; config.o:/<>/ipip.h:51: first defined here /usr/bin/ld: main.o:/<>/ipip.h:51: multiple definition of `debugd'; config.o:/<>/ipip.h:51: first defined here /usr/bin/ld: main.o:/<>/ipip.h:52: multiple definition of `debugt'; config.o:/<>/ipip.h:52: first defined here /usr/bin/ld: main.o:/<>/ipip.h:54: multiple definition of `no_timestamp'; config.o:/<>/ipip.h:54: first defined here /usr/bin/ld: main.o:/<>/ipip.h:55: multiple definition of `stat_interval'; config.o:/<>/ipip.h:55: first defined here /usr/bin/ld: main.o:/<>/ipip.h:53: multiple definition of `progname'; config.o:/<>/ipip.h:53: first defined here /usr/bin/ld: main.o:/<>/ipip.h:132: multiple definition of `ifs_top'; config.o:/<>/ipip.h:132: first defined here /usr/bin/ld: main.o:/<>/ipip.h:131: multiple definition of `ifs'; config.o:/<>/ipip.h:131: first defined here /usr/bin/ld: main.o:/<>/ipip.h:129: multiple definition of `rts_top'; config.o:/<>/ipip.h:129: first defined here /usr/bin/ld: main.o:/<>/ipip.h:125: multiple definition of `rts'; config.o:/<>/ipip.h:125: first defined here /usr/bin/ld: route.o:/<>/ipip.h:129: multiple definition of `rts_top'; config.o:/<>/ipip.h:129: first defined here /usr/bin/ld: route.o:/<>/ipip.h:125: multiple definition of `rts'; config.o:/<>/ipip.h:125: first defined here /usr/bin/ld: route.o:/<>/i
Bug#964679: marked as done (gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below)
Your message dated Wed, 05 Aug 2020 20:35:25 + with message-id and subject line Bug#964679: fixed in gtk+3.0 3.24.21-1 has caused the Debian Bug report #964679, regarding gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below 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.) -- 964679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gtk+3.0 Version: 3.24.20-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200709 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_makeshlibs -plibgtk-3-0 --add-udeb=libgtk-3-0-udeb > -Xusr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0 -- -c4 > dpkg-gensymbols: error: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: warning: debian/libgtk-3-0/DEBIAN/symbols doesn't match > completely debian/libgtk-3-0.symbols > --- debian/libgtk-3-0.symbols (libgtk-3-0_3.24.20-1_amd64) > +++ dpkg-gensymbolseXFnOd 2020-07-09 00:50:15.027590197 + > @@ -1,5 +1,8 @@ > libgdk-3.so.0 libgtk-3-0 #MINVER# > * Build-Depends-Package: libgtk-3-dev > + _gdk_get_resource@Base 3.24.20-1 > + _gdk_register_resource@Base 3.24.20-1 > + _gdk_unregister_resource@Base 3.24.20-1 > gdk__private__@Base 3.16.2 > gdk_add_option_entries_libgtk_only@Base 3.0.0 > gdk_anchor_hints_get_type@Base 3.21.5 > @@ -758,6 +761,9 @@ > gdk_x11_xatom_to_atom@Base 3.0.0 > gdk_x11_xatom_to_atom_for_display@Base 3.0.0 > libgtk-3.so.0 libgtk-3-0 #MINVER# > + _gtk_get_resource@Base 3.24.20-1 > + _gtk_register_resource@Base 3.24.20-1 > + _gtk_unregister_resource@Base 3.24.20-1 > gtk_about_dialog_add_credit_section@Base 3.3.16 > gtk_about_dialog_get_artists@Base 3.0.0 > gtk_about_dialog_get_authors@Base 3.0.0 > dh_makeshlibs: error: failing due to earlier errors > make[1]: *** [debian/rules:240: override_dh_makeshlibs] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/07/09/gtk+3.0_3.24.20-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: gtk+3.0 Source-Version: 3.24.21-1 Done: Simon McVittie We believe that the bug you reported is fixed in the latest version of gtk+3.0, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated gtk+3.0 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: Wed, 05 Aug 2020 15:33:48 +0100 Source: gtk+3.0 Architecture: source Version: 3.24.21-1 Distribution: experimental Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Closes: 960303 964679 Changes: gtk+3.0 (3.24.21-1) experimental; urgency=medium . * Team upload * New upstream release - Fix ability to use BSD-3-clause, Apache 2.0 and MPL 2.0 in GtkAboutDialog (Closes: #960303) * Add patch to fix FTBFS with newer GLib versions (Closes: #964679) Checksums-Sha1: 65270af3ce100a3475975542e5ca48fe2923f3c2 3945 gtk+3.0_3.24.21-1.dsc c34360a46556732d0143b2fd010f4065e9c3987b 21353740 gtk+3.0_3.24.21.orig.tar.xz 25cc4db5aab2a67d50c93b1316527b59fc35a9a7 156680 gtk+3.0_3.24.21-1.debian.tar.xz a60b8de0be25386bd5c56748d5871ef6dffda500 14609 gtk+3.0_3.24.21-1_source.buildinfo Checksums-Sha256: 98abfd82fa8333c4b23c76f1ff3cbfd51dc6fd55ae5b3e9ccc84bff2d89e28c1 3945 gtk+3.0_3.24.21-1.dsc aeea6ae7cd35e83dfc7699be716519faefca346c62e784dd1a37d9df94c08f52 21353740 gtk+3.0_3.24.21.orig.tar.xz 259df6378bde53a78fdedc3d1b1f4472233b49c4a7f5880f4c16e1dd1bfe03b3 156680 gtk+3.0_3.24.21-1.debian.tar.xz
Bug#967181: mupdf: Unversioned Python removal in sid/bullseye
As already pointed out in #937093, the upstream version 1.17.0 is compatibel with python3. Please update the Debian package to that version.
Bug#967955: golang-github-unknwon-cae: CVE-2020-7664
Source: golang-github-unknwon-cae Version: 0.0~git20160715.0.c6aac99-4 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for golang-github-unknwon-cae. CVE-2020-7664[0]: | In all versions of the package github.com/unknwon/cae/zip, the | ExtractTo function doesn't securely escape file paths in zip archives | which include leading or non-leading "..". This allows an attacker to | add or replace files system-wide. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-7664 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7664 [1] https://snyk.io/vuln/SNYK-GOLANG-GITHUBCOMUNKNWONCAEZIP-570383 Regards, Salvatore
Bug#967956: golang-github-unknwon-cae: CVE-2020-7668
Source: golang-github-unknwon-cae Version: 0.0~git20160715.0.c6aac99-4 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: car...@debian.org, Debian Security Team Hi, The following vulnerability was published for golang-github-unknwon-cae. CVE-2020-7668[0]: | In all versions of the package github.com/unknwon/cae/tz, the | ExtractTo function doesn't securely escape file paths in zip archives | which include leading or non-leading "..". This allows an attacker to | add or replace files system-wide. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-7668 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7668 Regards, Salvatore
Bug#936873: libhdate: diff for NMU version 1.6.02-2.1
Thanks Moritz for stepping forward and adopting this. I still haven't heard back from any member of the 'Debian Hebrew Maintainers' team, but will continue in the future to attempt to use them as a first point of contact until/unless I hear that they have been disolved / superseded / replaced. Any word on why the silence from them? On 2020-08-05 19:57, Moritz Mühlenhoff wrote: > The debdiff for my NMU for libhdate (versioned as 1.6.02-2.1) > > Cheers, > Moritz -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
Bug#957019: atlc: diff for NMU version 4.6.1-2.1
Sudip Mukherjee writes: > Control: tags 957019 + patch > Control: tags 957019 + pending > > Dear maintainer, > > I've prepared an NMU for atlc (versioned as 4.6.1-2.1) and > uploaded it to DELAYED/5. Please feel free to tell me if I > should cancel it. Thank you! Bdale signature.asc Description: PGP signature
Bug#966692: stunnel4: FTBFS because of test hang
On Wed, Aug 05, 2020 at 08:01:53PM +0200, Michał Mirosław wrote: > On Sun, Aug 02, 2020 at 05:34:40PM +0300, Peter Pentchev wrote: > > On Sun, Aug 02, 2020 at 02:02:22AM +0200, Michał Mirosław wrote: > [...] > > --- a/debian/tests/runtime > > +++ b/debian/tests/runtime > > @@ -432,6 +432,7 @@ MAIN: > > > > if (!defined $line) { > > $eof->send($got_version); > > + undef $f_out; > > } elsif (!$got_version) { > > if ($line =~ m{^ > > stunnel \s+ > > I believe $f_out will not be defined here, as it only gets set after > sub{} is created. Perl confirms this: > > $ TEST_STUNNEL=src/stunnel strace -f -o /tmp/log debian/tests/runtime > Global symbol "$f_out" requires explicit package name (did you forget to > declare "my $f_out"?) at debian/tests/runtime line 435. > Execution of debian/tests/runtime aborted due to compilation errors. Of course you're right. Sorry about that! That's what I get for writing a patch three minutes before I have to head out and never remembering to actually test it later :( How about the attached one? G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 commit eb303ad2e9c925bf7243e6877d8598d0356d68f9 Author: Peter Pentchev Date: Sun Aug 2 17:31:26 2020 +0300 Destroy the stunnel version watcher on EOF. diff --git a/debian/tests/runtime b/debian/tests/runtime index ecffe7b..f594d9a 100755 --- a/debian/tests/runtime +++ b/debian/tests/runtime @@ -424,7 +424,8 @@ MAIN: my ($got_version, $before_version) = (undef, ''); my $eof = AnyEvent->condvar; - my $f_out = AnyEvent->io( + my $f_out; + $f_out = AnyEvent->io( fh => $s_in, poll => 'r', cb => sub { @@ -432,6 +433,7 @@ MAIN: if (!defined $line) { $eof->send($got_version); + undef $f_out; } elsif (!$got_version) { if ($line =~ m{^ stunnel \s+ signature.asc Description: PGP signature
Bug#966562: marked as done (altos: hardcodes runtime json-c dependency)
Your message dated Wed, 05 Aug 2020 18:18:31 + with message-id and subject line Bug#966562: fixed in altos 1.9.4-2 has caused the Debian Bug report #966562, regarding altos: hardcodes runtime json-c dependency 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.) -- 966562: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966562 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: altos Version: 1.9.4-1 Severity: serious tags: patch Hello, please update to -c5 or better drop it in case you want to keep it, sed s/libjson-c4/libjson-c5/g -i debian/control does the job G. --- End Message --- --- Begin Message --- Source: altos Source-Version: 1.9.4-2 Done: Bdale Garbee We believe that the bug you reported is fixed in the latest version of altos, 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. Bdale Garbee (supplier of updated altos 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, 05 Aug 2020 11:27:40 -0600 Source: altos Architecture: source Version: 1.9.4-2 Distribution: unstable Urgency: medium Maintainer: Bdale Garbee Changed-By: Bdale Garbee Closes: 966562 Changes: altos (1.9.4-2) unstable; urgency=medium . * eliminate old explicit run-time dep on libjson-c4, closes: #966562 Checksums-Sha1: 28f9d52a9ee669489d74c23d8ec3453a13b47aa6 2263 altos_1.9.4-2.dsc b26ee95c2fc2a8dc81582a352af6e6733e39bdb5 77556 altos_1.9.4-2.debian.tar.xz bb3bced5bfbba3d6bd0b1820a8a50090b21e9c1c 12033 altos_1.9.4-2_amd64.buildinfo Checksums-Sha256: d4d4a34c8ceec850fe176ffdbd0b09b70556991ecfcfe3322c331208a510bf19 2263 altos_1.9.4-2.dsc 09b3924c9b6b73c33049246fdb8528271e257061fc9bdb23dea938745d7bdaf0 77556 altos_1.9.4-2.debian.tar.xz 38942fe7334934df8de6e15f4ff22cce165b7334362660512279526f027d373a 12033 altos_1.9.4-2_amd64.buildinfo Files: 8b3dff8a8dd9fc804953d512c847c27f 2263 electronics optional altos_1.9.4-2.dsc cd479ca840a9edcaade2f7194b26a777 77556 electronics optional altos_1.9.4-2.debian.tar.xz 662b95f79322d6ffce85f9329f43d573 12033 electronics optional altos_1.9.4-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEHguq2FwiMqGzzpLrtwRxBYMLn6EFAl8q8mcACgkQtwRxBYML n6GIfg/+MfsEqZDKfinGDjs1En8e1bB91QYMYC56j9D1eoqM0dQiMf9p9LOhFOJ/ iBvuDPsM3A1HHZVDc1miOlDb+WM26JbrL9cEx0P+tett3MgnQ/TyqovfJj9nQ88z ncSIyl6EWqf7JkrPbcQ1zK4DkGeV8eWG0ny8YPL7l9aPrn+U4a19msucvS5yYD1m wqM3/t09ZNkWa3rHL3E5bh0aoBm/ZNa/QgcG55eRtowF9TK2jdvBJf2MykxCAQD4 YJUDtrU7VZZObJXQNg4Xd4X+HVVHDDK7bHJuNvCUXj9/A2eltTYDjfxj5y2geJdX wqidZE0UdU/7QU+D0LN2dH6jlmQd3jUhi95TW3+3mGLgJlxRYFhyebx1Ek72c5/F 3CXabWSH4CMm0VQlOX4MvECckE87EnThjQrTD8c5gJKU+3CK4W1tmmNrQQXRf/9C KJdSK9Dpa6H4w+hM8kwvv/OmKfdaCXN7B8UqKhV9V1Q7ZQh3oBckWkpFaAinRXnr 4G4+pu9/X2WVa9MDL/xKJA3a/ufYg6qWZQnDN6afjjqEtdeN1Jhrk9K7U5dsXGm4 ALcfPQx9JLHkQagno7zmpa0nD9oGgWkww4n061AuOj0Mf8B7ANaV97mFmJsSY6S/ jztkp2bM8ByfpgPgkORmq6DX/wgmsQywktOvr5Zei5zhFNsAgN8= =V+Os -END PGP SIGNATURE End Message ---
Bug#957360: insighttoolkit4: ftbfs with GCC-10
Greetings, Étienne Mollier, on 2020-08-04 20:31:23 +0200: > On Mon, 3 Aug 2020 08:45:35 +0200 Étienne Mollier > wrote: > > * an update to ITK 4.13.3. > > I am now working on this part. Hopefuly this will help getting > through the build process further. I updated the package to version 4.13.3, and so, last night build went through; actually it ended around 11:00 AM today. I'm seeing several test failures in the build log, with a message like: ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded (cannot open shared object file): ignored. Loading ITKPyBase... Traceback (most recent call last): File "", line 1, in File "/home/emollier/debian/med-team/insighttoolkit/BUILD/Wrapping/Generators/Python/itkLazy.py", line 44, in __getattribute__ itkBase.LoadModule(module, namespace) File "/home/emollier/debian/med-team/insighttoolkit/BUILD/Wrapping/Generators/Python/itkBase.py", line 118, in LoadModule LoadModule(dep, namespace) File "/home/emollier/debian/med-team/insighttoolkit/BUILD/Wrapping/Generators/Python/itkBase.py", line 118, in LoadModule LoadModule(dep, namespace) File "/home/emollier/debian/med-team/insighttoolkit/BUILD/Wrapping/Generators/Python/itkBase.py", line 128, in LoadModule module = loader.load(swigModuleName) File "/home/emollier/debian/med-team/insighttoolkit/BUILD/Wrapping/Generators/Python/itkBase.py", line 250, in load return imp.load_module(name, fp, pathname, description) File "/home/emollier/debian/med-team/insighttoolkit/BUILD/lib/ITKPyBasePython.py", line 15, in import _ITKPyBasePython ImportError: /home/emollier/debian/med-team/insighttoolkit/BUILD/lib/_ITKPyBasePython.so: undefined symbol: PyUnicode_FromFormat However, I am suspecting an ill placed `fakeroot` in my building command. That may just be my bad hopefully. I will redo a run in a clean chroot. Kind Regards, -- Étienne Mollier Old rsa/3072: 5ab1 4edf 63bb ccff 8b54 2fa9 59da 56fe fff3 882d New rsa/4096: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da Sent from /dev/pts/1, please excuse my verbosity. signature.asc Description: PGP signature
Bug#966692: stunnel4: FTBFS because of test hang
On Sun, Aug 02, 2020 at 05:34:40PM +0300, Peter Pentchev wrote: > On Sun, Aug 02, 2020 at 02:02:22AM +0200, Michał Mirosław wrote: [...] > --- a/debian/tests/runtime > +++ b/debian/tests/runtime > @@ -432,6 +432,7 @@ MAIN: > > if (!defined $line) { > $eof->send($got_version); > + undef $f_out; > } elsif (!$got_version) { > if ($line =~ m{^ > stunnel \s+ I believe $f_out will not be defined here, as it only gets set after sub{} is created. Perl confirms this: $ TEST_STUNNEL=src/stunnel strace -f -o /tmp/log debian/tests/runtime Global symbol "$f_out" requires explicit package name (did you forget to declare "my $f_out"?) at debian/tests/runtime line 435. Execution of debian/tests/runtime aborted due to compilation errors. $ dpkg -l perl Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii perl 5.28.1-6 amd64Larry Wall's Practical Extraction and Report Language Best Regards Michał Mirosław
Bug#936873: libhdate: diff for NMU version 1.6.02-2.1
The debdiff for my NMU for libhdate (versioned as 1.6.02-2.1) Cheers, Moritz diff -Nru libhdate-1.6.02/debian/changelog libhdate-1.6.02/debian/changelog --- libhdate-1.6.02/debian/changelog 2018-07-30 05:49:11.0 +0200 +++ libhdate-1.6.02/debian/changelog 2020-08-02 23:13:33.0 +0200 @@ -1,3 +1,11 @@ +libhdate (1.6.02-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Drop python-hdate, there are no remaining rdeps remaining +(Closes: #936873) + + -- Moritz Muehlenhoff Sun, 02 Aug 2020 23:13:33 +0200 + libhdate (1.6.02-2) unstable; urgency=medium * Update maintainer address (Closes: #899576) diff -Nru libhdate-1.6.02/debian/control libhdate-1.6.02/debian/control --- libhdate-1.6.02/debian/control 2018-07-30 05:41:00.0 +0200 +++ libhdate-1.6.02/debian/control 2020-08-02 23:11:28.0 +0200 @@ -7,8 +7,6 @@ Vcs-Git: https://salsa.debian.org/hebrew-team/libhdate.git Build-Depends: debhelper (>= 9), swig, - python-dev (>= 2.6.6-3~), - dh-python, dh-autoreconf, Standards-Version: 3.9.8 Homepage: http://libhdate.sourceforge.net/ @@ -26,20 +24,6 @@ This package contains headers and support files required to build new applications with libhdate. -Package: python-hdate -Section: python -Architecture: any -Provides: ${python:Provides} -Depends: libhdate1 (= ${binary:Version}), ${python:Depends}, ${shlibs:Depends}, ${misc:Depends} -Description: Provides a library that help use Hebrew dates (Python bindings) - LibHdate is a small C,C++ library for Hebrew dates, - holidays, and reading sequence (parasha). It is using - the source code from Amos Shapir's "hdate" package fixed and - patched by Nadav Har'El. The Torah reading sequence - is from tables by Zvi Har'El. - . - This package contains Python bindings to libhdate - Package: libhdate-perl Section: perl Architecture: any diff -Nru libhdate-1.6.02/debian/python-hdate.install libhdate-1.6.02/debian/python-hdate.install --- libhdate-1.6.02/debian/python-hdate.install 2018-07-30 05:28:32.0 +0200 +++ libhdate-1.6.02/debian/python-hdate.install 1970-01-01 01:00:00.0 +0100 @@ -1 +0,0 @@ -usr/lib/python*/* diff -Nru libhdate-1.6.02/debian/rules libhdate-1.6.02/debian/rules --- libhdate-1.6.02/debian/rules 2018-07-30 05:28:32.0 +0200 +++ libhdate-1.6.02/debian/rules 2020-08-02 23:11:45.0 +0200 @@ -3,10 +3,7 @@ ARCHLIB := $(shell perl -MConfig -e 'print $$Config{vendorarch}') %: - dh $* --with python2,autoreconf + dh $* --with autoreconf override_dh_auto_configure: dh_auto_configure -- --with-perl-sitelib-dir=$(ARCHLIB) - -override_dh_python2: - dh_python2 -s --no-guessing-versions
Bug#967953: Package not installable in sid due to missing dependencies python-argcomplete and python-ipaddr
Package: ifupdown2 Version: 1.2.7-1 Severity: grave The package ifupdown2 currently cannot be installed on systems running sid as the two of its dependencies, python-argcomplete and python-ipaddr, are no longer present in sid. The suggested packages python-gvgen and python-mako also no longer exist.
Bug#967199: marked as done (pypy: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 5 Aug 2020 17:35:39 + with message-id <20200805173539.3rjkikitsvx4f...@satie.tumbleweed.org.za> and subject line Re: Bug#967199: pypy: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967199, regarding pypy: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pypy Version: 7.3.1+dfsg-3 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Hi Matthias (2020.08.04_09:29:04_+) > Your package either build-depends, depends on one of those packages. Nope, it doesn't. It remains buildable and installable, so don't think there's any action to take here. There was #967036, but that's fixed. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272--- End Message ---
Bug#967201: marked as done (pypy3: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 5 Aug 2020 17:35:57 + with message-id <20200805173556.yamlnsd73sqbn...@satie.tumbleweed.org.za> and subject line Re: Bug#967201: pypy3: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967201, regarding pypy3: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967201: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967201 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:pypy3 Version: 7.3.1+dfsg-4 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Hi Matthias (2020.08.04_09:29:03_+) > Your package either build-depends, depends on one of those packages. Nope, it doesn't. It remains buildable and installable, so don't think there's any action to take here. There was #967036, but that's fixed. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272--- End Message ---
Bug#957710: ftbfs with GCC-10
Hi, I've written a patch. After that, I've seen Reiner Herrmann already posted a working solution. It's mostly the same fix but slightly different. Please consider my version as an alternative. IMAO mine is preferable ;) Regards, -- Antoni Villalonga https://friki.cat/ Description: Fix ftbfs with GCC-10 Forwarded: no Author: Antoni Villalonga Last-Update: 2020-08-05 --- a/proxychains/core.h +++ b/proxychains/core.h @@ -68,27 +68,27 @@ typedef int (*connect_t)(int, const struct sockaddr *, socklen_t); -connect_t true_connect; +extern connect_t true_connect; typedef struct hostent* (*gethostbyname_t)(const char *); -gethostbyname_t true_gethostbyname; +extern gethostbyname_t true_gethostbyname; typedef int (*getaddrinfo_t)(const char *, const char *, const struct addrinfo *, struct addrinfo **); -getaddrinfo_t true_getaddrinfo; +extern getaddrinfo_t true_getaddrinfo; typedef int (*freeaddrinfo_t)(struct addrinfo *); -freeaddrinfo_t true_freeaddrinfo; +extern freeaddrinfo_t true_freeaddrinfo; typedef int (*getnameinfo_t) (const struct sockaddr *, socklen_t, char *, socklen_t, char *, socklen_t, unsigned int); -getnameinfo_t true_getnameinfo; +extern getnameinfo_t true_getnameinfo; typedef struct hostent *(*gethostbyaddr_t) (const void *, socklen_t, int); -gethostbyaddr_t true_gethostbyaddr; +extern gethostbyaddr_t true_gethostbyaddr; int proxy_getaddrinfo(const char *node, const char *service, const struct addrinfo *hints, --- a/proxychains/libproxychains.c +++ b/proxychains/libproxychains.c @@ -81,6 +81,12 @@ unsigned int *proxy_count, chain_type *ct, my_network *subnets); +connect_t true_connect; +gethostbyname_t true_gethostbyname; +getaddrinfo_t true_getaddrinfo; +freeaddrinfo_t true_freeaddrinfo; +getnameinfo_t true_getnameinfo; +gethostbyaddr_t true_gethostbyaddr; static void init_lib() {
Bug#966878: marked as done (figtree: FTBFS: [javac] /<>/src/figtree/application/JSONTreeExporter.java:56: error: JSONTreeExporter is not abstract and does not override abstract method
Your message dated Wed, 05 Aug 2020 17:18:34 + with message-id and subject line Bug#966878: fixed in figtree 1.4.4-5 has caused the Debian Bug report #966878, regarding figtree: FTBFS: [javac] /<>/src/figtree/application/JSONTreeExporter.java:56: error: JSONTreeExporter is not abstract and does not override abstract method close() in TreeExporter 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.) -- 966878: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966878 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: figtree Version: 1.4.4-4 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): > debian/rules build > make: 'build' is up to date. > fakeroot debian/rules binary > dh binary --with javahelper >dh_update_autotools_config >dh_autoreconf >dh_auto_configure >jh_linkjars >dh_auto_build > ant -Duser.name debian > Buildfile: /<>/build.xml > > init: >[tstamp] Honouring environment variable SOURCE_DATE_EPOCH which has been > set to 1575395523 > [mkdir] Created dir: /<>/dist > > compile: > [javac] /<>/build.xml:40: warning: 'includeantruntime' was > not set, defaulting to build.sysclasspath=last; set to false for repeatable > builds > [javac] Compiling 127 source files to /<>/build > [javac] warning: [options] bootstrap class path not set in conjunction > with -source 6 > [javac] warning: [options] source value 6 is obsolete and will be removed > in a future release > [javac] warning: [options] target value 1.6 is obsolete and will be > removed in a future release > [javac] warning: [options] To suppress warnings about obsolete options, > use -Xlint:-options. > [javac] > /<>/src/figtree/application/JSONTreeExporter.java:56: error: > JSONTreeExporter is not abstract and does not override abstract method > close() in TreeExporter > [javac] public class JSONTreeExporter implements TreeExporter { > [javac]^ > [javac] > /<>/src/figtree/application/JSONTreeExporter.java:181: error: > exportTrees(Collection) in JSONTreeExporter cannot implement > exportTrees(Collection) in TreeExporter > [javac] public void exportTrees(Collection trees) > throws IOException { > [javac] ^ > [javac] overridden method does not throw IOException > [javac] > /<>/src/figtree/application/JSONTreeExporter.java:83: error: > exportTree(Tree) in JSONTreeExporter cannot implement exportTree(Tree) in > TreeExporter > [javac] public void exportTree(Tree tree) throws IOException { > [javac] ^ > [javac] overridden method does not throw IOException > [javac] Note: Some input files use or override a deprecated API. > [javac] Note: Recompile with -Xlint:deprecation for details. > [javac] Note: Some input files use unchecked or unsafe operations. > [javac] Note: Recompile with -Xlint:unchecked for details. > [javac] 3 errors > [javac] 4 warnings > > BUILD FAILED > /<>/build.xml:40: Compile failed; see the compiler error output > for details. > > Total time: 2 seconds > dh_auto_build: error: ant -Duser.name debian returned exit code 1 > make: *** [debian/rules:10: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2020/08/02/figtree_1.4.4-4_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! 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: figtree Source-Version: 1.4.4-5 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of figtree, 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. Andreas Tille (supplier of updated figtree package) (This message was generated automatically at their request; if you believe that there is a problem with it ple
Bug#966868: marked as done (igor: FTBFS: CDR3SeqData.h:20:10: error: ‘string’ in namespace ‘std’ does not name a type)
Your message dated Wed, 05 Aug 2020 17:04:08 + with message-id and subject line Bug#966868: fixed in igor 1.4.0+dfsg-2 has caused the Debian Bug report #966868, regarding igor: FTBFS: CDR3SeqData.h:20:10: error: ‘string’ in namespace ‘std’ does not name a type 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.) -- 966868: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966868 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: igor Version: 1.4.0+dfsg-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): > g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include/jemalloc -I/usr/include/gsl -fopenmp > -DIGOR_DATA_DIR=\"/usr/share/igor\" -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o igor-ExtractFeatures.o `test -f > 'ExtractFeatures.cpp' || echo './'`ExtractFeatures.cpp > In file included from ExtractFeatures.h:30, > from ExtractFeatures.cpp:26: > CDR3SeqData.h:20:10: error: ‘string’ in namespace ‘std’ does not name a type >20 | std::string CDR3nt; > | ^~ > CDR3SeqData.h:1:1: note: ‘std::string’ is defined in header ‘’; did > you forget to ‘#include ’? > +++ |+#include > 1 | > CDR3SeqData.h:21:10: error: ‘string’ in namespace ‘std’ does not name a type >21 | std::string CDR3aa; > | ^~ > CDR3SeqData.h:21:5: note: ‘std::string’ is defined in header ‘’; did > you forget to ‘#include ’? >21 | std::string CDR3aa; > | ^~~ > CDR3SeqData.h:22:10: error: ‘string’ in namespace ‘std’ does not name a type >22 | std::string strData(); > | ^~ > CDR3SeqData.h:22:5: note: ‘std::string’ is defined in header ‘’; did > you forget to ‘#include ’? >22 | std::string strData(); > | ^~~ > g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include/jemalloc -I/usr/include/gsl -fopenmp > -DIGOR_DATA_DIR=\"/usr/share/igor\" -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o igor-Genechoice.o `test -f 'Genechoice.cpp' || > echo './'`Genechoice.cpp > g++ -DHAVE_CONFIG_H -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 > -I/usr/include/jemalloc -I/usr/include/gsl -fopenmp > -DIGOR_DATA_DIR=\"/usr/share/igor\" -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -c -o igor-GenModel.o `test -f 'GenModel.cpp' || echo > './'`GenModel.cpp > make[3]: *** [Makefile:635: igor-ExtractFeatures.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2020/08/02/igor_1.4.0+dfsg-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! 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: igor Source-Version: 1.4.0+dfsg-2 Done: Andreas Tille We believe that the bug you reported is fixed in the latest version of igor, 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. Andreas Tille (supplier of updated igor 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: Wed, 05 Aug 2020 18:37:57 +0200 Source: igor Architecture: source Version: 1.4.0+dfsg-2 Distribution: unstable Urgency: medium Maintainer: Debian Med Packaging Team Changed-By: Andreas Tille Closes: 966868 Changes: igor (1.4.0+dfsg-2) unstable; urgency=medium . * Team upload. * Fix gcc-10 build Closes: #966868 * debhelper-compat 13 (routine-update) * Do not use outdated libcblas any more Checksums-Sha1: abdbef4bfeca05791819c88b5ba38b2772c34260 2046 igor_1.4.0+dfsg-2.dsc 0a31
Bug#967950: doxygen: Autopkgtest regression with json-c 0.15
Source: doxygen Version: 1.8.18-1 Severity: serious Justification: failing autopkgtest on amd64 Dear Maintainer, doxygen autopkgtest started failing after json-c 0.15-1 was uploaded to unstable. This blocks migration of some other packages: https://ci.debian.net/user/britney/jobs?package=doxygen See any of the “test log” links for the log, for example this one: https://ci.debian.net/data/autopkgtest/testing/amd64/d/doxygen/6526799/log.gz The relevant line is: error: Doxyfile not found and no input file specified! Attached is a patch that adapts the test to work with new json-c. However, I think it would be better if that test did not rely on any external data, and the needed data was shipped with doxygen itself. Maybe the test can build doxygen's own documentation? -- Dmitry Shachnev diff --git a/debian/tests/control b/debian/tests/control index f46086a..d707d73 100644 --- a/debian/tests/control +++ b/debian/tests/control @@ -1,2 +1,7 @@ Tests: run -Depends: apt:native, dpkg-dev, doxygen, graphviz:native +Depends: apt:native, + build-essential, + cmake:native, + doxygen, + dpkg-dev, + graphviz:native diff --git a/debian/tests/run b/debian/tests/run index 31e4da5..f84a376 100755 --- a/debian/tests/run +++ b/debian/tests/run @@ -7,6 +7,10 @@ trap "rm -rf $WORKDIR" 0 INT QUIT ABRT PIPE TERM cd $WORKDIR apt-get source json-c 2>&1 cd json-c-* +mkdir build +cd build +cmake .. +cd doc doxygen 2>&1 cd / rm -Rf "$WORKDIR" signature.asc Description: PGP signature
Bug#957620: marked as done (nvtv: ftbfs with GCC-10)
Your message dated Wed, 05 Aug 2020 16:05:42 + with message-id and subject line Bug#957620: fixed in nvtv 0.4.7-8.1 has caused the Debian Bug report #957620, regarding nvtv: 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.) -- 957620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:nvtv Version: 0.4.7-8 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/nvtv_0.4.7-8_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 [...] from /usr/include/glib-2.0/gio/giotypes.h:28, from /usr/include/glib-2.0/gio/gio.h:26, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from gui_i810.c:28: /usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here 679 | { | ^ In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31, from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30, from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30, from /usr/include/gtk-2.0/gtk/gtk.h:126, from gui_i810.c:28: /usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 73 | GTimeVal last_popdown; | ^~~~ In file included from /usr/include/glib-2.0/glib/galloca.h:32, from /usr/include/glib-2.0/glib.h:30, from /usr/include/glib-2.0/gobject/gbinding.h:28, from /usr/include/glib-2.0/glib-object.h:23, from /usr/include/glib-2.0/gio/gioenums.h:28, from /usr/include/glib-2.0/gio/giotypes.h:28, from /usr/include/glib-2.0/gio/gio.h:26, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from gui_i810.c:28: /usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here 551 | struct _GTimeVal |^ gcc -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -g -pthread -I/usr/include/gtk-2.0 -I/usr/lib/x86_64-linux-gnu/gtk-2.0/include -I/usr/include/pango-1.0 -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 -Wl,-z,relro -Wl,-dy,--as-needed -o nvtv nvtv.o print.o libc_wrapper.o xf86i2c.o pipe.o mmio.o tv_common.o tv_nv.o tv_tdfx.o tv_i810.o tv_i2c.o tv_null.o tv_bt.o tv_cx.o tv_nx.o tv_ch1_7007.o tv_ch2_7009.o tv_ph1_saa7102.o tv_ph2_saa7104.o data.o data_bt.o data_cx.o data_ch.o data_ph.o data_nx.o data_nv.o data_tdfx.o data_i810.o data_xbox.o data_vesa.o calc_bt.o back_direct.o back_nvidia.o back_tdfx.o ba ck_i810.o back_null.o card_direct.o back_unix.o back_client.o actions.o gui.o gui_bt.o gui_cx.o gui_ch.o gui_ph.o gui_nx.o gui_nv.o gui_tdfx.o gui_i810.o -lSM -lICE -lgtk-x11-2.0 -lgdk-x11-2.0 -lpangocairo-1.0 -latk-1.0 -lcairo -lgdk_pixbuf-2.0
Bug#957114: marked as done (ctwm: ftbfs with GCC-10)
Your message dated Wed, 05 Aug 2020 16:03:47 + with message-id and subject line Bug#957114: fixed in ctwm 3.7-5 has caused the Debian Bug report #957114, regarding ctwm: 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.) -- 957114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ctwm Version: 3.7-4 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/ctwm_3.7-4_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DFUNCPROTO=15 -DNARROWPROTO-DUSEM4 -DGNOME -DXPM -DJPEG -DX11R6 -DSOUNDS -DI18N -DUSE_GNU_REGEX `dpkg-buildflags --get CPPFLAGS` -c -o workmgr.o workmgr.c In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, from /usr/include/stdio.h:27, from workmgr.c:26: /usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~ gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DFUNCPROTO=15 -DNARROWPROTO-DUSEM4 -DGNOME -DXPM -DJPEG -DX11R6 -DSOUNDS -DI18N -DUSE_GNU_REGEX `dpkg-buildflags --get CPPFLAGS` -c -o windowbox.o windowbox.c In file included from /usr/include/x86_64-linux-gnu/bits/libc-header-start.h:33, from /usr/include/stdio.h:27, from windowbox.c:28: /usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~ gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -DFUNCPROTO=15 -DNARROWPROTO-DUSEM4 -DGNOME -DXPM -DJPEG -DX11R6 -DSOUNDS -DI18N -DUSE_GNU_REGEX `dpkg-buildflags --get CPPFLAGS` -c -o clicktofocus.o clicktofocus.c In file included from /usr/include/x86_64-linux-gnu/sys/types.h:25, from /usr/include/X11/Xlib.h:38, from twm.h:81, from clicktofocus.h:4, from clicktofocus.c:1: /usr/include/features.h:185:3: warning: #warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp] 185 | # warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" | ^~~ gcc -g -O2 -fno-strict-aliasing -Dlinux -D__amd64__ -D_POSIX_C_SOURCE=199309L
Bug#957223: marked as done (foxtrotgps: ftbfs with GCC-10)
Your message dated Wed, 05 Aug 2020 15:48:36 + with message-id and subject line Bug#957223: fixed in foxtrotgps 1.2.2+bzr324-1 has caused the Debian Bug report #957223, regarding foxtrotgps: 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.) -- 957223: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957223 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:foxtrotgps Version: 1.2.2-2 Severity: normal Tags: sid bullseye User: debian-...@lists.debian.org Usertags: ftbfs-gcc-10 Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-10/g++-10, but succeeds to build with gcc-9/g++-9. The severity of this report will be raised before the bullseye release, so nothing has to be done for the buster release. The full build log can be found at: http://people.debian.org/~doko/logs/gcc10-20200225/foxtrotgps_1.2.2-2_unstable_gcc10.log The last lines of the build log are at the end of this report. To build with GCC 10, either set CC=gcc-10 CXX=g++-10 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-10/porting_to.html [...] | ^~~~ In file included from /usr/include/glib-2.0/glib/galloca.h:32, from /usr/include/glib-2.0/glib.h:30, from /usr/include/glib-2.0/gobject/gbinding.h:28, from /usr/include/glib-2.0/glib-object.h:23, from /usr/include/glib-2.0/gio/gioenums.h:28, from /usr/include/glib-2.0/gio/giotypes.h:28, from /usr/include/glib-2.0/gio/gio.h:26, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from route.c:8: /usr/include/glib-2.0/glib/gtypes.h:551:8: note: declared here 551 | struct _GTimeVal |^ In file included from /usr/include/gtk-2.0/gtk/gtkobject.h:37, from /usr/include/gtk-2.0/gtk/gtkwidget.h:36, from /usr/include/gtk-2.0/gtk/gtkcontainer.h:35, from /usr/include/gtk-2.0/gtk/gtkbin.h:35, from /usr/include/gtk-2.0/gtk/gtkwindow.h:36, from /usr/include/gtk-2.0/gtk/gtkdialog.h:35, from /usr/include/gtk-2.0/gtk/gtkaboutdialog.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:33, from globals.h:6, from hrm_functions.c:19: /usr/include/gtk-2.0/gtk/gtktypeutils.h:236:1: warning: ‘GTypeDebugFlags’ is deprecated [-Wdeprecated-declarations] 236 | voidgtk_type_init (GTypeDebugFlagsdebug_flags); | ^~~~ In file included from /usr/include/glib-2.0/gobject/gobject.h:24, from /usr/include/glib-2.0/gobject/gbinding.h:29, from /usr/include/glib-2.0/glib-object.h:23, from /usr/include/glib-2.0/gio/gioenums.h:28, from /usr/include/glib-2.0/gio/giotypes.h:28, from /usr/include/glib-2.0/gio/gio.h:26, from /usr/include/gtk-2.0/gdk/gdkapplaunchcontext.h:30, from /usr/include/gtk-2.0/gdk/gdk.h:32, from /usr/include/gtk-2.0/gtk/gtk.h:32, from globals.h:6, from hrm_functions.c:19: /usr/include/glib-2.0/gobject/gtype.h:679:1: note: declared here 679 | { | ^ In file included from /usr/include/gtk-2.0/gtk/gtktoolitem.h:31, from /usr/include/gtk-2.0/gtk/gtktoolbutton.h:30, from /usr/include/gtk-2.0/gtk/gtkmenutoolbutton.h:30, from /usr/include/gtk-2.0/gtk/gtk.h:126, from globals.h:6, from hrm_functions.c:19: /usr/include/gtk-2.0/gtk/gtktooltips.h:73:3: warning: ‘GTimeVal’ is deprecated: Use 'GDateTime' instead [-Wdeprecated-declarations] 73 | GTimeVal last_popdown; | ^~~~ In file included from /usr/include/glib-2.0/glib/galloca.h:32, from
Bug#966910: marked as done (polymake: FTBFS: pool_allocator.h:36:19: error: ‘typedef std::size_t __gnu_cxx::__pool_alloc_base::size_t’ is private within this context)
Your message dated Wed, 05 Aug 2020 15:04:13 + with message-id and subject line Bug#966910: fixed in polymake 4.1-4 has caused the Debian Bug report #966910, regarding polymake: FTBFS: pool_allocator.h:36:19: error: ‘typedef std::size_t __gnu_cxx::__pool_alloc_base::size_t’ is private within this context 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.) -- 966910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: polymake Version: 4.0r1-3 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): > g++ -c -o /<>/build/Opt/apps/common/bounding_box.o -MMD -MT > /<>/build/Opt/apps/common/bounding_box.o -MF > /<>/build/Opt/apps/common/bounding_box.o.d -fPIC -pipe -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 > -ftemplate-depth-200 -fno-strict-aliasing -fopenmp -Wshadow -Wlogical-op > -Wconversion -Wzero-as-null-pointer-constant -Wno-parentheses > -Wno-error=unused-function -Wno-stringop-overflow -DPOLYMAKE_WITH_FLINT > -DPOLYMAKE_DEBUG=0 -DNDEBUG -O2 -DPOLYMAKE_APPNAME=common > -DPOLYMAKE_DEFINITION_SOURCE_FILE="bounding_box.cc" > -DPOLYMAKE_DEFINITION_SOURCE_DIR="../../src" > -I/<>/include/app-wrappers -I/<>/include/apps > -I/<>/include/external/permlib > -I/<>/include/external/TOSimplex > -I/<>/include/core-wrappers -I/<>/include/core > /<>/apps/common/cpperl/generated/wrap-bounding_box.cc && : > 'COMPILER_USED=10.2.0' > In file included from > /<>/include/core/polymake/internal/type_manip.h:21, > from > /<>/include/core/polymake/internal/iterators.h:21, > from > /<>/include/core/polymake/internal/shared_object.h:21, > from > /<>/include/core/polymake/internal/singular_containers.h:21, > from > /<>/include/core/polymake/internal/modified_containers.h:21, > from > /<>/include/core/polymake/internal/iterator_filters.h:21, > from > /<>/include/core/polymake/internal/sparse.h:21, > from /<>/include/core/polymake/GenericIO.h:21, > from /<>/include/core/polymake/perl/Value.h:21, > from /<>/include/core/polymake/client.h:22, > from > /<>/include/apps/polymake/common/bounding_box.h:21, > from > /<>/apps/common/cpperl/generated/../../src/bounding_box.cc:18, > from > /<>/apps/common/cpperl/generated/wrap-bounding_box.cc:6: > /<>/include/core/polymake/internal/pool_allocator.h:36:19: > error: ‘typedef std::size_t __gnu_cxx::__pool_alloc_base::size_t’ is private > within this context >36 |void* allocate(size_t n) > | ^~ > In file included from > /<>/include/core/polymake/internal/pool_allocator.h:25, > from > /<>/include/core/polymake/internal/type_manip.h:21, > from > /<>/include/core/polymake/internal/iterators.h:21, > from > /<>/include/core/polymake/internal/shared_object.h:21, > from > /<>/include/core/polymake/internal/singular_containers.h:21, > from > /<>/include/core/polymake/internal/modified_containers.h:21, > from > /<>/include/core/polymake/internal/iterator_filters.h:21, > from > /<>/include/core/polymake/internal/sparse.h:21, > from /<>/include/core/polymake/GenericIO.h:21, > from /<>/include/core/polymake/perl/Value.h:21, > from /<>/include/core/polymake/client.h:22, > from > /<>/include/apps/polymake/common/bounding_box.h:21, > from > /<>/apps/common/cpperl/generated/../../src/bounding_box.cc:18, > from > /<>/apps/common/cpperl/generated/wrap-bounding_box.cc:6: > /usr/include/c++/10/ext/pool_allocator.h:77:27: note: declared private here >77 | typedef std::size_t size_t; > | ^~ > In file included from > /<>/include/core/polymake/internal/type_manip.h:21, > from > /<>/include/core/polymake/internal/iterators.h:21, > from > /<>/include/core/polymake/internal/shared_object.h:21, > from > /<>/include/core/polymake/internal/singular_containers.h:21, > from > /<
Processed: xscorch: diff for NMU version 0.2.1-1+nmu4
Processing control commands: > tags 957995 + pending Bug #957995 [src:xscorch] xscorch: ftbfs with GCC-10 Added tag(s) pending. -- 957995: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957995 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957995: xscorch: diff for NMU version 0.2.1-1+nmu4
Control: tags 957995 + pending Dear maintainer, I've prepared an NMU for xscorch (versioned as 0.2.1-1+nmu3) and uploaded it to mentors to be sponsored. Please feel free to tell me if I should remove it. A debdiff showing all changes is attatched. Regards, -- Luis Paulo (lpfll) diff -Nru xscorch-0.2.1/debian/changelog xscorch-0.2.1/debian/changelog --- xscorch-0.2.1/debian/changelog 2020-07-02 09:57:17.0 -0300 +++ xscorch-0.2.1/debian/changelog 2020-08-05 01:00:19.0 -0300 @@ -1,3 +1,11 @@ +xscorch (0.2.1-1+nmu4) unstable; urgency=medium + + * Non-maintainer upload. + * debian/patches/gcc10.patch: fix a FTBFS witch gcc 10. Thanks to +Reiner Herrmann . (Closes: #957995) + + -- Luis Paulo Linares Wed, 05 Aug 2020 01:00:19 -0300 + xscorch (0.2.1-1+nmu3) unstable; urgency=medium * Non-maintainer upload. diff -Nru xscorch-0.2.1/debian/patches/gcc10.patch xscorch-0.2.1/debian/patches/gcc10.patch --- xscorch-0.2.1/debian/patches/gcc10.patch1969-12-31 21:00:00.0 -0300 +++ xscorch-0.2.1/debian/patches/gcc10.patch2020-08-05 01:00:19.0 -0300 @@ -0,0 +1,29 @@ +Description: Fix FTBFS with GCC 10 +Author: Reiner Herrmann +Bug-Debian: https://bugs.debian.org/957995 +Last-Update: 2020-08-05 +Index: xscorch-0.2.1/sgame/slscape.c +=== +--- xscorch-0.2.1.orig/sgame/slscape.c xscorch-0.2.1/sgame/slscape.c +@@ -56,6 +56,7 @@ static double _sc_lscape_eval_plains(dou + static double _sc_lscape_eval_traditional(double x); + static double _sc_lscape_eval_valley(double x); + ++double (*_sc_lscape_eval)(double x); + + + static double _sc_lscape_eval_none(__libj_unused double x) { +Index: xscorch-0.2.1/sgame/slscape.h +=== +--- xscorch-0.2.1.orig/sgame/slscape.h xscorch-0.2.1/sgame/slscape.h +@@ -64,7 +64,7 @@ void sc_lscape_setup(const struct _sc_co + + /* Interface to the profile evaluating function */ + #define sc_lscape_eval(x) ((*_sc_lscape_eval)(x)) +-double (*_sc_lscape_eval)(double x); ++extern double (*_sc_lscape_eval)(double x); + + + #endif /* __slscape_h_included */ diff -Nru xscorch-0.2.1/debian/patches/series xscorch-0.2.1/debian/patches/series --- xscorch-0.2.1/debian/patches/series 2018-03-31 11:36:36.0 -0300 +++ xscorch-0.2.1/debian/patches/series 2020-08-05 01:00:19.0 -0300 @@ -1,2 +1,3 @@ overlapping-memcpy gdk-include +gcc10.patch
Processed: Bug fixed, but new version needs work on autopkgtest (Was: Bug#966876: trinityrnaseq: FTBFS: sift_bam_max_cov.cpp:99:10: error: ‘string’ is not a member of ‘std’)
Processing control commands: > tags -1 pending Bug #966876 [src:trinityrnaseq] trinityrnaseq: FTBFS: sift_bam_max_cov.cpp:99:10: error: ‘string’ is not a member of ‘std’ Added tag(s) pending. -- 966876: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966876 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966876: Bug fixed, but new version needs work on autopkgtest (Was: Bug#966876: trinityrnaseq: FTBFS: sift_bam_max_cov.cpp:99:10: error: ‘string’ is not a member of ‘std’)
Control: tags -1 pending On Mon, Aug 03, 2020 at 10:07:38AM +0200, Lucas Nussbaum wrote: > Relevant part (hopefully): > > g++ -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong > > -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > > -Wl,-z,relro -Wl,-z,now sift_bam_max_cov.cpp -Wall -lhts -O2 -o bamsifter > > sift_bam_max_cov.cpp: In function ‘int main(int, char**)’: > > sift_bam_max_cov.cpp:99:10: error: ‘string’ is not a member of ‘std’ > >99 | std::string tmp_text(input_header->text, input_header->l_text); > > | ^~ > > sift_bam_max_cov.cpp:16:1: note: ‘std::string’ is defined in header > > ‘’; did you forget to ‘#include ’? > >15 | #include "htslib/bgzf.h" > > +++ |+#include I've fixed this bug (and I think new upstream has found another way by using '-std=c++11' option (which would be hopefully unneeded by my patch but I did not tested). Unfortunately the autopkgtest is broken by the new version which I imported as well. Not sure whether seqtk-trinity is missing and thus autopkgtest fails is the only problem. seqtk-trinity was provided as *binary* which needed to be removed in Files-Excluded. I have not checked how / whether it is build and whether other issues might exist. Any takers for the remaining issues? Kind regards Andreas. -- http://fam-tille.de
Processed: py2removal bugs severity updates - 2020-08-05 14:33:55.682620+00:00
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html > # and https://lists.debian.org/debian-python/2019/12/msg00076.html > # and https://lists.debian.org/debian-python/2020/03/msg00087.html > # mail threads for more details on this severity update > # python-mode is a module and has 0 external rdeps or not in testing > severity 937927 serious Bug #937927 [src:python-mode] python-mode: Python2 removal in sid/bullseye Severity set to 'serious' from 'important' > End of message, stopping processing here. Please contact me if you need assistance. -- 937927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: Bug#964541: flatpak: Wrong argument order for clone syscall seccomp filter on s390x (Was: make: Regression on s390x, echo EPERM, caused by posix_spawn change)
Processing control commands: > reassign -1 flatpak Bug #964541 [make-dfsg] make: Regression on s390x, echo EPERM, caused by posix_spawn change Bug reassigned from package 'make-dfsg' to 'flatpak'. No longer marked as found in versions 4.3-4. Ignoring request to alter fixed versions of bug #964541 to the same values previously set > retitle -1 flatpak: Wrong argument order for clone syscall seccomp filter on > s390x Bug #964541 [flatpak] make: Regression on s390x, echo EPERM, caused by posix_spawn change Changed Bug title to 'flatpak: Wrong argument order for clone syscall seccomp filter on s390x' from 'make: Regression on s390x, echo EPERM, caused by posix_spawn change'. -- 964541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964541 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964541: flatpak: Wrong argument order for clone syscall seccomp filter on s390x (Was: make: Regression on s390x, echo EPERM, caused by posix_spawn change)
Control: reassign -1 flatpak Control: retitle -1 flatpak: Wrong argument order for clone syscall seccomp filter on s390x Hello flatpak maintainer! On Wed, Aug 05, 2020 at 03:19:39PM +0200, Christian Borntraeger wrote: > > On 21.07.20 13:24, Julian Andres Klode wrote: > > On Tue, Jul 21, 2020 at 12:49:59PM +0200, Christian Borntraeger wrote: > >> On 21.07.20 10:18, Adrian Bunk wrote: > >>> [ adding debian-s390 to Cc ] > >>> > >>> On Wed, Jul 08, 2020 at 01:42:33PM +0200, Julian Andres Klode wrote: > Package: make-dfsg > Version: 4.3-4 > Severity: serious > Tags: patch > User: ubuntu-de...@lists.ubuntu.com > Usertags: origin-ubuntu groovy ubuntu-patch > > In Ubuntu, the attached patch was applied to achieve the following: > > The autopkgtests for flatpak-builder/s390x where failing with > > echo Building > make: echo: Operation not permitted > make: *** [Makefile:2: all] Error 127 > >> > >> Julian, > >> > >> is there a launchpad entry for the Ubuntu bug that was fixed by this > >> change? > > > > Yes, https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1886814, it's > > also > > in the IBM bugzilla thingy - you can see Andreas Krebbel is replying to > > that. > > FWIW, Stefan Liebler looked into this and this needs to be fixed in > flatpak-build. > See the bug for details. flatpak has the wrong argument order in the seccomp filter for 390x, the attached patch should fix it. -- debian developer - deb.li/jak | jak-linux.org - free software dev ubuntu core developer i speak de, en Description: Fix argument order of clone() for s390x in seccomp filter clone() is a mad syscall with about 4 different argument orders. While most of them agree that argument 0 is flags, s390 and s390x have the flags argument second - A0 is the child stack pointer there. Author: Julian Andres Klode Bug-Debian: https://bugs.debian.org/964541 Bug-Ubuntu: https://launchpad.net/bugs/1886814 Forwarded: no Last-Update: 2020-08-05 --- flatpak-1.8.1.orig/common/flatpak-run.c +++ flatpak-1.8.1/common/flatpak-run.c @@ -2667,7 +2667,11 @@ setup_seccomp (FlatpakBwrap *bwrap, {SCMP_SYS (unshare)}, {SCMP_SYS (mount)}, {SCMP_SYS (pivot_root)}, +#if defined(__s390__) || defined(__s390x__) +{SCMP_SYS (clone), &SCMP_A1 (SCMP_CMP_MASKED_EQ, CLONE_NEWUSER, CLONE_NEWUSER)}, +#else {SCMP_SYS (clone), &SCMP_A0 (SCMP_CMP_MASKED_EQ, CLONE_NEWUSER, CLONE_NEWUSER)}, +#endif /* Don't allow faking input to the controlling tty (CVE-2017-5226) */ {SCMP_SYS (ioctl), &SCMP_A1 (SCMP_CMP_MASKED_EQ, 0xu, (int) TIOCSTI)},
Bug#937927: python-mode: Python2 removal in sid/bullseye
Control: severity -1 important Now uses python2 explicitly.
Bug#967204: marked as done (python-mode: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 5 Aug 2020 16:10:09 +0200 with message-id <7527aa13-762a-935a-c223-2f52e428c...@debian.org> and subject line Re: python-mode: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967204, regarding python-mode: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:python-mode Version: 1:6.2.3-1.3 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Version: 1:6.2.3-1.4 Fixed.--- End Message ---
Processed: Re: python-mode: Python2 removal in sid/bullseye
Processing control commands: > severity -1 important Bug #937927 [src:python-mode] python-mode: Python2 removal in sid/bullseye Severity set to 'important' from 'serious' -- 937927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966910: marked as done (polymake: FTBFS: pool_allocator.h:36:19: error: ‘typedef std::size_t __gnu_cxx::__pool_alloc_base::size_t’ is private within this context)
Your message dated Wed, 05 Aug 2020 13:48:40 + with message-id and subject line Bug#966910: fixed in polymake 4.1-3 has caused the Debian Bug report #966910, regarding polymake: FTBFS: pool_allocator.h:36:19: error: ‘typedef std::size_t __gnu_cxx::__pool_alloc_base::size_t’ is private within this context 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.) -- 966910: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966910 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: polymake Version: 4.0r1-3 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): > g++ -c -o /<>/build/Opt/apps/common/bounding_box.o -MMD -MT > /<>/build/Opt/apps/common/bounding_box.o -MF > /<>/build/Opt/apps/common/bounding_box.o.d -fPIC -pipe -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++14 > -ftemplate-depth-200 -fno-strict-aliasing -fopenmp -Wshadow -Wlogical-op > -Wconversion -Wzero-as-null-pointer-constant -Wno-parentheses > -Wno-error=unused-function -Wno-stringop-overflow -DPOLYMAKE_WITH_FLINT > -DPOLYMAKE_DEBUG=0 -DNDEBUG -O2 -DPOLYMAKE_APPNAME=common > -DPOLYMAKE_DEFINITION_SOURCE_FILE="bounding_box.cc" > -DPOLYMAKE_DEFINITION_SOURCE_DIR="../../src" > -I/<>/include/app-wrappers -I/<>/include/apps > -I/<>/include/external/permlib > -I/<>/include/external/TOSimplex > -I/<>/include/core-wrappers -I/<>/include/core > /<>/apps/common/cpperl/generated/wrap-bounding_box.cc && : > 'COMPILER_USED=10.2.0' > In file included from > /<>/include/core/polymake/internal/type_manip.h:21, > from > /<>/include/core/polymake/internal/iterators.h:21, > from > /<>/include/core/polymake/internal/shared_object.h:21, > from > /<>/include/core/polymake/internal/singular_containers.h:21, > from > /<>/include/core/polymake/internal/modified_containers.h:21, > from > /<>/include/core/polymake/internal/iterator_filters.h:21, > from > /<>/include/core/polymake/internal/sparse.h:21, > from /<>/include/core/polymake/GenericIO.h:21, > from /<>/include/core/polymake/perl/Value.h:21, > from /<>/include/core/polymake/client.h:22, > from > /<>/include/apps/polymake/common/bounding_box.h:21, > from > /<>/apps/common/cpperl/generated/../../src/bounding_box.cc:18, > from > /<>/apps/common/cpperl/generated/wrap-bounding_box.cc:6: > /<>/include/core/polymake/internal/pool_allocator.h:36:19: > error: ‘typedef std::size_t __gnu_cxx::__pool_alloc_base::size_t’ is private > within this context >36 |void* allocate(size_t n) > | ^~ > In file included from > /<>/include/core/polymake/internal/pool_allocator.h:25, > from > /<>/include/core/polymake/internal/type_manip.h:21, > from > /<>/include/core/polymake/internal/iterators.h:21, > from > /<>/include/core/polymake/internal/shared_object.h:21, > from > /<>/include/core/polymake/internal/singular_containers.h:21, > from > /<>/include/core/polymake/internal/modified_containers.h:21, > from > /<>/include/core/polymake/internal/iterator_filters.h:21, > from > /<>/include/core/polymake/internal/sparse.h:21, > from /<>/include/core/polymake/GenericIO.h:21, > from /<>/include/core/polymake/perl/Value.h:21, > from /<>/include/core/polymake/client.h:22, > from > /<>/include/apps/polymake/common/bounding_box.h:21, > from > /<>/apps/common/cpperl/generated/../../src/bounding_box.cc:18, > from > /<>/apps/common/cpperl/generated/wrap-bounding_box.cc:6: > /usr/include/c++/10/ext/pool_allocator.h:77:27: note: declared private here >77 | typedef std::size_t size_t; > | ^~ > In file included from > /<>/include/core/polymake/internal/type_manip.h:21, > from > /<>/include/core/polymake/internal/iterators.h:21, > from > /<>/include/core/polymake/internal/shared_object.h:21, > from > /<>/include/core/polymake/internal/singular_containers.h:21, > from > /<
Bug#964541: make: Regression on s390x, echo EPERM, caused by posix_spawn change
On 21.07.20 13:24, Julian Andres Klode wrote: > On Tue, Jul 21, 2020 at 12:49:59PM +0200, Christian Borntraeger wrote: >> On 21.07.20 10:18, Adrian Bunk wrote: >>> [ adding debian-s390 to Cc ] >>> >>> On Wed, Jul 08, 2020 at 01:42:33PM +0200, Julian Andres Klode wrote: Package: make-dfsg Version: 4.3-4 Severity: serious Tags: patch User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu groovy ubuntu-patch In Ubuntu, the attached patch was applied to achieve the following: The autopkgtests for flatpak-builder/s390x where failing with echo Building make: echo: Operation not permitted make: *** [Makefile:2: all] Error 127 >> >> Julian, >> >> is there a launchpad entry for the Ubuntu bug that was fixed by this change? > > Yes, https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1886814, it's > also > in the IBM bugzilla thingy - you can see Andreas Krebbel is replying to that. FWIW, Stefan Liebler looked into this and this needs to be fixed in flatpak-build. See the bug for details.
Processed: Bug#964679 marked as pending in gtk+3.0
Processing control commands: > tag -1 pending Bug #964679 [src:gtk+3.0] gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below Ignoring request to alter tags of bug #964679 to the same tags previously set -- 964679: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964679 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#964679: marked as pending in gtk+3.0
Control: tag -1 pending Hello, Bug #964679 in gtk+3.0 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gtk3/-/commit/df6191ce8af70e94235b96cc8a513c0a65a51b63 Add proposed patch to fix FTBFS with newer GLib versions Closes: #964679 (this message was generated automatically) -- Greetings https://bugs.debian.org/964679
Bug#966885: marked as done (spring: FTBFS: SHA512.cpp:25:3: error: ‘snprintf’ was not declared in this scope)
Your message dated Wed, 05 Aug 2020 13:03:50 + with message-id and subject line Bug#966885: fixed in spring 104.0+dfsg-7 has caused the Debian Bug report #966885, regarding spring: FTBFS: SHA512.cpp:25:3: error: ‘snprintf’ was not declared in this scope 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.) -- 966885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: spring Version: 104.0+dfsg-6 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): > cd /<>/obj-x86_64-linux-gnu/rts/builds/legacy && /usr/bin/c++ > -DASIO_STANDALONE -DBOOST_ALL_NO_LIB -DBOOST_NO_FENV_H -DBOOST_REGEX_DYN_LINK > -DBOOST_SYSTEM_DYN_LINK > -DSPRING_DATADIR=\"/usr/share/games/spring:/usr/lib/spring\" -DSTREFLOP_SSE > -DSYNCCHECK -DTHREADPOOL -DUSE_LIBSQUISH -D_GLIBCXX_USE_NANOSLEEP > -D_RANDOM_TCC -I/<>/rts/lib/lua/include > -I/<>/include/AL -I/<>/rts > -I/<>/rts/lib/assimp/include > -I/<>/obj-x86_64-linux-gnu/src-generated/engine > -I/<>/obj-x86_64-linux-gnu/rts/lib/gflags/include > -I/usr/include/SDL2 -I/usr/include/freetype2 -I/usr/include/AL > -I/<>/rts/lib/asio/include > -I/<>/rts/lib/slimsig/include -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++11 > -fdiagnostics-color=auto -mtune=generic -msse -mfpmath=sse -mno-sse2 > -mno-sse3 -mno-ssse3 -mno-sse4.1 -mno-sse4.2 -mno-sse4 -mno-sse4a -mno-avx > -mno-fma -mno-fma4 -mno-xop -mno-lwp -mno-avx2 -fsingle-precision-constant > -frounding-math -mieee-fp -pipe -fno-strict-aliasing -fvisibility=hidden > -fvisibility-inlines-hidden -pthread -O2 -Wformat -Wformat-security > -DNDEBUG -g -o > CMakeFiles/engine-legacy.dir/__/__/System/Platform/SharedLib.cpp.o -c > /<>/rts/System/Platform/SharedLib.cpp > /<>/rts/System/Sync/SHA512.cpp: In function ‘void > sha512::dump_digest(const std::array&, std::array 129>&)’: > /<>/rts/System/Sync/SHA512.cpp:25:3: error: ‘snprintf’ was not > declared in this scope >25 | snprintf(hex_chars.data() + (i * 2), hex_chars.size() - (i * 2), > "%02x", sha_bytes[i]); > | ^~~~ > /<>/rts/System/Sync/SHA512.cpp:7:1: note: ‘snprintf’ is defined > in header ‘’; did you forget to ‘#include ’? > 6 | #include "SHA512.hpp" > +++ |+#include > 7 | > make[4]: *** > [rts/builds/headless/CMakeFiles/engine-headless.dir/build.make:4174: > rts/builds/headless/CMakeFiles/engine-headless.dir/__/__/System/Sync/SHA512.cpp.o] > Error 1 The full build log is available from: http://qa-logs.debian.net/2020/08/02/spring_104.0+dfsg-6_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: spring Source-Version: 104.0+dfsg-7 Done: Markus Koschany We believe that the bug you reported is fixed in the latest version of spring, 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. Markus Koschany (supplier of updated spring 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, 05 Aug 2020 14:05:12 +0200 Source: spring Architecture: source Version: 104.0+dfsg-7 Distribution: unstable Urgency: medium Maintainer: Debian Games Team Changed-By: Markus Koschany Closes: 966885 Changes: spring (104.0+dfsg-7) unstable; urgency=medium . * Switch to debhelper-compat = 13. * Fix build failure with gcc 10 due to missing include. Thanks to Steve Langasek for the patch. (Closes: #966885) Checksums-Sha1: 6e54d99c7e8dd1d1de0a486c4ba1c87e89c89835 2519 spring_104.0+dfsg-7.dsc c6c481d5
Bug#966927: marked as done (gammapy: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)
Your message dated Wed, 05 Aug 2020 13:03:38 + with message-id and subject line Bug#966927: fixed in gammapy 0.17-2 has caused the Debian Bug report #966927, regarding gammapy: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 966927: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966927 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gammapy Version: 0.17-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): > fakeroot debian/rules clean > dh clean --with python3 --buildsystem=pybuild >dh_auto_clean -O--buildsystem=pybuild > I: pybuild base:217: python3.8 setup.py clean > Compiling gammapy/stats/fit_statistics_cython.pyx because it depends on > /usr/lib/python3/dist-packages/Cython/Includes/numpy/__init__.pxd. > [1/1] Cythonizing gammapy/stats/fit_statistics_cython.pyx > running clean > removing '/<>/.pybuild/cpython3_3.8_gammapy/build' (and > everything under it) > 'build/bdist.linux-x86_64' does not exist -- can't clean it > 'build/scripts-3.8' does not exist -- can't clean it >dh_autoreconf_clean -O--buildsystem=pybuild >dh_clean -O--buildsystem=pybuild > dpkg-source -b . > dpkg-source: info: using source format '3.0 (quilt)' > dpkg-source: info: building gammapy using existing ./gammapy_0.17.orig.tar.gz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: local changes detected, the modified files are: > gammapy-0.17/gammapy/stats/fit_statistics_cython.c > dpkg-source: error: aborting due to unexpected upstream changes, see > /tmp/gammapy_0.17-1.diff.qQQCXp > dpkg-source: info: you can integrate the local changes with dpkg-source > --commit > dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 > > Build finished at 2020-08-02T17:22:09Z The full build log is available from: http://qa-logs.debian.net/2020/08/02/gammapy_0.17-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: gammapy Source-Version: 0.17-2 Done: Ole Streicher We believe that the bug you reported is fixed in the latest version of gammapy, 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. Ole Streicher (supplier of updated gammapy 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, 05 Aug 2020 14:44:49 +0200 Source: gammapy Architecture: source Version: 0.17-2 Distribution: unstable Urgency: medium Maintainer: Debian Astro Team Changed-By: Ole Streicher Closes: 966927 Changes: gammapy (0.17-2) unstable; urgency=medium . * Remove cythonized file. (Closes: #966927) Checksums-Sha1: 7236c007dc16403e70f1d72a105c442c82f89e0a 2501 gammapy_0.17-2.dsc 9beb2b8cfbb563713341d77b8a7e36875a20cff0 5564 gammapy_0.17-2.debian.tar.xz Checksums-Sha256: b64f42c8f2313575c45e4493a46e48e191d055a38a706089e9fef90ed50a2b9d 2501 gammapy_0.17-2.dsc aa584bbdcff6a3f1521e1f8fa4b1c1c8d18986971242cddf8a81ce44928db3f3 5564 gammapy_0.17-2.debian.tar.xz Files: bf87c9151d10eda613dab1f8bcdea9b0 2501 python optional gammapy_0.17-2.dsc 6675a4e947f787cf43d4e59397345467 5564 python optional gammapy_0.17-2.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE7/BpV0Ra2/h0L3qtmk9WvbkOGL0FAl8qqogACgkQmk9WvbkO GL2+9w/8CZQxTPAVQTIDM2MddDVEWrQnQvfVmEzXgw2Dpb3XaCP0N2oxqLBh/JSo uVmHoAe3V15N46yMJUPhiuB1zGJNve/Zo00EmC1TcJx44Wm/Pm4QeSM8fljkgfz1 JxAlhsjnuQucxjE+9iZmyY4cdGe4q4go+/2pMYL7apjOiQwMcC6U4UlqLyMrALgJ
Bug#966962: marked as done (flask-restful: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8 returned exit code 13)
Your message dated Wed, 05 Aug 2020 13:03:33 + with message-id and subject line Bug#966962: fixed in flask-restful 0.3.8-3 has caused the Debian Bug report #966962, regarding flask-restful: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p 3.8 returned exit code 13 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.) -- 966962: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966962 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: flask-restful Version: 0.3.8-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): > make[2]: Entering directory '/<>/docs' > sphinx-build -b html -d _build/doctrees . _build/html > Running Sphinx v2.4.3 > making output directory... done > loading intersphinx inventory from > /usr/share/doc/python-flask-doc/html/objects.inv... > loading intersphinx inventory from > /usr/share/doc/python-werkzeug-doc/html/objects.inv... > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory '/usr/share/doc/python-flask-doc/html/objects.inv' not > fetchable due to : [Errno 2] No such file or > directory: '/usr/share/doc/python-flask-doc/html/objects.inv' > loading intersphinx inventory from > /usr/share/doc/python3-doc/html/objects.inv... > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory '/usr/share/doc/python-werkzeug-doc/html/objects.inv' > not fetchable due to : [Errno 2] No such file or > directory: '/usr/share/doc/python-werkzeug-doc/html/objects.inv' > loading intersphinx inventory from > /usr/share/doc/python3-doc/html/objects.inv... > loading intersphinx inventory from six/objects.inv... > WARNING: failed to reach any of the inventories with the following issues: > intersphinx inventory 'six/objects.inv' not fetchable due to 'FileNotFoundError'>: [Errno 2] No such file or directory: > '/<>/docs/six/objects.inv' > building [mo]: targets for 0 po files that are out of date > building [html]: targets for 9 source files that are out of date > updating environment: [new config] 9 added, 0 changed, 0 removed > reading sources... [ 11%] api > reading sources... [ 22%] extending > reading sources... [ 33%] fields > reading sources... [ 44%] index > reading sources... [ 55%] installation > reading sources... [ 66%] intermediate-usage > reading sources... [ 77%] quickstart > reading sources... [ 88%] reqparse > reading sources... [100%] testing > > /<>/docs/index.rst:6: WARNING: duplicate object description of > flask_restful, other instance in api, use :noindex: for one of them > /<>/docs/reqparse.rst:217: WARNING: Explicit markup ends without > a blank line; unexpected unindent. > looking for now-outdated files... none found > pickling environment... done > checking consistency... done > preparing documents... done > writing output... [ 11%] api > writing output... [ 22%] extending > writing output... [ 33%] fields > writing output... [ 44%] index > writing output... [ 55%] installation > writing output... [ 66%] intermediate-usage > writing output... [ 77%] quickstart > writing output... [ 88%] reqparse > writing output... [100%] testing > > /<>/docs/intermediate-usage.rst:80: WARNING: undefined label: > blueprints (if the link has no caption the label must precede a section > header) > /<>/docs/reqparse.rst:41: WARNING: undefined label: > error-messages (if the link has no caption the label must precede a section > header) > generating indices... genindex py-modindexdone > writing additional pages... searchdone > copying static files... ... done > copying extra files... done > dumping search index in English (code: en)... done > dumping object inventory... done > build succeeded, 7 warnings. > > The HTML pages are in _build/html. > > Build finished. The HTML pages are in _build/html. > make[2]: Leaving directory '/<>/docs' > make[1]: Leaving directory '/<>' >dh_auto_test -O--buildsystem=pybuild > I: pybuild base:217: cd > /<>/.pybuild/cpython3_3.8_flask-restful/build; python3.8 -m nose > -v tests > test_accept_default_any_pick_first (tests.test_accept.AcceptTestCase) ... ok > test_accept_default_application_json (tests.test_accept.AcceptTestCase) ... ok > test_accept_default_override_accept (tests.test_accept.AcceptTestCase) ... ok > test_accept_invalid_default_no_representations > (tests.test_accept.AcceptTestCase) ... ok > test_accept_no_defaul
Bug#966575: How to fix LLVM/LUKS installs?
I.d.k. if it helps: We had problems on many Systems (all of them used noninteractive installation method) We saw, that if we do debconf-show grub-pc it showed us a wrong device: grub2/update_nvram: true grub-pc/install_devices_failed: false grub2/force_efi_extra_removable: false * grub2/linux_cmdline: debian-installer=en_US grub-pc/kopt_extracted: false * grub2/linux_cmdline_default: quiet grub-pc/install_devices_disks_changed: grub2/kfreebsd_cmdline: grub-pc/install_devices_failed_upgrade: true grub2/kfreebsd_cmdline_default: quiet grub-pc/mixed_legacy_and_grub2: true grub-pc/hidden_timeout: false * grub-pc/install_devices: /dev/vda grub-pc/install_devices_empty: false grub-pc/partition_description: grub-pc/postrm_purge_boot_grub: false grub-pc/disk_description: grub-pc/timeout: 5 grub-pc/chainload_from_menu.lst: true * should be /dev/xvda if we start the installer manually (interactive) the output is like this * grub-pc/install_devices_disks_changed: /dev/xvda grub2/kfreebsd_cmdline: grub-pc/mixed_legacy_and_grub2: true grub-pc/kopt_extracted: false grub-pc/hidden_timeout: false grub-pc/partition_description: grub2/kfreebsd_cmdline_default: quiet grub-pc/timeout: 5 * grub2/linux_cmdline: debian-installer=en_US apparmor=1 security=apparmor grub-pc/disk_description: grub-pc/install_devices_empty: false * grub-pc/install_devices: /dev/xvda grub-pc/chainload_from_menu.lst: true grub2/force_efi_extra_removable: false grub-pc/postrm_purge_boot_grub: false grub-pc/install_devices_failed_upgrade: true * grub2/linux_cmdline_default: quiet grub2/update_nvram: true grub-pc/install_devices_failed: false with the last output the system worked flawlessly strangely we had no problems whatsoever with systems which where major upgraded to buster. All the Best Dorian
Processed: owner 966765
Processing commands for cont...@bugs.debian.org: > owner 966765 ! Bug #966765 [src:obs-build] obs-build: Unversioned Python removal in sid/bullseye Owner recorded as Andrej Shadura . > thanks Stopping processing here. Please contact me if you need assistance. -- 966765: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966765 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966765: obs-build: Unversioned Python removal in sid/bullseye
On Wed, 5 Aug 2020, at 14:39, Dimitri John Ledkov wrote: > On Sun, 02 Aug 2020 13:18:51 + Matthias Klose wrote: > > Package: src:obs-build > > Version: 20180831-3 > > Severity: serious > > Tags: sid bullseye > > User: debian-pyt...@lists.debian.org > > Usertags: py2unversioned > > > > Python2 becomes end-of-live upstream, and Debian aims to remove > > Python2 from the distribution, as discussed in > > https://lists.debian.org/debian-python/2019/07/msg00080.html > > > > We will keep some Python2 package as discussed in > > https://lists.debian.org/debian-python/2020/07/msg00039.html > > but removing the unversioned python packages python-minimal, python, > > python-dev, python-dbg, python-doc. > > > > Your package either build-depends, depends on one of those packages. > > Please either convert these packages to Python3, or if that is not > > possible, replaces the dependencies on the unversioned Python > > packages with one of the python2 dependencies (python2, python2-dev, > > python2-dbg, python2-doc). > > > > Please check for dependencies, build dependencies AND autopkg tests. > > > > If there are questions, please refer to the wiki page for the removal: > > https://wiki.debian.org/Python/2Removal, or ask for help on IRC > > #debian-python, or the debian-pyt...@lists.debian.org mailing list. > > > > > > This is obsolete version of obs-build which is no longer used or > maintained upstream. It has long moved on to python3 version, which > are still not packaged yet in Debian. > > Ditto other things in the same stack i.e. dnf / zypper / yum / rpm. > > Please RM obs-build, and somebody who still cares about OBS tooling in > Debian might want to repackage this. Please don't RM it, I'll update it shortly. > Note that OBS upstream do provide Debian & Ubuntu repositories with up > to date tooling, which is readily available and at this point in time, > recommended to be used. > > I've stopped using OBS years ago. > > -- > Regards, > > Dimitri. > > -- Cheers, Andrej
Processed: Bug#966885 marked as pending in spring
Processing control commands: > tag -1 pending Bug #966885 [src:spring] spring: FTBFS: SHA512.cpp:25:3: error: ‘snprintf’ was not declared in this scope Added tag(s) pending. -- 966885: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966885 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966885: marked as pending in spring
Control: tag -1 pending Hello, Bug #966885 in spring reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/games-team/spring/-/commit/e53b8e4b413013fd4860dc0bdbbfa2defe5445d7 Fix build failure with gcc 10 due to missing include. Closes: #966885 Thanks: Steve Langasek for the patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/966885
Bug#966765: obs-build: Unversioned Python removal in sid/bullseye
On Sun, 02 Aug 2020 13:18:51 + Matthias Klose wrote: > Package: src:obs-build > Version: 20180831-3 > Severity: serious > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2unversioned > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html > > We will keep some Python2 package as discussed in > https://lists.debian.org/debian-python/2020/07/msg00039.html > but removing the unversioned python packages python-minimal, python, > python-dev, python-dbg, python-doc. > > Your package either build-depends, depends on one of those packages. > Please either convert these packages to Python3, or if that is not > possible, replaces the dependencies on the unversioned Python > packages with one of the python2 dependencies (python2, python2-dev, > python2-dbg, python2-doc). > > Please check for dependencies, build dependencies AND autopkg tests. > > If there are questions, please refer to the wiki page for the removal: > https://wiki.debian.org/Python/2Removal, or ask for help on IRC > #debian-python, or the debian-pyt...@lists.debian.org mailing list. > > This is obsolete version of obs-build which is no longer used or maintained upstream. It has long moved on to python3 version, which are still not packaged yet in Debian. Ditto other things in the same stack i.e. dnf / zypper / yum / rpm. Please RM obs-build, and somebody who still cares about OBS tooling in Debian might want to repackage this. Note that OBS upstream do provide Debian & Ubuntu repositories with up to date tooling, which is readily available and at this point in time, recommended to be used. I've stopped using OBS years ago. -- Regards, Dimitri.
Bug#967153: marked as done (krb5-auth-dialog: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 5 Aug 2020 14:38:10 +0200 with message-id <8750b29f-6394-33f9-96d9-916de170c...@debian.org> and subject line Re: Bug#967153: krb5-auth-dialog: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967153, regarding krb5-auth-dialog: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967153: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967153 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:krb5-auth-dialog Version: 3.26.1-3 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- On 8/5/20 1:56 PM, Guido Günther wrote: > Hi, > On Tue, Aug 04, 2020 at 09:28:15AM +, Matthias Klose wrote: >> Package: src:krb5-auth-dialog >> Version: 3.26.1-3 >> Severity: serious >> Tags: sid bullseye >> User: debian-pyt...@lists.debian.org >> Usertags: py2unversioned >> >> Python2 becomes end-of-live upstream, and Debian aims to remove >> Python2 from the distribution, as discussed in >> https://lists.debian.org/debian-python/2019/07/msg00080.html >> >> We will keep some Python2 package as discussed in >> https://lists.debian.org/debian-python/2020/07/msg00039.html >> but removing the unversioned python packages python-minimal, python, >> python-dev, python-dbg, python-doc. >> >> Your package either build-depends, depends on one of those packages. >> Please either convert these packages to Python3, or if that is not >> possible, replaces the dependencies on the unversioned Python >> packages with one of the python2 dependencies (python2, python2-dev, >> python2-dbg, python2-doc). >> >> Please check for dependencies, build dependencies AND autopkg tests. > > Can you say how the list was generated? krb5-auth-dialog does not seem > to depend on any of these. that showed up because libglade2-dev was uninstallable. Closing.--- End Message ---
Bug#957849: marked as done (sup: ftbfs with GCC-10)
Your message dated Wed, 05 Aug 2020 12:20:49 + with message-id and subject line Bug#957849: fixed in sup 20100519-3 has caused the Debian Bug report #957849, regarding sup: 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.) -- 957849: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:sup Version: 20100519-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/sup_20100519-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 [...] dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh clean dh: warning: Compatibility levels before 9 are deprecated (level 7 in use) dh_auto_clean dh_auto_clean: warning: Compatibility levels before 9 are deprecated (level 7 in use) make -j1 distclean make[1]: Entering directory '/<>' rm -f sup supscan supfilesrv libextra.a netcrypt.c *.o core a.out make[1]: Leaving directory '/<>' dh_clean dh_clean: warning: Compatibility levels before 9 are deprecated (level 7 in use) debian/rules build dh build dh: warning: Compatibility levels before 9 are deprecated (level 7 in use) dh_update_autotools_config dh_auto_configure dh_auto_configure: warning: Compatibility levels before 9 are deprecated (level 7 in use) debian/rules override_dh_auto_build make[1]: Entering directory '/<>' dh_auto_build -- DEBIANCFLAGS="" SITE=LINUX dh_auto_build: warning: Compatibility levels before 9 are deprecated (level 7 in use) make -j1 DEBIANCFLAGS= SITE=LINUX make[2]: Entering directory '/<>' cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR -DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supcmain.o supcmain.c cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR -DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supcvers.o supcvers.c cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR -DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supcparse.o supcparse.c cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR -DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supcname.o supcname.c cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR -DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supcmisc.o supcmisc.c cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR -DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supcmeat.o supcmeat.c cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR -DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o scm.o scm.c scm.c: In function ‘service’: scm.c:316:2: warning: implicit declaration of function ‘setproctitle’ [-Wimplicit-function-declaration] 316 | setproctitle("Serving %s", remotehost()); | ^~~~ cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR -DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o scmio.o scmio.c cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR -DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o stree.o stree.c cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR -DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o log.o log.c cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR -DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o supmsg.o supmsg.c [ Using netcryptvoid.c ] cp netcryptvoid.c netcrypt.c cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR -DNEED_SETPROCTITLE -DLIBWRAP -I.-c -o netcrypt.o netcrypt.c cc -UCMUCS -UCMU -UMACH -DVAR_TMP -DHAS_DAEMON -DHAS_POSIX_DIR -
Bug#962596: ca-certificates: Removal of GeoTrust Global CA requires investigation
* Thomas Goirand [Wed Jul 15, 2020 at 02:48:20PM +0200]: > Thanks for maintaining ca-certificates. > I just wanted to let you know that a number of customers of $work are > affected by this, and we would very much welcome a return of the > GeoTrust Global CA. > It'd be nice if the uploaders of the ca-certificates could state what > they intend to do, so we could take the appropriate measure locally. Is there any news or timeline, or is there something we could help with to get this sorted out, Michael (Shuler)? regards -mika- signature.asc Description: Digital signature
Bug#957941: marked as done (wmcalclock: ftbfs with GCC-10)
Your message dated Wed, 05 Aug 2020 12:05:21 + with message-id and subject line Bug#957941: fixed in wmcalclock 1.25-16.1 has caused the Debian Bug report #957941, regarding wmcalclock: 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.) -- 957941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957941 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:wmcalclock Version: 1.25-16 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/wmcalclock_1.25-16_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 [...] SCHROOT_ALIAS_NAME=unstable SCHROOT_CHROOT_NAME=sid-amd64-sbuild SCHROOT_COMMAND=env SCHROOT_GID=1001 SCHROOT_GROUP=user42 SCHROOT_SESSION_ID=sid-amd64-sbuild-dd0a9ef6-63cd-4fa8-a84e-53db93ccd861 SCHROOT_UID=1001 SCHROOT_USER=user42 SHELL=/bin/sh USER=user42 dpkg-buildpackage - Command: dpkg-buildpackage -us -uc -b -rfakeroot dpkg-buildpackage: info: source package wmcalclock dpkg-buildpackage: info: source version 1.25-16 dpkg-buildpackage: info: source distribution unstable dpkg-buildpackage: info: source changed by Kevin Coyner dpkg-source --before-build . dpkg-buildpackage: info: host architecture amd64 fakeroot debian/rules clean dh_testdir dh_testroot rm -rf build-stamp install-stamp ./debian/wmcalclock find ./Src -name '*.o' | xargs rm -f make -C Src clean make[1]: Entering directory '/<>/Src' for i in wmCalClock.o xutils.o ; do \ rm -f $i; \ done rm -f wmCalClock make[1]: Leaving directory '/<>/Src' dh_clean debian/rules build dh_testdir make -C Src CFLAGS="-W -Wall -O2" make[1]: Entering directory '/<>/Src' x86_64-linux-gnu-gcc -W -Wall -O2 -DLinux -c wmCalClock.c -o wmCalClock.o -I/usr/X11R6/include/X11 -I/usr/X11R6/include wmCalClock.c: In function ‘ButtonPressEvent.part.0.isra’: wmCalClock.c:1034:27: warning: ‘%s’ directive writing up to 1023 bytes into a region of size 512 [-Wformat-overflow=] 1034 | sprintf(Command, "%s &", ExecuteCommand); | ^~ ~~ wmCalClock.c:1034:9: note: ‘sprintf’ output between 3 and 1026 bytes into a destination of size 512 1034 | sprintf(Command, "%s &", ExecuteCommand); | ^~~~ wmCalClock.c: In function ‘main’: wmCalClock.c:626:7: warning: ‘D[7]’ may be used uninitialized in this function [-Wmaybe-uninitialized] 626 | copyXPMArea(xsDigits[digit], yDigits, xdDigits[digit], ydDigits, xoff+extradx, 7+extrady); | ^ wmCalClock.c:623:24: warning: ‘D[6]’ may be used uninitialized in this function [-Wmaybe-uninitialized] 623 | xoff += (xdDigits[digit]+1); |^~~ x86_64-linux-gnu-gcc -W -Wall -O2 -DLinux -c xutils.c -o xutils.o -I/usr/X11R6/include/X11 -I/usr/X11R6/include xutils.c: In function ‘initXwindow’: xutils.c:139:22: warning: unused parameter ‘argc’ [-Wunused-parameter] 139 | void initXwindow(int argc, char *argv[]){ | ^~~~ x86_64-linux-gnu-gcc -o wmCalClock wmCalClock.o xutils.o -I/usr/X11R6/include/X11 -I/usr/X11R6/include -L/usr/X11R6/lib -lXpm -lX11 -lXext /usr/bin/ld: xutils.o:(.bss+0x1e8): multiple definition of `iconwin'; wmCalClock.o:(.bss+0x8e0): first defined here /usr/bin/ld: xutils.o:(.bss+0x1f8): multiple definition of `display'; wmCalClock.o:(.bss+0x8f0): first defined here
Bug#967153: krb5-auth-dialog: Unversioned Python removal in sid/bullseye
Hi, On Tue, Aug 04, 2020 at 09:28:15AM +, Matthias Klose wrote: > Package: src:krb5-auth-dialog > Version: 3.26.1-3 > Severity: serious > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2unversioned > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the distribution, as discussed in > https://lists.debian.org/debian-python/2019/07/msg00080.html > > We will keep some Python2 package as discussed in > https://lists.debian.org/debian-python/2020/07/msg00039.html > but removing the unversioned python packages python-minimal, python, > python-dev, python-dbg, python-doc. > > Your package either build-depends, depends on one of those packages. > Please either convert these packages to Python3, or if that is not > possible, replaces the dependencies on the unversioned Python > packages with one of the python2 dependencies (python2, python2-dev, > python2-dbg, python2-doc). > > Please check for dependencies, build dependencies AND autopkg tests. Can you say how the list was generated? krb5-auth-dialog does not seem to depend on any of these. Cheers, -- Guido > > If there are questions, please refer to the wiki page for the removal: > https://wiki.debian.org/Python/2Removal, or ask for help on IRC > #debian-python, or the debian-pyt...@lists.debian.org mailing list.
Bug#963356: marked as done (cross-toolchain-base-mipsen: FTBFS: dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2)
Your message dated Wed, 5 Aug 2020 19:41:41 +0800 with message-id and subject line Re: cross-toolchain-base-mipsen: FTBFS: dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2 has caused the Debian Bug report #963356, regarding cross-toolchain-base-mipsen: FTBFS: dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned exit status 2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 963356: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: cross-toolchain-base-mipsen Version: 10 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20200620 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > fakeroot debian/rules clean > debian/kernelarch.make:5: *** empty variable name. Stop. > dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned > exit status 2 > > Build finished at 2020-06-21T07:14:58Z The full build log is available from: http://qa-logs.debian.net/2020/06/20/cross-toolchain-base-mipsen_10_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 --- On Sun, 21 Jun 2020 22:20:52 +0200 Lucas Nussbaum wrote: > Source: cross-toolchain-base-mipsen > Version: 10 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200620 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > This problem has been fixed in version 11. > Relevant part (hopefully): > > fakeroot debian/rules clean > > debian/kernelarch.make:5: *** empty variable name. Stop. > > dpkg-buildpackage: error: fakeroot debian/rules clean subprocess returned > > exit status 2 > > > > Build finished at 2020-06-21T07:14:58Z > > The full build log is available from: > > http://qa-logs.debian.net/2020/06/20/cross-toolchain-base-mipsen_10_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 ---
Processed: atlc: diff for NMU version 4.6.1-2.1
Processing control commands: > tags 957019 + patch Bug #957019 [src:atlc] atlc: ftbfs with GCC-10 Added tag(s) patch. > tags 957019 + pending Bug #957019 [src:atlc] atlc: ftbfs with GCC-10 Added tag(s) pending. -- 957019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957019 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#957019: atlc: diff for NMU version 4.6.1-2.1
Control: tags 957019 + patch Control: tags 957019 + pending Dear maintainer, I've prepared an NMU for atlc (versioned as 4.6.1-2.1) and uploaded it to DELAYED/5. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru atlc-4.6.1/debian/changelog atlc-4.6.1/debian/changelog --- atlc-4.6.1/debian/changelog 2017-12-30 04:06:57.0 + +++ atlc-4.6.1/debian/changelog 2020-08-05 12:17:38.0 +0100 @@ -1,3 +1,10 @@ +atlc (4.6.1-2.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fix ftbfs with GCC-10. (Closes: #957019) + + -- Sudip Mukherjee Wed, 05 Aug 2020 12:17:38 +0100 + atlc (4.6.1-2) unstable; urgency=medium * remove libgsl0-dev build dependency, closes: #823876 diff -Nru atlc-4.6.1/debian/patches/fix_ftbfs.patch atlc-4.6.1/debian/patches/fix_ftbfs.patch --- atlc-4.6.1/debian/patches/fix_ftbfs.patch 1970-01-01 01:00:00.0 +0100 +++ atlc-4.6.1/debian/patches/fix_ftbfs.patch 2020-08-05 12:10:16.0 +0100 @@ -0,0 +1,19 @@ +Description: Fix ftbfs with GCC-10 + +Author: Sudip Mukherjee +Bug-Debian: https://bugs.debian.org/957019 +Forwarded: no + +--- + +--- atlc-4.6.1.orig/src/swap_conductor_voltages.c atlc-4.6.1/src/swap_conductor_voltages.c +@@ -36,7 +36,7 @@ CONDUCTOR_MINUS_ONE_V in definitions.h * + #include "definitions.h" + + extern int width, height; +-unsigned char **oddity; ++extern unsigned char **oddity; + extern double **Vij; + + /* This swaps any conductor orignally at -1 V to +1 V. Any diff -Nru atlc-4.6.1/debian/patches/series atlc-4.6.1/debian/patches/series --- atlc-4.6.1/debian/patches/series2017-12-30 04:06:57.0 + +++ atlc-4.6.1/debian/patches/series2020-08-05 12:08:40.0 +0100 @@ -1,3 +1,4 @@ atlc.1.patch lintian-fixes.diff lintian-fixes2.diff +fix_ftbfs.patch
Bug#966983: python-skbio: FTBFS: dh_sphinxdoc: error: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/search.html does not load searchindex.js
Control: tags -1 unreproducible On Mon, Aug 03, 2020 at 11:05:59AM +0200, Lucas Nussbaum wrote: > Source: python-skbio > Version: 0.5.6-2 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200802 ftbfs-bullseye ... > > dh_sphinxdoc --package=python-skbio-doc > > dh_sphinxdoc: error: > > debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/search.html > > does not load searchindex.js > > make[1]: *** [debian/rules:41: override_dh_sphinxdoc] Error 25 I tried to reproduce this bug I get: dh_sphinxdoc --package=python-skbio-doc dh_sphinxdoc: warning: ignoring unknown JavaScript code: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/bootstrap-sphinx.js dh_sphinxdoc: warning: ignoring unknown JavaScript code: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/copybutton.js dh_sphinxdoc: warning: ignoring unknown JavaScript code: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/MathJax.js dh_sphinxdoc: warning: ignoring unknown JavaScript code: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/bootstrap-3.3.7/js/bootstrap.min.js dh_sphinxdoc: warning: ignoring unknown JavaScript code: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/js/jquery-fix.js dh_sphinxdoc: warning: ignoring unknown JavaScript code: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/_static/js/jquery-1.11.0.min.js No error so far. Thus I'm tempted to close this bug. Kind regards Andreas. -- http://fam-tille.de
Processed: Re: Bug#966983: python-skbio: FTBFS: dh_sphinxdoc: error: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/search.html does not load searchindex.js
Processing control commands: > tags -1 unreproducible Bug #966983 [src:python-skbio] python-skbio: FTBFS: dh_sphinxdoc: error: debian/python-skbio-doc/usr/share/doc/python-skbio-doc/html/search.html does not load searchindex.js Added tag(s) unreproducible. -- 966983: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966983 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967156: marked as done (ledger: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 05 Aug 2020 11:18:44 + with message-id and subject line Bug#967156: fixed in ledger 3.2.1-2 has caused the Debian Bug report #967156, regarding ledger: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ledger Version: 3.2.1-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- Source: ledger Source-Version: 3.2.1-2 Done: David Bremner We believe that the bug you reported is fixed in the latest version of ledger, 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 967...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Bremner (supplier of updated ledger 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: Wed, 05 Aug 2020 07:46:45 -0300 Source: ledger Architecture: source Version: 3.2.1-2 Distribution: unstable Urgency: medium Maintainer: David Bremner Changed-By: David Bremner Closes: 843112 967156 Changes: ledger (3.2.1-2) unstable; urgency=medium . * Bug fix: "Unversioned Python removal in sid/bullseye", thanks to Matthias Klose (Closes: #967156). * Bug fix: "ledger deb package should suggest ledger-el", thanks to Thierry (Closes: #843112). Checksums-Sha1: 7ab04cfd0118817f6d4af06c32f6460a9e276aef 2251 ledger_3.2.1-2.dsc cf314e13325f2b5646b86b31059e5aabf611510c 7744 ledger_3.2.1-2.debian.tar.xz 5761c9507bf6816897a6bcd5a0a755dbcdbed510 584624 ledger_3.2.1.orig.tar.xz Checksums-Sha256: 67ab59b157db4bf5fbb04862e266c36b89308837a4e0fdf9b639c29baf4b61b4 2251 ledger_3.2.1-2.dsc 332310b6dfd37833e4549132d8176913d15727e37609313642492b0f7a82a19a 7744 ledger_3.2.1-2.debian.tar.xz 27dea60c2a314e59f2144365de3b0f4ad33ef72ea408046d58d475b61537a8d6 584624 ledger_3.2.1.orig.tar.xz Files: 60bbee567744c3a06017b5a1f49771a1 2251 utils optional ledger_3.2.1-2.dsc a03bcad8bcdb124edafa7bf9567cdf07 7744 utils optional ledger_3.2.1-2.debian.tar.xz 5dd2c2d5730e3ce959ea8ade0eda2519 584624 utils optional ledger_3.2.1.orig.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEkiyHYXwaY0SiY6fqA0U5G1WqFSEFAl8qj+kACgkQA0U5G1Wq FSGdqRAAqejB3LoAFq5qChJis/kYA5yyhbDQkvebKfWIyFIjqSOk8WbfbZ/q/Tdm 1ydrdIfnRSJik+Pp1+n2Cs2A0uRjswfXjrS7WvQeve/0SlS6OiooYfCXQu3Q2Mag awxavI7SCXQ5Cg3jPArrp5Etfm984kyOLonU0Wt5dIWTtjouJdlflAjyAS5WwLGg wAXoeNcXoI8GNH4vIl8i339RZuE+J9wG8ZvN1QF1t0AS+wBl1TslPjqXrH79YXkx +LNp5RfSmv+ij0P/vPxMijK7AVDU4K9f8Va3OmLD/Q7Y+BWWdFbwirgh8Jfo6X/h Hwqor+pM2T/Yg5j5Pf8tJG5TKSI0PcV0jMsZlUQGhvRVN+WUqI4/NpEENOgg2pHH +AB/LWy3Pn9HXPGsZBo+TNJ3Hbuub2zpgdrO2jdFFkszT76BI8q1q3pdJ80BMGkW yBDyq3/zjE4KK9NBrlkef/lB3Vb+iA6j21aI9QxVxN/nUFqBbsI0fWkMlNOFPz9q g0kl9Mzezo2fNE2QGTUyFWv/Fbf/IbZLtN26F1gO6AaP+EIvgQBgV7VDty4ha4Fg +DYjP4C+22IQ2xRkoww43ClwLBdLBykQ7aIeXMIWQSk/zESGO0s3BYBOcFzuk1d+ eZ6blaT3wFUMB5a4WjdQOk/Tl3sBOGRSYvn3skYd0Fyk3tskc+k= =bqbp -END PGP SIGNATURE End Message ---
Processed: bug 966436 is forwarded to https://github.com/ImageMagick/ImageMagick6/issues/90
Processing commands for cont...@bugs.debian.org: > forwarded 966436 https://github.com/ImageMagick/ImageMagick6/issues/90 Bug #966436 [src:imagemagick] scrambled property in identify -verbose output Set Bug forwarded-to-address to 'https://github.com/ImageMagick/ImageMagick6/issues/90'. > thanks Stopping processing here. Please contact me if you need assistance. -- 966436: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966436 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967012: vmem: FTBFS: FAIL: match: out0.log.match:2 did not match pattern
Control: block -1 by 964457 On Mon, Aug 03, 2020 at 01:19:42PM +0200, Lucas Nussbaum wrote: > Source: vmem > Version: 1.8-1 > Severity: serious > During a rebuild of all packages in sid, your package failed to build > on amd64. > > vmem_aligned_alloc@@LIBVMEM_1.0 > > vmem_calloc@@LIBVMEM_1.0 Another case of a test failing due to bogus decoration. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ ⢿⡄⠘⠷⠚⠋⠀ It's time to migrate your Imaginary Protocol from version 4i to 6i. ⠈⠳⣄
Processed: Re: Bug#966483: iptables-netflow: sourcing of external scripts in dkms file?
Processing control commands: > severity -1 normal Bug #966483 [src:iptables-netflow] iptables-netflow: sourcing of external scripts in dkms file? Severity set to 'normal' from 'serious' > tag -1 - patch Bug #966483 [src:iptables-netflow] iptables-netflow: sourcing of external scripts in dkms file? Removed tag(s) patch. -- 966483: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966483 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#966483: iptables-netflow: sourcing of external scripts in dkms file?
Control: severity -1 normal Control: tag -1 - patch Dear Gianfranco, first thanks for making me aware of suboptimal upstream code. Gianfranco Costamagna wrote: > Hello, looks like your dkms ship file is sourcing external stuff > with pushd/popd and so on. Not "external" stuff but stuff from its own source. > I don't think this is a sane idea, I disagree. Using pushd/popd (or "cd -") in scripts is a valid way to avoid a helper variable to save the previous directory. But what I dislike in the aforementioned code snippet is that $BASH_SOURCE is a) used at all and hence the script is not bourne-shell compatible. b) is used in an unclear way (couldn't find in bash(1) what the meaning of using an array as scalar should return. From my experiments, it seems to return its first value.) I also disagree that "I don't think this is a sane idea" is RC-level, not even important. Hence downgrading to "normal. > specially because in Debian we don't even use version.sh script to > fill the dkms.conf file. I don't understand what you refer to with "in Debian". Do you mean the fact that I didn't ship the package's upstream's version.sh? Do you think I should? > Can you please remove the two lines? At least not in the way you propsed. Hence removing the tag "patch". > this is what we do to test dkms packages: [...] > dkms_pkg=$(bash -c ". $dkms_conf; echo \$PACKAGE_NAME" 2>/dev/null) > dkms_ver=$(bash -c ". $dkms_conf; echo \$PACKAGE_VERSION" 2>/dev/null) You could do ". $dkms_conf > /dev/null" > bash -c ". dkms.conf; echo \$PACKAGE_NAME" > /tmp/iptables-netflow-2.5 /tmp/iptables-netflow-2.5 > /tmp/iptables-netflow-2.5 > ipt-netflow JFTR: This can also happen with "cd", depending on the shell's settings. (IIRC setting CDPATH might cause this. Granted, "bash -c" is probably neither an interactive nor an login shell and hence shouldn't source any local rc files, but I've ran into this with "cd" and some non-DKMS scripts, too, on some machines not administrated by myself. > I think dkms.conf files are meant to be sourced from outside, and > launching scripts is a bad idea. I don't see how this relates. > --- iptables-netflow-2.5.orig/dkms.conf > +++ iptables-netflow-2.5/dkms.conf > @@ -1,7 +1,5 @@ > PACKAGE_NAME="ipt-netflow" > -pushd `dirname $BASH_SOURCE` > PACKAGE_VERSION=`./version.sh` > -popd IMHO this makes it worse, because it will source version.sh from whatever working directory the script that sources dkms.conf was called from. I see these ways to solve this: * Remove that whole block including "PACKAGE_VERSION=`./version.sh`", or * make pushd/popd silent Regards, Axel -- ,''`. | Axel Beckert , https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `-| 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
Bug#966864: marked as done (libiscsi: FTBFS: ld: .libs/libiscsi_la-iser.o:./lib/./../include/iser-private.h:162: multiple definition of `__packed'; .libs/libiscsi_la-init.o:./lib/./../include/iser-pri
Your message dated Wed, 05 Aug 2020 11:03:45 + with message-id and subject line Bug#966864: fixed in libiscsi 1.19.0-2 has caused the Debian Bug report #966864, regarding libiscsi: FTBFS: ld: .libs/libiscsi_la-iser.o:./lib/./../include/iser-private.h:162: multiple definition of `__packed'; .libs/libiscsi_la-init.o:./lib/./../include/iser-private.h:162: 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.) -- 966864: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966864 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libiscsi Version: 1.19.0-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): > /bin/bash ../libtool --tag=CC --mode=link gcc -Wall -W -Wshadow > -Wstrict-prototypes -Wpointer-arith -Wcast-align -Wno-strict-aliasing > -Wno-unknown-warning-option -Wno-stringop-truncation -Wwrite-strings -g -O2 > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -version-info 7:0:0 -bindir /usr/bin -no-undefined > -export-symbols ./libiscsi.syms -libverbs -lrdmacm -lpthread -Wl,-z,relro > -Wl,-z,now -o libiscsi.la -rpath /usr/lib/x86_64-linux-gnu > libiscsi_la-connect.lo libiscsi_la-crc32c.lo libiscsi_la-discovery.lo > libiscsi_la-init.lo libiscsi_la-login.lo libiscsi_la-nop.lo > libiscsi_la-pdu.lo libiscsi_la-iscsi-command.lo libiscsi_la-scsi-lowlevel.lo > libiscsi_la-socket.lo libiscsi_la-sync.lo libiscsi_la-task_mgmt.lo > libiscsi_la-logging.lo libiscsi_la-md5.lo libiscsi_la-iser.lo > libtool: link: echo "{ global:" > .libs/libiscsi.ver > libtool: link: cat ./libiscsi.syms | sed -e "s/\(.*\)/\1;/" >> > .libs/libiscsi.ver > libtool: link: echo "local: *; };" >> .libs/libiscsi.ver > libtool: link: gcc -shared -fPIC -DPIC .libs/libiscsi_la-connect.o > .libs/libiscsi_la-crc32c.o .libs/libiscsi_la-discovery.o > .libs/libiscsi_la-init.o .libs/libiscsi_la-login.o .libs/libiscsi_la-nop.o > .libs/libiscsi_la-pdu.o .libs/libiscsi_la-iscsi-command.o > .libs/libiscsi_la-scsi-lowlevel.o .libs/libiscsi_la-socket.o > .libs/libiscsi_la-sync.o .libs/libiscsi_la-task_mgmt.o > .libs/libiscsi_la-logging.o .libs/libiscsi_la-md5.o .libs/libiscsi_la-iser.o > -libverbs -lrdmacm -lpthread -g -O2 -fstack-protector-strong -Wl,-z > -Wl,relro -Wl,-z -Wl,now -Wl,-soname -Wl,libiscsi.so.7 -Wl,-version-script > -Wl,.libs/libiscsi.ver -o .libs/libiscsi.so.7.0.0 > /usr/bin/ld: .libs/libiscsi_la-iser.o:./lib/./../include/iser-private.h:162: > multiple definition of `__packed'; > .libs/libiscsi_la-init.o:./lib/./../include/iser-private.h:162: 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/libiscsi_1.19.0-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: libiscsi Source-Version: 1.19.0-2 Done: Michael Tokarev We believe that the bug you reported is fixed in the latest version of libiscsi, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 966...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Tokarev (supplier of updated libiscsi 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: Wed, 05 Aug 2020 13:40:02 +0300 Source: libiscsi Architecture: source Version: 1.19.0-2 Distribution: unstable Urgency: medium Maintainer: Michael Tokarev Changed-By: Michael Tokarev Closes: 966864 Changes: libiscsi (1.19.0-2) unstable; urgency=medium . * attribute_packed.patch (Closes: #966864) * spelling.patch - fix a few selling mistakes * provide Build-Depends-Package for libiscsi.symbols * do not
Bug#964294: marked as done (mlpack FTBFS: dh_missing: error: missing files, aborting)
Your message dated Wed, 05 Aug 2020 10:49:11 + with message-id and subject line Bug#964294: fixed in mlpack 3.3.2-2 has caused the Debian Bug report #964294, regarding mlpack FTBFS: dh_missing: error: missing files, aborting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 964294: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964294 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: mlpack Version: 3.3.2-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=mlpack ... dh_missing -a -O--buildsystem=cmake -O--max-parallel=1 dh_missing: warning: usr/lib/x86_64-linux-gnu/cmake/mlpack/mlpack-targets-none.cmake exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/x86_64-linux-gnu/cmake/mlpack/mlpack-targets.cmake exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/x86_64-linux-gnu/cmake/mlpack/mlpack-config-version.cmake exists in debian/tmp but is not installed to anywhere dh_missing: warning: usr/lib/x86_64-linux-gnu/cmake/mlpack/mlpack-config.cmake exists in debian/tmp but is not installed to anywhere dh_missing: error: missing files, aborting The following debhelper tools have reported what they installed (with files per package) * dh_install: libmlpack-dev (45), libmlpack3 (2), mlpack-bin (1), mlpack-doc (37), python3-mlpack (2) * dh_installdocs: libmlpack-dev (0), libmlpack3 (0), mlpack-bin (0), mlpack-doc (6), python3-mlpack (0) * dh_installexamples: libmlpack-dev (0), libmlpack3 (0), mlpack-bin (0), mlpack-doc (1), python3-mlpack (0) * dh_installman: libmlpack-dev (0), libmlpack3 (0), mlpack-bin (47), mlpack-doc (0), python3-mlpack (0) If the missing files are installed by another tool, please file a bug against it. When filing the report, if the tool is not part of debhelper itself, please reference the "Logging helpers and dh_missing" section from the "PROGRAMMING" guide for debhelper (10.6.3+). (in the debhelper package: /usr/share/doc/debhelper/PROGRAMMING.gz) Be sure to test with dpkg-buildpackage -A/-B as the results may vary when only a subset is built For a short-term work-around: Add the files to debian/not-installed make: *** [debian/rules:46: binary-arch] Error 25 --- End Message --- --- Begin Message --- Source: mlpack Source-Version: 3.3.2-2 Done: b...@debian.org (Barak A. Pearlmutter) We believe that the bug you reported is fixed in the latest version of mlpack, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 964...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Barak A. Pearlmutter (supplier of updated mlpack package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 04 Aug 2020 13:39:14 +0100 Source: mlpack Architecture: source Version: 3.3.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Barak A. Pearlmutter Closes: 962533 964294 Changes: mlpack (3.3.2-2) unstable; urgency=medium . * include cmake support files in development package (closes: #964294) * update configuration options, including enabling building of tests * enable Julia bindings * avoid compile-time resource exhaustion by using CLANG instead of GCC (closes: #962533) * quilt patch for build-killing LaTeX markup typo * install stray html support file * Now formula.repository is gone, huh Checksums-Sha1: e1dbc0047e53d84b9369cb4d153e0452cbb3f1dd 2597 mlpack_3.3.2-2.dsc 212c7311e3242b8c68552c499cebc0a64f062851 10440 mlpack_3.3.2-2.debian.tar.xz a56f9a32de5aa2c12663e8c1a0e41f2691deff1d 11698 mlpack_3.3.2-2_source.buildinfo Checksums-Sha256: 4aa0fea272570ff7130cf457eb565b9f280a823d59169e8b49494076c8512d3d 2597 mlpack_3.3.2-2.dsc d515a00a7280b351e1053a2e6219c011f6762987a16a1e181d36296bf4aaa912 10440 mlpack_3.3.2-2.debian.tar.xz f4087d3635ece131938932f03fc76a8c9f677f14e95d191182084f5f85a30a7b 11698 mlpack_3.3.2-2_source.buildinfo Files: fea31a0d8bbb5404a5a3cc4f4f9e9907 2597 libs optional mlpack_3.3.2-2.dsc d1d89b73ad12635404ab1
Bug#967146: marked as done (guile-gnome-platform: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 5 Aug 2020 12:40:52 +0200 with message-id <5a4c1c09-b5fb-0739-8d18-79da2f97f...@debian.org> and subject line Re: Bug#967146: guile-gnome-platform: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967146, regarding guile-gnome-platform: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967146: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:guile-gnome-platform Version: 2.16.5-2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- fixed libglade2 is now in the archive. On 8/4/20 12:03 PM, Tommi Höynälänmaa wrote: > Hi > > I checked file debian/control and the test directories. I could not > find any Python dependencies. Where are they? > > - Tommi Höynälänmaa > > ti, 2020-08-04 kello 09:28 +, Matthias Klose kirjoitti: >> Package: src:guile-gnome-platform >> Version: 2.16.5-2 >> Severity: serious >> Tags: sid bullseye >> User: debian-pyt...@lists.debian.org >> Usertags: py2unversioned >> >> Python2 becomes end-of-live upstream, and Debian aims to remove >> Python2 from the distribution, as discussed in >> https://lists.debian.org/debian-python/2019/07/msg00080.html >> >> We will keep some Python2 package as discussed in >> https://lists.debian.org/debian-python/2020/07/msg00039.html >> but removing the unversioned python packages python-minimal, python, >> python-dev, python-dbg, python-doc. >> >> Your package either build-depends, depends on one of those packages. >> Please either convert these packages to Python3, or if that is not >> possible, replaces the dependencies on the unversioned Python >> packages with one of the python2 dependencies (python2, python2-dev, >> python2-dbg, python2-doc). >> >> Please check for dependencies, build dependencies AND autopkg tests. >> >> If there are questions, please refer to the wiki page for the >> removal: >> https://wiki.debian.org/Python/2Removal, or ask for help on IRC >> #debian-python, or the debian-pyt...@lists.debian.org mailing list. > --- End Message ---
Bug#967134: marked as done (g3dviewer: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 5 Aug 2020 12:41:26 +0200 with message-id <8461c094-eeab-c344-16c9-383ac765b...@debian.org> and subject line Re: Bug#967134: g3dviewer: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967134, regarding g3dviewer: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967134: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:g3dviewer Version: 0.2.99.5~svn130-11 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- On 8/4/20 11:36 AM, Sven Eckelmann wrote: > tags 967134 + moreinfo > thanks > > On Tuesday, 4 August 2020 11:27:54 CEST Matthias Klose wrote: > [...] >> Your package either build-depends, depends on one of those packages. >> Please either convert these packages to Python3, or if that is not >> possible, replaces the dependencies on the unversioned Python >> packages with one of the python2 dependencies (python2, python2-dev, >> python2-dbg, python2-doc). > > Hm? Where does it directly depend on python? I would like to fix it > but I don't see what. a fixed libglade2-dev is now in the archive.--- End Message ---
Bug#967171: marked as done (mdk: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 5 Aug 2020 12:39:27 +0200 with message-id and subject line Re: Bug#967171: mdk: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967171, regarding mdk: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:mdk Version: 1.2.10+dfsg-3 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- closing, fixed libglade2 is now in the archive. On 8/4/20 1:13 PM, Peter Pentchev wrote: > block 967171 by 967157 > thanks > > On Tue, Aug 04, 2020 at 09:28:34AM +, Matthias Klose wrote: >> Package: src:mdk >> Version: 1.2.10+dfsg-3 >> Severity: serious >> Tags: sid bullseye >> User: debian-pyt...@lists.debian.org >> Usertags: py2unversioned >> >> Python2 becomes end-of-live upstream, and Debian aims to remove >> Python2 from the distribution, as discussed in >> https://lists.debian.org/debian-python/2019/07/msg00080.html > > Hi, > > Thanks for filing this one! I believe that it will be automagically > fixed along with #967157, which you already took care of earlier today > :) > > Keeping this one open for now, of course... > > G'luck, > Peter > --- End Message ---
Bug#967117: marked as done (aeskulap: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 5 Aug 2020 12:38:44 +0200 with message-id and subject line Re: Bug#967117: aeskulap: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967117, regarding aeskulap: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:aeskulap Version: 0.2.2-beta2+git20190406.ef77f01-2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- closing, libglade2-dev (depending on python) was uninstallable. On 8/5/20 12:37 PM, Andreas Tille wrote: > Control: tags -1 moreinfo > > On Tue, Aug 04, 2020 at 09:27:37AM +, Matthias Klose wrote: >> Package: src:aeskulap >> Version: 0.2.2-beta2+git20190406.ef77f01-2 >> Severity: serious >> Tags: sid bullseye >> User: debian-pyt...@lists.debian.org >> Usertags: py2unversioned > > I grepped the packaging git for the string python which has no hits > except in some irrelevant documentation file and checked the > dependencies of aeskulap but I can not find any reference to python. > > Could you please explain this bug? > > Kind regards and thanks for all your work in the Python migration > > Andreas. > --- End Message ---
Processed: Re: Bug#967117: aeskulap: Unversioned Python removal in sid/bullseye
Processing control commands: > tags -1 moreinfo Bug #967117 [src:aeskulap] aeskulap: Unversioned Python removal in sid/bullseye Added tag(s) moreinfo. -- 967117: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967117 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#967117: aeskulap: Unversioned Python removal in sid/bullseye
Control: tags -1 moreinfo On Tue, Aug 04, 2020 at 09:27:37AM +, Matthias Klose wrote: > Package: src:aeskulap > Version: 0.2.2-beta2+git20190406.ef77f01-2 > Severity: serious > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2unversioned I grepped the packaging git for the string python which has no hits except in some irrelevant documentation file and checked the dependencies of aeskulap but I can not find any reference to python. Could you please explain this bug? Kind regards and thanks for all your work in the Python migration Andreas. -- http://fam-tille.de
Bug#967209: marked as done (rgtk2: Unversioned Python removal in sid/bullseye)
Your message dated Wed, 5 Aug 2020 12:36:41 +0200 with message-id and subject line Re: Bug#967209: rgtk2: Unversioned Python removal in sid/bullseye has caused the Debian Bug report #967209, regarding rgtk2: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 967209: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:rgtk2 Version: 2.20.36-2 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will keep some Python2 package as discussed in https://lists.debian.org/debian-python/2020/07/msg00039.html but removing the unversioned python packages python-minimal, python, python-dev, python-dbg, python-doc. Your package either build-depends, depends on one of those packages. Please either convert these packages to Python3, or if that is not possible, replaces the dependencies on the unversioned Python packages with one of the python2 dependencies (python2, python2-dev, python2-dbg, python2-doc). Please check for dependencies, build dependencies AND autopkg tests. If there are questions, please refer to the wiki page for the removal: https://wiki.debian.org/Python/2Removal, or ask for help on IRC #debian-python, or the debian-pyt...@lists.debian.org mailing list. --- End Message --- --- Begin Message --- fixed libglade2 is now in the archive. On 8/4/20 3:16 PM, Dirk Eddelbuettel wrote: > > On 4 August 2020 at 15:06, Matthias Klose wrote: > | block 967209 by 967157 > | thanks > | > | sorry, that's due to uninstallability of libglade2-dev. > > Thanks, that makes sense. > > (And thanks also to Julien, that was a good idea too but it does come up > negative: > > edd@rob:~/deb/rgtk2(master)$ grep -ri Python > inst/doc/tutorial.sgml:bindings for many other languages including C, C++, > Guile, Perl, Python, > edd@rob:~/deb/rgtk2(master)$ > > Dirk > > | On 8/4/20 2:49 PM, Dirk Eddelbuettel wrote: > | > > | > Hi doko and Python folks, > | > > | > On 4 August 2020 at 09:29, Matthias Klose wrote: > | > | Package: src:rgtk2 > | > | Version: 2.20.36-2 > | > | Severity: serious > | > | Tags: sid bullseye > | > | User: debian-pyt...@lists.debian.org > | > | Usertags: py2unversioned > | > | > | > | Python2 becomes end-of-live upstream, and Debian aims to remove > | > | Python2 from the distribution, as discussed in > | > | https://lists.debian.org/debian-python/2019/07/msg00080.html > | > | > | > | We will keep some Python2 package as discussed in > | > | https://lists.debian.org/debian-python/2020/07/msg00039.html > | > | but removing the unversioned python packages python-minimal, python, > | > | python-dev, python-dbg, python-doc. > | > | > | > | Your package either build-depends, depends on one of those packages. > | > | Please either convert these packages to Python3, or if that is not > | > | possible, replaces the dependencies on the unversioned Python > | > | packages with one of the python2 dependencies (python2, python2-dev, > | > | python2-dbg, python2-doc). > | > | > | > | Please check for dependencies, build dependencies AND autopkg tests. > | > > | > I am lost. > | > > | > Build-Depends: > | > Source: rgtk2 > | > Section: gnu-r > | > Priority: optional > | > Maintainer: Dirk Eddelbuettel > | > Build-Depends: debhelper (>= 10), dh-r (>= 20180615), r-base-dev (>= > 3.6.1), libgtk2.0-dev (>= 2.10.12), libglade2-dev, libpango1.0-dev, > libcairo2-dev > | > Standards-Version: 4.4.0 > | > Vcs-Browser: https://salsa.debian.org/edd/r-cran-rgtk2 > | > Vcs-Git: https://salsa.debian.org/edd/r-cran-rgtk2.git > | > Homepage: https://cran.r-project.org/package=RGtk2 > | > > | > Build-Depends: debhelper (>= 10), dh-r (>= 20180615), r-base-dev (>= > 3.6.1), libgtk2.0-dev (>= 2.10.12), libglade2-dev, libpango1.0-dev, > libcairo2-dev > | > > | > Depends: > | > Package: r-cran-rgtk2 > | > Source: rgtk2 (2.20.36-2) > | > Version: 2.20.36-2+b1 > | > Installed-Size: 18722 > | > Maintainer: Dirk Eddelbuettel > | > Architecture: amd64 > | > Depends: r-base-core (>= 4.0.0-3), r-api-4.0, libatk1.0-0 (>= 1.12.4), > libc6 (>= 2.14), libcairo2 (>= 1.8.0), libgdk-pixbuf2.0-0 (>= 2.22.0), > libglib2.0-0 (>= 2.41.1), libgtk2.0-0 (>= 2.20.0), libpango-1.0-0 (>= > 1.25.5), libpangocairo-1.0-0 (>= 1.22.0) > | > Description-en: GNU R
Bug#966920: spoa: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below
Control: tags -1 pending Package that is fixing this issue was uploaded to new https://ftp-master.debian.org/new/spoa_3.4.0-1.html Kind regards, Andreas.
Processed: Re: Bug#966920: spoa: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below
Processing control commands: > tags -1 pending Bug #966920 [src:spoa] spoa: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below Ignoring request to alter tags of bug #966920 to the same tags previously set -- 966920: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966920 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems