Bug#1038909: marked as done (dd-opentracing-cpp: build-depends on deprecated libcurl4-nss-dev, will be dropped in August 2023)
Your message dated Mon, 14 Aug 2023 05:33:44 + with message-id and subject line Bug#1038909: fixed in dd-opentracing-cpp 1.3.7-1 has caused the Debian Bug report #1038909, regarding dd-opentracing-cpp: build-depends on deprecated libcurl4-nss-dev, will be dropped in August 2023 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.) -- 1038909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038909 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: dd-opentracing-cpp Tags: trixie sid User: c...@packages.debian.org Usertags: curl-nss-deprecation X-Debbugs-Cc: samuel...@debian.org, sergi...@debian.org Control: block 1038907 by -1 Hello, This package build-depends on the NSS variant of libcurl "libcurl4-nss-dev". Curl's upstream announced support for NSS is going to be dropped in August 2023: https://curl.se/dev/deprecate.html#nss Please make sure to switch your build-dependency to something else before the due date. You might try switching to "libcurl4-openssl-dev" and in the big majority of the cases this won't cause any issues. Thank you, -- Samuel Henrique --- End Message --- --- Begin Message --- Source: dd-opentracing-cpp Source-Version: 1.3.7-1 Done: Stephen Gelman We believe that the bug you reported is fixed in the latest version of dd-opentracing-cpp, 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 1038...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stephen Gelman (supplier of updated dd-opentracing-cpp 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, 13 Aug 2023 23:48:41 -0500 Source: dd-opentracing-cpp Architecture: source Version: 1.3.7-1 Distribution: unstable Urgency: medium Maintainer: Stephen Gelman Changed-By: Stephen Gelman Closes: 1038909 Changes: dd-opentracing-cpp (1.3.7-1) unstable; urgency=medium . * New upstream release * Replace libcurl4-nss-dev dep with libcurl4-openssl-dev (Closes: #1038909) * Update standards version to 4.6.2 Checksums-Sha1: 7edbd5a3d05527964d2287598e51bad04092032d 2126 dd-opentracing-cpp_1.3.7-1.dsc 5775402ffc460079c950e7bfd1e743463aed16fe 816130 dd-opentracing-cpp_1.3.7.orig.tar.gz d346c97f610ca67ae2f7ec95577a29e0ecb9ee01 4196 dd-opentracing-cpp_1.3.7-1.debian.tar.xz ce2304942c4784d7b06206d0fdfd6a5c2c23177b 8072 dd-opentracing-cpp_1.3.7-1_amd64.buildinfo Checksums-Sha256: 847184db59a387dec6fd911ddce725f2afa8dc82c4f27cffd97ff25dd6558b6b 2126 dd-opentracing-cpp_1.3.7-1.dsc 8d39c6b23f941a2d11571daaccc04e69539a3fcbcc50a631837560d5861a7b96 816130 dd-opentracing-cpp_1.3.7.orig.tar.gz 36500f7c789d995cf4f7b248ef5992142226af643ba0671231e2d98a9ae8d231 4196 dd-opentracing-cpp_1.3.7-1.debian.tar.xz 277633a1b16b3768ac02c8769ac9c03d726c7a590f3990bc3b7bdb261319d050 8072 dd-opentracing-cpp_1.3.7-1_amd64.buildinfo Files: fa8ce292c8862aa9974aaaf8b8b564b5 2126 libs optional dd-opentracing-cpp_1.3.7-1.dsc af398f9e7995121de5f56cb8a8690536 816130 libs optional dd-opentracing-cpp_1.3.7.orig.tar.gz 1a0182a93989e8c4ec10153fe832322f 4196 libs optional dd-opentracing-cpp_1.3.7-1.debian.tar.xz 2f4ac260847d88424b0724b0b3b12523 8072 libs optional dd-opentracing-cpp_1.3.7-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJGBAEBCgAwFiEEPwDop1BN06KlsbfijqM4hED8f1wFAmTZtZESHHNzZ2VsbUBk ZWJpYW4ub3JnAAoJEI6jOIRA/H9cyksQAKklZ0LulehpNUxasIDWpv10ub9bCQR+ FpwipSywezjez6XsCSMIkrIX0THA11j2d6Sn3LdR9Ko4bx7ZTEpUaYFixNb9RdYZ tttBDGdIbJUQqNiaW7jbd+kbgEMdnHIl+tbuEP7XyyaDVBvi+XtFnijrfIKClEb3 JmNw/wPVe3FU2t2fSR4Rkp950JDboqswz75WpwXLeA/SbE+UWFXAw7i4S0x933+2 znQlfjTLKQ8G2KE9ZxOSkE/g+X5IZml7SjLA0XQgIMF/3sdiYNxlEMt8HVYlOjXL i8lJZP8wdkh7jMrBdREZr6UG7j3+PJK3tcEqwmBd+8S3IOB1M8RsamLXdPJPPVxC RLZbwNS/tN00d49B2AUdnw/uGZ2HP9P/a1ZeJmx0bUJNYDnW4F2PZ66jvUbDLOG9 pJBdHMzQ8R+auA4K3AuQ85myberY9WpfPlQrJ90MXrnQhfXLz4lBnhv9gcK5mgkC ifDPZqmugrZ5X4uxrsP8fGUa1RdVRlpt0m70oI2eC11udr6lIpvTMVcs2kEO5A9V hVe03QS9dnDlAb9Wlw3Veni19coQJ7//S7C9QZSlPmdOuv8lETB4vOxSfhbIiaX1 pFlsBXD1XGIqxcVRbFx7P3xzy6fKvg1Vsveasa34RMMael+7ABVZSnGSztdT1Hvt nZ6MIrnfX8hc =8FEl -END PGP SIGNATURE End Message ---
Bug#1025011: Release request filed
For the record, I have filed a request with the Release Team now to get the green light to upload Bullseye packages. See: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049325
Processed: tagging 1037841
Processing commands for cont...@bugs.debian.org: > tags 1037841 + patch Bug #1037841 [src:restinio] restinio: ftbfs with GCC-13 Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037841: restinio: ftbfs with GCC-13
Dear Matthias, Felix, Please find attached a patch that should fix this. Would one of you please upload it as well? Thanks, -a Description: Fix FTBFS with GCC-13 For more details, see: https://gcc.gnu.org/gcc-13/porting_to.html#header-dep-changes Author: Amin Bandali diff --git a/dev/test/router/cmp_router_bench/route_parser.hpp b/dev/test/router/cmp_router_bench/route_parser.hpp index cfbe981a..4d874cc7 100644 --- a/dev/test/router/cmp_router_bench/route_parser.hpp +++ b/dev/test/router/cmp_router_bench/route_parser.hpp @@ -1,5 +1,6 @@ #pragma once +#include #include enum class entity_type_t : std::uint8_t
Bug#1042889: marked as done (vm: autopkgtest fails against Emacs 29.1)
Your message dated Mon, 14 Aug 2023 01:18:45 + with message-id and subject line Bug#1042889: fixed in vm 8.2.0b-11 has caused the Debian Bug report #1042889, regarding vm: autopkgtest fails against Emacs 29.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.) -- 1042889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: vm Version: 8.2.0b-10 Severity: serious Dear maintainer, vm's autopkgtest fails with Emacs 29.1, which latter is now in sid. https://ci.debian.net/packages/v/vm/testing/amd64/ Thanks. -- Sean Whitton signature.asc Description: PGP signature --- End Message --- --- Begin Message --- Source: vm Source-Version: 8.2.0b-11 Done: Ian Jackson We believe that the bug you reported is fixed in the latest version of vm, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ian Jackson (supplier of updated vm 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, 14 Aug 2023 01:58:56 +0100 Source: vm Architecture: source Version: 8.2.0b-11 Distribution: unstable Urgency: medium Maintainer: Ian Jackson Changed-By: Ian Jackson Closes: 1042889 Changes: vm (8.2.0b-11) unstable; urgency=medium . * Expand byte-compilation workaround to new variable name. (Emacs 29 renamed the variable.) Closes: #1042889. * byte-compilation disablement: Fix a minor string escaping mistake. * Build-Depends: Allow emacs (nox) too Checksums-Sha1: 061efb873f13fcf499fe056412987985b7649704 1633 vm_8.2.0b-11.dsc d163867b6f98beb7e4d68ce9663b9dc94cf00989 106084 vm_8.2.0b-11.diff.gz Checksums-Sha256: 826b36c331cdd330c3e86ff13212b5d709a52cd7a72fe9c836bcdfbc919cf15a 1633 vm_8.2.0b-11.dsc 726c205fdcc26a702fa265f2361855a3a8cc7c9b636112b97e203aa4be1f621d 106084 vm_8.2.0b-11.diff.gz Files: 603ed7105c859de9dcc1f8febbdb8f12 1633 mail optional vm_8.2.0b-11.dsc 1faff08af0a9e2a282980620b2f911eb 106084 mail optional vm_8.2.0b-11.diff.gz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEVZrkbC1rbTJl58uh4+M5I0i1DTkFAmTZfYkACgkQ4+M5I0i1 DTlDAQf+Lf/jedIxIl4XTjS5SlMZP7obY8+I5zS7hNnbcJKtUWNOO8uUI+EttB3r pYK4swg2GgNRqPR7FxJPaxVZW/oEW8dBa3qZ4VQToMH/UD5WaW6fBEoRLI0Mejg2 W3kLfVaQAtPbA1yn3uGGl3S04cfOWfv5S+X8vwjlOzM/Am9qHqQMYg6lyfQ5rUnq Kgca6YjdagPMyXYVM4jPBJOCzK433lPoXiYD9Av6kJbpIblD9HbZWSRweZR0 Y+PvCJ1itne97s3XuEx2iv1ZuUUL249aMqkQ6VjFrPP1PED3wZeCAAXmNWuKhO6F hbxJBw3msO2YkpCrtZ21qezvbExgUw== =T2Rw -END PGP SIGNATURE End Message ---
Processed: limit source to vm, tagging 1042889
Processing commands for cont...@bugs.debian.org: > limit source vm Limiting to bugs with field 'source' containing at least one of 'vm' Limit currently set to 'source':'vm' > tags 1042889 + pending Bug #1042889 [src:vm] vm: autopkgtest fails against Emacs 29.1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042889: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042889 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1047864: impressive: Crashes at startup: «module 'PIL.Image' has no attribute 'ANTIALIAS'»
Package: impressive Version: 0.13.1-1 Severity: grave Justification: renders package unusable Hello again, I have stumbled upon a new bug that affects impressive :-( When starting up, I see the logo screen, but immediately afterwards, impressive crashes with the following: $ impressive test.pdf Welcome to Impressive version 0.13.1 Platform library: [pygame-unix] Python 3.11.4 / PyGame 2.5.0 / SDL 2.28.1 Detected screen size: 3840x2160 pixels PDF renderer: MuPDF 1.4 or newer OpenGL renderer: Mesa Intel(R) UHD Graphics 600 (GLK 2) Your version of PIL is too old or incomplete, disabling OSD. warning: ICC support is not available warning: ICC support is not available === OOPS! Impressive crashed! This shouldn't happen. Please report this incident to the author, including the full output of the program, particularly the following lines. If possible, please also send the input files you used. Impressive version: 0.13.1 Python version: 3.11.4 (main, Jun 7 2023, 10:13:09) [GCC 12.2.0] Impressive platform: pygame-unix PyGame version: 2.5.0 SDL version: 2.28.1 PIL version: Pillow 10.0.0 PDF renderer: MuPDF 1.4 or newer OpenGL vendor: Intel OpenGL renderer: Mesa Intel(R) UHD Graphics 600 (GLK 2) OpenGL version: 4.6 (Compatibility Profile) Mesa 23.1.4-1 Operating system: Linux 6.4.0-1-amd64 (x86_64) Linux distribution: Debian GNU/Linux trixie/sid Command line: /usr/bin/impressive test.pdf Traceback (most recent call last): File "/usr/bin/impressive", line 6569, in run_main main() File "/usr/bin/impressive", line 6486, in main RenderPage(Pcurrent, Tcurrent) File "/usr/bin/impressive", line 3741, in RenderPage gl.TexImage2D(gl.TEXTURE_2D, 0, gl.RGB, TexWidth, TexHeight, 0, gl.RGB, gl.UNSIGNED_BYTE, PageImage(page)) ^^^ File "/usr/bin/impressive", line 3706, in PageImage img.thumbnail((sx, sy), Image.ANTIALIAS) ^^^ AttributeError: module 'PIL.Image' has no attribute 'ANTIALIAS' $ I suppose this comes as a change in python3-pil's API. I got impressive to work again by very simplisticly substituting Image.ANTIALIAS in /usr/bin/impressive, but of course, I'm sure there are better ways to patch this issue :-) -- System Information: Debian Release: trixie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-1-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages impressive depends on: ii mupdf-tools 1.22.2+ds1-1 ii poppler-utils 22.12.0-2+b1 ii python3 3.11.4-5 ii python3-pil 10.0.0-1 ii python3-pygame 2.5.0-1 Versions of packages impressive recommends: ii ffmpeg 7:6.0-5 ii mplayer2:1.5+svn38423-2+b1 ii perl 5.36.0-7 ii xdg-utils 1.1.3-4.1 Versions of packages impressive suggests: ii ghostscript 10.01.2~dfsg-1 pn latex-beamer pn pdftk -- no debconf information
Bug#1042889: vm breakage with Emacs 29
Dirk Eddelbuettel writes ("Bug#1042889: vm breakage with Emacs 29"):
> Yes given the previous bug report and fix ensuring no byte-compilation takes
> place for vm may be best. At least until someone (upstream? another dev?)
> understand why it breaks vm.
FTR, I investigated this a bit and I discovered that the regression is
probably because
native-comp-deferred-compilation-deny-list
has been renamed to
native-comp-jit-compilation-deny-list
I think we should ahve a patch that works with both Emacs versions
(since I don't want to complicate backports etc.); currently I have
this:
(eval-after-load "comp"
'(dolist
deny-list '('native-comp-deferred-compilation-deny-list
'native-comp-jit-compilation-deny-list)
(if (boundp deny-list)
(add-to-list deny-list "/vm.*\.el"
but it is wrong in some way that my limited lisp-fu wasn't able to
diagnose in the limited time I have right now.
I will look at this again RSN.
Ian.
--
Ian JacksonThese opinions are my own.
Pronouns: they/he. If I emailed you from @fyvzl.net or @evade.org.uk,
that is a private address which bypasses my fierce spamfilter.
Bug#1041491: marked as done (yuzu: FTBFS: Unmet build dependencies: glslang-tools:native)
Il 13 agosto 2023 23:16:23 CEST, Debian Bug Tracking System ha scritto: >Your message dated Sun, 13 Aug 2023 23:13:56 +0200 >with message-id <0aa416df-8488-49ee-a38a-b57dbb2cf...@debian.org> >and subject line Re: yuzu: FTBFS: Unmet build dependencies: >glslang-tools:native >has caused the Debian Bug report #1041491, >regarding yuzu: FTBFS: Unmet build dependencies: glslang-tools:native >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.) > >
Bug#1041491: marked as done (yuzu: FTBFS: Unmet build dependencies: glslang-tools:native)
Your message dated Sun, 13 Aug 2023 23:13:56 +0200 with message-id <0aa416df-8488-49ee-a38a-b57dbb2cf...@debian.org> and subject line Re: yuzu: FTBFS: Unmet build dependencies: glslang-tools:native has caused the Debian Bug report #1041491, regarding yuzu: FTBFS: Unmet build dependencies: glslang-tools:native 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.) -- 1041491: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041491 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: yuzu Version: 0-1335+ds-1 Severity: serious Tags: ftbfs sid trixie Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=yuzu=amd64=0-1335%2Bds-1%2Bb1=1689519069=0 dpkg-buildpackage: info: host architecture amd64 dpkg-checkbuilddeps: error: Unmet build dependencies: glslang-tools:native dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting Cheers -- Sebastian Ramacher --- End Message --- --- Begin Message --- Version: yuzu/0-1335+ds-1.1--- End Message ---
Bug#1045688: FTBFS: Could NOT find zstd (missing: zstd_LIBRARY zstd_INCLUDE_DIR)
Source: rocm-device-libs Version: 5.2.3-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, rocm-device-libs fails to build from source. From my build log on amd64: | -- Found Terminfo: /usr/lib/x86_64-linux-gnu/libtinfo.so | -- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.13") | -- Could NOT find zstd (missing: zstd_LIBRARY zstd_INCLUDE_DIR) | -- Found LibXml2: /usr/lib/x86_64-linux-gnu/libxml2.so (found version "2.9.14") | -- Could NOT find zstd (missing: zstd_LIBRARY zstd_INCLUDE_DIR) | -- Linker detection: GNU ld | CMake Deprecation Warning at cmake/OCL.cmake:12 (cmake_policy): | The OLD behavior for policy CMP0053 will be removed from a future version | of CMake. | | The cmake-policies(7) manual explains that the OLD behaviors of all | policies are deprecated and that a policy should be set to OLD only under | specific short-term circumstances. Projects should be ported to the NEW | behavior and not rely on setting a policy to OLD. | Call Stack (most recent call first): | CMakeLists.txt:60 (include) | | | -- Running constant fold tests | device-libs CPACK_RPM_PACKAGE_RELEASE now is local | -- Configuring done (0.6s) | CMake Error at /usr/lib/llvm-15/lib/cmake/llvm/LLVMExports.cmake:73 (set_target_properties): | The link interface of target "LLVMSupport" contains: | | zstd::libzstd_shared | | but the target was not found. Possible reasons include: | | * There is a typo in the target name. | * A find_package call is missing for an IMPORTED target. | * An ALIAS target is missing. | | Call Stack (most recent call first): | /usr/lib/llvm-15/cmake/LLVMConfig.cmake:336 (include) | CMakeLists.txt:38 (find_package) | | | -- Generating done (0.0s) The full build log on riscv64 is available there: https://buildd.debian.org/status/fetch.php?pkg=rocm-device-libs=riscv64=5.2.3-2=1691809795=0 Regards Aurelien
Bug#1043451: libopencsd: binary-any FTBFS
control: tag -1 + patch On 2023-08-11 14:14, Adrian Bunk wrote: > Source: libopencsd > Version: 1.3.3-1 > Severity: serious > Tags: ftbfs trixie sid > > https://buildd.debian.org/status/fetch.php?pkg=libopencsd=riscv64=1.3.3-1=1691714850=0 > > ... >debian/rules override_dh_installdocs > make[1]: Entering directory '/<>' > # kick compat 11+ to put docs where we told it > dh_installdocs -X.md5 -X.map > install -m0755 -d debian/libopencsd-dev/usr/share/doc/libopencsd-dev > install -p -m0644 debian/copyright > debian/libopencsd-dev/usr/share/doc/libopencsd-dev/copyright > install -m0755 -d debian/libopencsd1/usr/share/doc/libopencsd1 > install -p -m0644 debian/copyright > debian/libopencsd1/usr/share/doc/libopencsd1/copyright > install -m0755 -d debian/libopencsd-bin/usr/share/doc/libopencsd-bin > install -p -m0644 debian/copyright > debian/libopencsd-bin/usr/share/doc/libopencsd-bin/copyright > jdupes -rl debian/libopencsd-doc/usr/share/doc/ > > could not stat dir debian/libopencsd-doc/usr/share/doc/ > No duplicates found. > make[1]: *** [debian/rules:46: override_dh_installdocs] Error 1 > > > > The return value of jdupes changed after bookworm to no longer return success > when > the given paths do not exist, which causes this failure in binary-and builds > (dpkg-buildpackage -B) where binary-all packages are not being built. > Please find a patch below to fix the issue: diff -Nru libopencsd-1.3.3/debian/rules libopencsd-1.3.3/debian/rules --- libopencsd-1.3.3/debian/rules +++ libopencsd-1.3.3/debian/rules @@ -40,7 +40,7 @@ make -f decoder/build/linux/makefile docs endif -override_dh_installdocs: +override_dh_installdocs-indep: # kick compat 11+ to put docs where we told it dh_installdocs -X.md5 -X.map jdupes -rl debian/libopencsd-doc/usr/share/doc/ Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Processed: Re: Bug#1043451: libopencsd: binary-any FTBFS
Processing control commands: > tag -1 + patch Bug #1043451 [src:libopencsd] libopencsd: binary-any FTBFS Added tag(s) patch. -- 1043451: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043451 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1045145: Netdata, since v1.41.0, includes a new, non-free version of the dashboard
Source: netdata Version: 1.41.0-1 Severity: serious Starting from version 1.41.0, Netdata has started to include their new agent dashboard - the so-called Cloud UI (or sometimes v2) [1]. This, however, is distributed under a different license than the rest of Netdata - the Netdata Cloud UI License v1.0 (NCUL1) [2]. This license restricts the use of the software, allowing it "only to interface with the licensor's other software components". This makes it violates the section 6 of the DFSG. Moreover, the UI itself is distributed in the minified form, violating the section 2 of DFSG. Luckily, the license does not restrict the redistribution, so Debian is probably not in a legal trouble just yet (disclaimer: IANAL). The old versions of dashboard is still distributed with Netdata. To the best of my knowledge, the old version of the dashboard is still distributed under GPL-3+. Users can choose to go to the old (so-called v1) dashboard by going to e.g. http://localhost:1/v1/. As a related issue, also since version 1.41.0 Netdata will, by default, download the latest version of the Cloud UI from their server to the browser, falling back to the local copy of the UI distributed with itself if it fails to do so. So, in this case, I believe it's possible for Debian to remove the new UI from the Debian version of Netdata. The source tarball will have to be re-packaged, and the relevant code will have to be patched so that it redirects the the v1 version of dashboard. Side note: in fact, the v1 version of the dashboard is also distributed with the agent in the minified form, and it seems like the source package isn't actually included in Debian's source package. There's the bug #982220 which intends to package the dashboard separately. It seems to be filed by one of Netdata's maintainer but doesn't seem to have any activity. In the meantime, including the source of the dashboard at [3] as a no-op secondary orig tarball (or part of debian/missing-source) might be a good stop gap. Whether it's worth an additional bug entry is up to you. Regards, Ratchanan Srirattanamet [1] https://github.com/netdata/netdata/releases/tag/v1.41.0#v1410-one-dashboard [2] https://github.com/netdata/netdata/blob/master/web/gui/v2/LICENSE.md [3] https://github.com/netdata/dashboard
Bug#1037742: marked as done (libssw: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 19:13:36 + with message-id and subject line Bug#1042114: fixed in libssw 1.1-14 has caused the Debian Bug report #1042114, regarding libssw: ftbfs with GCC-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.) -- 1042114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libssw Version: 1.1-13 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libssw_1.1-13_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] Query: 907 TTTCTGCAT-TAT--TTAATGACTCA-TATGTCA-CTCTTAAATGTAC957 Target: 9707TGTTGATTGTTTC-CTTT9723 |**|*||| Query: 958TTCTAATT-TTTCACTTT974 make[1]: Leaving directory '/<>' create-stamp debian/debhelper-build-stamp dh_prep debian/rules override_dh_auto_install make[1]: Entering directory '/<>' sed 's/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/g' debian/libssw0.install.in > debian/libssw0.install sed 's/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/g' debian/libssw-dev.install.in > debian/libssw-dev.install sed -e 's/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/g' \ -e 's/@DEB_JAVA_PKG_VERSION@/1.1/g' debian/libssw-dev.links.in > debian/libssw-dev.links sed 's/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/g' debian/libssw-java.install.in > debian/libssw-java.install sed -e 's/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/g' \ -e 's/@DEB_JAVA_PKG_VERSION@/1.1/g' debian/libssw-java.links.in > debian/libssw-java.links mv src/ssw.jar src/ssw-1.1.jar dh_auto_install make[1]: Leaving directory '/<>' dh_install jh_installjavadoc dh_installdocs dh_installchangelogs debian/rules override_dh_installman make[1]: Entering directory '/<>' LD_LIBRARY_PATH=`pwd`/src help2man --version-string=' ' --help-option=' ' \ -I debian/extra-man-info.txt \ -N -n 'fast Smith-Waterman aligner' \ --no-discard-stderr src/ssw-align \ | fgrep -v ERROR > debian/ssw-align.1 dh_installman make[1]: Leaving directory '/<>' dh_perl dh_link jh_installlibs jh_classpath jh_manifest jh_exec jh_depends mh_installpoms mh_linkjars --skip-clean-poms dh_strip_nondeterminism dh_compress dh_fixperms dh_missing dh_dwz -a dh_strip -a dh_makeshlibs -a dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libssw0/DEBIAN/symbols doesn't match completely debian/libssw0.symbols --- debian/libssw0.symbols (libssw0_1.1-13_amd64) +++ dpkg-gensymbolsRLn4HN 2023-05-22 02:10:01.559468309 + @@ -22,9 +22,9 @@ _ZNK20StripedSmithWaterman7Aligner5AlignEPKcRKNS_6FilterEPNS_9AlignmentE@Base 1.1 _ZNK20StripedSmithWaterman7Aligner5AlignEPKcS2_RKiRKNS_6FilterEPNS_9AlignmentE@Base 1.1 (optional)_ZNSt6vectorIjSaIjEE17_M_realloc_insertIJRKjEEEvN9__gnu_cxx17__normal_iteratorIPjS1_EEDpOT_@Base 1.1 - _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 1.1 - _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 1.1 - _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 1.1 +#MISSING: 1.1-13# _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 1.1 +#MISSING: 1.1-13# _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 1.1 +#MISSING: 1.1-13#
Bug#1042114: marked as done (libssw: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 19:13:36 + with message-id and subject line Bug#1037742: fixed in libssw 1.1-14 has caused the Debian Bug report #1037742, regarding libssw: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libssw Version: 1.1-13 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > LD_LIBRARY_PATH=`pwd`/src help2man --version-string=' ' --help-option=' ' \ > -I debian/extra-man-info.txt \ > -N -n 'fast Smith-Waterman aligner' \ > --no-discard-stderr src/ssw-align \ > | fgrep -v ERROR > debian/ssw-align.1 > dh_installman > make[1]: Leaving directory '/<>' >dh_perl >dh_link >jh_installlibs >jh_classpath >jh_manifest >jh_exec >jh_depends >mh_installpoms >mh_linkjars --skip-clean-poms >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libssw0/DEBIAN/symbols doesn't match > completely debian/libssw0.symbols > --- debian/libssw0.symbols (libssw0_1.1-13_amd64) > +++ dpkg-gensymbolsLQ_iNr 2023-07-26 19:14:10.300342095 + > @@ -22,9 +22,9 @@ > > _ZNK20StripedSmithWaterman7Aligner5AlignEPKcRKNS_6FilterEPNS_9AlignmentE@Base > 1.1 > > _ZNK20StripedSmithWaterman7Aligner5AlignEPKcS2_RKiRKNS_6FilterEPNS_9AlignmentE@Base > 1.1 > > (optional)_ZNSt6vectorIjSaIjEE17_M_realloc_insertIJRKjEEEvN9__gnu_cxx17__normal_iteratorIPjS1_EEDpOT_@Base > 1.1 > - _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 1.1 > - _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 1.1 > - _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 1.1 > +#MISSING: 1.1-13# > _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 1.1 > +#MISSING: 1.1-13# > _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 1.1 > +#MISSING: 1.1-13# > _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 1.1 > align_destroy@Base 1.1 > init_destroy@Base 1.1 > mark_mismatch@Base 1.1 > dh_makeshlibs: error: failing due to earlier errors > make: *** [debian/rules:20: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/07/26/libssw_1.1-13_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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: libssw Source-Version: 1.1-14 Done: Michael R. Crusoe We believe that the bug you reported is fixed in the latest version of libssw, 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 1037...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated libssw 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, 13 Aug 2023 20:51:28 +0200 Source: libssw Architecture: source Version: 1.1-14 Distribution: unstable Urgency: medium Maintainer: Debian
Bug#1042114: marked as done (libssw: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 19:13:36 + with message-id and subject line Bug#1042114: fixed in libssw 1.1-14 has caused the Debian Bug report #1042114, regarding libssw: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042114 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libssw Version: 1.1-13 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > LD_LIBRARY_PATH=`pwd`/src help2man --version-string=' ' --help-option=' ' \ > -I debian/extra-man-info.txt \ > -N -n 'fast Smith-Waterman aligner' \ > --no-discard-stderr src/ssw-align \ > | fgrep -v ERROR > debian/ssw-align.1 > dh_installman > make[1]: Leaving directory '/<>' >dh_perl >dh_link >jh_installlibs >jh_classpath >jh_manifest >jh_exec >jh_depends >mh_installpoms >mh_linkjars --skip-clean-poms >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libssw0/DEBIAN/symbols doesn't match > completely debian/libssw0.symbols > --- debian/libssw0.symbols (libssw0_1.1-13_amd64) > +++ dpkg-gensymbolsLQ_iNr 2023-07-26 19:14:10.300342095 + > @@ -22,9 +22,9 @@ > > _ZNK20StripedSmithWaterman7Aligner5AlignEPKcRKNS_6FilterEPNS_9AlignmentE@Base > 1.1 > > _ZNK20StripedSmithWaterman7Aligner5AlignEPKcS2_RKiRKNS_6FilterEPNS_9AlignmentE@Base > 1.1 > > (optional)_ZNSt6vectorIjSaIjEE17_M_realloc_insertIJRKjEEEvN9__gnu_cxx17__normal_iteratorIPjS1_EEDpOT_@Base > 1.1 > - _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 1.1 > - _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 1.1 > - _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 1.1 > +#MISSING: 1.1-13# > _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 1.1 > +#MISSING: 1.1-13# > _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 1.1 > +#MISSING: 1.1-13# > _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 1.1 > align_destroy@Base 1.1 > init_destroy@Base 1.1 > mark_mismatch@Base 1.1 > dh_makeshlibs: error: failing due to earlier errors > make: *** [debian/rules:20: binary] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/07/26/libssw_1.1-13_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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: libssw Source-Version: 1.1-14 Done: Michael R. Crusoe We believe that the bug you reported is fixed in the latest version of libssw, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael R. Crusoe (supplier of updated libssw 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, 13 Aug 2023 20:51:28 +0200 Source: libssw Architecture: source Version: 1.1-14 Distribution: unstable Urgency: medium Maintainer: Debian
Bug#1037742: marked as done (libssw: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 19:13:36 + with message-id and subject line Bug#1037742: fixed in libssw 1.1-14 has caused the Debian Bug report #1037742, regarding libssw: ftbfs with GCC-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.) -- 1037742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037742 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libssw Version: 1.1-13 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libssw_1.1-13_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] Query: 907 TTTCTGCAT-TAT--TTAATGACTCA-TATGTCA-CTCTTAAATGTAC957 Target: 9707TGTTGATTGTTTC-CTTT9723 |**|*||| Query: 958TTCTAATT-TTTCACTTT974 make[1]: Leaving directory '/<>' create-stamp debian/debhelper-build-stamp dh_prep debian/rules override_dh_auto_install make[1]: Entering directory '/<>' sed 's/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/g' debian/libssw0.install.in > debian/libssw0.install sed 's/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/g' debian/libssw-dev.install.in > debian/libssw-dev.install sed -e 's/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/g' \ -e 's/@DEB_JAVA_PKG_VERSION@/1.1/g' debian/libssw-dev.links.in > debian/libssw-dev.links sed 's/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/g' debian/libssw-java.install.in > debian/libssw-java.install sed -e 's/@DEB_HOST_MULTIARCH@/x86_64-linux-gnu/g' \ -e 's/@DEB_JAVA_PKG_VERSION@/1.1/g' debian/libssw-java.links.in > debian/libssw-java.links mv src/ssw.jar src/ssw-1.1.jar dh_auto_install make[1]: Leaving directory '/<>' dh_install jh_installjavadoc dh_installdocs dh_installchangelogs debian/rules override_dh_installman make[1]: Entering directory '/<>' LD_LIBRARY_PATH=`pwd`/src help2man --version-string=' ' --help-option=' ' \ -I debian/extra-man-info.txt \ -N -n 'fast Smith-Waterman aligner' \ --no-discard-stderr src/ssw-align \ | fgrep -v ERROR > debian/ssw-align.1 dh_installman make[1]: Leaving directory '/<>' dh_perl dh_link jh_installlibs jh_classpath jh_manifest jh_exec jh_depends mh_installpoms mh_linkjars --skip-clean-poms dh_strip_nondeterminism dh_compress dh_fixperms dh_missing dh_dwz -a dh_strip -a dh_makeshlibs -a dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libssw0/DEBIAN/symbols doesn't match completely debian/libssw0.symbols --- debian/libssw0.symbols (libssw0_1.1-13_amd64) +++ dpkg-gensymbolsRLn4HN 2023-05-22 02:10:01.559468309 + @@ -22,9 +22,9 @@ _ZNK20StripedSmithWaterman7Aligner5AlignEPKcRKNS_6FilterEPNS_9AlignmentE@Base 1.1 _ZNK20StripedSmithWaterman7Aligner5AlignEPKcS2_RKiRKNS_6FilterEPNS_9AlignmentE@Base 1.1 (optional)_ZNSt6vectorIjSaIjEE17_M_realloc_insertIJRKjEEEvN9__gnu_cxx17__normal_iteratorIPjS1_EEDpOT_@Base 1.1 - _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 1.1 - _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 1.1 - _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED2Ev@Base 1.1 +#MISSING: 1.1-13# _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 1.1 +#MISSING: 1.1-13# _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED1Ev@Base 1.1 +#MISSING: 1.1-13#
Bug#1037720: marked as done (libbpp-qt: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 19:13:12 + with message-id and subject line Bug#1037720: fixed in libbpp-qt 2.4.1-9 has caused the Debian Bug report #1037720, regarding libbpp-qt: ftbfs with GCC-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.) -- 1037720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-qt Version: 2.4.1-8 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libbpp-qt_2.4.1-8_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] _ZNSt10unique_ptrIN3bpp14NodeMouseEventESt14default_deleteIS1_EED2Ev@Base 2.4.1 - _ZNSt12_Vector_baseIPKN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS5_EED1Ev@Base 2.4.1 - _ZNSt12_Vector_baseIPKN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS5_EED2Ev@Base 2.4.1 - _ZNSt12_Vector_baseIPN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS4_EED1Ev@Base 2.4.1 - _ZNSt12_Vector_baseIPN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS4_EED2Ev@Base 2.4.1 - _ZNSt12_Vector_baseIdSaIdEED1Ev@Base 2.4.1 - _ZNSt12_Vector_baseIdSaIdEED2Ev@Base 2.4.1 - _ZNSt12_Vector_baseIiSaIiEED1Ev@Base 2.4.1 - _ZNSt12_Vector_baseIiSaIiEED2Ev@Base 2.4.1 - _ZNSt12_Vector_baseImSaImEED1Ev@Base 2.4.1 - _ZNSt12_Vector_baseImSaImEED2Ev@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseIPKN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS5_EED1Ev@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseIPKN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS5_EED2Ev@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseIPN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS4_EED1Ev@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseIPN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS4_EED2Ev@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseIdSaIdEED1Ev@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseIdSaIdEED2Ev@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseIiSaIiEED1Ev@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseIiSaIiEED2Ev@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseImSaImEED1Ev@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseImSaImEED2Ev@Base 2.4.1 _ZNSt3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPN3bpp8ClonableESt4lessIS5_ESaISt4pairIKS5_S8_EEEixERSC_@Base 2.4.1 _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE17_M_realloc_insertIJRKS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base 2.4.1 _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev@Base 2.4.1 _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base 2.4.1 _ZNSt6vectorIPKN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS5_EE17_M_realloc_insertIJS5_EEEvN9__gnu_cxx17__normal_iteratorIPS5_S7_EEDpOT_@Base 2.4.1 + _ZNSt6vectorIPKN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS5_EED1Ev@Base 2.4.1-8 + _ZNSt6vectorIPKN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS5_EED2Ev@Base 2.4.1-8 _ZNSt6vectorIPN3bpp11TreeDrawingESaIS2_EE17_M_realloc_insertIJRKS2_EEEvN9__gnu_cxx17__normal_iteratorIPS2_S4_EEDpOT_@Base 2.4.1 _ZNSt6vectorIPN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS4_EE17_M_realloc_insertIJS4_EEEvN9__gnu_cxx17__normal_iteratorIPS4_S6_EEDpOT_@Base 2.4.1 + _ZNSt6vectorIPN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS4_EED1Ev@Base 2.4.1-8 + _ZNSt6vectorIPN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS4_EED2Ev@Base 2.4.1-8
Bug#1042143: marked as done (libbpp-qt: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 19:13:12 + with message-id and subject line Bug#1037720: fixed in libbpp-qt 2.4.1-9 has caused the Debian Bug report #1037720, regarding libbpp-qt: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037720: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037720 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-qt Version: 2.4.1-8 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include/* usr/include \ > --movedev debian/tmp/usr/lib/*/cmake > usr/lib/x86_64-linux-gnu \ > debian/tmp/usr/lib/*/*.so > Library package automatic movement utility > --> libbpp-core-dev package exists. > --> libbpp-phyl-dev package exists. > --> qtdeclarative5-dev package exists. > set -e > install -d -m 755 debian/libbpp-qt-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-qt2/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-qt.a > debian/libbpp-qt-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-qt.so > debian/libbpp-qt-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-qt.so.2 > debian/libbpp-qt2/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-qt.so.2.0.0 > debian/libbpp-qt2/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-qt-dev > PKGSHL=libbpp-qt2 > install -d -m 755 debian/libbpp-qt-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-qt-dev/usr/include > install -d -m 755 debian/libbpp-qt-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-qt-dev/usr/lib/x86_64-linux-gnu > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbpp-qt2/DEBIAN/symbols doesn't match > completely debian/libbpp-qt2.symbols.amd64 > --- debian/libbpp-qt2.symbols.amd64 (libbpp-qt2_2.4.1-8_amd64) > +++ dpkg-gensymbolsriHxXk 2023-07-26 19:17:10.661655430 + > @@ -377,27 +377,37 @@ > _ZNSt10unique_ptrI14QGraphicsSceneSt14default_deleteIS0_EED2Ev@Base 2.4.1 > _ZNSt10unique_ptrIN3bpp14NodeMouseEventESt14default_deleteIS1_EED1Ev@Base > 2.4.1 > _ZNSt10unique_ptrIN3bpp14NodeMouseEventESt14default_deleteIS1_EED2Ev@Base > 2.4.1 > - > _ZNSt12_Vector_baseIPKN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS5_EED1Ev@Base > 2.4.1 > - > _ZNSt12_Vector_baseIPKN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS5_EED2Ev@Base > 2.4.1 > - > _ZNSt12_Vector_baseIPN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS4_EED1Ev@Base > 2.4.1 > - > _ZNSt12_Vector_baseIPN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS4_EED2Ev@Base > 2.4.1 > - _ZNSt12_Vector_baseIdSaIdEED1Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIdSaIdEED2Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIiSaIiEED1Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIiSaIiEED2Ev@Base 2.4.1 > - _ZNSt12_Vector_baseImSaImEED1Ev@Base 2.4.1 > - _ZNSt12_Vector_baseImSaImEED2Ev@Base 2.4.1 > +#MISSING: 2.4.1-8# > _ZNSt12_Vector_baseIPKN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS5_EED1Ev@Base > 2.4.1 > +#MISSING: 2.4.1-8# > _ZNSt12_Vector_baseIPKN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS5_EED2Ev@Base > 2.4.1 > +#MISSING: 2.4.1-8# > _ZNSt12_Vector_baseIPN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS4_EED1Ev@Base > 2.4.1 > +#MISSING: 2.4.1-8# > _ZNSt12_Vector_baseIPN3bpp12NodeTemplateINS0_19TreeDrawingNodeInfoEEESaIS4_EED2Ev@Base > 2.4.1 > +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseIdSaIdEED1Ev@Base 2.4.1 > +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseIdSaIdEED2Ev@Base 2.4.1 > +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseIiSaIiEED1Ev@Base 2.4.1 > +#MISSING: 2.4.1-8# _ZNSt12_Vector_baseIiSaIiEED2Ev@Base
Bug#1045144: grpc-java: binary-any FTBFS with recent jdupes
Source: grpc-java Version: 1.41.3+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Dear maintainer, grpc-java fails to build from source when building only binary-any and not binary-all: | make[1]: Leaving directory '/<>' |dh_installman -a -O--buildsystem=gradle | install -m0755 -d debian/protobuf-compiler-grpc-java-plugin/usr/share/man/man1/ | install -p -m0644 ./debian/grpc_java_plugin.1 debian/protobuf-compiler-grpc-java-plugin/usr/share/man/man1/grpc_java_plugin.1 | man-recode --to-code UTF-8 --suffix .dh-new debian/protobuf-compiler-grpc-java-plugin/usr/share/man/man1/grpc_java_plugin.1 | mv debian/protobuf-compiler-grpc-java-plugin/usr/share/man/man1/grpc_java_plugin.1.dh-new debian/protobuf-compiler-grpc-java-plugin/usr/share/man/man1/grpc_java_plugin.1 | chmod 0644 -- debian/protobuf-compiler-grpc-java-plugin/usr/share/man/man1/grpc_java_plugin.1 |dh_installsystemduser -a -O--buildsystem=gradle |dh_perl -a -O--buildsystem=gradle | rm -f debian/protobuf-compiler-grpc-java-plugin.debhelper.log |debian/rules override_dh_link | make[1]: Entering directory '/<>' | dh_link | jdupes -rl debian/libgrpc-java/usr | | could not stat dir debian/libgrpc-java/usr | No duplicates found. | make[1]: *** [debian/rules:46: override_dh_link] Error 1 The full build log is available there: https://buildd.debian.org/status/fetch.php?pkg=grpc-java=riscv64=1.41.3%2Bds-1=1691809480=0 The return value of jdupes changed after bookworm to no longer return success when the given paths do not exist, which causes this failure in binary-any builds. A possible patch is: --- grpc-java-1.41.3+ds/debian/rules +++ grpc-java-1.41.3+ds/debian/rules @@ -41,6 +41,5 @@ override_dh_auto_test: -override_dh_link: - dh_link +execute_after_dh_link-indep: jdupes -rl debian/libgrpc-java/usr Regards Aurelien
Processed: src:gmap: fails to migrate to testing for too long: FTBFS on !amd64
Processing control commands:
> close -1 2023-07-20+ds-1
Bug #1045094 [src:gmap] src:gmap: fails to migrate to testing for too long:
FTBFS on !amd64
Marked as fixed in versions gmap/2023-07-20+ds-1.
Bug #1045094 [src:gmap] src:gmap: fails to migrate to testing for too long:
FTBFS on !amd64
Marked Bug as done
> block -1 by 1041451
Bug #1045094 {Done: Paul Gevers } [src:gmap] src:gmap: fails
to migrate to testing for too long: FTBFS on !amd64
1045094 was not blocked by any bugs.
1045094 was not blocking any bugs.
Added blocking bug(s) of 1045094: 1041451
--
1045094: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1045094
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1045094: src:gmap: fails to migrate to testing for too long: FTBFS on !amd64
Source: gmap Version: 2021-12-17+ds-3 Severity: serious Control: close -1 2023-07-20+ds-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1041451 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:gmap has been trying to migrate for 31 days [2]. Hence, I am filing this bug. The version in unstable FTBFS as reported in bug #1041451. 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 trixie, 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/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=gmap OpenPGP_signature.asc Description: OpenPGP digital signature
Bug#1042171: imath: FTBFS: dh_install: error: missing files, aborting
Dear maintainer, On 2023-08-13 11:40, Aurelien Jarno wrote: > Dear maintainer, > > On 2023-08-13 10:53, Aurelien Jarno wrote: > > On 2023-07-26 22:03, Lucas Nussbaum wrote: > > > Source: imath > > > Version: 3.1.6-1 > > > Severity: serious > > > Justification: FTBFS > > > Tags: trixie sid ftbfs > > > User: lu...@debian.org > > > Usertags: ftbfs-20230726 ftbfs-trixie > > > > > > Hi, > > > > > > During a rebuild of all packages in sid, your package failed to build > > > on amd64. > > > > > The solution to fix this is to use PYIMATH_OVERRIDE_PYTHON_INSTALL_DIR > to define the installation of the Python modules instead of relying on > autodetection. > > I have prepared a NMU for imath (versioned as 3.1.6-1.1) to fix this > FTBFS, you will find the diff attached. I have uploaded DELAYED/2. > Please feel free to tell me if I should delay it further or cancel it. In the meantime, I have found a thread about the behavior change for Python packages built with CMake on debian-devel@l.d.o [1]. I have updated the NMU accordingly, please find attached the new diff. Regards, Aurelien [1] https://lists.debian.org/debian-devel/2023/07/msg00307.html -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net diff -Nru imath-3.1.6/debian/changelog imath-3.1.6/debian/changelog --- imath-3.1.6/debian/changelog 2023-01-21 15:17:19.0 +0100 +++ imath-3.1.6/debian/changelog 2023-08-13 18:36:57.0 +0200 @@ -1,3 +1,11 @@ +imath (3.1.6-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Export DEB_PYTHON_INSTALL_LAYOUT = deb in debian/rules to adjust to recent +change in CMake's Python_SITEARCH (Closes: #1042171). + + -- Aurelien Jarno Sun, 13 Aug 2023 16:36:57 + + imath (3.1.6-1) unstable; urgency=medium * New upstream release diff -Nru imath-3.1.6/debian/rules imath-3.1.6/debian/rules --- imath-3.1.6/debian/rules 2023-01-21 15:16:33.0 +0100 +++ imath-3.1.6/debian/rules 2023-08-13 18:36:57.0 +0200 @@ -4,6 +4,7 @@ export DH_OPTIONS export DEB_BUILD_MAINT_OPTIONS = hardening=+all +export DEB_PYTHON_INSTALL_LAYOUT = deb INSTDIR = debian/tmp signature.asc Description: PGP signature
Bug#1044138: RM: pcmanx-gtk2 -- RoQA; dead upstream; depends on gtk2
Source: pcmanx-gtk2 Severity: serious Version: 1.3-2 pcmanx-gtk2 does not seem to be used a lot anymore. I intend to file a RM bug. If you have any reasons to keep it in Debian please voice them here. To get people's attention, I am filing as a serious bug and will reassign to the FTP team when the package is autoremoved from testing.
Bug#1042171: imath: FTBFS: dh_install: error: missing files, aborting
On 2023-08-13 17:55, Michael Tokarev wrote: > On Sun, 13 Aug 2023 11:40:11 +0200 Aurelien Jarno wrote: > .. > > The solution to fix this is to use PYIMATH_OVERRIDE_PYTHON_INSTALL_DIR > > to define the installation of the Python modules instead of relying on > > autodetection. > > Can't this be done at the cmake level instead of overriding this in each > package? It seems that's not what currently planned according to the thread on debian-devel: https://lists.debian.org/debian-devel/2023/07/msg00307.html That said, I think it would be better using that more generic way in my patch than the imath specific PYIMATH_OVERRIDE_PYTHON_INSTALL_DIR. Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Bug#1035694: marked as done (python-bottle: tox 4 support: Build-Depend on python3-wheel)
Your message dated Sun, 13 Aug 2023 16:19:48 + with message-id and subject line Bug#1035694: fixed in python-bottle 0.12.23-1.2 has caused the Debian Bug report #1035694, regarding python-bottle: tox 4 support: Build-Depend on python3-wheel 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.) -- 1035694: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035694 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-bottle Version: 0.12.23-1.1 Severity: normal Control: block 1035675 with -1 Hi, With the tox 4 support in dh-python (bug 1035675), python-bottle will need to Build-Depend on python3-wheel, to continue to build successfully. Stefano --- End Message --- --- Begin Message --- Source: python-bottle Source-Version: 0.12.23-1.2 Done: Stefano Rivera We believe that the bug you reported is fixed in the latest version of python-bottle, 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 1035...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Stefano Rivera (supplier of updated python-bottle package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 11 Aug 2023 17:42:13 +0200 Source: python-bottle Architecture: source Version: 0.12.23-1.2 Distribution: unstable Urgency: medium Maintainer: Federico Ceratto Changed-By: Stefano Rivera Closes: 1035694 Changes: python-bottle (0.12.23-1.2) unstable; urgency=medium . * Non-maintainer upload. * Build-Depend on python3-wheel, for tox 4 support. (Closes: #1035694) Checksums-Sha1: 5a0882e8adbb545468722c215bd819baa07c0324 1594 python-bottle_0.12.23-1.2.dsc e9273fb823e03a888c4e052ad856bb1a13944dea 7048 python-bottle_0.12.23-1.2.debian.tar.xz c51420542684596f1d9b9672b8189ecfd7e874dc 5384 python-bottle_0.12.23-1.2_source.buildinfo Checksums-Sha256: afd0bc8ff4437fd5092b382bd5e5c01d6c963ff2d5bc8317bcadec74f6b775e9 1594 python-bottle_0.12.23-1.2.dsc 95048eecb16f8c3cc121abe8faab385127a7a6f0c9e0b966f6843a1e87f83eb9 7048 python-bottle_0.12.23-1.2.debian.tar.xz a0559f32898fd8da78c9bf755ee46f198175abda675c610eb5b55dc8aca3bfa9 5384 python-bottle_0.12.23-1.2_source.buildinfo Files: 680f53dd46a011c5609d8b45537df5bf 1594 python optional python-bottle_0.12.23-1.2.dsc 34f49b0675bd11d9ed04968613a921b5 7048 python optional python-bottle_0.12.23-1.2.debian.tar.xz a50e87902749a7b38cace4b5af99b51c 5384 python optional python-bottle_0.12.23-1.2_source.buildinfo -BEGIN PGP SIGNATURE- iIoEARYKADIWIQTumtb5BSD6EfafSCRHew2wJjpU2AUCZNZYLxQcc3RlZmFub3JA ZGViaWFuLm9yZwAKCRBHew2wJjpU2IQeAQCOtQEXpBQPG3DBpmgTFUEgXtdT+MX8 IaeRYEIKB/YNPAD/Vb1z27wRQf7uperUZlwCyHtOcQA9rxjuIwnnPZ57XQM= =BTSU -END PGP SIGNATURE End Message ---
Bug#1042512: marked as done (src:python-numpysane: fails to migrate to testing for too long: uploader built arch:all binary)
Your message dated Sun, 13 Aug 2023 15:50:23 + with message-id and subject line Bug#1042512: fixed in python-numpysane 0.39-1.1 has caused the Debian Bug report #1042512, regarding src:python-numpysane: fails to migrate to testing for too long: uploader built arch:all binary 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.) -- 1042512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-numpysane Version: 0.36-1 Severity: serious Control: close -1 0.39-1 Tags: sid trixie pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as having a Release Critical bug in testing [1]. Your package src:python-numpysane has been trying to migrate for 31 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 trixie, so it doesn't affect (old-)stable. Your package is only blocked because the arch:all binary package(s) aren't built on a buildd. Unfortunately the Debian infrastructure doesn't allow arch:all packages to be properly binNMU'ed. Hence, I will shortly do a no-changes source-only upload to DELAYED/15, closing this bug. Please let me know if I should delay or cancel that upload. Paul [1] https://lists.debian.org/debian-devel-announce/2023/06/msg1.html [2] https://qa.debian.org/excuses.php?package=python-numpysane OpenPGP_signature Description: OpenPGP digital signature --- End Message --- --- Begin Message --- Source: python-numpysane Source-Version: 0.39-1.1 Done: Paul Gevers We believe that the bug you reported is fixed in the latest version of python-numpysane, 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 1042...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Paul Gevers (supplier of updated python-numpysane package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 29 Jul 2023 16:46:46 +0200 Source: python-numpysane Architecture: source Version: 0.39-1.1 Distribution: unstable Urgency: medium Maintainer: Debian Python Team Changed-By: Paul Gevers Closes: 1042512 Changes: python-numpysane (0.39-1.1) unstable; urgency=medium . * Non-maintainer upload. * source only upload to enable migration (Closes: #1042512) Checksums-Sha1: b3faef10b4be6b40a81dbfcf53b14da5a8e155f2 1853 python-numpysane_0.39-1.1.dsc 8d010c513a6bf53d35bcf04998dad445896c4512 3120 python-numpysane_0.39-1.1.debian.tar.xz Checksums-Sha256: d290a55d906195b57f00cf51eb888b577ca6fef595d90d1801c368f2633ead2e 1853 python-numpysane_0.39-1.1.dsc 651c2377ff13d3c210d46463ba7957f39240e66ed05d2b7b27362dce218aaa53 3120 python-numpysane_0.39-1.1.debian.tar.xz Files: a554d3218d08184f0867e06f63ef5c5b 1853 python optional python-numpysane_0.39-1.1.dsc 358e6fbe170591b9b2f25747a57335a0 3120 python optional python-numpysane_0.39-1.1.debian.tar.xz -BEGIN PGP SIGNATURE- iQEzBAEBCAAdFiEEWLZtSHNr6TsFLeZynFyZ6wW9dQoFAmTFJosACgkQnFyZ6wW9 dQpY0ggAy9ssSkfSimQMOhC5cBJvx9UCMfIsJKwrNJ7GSF/++8OCOdH+WPLoVnaU 1l4B9hlPT4zGD5CxLhYoM47MtsuJFLM44HE62/m2w2LJZJZ9FK+7EKVc7N0PveBY lutH4uYEkqMkcD9Q690R52L+dJToX+dTrJ9RUXEAXgCgO7cKS3d+9FQw/mXUcdpw P1WeyjBGLSNzpWzIGRLszAQazugxadVy52pIVN4VfhgCj9bNLrv5QwCM6yr1PIPY
Bug#1042171: imath: FTBFS: dh_install: error: missing files, aborting
On Sun, 13 Aug 2023 11:40:11 +0200 Aurelien Jarno wrote: .. The solution to fix this is to use PYIMATH_OVERRIDE_PYTHON_INSTALL_DIR to define the installation of the Python modules instead of relying on autodetection. Can't this be done at the cmake level instead of overriding this in each package? /mjt
Bug#1028111: marked as done (r-cran-clock: autopkgtest failure on 32bit)
Your message dated Sun, 13 Aug 2023 14:52:07 +
with message-id
and subject line Bug#1028111: fixed in r-cran-clock 0.7.0-1.1
has caused the Debian Bug report #1028111,
regarding r-cran-clock: autopkgtest failure on 32bit
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.)
--
1028111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028111
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: r-cran-clock
Version: 0.6.1-1
Severity: serious
https://tracker.debian.org/pkg/r-cran-clock
Issues preventing migration:
∙ ∙ autopkgtest for r-cran-clock/0.6.1-1: amd64: Pass, arm64: Pass, armel:
Regression ♻ , armhf: Regression ♻ , i386: Regression ♻
...
> test_check("clock")
[ FAIL 2 | WARN 29 | SKIP 252 | PASS 1146 ]
══ Skipped tests ═══
• On CRAN (252)
══ Failed tests
── Failure ('test-posixt.R:151'): can group by
year/month/day/hour/minute/second ──
date_group(z, "year") (`actual`) not identical to `expect` (`expected`).
actual | expected
[1] "-1-12-31 23:56:02" - "0-01-01" [1]
[2] "0-12-31 23:56:02" - "1-01-01" [2]
[3] "1-12-31 23:56:02" - "2-01-01" [3]
[4] "2-12-31 23:56:02" - "3-01-01" [4]
[5] "3-12-31 23:56:02" - "4-01-01" [5]
── Failure ('test-posixt.R:152'): can group by
year/month/day/hour/minute/second ──
date_group(z, "year", n = 3) (`actual`) not identical to expect[c(1, 1, 1, 4,
4)] (`expected`).
actual | expected
[1] "-1-12-31 23:56:02" - "0-01-01" [1]
[2] "-1-12-31 23:56:02" - "0-01-01" [2]
[3] "-1-12-31 23:56:02" - "0-01-01" [3]
[4] "2-12-31 23:56:02" - "3-01-01" [4]
[5] "2-12-31 23:56:02" - "3-01-01" [5]
[ FAIL 2 | WARN 29 | SKIP 252 | PASS 1146 ]
Error: Test failures
Execution halted
autopkgtest [16:10:54]: test run-unit-test: ---]
autopkgtest [16:10:55]: test run-unit-test: - - - - - - - - - - results - - -
- - - - - - -
run-unit-testFAIL non-zero exit status 1
...
--- End Message ---
--- Begin Message ---
Source: r-cran-clock
Source-Version: 0.7.0-1.1
Done: Dirk Eddelbuettel
We believe that the bug you reported is fixed in the latest version of
r-cran-clock, 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 1028...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Dirk Eddelbuettel (supplier of updated r-cran-clock package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sun, 13 Aug 2023 09:17:02 -0500
Source: r-cran-clock
Architecture: source
Version: 0.7.0-1.1
Distribution: unstable
Urgency: medium
Maintainer: Debian R Packages Maintainers
Changed-By: Dirk Eddelbuettel
Closes: 1028111
Changes:
r-cran-clock (0.7.0-1.1) unstable; urgency=medium
.
* Non-maintainer upload
* debian/tests/run-unit-test: Undo change from 0.6.1-2 which breaks
tests under 0.7.0, change to (on those architectures) skipping the
particular test file for now and unblocking a regression which would
lead to AUTORM of dozens of dependee packages. (Closes: #1028111)
Checksums-Sha1:
8ff6b3de915e5cf9604dbf3120fec7821ef86ffa 2172 r-cran-clock_0.7.0-1.1.dsc
f3f69afdedd396649d1a0ff2b5e17fd064d38ed2 3484
r-cran-clock_0.7.0-1.1.debian.tar.xz
e3a2f8f5605e4eed776c9daa92ef22c4b482ebfb 11023
r-cran-clock_0.7.0-1.1_amd64.buildinfo
Checksums-Sha256:
ecce57221246736f503d0499df1d8cbf1ae14e52af47cda74d8f21489f724a3c 2172
r-cran-clock_0.7.0-1.1.dsc
995d6eab1d266bb227d6a3d6d7e9c10b02fd6b3dcab62cdc145cdab2e3fb52eb 3484
r-cran-clock_0.7.0-1.1.debian.tar.xz
b31c0e993e5058f5c5d102aceeac81c019e497314498ef34e45d1579df385b0c 11023
r-cran-clock_0.7.0-1.1_amd64.buildinfo
Files:
8f7e687beb3de5b614328be70ee0a765 2172 gnu-r optional r-cran-clock_0.7.0-1.1.dsc
bc5ec69b68a125219d27ba6080e0caba 3484 gnu-r optional
r-cran-clock_0.7.0-1.1.debian.tar.xz
32e616d6e4510e2b9b3a8fdf6d404bfd 11023 gnu-r optional
r-cran-clock_0.7.0-1.1_amd64.buildinfo
-BEGIN PGP SIGNATURE-
iQIVAwUBZNjm46FIn+KrmaIaAQhJeBAAuYHkMYjpDIMgSelHGU2Wdm0c4lLqCE1I
Bug#1043417: marked as done (libwraster6: libwraster ABI breakage)
Your message dated Sun, 13 Aug 2023 13:04:56 + with message-id and subject line Bug#1043417: fixed in wmaker 0.96.0-2 has caused the Debian Bug report #1043417, regarding libwraster6: libwraster ABI breakage 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.) -- 1043417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043417 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libwraster6 Version: 0.96.0-1 Severity: grave Tags: upstream Justification: Policy 8.6.2 Hello, already communicated upstream, lets add a blocker bug. The new release bumped the symbol version of all symbols from LIBWRASTER6 to LIBWRASTER7, i.e. we have got total ABI breakage, none of the previously exported symbols are exported anymore. - ametzler@argenau:~$ wmweather+ ; echo $? wmweather+: /lib/x86_64-linux-gnu/libwraster.so.6: version `LIBWRASTER6' not found (required by wmweather+) 1 - Upstream had introduced a script for automatic symbol versioning, however given a libtool version string current:revision:age it constructs the symbol versioning from $current instead of the soname. libwraster went from 6:0:0 to 7:0:1 (no soname change). cu Andreas --- End Message --- --- Begin Message --- Source: wmaker Source-Version: 0.96.0-2 Done: Doug Torrance We believe that the bug you reported is fixed in the latest version of wmaker, 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 1043...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Doug Torrance (supplier of updated wmaker 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, 13 Aug 2023 08:48:41 -0400 Source: wmaker Built-For-Profiles: noudeb Architecture: source Version: 0.96.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Window Maker Team Changed-By: Doug Torrance Closes: 1043417 Changes: wmaker (0.96.0-2) unstable; urgency=medium . * debian/libwraster6.symbols - Drop symbol versions back to LIBWRASTER6. * debian/patches/10_libwraster6.diff - New patch; fix libwraster symbol version (Closes: #1043417). Checksums-Sha1: 75045a3bdc937436c68a8e0497bcdf4064ffd41a 2746 wmaker_0.96.0-2.dsc d4a0a36f663d83ebc31b5eef2e4c70cf162129d5 483280 wmaker_0.96.0-2.debian.tar.xz 8bb7950a376d09b932cf7a983b14532b0d46ae38 13859 wmaker_0.96.0-2_source.buildinfo Checksums-Sha256: e77ef5042504099879bf00e5cd61e59131046da4bcd6b4a6da644138492b1665 2746 wmaker_0.96.0-2.dsc 62a74dc433da25dbc9ad97ac8627cc72f4287713ad55eb4f6e7a9bb88e233501 483280 wmaker_0.96.0-2.debian.tar.xz 2ae75c1bde5382585e28719d0b58b44f212d576934639c14cde609fb9bb00870 13859 wmaker_0.96.0-2_source.buildinfo Files: ffc2b2b132fd3f06e7c28ebd4d59ebca 2746 x11 optional wmaker_0.96.0-2.dsc a40f74c290f603389f83ceebb9f3556c 483280 x11 optional wmaker_0.96.0-2.debian.tar.xz 7f80ab5b1494ee77a722d2bc823d183d 13859 x11 optional wmaker_0.96.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJJBAEBCgAzFiEEupghwS4HiU+y5K0AkdxKd57FyRAFAmTY0VoVHGR0b3JyYW5j ZUBkZWJpYW4ub3JnAAoJEJHcSneexckQ/EwP/jD98E+d+Dso8Ck47OexEkpyTPjf eogQ8GaBl6PMs6hZL2pF3Zy5XLNek4DQ/844X/eCZm51r4mCnQvrnOUPzCUgQlmg U52J6/0E7PqhvBtCCWXCt7bz43U8Tbl5ca2H2nOGLP96nZsyJJWeGICDHOZG2U11 DWh8HHV9gEh7ICdDTYLgI9ww8xFsPWWd15baue4QddY0uq1S6+55lvhijko5CSip rXTg06yKZWUdaH4yKVVhqHKoW9cp5rJGeZrEZGLEZ4sdtphhjpxCg0ocPW9oOcxf m9ePGAowTjdZr53yCC2W4TmxapyEAKjRM62WQn5m7S+hZNtzBSwj2iaDE5Yt56mI j4cgKrcYu/DI7Z1rQOneHPzUnuiTw1hojt9q6fEhXG7tKrZoWVQBB4TpWrbDRdQZ 6EceAW9BDlj3CIF3Ht3BjnRPnZc9MtR1o4sy5ALBj+qshoe+ub+4yUEUHoStdh4J sdxkqUqcM8/fJpcPloVAXI1RU30nvBTY3JpCDYDyVOpIOIVFHMsfF7xoALQoWIlj D8lhRBooNve32d6e6t2UXeupqHrIkFUx8W82FrMd5hhfaaw9fEVFGsz321y4Fk2c dhCjA4G2iam95lDe+62KQ2bDEmbyprQ92jn32MvC14qnA1WEnbF/76PFDBvDsnpf VFOvYmxLR6UNlVPP =+cMm -END PGP SIGNATURE End Message ---
Processed (with 1 error): transition: libunistring
Processing control commands: > affects -1 + src:libunistring Bug #1043599 [release.debian.org] transition: libunistring Added indication that 1043599 affects src:libunistring > forwarded -1 > https://release.debian.org/transitions/html/auto-libunistring.html Unknown command or malformed arguments to command. > block -1 by 1026820 Bug #1043599 [release.debian.org] transition: libunistring 1043599 was not blocked by any bugs. 1043599 was not blocking any bugs. Added blocking bug(s) of 1043599: 1026820 -- 1043599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043599 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037721: marked as done (libbpp-seq: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 12:43:29 + with message-id and subject line Bug#1042204: fixed in libbpp-seq 2.4.1-10 has caused the Debian Bug report #1042204, regarding libbpp-seq: ftbfs with GCC-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.) -- 1042204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-seq Version: 2.4.1-9 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libbpp-seq_2.4.1-9_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] - _ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOiEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOiEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESG_IJESt17_Rb_tree_iteratorIS5_ESt23_Rb_tree_const_iteratorIS5_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOmEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-9#
Bug#1042204: marked as done (libbpp-seq: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 12:43:29 + with message-id and subject line Bug#1042204: fixed in libbpp-seq 2.4.1-10 has caused the Debian Bug report #1042204, regarding libbpp-seq: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-seq Version: 2.4.1-9 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include/* usr/include \ > --movedev debian/tmp/usr/lib/*/cmake > usr/lib/x86_64-linux-gnu \ > debian/tmp/usr/lib/*/*.so > Library package automatic movement utility > --> libbpp-core-dev package exists. > set -e > install -d -m 755 debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-seq12/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.a > debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.so > debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.so.12 > debian/libbpp-seq12/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.so.12.0.0 > debian/libbpp-seq12/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-seq-dev > PKGSHL=libbpp-seq12 > install -d -m 755 debian/libbpp-seq-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-seq-dev/usr/include > install -d -m 755 debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbpp-seq12/DEBIAN/symbols doesn't match > completely debian/libbpp-seq12.symbols.amd64 > --- debian/libbpp-seq12.symbols.amd64 (libbpp-seq12_2.4.1-9_amd64) > +++ dpkg-gensymbolsOYBxjI 2023-07-26 19:16:14.047434493 + > @@ -4,6 +4,7 @@ > _ZN3bpp10MultiRangeImE10restrictToERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImE12filterWithinERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImE5clearEv@Base 2.4.1 > + _ZN3bpp10MultiRangeImE6clean_Ev@Base 2.4.1-9 > _ZN3bpp10MultiRangeImE8addRangeERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImED0Ev@Base 2.4.1 > _ZN3bpp10MultiRangeImED1Ev@Base 2.4.1 > @@ -83,7 +84,7 @@ > _ZN3bpp12WordAlphabetC2ERKSt6vectorIPKNS_8AlphabetESaIS4_EE@Base 2.4.1 > _ZN3bpp12WordAlphabetD0Ev@Base 2.4.1 > _ZN3bpp12WordAlphabetD1Ev@Base 2.4.1 > - _ZN3bpp13AAChargeIndexC1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp13AAChargeIndexC1Ev@Base 2.4.1 > _ZN3bpp13AAChargeIndexD0Ev@Base 2.4.1 > _ZN3bpp13AAChargeIndexD1Ev@Base 2.4.1 > _ZN3bpp13AAIndex1EntryC1ERSi@Base 2.4.1 > @@ -94,7 +95,7 @@ > _ZN3bpp13AAIndex2EntryC2ERSib@Base 2.4.1 > _ZN3bpp13AAIndex2EntryD0Ev@Base 2.4.1 > _ZN3bpp13AAIndex2EntryD1Ev@Base 2.4.1 > - _ZN3bpp13AAVolumeIndexC1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp13AAVolumeIndexC1Ev@Base 2.4.1 > _ZN3bpp13AAVolumeIndexD0Ev@Base 2.4.1 > _ZN3bpp13AAVolumeIndexD1Ev@Base 2.4.1 > > _ZN3bpp13AlphabetStateC1EiRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_@Base > 2.4.1 > @@ -186,7 +187,7 @@ > _ZN3bpp13SiteExceptionD0Ev@Base 2.4.1 > _ZN3bpp13SiteExceptionD1Ev@Base 2.4.1 > _ZN3bpp13SiteExceptionD2Ev@Base 2.4.1 > - _ZN3bpp14AASEA1030IndexC1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp14AASEA1030IndexC1Ev@Base 2.4.1 > _ZN3bpp14AASEA1030IndexD0Ev@Base 2.4.1 > _ZN3bpp14AASEA1030IndexD1Ev@Base 2.4.1 > _ZN3bpp14AASurfaceIndexD0Ev@Base 2.4.1 > @@ -221,10 +222,10 @@ > _ZN3bpp14LetterAlphabetD2Ev@Base 2.4.1 > _ZN3bpp14SequenceWalker19getSequencePositionEm@Base 2.4.1 >
Bug#1042204: marked as done (libbpp-seq: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 12:43:29 + with message-id and subject line Bug#1037721: fixed in libbpp-seq 2.4.1-10 has caused the Debian Bug report #1037721, regarding libbpp-seq: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-seq Version: 2.4.1-9 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include/* usr/include \ > --movedev debian/tmp/usr/lib/*/cmake > usr/lib/x86_64-linux-gnu \ > debian/tmp/usr/lib/*/*.so > Library package automatic movement utility > --> libbpp-core-dev package exists. > set -e > install -d -m 755 debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-seq12/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.a > debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.so > debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.so.12 > debian/libbpp-seq12/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.so.12.0.0 > debian/libbpp-seq12/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-seq-dev > PKGSHL=libbpp-seq12 > install -d -m 755 debian/libbpp-seq-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-seq-dev/usr/include > install -d -m 755 debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbpp-seq12/DEBIAN/symbols doesn't match > completely debian/libbpp-seq12.symbols.amd64 > --- debian/libbpp-seq12.symbols.amd64 (libbpp-seq12_2.4.1-9_amd64) > +++ dpkg-gensymbolsOYBxjI 2023-07-26 19:16:14.047434493 + > @@ -4,6 +4,7 @@ > _ZN3bpp10MultiRangeImE10restrictToERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImE12filterWithinERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImE5clearEv@Base 2.4.1 > + _ZN3bpp10MultiRangeImE6clean_Ev@Base 2.4.1-9 > _ZN3bpp10MultiRangeImE8addRangeERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImED0Ev@Base 2.4.1 > _ZN3bpp10MultiRangeImED1Ev@Base 2.4.1 > @@ -83,7 +84,7 @@ > _ZN3bpp12WordAlphabetC2ERKSt6vectorIPKNS_8AlphabetESaIS4_EE@Base 2.4.1 > _ZN3bpp12WordAlphabetD0Ev@Base 2.4.1 > _ZN3bpp12WordAlphabetD1Ev@Base 2.4.1 > - _ZN3bpp13AAChargeIndexC1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp13AAChargeIndexC1Ev@Base 2.4.1 > _ZN3bpp13AAChargeIndexD0Ev@Base 2.4.1 > _ZN3bpp13AAChargeIndexD1Ev@Base 2.4.1 > _ZN3bpp13AAIndex1EntryC1ERSi@Base 2.4.1 > @@ -94,7 +95,7 @@ > _ZN3bpp13AAIndex2EntryC2ERSib@Base 2.4.1 > _ZN3bpp13AAIndex2EntryD0Ev@Base 2.4.1 > _ZN3bpp13AAIndex2EntryD1Ev@Base 2.4.1 > - _ZN3bpp13AAVolumeIndexC1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp13AAVolumeIndexC1Ev@Base 2.4.1 > _ZN3bpp13AAVolumeIndexD0Ev@Base 2.4.1 > _ZN3bpp13AAVolumeIndexD1Ev@Base 2.4.1 > > _ZN3bpp13AlphabetStateC1EiRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_@Base > 2.4.1 > @@ -186,7 +187,7 @@ > _ZN3bpp13SiteExceptionD0Ev@Base 2.4.1 > _ZN3bpp13SiteExceptionD1Ev@Base 2.4.1 > _ZN3bpp13SiteExceptionD2Ev@Base 2.4.1 > - _ZN3bpp14AASEA1030IndexC1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp14AASEA1030IndexC1Ev@Base 2.4.1 > _ZN3bpp14AASEA1030IndexD0Ev@Base 2.4.1 > _ZN3bpp14AASEA1030IndexD1Ev@Base 2.4.1 > _ZN3bpp14AASurfaceIndexD0Ev@Base 2.4.1 > @@ -221,10 +222,10 @@ > _ZN3bpp14LetterAlphabetD2Ev@Base 2.4.1 > _ZN3bpp14SequenceWalker19getSequencePositionEm@Base 2.4.1 >
Bug#1037721: marked as done (libbpp-seq: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 12:43:29 + with message-id and subject line Bug#1037721: fixed in libbpp-seq 2.4.1-10 has caused the Debian Bug report #1037721, regarding libbpp-seq: ftbfs with GCC-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.) -- 1037721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-seq Version: 2.4.1-9 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libbpp-seq_2.4.1-9_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] - _ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOiEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOiEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESG_IJESt17_Rb_tree_iteratorIS5_ESt23_Rb_tree_const_iteratorIS5_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOmEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-9#
Processed: Debian bug #1026820 FTBFS: Fail to build with libunistring5
Processing commands for cont...@bugs.debian.org: > Severity 1026820 serious Bug #1026820 [src:clisp] FTBFS: Fail to build with libunistring5 Severity set to 'serious' from 'important' > -- Stopping processing here. Please contact me if you need assistance. -- 1026820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042145: marked as done (rust-rtnetlink: FTBFS: unsatisfiable build-dependencies: librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~), librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~
Your message dated Sun, 13 Aug 2023 13:20:07 +0100 with message-id and subject line re: rust-rtnetlink: FTBFS: unsatisfiable build-dependencies: librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~), librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~) has caused the Debian Bug report #1042145, regarding rust-rtnetlink: FTBFS: unsatisfiable build-dependencies: librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~), librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042145 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: rust-rtnetlink Version: 0.10.1-5 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie 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 (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-futures-0.3+default-dev (>= 0.3.11-~~), > librust-log-0.4+default-dev (>= 0.4.8-~~), > librust-netlink-packet-route-0.12+default-dev, > librust-netlink-proto-0.10+tokio-socket-dev, librust-netlink-proto-0.10-dev, > librust-nix-0+fs-dev (>= 0.24.1-~~), librust-nix-0+mount-dev (>= 0.24.1-~~), > librust-nix-0+sched-dev (>= 0.24.1-~~), librust-nix-0+signal-dev (>= > 0.24.1-~~), librust-thiserror-1+default-dev, librust-tokio-1+default-dev (>= > 1.0.1-~~), librust-tokio-1+rt-dev (>= 1.0.1-~~), build-essential, fakeroot > Filtered Build-Depends: debhelper (>= 12), dh-cargo (>= 25), cargo, rustc, > libstd-rust-dev, librust-futures-0.3+default-dev (>= 0.3.11-~~), > librust-log-0.4+default-dev (>= 0.4.8-~~), > librust-netlink-packet-route-0.12+default-dev, > librust-netlink-proto-0.10+tokio-socket-dev, librust-netlink-proto-0.10-dev, > librust-nix-0+fs-dev (>= 0.24.1-~~), librust-nix-0+mount-dev (>= 0.24.1-~~), > librust-nix-0+sched-dev (>= 0.24.1-~~), librust-nix-0+signal-dev (>= > 0.24.1-~~), librust-thiserror-1+default-dev, librust-tokio-1+default-dev (>= > 1.0.1-~~), librust-tokio-1+rt-dev (>= 1.0.1-~~), 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 [544 B] > Get:5 copy:/<>/apt_archive ./ Packages [618 B] > Fetched 2125 B in 0s (162 kB/s) > Reading package lists... > Reading package lists... > > Install main build dependencies (apt-based resolver) > > > Installing build dependencies > Reading package lists... > Building dependency tree... > 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: > librust-netlink-packet-route-dev : Depends: > librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~) but it is not > installable > librust-netlink-proto-dev : Depends: > librust-netlink-packet-core-0.4+default-dev (>= 0.4.2-~~) 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/2023/07/26/rust-rtnetlink_0.10.1-5_unstable.log All bugs filed during this archive rebuild are listed at: https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230726;users=lu...@debian.org or: https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230726=lu...@debian.org=1=1=1=1#results A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! If you reassign this bug to another package, please mark 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
Bug#1042230: marked as done (libbpp-core: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 11:34:16 + with message-id and subject line Bug#1042230: fixed in libbpp-core 2.4.1-11 has caused the Debian Bug report #1042230, regarding libbpp-core: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-core Version: 2.4.1-10 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include/* usr/include \ > --movedev debian/tmp/usr/lib/*/cmake > usr/lib/x86_64-linux-gnu \ > debian/tmp/usr/lib/*/*.so > Library package automatic movement utility > set -e > install -d -m 755 debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-core4/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-core.a > debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-core.so > debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-core.so.4 > debian/libbpp-core4/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-core.so.4.1.0 > debian/libbpp-core4/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-core-dev > PKGSHL=libbpp-core4 > install -d -m 755 debian/libbpp-core-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-core-dev/usr/include > install -d -m 755 debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbpp-core4/DEBIAN/symbols doesn't match > completely debian/libbpp-core4.symbols.amd64 > --- debian/libbpp-core4.symbols.amd64 (libbpp-core4_2.4.1-10_amd64) > +++ dpkg-gensymbolsqyy2Q2 2023-07-26 19:14:55.849755833 + > @@ -2034,7 +2034,7 @@ > _ZNKSt5ctypeIcE8do_widenEc@Base 2.4.1 > > _ZNKSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8FunctionEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE4findERS7_@Base > 2.4.1 > > _ZNKSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE4findERS7_@Base > 2.4.1 > - > _ZNKSt8_Rb_treeIdSt4pairIKddESt10_Select1stIS2_EN3bpp28AbstractDiscreteDistribution5OrderESaIS2_EE4findERS1_@Base > 2.4.1 > +#MISSING: 2.4.1-10# > _ZNKSt8_Rb_treeIdSt4pairIKddESt10_Select1stIS2_EN3bpp28AbstractDiscreteDistribution5OrderESaIS2_EE4findERS1_@Base > 2.4.1 > _ZNSt10shared_ptrIN3bpp12OutputStreamEED1Ev@Base 2.4.1 > _ZNSt10shared_ptrIN3bpp12OutputStreamEED2Ev@Base 2.4.1 > _ZNSt10unique_ptrIN3bpp15StringTokenizerESt14default_deleteIS1_EED1Ev@Base > 2.4.1 > @@ -2056,26 +2056,26 @@ > _ZNSt12_Vector_baseIN3bpp7SimplexESaIS1_EED2Ev@Base 2.4.1 > > _ZNSt12_Vector_baseINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev@Base > 2.4.1 > > _ZNSt12_Vector_baseINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base > 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp17ParameterListenerESaIS2_EED1Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp17ParameterListenerESaIS2_EED2Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp20DiscreteDistributionESaIS2_EED1Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp20DiscreteDistributionESaIS2_EED2Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp20OptimizationListenerESaIS2_EED1Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp20OptimizationListenerESaIS2_EED2Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp24BetaDiscreteDistributionESaIS2_EED1Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp24BetaDiscreteDistributionESaIS2_EED2Ev@Base
Processed: found 1043501 in 1.18.4-2
Processing commands for cont...@bugs.debian.org: > found 1043501 1.18.4-2 Bug #1043501 [src:gst-plugins-ugly1.0] gst-plugins-ugly1.0: ZDI-CAN-21443 ZDI-CAN-21444 Marked as found in versions gst-plugins-ugly1.0/1.18.4-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 1043501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 1043501 in 1.18.4-2+deb11u1, fixed 1043501 in 1.22.0-2+deb12u1
Processing commands for cont...@bugs.debian.org: > fixed 1043501 1.18.4-2+deb11u1 Bug #1043501 [src:gst-plugins-ugly1.0] gst-plugins-ugly1.0: ZDI-CAN-21443 ZDI-CAN-21444 Marked as fixed in versions gst-plugins-ugly1.0/1.18.4-2+deb11u1. > fixed 1043501 1.22.0-2+deb12u1 Bug #1043501 [src:gst-plugins-ugly1.0] gst-plugins-ugly1.0: ZDI-CAN-21443 ZDI-CAN-21444 Marked as fixed in versions gst-plugins-ugly1.0/1.22.0-2+deb12u1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1043501: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043501 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: fixed 1041110 in 14.4.2+git20190427-3.2
Processing commands for cont...@bugs.debian.org:
> fixed 1041110 14.4.2+git20190427-3.2
Bug #1041110 {Done: Bastien Roucariès } [src:sox] sox:
CVE-2023-34432
Marked as fixed in versions sox/14.4.2+git20190427-3.2.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
1041110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041110
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1042230: marked as done (libbpp-core: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042230: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042230, regarding libbpp-core: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042230: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042230 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-core Version: 2.4.1-10 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include/* usr/include \ > --movedev debian/tmp/usr/lib/*/cmake > usr/lib/x86_64-linux-gnu \ > debian/tmp/usr/lib/*/*.so > Library package automatic movement utility > set -e > install -d -m 755 debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-core4/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-core.a > debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-core.so > debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-core.so.4 > debian/libbpp-core4/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-core.so.4.1.0 > debian/libbpp-core4/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-core-dev > PKGSHL=libbpp-core4 > install -d -m 755 debian/libbpp-core-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-core-dev/usr/include > install -d -m 755 debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-core-dev/usr/lib/x86_64-linux-gnu > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbpp-core4/DEBIAN/symbols doesn't match > completely debian/libbpp-core4.symbols.amd64 > --- debian/libbpp-core4.symbols.amd64 (libbpp-core4_2.4.1-10_amd64) > +++ dpkg-gensymbolsqyy2Q2 2023-07-26 19:14:55.849755833 + > @@ -2034,7 +2034,7 @@ > _ZNKSt5ctypeIcE8do_widenEc@Base 2.4.1 > > _ZNKSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_PN3bpp8FunctionEESt10_Select1stISB_ESt4lessIS5_ESaISB_EE4findERS7_@Base > 2.4.1 > > _ZNKSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE4findERS7_@Base > 2.4.1 > - > _ZNKSt8_Rb_treeIdSt4pairIKddESt10_Select1stIS2_EN3bpp28AbstractDiscreteDistribution5OrderESaIS2_EE4findERS1_@Base > 2.4.1 > +#MISSING: 2.4.1-10# > _ZNKSt8_Rb_treeIdSt4pairIKddESt10_Select1stIS2_EN3bpp28AbstractDiscreteDistribution5OrderESaIS2_EE4findERS1_@Base > 2.4.1 > _ZNSt10shared_ptrIN3bpp12OutputStreamEED1Ev@Base 2.4.1 > _ZNSt10shared_ptrIN3bpp12OutputStreamEED2Ev@Base 2.4.1 > _ZNSt10unique_ptrIN3bpp15StringTokenizerESt14default_deleteIS1_EED1Ev@Base > 2.4.1 > @@ -2056,26 +2056,26 @@ > _ZNSt12_Vector_baseIN3bpp7SimplexESaIS1_EED2Ev@Base 2.4.1 > > _ZNSt12_Vector_baseINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED1Ev@Base > 2.4.1 > > _ZNSt12_Vector_baseINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EED2Ev@Base > 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp17ParameterListenerESaIS2_EED1Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp17ParameterListenerESaIS2_EED2Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp20DiscreteDistributionESaIS2_EED1Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp20DiscreteDistributionESaIS2_EED2Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp20OptimizationListenerESaIS2_EED1Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp20OptimizationListenerESaIS2_EED2Ev@Base 2.4.1 > - _ZNSt12_Vector_baseIPN3bpp24BetaDiscreteDistributionESaIS2_EED1Ev@Base 2.4.1 > -
Bug#1042204: marked as done (libbpp-seq: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042204: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042204, regarding libbpp-seq: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-seq Version: 2.4.1-9 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include/* usr/include \ > --movedev debian/tmp/usr/lib/*/cmake > usr/lib/x86_64-linux-gnu \ > debian/tmp/usr/lib/*/*.so > Library package automatic movement utility > --> libbpp-core-dev package exists. > set -e > install -d -m 755 debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-seq12/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.a > debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.so > debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.so.12 > debian/libbpp-seq12/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.so.12.0.0 > debian/libbpp-seq12/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-seq-dev > PKGSHL=libbpp-seq12 > install -d -m 755 debian/libbpp-seq-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-seq-dev/usr/include > install -d -m 755 debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbpp-seq12/DEBIAN/symbols doesn't match > completely debian/libbpp-seq12.symbols.amd64 > --- debian/libbpp-seq12.symbols.amd64 (libbpp-seq12_2.4.1-9_amd64) > +++ dpkg-gensymbolsOYBxjI 2023-07-26 19:16:14.047434493 + > @@ -4,6 +4,7 @@ > _ZN3bpp10MultiRangeImE10restrictToERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImE12filterWithinERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImE5clearEv@Base 2.4.1 > + _ZN3bpp10MultiRangeImE6clean_Ev@Base 2.4.1-9 > _ZN3bpp10MultiRangeImE8addRangeERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImED0Ev@Base 2.4.1 > _ZN3bpp10MultiRangeImED1Ev@Base 2.4.1 > @@ -83,7 +84,7 @@ > _ZN3bpp12WordAlphabetC2ERKSt6vectorIPKNS_8AlphabetESaIS4_EE@Base 2.4.1 > _ZN3bpp12WordAlphabetD0Ev@Base 2.4.1 > _ZN3bpp12WordAlphabetD1Ev@Base 2.4.1 > - _ZN3bpp13AAChargeIndexC1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp13AAChargeIndexC1Ev@Base 2.4.1 > _ZN3bpp13AAChargeIndexD0Ev@Base 2.4.1 > _ZN3bpp13AAChargeIndexD1Ev@Base 2.4.1 > _ZN3bpp13AAIndex1EntryC1ERSi@Base 2.4.1 > @@ -94,7 +95,7 @@ > _ZN3bpp13AAIndex2EntryC2ERSib@Base 2.4.1 > _ZN3bpp13AAIndex2EntryD0Ev@Base 2.4.1 > _ZN3bpp13AAIndex2EntryD1Ev@Base 2.4.1 > - _ZN3bpp13AAVolumeIndexC1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp13AAVolumeIndexC1Ev@Base 2.4.1 > _ZN3bpp13AAVolumeIndexD0Ev@Base 2.4.1 > _ZN3bpp13AAVolumeIndexD1Ev@Base 2.4.1 > > _ZN3bpp13AlphabetStateC1EiRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_@Base > 2.4.1 > @@ -186,7 +187,7 @@ > _ZN3bpp13SiteExceptionD0Ev@Base 2.4.1 > _ZN3bpp13SiteExceptionD1Ev@Base 2.4.1 > _ZN3bpp13SiteExceptionD2Ev@Base 2.4.1 > - _ZN3bpp14AASEA1030IndexC1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp14AASEA1030IndexC1Ev@Base 2.4.1 > _ZN3bpp14AASEA1030IndexD0Ev@Base 2.4.1 > _ZN3bpp14AASEA1030IndexD1Ev@Base 2.4.1 > _ZN3bpp14AASurfaceIndexD0Ev@Base 2.4.1 > @@ -221,10 +222,10 @@ > _ZN3bpp14LetterAlphabetD2Ev@Base 2.4.1 > _ZN3bpp14SequenceWalker19getSequencePositionEm@Base 2.4.1 >
Bug#1037721: marked as done (libbpp-seq: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042204: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042204, regarding libbpp-seq: ftbfs with GCC-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.) -- 1042204: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-seq Version: 2.4.1-9 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libbpp-seq_2.4.1-9_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] - _ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOiEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOiEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESG_IJESt17_Rb_tree_iteratorIS5_ESt23_Rb_tree_const_iteratorIS5_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOmEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-9#
Bug#1037722: marked as done (libbpp-seq-omics: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042139: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042139, regarding libbpp-seq-omics: ftbfs with GCC-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.) -- 1042139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-seq-omics Version: 2.4.1-9 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libbpp-seq-omics_2.4.1-9_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC2IS3_EEPKcRKS3_@Base 2.4.1 _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 2.4.1 @@ -568,33 +585,33 @@ _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_jESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_jESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base 2.4.1 _ZNSt8_Rb_treeIPN3bpp5RangeImEES3_St9_IdentityIS3_ENS0_10rangeComp_ImEESaIS3_EE16_M_insert_uniqueIS3_EESt4pairISt17_Rb_tree_iteratorIS3_EbEOT_@Base 2.4.1 - _ZNSt8_Rb_treeIPN3bpp5RangeImEES3_St9_IdentityIS3_ENS0_10rangeComp_ImEESaIS3_EE24_M_get_insert_unique_posERKS3_@Base 2.4.1 - _ZNSt8_Rb_treeIPN3bpp5RangeImEES3_St9_IdentityIS3_ENS0_10rangeComp_ImEESaIS3_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS3_ERKS3_@Base 2.4.1 - _ZNSt8_Rb_treeIcSt4pairIKcSt3mapImS2_ImmSt4lessImESaIS0_IKmmEEES4_SaIS0_IS5_S8_St10_Select1stISC_ES3_IcESaISC_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIcSt4pairIKcSt3mapImS2_ImmSt4lessImESaIS0_IKmmEEES4_SaIS0_IS5_S8_St10_Select1stISC_ES3_IcESaISC_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISC_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessIiESaIS8_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessIiESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKijESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKijESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 -
Bug#1042139: marked as done (libbpp-seq-omics: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042139: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042139, regarding libbpp-seq-omics: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042139: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042139 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-seq-omics Version: 2.4.1-9 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include/* usr/include \ > --movedev debian/tmp/usr/lib/*/cmake > usr/lib/x86_64-linux-gnu \ > debian/tmp/usr/lib/*/*.so > Library package automatic movement utility > --> libbpp-core-dev package exists. > --> libbpp-seq-dev package exists. > set -e > install -d -m 755 debian/libbpp-seq-omics-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-seq-omics3/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq-omics.a > debian/libbpp-seq-omics-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq-omics.so > debian/libbpp-seq-omics-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq-omics.so.3 > debian/libbpp-seq-omics3/usr/lib/x86_64-linux-gnu > mv > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq-omics.so.3.0.0 > debian/libbpp-seq-omics3/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-seq-omics-dev > PKGSHL=libbpp-seq-omics3 > install -d -m 755 debian/libbpp-seq-omics-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-seq-omics-dev/usr/include > install -d -m 755 debian/libbpp-seq-omics-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-seq-omics-dev/usr/lib/x86_64-linux-gnu > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbpp-seq-omics3/DEBIAN/symbols doesn't > match completely debian/libbpp-seq-omics3.symbols.amd64 > --- debian/libbpp-seq-omics3.symbols.amd64 (libbpp-seq-omics3_2.4.1-9_amd64) > +++ dpkg-gensymbolsaXh5dv 2023-07-26 19:16:12.508745512 + > @@ -4,6 +4,7 @@ > _ZN3bpp10MultiRangeImE10restrictToERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImE12filterWithinERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImE5clearEv@Base 2.4.1 > + _ZN3bpp10MultiRangeImE6clean_Ev@Base 2.4.1-9 > _ZN3bpp10MultiRangeImE8addRangeERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImED0Ev@Base 2.4.1 > _ZN3bpp10MultiRangeImED1Ev@Base 2.4.1 > @@ -43,7 +44,7 @@ > _ZN3bpp13AlphabetStateD0Ev@Base 2.4.1 > _ZN3bpp13AlphabetStateD1Ev@Base 2.4.1 > _ZN3bpp13BasicSequenceD0Ev@Base 2.4.1 > - _ZN3bpp13BasicSequenceD1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp13BasicSequenceD1Ev@Base 2.4.1 > _ZN3bpp13SequenceTools6subseqERKNS_8SequenceEmmRS1_@Base 2.4.1 > _ZN3bpp13SiteContainerD2Ev@Base 2.4.1 > _ZN3bpp14LetterAlphabet13registerStateEPNS_13AlphabetStateE@Base 2.4.1 > @@ -479,6 +480,8 @@ > _ZNKSt5ctypeIcE8do_widenEc@Base 2.4.1 > _ZNSt10unique_ptrIN3bpp11MafSequenceESt14default_deleteIS1_EED1Ev@Base 2.4.1 > _ZNSt10unique_ptrIN3bpp11MafSequenceESt14default_deleteIS1_EED2Ev@Base 2.4.1 > + _ZNSt10unique_ptrIN3bpp13BasicSequenceESt14default_deleteIS1_EED1Ev@Base > 2.4.1-9 > + _ZNSt10unique_ptrIN3bpp13BasicSequenceESt14default_deleteIS1_EED2Ev@Base > 2.4.1-9 > _ZNSt10unique_ptrIN3bpp13SiteContainerESt14default_deleteIS1_EED1Ev@Base > 2.4.1 > _ZNSt10unique_ptrIN3bpp13SiteContainerESt14default_deleteIS1_EED2Ev@Base > 2.4.1 > > _ZNSt10unique_ptrIN3bpp18SequenceFeatureSetESt14default_deleteIS1_EED1Ev@Base > 2.4.1 > @@ -492,20 +495,20 @@ > _ZNSt11_Deque_baseImSaImEED2Ev@Base 2.4.1 > >
Bug#1042137: marked as done (libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042137: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042137, regarding libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-phyl Version: 2.4.1-8 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include/* usr/include \ > --movedev debian/tmp/usr/lib/*/cmake > usr/lib/x86_64-linux-gnu \ > debian/tmp/usr/lib/*/*.so > Library package automatic movement utility > --> libbpp-core-dev package exists. > --> libbpp-seq-dev package exists. > set -e > install -d -m 755 debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-phyl12/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.a > debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.so > debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.so.12 > debian/libbpp-phyl12/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.so.12.0.0 > debian/libbpp-phyl12/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-phyl-dev > PKGSHL=libbpp-phyl12 > install -d -m 755 debian/libbpp-phyl-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-phyl-dev/usr/include > install -d -m 755 debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbpp-phyl12/DEBIAN/symbols doesn't match > completely debian/libbpp-phyl12.symbols.amd64 > --- debian/libbpp-phyl12.symbols.amd64 (libbpp-phyl12_2.4.1-8_amd64) > +++ dpkg-gensymbolsfyNrmd 2023-07-26 19:24:09.342489833 + > @@ -27,6 +27,7 @@ > > _ZN3bpp11MatrixTools13kroneckerMultIdEEvRKNS_6MatrixIT_EES6_RKS3_S8_RS4_b@Base > 2.4.1 > _ZN3bpp11MatrixTools13kroneckerMultIdEEvRKNS_6MatrixIT_EEmRKS3_RS4_b@Base > 2.4.1 > _ZN3bpp11MatrixTools3addINS_9RowMatrixIdEES3_EEvRT_RKT0_@Base 2.4.1 > + _ZN3bpp11MatrixTools3addINS_9RowMatrixIdEES3_dEEvRT_RT1_RKT0_@Base 2.4.1-8 > _ZN3bpp11MatrixTools3powINS_9RowMatrixIdvRKT_mRS4_@Base 2.4.1 > _ZN3bpp11MatrixTools4copyINS_9RowMatrixIdEES3_EEvRKT_RT0_@Base 2.4.1 > > _ZN3bpp11MatrixTools4multIdEEvRKNS_6MatrixIT_EERKSt6vectorIS3_SaIS3_EES6_RS4_@Base > 2.4.1 > @@ -63,6 +64,8 @@ > _ZN3bpp12LinearMatrixIdED1Ev@Base 2.4.1 > _ZN3bpp12LinearMatrixIdED2Ev@Base 2.4.1 > _ZN3bpp12LinearMatrixIdEclEmm@Base 2.4.1 > + _ZN3bpp12MutationPathC1ERKS0_@Base 2.4.1-8 > + _ZN3bpp12MutationPathC2ERKS0_@Base 2.4.1-8 > _ZN3bpp12MutationPathD0Ev@Base 2.4.1 > _ZN3bpp12MutationPathD1Ev@Base 2.4.1 > _ZN3bpp12MutationPathD2Ev@Base 2.4.1 > @@ -278,8 +281,8 @@ > _ZN3bpp13AlphabetStateD0Ev@Base 2.4.1 > _ZN3bpp13AlphabetStateD1Ev@Base 2.4.1 > > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_13CodonAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > - > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_14BinaryAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > - > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_15NucleicAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > +#MISSING: 2.4.1-8# > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_14BinaryAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > +#MISSING: 2.4.1-8# > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_15NucleicAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > >
Bug#1037718: marked as done (libbpp-phyl: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1042137: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1042137, regarding libbpp-phyl: ftbfs with GCC-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.) -- 1042137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-phyl Version: 2.4.1-8 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libbpp-phyl_2.4.1-8_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessImESaIS8_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessImESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmPN3bpp4NodeEESt10_Select1stIS5_ESt4lessImESaIS5_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESG_IJESt17_Rb_tree_iteratorIS5_ESt23_Rb_tree_const_iteratorIS5_EDpOT_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmPN3bpp4NodeEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmPN3bpp4NodeEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt3mapImSt6vectorImSaImEESt4lessImESaIS0_IS1_S5_St10_Select1stISB_ES7_SaISB_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt3mapImSt6vectorImSaImEESt4lessImESaIS0_IS1_S5_St10_Select1stISB_ES7_SaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIiSaIiEEESt10_Select1stIS5_ESt4lessImESaIS5_EE20_Reuse_or_alloc_nodeclIRKS5_EEPSt13_Rb_tree_nodeIS5_EOT_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIiSaIiEEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIiSaIiEEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 +#MISSING:
Bug#1042139: marked as done (libbpp-seq-omics: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1037722: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1037722, regarding libbpp-seq-omics: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-seq-omics Version: 2.4.1-9 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include/* usr/include \ > --movedev debian/tmp/usr/lib/*/cmake > usr/lib/x86_64-linux-gnu \ > debian/tmp/usr/lib/*/*.so > Library package automatic movement utility > --> libbpp-core-dev package exists. > --> libbpp-seq-dev package exists. > set -e > install -d -m 755 debian/libbpp-seq-omics-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-seq-omics3/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq-omics.a > debian/libbpp-seq-omics-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq-omics.so > debian/libbpp-seq-omics-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq-omics.so.3 > debian/libbpp-seq-omics3/usr/lib/x86_64-linux-gnu > mv > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq-omics.so.3.0.0 > debian/libbpp-seq-omics3/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-seq-omics-dev > PKGSHL=libbpp-seq-omics3 > install -d -m 755 debian/libbpp-seq-omics-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-seq-omics-dev/usr/include > install -d -m 755 debian/libbpp-seq-omics-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-seq-omics-dev/usr/lib/x86_64-linux-gnu > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbpp-seq-omics3/DEBIAN/symbols doesn't > match completely debian/libbpp-seq-omics3.symbols.amd64 > --- debian/libbpp-seq-omics3.symbols.amd64 (libbpp-seq-omics3_2.4.1-9_amd64) > +++ dpkg-gensymbolsaXh5dv 2023-07-26 19:16:12.508745512 + > @@ -4,6 +4,7 @@ > _ZN3bpp10MultiRangeImE10restrictToERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImE12filterWithinERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImE5clearEv@Base 2.4.1 > + _ZN3bpp10MultiRangeImE6clean_Ev@Base 2.4.1-9 > _ZN3bpp10MultiRangeImE8addRangeERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImED0Ev@Base 2.4.1 > _ZN3bpp10MultiRangeImED1Ev@Base 2.4.1 > @@ -43,7 +44,7 @@ > _ZN3bpp13AlphabetStateD0Ev@Base 2.4.1 > _ZN3bpp13AlphabetStateD1Ev@Base 2.4.1 > _ZN3bpp13BasicSequenceD0Ev@Base 2.4.1 > - _ZN3bpp13BasicSequenceD1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp13BasicSequenceD1Ev@Base 2.4.1 > _ZN3bpp13SequenceTools6subseqERKNS_8SequenceEmmRS1_@Base 2.4.1 > _ZN3bpp13SiteContainerD2Ev@Base 2.4.1 > _ZN3bpp14LetterAlphabet13registerStateEPNS_13AlphabetStateE@Base 2.4.1 > @@ -479,6 +480,8 @@ > _ZNKSt5ctypeIcE8do_widenEc@Base 2.4.1 > _ZNSt10unique_ptrIN3bpp11MafSequenceESt14default_deleteIS1_EED1Ev@Base 2.4.1 > _ZNSt10unique_ptrIN3bpp11MafSequenceESt14default_deleteIS1_EED2Ev@Base 2.4.1 > + _ZNSt10unique_ptrIN3bpp13BasicSequenceESt14default_deleteIS1_EED1Ev@Base > 2.4.1-9 > + _ZNSt10unique_ptrIN3bpp13BasicSequenceESt14default_deleteIS1_EED2Ev@Base > 2.4.1-9 > _ZNSt10unique_ptrIN3bpp13SiteContainerESt14default_deleteIS1_EED1Ev@Base > 2.4.1 > _ZNSt10unique_ptrIN3bpp13SiteContainerESt14default_deleteIS1_EED2Ev@Base > 2.4.1 > > _ZNSt10unique_ptrIN3bpp18SequenceFeatureSetESt14default_deleteIS1_EED1Ev@Base > 2.4.1 > @@ -492,20 +495,20 @@ > _ZNSt11_Deque_baseImSaImEED2Ev@Base 2.4.1 > >
Bug#1037722: marked as done (libbpp-seq-omics: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1037722: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1037722, regarding libbpp-seq-omics: ftbfs with GCC-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.) -- 1037722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037722 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-seq-omics Version: 2.4.1-9 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libbpp-seq-omics_2.4.1-9_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] _ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEC2IS3_EEPKcRKS3_@Base 2.4.1 _ZNSt7__cxx1115basic_stringbufIcSt11char_traitsIcESaIcEED0Ev@Base 2.4.1 @@ -568,33 +585,33 @@ _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_jESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_jESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base 2.4.1 _ZNSt8_Rb_treeIPN3bpp5RangeImEES3_St9_IdentityIS3_ENS0_10rangeComp_ImEESaIS3_EE16_M_insert_uniqueIS3_EESt4pairISt17_Rb_tree_iteratorIS3_EbEOT_@Base 2.4.1 - _ZNSt8_Rb_treeIPN3bpp5RangeImEES3_St9_IdentityIS3_ENS0_10rangeComp_ImEESaIS3_EE24_M_get_insert_unique_posERKS3_@Base 2.4.1 - _ZNSt8_Rb_treeIPN3bpp5RangeImEES3_St9_IdentityIS3_ENS0_10rangeComp_ImEESaIS3_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS3_ERKS3_@Base 2.4.1 - _ZNSt8_Rb_treeIcSt4pairIKcSt3mapImS2_ImmSt4lessImESaIS0_IKmmEEES4_SaIS0_IS5_S8_St10_Select1stISC_ES3_IcESaISC_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIcSt4pairIKcSt3mapImS2_ImmSt4lessImESaIS0_IKmmEEES4_SaIS0_IS5_S8_St10_Select1stISC_ES3_IcESaISC_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISC_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessIiESaIS8_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessIiESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKijESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKijESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 -
Bug#1042204: marked as done (libbpp-seq: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1037721: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1037721, regarding libbpp-seq: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-seq Version: 2.4.1-9 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include/* usr/include \ > --movedev debian/tmp/usr/lib/*/cmake > usr/lib/x86_64-linux-gnu \ > debian/tmp/usr/lib/*/*.so > Library package automatic movement utility > --> libbpp-core-dev package exists. > set -e > install -d -m 755 debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-seq12/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.a > debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.so > debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.so.12 > debian/libbpp-seq12/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-seq.so.12.0.0 > debian/libbpp-seq12/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-seq-dev > PKGSHL=libbpp-seq12 > install -d -m 755 debian/libbpp-seq-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-seq-dev/usr/include > install -d -m 755 debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-seq-dev/usr/lib/x86_64-linux-gnu > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbpp-seq12/DEBIAN/symbols doesn't match > completely debian/libbpp-seq12.symbols.amd64 > --- debian/libbpp-seq12.symbols.amd64 (libbpp-seq12_2.4.1-9_amd64) > +++ dpkg-gensymbolsOYBxjI 2023-07-26 19:16:14.047434493 + > @@ -4,6 +4,7 @@ > _ZN3bpp10MultiRangeImE10restrictToERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImE12filterWithinERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImE5clearEv@Base 2.4.1 > + _ZN3bpp10MultiRangeImE6clean_Ev@Base 2.4.1-9 > _ZN3bpp10MultiRangeImE8addRangeERKNS_5RangeImEE@Base 2.4.1 > _ZN3bpp10MultiRangeImED0Ev@Base 2.4.1 > _ZN3bpp10MultiRangeImED1Ev@Base 2.4.1 > @@ -83,7 +84,7 @@ > _ZN3bpp12WordAlphabetC2ERKSt6vectorIPKNS_8AlphabetESaIS4_EE@Base 2.4.1 > _ZN3bpp12WordAlphabetD0Ev@Base 2.4.1 > _ZN3bpp12WordAlphabetD1Ev@Base 2.4.1 > - _ZN3bpp13AAChargeIndexC1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp13AAChargeIndexC1Ev@Base 2.4.1 > _ZN3bpp13AAChargeIndexD0Ev@Base 2.4.1 > _ZN3bpp13AAChargeIndexD1Ev@Base 2.4.1 > _ZN3bpp13AAIndex1EntryC1ERSi@Base 2.4.1 > @@ -94,7 +95,7 @@ > _ZN3bpp13AAIndex2EntryC2ERSib@Base 2.4.1 > _ZN3bpp13AAIndex2EntryD0Ev@Base 2.4.1 > _ZN3bpp13AAIndex2EntryD1Ev@Base 2.4.1 > - _ZN3bpp13AAVolumeIndexC1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp13AAVolumeIndexC1Ev@Base 2.4.1 > _ZN3bpp13AAVolumeIndexD0Ev@Base 2.4.1 > _ZN3bpp13AAVolumeIndexD1Ev@Base 2.4.1 > > _ZN3bpp13AlphabetStateC1EiRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEES8_@Base > 2.4.1 > @@ -186,7 +187,7 @@ > _ZN3bpp13SiteExceptionD0Ev@Base 2.4.1 > _ZN3bpp13SiteExceptionD1Ev@Base 2.4.1 > _ZN3bpp13SiteExceptionD2Ev@Base 2.4.1 > - _ZN3bpp14AASEA1030IndexC1Ev@Base 2.4.1 > +#MISSING: 2.4.1-9# _ZN3bpp14AASEA1030IndexC1Ev@Base 2.4.1 > _ZN3bpp14AASEA1030IndexD0Ev@Base 2.4.1 > _ZN3bpp14AASEA1030IndexD1Ev@Base 2.4.1 > _ZN3bpp14AASurfaceIndexD0Ev@Base 2.4.1 > @@ -221,10 +222,10 @@ > _ZN3bpp14LetterAlphabetD2Ev@Base 2.4.1 > _ZN3bpp14SequenceWalker19getSequencePositionEm@Base 2.4.1 >
Bug#1042137: marked as done (libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1037718: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1037718, regarding libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-phyl Version: 2.4.1-8 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include/* usr/include \ > --movedev debian/tmp/usr/lib/*/cmake > usr/lib/x86_64-linux-gnu \ > debian/tmp/usr/lib/*/*.so > Library package automatic movement utility > --> libbpp-core-dev package exists. > --> libbpp-seq-dev package exists. > set -e > install -d -m 755 debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-phyl12/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.a > debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.so > debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.so.12 > debian/libbpp-phyl12/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.so.12.0.0 > debian/libbpp-phyl12/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-phyl-dev > PKGSHL=libbpp-phyl12 > install -d -m 755 debian/libbpp-phyl-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-phyl-dev/usr/include > install -d -m 755 debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbpp-phyl12/DEBIAN/symbols doesn't match > completely debian/libbpp-phyl12.symbols.amd64 > --- debian/libbpp-phyl12.symbols.amd64 (libbpp-phyl12_2.4.1-8_amd64) > +++ dpkg-gensymbolsfyNrmd 2023-07-26 19:24:09.342489833 + > @@ -27,6 +27,7 @@ > > _ZN3bpp11MatrixTools13kroneckerMultIdEEvRKNS_6MatrixIT_EES6_RKS3_S8_RS4_b@Base > 2.4.1 > _ZN3bpp11MatrixTools13kroneckerMultIdEEvRKNS_6MatrixIT_EEmRKS3_RS4_b@Base > 2.4.1 > _ZN3bpp11MatrixTools3addINS_9RowMatrixIdEES3_EEvRT_RKT0_@Base 2.4.1 > + _ZN3bpp11MatrixTools3addINS_9RowMatrixIdEES3_dEEvRT_RT1_RKT0_@Base 2.4.1-8 > _ZN3bpp11MatrixTools3powINS_9RowMatrixIdvRKT_mRS4_@Base 2.4.1 > _ZN3bpp11MatrixTools4copyINS_9RowMatrixIdEES3_EEvRKT_RT0_@Base 2.4.1 > > _ZN3bpp11MatrixTools4multIdEEvRKNS_6MatrixIT_EERKSt6vectorIS3_SaIS3_EES6_RS4_@Base > 2.4.1 > @@ -63,6 +64,8 @@ > _ZN3bpp12LinearMatrixIdED1Ev@Base 2.4.1 > _ZN3bpp12LinearMatrixIdED2Ev@Base 2.4.1 > _ZN3bpp12LinearMatrixIdEclEmm@Base 2.4.1 > + _ZN3bpp12MutationPathC1ERKS0_@Base 2.4.1-8 > + _ZN3bpp12MutationPathC2ERKS0_@Base 2.4.1-8 > _ZN3bpp12MutationPathD0Ev@Base 2.4.1 > _ZN3bpp12MutationPathD1Ev@Base 2.4.1 > _ZN3bpp12MutationPathD2Ev@Base 2.4.1 > @@ -278,8 +281,8 @@ > _ZN3bpp13AlphabetStateD0Ev@Base 2.4.1 > _ZN3bpp13AlphabetStateD1Ev@Base 2.4.1 > > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_13CodonAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > - > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_14BinaryAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > - > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_15NucleicAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > +#MISSING: 2.4.1-8# > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_14BinaryAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > +#MISSING: 2.4.1-8# > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_15NucleicAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > >
Bug#1037721: marked as done (libbpp-seq: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1037721: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1037721, regarding libbpp-seq: ftbfs with GCC-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.) -- 1037721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037721 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-seq Version: 2.4.1-9 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libbpp-seq_2.4.1-9_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] - _ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOiEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOiEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESG_IJESt17_Rb_tree_iteratorIS5_ESt23_Rb_tree_const_iteratorIS5_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmPN3bpp13SiteContainerEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOmEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmmESt10_Select1stIS2_ESt4lessImESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-9#
Bug#1042137: marked as done (libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Sun, 13 Aug 2023 10:49:57 + with message-id and subject line Bug#1037718: fixed in libbpp-phyl 2.4.1-9 has caused the Debian Bug report #1037718, regarding libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1037718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-phyl Version: 2.4.1-8 Severity: serious Justification: FTBFS Tags: trixie sid ftbfs User: lu...@debian.org Usertags: ftbfs-20230726 ftbfs-trixie Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_install > d-shlibmove --commit \ > --multiarch \ > --devunversioned \ > --exclude-la \ > --movedev debian/tmp/usr/include/* usr/include \ > --movedev debian/tmp/usr/lib/*/cmake > usr/lib/x86_64-linux-gnu \ > debian/tmp/usr/lib/*/*.so > Library package automatic movement utility > --> libbpp-core-dev package exists. > --> libbpp-seq-dev package exists. > set -e > install -d -m 755 debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-phyl12/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.a > debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.so > debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.so.12 > debian/libbpp-phyl12/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-phyl.so.12.0.0 > debian/libbpp-phyl12/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-phyl-dev > PKGSHL=libbpp-phyl12 > install -d -m 755 debian/libbpp-phyl-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-phyl-dev/usr/include > install -d -m 755 debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-phyl-dev/usr/lib/x86_64-linux-gnu > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_perl >dh_link >dh_strip_nondeterminism >dh_compress >dh_fixperms >dh_missing >dh_dwz -a >dh_strip -a >dh_makeshlibs -a > dpkg-gensymbols: warning: some new symbols appeared in the symbols file: see > diff output below > dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols > file: see diff output below > dpkg-gensymbols: warning: debian/libbpp-phyl12/DEBIAN/symbols doesn't match > completely debian/libbpp-phyl12.symbols.amd64 > --- debian/libbpp-phyl12.symbols.amd64 (libbpp-phyl12_2.4.1-8_amd64) > +++ dpkg-gensymbolsfyNrmd 2023-07-26 19:24:09.342489833 + > @@ -27,6 +27,7 @@ > > _ZN3bpp11MatrixTools13kroneckerMultIdEEvRKNS_6MatrixIT_EES6_RKS3_S8_RS4_b@Base > 2.4.1 > _ZN3bpp11MatrixTools13kroneckerMultIdEEvRKNS_6MatrixIT_EEmRKS3_RS4_b@Base > 2.4.1 > _ZN3bpp11MatrixTools3addINS_9RowMatrixIdEES3_EEvRT_RKT0_@Base 2.4.1 > + _ZN3bpp11MatrixTools3addINS_9RowMatrixIdEES3_dEEvRT_RT1_RKT0_@Base 2.4.1-8 > _ZN3bpp11MatrixTools3powINS_9RowMatrixIdvRKT_mRS4_@Base 2.4.1 > _ZN3bpp11MatrixTools4copyINS_9RowMatrixIdEES3_EEvRKT_RT0_@Base 2.4.1 > > _ZN3bpp11MatrixTools4multIdEEvRKNS_6MatrixIT_EERKSt6vectorIS3_SaIS3_EES6_RS4_@Base > 2.4.1 > @@ -63,6 +64,8 @@ > _ZN3bpp12LinearMatrixIdED1Ev@Base 2.4.1 > _ZN3bpp12LinearMatrixIdED2Ev@Base 2.4.1 > _ZN3bpp12LinearMatrixIdEclEmm@Base 2.4.1 > + _ZN3bpp12MutationPathC1ERKS0_@Base 2.4.1-8 > + _ZN3bpp12MutationPathC2ERKS0_@Base 2.4.1-8 > _ZN3bpp12MutationPathD0Ev@Base 2.4.1 > _ZN3bpp12MutationPathD1Ev@Base 2.4.1 > _ZN3bpp12MutationPathD2Ev@Base 2.4.1 > @@ -278,8 +281,8 @@ > _ZN3bpp13AlphabetStateD0Ev@Base 2.4.1 > _ZN3bpp13AlphabetStateD1Ev@Base 2.4.1 > > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_13CodonAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > - > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_14BinaryAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > - > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_15NucleicAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > +#MISSING: 2.4.1-8# > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_14BinaryAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > +#MISSING: 2.4.1-8# > _ZN3bpp13AlphabetTools20alphabetInheritsFromINS_15NucleicAlphabetEEEbPKNS_8AlphabetE@Base > 2.4.1 > >
Bug#1037718: marked as done (libbpp-phyl: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 10:50:05 + with message-id and subject line Bug#1037718: fixed in libbpp-seq-omics 2.4.1-10 has caused the Debian Bug report #1037718, regarding libbpp-phyl: ftbfs with GCC-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.) -- 1037718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-phyl Version: 2.4.1-8 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libbpp-phyl_2.4.1-8_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessImESaIS8_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessImESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmPN3bpp4NodeEESt10_Select1stIS5_ESt4lessImESaIS5_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESG_IJESt17_Rb_tree_iteratorIS5_ESt23_Rb_tree_const_iteratorIS5_EDpOT_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmPN3bpp4NodeEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmPN3bpp4NodeEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt3mapImSt6vectorImSaImEESt4lessImESaIS0_IS1_S5_St10_Select1stISB_ES7_SaISB_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt3mapImSt6vectorImSaImEESt4lessImESaIS0_IS1_S5_St10_Select1stISB_ES7_SaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIiSaIiEEESt10_Select1stIS5_ESt4lessImESaIS5_EE20_Reuse_or_alloc_nodeclIRKS5_EEPSt13_Rb_tree_nodeIS5_EOT_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIiSaIiEEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIiSaIiEEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 +#MISSING:
Bug#1037718: marked as done (libbpp-phyl: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 10:49:57 + with message-id and subject line Bug#1037718: fixed in libbpp-phyl 2.4.1-9 has caused the Debian Bug report #1037718, regarding libbpp-phyl: ftbfs with GCC-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.) -- 1037718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037718 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-phyl Version: 2.4.1-8 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/libbpp-phyl_2.4.1-8_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeIiSt4pairIKimESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessImESaIS8_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcSt10_Select1stIS8_ESt4lessImESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmPN3bpp4NodeEESt10_Select1stIS5_ESt4lessImESaIS5_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJRS1_EESG_IJESt17_Rb_tree_iteratorIS5_ESt23_Rb_tree_const_iteratorIS5_EDpOT_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmPN3bpp4NodeEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmPN3bpp4NodeEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt3mapImSt6vectorImSaImEESt4lessImESaIS0_IS1_S5_St10_Select1stISB_ES7_SaISB_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt3mapImSt6vectorImSaImEESt4lessImESaIS0_IS1_S5_St10_Select1stISB_ES7_SaISB_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISB_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIdSaIdEEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIiSaIiEEESt10_Select1stIS5_ESt4lessImESaIS5_EE20_Reuse_or_alloc_nodeclIRKS5_EEPSt13_Rb_tree_nodeIS5_EOT_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIiSaIiEEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 +#MISSING: 2.4.1-8# _ZNSt8_Rb_treeImSt4pairIKmSt6vectorIiSaIiEEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 +#MISSING:
Processed: Bug#1037718 marked as pending in libbpp-phyl
Processing control commands: > tag -1 pending Bug #1037718 [src:libbpp-phyl] libbpp-phyl: ftbfs with GCC-13 Bug #1042137 [src:libbpp-phyl] libbpp-phyl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below Added tag(s) pending. Added tag(s) pending. -- 1037718: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037718 1042137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042137 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037718: marked as pending in libbpp-phyl
Control: tag -1 pending Hello, Bug #1037718 in libbpp-phyl reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/libbpp-phyl/-/commit/38f671626f6ec730aa6efe9b7b46af5226fdc012 d/*.symbols*: mark some gcc specific symbols as optional. Closes: #1037718 (this message was generated automatically) -- Greetings https://bugs.debian.org/1037718
Bug#1041110: marked as done (sox: CVE-2023-34432)
Your message dated Sun, 13 Aug 2023 10:20:03 + with message-id <3800367.xhOnM9cPy3@portable-bastien> and subject line Fixed by fix of CVE-2021-23159 and CVE-2021-23172 has caused the Debian Bug report #1041110, regarding sox: CVE-2023-34432 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.) -- 1041110: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041110 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: sox X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for sox. CVE-2023-34432[0]: | A heap buffer overflow vulnerability was found in sox, in the | lsx_readbuf function at sox/src/formats_i.c:98:16. This flaw can | lead to a denial of service, code execution, or information | disclosure. https://bugzilla.redhat.com/show_bug.cgi?id=2212291 https://sourceforge.net/p/sox/bugs/367/ If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2023-34432 https://www.cve.org/CVERecord?id=CVE-2023-34432 Please adjust the affected versions in the BTS as needed. --- End Message --- --- Begin Message --- Hi, Bug is already fixed on debian side see fix of CVE-2021-23159 and CVE-2021-23172 signature.asc Description: This is a digitally signed message part. --- End Message ---
Processed: Re: systemd-boot postinst update causes EFI crash
Processing control commands: > severity -1 minor Bug #1043583 [systemd-boot] systemd-boot postinst update causes EFI crash Severity set to 'minor' from 'critical' > tags -1 moreinfo Bug #1043583 [systemd-boot] systemd-boot postinst update causes EFI crash Added tag(s) moreinfo. -- 1043583: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043583 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1043583: systemd-boot postinst update causes EFI crash
Control: severity -1 minor Control: tags -1 moreinfo On Sun, 13 Aug 2023 12:59:07 +0300 Maria Lisina wrote: > Package: systemd-boot > Version: 252.12-1~deb12u1 > Severity: critical > Tags: patch > Justification: breaks unrelated software > X-Debbugs-Cc: sekoohaka.sari...@gmail.com > > Dear Maintainer, when systemd-boot updates and if bootctl is- installed reports > 0, it runs bootctl update --graceful without --no-variables option. It causes > EFI crash on my machine because it doesn't support nvram. Official systemd-boot > update service has this option (/usr/lib/systemd/system/systemd-boot- > update.service:21). I think it should be added to postints too. Which hardware is that? And what does 'EFI crash' mean exactly? What's the output of 'SYSTEMD_LOG_LEVEL=debug bootctl update' ? -- Kind regards, Luca Boccassi signature.asc Description: This is a digitally signed message part
Bug#1043584: pbbam FTBFS with pbcopper 2.2.0
Source: pbbam Version: 2.1.0+dfsg-2 Severity: serious Tags: ftbfs trixie sid Forwarded: https://github.com/PacificBiosciences/pbbam/commit/1142a51493d2b047f6f8c71931ced230f593ef2b https://buildd.debian.org/status/fetch.php?pkg=pbbam=amd64=2.1.0%2Bdfsg-2%2Bb1=1691776254=0 ... FAILED: src/libpbbam.so.2.1.0.p/AlignmentPrinter.cpp.o c++ -Isrc/libpbbam.so.2.1.0.p -Isrc -I../src -Iinclude -I../include -fdiagnostics-color=always -DNDEBUG -D_FILE_OFFSET_BITS=64 -Wall -Winvalid-pch -Wextra -Wpedantic -std=c++20 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -DBOOST_ALL_NO_LIB -pthread -Wduplicated-cond -Wduplicated-branches -Wlogical-op -Wrestrict -Wnull-dereference -Wuseless-cast -Wdouble-promotion -Wshadow -Wformat=1 -MD -MQ src/libpbbam.so.2.1.0.p/AlignmentPrinter.cpp.o -MF src/libpbbam.so.2.1.0.p/AlignmentPrinter.cpp.o.d -o src/libpbbam.so.2.1.0.p/AlignmentPrinter.cpp.o -c ../src/AlignmentPrinter.cpp In file included from ../include/pbbam/AlignmentPrinter.h:6, from ../src/AlignmentPrinter.cpp:3: ../include/pbbam/BamRecord.h:1525:50: error: ‘UnmappedPosition’ is not a member of ‘PacBio::Data’; did you mean ‘PacBio::BAM::UnmappedPosition’? 1525 | mutable Data::Position alignedStart_ = Data::UnmappedPosition; | ^~~~ ...
Bug#1040960: marked as done (gcc-sh-elf binary-all build rejected)
Your message dated Sun, 13 Aug 2023 10:04:04 + with message-id and subject line Bug#1040960: fixed in gcc-sh-elf 8 has caused the Debian Bug report #1040960, regarding gcc-sh-elf binary-all build rejected 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.) -- 1040960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040960 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gcc-sh-elf Version: 7 Severity: serious Tags: ftbfs bunk@coccia:~$ cat /srv/ftp-master.debian.org/queue/reject/gcc-sh-elf_7_all-buildd.changes.reason Version check failed: Your upload included the binary package libnewlib-sh-elf-dev, version 3.3.0-1.3+7, for all, however testing already has version 3.3.0+6. Uploads to unstable must have a higher version than present in testing. bunk@coccia:~$ Fixing #996432 including the upgrade would be one way to fix this problem. --- End Message --- --- Begin Message --- Source: gcc-sh-elf Source-Version: 8 Done: John Scott We believe that the bug you reported is fixed in the latest version of gcc-sh-elf, 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 1040...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. John Scott (supplier of updated gcc-sh-elf package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 11 Aug 2023 17:57:32 -0400 Source: gcc-sh-elf Architecture: source Version: 8 Distribution: unstable Urgency: medium Maintainer: Debian Electronics Team Changed-By: John Scott Closes: 1040960 Changes: gcc-sh-elf (8) unstable; urgency=medium . * Revert the change of the previous upload (Closes: #1040960) Version numbers must increase monotonically. * As an alternative solution to record what Newlib source package was used, introduce an unofficial 'Built-Using-Newlib-Source' binary package control field. * Build depend on gcc-sh-elf when we're cross compiling the cross compiler Checksums-Sha1: d034004af9af24af2f0510d4eea02bfc2540b03f 1941 gcc-sh-elf_8.dsc 6e194da6156be207a5d6a8078770f3da1b3ab3e0 8304 gcc-sh-elf_8.tar.xz 2e09e295d6852ea919883457633abee01e9d843c 8183 gcc-sh-elf_8_amd64.buildinfo Checksums-Sha256: 34b937d189f276376b47c42865a3b4dfa106a54826cc993be2fd588ae7fc0803 1941 gcc-sh-elf_8.dsc f37d8ffc56f41cb619a2bcf30f4060daaa2d406a38c0afa11ead3fcc994b386a 8304 gcc-sh-elf_8.tar.xz cbd04b74988ec61f26cae745d6842596cf7049b8a922fc59143d2b59fa58cee9 8183 gcc-sh-elf_8_amd64.buildinfo Files: 7d76b2d56e7526b1206082e6da379139 1941 devel optional gcc-sh-elf_8.dsc 66f01da2f0b2eccbed3ca4be2b16d68d 8304 devel optional gcc-sh-elf_8.tar.xz 47944e0aeb35617d85cb578ddd673a98 8183 devel optional gcc-sh-elf_8_amd64.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAmTYp68ACgkQdCY7N/W1 +ROXPRAAyz3xw7ShR+q8OmyUgk+f1R+VGEE6W62Ra6VRan1aGBBPIT+hBZNut6qH hzMGsSfTZL9AQ2pVMKUXPqzUm7klQ2dOyIU9Q0zGIJR6wOXEHE6CVKNvvjPA1kjA tWY9uNfKRTU/oiNGmCv0RBaGTiV+bHp1zjXRLMeO67d1S5YQvWj2J0kMDkehC2jl jVG1K6cpdMUlKNA8MiJaxoCufQCSS6IaoYOAmsYpFq+nH/2LfSjgzMed+upP/QbR HJGmho911EDJmy5rrBJduGQ5rUXHxEskIP8RJHaDmnbSBcMQBW2mIMQc/wZnq5dK QbkATLN4aKHXYiAMitTMH9/cIlxb89avqwKOtfg1Vag6XDE2fHPEEv7MROWthjeL 0v6g9nDHTXC186V0OM3/NVnHp41tnmxhqAOOlwXcOcLZq31AghlO3FlrfhhIafxG zc4tS5fgVOPNwYsGXe4p3xkXszQ4mKxxcly9zejAWZz2XFYfLHOFWftXm8kTKBLH 1DULlMref+oGGn0eDtSY9bPCSXSCM0YcaI711GRLWXSSTB84Y1sSExz5F3gffgqY NXDdN4e5UgCzBk9s+IqB+57BrZhJAIfDUFYZTILu/e3aJEIuzfRIR7QtJNbFmH1t 5o059TDduoEvsOpgg5faOqyN2IGP45aiZTy2iDabHTB4epV9Kyc= =UqYy -END PGP SIGNATURE End Message ---
Bug#1037689: marked as done (hhsuite: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 10:04:13 + with message-id and subject line Bug#1037689: fixed in hhsuite 3.3.0+ds-8 has caused the Debian Bug report #1037689, regarding hhsuite: ftbfs with GCC-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.) -- 1037689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:hhsuite Version: 3.3.0+ds-7 Severity: normal Tags: sid trixie User: debian-...@lists.debian.org Usertags: ftbfs-gcc-13 [This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The severity of this report will be raised before the trixie release. The full build log can be found at: http://qa-logs.debian.net/2023/05/22/logs/hhsuite_3.3.0+ds-7_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html [...] [ 9%] Linking C static library libffindex.a cd /<>/build_plain/lib/ffindex/src && /usr/bin/cmake -P CMakeFiles/ffindex.dir/cmake_clean_target.cmake cd /<>/build_plain/lib/ffindex/src && /usr/bin/cmake -E cmake_link_script CMakeFiles/ffindex.dir/link.txt --verbose=1 make[4]: *** [src/CMakeFiles/A3M_COMPRESS.dir/build.make:79: src/CMakeFiles/A3M_COMPRESS.dir/a3m_compress.cpp.o] Error 1 make[4]: Leaving directory '/<>/build_plain' make[3]: *** [CMakeFiles/Makefile2:843: src/CMakeFiles/A3M_COMPRESS.dir/all] Error 2 make[3]: *** Waiting for unfinished jobs /usr/bin/ar qc libffindex.a CMakeFiles/ffindex.dir/ffindex.c.o CMakeFiles/ffindex.dir/ffutil.c.o [ 10%] Generating ../generated/cs219.lib.h cd /<>/data && mkdir -p /<>/build_plain/generated cd /<>/data && /<>/cmake/xxdi.pl cs219.lib > /<>/build_plain/generated/cs219.lib.h /usr/bin/ranlib libffindex.a make[4]: Leaving directory '/<>/build_plain' [ 10%] Built target ffindex [ 11%] Building CXX object src/cs/CMakeFiles/CS_OBJECTS.dir/as.cc.o cd /<>/build_plain/src/cs && /usr/bin/c++ -DOPENMP -I/<>/build_plain/generated -I/<>/src -I/<>/lib/ffindex/src -I/<>/lib/simde -I/<>/lib/simd -I/<>/build_plain/src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -include stdlib.h -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -fsigned-char -mfpmath=sse -fopenmp -fno-strict-aliasing -MD -MT src/cs/CMakeFiles/CS_OBJECTS.dir/as.cc.o -MF CMakeFiles/CS_OBJECTS.dir/as.cc.o.d -o CMakeFiles/CS_OBJECTS.dir/as.cc.o -c /<>/src/cs/as.cc cd /<>/data && /bin/sed 's!unsigned char!static const unsigned char!' < /<>/build_plain/generated/cs219.lib.h > /<>/build_plain/generated/cs219.lib.h.tmp cd /<>/data && mv -f /<>/build_plain/generated/cs219.lib.h.tmp /<>/build_plain/generated/cs219.lib.h [ 12%] Building CXX object src/cs/CMakeFiles/CS_OBJECTS.dir/assert_helpers.cc.o cd /<>/build_plain/src/cs && /usr/bin/c++ -DOPENMP -I/<>/build_plain/generated -I/<>/src -I/<>/lib/ffindex/src -I/<>/lib/simde -I/<>/lib/simd -I/<>/build_plain/src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -include stdlib.h -DSIMDE_ENABLE_OPENMP -fopenmp-simd -O3 -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++0x -fsigned-char -mfpmath=sse -fopenmp -fno-strict-aliasing -MD -MT src/cs/CMakeFiles/CS_OBJECTS.dir/assert_helpers.cc.o -MF CMakeFiles/CS_OBJECTS.dir/assert_helpers.cc.o.d -o CMakeFiles/CS_OBJECTS.dir/assert_helpers.cc.o -c /<>/src/cs/assert_helpers.cc [ 13%] Building CXX object src/cs/CMakeFiles/CS_OBJECTS.dir/blosum_matrix.cc.o cd /<>/build_plain/src/cs && /usr/bin/c++ -DOPENMP -I/<>/build_plain/generated -I/<>/src -I/<>/lib/ffindex/src -I/<>/lib/simde -I/<>/lib/simd -I/<>/build_plain/src -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -include stdlib.h -DSIMDE_ENABLE_OPENMP
Bug#1041029: marked as done (zimlib FTBFS with googletest 1.13.0)
Your message dated Sun, 13 Aug 2023 10:00:11 + with message-id and subject line Bug#1041029: fixed in libzim 8.2.1-1 has caused the Debian Bug report #1041029, regarding zimlib FTBFS with googletest 1.13.0 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.) -- 1041029: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041029 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zimlib Version: 8.1.1-0.2 Severity: serious Tags: ftbfs trixie sid Forwarded: https://github.com/openzim/libzim/issues/757 https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/zimlib.html ... /tools.cpp.o.d -o test/creator.p/tools.cpp.o -c ../test/tools.cpp In file included from /usr/include/gtest/gtest-message.h:57, from /usr/include/gtest/gtest-assertion-result.h:46, from /usr/include/gtest/gtest.h:64, from ../test/tools.cpp:36: /usr/include/gtest/internal/gtest-port.h:270:2: error: #error C++ versions less than C++14 are not supported. 270 | #error C++ versions less than C++14 are not supported. | ^ ... --- End Message --- --- Begin Message --- Source: libzim Source-Version: 8.2.1-1 Done: Kunal Mehta We believe that the bug you reported is fixed in the latest version of libzim, 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 1041...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kunal Mehta (supplier of updated libzim package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 21 Jul 2023 21:50:46 -0400 Source: libzim Binary: libzim-dev libzim8 libzim8-dbgsym Architecture: source amd64 Version: 8.2.1-1 Distribution: experimental Urgency: medium Maintainer: Kunal Mehta Changed-By: Kunal Mehta Description: libzim-dev - library implementation of ZIM specifications (development) libzim8- library implementation of ZIM specifications Closes: 1032771 1041029 Changes: libzim (8.2.1-1) experimental; urgency=medium . * New upstream version 8.2.1 * Rename source package to libzim (Closes: #1032771) * Add patch to build with c++14 (Closes: #1041029) Checksums-Sha1: 8953983871a395f0bd695b5b5645acb9717173f4 2095 libzim_8.2.1-1.dsc 952730c6e36dc0678d0aafc549891e5f3aada0af 244944 libzim_8.2.1.orig.tar.gz 4d0f2bcaf3fe27c960a35c205e86eea09b60df7f 12520 libzim_8.2.1-1.debian.tar.xz 3817a917add8e6c140473e200e7cf553bcfc0f80 29048 libzim-dev_8.2.1-1_amd64.deb 6c0eeb0d458b3f90c71728ef539259e2b272dd0b 3658424 libzim8-dbgsym_8.2.1-1_amd64.deb a85e06000b59190aefd96ff58f44a1c2e2301295 275556 libzim8_8.2.1-1_amd64.deb 95668d81fd945ac6395ee64e57cea46d42da0b14 7388 libzim_8.2.1-1_amd64.buildinfo Checksums-Sha256: 30f3609f36e5fa2d9597866d9ad98e09a672a1f6a8a122a2576e4ce109b946d6 2095 libzim_8.2.1-1.dsc b8296644b04b02c04d2ff1458fed829df39b54e8fd1bcd23c10440e160819f13 244944 libzim_8.2.1.orig.tar.gz a67887ac2a4a89c80f06340dd52ffd8eca5e3e85337054b4f024b54d7fb69ded 12520 libzim_8.2.1-1.debian.tar.xz ec6e47e598cd41623adc85a74727dff1200e2b0779d358ebd2190fd60aa42ae4 29048 libzim-dev_8.2.1-1_amd64.deb e69d34c86f3a68cbac11f217fe28563464e60f961b2560c584bf842f63406217 3658424 libzim8-dbgsym_8.2.1-1_amd64.deb 2e9c1dd32b8b879221b730daf8225c9fe7596f7e4ef962ca2ad45756c8837f21 275556 libzim8_8.2.1-1_amd64.deb 61c36d885b693fa531eb239564478f0fda3100b1784ec6ed5c3ce4e3f36bcc12 7388 libzim_8.2.1-1_amd64.buildinfo Files: 7a7428be821e77d833023ffc825deb7e 2095 libs optional libzim_8.2.1-1.dsc f75b5e4804cf4fc5293e69dabc3e11e1 244944 libs optional libzim_8.2.1.orig.tar.gz 92a19244a7f84f6e3537c8d5c0f85915 12520 libs optional libzim_8.2.1-1.debian.tar.xz 419c719be8cf7e40c0f5f4741c90c9aa 29048 libdevel optional libzim-dev_8.2.1-1_amd64.deb 2bc46b89687a5a8123ae66f4c980959b 3658424 debug optional libzim8-dbgsym_8.2.1-1_amd64.deb 72b6f153449a8f2ae3ecc5a8cbeca57e 275556 libs optional libzim8_8.2.1-1_amd64.deb d0cf0e03515ea1d6c4bef5931c92bf13 7388 libs optional libzim_8.2.1-1_amd64.buildinfo -BEGIN PGP SIGNATURE- iQJHBAEBCAAxFiEE2MtZ8F27ngU4xIGd8QX4EBsFJpsFAmS7Q10THGxlZ29rdG1A cmlzZXVwLm5ldAAKCRDxBfgQGwUmm1aVEACS1di7FdKrjSY1YUM/yEfsEzIt4ugB
Bug#1043583: systemd-boot postinst update causes EFI crash
Package: systemd-boot Version: 252.12-1~deb12u1 Severity: critical Tags: patch Justification: breaks unrelated software X-Debbugs-Cc: sekoohaka.sari...@gmail.com Dear Maintainer, when systemd-boot updates and if bootctl is-installed reports 0, it runs bootctl update --graceful without --no-variables option. It causes EFI crash on my machine because it doesn't support nvram. Official systemd-boot update service has this option (/usr/lib/systemd/system/systemd-boot- update.service:21). I think it should be added to postints too. -- System Information: Debian Release: 12.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-11-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd-boot depends on: ii libc6 2.36-9+deb12u1 ii libsystemd-shared 252.12-1~deb12u1 ii systemd-boot-efi 252.12-1~deb12u1 Versions of packages systemd-boot recommends: ii efibootmgr 17-2 systemd-boot suggests no packages. -- no debconf information --- postinst2023-08-13 12:57:31.625391255 +0300 +++ postinst.1 2023-08-13 12:57:55.169585926 +0300 @@ -14,6 +14,6 @@ fi if [ "$1" = configure ] && [ -n "$2" ] && bootctl is-installed > /dev/null 2>&1; then -bootctl update --graceful +bootctl update --no-variables --graceful fi --- postinst2023-08-13 12:57:31.625391255 +0300 +++ postinst.1 2023-08-13 12:57:55.169585926 +0300 @@ -14,6 +14,6 @@ fi if [ "$1" = configure ] && [ -n "$2" ] && bootctl is-installed > /dev/null 2>&1; then -bootctl update --graceful +bootctl update --no-variables --graceful fi
Processed: tagging 1042171
Processing commands for cont...@bugs.debian.org: > tags 1042171 + pending Bug #1042171 [src:imath] imath: FTBFS: dh_install: error: missing files, aborting Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: tagging 1042171
Processing commands for cont...@bugs.debian.org: > tags 1042171 + patch Bug #1042171 [src:imath] imath: FTBFS: dh_install: error: missing files, aborting Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1042171: imath: FTBFS: dh_install: error: missing files, aborting
Dear maintainer, On 2023-08-13 10:53, Aurelien Jarno wrote: > On 2023-07-26 22:03, Lucas Nussbaum wrote: > > Source: imath > > Version: 3.1.6-1 > > Severity: serious > > Justification: FTBFS > > Tags: trixie sid ftbfs > > User: lu...@debian.org > > Usertags: ftbfs-20230726 ftbfs-trixie > > > > Hi, > > > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > The solution to fix this is to use PYIMATH_OVERRIDE_PYTHON_INSTALL_DIR to define the installation of the Python modules instead of relying on autodetection. I have prepared a NMU for imath (versioned as 3.1.6-1.1) to fix this FTBFS, you will find the diff attached. I have uploaded DELAYED/2. Please feel free to tell me if I should delay it further or cancel it. Regards, Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net diff -Nru imath-3.1.6/debian/changelog imath-3.1.6/debian/changelog --- imath-3.1.6/debian/changelog 2023-01-21 14:17:19.0 + +++ imath-3.1.6/debian/changelog 2023-08-13 09:25:04.0 + @@ -1,3 +1,11 @@ +imath (3.1.6-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Define the Python modules installation directory using +PYIMATH_OVERRIDE_PYTHON_INSTALL_DIR. Closes: #1042171. + + -- Aurelien Jarno Sun, 13 Aug 2023 09:25:04 + + imath (3.1.6-1) unstable; urgency=medium * New upstream release diff -Nru imath-3.1.6/debian/rules imath-3.1.6/debian/rules --- imath-3.1.6/debian/rules 2023-01-21 14:16:33.0 + +++ imath-3.1.6/debian/rules 2023-08-13 09:25:03.0 + @@ -21,7 +21,8 @@ dh_auto_configure -- \ -DDOCS=$(BUILDDOC) \ -DCMAKE_BUILD_RPATH_USE_ORIGIN=ON \ - -DPYTHON=ON + -DPYTHON=ON \ + -DPYIMATH_OVERRIDE_PYTHON_INSTALL_DIR=lib/python3/dist-packages # https://github.com/AcademySoftwareFoundation/Imath/issues/226 override_dh_auto_test-arch: signature.asc Description: PGP signature
Bug#1037662: marked as done (flye: ftbfs with GCC-13)
Your message dated Sun, 13 Aug 2023 09:18:51 +
with message-id
and subject line Bug#1037662: fixed in flye 2.9.2+dfsg-2
has caused the Debian Bug report #1037662,
regarding flye: ftbfs with GCC-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.)
--
1037662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037662
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:flye
Version: 2.9.1+dfsg-1
Severity: normal
Tags: sid trixie
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-13
[This bug is targeted to the upcoming trixie 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-13/g++-13, but succeeds to build with gcc-12/g++-12. The
severity of this report will be raised before the trixie release.
The full build log can be found at:
http://qa-logs.debian.net/2023/05/22/logs/flye_2.9.1+dfsg-1_unstable_gccexp.log
The last lines of the build log are at the end of this report.
To build with GCC 13, either set CC=gcc-13 CXX=g++-13 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-13/porting_to.html
[...]
16 | class Id
| ^~
repeat_graph/../sequence/sequence_container.h:16:15: note: no known
conversion for argument 1 from ‘size_t’ {aka ‘long unsigned int’} to ‘const
FastaRecord::Id&’
repeat_graph/../sequence/sequence_container.h:16:15: note: candidate:
‘constexpr FastaRecord::Id::Id(FastaRecord::Id&&)’
repeat_graph/../sequence/sequence_container.h:16:15: note: no known
conversion for argument 1 from ‘size_t’ {aka ‘long unsigned int’} to
‘FastaRecord::Id&&’
repeat_graph/graph_processing.cpp: In lambda function:
repeat_graph/graph_processing.cpp:334:62: error: no matching function for call
to ‘FastaRecord::Id::Id(size_t)’
334 | return FastaRecord::Id(nextEdgeId - 2);
| ^
repeat_graph/../sequence/sequence_container.h:19:17: note: candidate:
‘FastaRecord::Id::Id()’
19 | Id(): _id(std::numeric_limits::max()) {}
| ^~
repeat_graph/../sequence/sequence_container.h:19:17: note: candidate expects
0 arguments, 1 provided
repeat_graph/../sequence/sequence_container.h:16:15: note: candidate:
‘constexpr FastaRecord::Id::Id(const FastaRecord::Id&)’
16 | class Id
| ^~
repeat_graph/../sequence/sequence_container.h:16:15: note: no known
conversion for argument 1 from ‘size_t’ {aka ‘long unsigned int’} to ‘const
FastaRecord::Id&’
repeat_graph/../sequence/sequence_container.h:16:15: note: candidate:
‘constexpr FastaRecord::Id::Id(FastaRecord::Id&&)’
repeat_graph/../sequence/sequence_container.h:16:15: note: no known
conversion for argument 1 from ‘size_t’ {aka ‘long unsigned int’} to
‘FastaRecord::Id&&’
repeat_graph/graph_processing.cpp:336:69: error: no matching function for call
to ‘FastaRecord::Id::Id(std::unordered_map::mapped_type&)’
336 | return FastaRecord::Id(edgeIds[path.front()->edgeId]);
| ^
repeat_graph/../sequence/sequence_container.h:19:17: note: candidate:
‘FastaRecord::Id::Id()’
19 | Id(): _id(std::numeric_limits::max()) {}
| ^~
repeat_graph/../sequence/sequence_container.h:19:17: note: candidate expects
0 arguments, 1 provided
repeat_graph/../sequence/sequence_container.h:16:15: note: candidate:
‘constexpr FastaRecord::Id::Id(const FastaRecord::Id&)’
16 | class Id
| ^~
repeat_graph/../sequence/sequence_container.h:16:15: note: no known
conversion for argument 1 from ‘std::unordered_map::mapped_type’ {aka ‘long unsigned int’} to ‘const
FastaRecord::Id&’
repeat_graph/../sequence/sequence_container.h:16:15: note: candidate:
‘constexpr FastaRecord::Id::Id(FastaRecord::Id&&)’
repeat_graph/../sequence/sequence_container.h:16:15: note: no known
conversion for argument 1 from
Bug#1042171: imath: FTBFS: dh_install: error: missing files, aborting
On 2023-08-13 10:53, Aurelien Jarno wrote:
> On 2023-07-26 22:03, Lucas Nussbaum wrote:
> > Source: imath
> > Version: 3.1.6-1
> > Severity: serious
> > Justification: FTBFS
> > Tags: trixie sid ftbfs
> > User: lu...@debian.org
> > Usertags: ftbfs-20230726 ftbfs-trixie
> >
> > Hi,
> >
> > During a rebuild of all packages in sid, your package failed to build
> > on amd64.
> >
>
> The problem has been introduced by cmake 3.27.0-1:
>
> - With cmake 3.26.4-4:
> -- Will install to: lib/python3/dist-packages
>
> - With cmake 3.27.0-1:
> -- Will install to: local/lib/python3.11/dist-packages
And more specifically, cmake 3.27 changed the value return by
Python3_SITEARCH in FindPython3.cmake from:
distutils.sysconfig.get_python_lib(plat_specific=False,standard_lib=False)
or else sysconfig.get_path('purelib')
to
sysconfig.get_path('purelib')
I believe this is due to the upcoming removal of distutils in python
3.12.
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://aurel32.net
Bug#1043417: libwraster6: libwraster ABI breakage
On 2023-08-10 "Torrance, Douglas" wrote: [...] > I've applied the patch that you submitted upstream [1] to the package. I > think this should fix the issue. See the latest draft in Salsa [2]. > Does this look okay? Thank you, yes. (As you are no doubt aware) there is a functionally identally (but different) patch in upstream GIT, let's go with this one. (Please tell me if I should make an upload.) cu Andreas -- `What a good friend you are to him, Dr. Maturin. His other friends are so grateful to you.' `I sew his ears on from time to time, sure'
Bug#1042171: imath: FTBFS: dh_install: error: missing files, aborting
On 2023-07-26 22:03, Lucas Nussbaum wrote: > Source: imath > Version: 3.1.6-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20230726 ftbfs-trixie > > Hi, > > During a rebuild of all packages in sid, your package failed to build > on amd64. > The problem has been introduced by cmake 3.27.0-1: - With cmake 3.26.4-4: -- Will install to: lib/python3/dist-packages - With cmake 3.27.0-1: -- Will install to: local/lib/python3.11/dist-packages -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
Bug#1037689: marked as pending in hhsuite
Control: tag -1 pending Hello, Bug #1037689 in hhsuite reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/hhsuite/-/commit/5538ace5c83d75ccf3bd22ef8cfa74cf9bfd819e gcc-13.patch: new: fix ftbfs with gcc 13. Closes: #1037689 (this message was generated automatically) -- Greetings https://bugs.debian.org/1037689
Processed: Bug#1037689 marked as pending in hhsuite
Processing control commands: > tag -1 pending Bug #1037689 [src:hhsuite] hhsuite: ftbfs with GCC-13 Added tag(s) pending. -- 1037689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037689 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037662: marked as pending in flye
Control: tag -1 pending Hello, Bug #1037662 in flye reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/flye/-/commit/b50fc2b3b4393d39136ea6cd9d2063ac089613b2 gcc-13.patch: new: fix ftbfs with gcc-13. Closes: #1037662 (this message was generated automatically) -- Greetings https://bugs.debian.org/1037662
Processed: Bug#1037662 marked as pending in flye
Processing control commands: > tag -1 pending Bug #1037662 [src:flye] flye: ftbfs with GCC-13 Added tag(s) pending. -- 1037662: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1035639: marked as done (git-imerge: FTBFS with tox 4)
Your message dated Sun, 13 Aug 2023 07:05:30 +
with message-id
and subject line Bug#1035639: fixed in git-imerge 1.2.0-4
has caused the Debian Bug report #1035639,
regarding git-imerge: FTBFS with tox 4
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.)
--
1035639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: git-imerge
Version: 1.2.0-3
Severity: normal
tox 4 is now available in experimental, but it causes git-imerge to
FTBFS. See bug 1035635 for a discussion of the general issues around tox
4.
Log snippet:
dh_auto_test -O--buildsystem=pybuild
I: pybuild base:240: cd /<>/.pybuild/cpython3_3.11/build; tox -c
/<>
/tox.ini --sitepackages -e py311
.pkg: install_requires .pybuild/cpython3_3.11/build> python -I -m pip install
'setuptools>=40.
8.0' wheel
.pkg: _optional_hooks .pybuild/cpython3_3.11/build> python
/usr/lib/python3/dist-packages/pypr
oject_api/_backend.py True setuptools.build_meta __legacy__
.pkg: get_requires_for_build_sdist .pybuild/cpython3_3.11/build> python
/usr/lib/python3/dist-
packages/pyproject_api/_backend.py True setuptools.build_meta __legacy__
.pkg: prepare_metadata_for_build_wheel .pybuild/cpython3_3.11/build> python
/usr/lib/python3/d
ist-packages/pyproject_api/_backend.py True setuptools.build_meta __legacy__
.pkg: build_sdist .pybuild/cpython3_3.11/build> python
/usr/lib/python3/dist-packages/pyprojec
t_api/_backend.py True setuptools.build_meta __legacy__
py311: install_package .pybuild/cpython3_3.11/build> python -I -m pip install
--force-reinstal
l --no-deps /<>/.tox/.tmp/package/1/git-imerge-1.2.0.tar.gz
py311: commands[0] .pybuild/cpython3_3.11/build> /bin/sh t/test-unconflicted
py311: failed with /bin/sh (resolves to /bin/sh) is not allowed, use
allowlist_externals to al
low it
.pkg: _exit .pybuild/cpython3_3.11/build> python
/usr/lib/python3/dist-packages/pyproject_api/
_backend.py True setuptools.build_meta __legacy__
py311: FAIL code 1 (3.44 seconds)
evaluation failed :( (3.49 seconds)
E: pybuild pybuild:388: test: plugin distutils failed with: exit code=1: cd
/<>/.pybuild/cpython3_3.11/build; tox -c /<>/tox.ini
--sitepackages -e py311
dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit
code 13
Full log attached.
Stefano
sbuild (Debian sbuild) 0.85.0 (04 January 2023) on haydn.kardiogramm.net
+==+
| git-imerge (amd64) Sat, 06 May 2023 18:51:41 + |
+==+
Package: git-imerge
Distribution: unstable
Machine Architecture: amd64
Host Architecture: amd64
Build Architecture: amd64
Build Type: binary
I: NOTICE: Log filtering will replace 'autopkgtest-virt-dummy-location' with
'<>'
I: NOTICE: Log filtering will replace 'build/git-imerge-fTmA7y/resolver-jnQhPV'
with '<>'
+--+
| Update chroot|
+--+
Get:1 http://deb.debian.org/debian unstable InRelease [188 kB]
Get:2 http://deb.debian.org/debian experimental InRelease [101 kB]
Get:3 http://deb.debian.org/debian unstable/main Sources.diff/Index [63.6 kB]
Get:4 http://deb.debian.org/debian unstable/main amd64 Packages.diff/Index
[63.6 kB]
Get:5 http://deb.debian.org/debian unstable/contrib amd64 Packages.diff/Index
[63.3 kB]
Get:6 http://deb.debian.org/debian unstable/main Sources
T-2023-05-06-1402.39-F-2023-04-30-2005.36.pdiff [44.0 kB]
Get:7 http://deb.debian.org/debian unstable/main amd64 Packages
T-2023-05-06-1402.39-F-2023-04-30-2005.36.pdiff [67.4 kB]
Get:6 http://deb.debian.org/debian unstable/main Sources
T-2023-05-06-1402.39-F-2023-04-30-2005.36.pdiff [44.0 kB]
Get:7 http://deb.debian.org/debian unstable/main amd64 Packages
T-2023-05-06-1402.39-F-2023-04-30-2005.36.pdiff [67.4 kB]
Get:8 http://deb.debian.org/debian unstable/contrib amd64 Packages
T-2023-05-05-0202.38-F-2023-04-30-2005.36.pdiff [581 B]
Get:8 http://deb.debian.org/debian unstable/contrib amd64 Packages
T-2023-05-05-0202.38-F-2023-04-30-2005.36.pdiff [581 B]
Get:9 http://deb.debian.org/debian experimental/main amd64 Packages [870 kB]
Fetched 1461 kB in 2s (782 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following packages were
