Bug#999342: shadow FTBFS: bd-uninstallable due to conflict on libsepol1-dev
Source: shadow Version: 1:4.8.1-1.1 Severity: serious Tags: ftbfs patch User: helm...@debian.org Usertags: rebootstrap shadow fails to build from source in unstable, because the selinux people started a transition, bumped soname and in that process moved to unversioned -dev packages. The final result is that for now shadow exhibits a conflict on libsepol1-dev, but before too long it will miss a versioned -dev package. Switching to unversioned ones fixes the issue in practice and completes the transition for shadow. Helmut diff --minimal -Nru shadow-4.8.1/debian/changelog shadow-4.8.1/debian/changelog --- shadow-4.8.1/debian/changelog 2021-10-23 21:04:57.0 +0200 +++ shadow-4.8.1/debian/changelog 2021-11-10 07:51:53.0 +0100 @@ -1,3 +1,11 @@ +shadow (1:4.8.1-1.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS: Use unversioned selinux and semanage dependencies. +(Closes: #-1) + + -- Helmut Grohne Wed, 10 Nov 2021 07:51:53 +0100 + shadow (1:4.8.1-1.1) unstable; urgency=medium [ Johannes Schauer Marin Rodrigues ] diff --minimal -Nru shadow-4.8.1/debian/control shadow-4.8.1/debian/control --- shadow-4.8.1/debian/control 2021-10-23 20:29:33.0 +0200 +++ shadow-4.8.1/debian/control 2021-11-10 07:51:49.0 +0100 @@ -12,8 +12,8 @@ docbook-xsl, docbook-xml, libxml2-utils, - libselinux1-dev [linux-any], - libsemanage1-dev [linux-any], + libselinux-dev [linux-any], + libsemanage-dev [linux-any], itstool, bison, libaudit-dev [linux-any]
Bug#998582: marked as done (ocaml-ffmpeg: FTBFS: build-dependency not installable:)
Your message dated Wed, 10 Nov 2021 08:15:40 +0100 with message-id and subject line Re: ocaml-ffmpeg: FTBFS: build-dependency not installable has caused the Debian Bug report #998582, regarding ocaml-ffmpeg: FTBFS: build-dependency not installable: 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.) -- 998582: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998582 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: liquidsoap Version: 1.4.4-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: chrpath, debhelper (>= 11), debhelper-compat (= 13), > dh-elpa, dh-ocaml (>= 1.0.1), festival, fonts-liberation, pandoc, > libalsa-ocaml-dev (>= 0.2.1), libao-ocaml-dev (>= 0.2.0), libbjack-ocaml-dev > (>= 0.1.3), libcamlimages-ocaml-dev (>= 4.0.1-6), libcamomile-ocaml-dev (>= > 1.0.0), libcry-ocaml-dev (>= 0.6.0), libdtools-ocaml-dev (>= 0.4.1), > libduppy-ocaml-dev (>= 0.8.0), libfaad-ocaml-dev (>= 0.4.0), > libffmpeg-ocaml-dev (>= 0.2.), libflac-ocaml-dev (>= 0.1.5), > libfrei0r-ocaml-dev (>= 0.1.0), libgavl-ocaml-dev (>= 0.1.4), libgd-ocaml-dev > | libgd-gd2-noxpm-ocaml-dev, libssl-ocaml-dev (>= 0.5.2), > libgstreamer-ocaml-dev (>= 0.3.0), libinotify-ocaml-dev (>= 1.0), > libladspa-ocaml-dev (>= 0.1.4), liblastfm-ocaml-dev (>= 0.3.0), > liblo-ocaml-dev (>= 0.1.2), libmad-ocaml-dev (>= 0.1.4), libmagic-ocaml-dev > (>= 0.6), libmenhir-ocaml-dev, libmm-ocaml-dev (>= 0.5.0), > libmp3lame-ocaml-dev (>= 0.3.2), libogg-ocaml-dev (>= 0.5.0), > libopus-ocaml-dev (>= 0.1.3), libpcre-ocaml-dev, libportaudio-ocaml-dev (>= > 0.2.0), libpulse-ocaml-dev (>= 0.1.2), libsamplerate-ocaml-dev (>= 0.1.1), > libsdl-ocaml-dev, libsedlex-ocaml-dev (>= 2.0), libshine-ocaml-dev (>= > 0.2.0), libsoundtouch-ocaml-dev (>= 0.1.7), libspeex-ocaml-dev (>= 0.2.1), > libtaglib-ocaml-dev (>= 0.3.0), libtheora-ocaml-dev (>= 0.3.1), > libvoaacenc-ocaml-dev, libvorbis-ocaml-dev (>= 0.7.0), libxml-dom-perl, > libxmlplaylist-ocaml-dev (>= 0.1.3), libyojson-ocaml-dev, menhir, > ocaml-findlib, ocaml-nox (>= 4.08), sox, build-essential, fakeroot > Filtered Build-Depends: chrpath, debhelper (>= 11), debhelper-compat (= 13), > dh-elpa, dh-ocaml (>= 1.0.1), festival, fonts-liberation, pandoc, > libalsa-ocaml-dev (>= 0.2.1), libao-ocaml-dev (>= 0.2.0), libbjack-ocaml-dev > (>= 0.1.3), libcamlimages-ocaml-dev (>= 4.0.1-6), libcamomile-ocaml-dev (>= > 1.0.0), libcry-ocaml-dev (>= 0.6.0), libdtools-ocaml-dev (>= 0.4.1), > libduppy-ocaml-dev (>= 0.8.0), libfaad-ocaml-dev (>= 0.4.0), > libffmpeg-ocaml-dev (>= 0.2.), libflac-ocaml-dev (>= 0.1.5), > libfrei0r-ocaml-dev (>= 0.1.0), libgavl-ocaml-dev (>= 0.1.4), > libgd-ocaml-dev, libssl-ocaml-dev (>= 0.5.2), libgstreamer-ocaml-dev (>= > 0.3.0), libinotify-ocaml-dev (>= 1.0), libladspa-ocaml-dev (>= 0.1.4), > liblastfm-ocaml-dev (>= 0.3.0), liblo-ocaml-dev (>= 0.1.2), libmad-ocaml-dev > (>= 0.1.4), libmagic-ocaml-dev (>= 0.6), libmenhir-ocaml-dev, libmm-ocaml-dev > (>= 0.5.0), libmp3lame-ocaml-dev (>= 0.3.2), libogg-ocaml-dev (>= 0.5.0), > libopus-ocaml-dev (>= 0.1.3), libpcre-ocaml-dev, libportaudio-ocaml-dev (>= > 0.2.0), libpulse-ocaml-dev (>= 0.1.2), libsamplerate-ocaml-dev (>= 0.1.1), > libsdl-ocaml-dev, libsedlex-ocaml-dev (>= 2.0), libshine-ocaml-dev (>= > 0.2.0), libsoundtouch-ocaml-dev (>= 0.1.7), libspeex-ocaml-dev (>= 0.2.1), > libtaglib-ocaml-dev (>= 0.3.0), libtheora-ocaml-dev (>= 0.3.1), > libvoaacenc-ocaml-dev, libvorbis-ocaml-dev (>= 0.7.0), libxml-dom-perl, > libxmlplaylist-ocaml-dev (>= 0.1.3), libyojson-ocaml-dev, menhir, > ocaml-findlib, ocaml-nox (>= 4.08), sox, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [963 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [805 B] > Get:5 copy:/<>/apt_archive ./ Packages [865 B] > Fetched 2633 B in 0s (258 kB/s) > Reading package lists... > Reading package lists... > >
Bug#998533: marked as done (nurpawiki: FTBFS: build-dependency not installable: libocamlnet-ocaml-dev-2d6s9)
Your message dated Wed, 10 Nov 2021 08:06:17 +0100 with message-id and subject line Re: Bug#998533: nurpawiki: FTBFS: build-dependency not installable: libocamlnet-ocaml-dev-2d6s9 has caused the Debian Bug report #998533, regarding nurpawiki: FTBFS: build-dependency not installable: libocamlnet-ocaml-dev-2d6s9 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.) -- 998533: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: nurpawiki Version: 1.2.4-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211104 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > +--+ > | Install package build dependencies > | > +--+ > > > Setup apt archive > - > > Merged Build-Depends: debhelper-compat (= 13), dh-ocaml, ocamlbuild, > libeliom-ocaml-dev (>= 6.12.1), libcalendar-ocaml-dev, libextlib-ocaml-dev, > libpostgresql-ocaml-dev, ocaml-nox, build-essential, fakeroot > Filtered Build-Depends: debhelper-compat (= 13), dh-ocaml, ocamlbuild, > libeliom-ocaml-dev (>= 6.12.1), libcalendar-ocaml-dev, libextlib-ocaml-dev, > libpostgresql-ocaml-dev, ocaml-nox, build-essential, fakeroot > dpkg-deb: building package 'sbuild-build-depends-main-dummy' in > '/<>/apt_archive/sbuild-build-depends-main-dummy.deb'. > Ign:1 copy:/<>/apt_archive ./ InRelease > Get:2 copy:/<>/apt_archive ./ Release [957 B] > Ign:3 copy:/<>/apt_archive ./ Release.gpg > Get:4 copy:/<>/apt_archive ./ Sources [430 B] > Get:5 copy:/<>/apt_archive ./ Packages [516 B] > Fetched 1903 B in 0s (187 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > Reading state information... > Some packages could not be installed. This may mean that you have > requested an impossible situation or if you are using the unstable > distribution that some required packages have not yet been created > or been moved out of Incoming. > The following information may help to resolve the situation: > > The following packages have unmet dependencies: > libeliom-ocaml-dev : Depends: libocamlnet-ocaml-dev-2d6s9 but it is not > installable > E: Unable to correct problems, you have held broken packages. > apt-get failed. The full build log is available from: http://qa-logs.debian.net/2021/11/04/nurpawiki_1.2.4-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- On Thu, Nov 04, 2021 at 08:26:53PM +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. Resolved by the rebuild of eliom.--- End Message ---
Processed: reassign 998911 to node-string-width,node-slice-ansi, forcibly merging 998886 998911
Processing commands for cont...@bugs.debian.org:
> reassign 998911 node-string-width,node-slice-ansi
Bug #998911 [node-string-width] node-string-width: file conflict with
node-slice-ansi
Bug reassigned from package 'node-string-width' to
'node-string-width,node-slice-ansi'.
No longer marked as found in versions node-string-width/4.2.3+~3.0.0+~9.2.2-1.
Ignoring request to alter fixed versions of bug #998911 to the same values
previously set
> forcemerge 998886 998911
Bug #998886 {Done: Yadd } [node-string-width,node-slice-ansi]
node-string-width,node-slice-ansi: both ship
/usr/share/nodejs/is-fullwidth-code-point/*
Bug #998911 [node-string-width,node-slice-ansi] node-string-width: file
conflict with node-slice-ansi
Marked Bug as done
Marked as fixed in versions node-string-width/4.2.3+~9.2.2-1.
Marked as found in versions node-string-width/4.2.3+~3.0.0+~9.2.2-1 and
node-slice-ansi/5.0.0+~4.0.0-2.
Merged 998886 998911
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
998886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998886
998911: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998911
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 998565 is forwarded to https://github.com/flyingcircusio/pycountry/issues/85
Processing commands for cont...@bugs.debian.org:
> forwarded 998565 https://github.com/flyingcircusio/pycountry/issues/85
Bug #998565 [src:pycountry] pycountry: FTBFS: dh_auto_test: error: pybuild
--test -i python{version} -p 3.9 returned exit code 13
Set Bug forwarded-to-address to
'https://github.com/flyingcircusio/pycountry/issues/85'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
998565: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998565
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#994055:
Hi, thanks for this fix. I think it meets the threshold for NMU (and also the maintainer seems to have been awol since 2015) so I'm uploading it to DELAYED/10.
Bug#996632: marked as done (llvm-toolchain-13: autopkgtest failure on i386)
Your message dated Wed, 10 Nov 2021 02:47:27 + with message-id and subject line re: llvm-toolchain-13: autopkgtest failure on i386 has caused the Debian Bug report #996632, regarding llvm-toolchain-13: autopkgtest failure on i386 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.) -- 996632: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996632 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: llvm-toolchain-13 Version: 1:13.0.0-3 Severity: serious X-Debbugs-Cc: sramac...@debian.org While the changelog of 1:13.0.0-3 says those three tests should be disabled, they are still failing on i386: | FAIL: LLVM regression suite :: basic_lldb.c (5 of 40) | TEST 'LLVM regression suite :: basic_lldb.c' FAILED | Script: | -- | : 'RUN: at line 1'; /usr/bin/clang-13 -g -o /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/build/tests/Output/basic_lldb.c.tmp /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/tests/basic_lldb.c | : 'RUN: at line 2'; /usr/bin/lldb-13 -s /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/tests/basic_lldb.in /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/build/tests/Output/basic_lldb.c.tmp | grep "main at basic_lldb.c:" | -- | Exit Code: 1 | | Command Output (stderr): | -- | error: Lost debug server connection | | -- | | | FAIL: LLVM regression suite :: basic_lldb2.cpp (6 of 40) | TEST 'LLVM regression suite :: basic_lldb2.cpp' FAILED | Script: | -- | : 'RUN: at line 1'; /usr/bin/clang++-13 -g -o /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/build/tests/Output/basic_lldb2.cpp.tmp /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/tests/basic_lldb2.cpp | : 'RUN: at line 2'; /usr/bin/lldb-13 -s /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/tests/basic_lldb2.in /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/build/tests/Output/basic_lldb2.cpp.tmp | grep "stop reason = step over" | -- | Exit Code: 1 | | Command Output (stderr): | -- | error: Lost debug server connection | | -- | | | PASS: LLVM regression suite :: basic_openmp.c (7 of 40) ... | PASS: LLVM regression suite :: test_leaksan.c (34 of 40) | FAIL: LLVM regression suite :: test_tsan.c (35 of 40) | TEST 'LLVM regression suite :: test_tsan.c' FAILED | Script: | -- | : 'RUN: at line 4'; /usr/bin/clang-13 -o /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/build/tests/Output/test_tsan.c.tmp -fsanitize=thread -g -O1 /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/tests/test_tsan.c | : 'RUN: at line 5'; /usr/bin/llvm-nm-13 /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/build/tests/Output/test_tsan.c.tmp | grep __tsan | : 'RUN: at line 6'; env TSAN_OPTIONS="log_path=stdout:exitcode=0" /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/build/tests/Output/test_tsan.c.tmp 2>&1 > /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/build/tests/Output/test_tsan.c.tmp.out | : 'RUN: at line 7'; grep -q "data race" /tmp/autopkgtest-lxc.4iluiq00/downtmp/autopkgtest_tmp/build/tests/Output/test_tsan.c.tmp.out | -- | Exit Code: 1 | | Command Output (stderr): | -- | clang: error: unsupported option '-fsanitize=thread' for target 'i686-pc-linux-gnu' | | -- | | | PASS: LLVM regression suite :: thinlto.c (36 of 40) | PASS: LLVM regression suite :: warning_conversion.c (37 of 40) | UNSUPPORTED: LLVM regression suite :: whole-toolchain.c (38 of 40) | UNSUPPORTED: LLVM regression suite :: whole-toolchain.cpp (39 of 40) | PASS: LLVM regression suite :: scanbuild_missing_delete.cpp (40 of 40) | | Unsupported Tests (8): | LLVM regression suite :: buildid.c | LLVM regression suite :: format_diff.c | LLVM regression suite :: llvm-ir.c | LLVM regression suite :: scanbuild_py_makefile.txt | LLVM regression suite :: test_asan_heap.c | LLVM regression suite :: test_clangd.txt | LLVM regression suite :: whole-toolchain.c | LLVM regression suite :: whole-toolchain.cpp | | | Failed Tests (3): | LLVM regression suite :: basic_lldb.c | LLVM regression suite :: basic_lldb2.cpp | LLVM regression suite :: test_tsan.c | | | Testing Time: 20.59s | Unsupported: 8 | Passed : 29 | Failed : 3 | make[3]: *** [CMakeFiles/check.dir/build.make:70: CMakeFiles/check] Error 1 | make[2]: *** [CMakeFiles/Makefile2:83: CMakeFiles/check.dir/all] Error 2 | make[1]: *** [CMakeFiles/Makefile2:90:
Bug#997225: Vendoring image-spec and runtime-spec seem to be the issue
Cloud you backport following commit? https://github.com/containers/libocispec/commit/8489d9b60105e487564c9966b5748e2a6ea2855b (Sent on my mobile phone) Reinhard Tartler 于 2021年11月10日周三 07:05写道： > I took a look at the issue and here are my thoughts: > > - the build error is a failure to link some test binaries. excluding them > from the build might be possible with some patching. > - I've upgraded the package to the latest upstream 1.3, and was seeing > exactly the same build failure > - the build failure goes away when not stripping the bundled copies of > runtime-spec and image-spec > - Dimtry had a conversation about this with upstream at > https://github.com/containers/crun/issues/240. It seems to be that > upstream strongly recommends to just use the vendored copies of image-spc > and runtime-spec > - I've pushed my work to > https://salsa.debian.org/debian/crun/-/merge_requests/1 > - I believe the issue was introduced by Shengjing's update in > https://tracker.debian.org/news/1249177/accepted-golang-github-opencontainers-specs-10266g20a2d97-1-source-into-unstable/ > -- but that was already months ago. So that may not be true > > With this, I'd like to suggest to move ahead with my merge request and > don't strip image-spec and runtime-spec from the package. > > Any thoughts? > > -- > regards, > Reinhard >
Bug#990340: marked as done (glances: contains prebuilt javascript without source)
Your message dated Wed, 10 Nov 2021 01:19:10 + with message-id and subject line Bug#990340: fixed in glances 3.2.3.1+dfsg-1 has caused the Debian Bug report #990340, regarding glances: contains prebuilt javascript without source 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.) -- 990340: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990340 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: glances Version: 3.1.5-1 Severity: serious Justification: Policy 2.2.1 Hi, the source package contains: glances/outputs/static/public/glances.js glances/outputs/static/public/glances.map.js these files are copied into the binary package as: /usr/lib/python3/dist-packages/glances/outputs/static/public/glances.js /usr/lib/python3/dist-packages/glances/outputs/static/public/glances.map.js they trigger the following lintian errors: E source-is-missing glances/outputs/static/public/glances.js line 52292 is 44264 characters long (>512) E source-is-missing glances/outputs/static/public/glances.map.js line 2 is 2631202 characters long (>512) Don't distribute those files or build them from source. Thanks! cheers, josch --- End Message --- --- Begin Message --- Source: glances Source-Version: 3.2.3.1+dfsg-1 Done: Daniel Echeverri We believe that the bug you reported is fixed in the latest version of glances, 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 990...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Echeverri (supplier of updated glances package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 07 Nov 2021 19:35:20 -0500 Source: glances Architecture: source Version: 3.2.3.1+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Daniel Echeverri Changed-By: Daniel Echeverri Closes: 850258 990340 Changes: glances (3.2.3.1+dfsg-1) unstable; urgency=medium . [Alexis Murzeau] * Remove Exclude prebuilt javascript files. (Closes: #990340) + Please see this MR for the full changes. + https://salsa.debian.org/debian/glances/-/merge_requests/2 + Thanks to Alexis for the work! . [Daniel Echeverri] * New upstream release. * debian/control + Add python3-defusedxml and python3-sphinx-rtd-theme in B-D. + Bump to Standards-Version 4.6.0.1 (no changes needed). * debian/patches + Add 007_disable_ip_module_by_default.diff patch. + Disable ip module by default. (Closes: #850258) + Remove 001_reproducible-build.patch. + Merge with upstream + Remove 005_fix-typo.patch. + Merge with upstream + Refresh 004_disable-pypi.patch. * Add entry in README.debian file. * Remove lintian overrides. Checksums-Sha1: ca28256045f3cf75ada1b1420682aa5fb0ce07e7 2173 glances_3.2.3.1+dfsg-1.dsc 873a4adca3ee445601de9b6281782f3a07525666 5816374 glances_3.2.3.1+dfsg.orig.tar.gz fef20f9eaae0eccb54483f5f7ff5cd14cb4c0915 12052 glances_3.2.3.1+dfsg-1.debian.tar.xz e02216ac1b979a49cdad32098f3838b42c9ca792 7852 glances_3.2.3.1+dfsg-1_amd64.buildinfo Checksums-Sha256: c94d9a659c76176b3ab28c83e4c96afce0e6ac7d1745e7530c24be8b66a9788a 2173 glances_3.2.3.1+dfsg-1.dsc 2291ddc75e9c50fdc4f119be12101cbf5071a118f6c4c3dd42120c71fd68d6a7 5816374 glances_3.2.3.1+dfsg.orig.tar.gz 44d835716a732dda65da08fc54e0812a3a97b0f3d3e4f94a08fce48758a3fac7 12052 glances_3.2.3.1+dfsg-1.debian.tar.xz 95ff53bac2a199d14a83ebb801c2c5fa11599de1d4c43758665ce1353609f972 7852 glances_3.2.3.1+dfsg-1_amd64.buildinfo Files: be1250a4b1cd02a8713b961589d753ea 2173 utils optional glances_3.2.3.1+dfsg-1.dsc 7222e07b8a816c99978642bded2265da 5816374 utils optional glances_3.2.3.1+dfsg.orig.tar.gz 3f8b958bd45ed09ca4eb67ed264a2530 12052 utils optional glances_3.2.3.1+dfsg-1.debian.tar.xz ae3b26fab34c601cb236acb9de1aa538 7852 utils optional glances_3.2.3.1+dfsg-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE0NCFsWnDv9lASFj6IfwpUEtSMNsFAmGLF5QTHGVwc2lsb25A ZGViaWFuLm9yZwAKCRAh/ClQS1Iw2yhYEACTwkBvBCuv4xpuAk6Girnk2qmNPZcm sC9tH1dgNchjkEWfdebFc3B5GI6P7O4RSJggkKn48xhNuQY6yAGg2VMMr+9GxrXe
Bug#998108: Acknowledgement (firefox freezes shortly after start)
Not sure if this is related, but since a while I've noted even bigger than the usual performance problems of firefox... Crackling sound is something I've heard for a month now... but since about FF93 came out CPU utilisation seems to be much higher. I just load simple webpages and may CPU goes up to 70-80°C. Anyone else seen this, too?
Bug#998838: marked as done (h5py: FTBFS on armhf)
Your message dated Tue, 09 Nov 2021 23:18:36 + with message-id and subject line Bug#998838: fixed in h5py 3.3.0-5 has caused the Debian Bug report #998838, regarding h5py: FTBFS on armhf 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.) -- 998838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: h5py Version: 3.3.0-4 Severity: serious Tags: ftbfs Hi Maintainer As can be seen on reproducible builds [1], h5py FTBFS on armhf with the following error: build/h5py/_debian_h5py_serial/tests/test_dtype.py::TestVlen::test_compound_vlen_bool Fatal Python error: Bus error The cause is most likely an alignment error, which is exposed when running armhf on an arm64 kernel. There are often failures on the official buildds as well [2], depending on which host the build lands. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-pkg/h5py.html [2] https://buildd.debian.org/status/logs.php?pkg=h5py=armhf --- End Message --- --- Begin Message --- Source: h5py Source-Version: 3.3.0-5 Done: Drew Parsons We believe that the bug you reported is fixed in the latest version of h5py, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Drew Parsons (supplier of updated h5py 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: Tue, 09 Nov 2021 23:52:01 +0100 Source: h5py Architecture: source Version: 3.3.0-5 Distribution: unstable Urgency: medium Maintainer: Debian Science Maintainers Changed-By: Drew Parsons Closes: 998838 Changes: h5py (3.3.0-5) unstable; urgency=medium . * Team upload. * debian patch fix-unaligned-access.patch avoids an unaligned memory access causing build failure on armhf. Thanks Michael Hudson-Doyle. Closes: #998838. Checksums-Sha1: 4da2ebcfe900dbd68031a08a3a4ea86a9ae8b36d 2729 h5py_3.3.0-5.dsc d25c2328622f321e6e59d99fdbb19b3d7782020c 18660 h5py_3.3.0-5.debian.tar.xz Checksums-Sha256: d5579fc7c2e22ed014f064a9bed4700d42b4e656f6559e3874b50400a8e02049 2729 h5py_3.3.0-5.dsc 4978bc26ff18b4ef98c2f7b4363435dbebacb2a0ca676b3a3e1cae0e18e0df1a 18660 h5py_3.3.0-5.debian.tar.xz Files: f3957316562af91c792cff6d88b7f106 2729 python optional h5py_3.3.0-5.dsc d2b525f32f92afe38c3c739fe98a8f3b 18660 python optional h5py_3.3.0-5.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEI8mpPlhYGekSbQo2Vz7x5L1aAfoFAmGK/bcACgkQVz7x5L1a Afp0/A//dhlX6ypuNNrvvhOvXxCYeZc7O8fPdGTeuYTlyRiRjw9YFrl+IIyK6lt8 jSJnkESRXlyzC1j602biPXsyO35fj14Jr8aPRHGsAnVm9ZpJ3Sg8nE01j7gdZyEi PsAuc45ja5GteuSzJYEcjDq/+vRzimGpLhVVjkGd01l1R8noYb91n05bb/azUlSs 9XHxegusI4VnvJX4UeOCy+13CteOkOfZNckLObz8WJqrCLVOIV2PrpnI2lJJuBj5 adi1ZwMESZPImGz8hmcemxDdEm2qh0VfgXf3Zzi+GtorV9TQTTTb9RIq7XjsYNtM JvxtlTXCCw6TsoxHuvlknzVblwSExDjMMi09aO9Cf5iTYQ6DKSIy2H1SsTAQLMGr G/htTTojVeO+4QYyyR2C45AoG2srhx0tvi3/L2qP3Dr6Wg5lehbymcsvRmDJHCnX HVbbW05/D+TBI50fePblTjUuT1Zjrspp9pfnGCYBj8xnHPFOIBGQUZR6f75ThDdw k0Joex9lDqxgfbyzTGAvi7F59zYjKp125qE+avitXlfX66djjig6YoQ8m8bufZSG odaQ1Z4MYuQtndQpeCRrMhx1f6y1hag6DY9O1o9MyeA/ad4NXKj8rlqs5LOdAu4L gsXmNBvRZcA4g9WB20u5qJUzjDQr5BYY9LvyGyUFYAHWynzEClY= =W5Yd -END PGP SIGNATURE End Message ---
Bug#997225: Vendoring image-spec and runtime-spec seem to be the issue
I took a look at the issue and here are my thoughts: - the build error is a failure to link some test binaries. excluding them from the build might be possible with some patching. - I've upgraded the package to the latest upstream 1.3, and was seeing exactly the same build failure - the build failure goes away when not stripping the bundled copies of runtime-spec and image-spec - Dimtry had a conversation about this with upstream at https://github.com/containers/crun/issues/240. It seems to be that upstream strongly recommends to just use the vendored copies of image-spc and runtime-spec - I've pushed my work to https://salsa.debian.org/debian/crun/-/merge_requests/1 - I believe the issue was introduced by Shengjing's update in https://tracker.debian.org/news/1249177/accepted-golang-github-opencontainers-specs-10266g20a2d97-1-source-into-unstable/ -- but that was already months ago. So that may not be true With this, I'd like to suggest to move ahead with my merge request and don't strip image-spec and runtime-spec from the package. Any thoughts? -- regards, Reinhard
Processed: h5py
Processing commands for cont...@bugs.debian.org: > forwarded 998838 https://github.com/h5py/h5py/issues/1927 Bug #998838 [src:h5py] h5py: FTBFS on armhf Set Bug forwarded-to-address to 'https://github.com/h5py/h5py/issues/1927'. > thanks Stopping processing here. Please contact me if you need assistance. -- 998838: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998838 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#979102: Legally problematic GPL-3+ readline dependency
Hi Camm, On 09.11.21 23:12, Camm Maguire wrote: But in any case, I no longer understand the premise of this bug, unless it was your understanding that the source was gplv2*only* instead of "or any later version". Yes, this was the premise and that is what debian/copyright claims at the bottom. Grepping through the source I can quickly identify some GPL-2-only files: src/numth.lisp src/nset.lisp share/stringproc/printf.lisp share/stringproc/stringproc.lisp Thanks, Bastian
Bug#996310: marked as done (ruby-kyotocabinet: FTBFS with ruby3.0: stdalign.h:93:1: error: template with C linkage)
Your message dated Tue, 09 Nov 2021 22:19:52 +
with message-id
and subject line Bug#996310: fixed in ruby-kyotocabinet 1.34-0.1
has caused the Debian Bug report #996310,
regarding ruby-kyotocabinet: FTBFS with ruby3.0: stdalign.h:93:1: error:
template with C linkage
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.)
--
996310: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996310
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-kyotocabinet
Version: 1.33-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-kyotocabinet was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
> g++ -fdebug-prefix-map=/<>=. -I.
> -I/usr/include/x86_64-linux-gnu/ruby-3.0.0
> -I/usr/include/ruby-3.0.0/ruby/backward -I/usr/include/ruby-3.0.0 -I.
> -DHAVE_KCCOMMON_H -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -g -O2
> -ffile-prefix-map=/build/ruby3.0-2KsnwC/ruby3.0-3.0.2=.
> -fstack-protector-strong -Wformat -Werror=format-security -o kyotocabinet.o
> -c kyotocabinet.cc
> In file included from /usr/include/ruby-3.0.0/ruby/backward/2/stdalign.h:23,
> from /usr/include/ruby-3.0.0/ruby/defines.h:77,
> from /usr/include/ruby-3.0.0/ruby/ruby.h:23,
> from /usr/include/ruby-3.0.0/ruby.h:38,
> from kyotocabinet.cc:22:
> /usr/include/ruby-3.0.0/ruby/internal/stdalign.h:93:1: error: template with C
> linkage
>93 | template
> | ^~~~
> kyotocabinet.cc:20:1: note: ‘extern "C"’ linkage started here
>20 | extern "C" {
> | ^~
> make[1]: *** [Makefile:213: kyotocabinet.o] Error 1
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-kyotocabinet/ruby-kyotocabinet_1.33-1+rebuild1633384978_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-kyotocabinet
Source-Version: 1.34-0.1
Done: Boyuan Yang
We believe that the bug you reported is fixed in the latest version of
ruby-kyotocabinet, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Boyuan Yang (supplier of updated ruby-kyotocabinet 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, 09 Nov 2021 16:46:46 -0500
Source: ruby-kyotocabinet
Architecture: source
Version: 1.34-0.1
Distribution: unstable
Urgency: high
Maintainer: Debian Ruby Extras Maintainers
Changed-By: Boyuan Yang
Closes: 992315 996310
Changes:
ruby-kyotocabinet (1.34-0.1) unstable; urgency=high
.
* Non-maintainer upload.
* New upstream release. (Closes: #992315)
* debian/watch: Fix upstream monitoring.
* debian/patches: Drop obsolete patches (0004-0008).
* debian/docs: Drop doc installation, no longer provided upstream.
* debian/source/lintian-overrides: Dropped.
* debian/missing-sources: Dropped, not needed.
* debian/patches/0004-Fix-ruby3.0-FTBFS-extern-C.patch:
Add patch to fix compatibility with Ruby 3.0. (Closes: #996310)
* debian/copyright: Update homepage information.
Checksums-Sha1:
21dd3855d42d83da71045b6f1f6585e709634bce 2114 ruby-kyotocabinet_1.34-0.1.dsc
5ff197f094c79239391042934ac743799843f6be 43191
ruby-kyotocabinet_1.34.orig.tar.gz
163cc723b33a739c151bded51d30bc7e997102b8 4908
ruby-kyotocabinet_1.34-0.1.debian.tar.xz
9230b550b7d245a33f3a6a0512cf4fdf965eaa7b 9632
ruby-kyotocabinet_1.34-0.1_amd64.buildinfo
Checksums-Sha256:
4afc9602393f799346f9481b226de1ca9fe4a57ff2d1f6c7fd3b301b046eec51 2114
ruby-kyotocabinet_1.34-0.1.dsc
d8d6321540799143efb2f7fb0a8a1ea029996989db1bf008599fdbb3f4fc5f14 43191
ruby-kyotocabinet_1.34.orig.tar.gz
bf36bd2c1b124a012f5ccc5e410bad1e332fb699e7a404bf4b6e079bac33610d 4908
ruby-kyotocabinet_1.34-0.1.debian.tar.xz
Bug#979102: marked as done (Legally problematic GPL-3+ readline dependency)
Your message dated Tue, 09 Nov 2021 22:19:35 + with message-id and subject line Bug#979102: fixed in maxima 5.45.1-2 has caused the Debian Bug report #979102, regarding Legally problematic GPL-3+ readline 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.) -- 979102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979102 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: maxima Severity: important This package depends on libreadline8 which is GPL-3+ licensed. According to debian/copyright parts of your package are GPL-2-only licensed. If that is also (transitively) the case for the binaries that link with libreadline.so.8 it might be legally problematic (see https://www.gnu.org/licenses/gpl-faq.html#AllCompatibility). There is an easy solution to the problem: Replacing the build dependency libreadline-dev with libreadline-gplv2-dev links with the GPL-2+ licensed older version. However, that is orphaned in Debian, so libeditreadline-dev should be preferred, which does not compile with your package without any patch. It links with the BSD-licensed libedit library which is a readline replacement. --- End Message --- --- Begin Message --- Source: maxima Source-Version: 5.45.1-2 Done: Camm Maguire We believe that the bug you reported is fixed in the latest version of maxima, 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 979...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Camm Maguire (supplier of updated maxima 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: Tue, 09 Nov 2021 21:31:06 + Source: maxima Architecture: source Version: 5.45.1-2 Distribution: unstable Urgency: medium Maintainer: Camm Maguire Changed-By: Camm Maguire Closes: 979102 981979 Changes: maxima (5.45.1-2) unstable; urgency=medium . * latest standards * build-dep gcl >= 2.6.12-107 * Bug fix: "Legally problematic GPL-3+ readline dependency", thanks to Bastian Germann (Closes: #979102). * Bug fix: "imaxima bugs", thanks to Jesús Lago Macía (Closes: #981979). Checksums-Sha1: 1e8801126644de71023aac3cb8c0a47fe36dbe26 2167 maxima_5.45.1-2.dsc 049c1d402820174c38f69afd86f9833770d0d650 1760676 maxima_5.45.1-2.debian.tar.xz 60a107be2046145f0c02dd6c771f7287f80fdc48 9345 maxima_5.45.1-2_source.buildinfo Checksums-Sha256: 2eeccb0f0db6fe0f759d51e5a758adc74cf9d13e23241c976ca7ace6b2e37332 2167 maxima_5.45.1-2.dsc 6c0cea8b0bc706c50e8d73aa3873361f842c82ccda59ed138ddac5bbd6a275e8 1760676 maxima_5.45.1-2.debian.tar.xz 55640d2ac4a1a48d86dcb0c99fc0f45a6fc9f7d419d6bcc7bee90e21fa25c1cd 9345 maxima_5.45.1-2_source.buildinfo Files: dd6c42125dcdaea496ebce8273e4ecd1 2167 math optional maxima_5.45.1-2.dsc 46a79715949b921d9619bec1cbbb289a 1760676 math optional maxima_5.45.1-2.debian.tar.xz cfb3b9c102f8d8dbfb8284449289435f 9345 math optional maxima_5.45.1-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/iFPNjaXdzJC6BbsuEXOUQ+bcU0FAmGK7/QACgkQuEXOUQ+b cU0AUA/+Pmt3wJOc//NEcV6/p6cKGfOaeX9x40brcjAk+0Y9rnwPIWQK74SVUQt6 DV0NSV6THp/SeTHzZ/YHfdayHZllIuzjb3yy6j4gyd9q7drUoLe0YeX+QPXY67fO UMBcfrTdIOzYyQHs3+EpQwZZfe1pSN1ZySul9SvoG1bjm81H8TW4JWCn6A/a/hrM N4+lbDYwJK83liwR9cMRE6PiV8a4kI+g0oPwuuqsf5BLPjSgf2CrVRNW23ivoI4o zrPj+wLkMt1NNrfbc8wF8451zP5x6/t5fxM8f/3tAgeZzvRqw7p/zJnWluXNdPMO 66Bte+2X97XKD6pg+P/As7GxW74NNMaexj0bPIHgytNtZaXM56/pyG/Y3dYU16VJ jW7OSnrBPtConULT/9YbndbtnxcobTzbkU7kictUKrs/p7jApMOCH/xA5cBno95H lItEoltWurGHATA8CsBe4DNlYAcLPmNnfkyFeVDZzbR6P2vRrMJa2JhvMi3rScZc +QdI5HSUR/lJ/w6zF6lcPG0TbkdETiVO8OVC95LXxvo+hbVhBNyGZbrmiKlU5bkZ rkFwYDkFNVMUOjGlJZ/qggt0AZLv8Yw+LsQYwN7MrhAbec/tpMZFOr4Qynf4BOv3 C4I2uIfiwT0vpUYFuoJjjsSc5FUNSokMNA4ZSRkLh0ij9TnJoi0= =87Q4 -END PGP SIGNATURE End Message ---
Bug#979102: Legally problematic GPL-3+ readline dependency
Greetings! I've uploaded a gcl and maxima closing this to see how it goes. This will require changing the build-depends of every reverse gcl dependency, which is a little annoying but ok I suppose. The obvious alternative is to stick with readline and indicate that the binary is gclv3, as I do not think we have any gplv2 *only* code (checking this). The latest standard for the debian/copyright file refers to source files only. In fact I do not see how it could do otherwise, as say someone revives libreadline-gplv2 and runs maxima with that installed -- one cannot figure out the binary license until it is actually run. Hence the GCL runtime banner, which could be extended for this purpose I suppose. But in any case, I no longer understand the premise of this bug, unless it was your understanding that the source was gplv2 *only* instead of "or any later version". To my (extremely limited) understanding, we do not have a systematic way to track binary licenses which can only be determined at runtime in Debian. If I have overlooked anything, my humblest apologies -- am eager to be enlightened further. Take care, Bastian Germann writes: > Hi Camm, > > I think the runtime cannot distinguish between libraries because it is > the library that gcl is linked with that is loaded. You can also > compile gcl with build dependency libeditreadline-dev if you remove > the RL_READLINE_VERSION check that is introduced with patch > Version_2_6_13pre12. Additionally you could remove "READLINE" from the > GPL banner then (not necessary). > > I see that you are also the gcl maintainer, so you can coordinate > uploads of maxima and gcl linked with libedit. > > Thanks, > Bastian > > Am 12.10.21 um 16:07 schrieb Camm Maguire: >> Greetings, and thanks for this! >> It would be nice to migrate to editreadline. GCL at present >> constructs >> a binary license banner indicating GPL'ed components. How would runtime >> gcl distinguish between these two libraries of the same name? >> Take care, >> Bastian Germann writes: >> >>> Control: found -1 5.44.0-3 >>> >>> On Sat, 2 Jan 2021 18:48:19 +0100 Bastian Germann >>> wrote: However, that is orphaned in Debian, so libeditreadline-dev should be preferred, which does not compile with your package without any patch. It links with the BSD-licensed libedit library which is a readline replacement. >>> >>> The current version compiles with libeditreadline-dev without any patch. >>> I do not see the build influenced by it and guess libreadline is still >>> loaded via gcl. >>> Can you please comment on this? > > > -- Camm Maguirec...@maguirefamily.org == "The earth is but one country, and mankind its citizens." -- Baha'u'llah
Bug#999334: android-platform-tools: FTBFS: error: no member named 'unique_lock' in namespace 'std'
Source: android-platform-tools
Version: 29.0.6-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source
X-Debbugs-Cc: sramac...@debian.org
| clang++ -c -o system/core/liblog/event_tag_map.o
system/core/liblog/event_tag_map.cpp -g -O2
-ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat
-Werror=format-security -fPIC -std=gnu++17 -Wdate-time -D_FORTIFY_SOURCE=2
-DNDEBUG -UDEBUG -Isystem/core/liblog/include -Isystem/core/include
-Isystem/core/base/include -I/usr/include/android -DLIBLOG_LOG_TAG=1006
-DFAKE_LOG_DEVICE=1 -DSNET_EVENT_LOG_TAG=1397638484
| system/core/liblog/logger_write.cpp:147:20: error: no member named
'unique_lock' in namespace 'std'
| auto lock = std::unique_lock{default_tag_lock};
| ~^
| system/core/liblog/logger_write.cpp:147:31: error: expected ';' at end of
declaration
| auto lock = std::unique_lock{default_tag_lock};
| ^
| ;
| system/core/liblog/logger_write.cpp:170:20: error: no member named
'unique_lock' in namespace 'std'
| auto lock = std::unique_lock{logger_function_lock};
| ~^
| system/core/liblog/logger_write.cpp:170:31: error: expected ';' at end of
declaration
| auto lock = std::unique_lock{logger_function_lock};
| ^
| ;
| system/core/liblog/logger_write.cpp:187:20: error: no member named
'unique_lock' in namespace 'std'
| auto lock = std::unique_lock{aborter_function_lock};
| ~^
| system/core/liblog/logger_write.cpp:187:31: error: expected ';' at end of
declaration
| auto lock = std::unique_lock{aborter_function_lock};
| ^
| ;
| 6 errors generated.
See
https://buildd.debian.org/status/fetch.php?pkg=android-platform-tools=amd64=29.0.6-1%2Bb1=1636368880=0
Cheers
--
Sebastian Ramacher
signature.asc
Description: PGP signature
Bug#997474: marked as done (pysdl2: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)
Your message dated Tue, 9 Nov 2021 22:35:04 +0100
with message-id <8e4eebab-424c-53b4-3b5d-b0a7921a2...@debian.org>
and subject line pysdl2: FTBFS: dh_auto_test: error: pybuild --test
--test-pytest -i python{version} -p 3.9 returned exit code 13
has caused the Debian Bug report #997474,
regarding pysdl2: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i
python{version} -p 3.9 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.)
--
997474: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997474
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pysdl2
Version: 0.9.7+dfsg1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> mkdir -p ./doc/_static
> set -e; \
> for i in ./doc/modules/images/*.dia; do \
> dia "${i}" --filter=png-libart --export="$(echo $i|sed
> 's/\.dia$//').png"; \
> done
> ./doc/modules/images/coordinate_rhs.dia -->
> ./doc/modules/images/coordinate_rhs.png
> ./doc/modules/images/copprocessing.dia -->
> ./doc/modules/images/copprocessing.png
> ./doc/modules/images/ebs.dia --> ./doc/modules/images/ebs.png
> ./doc/modules/images/uiprocessing.dia -->
> ./doc/modules/images/uiprocessing.png
> rsvg-convert --format=png --background-color=white
> examples/resources/testimage.svg|convert png:- examples/resources/hello.bmp
> make[1]: Leaving directory '/<>'
>dh_auto_build -O--buildsystem=pybuild
> I: pybuild base:232: /usr/bin/python3 setup.py build
> running build
> running build_py
> creating /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/video.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/dll.py -> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/error.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/rect.py -> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/__init__.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/joystick.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/mouse.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/sdlgfx.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/stdinc.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/power.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/scancode.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/events.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/hints.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/sdlttf.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/surface.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/endian.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/messagebox.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/pixels.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/keyboard.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/blendmode.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/sdlimage.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/keycode.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/touch.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/vulkan.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/sdlmixer.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/rwops.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/platform.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/loadso.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/filesystem.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/clipboard.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/version.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/log.py -> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/timer.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/gesture.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/gamecontroller.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/shape.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/haptic.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/cpuinfo.py ->
> /<>/.pybuild/cpython3_3.9_sdl2/build/sdl2
> copying sdl2/render.py ->
>
Bug#998913: libbiod: FTBFS with ldc 1.28.0
Source: libbiod Version: 0.2.3+git20191120.b8eecef-2 Severity: serious Tags: ftbfs sid bookworm Justification: fails to build from source (but built successfully in the past) libbiod fails to build: | ../bio/std/experimental/hts/bam/reader.d(237): Error: no property `cleanup` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(245): Error: no property `is_mapped` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(246): Error: no property `refid` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(250): Error: no property `refid` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(254): Error: no property `_flag_nc` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(258): Error: no property `_flag` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(267): Error: no property `is_mapped` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(268): Error: no property `pos` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(269): Error: no property `pos` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(273): Error: no property `pos` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(280): Error: incompatible types for `(this.start_pos()) + (this.consumed_reference_bases())`: `uint` and `Nullable!uint` | ../bio/std/experimental/hts/bam/reader.d(284): Error: incompatible types for `(this.raw_start_pos()) + (this.consumed_reference_bases())`: `uint` and `Nullable!uint` | ../bio/std/experimental/hts/bam/reader.d(296): Error: no property `is_mapped` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(297): Error: no property `mapping_quality` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(301): Error: no property `_tlen` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(306): Error: no property `sequence_length` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(307): Error: cannot implicitly convert expression `this.sequence_length2` of type `Nullable!int` to `uint` | ../bio/std/experimental/hts/bam/reader.d(314): Error: no property `is_mapped` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(316): Error: no property `raw_cigar` for type `std.typecons.Nullable!(ReadBlob)` | ../bio/std/experimental/hts/bam/reader.d(335): Error: no property `is_mapped` for type `std.typecons.Nullable!(ReadBlob)` See https://buildd.debian.org/status/fetch.php?pkg=libbiod=amd64=0.2.3%2Bgit20191120.b8eecef-2%2Bb4=1636458777=0 Cheers -- Sebastian Ramacher
Bug#984421: marked as done (yade: ftbfs with GCC-11)
Your message dated Tue, 09 Nov 2021 21:21:51 + with message-id and subject line Bug#984421: fixed in yade 2021.11~git~6f71ebd-1 has caused the Debian Bug report #984421, regarding yade: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 984421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984421 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:yade Version: 2021.01a-3 Severity: normal Tags: sid bookworm User: debian-...@lists.debian.org Usertags: ftbfs-gcc-11 [This bug is not targeted to the upcoming bullseye release] Please keep this issue open in the bug tracker for the package it was filed for. If a fix in another package is required, please file a bug for the other package (or clone), and add a block in this package. Please keep the issue open until the package can be built in a follow-up test rebuild. The package fails to build in a test rebuild on at least amd64 with gcc-11/g++-11, but succeeds to build with gcc-10/g++-10. The severity of this report will be raised before the bookworm release, so nothing has to be done for the bullseye release. The full build log can be found at: http://people.debian.org/~doko/logs/20210228/filtered/gcc11/yade_2021.01a-3_unstable_gcc11.log The last lines of the build log are at the end of this report. To build with GCC 11, either set CC=gcc-11 CXX=g++-11 explicitly, or install the gcc, g++, gfortran, ... packages from experimental. apt-get -t=experimental install g++ Common build failures are new warnings resulting in build failures with -Werror turned on, or new/dropped symbols in Debian symbols files. For other C/C++ related build failures see the porting guide at http://gcc.gnu.org/gcc-11/porting_to.html GCC 11 defaults to the GNU++17 standard. If your package installs header files in /usr/include, please don't work around C++17 issues by choosing a lower C++ standard for the package build, but fix these issues to build with the C++17 standard. [...] /usr/lib/qt5/bin/moc -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_LOG_DYN_LINK -DBOOST_PYTHON_DYN_LINK -DBOOST_REGEX_DYN_LINK -DBOOST_SERIALIZATION_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK -DMAX_LOG_LEVEL=5 -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB -DSUITESPARSE_VERSION_4 -DYADE_BOOST_LOG -DYADE_DISABLE_REAL_MULTI_HP -DYADE_FEM -DYADE_ODEINT -DYADE_POTENTIAL_PARTICLES -DYADE_REAL_BIT=64 -DYADE_REAL_DEC=15 -DYADE_SPH -D_GLViewer_EXPORTS -I/<> -I/usr/include/python3.9 -I/usr/lib/python3/dist-packages/numpy/core/include -I/usr/include/eigen3 -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include -I/usr/include/suitesparse -I/usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -I/usr/lib/x86_64-linux-gnu/openmpi/include -I/usr/lib/python3/dist-packages/mpi4py/include -I/<>/debian/b uild -I/usr/include/QGLViewer -I/usr/include/x86_64-linux-gnu/qt5 -I/usr/include/x86_64-linux-gnu/qt5/QtWidgets -I/usr/include/x86_64-linux-gnu/qt5/QtGui -I/usr/include/x86_64-linux-gnu/qt5/QtCore -I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++ -I/usr/include/x86_64-linux-gnu/qt5/QtXml -I/usr/include/x86_64-linux-gnu/qt5/QtOpenGL -I/usr/include -I/usr/include/x86_64-linux-gnu -I/usr/include/c++/11 -I/usr/include/x86_64-linux-gnu/c++/11 -I/usr/include/c++/11/backward -I/usr/lib/gcc/x86_64-linux-gnu/11/include -I/usr/local/include --include /<>/debian/build/gui/_GLViewer_autogen/moc_predefs.h --output-dep-file -o /<>/debian/build/gui/_GLViewer_autogen/OXRBQHTNNB/moc_OpenGLManager.cpp /<>/gui/qt5/OpenGLManager.hpp AutoMoc: Generating "SRC:/debian/build/gui/_GLViewer_autogen/OXRBQHTNNB/moc_GLViewer.cpp", because it doesn't exist, from "SRC:/gui/qt5/GLViewer.hpp" /usr/lib/qt5/bin/moc -DBOOST_ALL_NO_LIB -DBOOST_ATOMIC_DYN_LINK -DBOOST_CHRONO_DYN_LINK -DBOOST_DATE_TIME_DYN_LINK -DBOOST_FILESYSTEM_DYN_LINK -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_LOG_DYN_LINK -DBOOST_PYTHON_DYN_LINK -DBOOST_REGEX_DYN_LINK -DBOOST_SERIALIZATION_DYN_LINK -DBOOST_SYSTEM_DYN_LINK -DBOOST_THREAD_DYN_LINK -DMAX_LOG_LEVEL=5 -DQT_CORE_LIB -DQT_GUI_LIB -DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB -DSUITESPARSE_VERSION_4 -DYADE_BOOST_LOG -DYADE_DISABLE_REAL_MULTI_HP -DYADE_FEM -DYADE_ODEINT -DYADE_POTENTIAL_PARTICLES -DYADE_REAL_BIT=64 -DYADE_REAL_DEC=15 -DYADE_SPH -D_GLViewer_EXPORTS -I/<> -I/usr/include/python3.9 -I/usr/lib/python3/dist-packages/numpy/core/include
Bug#998912: python3-hbmqtt: MQTTClient fails connecting to any broker: TypeError: 'Lock' object is not iterable
Package: python3-hbmqtt
Version: 0.9.6-1.1
Severity: grave
Justification: hbmqtt.client.MQTTClient.connect never works
Tags: patch upstream
The MQTTClient is not useable at all at present. Trying to connect to
any broker results in the following:
| Unhandled exception: 'Lock' object is not iterable
| Connection failed: TypeError("'Lock' object is not iterable")
| Unhandled exception: 'Lock' object is not iterable
| Reconnection attempt failed: TypeError("'Lock' object is not iterable")
| Unhandled exception: 'Lock' object is not iterable
| Reconnection attempt failed: TypeError("'Lock' object is not iterable")
| Unhandled exception: 'Lock' object is not iterable
| Reconnection attempt failed: TypeError("'Lock' object is not iterable")
| Maximum number of connection attempts reached. Reconnection aborted
| Traceback (most recent call last):
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 149, in connect
| return (yield from self._do_connect())
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 234, in
_do_connect
| return_code = yield from self._connect_coro()
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 423, in
_connect_coro
| return_code = yield from self._handler.mqtt_connect()
| File
"/usr/lib/python3/dist-packages/hbmqtt/mqtt/protocol/client_handler.py", line
83, in mqtt_connect
| yield from self._send_packet(connect_packet)
| File "/usr/lib/python3/dist-packages/hbmqtt/mqtt/protocol/handler.py", line
445, in _send_packet
| with (yield from self._write_lock):
| TypeError: 'Lock' object is not iterable
|
| During handling of the above exception, another exception occurred:
|
| Traceback (most recent call last):
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 220, in
reconnect
| return (yield from self._do_connect())
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 234, in
_do_connect
| return_code = yield from self._connect_coro()
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 423, in
_connect_coro
| return_code = yield from self._handler.mqtt_connect()
| File
"/usr/lib/python3/dist-packages/hbmqtt/mqtt/protocol/client_handler.py", line
83, in mqtt_connect
| yield from self._send_packet(connect_packet)
| File "/usr/lib/python3/dist-packages/hbmqtt/mqtt/protocol/handler.py", line
445, in _send_packet
| with (yield from self._write_lock):
| TypeError: 'Lock' object is not iterable
|
| During handling of the above exception, another exception occurred:
|
| Traceback (most recent call last):
| File "", line 1, in
| File "/usr/lib/python3.9/asyncio/base_events.py", line 642, in
run_until_complete
| return future.result()
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 156, in connect
| return (yield from self.reconnect())
| File "/usr/lib/python3/dist-packages/hbmqtt/client.py", line 225, in
reconnect
| raise ConnectException("Too many connection attempts failed")
| hbmqtt.client.ConnectException: Too many connection attempts failed
The cause for this is a change in how asyncio Locks work. Their support
for the pre-async API based on iterators has ceased, but hbmqtt attempts
to do so. Avoiding the context manager does the trick here. Please find
a minimal patch fixing the problem attached.
In any case, hbmqtt looks quite dead upstream. Maybe replacing it with
https://github.com/sbtinstruments/asyncio-mqtt would be better.
Helmut
--- a/hbmqtt/mqtt/protocol/handler.py
+++ b/hbmqtt/mqtt/protocol/handler.py
@@ -442,8 +442,11 @@ class ProtocolHandler:
@asyncio.coroutine
def _send_packet(self, packet):
try:
-with (yield from self._write_lock):
+yield from self._write_lock.acquire()
+try:
yield from packet.to_stream(self.writer)
+finally:
+self._write_lock.release()
if self._keepalive_task:
self._keepalive_task.cancel()
self._keepalive_task = self._loop.call_later(self.keepalive_timeout, self.handle_write_timeout)
Processed: update bts with the right meta info
Processing commands for cont...@bugs.debian.org:
> reassign 998143 src:discosnp 4.4.4-2
Bug #998143 {Done: Andreas Tille } [src:gatb-core,
src:discosnp] gatb-core breaks discosnp autopkgtest: Segmentation fault
Bug reassigned from package 'src:gatb-core, src:discosnp' to 'src:discosnp'.
No longer marked as found in versions discosnp/4.4.4-2 and
gatb-core/1.4.2+dfsg-7.
No longer marked as fixed in versions discosnp/1:2.5.4-1.
Bug #998143 {Done: Andreas Tille } [src:discosnp] gatb-core
breaks discosnp autopkgtest: Segmentation fault
Marked as found in versions discosnp/4.4.4-2.
> fixed 998143 1:2.5.4-1
Bug #998143 {Done: Andreas Tille } [src:discosnp] gatb-core
breaks discosnp autopkgtest: Segmentation fault
The source 'discosnp' and version '1:2.5.4-1' do not appear to match any binary
packages
Marked as fixed in versions discosnp/1:2.5.4-1.
> affects 998143 src:gatb-core
Bug #998143 {Done: Andreas Tille } [src:discosnp] gatb-core
breaks discosnp autopkgtest: Segmentation fault
Added indication that 998143 affects src:gatb-core
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
998143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998143
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#998911: node-string-width: file conflict with node-slice-ansi
Package: node-string-width Version: 4.2.3+~3.0.0+~9.2.2-1 Severity: serious Unpacking node-slice-ansi (5.0.0+~4.0.0-2) ... dpkg: error processing archive /tmp/apt-dpkg-install-DvqJPE/12-node-slice-ansi_5.0.0+~4.0.0-2_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/is-fullwidth-code-point/index.d.ts', which is also in package node-string-width 4.2.3+~3.0.0+~9.2.2-1
Bug#855541: purple-matrix: Not ready for release yet
On Mon, Sep 28, 2020 at 07:03:45PM +0200, Alberto Garcia wrote: > I think that this project is essentially dead, there has never been > a release and as you say there hasn't been changes in almost a year. > > I have stopped using it myself and the reason why I didn't ask for > its removal from Debian is that it's a very small package with a > very low manteinance burden (and because popcon shows that it has > some users). FYI I decided to give this package for adoption. I'll request its removal from the archive if there are no volunteers to take over its maintenance after some time. https://bugs.debian.org/998660 Berto
Bug#998143: marked as done (gatb-core breaks discosnp autopkgtest: Segmentation fault)
Your message dated Tue, 09 Nov 2021 20:36:02 + with message-id and subject line Bug#998143: fixed in discosnp 1:2.5.4-1 has caused the Debian Bug report #998143, regarding gatb-core breaks discosnp autopkgtest: Segmentation fault 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.) -- 998143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998143 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gatb-core, discosnp Control: found -1 gatb-core/1.4.2+dfsg-7 Control: found -1 discosnp/4.4.4-2 Severity: serious Tags: sid bookworm X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent upload of gatb-core the autopkgtest of discosnp fails in testing when that autopkgtest is run with the binary packages of gatb-core from unstable. It passes when run with only packages from testing. In tabular form: passfail gatb-core from testing1.4.2+dfsg-7 discosnp from testing4.4.4-2 all others from testingfrom testing I copied some of the output at the bottom of this report. Currently this regression is blocking the migration of gatb-core to testing [1]. Due to the nature of this issue, I filed this bug report against both packages. Can you please investigate the situation and reassign the bug to the right package? More information about this bug and the reason for filing it can be found on https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation Paul [1] https://qa.debian.org/excuses.php?package=gatb-core https://ci.debian.net/data/autopkgtest/testing/amd64/d/discosnp/16314588/log.gz tput: No value for $TERM and no -T specified tput: No value for $TERM and no -T specified tput: No value for $TERM and no -T specified tput: No value for $TERM and no -T specified tput: No value for $TERM and no -T specified tput: No value for $TERM and no -T specified Running discoSnp++ 2.3.X, in directory /usr with following parameters: read_sets=fof.txt prefix=discoRes_k_31_c_3 c=3 C=2147483647 k=31 b=0 d=1 D=100 s= P=3 p=discoRes G= e= starting date=Sat Oct 30 11:09:22 UTC 2021 GRAPH CREATION ### /usr/bin/dbgh5 -in fof.txt_discoRes_k_31_c_3_D_100_P_3_b_0_removemeplease -out discoRes_k_31_c_3 -kmer-size 31 -abundance-min 3 -abundance-max 2147483647 -solidity-kind one -verbose 1 -skip-bcalm -skip-bglue -no-mphf [DSK: counting kmers ] 0% elapsed: 0 min 0 sec remaining: 0 min 0 sec cpu: -1.0 % mem: [ 25, 25, 58] MB [DSK: Pass 1/1, Step 1: partitioning ] 0% elapsed: 0 min 0 sec remaining: 0 min 0 sec cpu: -1.0 % mem: [ 53, 53, 58] MB [DSK: Pass 1/1, Step 2: counting kmers ] 2.24 % elapsed: 0 min 2 sec remaining: 1 min 8 sec cpu: 108.3 % mem: [1902, 1902, 1902] MB [DSK: Pass 1/1, Step 2: counting kmers ] 2.24 % elapsed: 0 min 2 sec remaining: 1 min 8 sec cpu: 108.3 % mem: [1904, 1904, 1904] MB [DSK: Pass 1/1, Step 2: counting kmers ] 3.72 % elapsed: 0 min 2 sec remaining: 0 min 41 sec cpu: 109.6 % mem: [1904, 1904, 1904] MB [DSK: Pass 1/1, Step 2: counting kmers ] 5.27 % elapsed: 0 min 2 sec remaining: 0 min 28 sec cpu: 109.6 % mem: [1904, 1904, 1904] MB [DSK: Pass 1/1, Step 2: counting kmers ] 5.27 % elapsed: 0 min 2 sec remaining: 0 min 28 sec cpu: 109.6 % mem: [1905, 1905, 1905] MB [DSK: Pass 1/1, Step 2: counting kmers ] 6.52 % elapsed: 0 min 2 sec remaining: 0 min 22 sec cpu: 109.6 % mem: [1909, 1909, 1909] MB [DSK: Pass 1/1, Step 2: counting kmers ] 8% elapsed: 0 min 2 sec remaining: 0 min 18 sec cpu: 110.8 % mem: [1912, 1912, 1912] MB [DSK: Pass 1/1, Step 2: counting kmers ] 8.81 % elapsed: 0 min 2 sec remaining: 0 min 16 sec cpu: 111.5 % mem: [1912, 1912, 1912] MB [DSK: Pass 1/1, Step 2: counting kmers ] 10.1 % elapsed: 0 min 2 sec remaining: 0 min 14 sec cpu: 111.5 % mem: [1913, 1913, 1913] MB [DSK: Pass 1/1, Step 2: counting kmers ] 10.1 % elapsed: 0 min 2 sec remaining: 0 min 14 sec cpu: 111.5 % mem: [1913, 1913, 1914] MB [DSK: Pass 1/1, Step 2: counting kmers ] 12.2 % elapsed: 0 min 2 sec
Processed: block 984016 with 996589
Processing commands for cont...@bugs.debian.org:
> block 984016 with 996589
Bug #984016 {Done: Adrian Bunk } [src:cloudcompare]
cloudcompare: ftbfs with GCC-11
984016 was blocked by: 996589
984016 was not blocking any bugs.
Ignoring request to alter blocking bugs of bug #984016 to the same blocks
previously set
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984016: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984016
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: 2.20.0 builds
Processing commands for cont...@bugs.debian.org: > tags 996228 fixed-upstream Bug #996228 [src:ruby-ffaker] ruby-ffaker: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Error: test_ssn_with_from_to(TestSSNSE): ArgumentError: wrong number of arguments (given 4, expected 3) Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 996228: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996228 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: 4.2.0 builds
Processing commands for cont...@bugs.debian.org: > tags 996215 fixed-upstream Bug #996215 [src:ruby-dbf] ruby-dbf: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: Failure/Error: @encoding ? value.force_encoding(@encoding).encode(*ENCODING_ARGS) : value Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 996215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996215 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996318: marked as done (ruby-messagebus-api: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: expected no Exception, got # with bac
Your message dated Tue, 09 Nov 2021 19:51:05 +
with message-id
and subject line Bug#996318: fixed in ruby-messagebus-api
3.0.7+git.20130130.97b34ece.REALLY.1.0.3-3
has caused the Debian Bug report #996318,
regarding ruby-messagebus-api: FTBFS with ruby3.0: ERROR: Test "ruby3.0"
failed:expected no Exception, got # with backtrace:
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.)
--
996318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996318
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: ruby-messagebus-api
Version: 3.0.7+git.20130130.97b34ece.REALLY.1.0.3-2.1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: debian-r...@lists.debian.org
Usertags: ruby3.0
Hi,
We are about to enable building against ruby3.0 on unstable. During a test
rebuild, ruby-messagebus-api was found to fail to build in that situation.
To reproduce this locally, you need to install ruby-all-dev from experimental
on an unstable system or build chroot.
Relevant part (hopefully):
>expected no Exception, got # for URI:Module> with backtrace:
> # /<>/lib/messagebus_ruby_api/messagebus.rb:130:in
> `stats'
> #
> /<>/spec/messagebus_ruby_api/messagebus_spec.rb:320:in `block (4
> levels) in '
> #
> /<>/spec/messagebus_ruby_api/messagebus_spec.rb:319:in `block (3
> levels) in '
> # /<>/spec/messagebus_ruby_api/messagebus_spec.rb:319:in
> `block (3 levels) in '
>
> Finished in 0.09083 seconds (files took 0.71624 seconds to load)
> 22 examples, 3 failures
>
> Failed examples:
>
> rspec /<>/spec/messagebus_ruby_api/messagebus_spec.rb:223 #
> MessagebusApi::Messagebus#delivery_errors request delivery errors list
> rspec /<>/spec/messagebus_ruby_api/messagebus_spec.rb:238 #
> MessagebusApi::Messagebus#unsubscribes request blocked emails list
> rspec /<>/spec/messagebus_ruby_api/messagebus_spec.rb:312 #
> MessagebusApi::Messagebus#stats stats
>
> /usr/bin/ruby3.0
> -I/usr/share/rubygems-integration/all/gems/rspec-support-3.9.3/lib:/usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/lib
> /usr/share/rubygems-integration/all/gems/rspec-core-3.9.2/exe/rspec
> --pattern ./spec/\*\*/\*_spec.rb failed
> ERROR: Test "ruby3.0" failed:
The full build log is available at
https://people.debian.org/~kanashiro/ruby3.0/round2/builds/3/ruby-messagebus-api/ruby-messagebus-api_3.0.7+git.20130130.97b34ece.REALLY.1.0.3-2.1+rebuild1633386486_amd64.build.txt
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Source: ruby-messagebus-api
Source-Version: 3.0.7+git.20130130.97b34ece.REALLY.1.0.3-3
Done: Daniel Leidert
We believe that the bug you reported is fixed in the latest version of
ruby-messagebus-api, 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 996...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Leidert (supplier of updated ruby-messagebus-api
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, 09 Nov 2021 20:02:12 +0100
Source: ruby-messagebus-api
Architecture: source
Version: 3.0.7+git.20130130.97b34ece.REALLY.1.0.3-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team
Changed-By: Daniel Leidert
Closes: 996318
Changes:
ruby-messagebus-api (3.0.7+git.20130130.97b34ece.REALLY.1.0.3-3) unstable;
urgency=medium
.
* Team upload.
.
[ Cédric Boutillier ]
* Remove version in the gem2deb build-dependency
.
[ Debian Janitor ]
* Use secure copyright file specification URI.
* Use secure URI in debian/watch.
* Set debhelper-compat version in Build-Depends.
* Update Vcs-* headers from URL redirect.
* Use canonical URL in Vcs-Git.
* Bump debhelper to 13.
* Remove overrides for lintian tags that are no longer supported.
.
[ Daniel Leidert ]
* d/control: Add Rules-Requires-Root and Testsuite fields.
(Standards-Version): Bump to 4.6.0.
(Homepage): Set to rubygems.
(Depends): Remove interpreters and use ${ruby:Depends}.
* d/messagebus-ruby-api.docs: Renamed to d/ruby-messagebus-api.docs.
* d/messagebus-ruby-api.examples:
Bug#998867: debootstrap: --no-merged-usr became a no-op
Quoting Julien Cristau (2021-11-09 09:33:14) > On Tue, Nov 09, 2021 at 07:49:03AM +0100, Johannes Schauer Marin Rodrigues > wrote: > > since 1.0.126 the --no-merged-usr option became a no-op if for any code > > name but > > etch*|lenny|squeeze|wheezy|jessie*|stretch|ascii|buster|beowulf|bullseye > > > > This means that I cannot create a Debian chroot from Debian unstable > > from 10 years ago from snapshot.debian.org without merged-/usr and thus > > my chroot will behave differently as it did back then. > > > > Please re-enable --no-merged-usr so that I can re-create old chroots > > from snapshot.d.o again. > > > Also, build chroots must still be created without merged-usr for > sid/bookworm, until something's been done to migrate user systems. Furthermore, you see a regression in the mmdebstrap autopkgtest due to this version: https://tracker.debian.org/pkg/debootstrap That regression is to this change of --no-merged-usr. Please point out what you plan to do about this change in debootstrap so that I can adapt the mmdebstrap autopkgtest accordingly. Thanks! cheers, josch signature.asc Description: signature
Processed: 4.6.0 builds
Processing commands for cont...@bugs.debian.org: > tags 996208 fixed-upstream Bug #996208 [src:ruby-commander] ruby-commander: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: RuntimeError: Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 996208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996208 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#988462: A little more info please?
Hi, Please could you expand on this slightly. I just upgraded my server from buster to bullseye, and was very unpleasantly surprised to discover that trac has been removed. I've been using it for 11 years, I run my whole life with it. It's never caused me any problems at all - please could you explain why it is not suitable for inclusion in bullseye? What is it that I am not seeing or experiencing in my daily use of it? Also, please could you recommend an alternative ticket management package that is included in bullseye. Preferably one that will import my trac db so I don't have to re-enter 11 years of history. Thanks Chris
Bug#997639: marked as done (python-keepalive: FTBFS: error in keepalive setup command: use_2to3 is invalid.)
Your message dated Tue, 09 Nov 2021 19:34:33 +
with message-id
and subject line Bug#997639: fixed in python-keepalive 0.5-3
has caused the Debian Bug report #997639,
regarding python-keepalive: FTBFS: error in keepalive setup command: use_2to3
is invalid.
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
997639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-keepalive
Version: 0.5-2
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> fakeroot debian/rules clean
> dh clean --with python3 --buildsystem=pybuild
>dh_auto_clean -O--buildsystem=pybuild
> I: pybuild base:232: python3.9 setup.py clean
> error in keepalive setup command: use_2to3 is invalid.
> E: pybuild pybuild:354: clean: plugin distutils failed with: exit code=1:
> python3.9 setup.py clean
> dh_auto_clean: error: pybuild --clean -i python{version} -p 3.9 returned exit
> code 13
> make: *** [debian/rules:9: clean] Error 25
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/python-keepalive_0.5-2_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Source: python-keepalive
Source-Version: 0.5-3
Done: Nilesh Patra
We believe that the bug you reported is fixed in the latest version of
python-keepalive, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 997...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nilesh Patra (supplier of updated python-keepalive 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, 10 Nov 2021 00:43:50 +0530
Source: python-keepalive
Architecture: source
Version: 0.5-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Team
Changed-By: Nilesh Patra
Closes: 997639
Changes:
python-keepalive (0.5-3) unstable; urgency=medium
.
* Team Upload.
[ Debian Janitor ]
* Set upstream metadata fields: Bug-Database, Repository, Repository-
Browse.
.
[ Ondřej Nový ]
* d/control: Update Maintainer field with new Debian Python Team
contact address.
* d/control: Update Vcs-* fields with new Debian Python Team Salsa
layout.
.
[ Nilesh Patra ]
* Add patch to fix FTBFS with new setuptools (Closes: #997639)
* Add patch to port to python3 syntax
Checksums-Sha1:
d782280ef7a3ddc0a255a58ac7c43d5ed2255348 2100 python-keepalive_0.5-3.dsc
755253d764d2b64df20854c4a01a03c778647a38 5392
python-keepalive_0.5-3.debian.tar.xz
e4195bbaffb63d16c70e8f4b657269c529b10093 6243
python-keepalive_0.5-3_amd64.buildinfo
Checksums-Sha256:
dafa60712927d7bf69efe2c0acc6330c21687dc03b495c5bdd4ea5b7fcaa6cf9 2100
python-keepalive_0.5-3.dsc
51115427d018e8a18baddbd452275234ad4e55155e71d1364f2d1b23c868c405 5392
python-keepalive_0.5-3.debian.tar.xz
1fa23ded369d9b7ba869898f7a1b6bf8f75d36229c148801e364fddac3e1200a 6243
python-keepalive_0.5-3_amd64.buildinfo
Files:
4f9f93d55c6b3a4a2ffaef318bdce5a9 2100 python optional
python-keepalive_0.5-3.dsc
486344323def46f759d14b7bb101361c 5392 python optional
python-keepalive_0.5-3.debian.tar.xz
3e4b3eaaca37c14f0e3cc0957486c867 6243 python optional
python-keepalive_0.5-3_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQJGBAEBCgAwFiEEPpmlJvXcwMu/HO6mALrnSzQzafEFAmGKzFUSHG5pbGVzaEBk
ZWJpYW4ub3JnAAoJEAC650s0M2nxaPgP/jaE3VduC80MpHWKUNcI34nyFG2eWjAD
DNv4kxcgMNe4qlDmtExc1qqq9p03uDP/xp/+yF9i+6/aUnAkBxWquSvKTcdZoSOs
MeI0+qQd2jTfiO43wYjX2NEorJkXLCNDxmBWEbpYFpIC9sfgPskzj0OOdmThC7JN
Processed: Bug#996318 marked as pending in ruby-messagebus-api
Processing control commands: > tag -1 pending Bug #996318 [src:ruby-messagebus-api] ruby-messagebus-api: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed:expected no Exception, got # with backtrace: Added tag(s) pending. -- 996318: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996318: marked as pending in ruby-messagebus-api
Control: tag -1 pending Hello, Bug #996318 in ruby-messagebus-api reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-messagebus-api/-/commit/5d8a162ba9eecd016058ea7e42b0a2090f04e30f Add patch to fix FTBFS * d/patches/replace-deprecated-uri-escape.patch: Add patch. - Replace deprecated URI.escape method to fix FTBFS (closes: #996318). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996318
Bug#997639: marked as pending in python-keepalive
Control: tag -1 pending Hello, Bug #997639 in python-keepalive reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/python-keepalive/-/commit/1380546ed19ea18d6d0391874e1ca04c9c4b2636 Add patch to fix FTBFS with new setuptools (Closes: #997639) (this message was generated automatically) -- Greetings https://bugs.debian.org/997639
Processed: Bug#997639 marked as pending in python-keepalive
Processing control commands: > tag -1 pending Bug #997639 [src:python-keepalive] python-keepalive: FTBFS: error in keepalive setup command: use_2to3 is invalid. Added tag(s) pending. -- 997639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997639 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#988462: A little more info please?
Hi, Please could you expand on this slightly. I just upgraded my server from buster to bullseye, and was very unpleasantly surprised to discover that trac has been removed. I've been using it for 11 years, I run my whole life with it. It's never caused me any problems at all - please could you explain why it is not suitable for inclusion in bullseye? What is it that I am not seeing or experiencing in my daily use of it? Also, please could you recommend an alternative ticket management package that is included in bullseye. Preferably one that will import my trac db so I don't have to re-enter 11 years of history. Thanks Chris
Bug#992508: marked as done (units-filter FTBFS: dh_installdocs: error: Cannot find (any matches for) "README" (tried in ., debian/tmp))
Your message dated Tue, 09 Nov 2021 19:00:14 + with message-id and subject line Bug#992508: fixed in units-filter 4.1-1 has caused the Debian Bug report #992508, regarding units-filter FTBFS: dh_installdocs: error: Cannot find (any matches for) "README" (tried in ., debian/tmp) 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.) -- 992508: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992508 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: units-filter Version: 4.0.1-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: debhel...@packages.debian.org units-filter fails to build from source. A build ends with: |dh_installdocs | dh_installdocs: error: Cannot find (any matches for) "README" (tried in ., debian/tmp) | | make: *** [debian/rules:15: binary] Error 25 | dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 This is reproduced on crossqa: http://crossqa.debian.net/src/units-filter Helmut --- End Message --- --- Begin Message --- Source: units-filter Source-Version: 4.1-1 Done: Georges Khaznadar We believe that the bug you reported is fixed in the latest version of units-filter, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 992...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Georges Khaznadar (supplier of updated units-filter 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, 18 Aug 2021 14:43:52 +0200 Source: units-filter Binary: units-filter units-filter-dbgsym units-master Architecture: source amd64 all Version: 4.1-1 Distribution: unstable Urgency: medium Maintainer: Georges Khaznadar Changed-By: Georges Khaznadar Description: units-filter - Parser for expressions concerning physical values units-master - Powerful units converter with a GUI Closes: 992508 Changes: units-filter (4.1-1) unstable; urgency=medium . * new upstream version : features a new GUI * rewritten debian/copyright (DEP5 style), mentioned the three icons borrowed from KDE Oxygen development group and used for the GUI. * referenced README.rst and LISEZMOI.rst instead of README, LISEZMOI; Closes: #992508 * bumped a build-dependency: debhelper-compat (=13), and debian policy, Standards-Version: 4.5.1 * build-dependecies: added dh-python, python3, pyqt5-dev-tools, python3-docutils, qttools5-dev-tools, qt5-qmake * dependencies for the GUI: python3-pyqt5, units-filter, texlive-latex-base, pdf2svg, librsvg2-bin * separated the package units-master, which provides the GUI application Checksums-Sha1: 9814d9d80166e7fbcdda16a6fe245a5f0b57e759 2047 units-filter_4.1-1.dsc 8ee65d32c4db9da313a18484a47f06b59d9620ba 178916 units-filter_4.1.orig.tar.xz 035045b33b3b6cbc77e0cbcdc401d6043b0c4220 5956 units-filter_4.1-1.debian.tar.xz 7eee8a816c1053ffe07acf667f50b974492ee161 162492 units-filter-dbgsym_4.1-1_amd64.deb d870e2e46c7d7ae6181fdec09329b731178367d7 11925 units-filter_4.1-1_amd64.buildinfo 76a293d6c80106ae1c4db5934d5f2be3d11fbf00 42440 units-filter_4.1-1_amd64.deb fec3eb05d19b5269bd4c4bb5c0d49fb7567a1319 32256 units-master_4.1-1_all.deb Checksums-Sha256: 084b1cfe780952a7b9813ea545c271f30edad03d647bcf6899e0c37448b78fdf 2047 units-filter_4.1-1.dsc 923a32a49232fdf7fb10908ac2eb3d5054a5d4c6e1a7dda74df22fc12905288e 178916 units-filter_4.1.orig.tar.xz d32c21dc0656f204c13f18d1569415a4ef2925c539c86bbc594e9e0cd3b89f99 5956 units-filter_4.1-1.debian.tar.xz 071e9962d39fab874f1d2e3bec4d8a6b2e8c299448c6b1141fac23dd583896b2 162492 units-filter-dbgsym_4.1-1_amd64.deb 0c8f3b2c8dcf5fef56de2df3022b508580b0d35d5e16f8c130f1f11dc76e2511 11925 units-filter_4.1-1_amd64.buildinfo 503bceb8a4351491c4deedad1663a98f979b42b16f7b126ff7efca97d667879e 42440 units-filter_4.1-1_amd64.deb f763ab799bb9b2402501a8739ffc366d43d34fe5b81780e74d49f9e408883543 32256 units-master_4.1-1_all.deb Files: c8bc6592939b70df38878f358ba63017 2047 science optional units-filter_4.1-1.dsc 2b80570eb4fedb5bce9fdb71f7294ad3 178916 science optional units-filter_4.1.orig.tar.xz 0f39b2d1890676cd1c5ac36634646515 5956 science optional
Processed: tagging 997291
Processing commands for cont...@bugs.debian.org: > tags 997291 + pending Bug #997291 [src:tellico] tellico: FTBFS: ld: cannot find -lz Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 997291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997291 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: src:python-django: fails to migrate to testing for too long: autopkgtest regressions and unresolved RC bugs
Processing control commands:
> close -1 2:3.2.9-1
Bug #998904 [src:python-django] src:python-django: fails to migrate to testing
for too long: autopkgtest regressions and unresolved RC bugs
Marked as fixed in versions python-django/2:3.2.9-1.
Bug #998904 [src:python-django] src:python-django: fails to migrate to testing
for too long: autopkgtest regressions and unresolved RC bugs
Marked Bug as done
> block -1 by 996931
Bug #998904 {Done: Paul Gevers } [src:python-django]
src:python-django: fails to migrate to testing for too long: autopkgtest
regressions and unresolved RC bugs
998904 was not blocked by any bugs.
998904 was not blocking any bugs.
Added blocking bug(s) of 998904: 996931
--
998904: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998904
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#998904: src:python-django: fails to migrate to testing for too long: autopkgtest regressions and unresolved RC bugs
Source: python-django Version: 2:2.2.24-1 Severity: serious Control: close -1 2:3.2.9-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 996931 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:python-django has been trying to migrate for 61 days [2]. Hence, I am filing this bug. If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=python-django OpenPGP_signature Description: OpenPGP digital signature
Bug#998903: src:libidn: fails to migrate to testing for too long
Source: libidn Version: 1.38-3 Severity: serious Control: close -1 1.38-4 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 998901 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60 days as having a Release Critical bug in testing [1]. Your package src:libidn has been trying to migrate for 62 days [2]. Hence, I am filing this bug. The problem is that arch:all cruft is not automatically cleaned up, but in this case, the dropped binary also had a reverse dependency (just filed a bug about that), so I don't know if the cruft binary should just be removed (with the new source package that added the binary that depends on it). If a package is out of sync between unstable and testing for a longer period, this usually means that bugs in the package in testing cannot be fixed via unstable. Additionally, blocked packages can have impact on other packages, which makes preparing for the release more difficult. Finally, it often exposes issues with the package and/or its (reverse-)dependencies. We expect maintainers to fix issues that hamper the migration of their package in a timely manner. This bug will trigger auto-removal when appropriate. As with all new bugs, there will be at least 30 days before the package is auto-removed. I have immediately closed this bug with the version in unstable, so if that version or a later version migrates, this bug will no longer affect testing. I have also tagged this bug to only affect sid and bookworm, so it doesn't affect (old-)stable. If you believe your package is unable to migrate to testing due to issues beyond your control, don't hesitate to contact the Release Team. Paul [1] https://lists.debian.org/debian-devel-announce/2020/02/msg5.html [2] https://qa.debian.org/excuses.php?package=libidn OpenPGP_signature Description: OpenPGP digital signature
Bug#997187: marked as done (smemstat: FTBFS: smemstat.c:348:33: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Tue, 09 Nov 2021 18:49:16 + with message-id and subject line Bug#997187: fixed in smemstat 0.02.11-1 has caused the Debian Bug report #997187, regarding smemstat: FTBFS: smemstat.c:348:33: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 997187: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: smemstat Version: 0.02.10-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wall -Wextra -DVERSION='"0.02.10"' -O2 > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o smemstat.o smemstat.c > smemstat.c: In function ‘smemstat_top_printf’: > smemstat.c:348:33: error: format not a string literal and no format arguments > [-Werror=format-security] > 348 | (void)mvprintw(cury, 0, buf); > | ^~~ > cc1: some warnings being treated as errors > make[2]: *** [: smemstat.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/smemstat_0.02.10-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: smemstat Source-Version: 0.02.11-1 Done: Colin Ian King We believe that the bug you reported is fixed in the latest version of smemstat, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Ian King (supplier of updated smemstat 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: Tue, 9 Nov 2021 18:31:23 +0100 Source: smemstat Built-For-Profiles: noudeb Architecture: source Version: 0.02.11-1 Distribution: unstable Urgency: medium Maintainer: Colin Ian King Changed-By: Colin Ian King Closes: 997187 Changes: smemstat (0.02.11-1) unstable; urgency=medium . * Makefile: bump version * Makefile: add README.md to make dist rule * debian/watch: change location to github for tarballs * Update copyright and project email contact information * debian/control: update maintainer email address and project URL * smemstat.c: always use "%s"-style format for printf()-style functions (Closes: #997187) * README.md: Make headings into subheadings * Add README.md * snapcraft: update to core20 Checksums-Sha1: f8a521cbc6f327d8216f32a4be8e351c4e1b3c32 1802 smemstat_0.02.11-1.dsc e9d6c0bd898462c4c80d83b87f3d4558ba2015ac 22544 smemstat_0.02.11.orig.tar.xz 9bd50207d0f22212bdfb8252d5d1f71e60f7b8e7 3796 smemstat_0.02.11-1.debian.tar.xz 8577c293af55a0cb1ca96313263d19ffa7a879ca 8237 smemstat_0.02.11-1_source.buildinfo Checksums-Sha256: f28d14182343deb76d25d4311f0158241738b3e44ba13b84cf667b82cecec530 1802 smemstat_0.02.11-1.dsc 9d7788723c15283b2796392d4185d01d1901c5071e3849baf9d6cf3f63a9e63a 22544 smemstat_0.02.11.orig.tar.xz aeb59f05c234c92cab0ad30957ac76f600937048de4e506dec18b78d128355c0 3796 smemstat_0.02.11-1.debian.tar.xz c51307c4c0afbf316255540803a604c8618afd1dd241d37613823dd35a6b350d 8237 smemstat_0.02.11-1_source.buildinfo Files: 319ec12bf6d070321b7887e2c618791a 1802 admin optional smemstat_0.02.11-1.dsc cb90526946e23957d9bfe83b861f69c6 22544 admin optional smemstat_0.02.11.orig.tar.xz 513621a09081b9a7b8b6763494117b6d 3796 admin optional smemstat_0.02.11-1.debian.tar.xz 7fb3f8a34c184d5af57760fbd5bf677f 8237 admin optional smemstat_0.02.11-1_source.buildinfo -BEGIN PGP SIGNATURE-
Processed: src:libidn: fails to migrate to testing for too long
Processing control commands:
> close -1 1.38-4
Bug #998903 [src:libidn] src:libidn: fails to migrate to testing for too long
Marked as fixed in versions libidn/1.38-4.
Bug #998903 [src:libidn] src:libidn: fails to migrate to testing for too long
Marked Bug as done
> block -1 by 998901
Bug #998903 {Done: Paul Gevers } [src:libidn] src:libidn:
fails to migrate to testing for too long
998903 was not blocked by any bugs.
998903 was not blocking any bugs.
Added blocking bug(s) of 998903: 998901
--
998903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998903
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#997155: marked as done (faultstat: FTBFS: faultstat.c:389:22: error: format not a string literal and no format arguments [-Werror=format-security])
Your message dated Tue, 09 Nov 2021 18:33:33 + with message-id and subject line Bug#997155: fixed in faultstat 0.01.07-1 has caused the Debian Bug report #997155, regarding faultstat: FTBFS: faultstat.c:389:22: error: format not a string literal and no format arguments [-Werror=format-security] 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.) -- 997155: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997155 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: faultstat Version: 0.01.06-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong > -Wformat -Werror=format-security -Wall -Wextra -DVERSION='"0.01.06"' -O2 > -Wdate-time -D_FORTIFY_SOURCE=2 -c -o faultstat.o faultstat.c > faultstat.c: In function ‘faultstat_top_printf’: > faultstat.c:389:22: error: format not a string literal and no format > arguments [-Werror=format-security] > 389 | (void)printw(buf); > | ^~~ > cc1: some warnings being treated as errors > make[2]: *** [: faultstat.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/faultstat_0.01.06-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: faultstat Source-Version: 0.01.07-1 Done: Colin Ian King We believe that the bug you reported is fixed in the latest version of faultstat, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Colin Ian King (supplier of updated faultstat 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: Tue, 9 Nov 2021 18:06:12 + Source: faultstat Built-For-Profiles: noudeb Architecture: source Version: 0.01.07-1 Distribution: unstable Urgency: medium Maintainer: Colin Ian King Changed-By: Colin Ian King Closes: 997155 Changes: faultstat (0.01.07-1) unstable; urgency=medium . * Makefile: bump version * Makefile: add README.md to make dist rule * debian/watch: refresh to new tarball path on watch file * debian/copyright: add Colin Ian King details * Debian: update control file, new URL and maintainer info * Use "%s" format specifier for printw (Closes: #997155) * README.md: Add one more example * Add README.md Checksums-Sha1: daa977d13370cb1428686ec1804c7ea47a703dfd 1812 faultstat_0.01.07-1.dsc 826ddac91ecb68a07a3d65e609600fa462882b9a 19320 faultstat_0.01.07.orig.tar.xz 6ee3d0091133659f601bcbc69794539e0e098f4b 1992 faultstat_0.01.07-1.debian.tar.xz 76b1d6139d368bf3c30056314a0f811998a995c8 8241 faultstat_0.01.07-1_source.buildinfo Checksums-Sha256: 71137a4b79ab80cdf47179c034946fdb15b7a53cc85fd7ccb2dca2688905cf56 1812 faultstat_0.01.07-1.dsc ccd72e280935b7dc2aec72a8efb183ffcb09badafca6f3eda8c7e5eb44fe255d 19320 faultstat_0.01.07.orig.tar.xz 95aa0296706ce236d95332fdf46b28395a052d67b35818d1acacb9a73f2c3ca9 1992 faultstat_0.01.07-1.debian.tar.xz 782051a466305bf9bc9ffe361c926494ea5b5d6c39dc5f6fcc05cc21c84998ba 8241 faultstat_0.01.07-1_source.buildinfo Files: 8e8993c1c9c55a6d18973b002bbbd6c6 1812 admin optional faultstat_0.01.07-1.dsc cd38fc7301781d9e37d3fbfdc329a193 19320 admin optional faultstat_0.01.07.orig.tar.xz 58dd1bc4beb301e1ff34a319b023a403 1992 admin optional faultstat_0.01.07-1.debian.tar.xz 98466c2eaf7066a00afe5519217e 8241 admin optional faultstat_0.01.07-1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEcGLapPABucZhZwDPaMKH38aoAiYFAmGKuyMACgkQaMKH38ao
Processed: tagging 994423
Processing commands for cont...@bugs.debian.org: > tags 994423 + pending Bug #994423 [src:pytorch] pytorch: Baseline violation on armhf Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 994423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994423 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 998633
Processing commands for cont...@bugs.debian.org: > tags 998633 + pending Bug #998633 [src:shadow] shadow: Please switch libsemanage1-dev BD to libsemanage-dev Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 998633: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 984304 with 995360
Processing commands for cont...@bugs.debian.org:
> block 984304 with 995360
Bug #984304 {Done: Adrian Bunk } [src:pytorch] pytorch: ftbfs
with GCC-11
984304 was not blocked by any bugs.
984304 was not blocking any bugs.
Added blocking bug(s) of 984304: 995360
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
984304: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984304
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processed: bug 984118 is forwarded to https://github.com/google/farmhash/issues/24
Processing commands for cont...@bugs.debian.org: > forwarded 984118 https://github.com/google/farmhash/issues/24 Bug #984118 [src:farmhash] farmhash: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://github.com/google/farmhash/issues/24'. > thanks Stopping processing here. Please contact me if you need assistance. -- 984118: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984118 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 984050 with 944757
Processing commands for cont...@bugs.debian.org: > block 984050 with 944757 Bug #984050 [src:endless-sky] endless-sky: ftbfs with GCC-11 984050 was not blocked by any bugs. 984050 was not blocking any bugs. Added blocking bug(s) of 984050: 944757 > thanks Stopping processing here. Please contact me if you need assistance. -- 984050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984050 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998108: Rebuild w/ new toolchain
On Mon, 8 Nov 2021 12:58:54 +0100 Simon Frei wrote: > On 08/11/2021 12:21, Jakob Haufe wrote: > > On Mon, 8 Nov 2021 10:25:24 +0100 > > Matthias Urlichs wrote: > > > >> Looks like the problem is a toolchain matter and requires a rebuild with > >> Rust 1.56. > >> > >> https://bugzilla.opensuse.org/show_bug.cgi?id=1192067 > > According to the build log, 94.0-1 has been built with 1.56. > > > > I read that bug as saying that 1.56 does not have any changes compared > to 1.55 that are likely to change anything. They talk about 1.55 > requiring llvm12, not llvm13. As far as I understand their fix was to go > back to rust 1.55 with llvm12. > When I look at the dependencies of firefox, it does depend on rust 1.56, > which in turn was built with llvm13, so that's fine. However firefox > also depends on libgl1-mesa-dri and mesa-va-drivers, which depend on > llvm12. Maybe this discrepancy is the culprit? > Note that with lichess page I posted above it should be very easy to reproduce. Open page, refresh once.
Processed: Merge duplicates
Processing commands for cont...@bugs.debian.org: > reassign 984049 src:libvigraimpex Bug #984049 [src:enblend-enfuse] enblend-enfuse: ftbfs with GCC-11 Bug reassigned from package 'src:enblend-enfuse' to 'src:libvigraimpex'. No longer marked as found in versions enblend-enfuse/4.2-8. Ignoring request to alter fixed versions of bug #984049 to the same values previously set > forcemerge 984213 984049 Bug #984213 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-11 Bug #984049 [src:libvigraimpex] enblend-enfuse: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://github.com/ukoethe/vigra/issues/491'. Marked as found in versions libvigraimpex/1.11.1+dfsg-8. Added tag(s) help. Merged 984049 984213 > affects 984213 src:enblend-enfuse Bug #984213 [src:libvigraimpex] libvigraimpex: ftbfs with GCC-11 Bug #984049 [src:libvigraimpex] enblend-enfuse: ftbfs with GCC-11 Added indication that 984213 affects src:enblend-enfuse Added indication that 984049 affects src:enblend-enfuse > thanks Stopping processing here. Please contact me if you need assistance. -- 984049: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984049 984213: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984213 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 984166 is forwarded to https://github.com/jessek/hashdeep/commit/6ef69a26126ee4e69a25392fd456b8a66c51dffd
Processing commands for cont...@bugs.debian.org: > forwarded 984166 > https://github.com/jessek/hashdeep/commit/6ef69a26126ee4e69a25392fd456b8a66c51dffd Bug #984166 [src:hashdeep] hashdeep: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://github.com/jessek/hashdeep/commit/6ef69a26126ee4e69a25392fd456b8a66c51dffd'. > thanks Stopping processing here. Please contact me if you need assistance. -- 984166: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984166 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 984122 is forwarded to https://github.com/TASEmulators/fceux/commit/f4183a64952bc490229f3023561e6d9542ab51a2
Processing commands for cont...@bugs.debian.org: > forwarded 984122 > https://github.com/TASEmulators/fceux/commit/f4183a64952bc490229f3023561e6d9542ab51a2 Bug #984122 [src:fceux] fceux: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://github.com/TASEmulators/fceux/commit/f4183a64952bc490229f3023561e6d9542ab51a2'. > thanks Stopping processing here. Please contact me if you need assistance. -- 984122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984122 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 984214 is forwarded to https://github.com/openSUSE/libzypp/commit/1eaf650db88a74836a520e7881ead9b1e1b5d004
Processing commands for cont...@bugs.debian.org: > forwarded 984214 > https://github.com/openSUSE/libzypp/commit/1eaf650db88a74836a520e7881ead9b1e1b5d004 Bug #984214 [src:libzypp] libzypp: ftbfs with GCC-11 Set Bug forwarded-to-address to 'https://github.com/openSUSE/libzypp/commit/1eaf650db88a74836a520e7881ead9b1e1b5d004'. > thanks Stopping processing here. Please contact me if you need assistance. -- 984214: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984214 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: bug 984373 is forwarded to http://git.savannah.gnu.org/cgit/commoncpp.git/commit/?id=543e7a6fb37bc0527f945e3bb882a95c441c6414
Processing commands for cont...@bugs.debian.org: > forwarded 984373 > http://git.savannah.gnu.org/cgit/commoncpp.git/commit/?id=543e7a6fb37bc0527f945e3bb882a95c441c6414 Bug #984373 [src:ucommon] ucommon: ftbfs with GCC-11 Set Bug forwarded-to-address to 'http://git.savannah.gnu.org/cgit/commoncpp.git/commit/?id=543e7a6fb37bc0527f945e3bb882a95c441c6414'. > thanks Stopping processing here. Please contact me if you need assistance. -- 984373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984373 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#993350: Epson Perfection1640: Slide scan fails
> I have had a very quick skim of epson2.c and a couple of other files. > I can see a DBG macro which seems to be defined in sanei_debug.h > but I am not sure how to invoke it just yet. SANE_DEBUG_EPSON2= xsane Sorry, I am stuffed with work currently. I'll try to check your other mails until the weekend. signature.asc Description: PGP signature
Processed: 2.4.3 builds
Processing commands for cont...@bugs.debian.org: > tags 984270 fixed-upstream Bug #984270 [src:onednn] onednn: ftbfs with GCC-11 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 984270: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984270 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#997133: marked as done (consul: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 -short -failfast -timeout 8m [...] returned exit code 1)
Your message dated Tue, 09 Nov 2021 15:33:40 + with message-id and subject line Bug#997133: fixed in consul 1.8.7+dfsg1-3 has caused the Debian Bug report #997133, regarding consul: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 -short -failfast -timeout 8m [...] returned exit code 1 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.) -- 997133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: consul Version: 1.8.7+dfsg1-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > okgithub.com/hashicorp/consul/tlsutil 0.044s > ? github.com/hashicorp/consul/types [no test files] > ? github.com/hashicorp/consul/version [no test files] > FAIL > dh_auto_test: error: cd _build && go test -vet=off -v -p 4 -short -failfast > -timeout 8m github.com/hashicorp/consul github.com/hashicorp/consul/acl > github.com/hashicorp/consul/agent github.com/hashicorp/consul/agent/ae > github.com/hashicorp/consul/agent/auto-config > github.com/hashicorp/consul/agent/config > github.com/hashicorp/consul/agent/debug github.com/hashicorp/consul/agent/dns > github.com/hashicorp/consul/agent/exec > github.com/hashicorp/consul/agent/local > github.com/hashicorp/consul/agent/metadata > github.com/hashicorp/consul/agent/mock github.com/hashicorp/consul/agent/pool > github.com/hashicorp/consul/agent/router > github.com/hashicorp/consul/agent/structs > github.com/hashicorp/consul/agent/systemd > github.com/hashicorp/consul/agent/token github.com/hashicorp/consul/agent/xds > github.com/hashicorp/consul/agent/xds/proxysupport > github.com/hashicorp/consul/command github.com/hashicorp/consul/command/acl > github.com/hashicorp/consul/command/acl/agenttokens > github.com/hashicorp/consul/command/acl/authmethod > github.com/hashicorp/consul/command/acl/authmethod/create > github.com/hashicorp/consul/command/acl/authmethod/delete > github.com/hashicorp/consul/command/acl/authmethod/list > github.com/hashicorp/consul/command/acl/authmethod/read > github.com/hashicorp/consul/command/acl/authmethod/update > github.com/hashicorp/consul/command/acl/bindingrule > github.com/hashicorp/consul/command/acl/bindingrule/create > github.com/hashicorp/consul/command/acl/bindingrule/delete > github.com/hashicorp/consul/command/acl/bindingrule/list > github.com/hashicorp/consul/command/acl/bindingrule/read > github.com/hashicorp/consul/command/acl/bindingrule/update > github.com/hashicorp/consul/command/acl/bootstrap > github.com/hashicorp/consul/command/acl/policy > github.com/hashicorp/consul/command/acl/policy/create > github.com/hashicorp/consul/command/acl/policy/delete > github.com/hashicorp/consul/command/acl/policy/list > github.com/hashicorp/consul/command/acl/policy/read > github.com/hashicorp/consul/command/acl/policy/update > github.com/hashicorp/consul/command/acl/role > github.com/hashicorp/consul/command/acl/role/create > github.com/hashicorp/consul/command/acl/role/delete > github.com/hashicorp/consul/command/acl/role/list > github.com/hashicorp/consul/command/acl/role/read > github.com/hashicorp/consul/command/acl/role/update > github.com/hashicorp/consul/command/acl/rules > github.com/hashicorp/consul/command/acl/token > github.com/hashicorp/consul/command/acl/token/clone > github.com/hashicorp/consul/command/acl/token/create > github.com/hashicorp/consul/command/acl/token/delete > github.com/hashicorp/consul/command/acl/token/list > github.com/hashicorp/consul/command/acl/token/read > github.com/hashicorp/consul/command/acl/token/update > github.com/hashicorp/consul/command/agent > github.com/hashicorp/consul/command/catalog > github.com/hashicorp/consul/command/catalog/list/dc > github.com/hashicorp/consul/command/catalog/list/nodes > github.com/hashicorp/consul/command/catalog/list/services > github.com/hashicorp/consul/command/config > github.com/hashicorp/consul/command/config/delete > github.com/hashicorp/consul/command/config/list > github.com/hashicorp/consul/command/config/read > github.com/hashicorp/consul/command/config/write > github.com/hashicorp/consul/command/connect > github.com/hashicorp/consul/command/connect/ca > github.com/hashicorp/consul/command/connect/ca/get > github.com/hashicorp/consul/command/connect/ca/set > github.com/hashicorp/consul/command/connect/envoy >
Bug#998894: wlcs FTBFS with GTest 1.11
Source: wlcs Version: 1.2.1-1 Severity: serious Tags: ftbfs bookworm sid Forwarded: https://github.com/MirServer/wlcs/issues/205 https://tests.reproducible-builds.org/debian/rb-pkg/bookworm/amd64/wlcs.html ... /src/version_specifier.cpp.o -c /build/wlcs-1.2.1/src/version_specifier.cpp /build/wlcs-1.2.1/tests/pointer_constraints.cpp:45:5: error: reference to 'Pointer' is ambiguous 45 | Pointer cursor = the_server().create_pointer(); | ^~~ ... wlcs builds with the two commits from the issue linked above applied.
Processed: closing 984411
Processing commands for cont...@bugs.debian.org: > close 984411 1.3.0-1 Bug #984411 [src:wlcs] wlcs: ftbfs with GCC-11 Marked as fixed in versions wlcs/1.3.0-1. Bug #984411 [src:wlcs] wlcs: ftbfs with GCC-11 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 984411: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984411 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995999: FTBFS: FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks
Hi, On 09/11/2021 12:50, Christoph Berg wrote: Re: Martina Ferrari The GH issue you linked seems to be fixed upstream already with this patch: https://github.com/prometheus/prometheus/pull/8538/files Is anyone working on getting this uploaded? prometheus just got removed from testing. Yes, I have not had time to work on this lately, but we (the prometheus team) know about this and we hope to get it fixed asap. -- Martina Ferrari (Tina)
Processed: vdr-plugin-fritzbox: Please drop the stale build dependency on libcommoncpp2-dev
Processing control commands: > block 984096 by -1 Bug #984096 [src:libcommoncpp2] libcommoncpp2: ftbfs with GCC-11 984096 was not blocked by any bugs. 984096 was not blocking any bugs. Added blocking bug(s) of 984096: 998892 > block 998889 by -1 Bug #998889 [src:libcommoncpp2] libcommoncpp2: Remove in bookworm? 998889 was not blocked by any bugs. 998889 was not blocking any bugs. Added blocking bug(s) of 998889: 998892 -- 984096: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984096 998889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998889 998892: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998892 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998892: vdr-plugin-fritzbox: Please drop the stale build dependency on libcommoncpp2-dev
Source: vdr-plugin-fritzbox Version: 1.5.3-9 Severity: serious Tags: bookworm sid Control: block 984096 by -1 Control: block 998889 by -1 vdr-plugin-fritzbox is the only remaining package build depending on libcommoncpp2-dev, but HISTORY says: 2013-12-01: Version 1.5.3 - New dependency boost::asio, dropped dependency to commoncpp Please drop the stale build dependency on libcommoncpp2-dev. Severity of this bug is RC since libcommoncpp2 will likely soon be removed from testing.
Bug#997722: marked as done (pg-partman: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)
Your message dated Tue, 9 Nov 2021 16:02:05 +0100
with message-id
and subject line Re: Bug#997722: pg-partman: FTBFS: Error: debian/control needs
updating from debian/control.in. Run 'pg_buildext updatecontrol'.
has caused the Debian Bug report #997722,
regarding pg-partman: FTBFS: Error: debian/control needs updating from
debian/control.in. Run 'pg_buildext updatecontrol'.
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.)
--
997722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pg-partman
Version: 4.5.1-1
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
> rm -f src/pg_partman_bgw.so src/pg_partman_bgw.o \
> src/pg_partman_bgw.bc
> rm -rf sql/pg_partman--4.5.1.sql
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2021-02-04 15:59:40.0 +
> +++ debian/control.ffLqBs 2021-10-23 07:39:15.041961159 +
> @@ -14,10 +14,10 @@
> Vcs-Git: https://salsa.debian.org/postgresql/pg-partman.git
> Homepage: https://github.com/pgpartman/pg_partman
>
> -Package: postgresql-13-partman
> +Package: postgresql-14-partman
> Architecture: any
> Depends:
> - postgresql-13,
> + postgresql-14,
> python3,
> python3-psycopg2,
> ${misc:Depends},
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [debian/rules:11: clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pg-partman_4.5.1-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 4.6.0-1
Re: Lucas Nussbaum
> > Error: debian/control needs updating from debian/control.in. Run
> > 'pg_buildext updatecontrol'.
> > If you are seeing this message in a buildd log, a sourceful upload is
> > required.
Fixed in unstable.
Christoph--- End Message ---
Bug#997762: marked as done (pgtap: FTBFS: Error: debian/control needs updating from debian/control.in. Run 'pg_buildext updatecontrol'.)
Your message dated Tue, 9 Nov 2021 16:02:50 +0100
with message-id
and subject line Re: Bug#997762: pgtap: FTBFS: Error: debian/control needs
updating from debian/control.in. Run 'pg_buildext updatecontrol'.
has caused the Debian Bug report #997762,
regarding pgtap: FTBFS: Error: debian/control needs updating from
debian/control.in. Run 'pg_buildext updatecontrol'.
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.)
--
997762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997762
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pgtap
Version: 1.1.0-5
Severity: serious
Justification: FTBFS
Tags: bookworm sid ftbfs
User: lu...@debian.org
Usertags: ftbfs-20211023 ftbfs-bookworm
Hi,
During a rebuild of all packages in sid, your package failed to build
on amd64.
Relevant part (hopefully):
> make[1]: Entering directory '/<>'
>
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in
> scripts instead.
> GNUmake running against Postgres version 14.0, with pg_config located at
> /usr/bin
>
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in
> scripts instead.
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in
> scripts instead.
> /usr/bin/which: this version of `which' is deprecated; use `command -v' in
> scripts instead.
> rm -rf sql/pgtap--1.1.0.sql sql/pgtap-core--1.1.0.sql
> sql/pgtap-schema--1.1.0.sql sql/pgtap.sql sql/uninstall_pgtap.sql
> sql/pgtap-core.sql sql/pgtap-schema.sql doc/*.html test/sql/build.sql
> test/sql/create.sql test/sql/update.sql sql/pgtap--0.95.0--0.96.0.sql
> sql/pgtap--0.96.0--0.97.0.sql sql/pgtap--0.97.0--0.98.0.sql
> sql/pgtap--0.98.0--0.99.0.sql sql/pgtap--0.99.0--1.0.0.sql
> sql/pgtap--0.99.0--1.0.0.sql sql/pgtap--0.98.0--0.99.0.sql
> sql/pgtap--0.97.0--0.98.0.sql sql/pgtap--0.96.0--0.97.0.sql
> sql/pgtap--0.95.0--0.96.0.sql sql/pgtap-static.sql sql/pgtap-static.sql.tmp
> rm -rf results/ regression.diffs regression.out tmp_check/ tmp_check_iso/
> log/ output_iso/
> make[1]: Leaving directory '/<>'
>dh_clean
>pg_buildext checkcontrol
> --- debian/control2020-10-15 09:51:15.0 +
> +++ debian/control.bzTKbG 2021-10-23 07:36:40.512822253 +
> @@ -46,11 +46,11 @@
> .
> This package contains the documentation for pgTAP.
>
> -Package: postgresql-13-pgtap
> +Package: postgresql-14-pgtap
> Architecture: all
> Depends: ${shlibs:Depends}, ${misc:Depends},
> ${perl:Depends},
> -postgresql-13
> +postgresql-14
> Replaces: pgtap (<< 0.95)
> Breaks: pgtap (<< 0.95)
> Recommends: pgtap-doc,
> @@ -58,7 +58,7 @@
> libtest-harness-perl,
> libtap-harness-archive-perl
> Provides: postgresql-pgtap
> -Description: Unit testing framework extension for PostgreSQL 13
> +Description: Unit testing framework extension for PostgreSQL 14
> pgTAP is a suite of database functions that make it easy to write
> TAP-emitting unit tests in psql scripts suitable for harvesting,
> analysis, and reporting by a TAP harness, such as those used in Perl
> @@ -66,4 +66,4 @@
> .
> TAP is the Test Anything Protocol (http://testanything.org/).
> .
> - This package contains the extension for PostgreSQL 13.
> + This package contains the extension for PostgreSQL 14.
> Error: debian/control needs updating from debian/control.in. Run 'pg_buildext
> updatecontrol'.
> If you are seeing this message in a buildd log, a sourceful upload is
> required.
> make: *** [debian/rules:6: clean] Error 1
The full build log is available from:
http://qa-logs.debian.net/2021/10/23/pgtap_1.1.0-5_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
If you reassign this bug to another package, please marking it as 'affects'-ing
this package. See https://www.debian.org/Bugs/server-control#affects
If you fail to reproduce this, please provide a build log and diff it with mine
so that we can identify if something relevant changed in the meantime.
--- End Message ---
--- Begin Message ---
Version: 1.1.0-6
Re: Lucas Nussbaum
> > Error: debian/control needs updating from debian/control.in. Run
> > 'pg_buildext updatecontrol'.
> > If you are seeing this message in a buildd log, a sourceful upload is
> > required.
Fixed in unstable.
Christoph--- End Message ---
Bug#984268: ogmtools: diff for NMU version 1:1.5-4.1
Control: tags 984268 + patch Control: tags 984268 + pending Dear maintainer, I've prepared an NMU for ogmtools (versioned as 1:1.5-4.1) and uploaded it to DELAYED/15. Please feel free to tell me if I should cancel it. cu Adrian diff -Nru ogmtools-1.5/debian/changelog ogmtools-1.5/debian/changelog --- ogmtools-1.5/debian/changelog 2016-09-01 15:34:32.0 +0300 +++ ogmtools-1.5/debian/changelog 2021-11-09 11:16:08.0 +0200 @@ -1,3 +1,12 @@ +ogmtools (1:1.5-4.1) unstable; urgency=medium + + * Non-maintainer upload. + * Don't ignore provided CFLAGS/CXXFLAGS. + * Build with -std=gnu++14 to workaround FTBFS with gcc 11. +(Closes: #984268) + + -- Adrian Bunk Tue, 09 Nov 2021 11:16:08 +0200 + ogmtools (1:1.5-4) unstable; urgency=medium * debian: add source format to quilt diff -Nru ogmtools-1.5/debian/patches/0006-pass-CFLAGS.patch ogmtools-1.5/debian/patches/0006-pass-CFLAGS.patch --- ogmtools-1.5/debian/patches/0006-pass-CFLAGS.patch 1970-01-01 02:00:00.0 +0200 +++ ogmtools-1.5/debian/patches/0006-pass-CFLAGS.patch 2021-11-09 11:15:57.0 +0200 @@ -0,0 +1,15 @@ +Description: Don't ignore provided CFLAGS/CXXFLAGS +Author: Adrian Bunk + +--- ogmtools-1.5.orig/configure.in ogmtools-1.5/configure.in +@@ -31,7 +31,7 @@ fi + dnl Check for headers + AC_HEADER_STDC() + +-CFLAGS="-Wall -Wno-sign-compare $OGG_CFLAGS $VORBIS_CFLAGS $AVILIB_CFLAGS $DEBUG_CFLAGS $PROFILING_CFLAGS" +-CXXFLAGS="-Wall -Wno-sign-compare $OGG_CFLAGS $VORBIS_CFLAGS $AVILIB_CFLAGS $DEBUG_CFLAGS $PROFILING_CFLAGS" ++CFLAGS="-Wall -Wno-sign-compare $OGG_CFLAGS $VORBIS_CFLAGS $AVILIB_CFLAGS $DEBUG_CFLAGS $PROFILING_CFLAGS $CFLAGS" ++CXXFLAGS="-Wall -Wno-sign-compare $OGG_CFLAGS $VORBIS_CFLAGS $AVILIB_CFLAGS $DEBUG_CFLAGS $PROFILING_CFLAGS $CXXFLAGS" + + AC_OUTPUT(Makefile avilib/Makefile) diff -Nru ogmtools-1.5/debian/patches/series ogmtools-1.5/debian/patches/series --- ogmtools-1.5/debian/patches/series 2016-09-01 15:00:20.0 +0300 +++ ogmtools-1.5/debian/patches/series 2021-11-09 11:15:18.0 +0200 @@ -3,3 +3,4 @@ 0003-ogmmerge-spell-correct.patch 0004-ogminfo-timestamp-correction.patch 0005-ogminfo-increase-verbosity.patch +0006-pass-CFLAGS.patch diff -Nru ogmtools-1.5/debian/rules ogmtools-1.5/debian/rules --- ogmtools-1.5/debian/rules 2016-09-01 15:02:42.0 +0300 +++ ogmtools-1.5/debian/rules 2021-11-09 11:16:04.0 +0200 @@ -5,5 +5,7 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 +export DEB_CXXFLAGS_MAINT_APPEND += -std=gnu++14 + include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/class/autotools.mk
Processed: ogmtools: diff for NMU version 1:1.5-4.1
Processing control commands: > tags 984268 + patch Bug #984268 [src:ogmtools] ogmtools: ftbfs with GCC-11 Added tag(s) patch. > tags 984268 + pending Bug #984268 [src:ogmtools] ogmtools: ftbfs with GCC-11 Added tag(s) pending. -- 984268: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984268 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#984199: libpappsomspp: ftbfs with GCC-11
Control: tags -1 patch On Wed, Mar 03, 2021 at 04:14:50PM +, Matthias Klose wrote: > Package: src:libpappsomspp > Version: 0.8.15-1 > Severity: normal > Tags: sid bookworm > User: debian-...@lists.debian.org > Usertags: ftbfs-gcc-11 >... > /<>/src/pappsomspp/massspectrum/massspectrumid.h:54:38: error: > ‘numeric_limits’ is not a member of ‘std’ >54 | std::size_t m_spectrumIndex = > std::numeric_limits::max(); > | ^~ >... This is fixed in https://salsa.debian.org/debichem-team/libpappsomspp/-/merge_requests/1 cu Adrian
Processed: Re: Bug#984199: libpappsomspp: ftbfs with GCC-11
Processing control commands: > tags -1 patch Bug #984199 [src:libpappsomspp] libpappsomspp: ftbfs with GCC-11 Added tag(s) patch. -- 984199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998889: libcommoncpp2: Remove in bookworm?
Source: libcommoncpp2 Version: 1.8.1-10 Severity: serious Tags: bookworm sid src:ucommon is the successor of libcommoncpp2, and the only remaining build dependency on libcommoncpp2-dev in vdr-plugin-fritzbox is stale.
Bug#998886: marked as done (node-string-width,node-slice-ansi: both ship /usr/share/nodejs/is-fullwidth-code-point/*)
Your message dated Tue, 09 Nov 2021 14:36:46 + with message-id and subject line Bug#998886: fixed in node-string-width 4.2.3+~9.2.2-1 has caused the Debian Bug report #998886, regarding node-string-width,node-slice-ansi: both ship /usr/share/nodejs/is-fullwidth-code-point/* 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.) -- 998886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: node-string-width,node-slice-ansi Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 4.2.3+~3.0.0+~9.2.2-1 Control: found -1 5.0.0+~4.0.0-2 Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package node-slice-ansi. Preparing to unpack .../node-slice-ansi_5.0.0+~4.0.0-2_all.deb ... Unpacking node-slice-ansi (5.0.0+~4.0.0-2) ... dpkg: error processing archive /var/cache/apt/archives/node-slice-ansi_5.0.0+~4.0.0-2_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/is-fullwidth-code-point/index.d.ts', which is also in package node-string-width 4.2.3+~3.0.0+~9.2.2-1 Errors were encountered while processing: /var/cache/apt/archives/node-slice-ansi_5.0.0+~4.0.0-2_all.deb The following files are in conflict between the two packages: usr/share/nodejs/is-fullwidth-code-point/index.d.ts usr/share/nodejs/is-fullwidth-code-point/index.js usr/share/nodejs/is-fullwidth-code-point/package.json cheers, Andreas node-string-width=4.2.3+~3.0.0+~9.2.2-1_node-slice-ansi=5.0.0+~4.0.0-2.log.gz Description: application/gzip --- End Message --- --- Begin Message --- Source: node-string-width Source-Version: 4.2.3+~9.2.2-1 Done: Yadd We believe that the bug you reported is fixed in the latest version of node-string-width, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yadd (supplier of updated node-string-width 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, 09 Nov 2021 15:09:24 +0100 Source: node-string-width Architecture: source Version: 4.2.3+~9.2.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Javascript Maintainers Changed-By: Yadd Closes: 998886 Changes: node-string-width (4.2.3+~9.2.2-1) unstable; urgency=medium . * Team upload * Replace is-fullwidth-code-point component by dependency to node-is-fullwidth-code-point virtual package (Closes: #998886) and repack * Add fix for is-fullwidth-code-point ≥ 4 Checksums-Sha1: 1045e87435dc2644a9ded194a5639eaa84bda7ab 2578 node-string-width_4.2.3+~9.2.2-1.dsc 067cec5338838b7953ec0f233720fed9f1b11142 16352 node-string-width_4.2.3+~9.2.2.orig-emoji-regex.tar.gz 29d888bda54266462d007a295400554d0a426ab1 3830 node-string-width_4.2.3+~9.2.2.orig.tar.gz f12169facdf7a152c667958eab7ef07a791d3487 4292 node-string-width_4.2.3+~9.2.2-1.debian.tar.xz Checksums-Sha256: 8f480dbc80434d62b56e8cb4c580cf32a5c85552c9ccae08bef290a3b8c66ed0 2578 node-string-width_4.2.3+~9.2.2-1.dsc 1f8dde318be7e7e38398fe043f9cf8c4dbb3cad92973aea4a06fbff1e5f4f244 16352 node-string-width_4.2.3+~9.2.2.orig-emoji-regex.tar.gz 3cd0d3cb5f500ccffd73dd0c0779d86319b5aeb230adad0e106a41c40b572980 3830 node-string-width_4.2.3+~9.2.2.orig.tar.gz fcd94822fadad35b85b0c1791cef927d7377c2a7f58d5780c217a9c770130b8c 4292 node-string-width_4.2.3+~9.2.2-1.debian.tar.xz Files: 662445b7d3c3c899f22ce4840a07fe9c 2578 javascript optional node-string-width_4.2.3+~9.2.2-1.dsc 7d4ae4410d13ccbd12fd0488c4362032 16352 javascript optional node-string-width_4.2.3+~9.2.2.orig-emoji-regex.tar.gz c63b540d6d5b28fbab3f005ce3c30808 3830 javascript optional node-string-width_4.2.3+~9.2.2.orig.tar.gz 4abb3b7a694a15334d5ccd90e8920e19 4292 javascript optional node-string-width_4.2.3+~9.2.2-1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEAN/li4tVV3nRAF7J9tdMp8mZ7ukFAmGKgW0ACgkQ9tdMp8mZ 7unbkw/9HvWJHtqIbZKAj1cE7zVyobMAK1cOm9yMi4oEcfnMDFxvjQYXEFenxD7J
Bug#997070: marked as done (geoalchemy2: FTBFS: build hangs during connection to postgresql)
Your message dated Tue, 09 Nov 2021 14:34:28 + with message-id and subject line Bug#997070: fixed in geoalchemy2 0.9.4-2 has caused the Debian Bug report #997070, regarding geoalchemy2: FTBFS: build hangs during connection to postgresql 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.) -- 997070: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: geoalchemy2 Version: 0.9.4-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > File "/<>/debian/tests/setup-db-and-run-tests.py", line 124, > in main > configure_database(port) > File "/<>/debian/tests/setup-db-and-run-tests.py", line 79, in > configure_database > conn = psycopg2.connect(dbname='template1', **conn_params) > File "/usr/lib/python3/dist-packages/psycopg2/__init__.py", line 122, in > connect > conn = _connect(dsn, connection_factory=connection_factory, **kwasync) > psycopg2.OperationalError: connection to server at "localhost" (::1), port > 50037 failed: Connection refused > Is the server running on that host and accepting TCP/IP connections? > connection to server at "localhost" (127.0.0.1), port 50037 failed: > Connection refused > Is the server running on that host and accepting TCP/IP connections? > > make[1]: *** [debian/rules:15: override_dh_auto_test] Error 1 > make[1]: Leaving directory '/<>' > make: *** [debian/rules:5: binary] Error 2 > dpkg-buildpackage: error: debian/rules binary subprocess returned exit status > 2 > E: Build killed with signal TERM after 150 minutes of inactivity The full build log is available from: http://qa-logs.debian.net/2021/10/23/geoalchemy2_0.9.4-1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: geoalchemy2 Source-Version: 0.9.4-2 Done: Edward Betts We believe that the bug you reported is fixed in the latest version of geoalchemy2, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Edward Betts (supplier of updated geoalchemy2 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, 09 Nov 2021 14:07:38 + Source: geoalchemy2 Architecture: source Version: 0.9.4-2 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Edward Betts Closes: 995807 997070 Changes: geoalchemy2 (0.9.4-2) unstable; urgency=medium . [ Edward Betts ] * Fix failing tests. (Closes: #997070) * Update debian/watch to check github tags instead of releases. * Update Standards-Version . [ Bas Couwenberg ] * Use virtual postgis packages to be PG version independent. (Closes: #995807) Checksums-Sha1: 9df9e96925332e91aff96fa51a5f6939e38daf66 2461 geoalchemy2_0.9.4-2.dsc 0fc87f49100a13b1a46d6627c71369bae1013fe9 6684 geoalchemy2_0.9.4-2.debian.tar.xz 6ad5df2a76918636a036bdd0a87b2fe9c2007906 11795 geoalchemy2_0.9.4-2_source.buildinfo Checksums-Sha256: 2ff081c5642066be7818f3a3c711ef31b3b6c9bf09ebad802b2b5eaf4a13e8c1 2461 geoalchemy2_0.9.4-2.dsc 8409d31f7a709a5bc124298d4bce5bf87d098986a08c9045c9ec96886e26c4cb 6684 geoalchemy2_0.9.4-2.debian.tar.xz eb7082c66a8a65b576fabd7968c82d1a337373c9e3657c95fffa6f6d7dc385da 11795 geoalchemy2_0.9.4-2_source.buildinfo Files: 7b0c375c06783a8d627cec48ee5dedaa 2461 python optional geoalchemy2_0.9.4-2.dsc f7a39820c10c8a985a7179274fd93e3c 6684 python optional geoalchemy2_0.9.4-2.debian.tar.xz 19c69ed4bf99db6b8d656000d1f2d483 11795 python
Processed: transition: gdal
Processing control commands: > forwarded -1 https://release.debian.org/transitions/html/auto-gdal.html Bug #998887 [release.debian.org] transition: gdal Set Bug forwarded-to-address to 'https://release.debian.org/transitions/html/auto-gdal.html'. > block -1 by 998833 998827 984398 984401 984283 984284 Bug #998887 [release.debian.org] transition: gdal 998887 was not blocked by any bugs. 998887 was not blocking any bugs. Added blocking bug(s) of 998887: 984401, 984284, 998827, 984283, 998833, and 984398 -- 998887: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998887 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998886: node-string-width,node-slice-ansi: both ship /usr/share/nodejs/is-fullwidth-code-point/*
Package: node-string-width,node-slice-ansi Severity: serious User: debian...@lists.debian.org Usertags: piuparts Control: found -1 4.2.3+~3.0.0+~9.2.2-1 Control: found -1 5.0.0+~4.0.0-2 Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Selecting previously unselected package node-slice-ansi. Preparing to unpack .../node-slice-ansi_5.0.0+~4.0.0-2_all.deb ... Unpacking node-slice-ansi (5.0.0+~4.0.0-2) ... dpkg: error processing archive /var/cache/apt/archives/node-slice-ansi_5.0.0+~4.0.0-2_all.deb (--unpack): trying to overwrite '/usr/share/nodejs/is-fullwidth-code-point/index.d.ts', which is also in package node-string-width 4.2.3+~3.0.0+~9.2.2-1 Errors were encountered while processing: /var/cache/apt/archives/node-slice-ansi_5.0.0+~4.0.0-2_all.deb The following files are in conflict between the two packages: usr/share/nodejs/is-fullwidth-code-point/index.d.ts usr/share/nodejs/is-fullwidth-code-point/index.js usr/share/nodejs/is-fullwidth-code-point/package.json cheers, Andreas node-string-width=4.2.3+~3.0.0+~9.2.2-1_node-slice-ansi=5.0.0+~4.0.0-2.log.gz Description: application/gzip
Processed: node-string-width,node-slice-ansi: both ship /usr/share/nodejs/is-fullwidth-code-point/*
Processing control commands: > found -1 4.2.3+~3.0.0+~9.2.2-1 Bug #998886 [node-string-width,node-slice-ansi] node-string-width,node-slice-ansi: both ship /usr/share/nodejs/is-fullwidth-code-point/* There is no source info for the package 'node-slice-ansi' at version '4.2.3+~3.0.0+~9.2.2-1' with architecture '' Marked as found in versions node-string-width/4.2.3+~3.0.0+~9.2.2-1. > found -1 5.0.0+~4.0.0-2 Bug #998886 [node-string-width,node-slice-ansi] node-string-width,node-slice-ansi: both ship /usr/share/nodejs/is-fullwidth-code-point/* There is no source info for the package 'node-string-width' at version '5.0.0+~4.0.0-2' with architecture '' Marked as found in versions node-slice-ansi/5.0.0+~4.0.0-2. -- 998886: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998886 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#996139: marked as done (ruby-bluefeather: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError:)
Your message dated Tue, 09 Nov 2021 13:34:28 + with message-id and subject line Bug#996139: fixed in ruby-bluefeather 0.41-6 has caused the Debian Bug report #996139, regarding ruby-bluefeather: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError: to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 996139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: ruby-bluefeather Version: 0.41-5.1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: debian-r...@lists.debian.org Usertags: ruby3.0 Hi, We are about to enable building against ruby3.0 on unstable. During a test rebuild, ruby-bluefeather was found to fail to build in that situation. To reproduce this locally, you need to install ruby-all-dev from experimental on an unstable system or build chroot. Relevant part (hopefully): > NoMethodError: >undefined method `escape' for URI:Module > # ./lib/bluefeather.rb:2016:in `escape_to_header_id' > # ./lib/bluefeather.rb:1641:in `block in transform_headers' > # ./lib/bluefeather.rb:1588:in `gsub' > # ./lib/bluefeather.rb:1588:in `transform_headers' > # ./lib/bluefeather.rb:732:in `apply_block_transforms' > # ./lib/bluefeather.rb:546:in `parse_text' > # ./lib/bluefeather.rb:583:in `parse_text_with_render_state' > # ./spec/header-id.rb:42:in `block (2 levels) in ' > > Deprecation Warnings: > > > CUIMatcher::WriteToStderr implements a legacy RSpec matcher > protocol. For the current protocol you should expose the failure messages > via the `failure_message` and `failure_message_when_negated` methods. > (Used from /<>/spec/cui.rb:25:in `block (2 levels) in (required)>') > > > CUIMatcher::WriteToStderr implements a legacy RSpec matcher > protocol. For the current protocol you should expose the failure messages > via the `failure_message` and `failure_message_when_negated` methods. > (Used from /<>/spec/cui.rb:32:in `block (2 levels) in (required)>') > > > CUIMatcher::WriteToStderr implements a legacy RSpec matcher > protocol. For the current protocol you should expose the failure messages > via the `failure_message` and `failure_message_when_negated` methods. > (Used from /<>/spec/cui.rb:38:in `block (2 levels) in (required)>') > > Too many similar deprecation messages reported, disregarding further reports. > Pass `--deprecation-out` or set `config.deprecation_stream` to a file for > full output. > > > CUIMatcher::WriteToStdout implements a legacy RSpec matcher > protocol. For the current protocol you should expose the failure messages > via the `failure_message` and `failure_message_when_negated` methods. > (Used from /<>/spec/cui.rb:24:in `block (2 levels) in (required)>') > > > CUIMatcher::WriteToStdout implements a legacy RSpec matcher > protocol. For the current protocol you should expose the failure messages > via the `failure_message` and `failure_message_when_negated` methods. > (Used from /<>/spec/cui.rb:31:in `block (2 levels) in (required)>') > > > CUIMatcher::WriteToStdout implements a legacy RSpec matcher > protocol. For the current protocol you should expose the failure messages > via the `failure_message` and `failure_message_when_negated` methods. > (Used from /<>/spec/cui.rb:37:in `block (2 levels) in (required)>') > > Too many similar deprecation messages reported, disregarding further reports. > Pass `--deprecation-out` or set `config.deprecation_stream` to a file for > full output. > >
Bug#996139: marked as pending in ruby-bluefeather
Control: tag -1 pending Hello, Bug #996139 in ruby-bluefeather reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/ruby-bluefeather/-/commit/676d9f0c89c2c1a2a49c2a81504f65934bb72886 Add patch to fix FTBFS * d/patches/fix_uri_escape_deprecation.patch: Add patch. - Work around deprecation of URI.escape to fix FTBFS (closes: #996139). * d/patches/series: Enable new patch. (this message was generated automatically) -- Greetings https://bugs.debian.org/996139
Processed: Bug#996139 marked as pending in ruby-bluefeather
Processing control commands: > tag -1 pending Bug #996139 [src:ruby-bluefeather] ruby-bluefeather: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed: NoMethodError: Added tag(s) pending. -- 996139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#995999: FTBFS: FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks
Re: Martina Ferrari > The GH issue you linked seems to be fixed upstream already with this patch: > https://github.com/prometheus/prometheus/pull/8538/files Is anyone working on getting this uploaded? prometheus just got removed from testing. > On 09/10/2021 19:34, Shengjing Zhu wrote: > > Package: prometheus > > Version: 2.24.1+ds-1 > > Severity: serious > > X-Debbugs-Cc: z...@debian.org > > > > Hi, > > > > When rebuild packages, I find it FTBFS. > > > > === RUN TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks > > --- FAIL: TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks (0.05s) > > panic: runtime error: slice bounds out of range [:104326] with capacity > > 104293 [recovered] > > panic: runtime error: slice bounds out of range [:104326] with capacity > > 104293 > > > > goroutine 7 [running]: > > testing.tRunner.func1.2(0x60da60, 0xc0005f8030) > > /usr/lib/go-1.16/src/testing/testing.go:1143 +0x332 > > testing.tRunner.func1(0xc01e00) > > /usr/lib/go-1.16/src/testing/testing.go:1146 +0x4b6 > > panic(0x60da60, 0xc0005f8030) > > /usr/lib/go-1.16/src/runtime/panic.go:965 +0x1b9 > > github.com/prometheus/prometheus/tsdb/chunks.TestChunkDiskMapper_WriteChunk_Chunk_IterateChunks(0xc01e00) > > > > /build/1st/prometheus-2.24.1+ds/build/src/github.com/prometheus/prometheus/tsdb/chunks/head_chunks_test.go:122 > > +0xc9c > > testing.tRunner(0xc01e00, 0x637600) > > /usr/lib/go-1.16/src/testing/testing.go:1193 +0xef > > created by testing.(*T).Run > > /usr/lib/go-1.16/src/testing/testing.go:1238 +0x2b3 > > FAILgithub.com/prometheus/prometheus/tsdb/chunks0.116s > > > > > > It also FTBFS on tests.reproducible-builds.org, ci.debian.net > > > > https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/prometheus.html > > https://ci.debian.net/data/autopkgtest/unstable/amd64/p/prometheus/15535224/log.gz > > > > -- > Martina Ferrari (Tina) Christoph
Bug#516394: Investitsionnyy proyekt!
YA zainteresovan v finansirovanii vashego investitsionnogo proyekta za schet kredita ili partnerstva.
Bug#998822: marked as done (python3-satpy: ships .../dist-packages/benchmarks/*.py)
Your message dated Tue, 09 Nov 2021 12:25:04 + with message-id and subject line Bug#998822: fixed in satpy 0.31.0-2 has caused the Debian Bug report #998822, regarding python3-satpy: ships .../dist-packages/benchmarks/*.py 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.) -- 998822: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998822 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: python3-satpy Version: 0.31.0-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'stable'. It installed fine in 'stable', then the upgrade to 'sid' fails because it tries to overwrite other packages files. >From the attached log (scroll to the bottom...): Preparing to unpack .../python3-satpy_0.31.0-1_all.deb ... Unpacking python3-satpy (0.31.0-1) ... dpkg: error processing archive /var/cache/apt/archives/python3-satpy_0.31.0-1_all.deb (--unpack): trying to overwrite '/usr/lib/python3/dist-packages/benchmarks/__init__.py', which is also in package python3-skbio 0.5.6-4 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/python3-satpy_0.31.0-1_all.deb That is an overly generic python module name, either don't ship benchmarks/*.py at all (python3-skbio fixed it this way in sid, #991981) or move them to a namespaced location, e.g. benchmarks/satpy/*.py. cheers, Andreas --- End Message --- --- Begin Message --- Source: satpy Source-Version: 0.31.0-2 Done: Antonio Valentino We believe that the bug you reported is fixed in the latest version of satpy, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Antonio Valentino (supplier of updated satpy 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: Tue, 09 Nov 2021 11:08:48 + Source: satpy Architecture: source Version: 0.31.0-2 Distribution: unstable Urgency: medium Maintainer: Debian GIS Project Changed-By: Antonio Valentino Closes: 998822 Changes: satpy (0.31.0-2) unstable; urgency=medium . * debian/rules: - do not install python code that is not part of the satpy package (Closes: #998822). * debian/control: - do not use undefined substitution variables. * debian/patches: - improve 0002-No-setuptools-scm.patch to properly set the version in the setup.py script. Checksums-Sha1: 8e61ac5c8b5556eff2c5fcd5a9d189cd4f319833 2991 satpy_0.31.0-2.dsc 5eb45ea4e60e36a5981a707efc0b53f571aefc65 10028 satpy_0.31.0-2.debian.tar.xz d319f7ad5f17b5b490182e1e869a01e4a37ebb3f 17861 satpy_0.31.0-2_amd64.buildinfo Checksums-Sha256: 3897990a3f6d848dcac4a59ab6e2a0969b634b10f0dc4ecc7ee8ebb8200d278e 2991 satpy_0.31.0-2.dsc bf2685f0f5e9c43858c98093856893b404b0ecd66e8cc08da2c97c71c602effc 10028 satpy_0.31.0-2.debian.tar.xz 21b5fd281f32cc093eaa4acd610890b2f9aa70f3da8aa1c64c05c08cb4a53716 17861 satpy_0.31.0-2_amd64.buildinfo Files: 2c3a605d0284b779931f35fa44c122f3 2991 python optional satpy_0.31.0-2.dsc 84b98e310a33c61db58e3c171dc7a7d6 10028 python optional satpy_0.31.0-2.debian.tar.xz e9645c0ff224728b042721a0e064be24 17861 python optional satpy_0.31.0-2_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJRBAEBCAA7FiEEO3DyCaX/1okDxHLF6/SKslePmBIFAmGKYi8dHGFudG9uaW8u dmFsZW50aW5vQHRpc2NhbGkuaXQACgkQ6/SKslePmBJnVQ/8DDzUvyZ/Fv6/Ftr6 tVr0flBSIZX9/yiwhPtMtfkJWmQG9ceWiqGDO+R+y8f7wQ/tQTnJ5pDYo+kdfD9i zQ13jOtjaoITcxOAF2UHryX2rtq1zs4/ZM4mU4Dx4YGw3zgDtOPaZ3M/O6BF+26l m7EIByDcz7BSRVdSdKq+3H719kv5rsimVa3EOXbqyVLsupwfsua6arWxc2td6Ibk aFGcgzvFhzbR9qUuQh3ho5Xml8pOWF71RJsguW/j3s0RQgqO72VptRxELLAEJXy1 Z4NTB/zm2yJf/odxfT7Fu6ZOr7z4F2F+Dux7T4IQhTNwmCrAKdHi77w9fwqwruxe XSltwtpS+UuBQ8z2j9e2cA6cmd1nJbBKuXChkIuT5DHoQiuGEhET07ZjRPMS9DAO k03yZdos7eJVOs1YOqlYuWJaZCYFRZEqFBZoEp+89/vbnxvT29ReBPVe+4LEEaQi zktDq0Ow7kOJwLINhG7euqa4GQI9BtzhLiA2Bp++zfqUYir4p78U4Y9Vf0mLD62A Tx2Zlp3VkhPS9yAjbEsM3ceX3hkVMU/CIoQuT0nw48R6PA70n4Ewl8o8Q/aWVV3I PW6pxZaVyxD3dQlbKTclpKxoQ5eZKCfJbLWIvHdzftBGVMRR4uh0HFphU1PYmWHY
Bug#997942: tomboy-ng: FTBFS with fpc 3.2.2
No, sorry, I cannot do a sensible test of my app using FPC and/or Lazarus from sid. I can install FPC3.2.2 from Sid by using priorities. But the Lazarus in Sid is non functional, blocked, because of an issue about "diversions". So, falling back to using Testing's Lazarus, I find it insists on installing FPC3.2.0. It should not, Lazarus 2.0.10 is fine with FPC3.2.2, I just tested in on my system. So, that leaves me with a partially overwritten FPC3.2.2. Yes it built and makes a nice SRC package but I cannot be sure it has not used FPC3.2.0 components so the test is not absolute. So, I will have to wait until the Lazarus on Sid issue is resolved. And Lazarus 2.2.0 cannot be far way. It has a fix (I wrote) for the problem affecting Gnome Desktops caused when Debian dropped libappindicator3 in favour of libayatana-appindicator3 apparently without considering that they have different names. Davo On Mon, 2021-11-08 at 13:03 +0200, Graham Inggs wrote: > Hi David > > Apologies for the delayed response. > > On Sat, 30 Oct 2021 at 06:57, David Bannon > wrote: > > Thanks Graham. I noticed the same problem myself a few days ago. > > Its a > > very simple fix but as I am very close to releasing a new version > > anyway, maybe we can wait until them ? > > Sure, there's no reason to rush a fix now. Replying to this bug will > delay the pending autoremoval. > > On Sun, 7 Nov 2021 at 02:41, David Bannon > wrote: > > However, Testing still has the 'older' compiler and it builds fine > > with > > that. How do I test my build against tools only available in sid ? > > Development of Debian takes place in unstable (aka sid), and if you > uploaded a new version of tomboy-ng to the archive, it would be built > against all of the packages in unstable. It is possible to install > individual packages from unstable on a testing system [1]. Take care > to set priorities [2] so that you don't end up with all of the > packages from unstable, unless you like living on the edge. > > I suggest subscribing to the Debian Pascal Packaging Team's mailing > list [3], to keep up to date with FPC and Lazarus packaging > developments. You are also welcome to join the team and you will > have > no shortage of sponsors for your uploads. > > Regards > Graham > > > [1] https://wiki.debian.org/DebianUnstable > [2] https://wiki.debian.org/AptConfiguration > [3] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-pascal-devel
Bug#997284: marked as done (pvm: FTBFS: ddpro.c:398:10: fatal error: rpc/types.h: No such file or directory)
Your message dated Tue, 09 Nov 2021 11:56:05 + with message-id and subject line Bug#997284: fixed in pvm 3.4.6-3.1 has caused the Debian Bug report #997284, regarding pvm: FTBFS: ddpro.c:398:10: fatal error: rpc/types.h: No such file or directory to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 997284: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997284 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: pvm Version: 3.4.6-3 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -DSYSVSIGNAL -DNOWAIT3 -DRSHCOMMAND=\"/usr/bin/rsh\" -DNEEDENDIAN > -DFDSETNOTSTRUCT -DHASERRORVARS -DHASSTDLIB -DCTIMEISTIMET -DSYSERRISCONST > -DNOTMPNAM -DSYSVSTR -DUSESTRERROR -g -O2 > -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 > -DRSHCOMMAND=\"/usr/lib/pvm3/bin/rsh\" -DPVMDPATH=\"pvmd\" > -DPVMDFILE=\"/usr/bin/pvmd\" -DPVM_DEFAULT_ROOT=\"/usr/lib/pvm3\" > -DOVERLOADHOST -Wl,-z,relro -Wl,-z,now -fPIC -DCLUMP_ALLOC -DSTATISTICS > -DTIMESTAMPLOG -DSANITY -I/<>/include -DARCHCLASS=\"LINUX64\" > -DIMA_LINUX64 -c /<>/src/ddpro.c > : warning: "RSHCOMMAND" redefined > : note: this is the location of the previous definition > /<>/src/ddpro.c:398:10: fatal error: rpc/types.h: No such file > or directory > 398 | #include > | ^ > compilation terminated. > make[3]: *** [/<>/src/Makefile.aimk:375: ddpro.o] Error 1 The full build log is available from: http://qa-logs.debian.net/2021/10/23/pvm_3.4.6-3_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: pvm Source-Version: 3.4.6-3.1 Done: Camm Maguire We believe that the bug you reported is fixed in the latest version of pvm, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Camm Maguire (supplier of updated pvm 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: Tue, 09 Nov 2021 11:26:42 + Source: pvm Architecture: source Version: 3.4.6-3.1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Camm Maguire Closes: 997284 Changes: pvm (3.4.6-3.1) unstable; urgency=medium . * Non-maintainer upload * Bug fix: "FTBFS: ddpro.c:398:10: fatal error: rpc/types.h: No such file or directory", thanks to Lucas Nussbaum (Closes: #997284). * Add -I/usr/include/tirpc/ to CFLAGS in debian/rules * Add -Wl,--start-group -ltirpc to LDFLAGS in debian/rules * Add libtirpc-dev to build depends Checksums-Sha1: 143213c1ad9da01876b5c600317bdb03e6743acf 2017 pvm_3.4.6-3.1.dsc 06ed56366554e6c394ba73e712a5308b822d442a 24924 pvm_3.4.6-3.1.debian.tar.xz e0501dd16b7f2fbacae97d96265600c9d8e29275 6586 pvm_3.4.6-3.1_source.buildinfo Checksums-Sha256: 2b9dc2154ed85a7f5865b903a279329f470830efe9dc4e261318bb4f44b2fe13 2017 pvm_3.4.6-3.1.dsc 4354211f61e5e538d89a3a80f10bde2c89c4019355f413beb9c1e4ddd0e74893 24924 pvm_3.4.6-3.1.debian.tar.xz f9aa767a81a5d49550f5bd7e3b4df86609506f89eb3d3fc0ea94e41d6ec16eb4 6586 pvm_3.4.6-3.1_source.buildinfo Files: df423d8a01dac663cb02ee62b3b8a06c 2017 devel optional pvm_3.4.6-3.1.dsc 6223bb804ffdda3b863b9e8957a225b2 24924 devel optional pvm_3.4.6-3.1.debian.tar.xz bc8fac9345e8bafe388089ccdacf8e5c 6586 devel optional pvm_3.4.6-3.1_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEE/iFPNjaXdzJC6BbsuEXOUQ+bcU0FAmGKWysACgkQuEXOUQ+b cU2AUQ//R91P823RrkyTZGZaRujWx9HaDMyrIniVByy4SgPbVB9pvp0W92nOf+3E
Bug#997727: marked as done (rdma-core: FTBFS: dh_installsystemd: error: Package 'ibacm' does not install unit 'ibacm.service'.)
Your message dated Tue, 09 Nov 2021 10:34:27 + with message-id and subject line Bug#997727: fixed in rdma-core 36.0-2 has caused the Debian Bug report #997727, regarding rdma-core: FTBFS: dh_installsystemd: error: Package 'ibacm' does not install unit 'ibacm.service'. 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.) -- 997727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997727 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rdma-core Version: 36.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20211023 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_installinit -prdma-core --onlyscripts --name=iwpmd > dh_installinit --remaining-packages > make[1]: Leaving directory '/<>' >debian/rules override_dh_installsystemd > make[1]: Entering directory '/<>' > dh_installsystemd -pibacm --no-start ibacm.service > dh_installsystemd: error: Package 'ibacm' does not install unit > 'ibacm.service'. > make[1]: *** [debian/rules:92: override_dh_installsystemd] Error 25 The full build log is available from: http://qa-logs.debian.net/2021/10/23/rdma-core_36.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! If you reassign this bug to another package, please marking it as 'affects'-ing this package. See https://www.debian.org/Bugs/server-control#affects If you fail to reproduce this, please provide a build log and diff it with mine so that we can identify if something relevant changed in the meantime. --- End Message --- --- Begin Message --- Source: rdma-core Source-Version: 36.0-2 Done: Benjamin Drung We believe that the bug you reported is fixed in the latest version of rdma-core, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 997...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Benjamin Drung (supplier of updated rdma-core 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, 09 Nov 2021 11:13:56 +0100 Source: rdma-core Built-For-Profiles: noudeb Architecture: source Version: 36.0-2 Distribution: unstable Urgency: medium Maintainer: Benjamin Drung Changed-By: Benjamin Drung Closes: 997727 Changes: rdma-core (36.0-2) unstable; urgency=medium . * Revert installing systemd services in /usr/lib/systemd/system. See #994388 for more details. (Closes: #997727) Checksums-Sha1: 9098dd436b3fff7162b63a004566b907216c5d0e 3195 rdma-core_36.0-2.dsc f521e1dfddea46256697253534f33be7598402a2 22836 rdma-core_36.0-2.debian.tar.xz 1aaa223cb6c88d51209e1fd6a9fcc2089d1dc01b 9983 rdma-core_36.0-2_source.buildinfo Checksums-Sha256: 38d4cf5c860dcf89726d40c7d1f1faf825ea54886ef50f6245125fb2e5620bb0 3195 rdma-core_36.0-2.dsc 54611fecc26cf50a9e5c1b0e4deb7ca8c35ad4bc2acc8dd4b8c02becd01d0f26 22836 rdma-core_36.0-2.debian.tar.xz 59abef84df1cd2cf09910a278d639932b322ce53d62ffa8690b96d582683b5ae 9983 rdma-core_36.0-2_source.buildinfo Files: c8fe5b2d7a3f8d81aaa60ee1477a7c86 3195 net optional rdma-core_36.0-2.dsc 9ecbb47a01c5f04924db3bb206e5ddef 22836 net optional rdma-core_36.0-2.debian.tar.xz 4cad664d63ffe7a4db2aff0e08bffd74 9983 net optional rdma-core_36.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEE5/q3CzlQJ15towl13YzVpd6MfnoFAmGKSq0ACgkQ3YzVpd6M fno0mA/9FUjYWCTuYlWb0r3u1nWkpunr7HggrzSg/Pq5JWLUmxcvA87S3RU4quX8 zcv1G+qlL71KS5zzMmPTlbGk+W32bvE1twnQKYT/8GxcbGh/4DmMmMH4ViLaLtK1 CSlj82CRwI7wj3Ga4cvN11UxCQ/Vb+7ecS47FLckIhADDLxX0FZ/yDJfs643F70s MSNWbMINCfJtwvGibKX6Odh+z4Cr9kL5mn3XFU/7yIwy9KMgfquWqKjQa+/4OFhT Ox6sNPsZovFALzqLjNB7XGA9Xx8mBEtwVyH9OOh22n/6Rcdl2F62iZC0M9CkB7hI fGSA8inchQGe8gPrGh0t48LifRBEVVy4rToPO+FW7kqnaWvbhjI/2bfld3S70TjQ JgDkEztHPBajnmAKW12MSzgIRWPMj3hrKUyC/otWLfkqcbJcbORB12XXwP1Pi2G3 s/RmC0mMvCjotDtKnXxEygRn6j4bfoq2p29LPOfQdOzycqpR6KVxLBivupo8Iah+ zF8Jw+FKDijbhGTQY6EbMPRnIVZFxmMkJzOE6WlmdmoDEbZKt8eiSSrAolvsP652
Processed: your mail
Processing commands for cont...@bugs.debian.org: > forcemerge 980421 997409 Bug #980421 [src:libjpeg] libjpeg FTCBFS: fails to compute reasonable compiler identification from cross tools Bug #997409 [src:libjpeg] libjpeg: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 Severity set to 'normal' from 'serious' Marked as found in versions libjpeg/0.0~git20200925.f145908-1. Added tag(s) patch and upstream. Bug #980421 [src:libjpeg] libjpeg FTCBFS: fails to compute reasonable compiler identification from cross tools Marked as found in versions libjpeg/0.0~git20210129.91985dc-1. Added tag(s) sid, bookworm, and ftbfs. Merged 980421 997409 > End of message, stopping processing here. Please contact me if you need assistance. -- 980421: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=980421 997409: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=997409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#998317: marked as done (PostgreSQL 14 transition)
Your message dated Tue, 09 Nov 2021 09:18:33 + with message-id and subject line Bug#998317: fixed in gavodachs 2.3+dfsg-3.1 has caused the Debian Bug report #998317, regarding PostgreSQL 14 transition 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.) -- 998317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998317 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gavodachs2-server Version: 2.3+dfsg-3 Severity: serious gavodachs2-server currently depends on the postgresql-13 versions of -pgsphere and -q3c, and is blocking the transition to postgresql-14: Package: gavodachs2-server Source: gavodachs Version: 2.3+dfsg-3 Depends: adduser, members, postgresql-13-pgsphere, postgresql-13-q3c, python3-gavo (= 2.3+dfsg-3) Both packages are providing virtual packages that would make the need to update the dependency every year obsolete, so I would suggest switching that to: Depends: postgresql-pgsphere, postgresql-q3c Alternatively, switch it to postgresql-14-pgsphere, postgresql-14-q3c (pgsphere itself still has problems with PG14 to be resolved, but moving to the version-less dependency would already work now.) Christoph --- End Message --- --- Begin Message --- Source: gavodachs Source-Version: 2.3+dfsg-3.1 Done: Christoph Berg We believe that the bug you reported is fixed in the latest version of gavodachs, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 998...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christoph Berg (supplier of updated gavodachs 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: Mon, 08 Nov 2021 13:18:35 +0100 Source: gavodachs Architecture: source Version: 2.3+dfsg-3.1 Distribution: unstable Urgency: medium Maintainer: Debian Astronomy Team Changed-By: Christoph Berg Closes: 998317 Changes: gavodachs (2.3+dfsg-3.1) unstable; urgency=medium . * Non-maintainer upload. * gavodachs2-server: Depend on postgresql-pgsphere, postgresql-q3c without a specific PostgreSQL version. (Closes: #998317) Checksums-Sha1: eb55ab48708e96da3fe322f681cb6d5b4cb83726 2408 gavodachs_2.3+dfsg-3.1.dsc 763cf18157420446dc00b62778f8ad6246a02190 63248 gavodachs_2.3+dfsg-3.1.debian.tar.xz Checksums-Sha256: 15866d326771eb01b2d0db2df4232f9d3bfff21277745d77c7b7735a749c56d9 2408 gavodachs_2.3+dfsg-3.1.dsc 96f978cf0cceb9352ddd13bb4ac278bcc9f8dffc4600ee7549cabca7faaed938 63248 gavodachs_2.3+dfsg-3.1.debian.tar.xz Files: e3a49794b1b18763ddc188164be17410 2408 python optional gavodachs_2.3+dfsg-3.1.dsc fb4fd86d2fa3254fae1f244106952505 63248 python optional gavodachs_2.3+dfsg-3.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAmGJFzgACgkQTFprqxLS p64HMw/+MZ8nO2dbsp+dmNbOF4EAGExfgynxrYhDg/+IIr1/Y0BaHNxux4qMoeTI /k8Cs26FtKCHsvCOyym8o9ZgKNhYx52wQHA+UrFsKHK3MDMbzocH1ACzLo/W9A1C 3+toDoFULH3obRMUS5nNkquueQMy1NMmtiLEtj1dD50js3cEHOnsNdYAVYa3a5OK zMcFyMSi8RckL9Cu9dK43v6dsKzMGxHhY3URwH1sRun1YesnW25oadmzrz5ScXHJ y09Pkl6R1vSo802tJt59ifH4xxt8lZwPG4cy8IJWj0sti6yhoUeZR+28gDpjX3dD m8WCUbW5YFuhBvgONa5taFKESlGy2i9q7JjZTrX5ls1++C4KUU0aPbB1P5DHw8i/ 5Y9/YwWQeTNVJ6jHddRM4cRjVsTPty561Vr8CJkENyvxuTV8+zysfu6tZymlVAZW QnQsE3T0cliQhEMYJYS9Y7mOLt/0yURFY10jZrGZlYLQQ/8xIUd5esXnLyPPoiqG hUI+vZDQMgvTY4mOgXxAuYOawqtSvESDpLxm6ODSWqbCmZqPnBXDSImP4O36lwOK BC2dCxpduaKuTRIQ5xqyde5+AZoW6bZdSHGf8TWnH3VwX8FedYQ6Vl0swBMG9h1h HZj0z8W3AURRNwB5qg4JlEbcx9zANB9Fc0D2kEpFu+eBUkfkxgg= =e0zd -END PGP SIGNATURE End Message ---
Bug#998575: [Pkg-freeipa-devel] Bug#998575: bind-dyndb-ldap: FTBFS: build-dependency not installable: bind9-libs (= 1:9.16.21-1)
Hi Timo, > On 5. 11. 2021, at 8:09, Timo Aaltonen wrote: > > On 5.11.2021 1.37, peter green wrote: >> > bind9-dev : Depends: bind9-libs (= 1:9.16.21-1) but it is not going to be >> > installed >> It looks like bind8 no longer builds the bind9-dev package. It's still >> present in >> unstable as a cruft package but is uninstallable due to version constraints, >> it's >> completely gone from testing. > > I don't know what's going on here, but at least the current bind9 packaging > is not available on salsa, debian/main is on 9.16.22-1 and according to > d/changelog it was uploaded to unstable on the same day as 9.17.19-1... > (which has now migrated to testing already) The 9.17 packaging is available from the isc/9.17 branch which should be up to date. > The new bind9 doesn't mention dropping bind9-dev on d/changelog. Ondrej, why > was it dropped? We need to figure out what to do with bind-dyndb-ldap in the future. The BIND 9 libraries are not meant for public consumption since 9.14.0. The upstream (which is incidentally also me) has declare the libraries private and the symbols could change even between patch releases. There’s absolutely no guarantee about symbol stability even on stable branch. Unfortunately, bind-dyndb-ldap is licensed under GPL-2.0 which makes it impossible to include it directly in the src:bind9 package. I see no easy way from this. I will reintroduce the bind9-dev package, but this will make the bind-dyndb-ldap package to regularly FTBFS anyway and it needs to be fixed before the next stable release. Ondrej
Processed: Re: Bug#998867: debootstrap: --no-merged-usr became a no-op
Processing control commands: > severity -1 grave Bug #998867 [debootstrap] debootstrap: --no-merged-usr became a no-op Severity set to 'grave' from 'important' -- 998867: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=998867 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
