Bug#1041435: fixed in bitsnpicas 2.0+ds-2
Hey Gurkan, On Mon, 24 Jul 2023 21:40:31 +0530 Nilesh Patra wrote: Control: reopen -1 Control: retitle -1 bitsnpicas: Contains potentially non-free binary unicode data Control: found -1 2.0+ds-2 On Mon, 24 Jul 2023 13:20:33 + Debian FTP Masters wrote: > bitsnpicas (2.0+ds-2) unstable; urgency=medium > . >* Apply patch to fix usability. (Closes: #1041435) > Thank you Nilesh Patra. Thanks for applying my patch, it is atleast usable now. However, this part of the bug still remains un-fixed, which would mean potentially pushing non-free software into main. I've thus retitled the bug and reopened it. Have you contacted the upstream yet to ask if the unicode file contains non-free data or not? If not, can you open an issue? Best Nilesh
Bug#1049384: zlib: trying to overwrite '/usr/include/minizip/crypt.h', which is also in package libminizip-dev:amd64 1:1.2.13.dfsg-2
Source: zlib Version: 1:1.2.13.dfsg-2 Severity: serious Justification: makes the package in question unusable or mostly so Dear Maintainer, zlib1g-dev fails to upgrade due to a file confict with libminizip-dev: Preparing to unpack .../zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb ... Unpacking zlib1g-dev:amd64 (1:1.2.13.dfsg-2) over (1:1.2.13.dfsg-1) ... dpkg: error processing archive /var/cache/apt/archives/zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb (--unpack): trying to overwrite '/usr/include/minizip/crypt.h', which is also in package libminizip-dev:amd64 1:1.2.13.dfsg-2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/zlib1g-dev_1%3a1.2.13.dfsg-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Breaks/Replaces or Conflicts seem to be missing. Kind Regards, Bas
Bug#1039054: marked as done (miniupnpd-nftables: Fails to start: /etc/miniupnpd/nft_init.sh: 75: -f: not found)
Your message dated Tue, 15 Aug 2023 03:07:17 + with message-id and subject line Bug#1039054: fixed in miniupnpd 2.3.3-1 has caused the Debian Bug report #1039054, regarding miniupnpd-nftables: Fails to start: /etc/miniupnpd/nft_init.sh: 75: -f: not found 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.) -- 1039054: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039054 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: miniupnpd-nftables Version: 2.3.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, In the hope of fixing miniupnpd breakage on my system (different problem to #1033012 BTW), I switched from the xtables backend to nftables. Unfortunately, like miniupnpd-iptables, the systemd configuration seems to be in a "could never have worked" state. Line 75 of /etc/miniupnpd/nft_init.sh is: $NFT -f /tmp/miniupnpd.nft Nothing in miniupnpd or miniupnpd-nftables defines $NFT! Okay, so I add 'NFT=nft' to miniupnpd_functions.sh. I then discover that neither $TABLE, $NAT_TABLE, $CHAIN, $PREROUTING_CHAIN, or $POSTROUTING_CHAIN are set either. I worked around all this by setting all of the above from within miniupnpd_functions.sh, but I expect the correct fix would also take into account table/chain names specified in miniupnpd.conf -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldoldstable-updates'), (500, 'oldoldstable-debug'), (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (460, 'unstable') Architecture: i386 (i686) Kernel: Linux 6.1.0-9-686-pae (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.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 miniupnpd-nftables depends on: ii libc6 2.36-9 ii libmnl0 1.0.4-3 ii libnftnl11 1.2.4-2 miniupnpd-nftables recommends no packages. miniupnpd-nftables suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: miniupnpd Source-Version: 2.3.3-1 Done: Yangfl We believe that the bug you reported is fixed in the latest version of miniupnpd, 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 1039...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Yangfl (supplier of updated miniupnpd 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, 06 Aug 2023 07:27:24 +0800 Source: miniupnpd Architecture: source Version: 2.3.3-1 Distribution: unstable Urgency: medium Maintainer: Thomas Goirand Changed-By: Yangfl Closes: 994726 1032727 1039054 Changes: miniupnpd (2.3.3-1) unstable; urgency=medium . * New upstream release. - Fix nftables scripts (Closes: #994726). * Split miniupnpd_functions.sh for each backend. (Closes: #1039054). * Add Romanian debconf translaiton, thanks to "Remus-Gabriel Chelu" (Closes: #1032727). Checksums-Sha1: 9e3442f2ed1cdf393101e673de868a3ecdd4d47f 2416 miniupnpd_2.3.3-1.dsc 53ec4472f11f379a7539065ae6a20902271dc9dd 260079 miniupnpd_2.3.3.orig.tar.gz ae9fd2c92840a606fdcfa50d8ec5b51280bd14e6 801 miniupnpd_2.3.3.orig.tar.gz.asc fb9b1743fc95cd11ab45ff6fd10d752fd7d52a98 27944 miniupnpd_2.3.3-1.debian.tar.xz 6b25aee2aab287a571d3b75aadebc339b78f0b70 7482 miniupnpd_2.3.3-1_amd64.buildinfo Checksums-Sha256: f810c652ee28804179b97e41a37414b50639a6affdb3d3250c3360d1eeca7385 2416 miniupnpd_2.3.3-1.dsc 6fd7019f936ff88c41e7c822f46f10b51bd72d665978f6586483de75b30c36bf 260079 miniupnpd_2.3.3.orig.tar.gz 41195a6cb8c28709faef5022d14bd10527fb8ad3fc466c9db3a59b1b8326ec18 801 miniupnpd_2.3.3.orig.tar.gz.asc fdc70e405cbc8f6d8a52d7fdd05a9d40172be1714c687ad455609efc56da7c0e 27944 miniupnpd_2.3.3-1.debian.tar.xz c5846d72468a32c4b98ae6d37285fee316d5085ce727327ad96347bdcde2f28b 7482 miniupnpd_2.3.3-1_amd64.buildinfo Files: 94c066b35fbf54694718689104308cf4 2416 net optional miniupnpd_2.3.3-1.dsc e56dbbad8bc7a19dba0821737022ad88 260079 net optional miniupnpd_2.3.3.orig.tar.gz
Bug#1037841: marked as done (restinio: ftbfs with GCC-13)
Your message dated Tue, 15 Aug 2023 02:25:04 + with message-id and subject line Bug#1037841: fixed in restinio 0.6.16-1 has caused the Debian Bug report #1037841, regarding restinio: 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.) -- 1037841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037841 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:restinio Version: 0.6.16-0.2 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/restinio_0.6.16-0.2_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 [...] make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' [ 13%] Built target _test.router.express_router_pcre2_bench [ 14%] Building CXX object so_5/CMakeFiles/so_s.5.5.24.3.dir/rt/impl/mt_env_infrastructure.cpp.o cd /<>/obj-x86_64-linux-gnu/so_5 && /usr/bin/c++ -DSO_5_PRJ -DSO_5_STATIC_LIB -I/<>/dev/clara -I/<>/dev -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -MD -MT so_5/CMakeFiles/so_s.5.5.24.3.dir/rt/impl/mt_env_infrastructure.cpp.o -MF CMakeFiles/so_s.5.5.24.3.dir/rt/impl/mt_env_infrastructure.cpp.o.d -o CMakeFiles/so_s.5.5.24.3.dir/rt/impl/mt_env_infrastructure.cpp.o -c /<>/dev/so_5/rt/impl/mt_env_infrastructure.cpp [ 14%] Linking CXX executable _test.router.express_router_bench cd /<>/obj-x86_64-linux-gnu/test/router/express_router_bench && /usr/bin/cmake -E cmake_link_script CMakeFiles/_test.router.express_router_bench.dir/link.txt --verbose=1 /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-z,now CMakeFiles/_test.router.express_router_bench.dir/main.cpp.o -o _test.router.express_router_bench /usr/lib/x86_64-linux-gnu/libfmt.so.9.1.0 -lhttp_parser [ 14%] Building CXX object so_5/CMakeFiles/so_s.5.5.24.3.dir/rt/impl/simple_mtsafe_st_env_infrastructure.cpp.o cd /<>/obj-x86_64-linux-gnu/so_5 && /usr/bin/c++ -DSO_5_PRJ -DSO_5_STATIC_LIB -I/<>/dev/clara -I/<>/dev -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -MD -MT so_5/CMakeFiles/so_s.5.5.24.3.dir/rt/impl/simple_mtsafe_st_env_infrastructure.cpp.o -MF CMakeFiles/so_s.5.5.24.3.dir/rt/impl/simple_mtsafe_st_env_infrastructure.cpp.o.d -o CMakeFiles/so_s.5.5.24.3.dir/rt/impl/simple_mtsafe_st_env_infrastructure.cpp.o -c /<>/dev/so_5/rt/impl/simple_mtsafe_st_env_infrastructure.cpp make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' [ 14%] Built target _test.router.express_router_bench [ 14%] Building CXX object so_5/CMakeFiles/so_s.5.5.24.3.dir/rt/impl/simple_not_mtsafe_st_env_infrastructure.cpp.o cd /<>/obj-x86_64-linux-gnu/so_5 && /usr/bin/c++ -DSO_5_PRJ -DSO_5_STATIC_LIB -I/<>/dev/clara -I/<>/dev -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -std=gnu++14 -MD -MT so_5/CMakeFiles/so_s.5.5.24.3.dir/rt/impl/simple_not_mtsafe_st_env_infrastructure.cpp.o -MF CMakeFiles/so_s.5.5.24.3.dir/rt/impl/simple_not_mtsafe_st_env_infrastructure.cpp.o.d -o CMakeFiles/so_s.5.5.24.3.dir/rt/impl/simple_not_mtsafe_st_env_infrastructure.cpp.o -c /<>/dev/so_5/rt/impl/simple_not_mtsafe_st_env_infrastructure.cpp [ 15%] Building CXX object so_5/CMakeFiles/so_s.5.5.24.3.dir/rt/stats/repository.cpp.o cd /<>/obj-x86_64-linux-gnu/so_5 && /usr/bin/c++
Bug#1042857: coinor-libcbc3.1: Fails to install, conflicts with coinor-libcbc3:amd64
Package: coinor-libcbc3.1 Version: 2.10.10+really2.10.10+ds1-2 Followup-For: Bug #1042857 X-Debbugs-Cc: kirv...@gmail.com Dear Maintainer, I replied previously to confirm the bug, I was unable to resolve the issue at the time, but did find a way to do so before you put ds1-3 into sid: 1. Using dpkg directly: ```bash sudo dpkg -r coinor-libcbc3 ``` 2. Again, using dpkg directly after a successful removal of v3: ```bash sudo dpkg -i /var/cache/apt/archives/coinor- libcbc3.1_2.10.10+really2.10.10+ds1-2_amd64.deb ``` 3. Finally, to fix the failed upgrade: ```bash sudo apt-get --fix-broken install ``` The chain of broken dependencies for those of us that have gnome and standard- tools installed wanted to uninstall gnome and friends if using apt and going up the chain far enough: ```bash rik@devrikx:~$ sudo apt-get remove coinor-libcbc3 -f Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: coinor-libcoinmp1v5 : Depends: coinor-libcbc3.1 (>= 2.10.10+really2.10.10+ds1) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). rik@devrikx:~$ sudo apt-get remove coinor-libcoinmp1v5 Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libreoffice-calc : Depends: coinor-libcoinmp1v5 (>= 1.8.3-3) but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). rik@devrikx:~$ sudo apt-get remove libreoffice-calc coinor-libcoinmp1v5 Reading package lists... Done Building dependency tree... Done Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: gnome : Depends: libreoffice-calc but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). ``` So using dpkg directly was the only way to resolve it - perhaps aptitude could have resolved it if it was already installed, but it wasn't possible to do so with apt in the middle of a broken upgrade. I see you pushed a fix, I just thought maybe this might help someone stuck in a failed update before it moves from experimental to testing - given the circumstances. Here's the succeeded upgrade output: ```bash rik@devrikx:~$ sudo apt-get --fix-broken install Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: docker-scan-plugin g++-12 gcc-12-base:i386 gir1.2-gtkclutter-1.0 libamd2 libatk-wrapper-java libatk-wrapper-java-jni libavutil57:i386 libblockdev- crypto2 libblockdev-fs2 libblockdev-loop2 libblockdev-part-err2 libblockdev-part2 libblockdev-swap2 libblockdev-utils2 libblockdev2 libcamd2 libccolamd2 libcholmod3 libcodec2-1.0:i386 libcolamd2 libdecor-0-0:i386 libdecor-0-plugin-1-cairo:i386 libdigest-md5-file-perl libdmapsharing-3.0-2 libdraco7 libexecs0 libgdal32 libgeos3.11.1 libhttp-cookiejar-perl libixml10 libjavascriptcoregtk-5.0-0 liblc3-0 libmetis5 libossp-uuid-perl libossp-uuid16 libraw20 libre2-9 libsdl-image1.2 libsdl2-2.0-0:i386 libstdc++-12-dev libsuitesparseconfig5 libswitch-perl libumfpack5 libupnp13 libusb-1.0-0:i386 libwayland-cursor0:i386 libwayland-egl1:i386 libwebkit2gtk-5.0-0 libxcursor1:i386 libxdamage1:i386 libxi6:i386 libxkbcommon0:i386 libxrandr2:i386 libxt-dev linux-headers-6.1.0-3-amd64 linux-headers-6.1.0-3-common linux- headers-6.1.0-5-amd64 linux-headers-6.1.0-5-common linux-headers-6.1.0-6-amd64 linux-headers-6.1.0-6-common linux-headers-6.1.0-7-amd64 linux- headers-6.1.0-7-common linux-headers-6.1.0-9-amd64 linux-headers-6.1.0-9-common linux-image-6.1.0-3-amd64 linux-image-6.1.0-5-amd64 linux-image-6.1.0-6-amd64 linux-image-6.1.0-7-amd64 linux-image-6.1.0-9-amd64 linux-kbuild-6.1 python3-renderpm python3-reportlab-accel steam-devices steam-libs:i386 Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 85 not upgraded. 564 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up libpipewire-0.3-common (0.3.76-1) ... Setting up libboost-chrono1.74.0:amd64 (1.74.0+ds1-22) ... Setting up libgoa-1.0-common (3.48.0-2) ... Setting up media-types (10.1.0) ... Installing new version of config file /etc/mime.types ... Setting up libboost-system1.74.0:amd64 (1.74.0+ds1-22) ... Setting up python3-more-itertools (10.0.1-1) ... Setting up bzip2-doc (1.0.8-5) ... Setting up gcc-11-base:amd64 (11.4.0-2) ... Setting up libwayland-server0:amd64 (1.22.0-2) ... Setting up bat (0.23.0-4) ... Setting up
Bug#1037610: marked as pending in criu
Control: tag -1 pending Hello, Bug #1037610 in criu 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/debian/criu/-/commit/364ef16542af0da5e7d86b0317faeb9f644a63c2 make: disable '-Wdangling-pointer' warning with gcc 12 Closes: #1037610 (this message was generated automatically) -- Greetings https://bugs.debian.org/1037610
Processed: Bug#1037610 marked as pending in criu
Processing control commands:
> tag -1 pending
Bug #1037610 {Done: Salvatore Bonaccorso } [src:criu] criu:
ftbfs with GCC-13
Added tag(s) pending.
--
1037610: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037610
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#1049380: RM: gliv -- RoQA; unmaintained; depends on gtk2
Source: gliv Severity: serious Version: 1.9.7-2 gliv does not seem to be used a lot. 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.
Processed: Re: Bug#1049326: pandas FTBFS with numexpr 2.8.5
Processing control commands: > forwarded -1 https://github.com/pandas-dev/pandas/issues/54546 Bug #1049326 [python3-numexpr] pandas FTBFS with numexpr 2.8.5 Changed Bug forwarded-to-address to 'https://github.com/pandas-dev/pandas/issues/54546' from 'https://github.com/pandas-dev/pandas/issues/54449'. > affects -1 python3-pandas Bug #1049326 [python3-numexpr] pandas FTBFS with numexpr 2.8.5 Added indication that 1049326 affects python3-pandas -- 1049326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1049326: pandas FTBFS with numexpr 2.8.5
Control: forwarded -1 https://github.com/pandas-dev/pandas/issues/54546 Control: affects -1 python3-pandas There's actually *two* bugs here: an exception in eval/query, https://github.com/pandas-dev/pandas/issues/54449, and a changed result with integer overflow, https://github.com/pandas-dev/pandas/issues/54546. I now consider the exception non-RC, but I don't currently know whether the changed result counts as a wrong result (RC) or as something that was always undefined (not RC, disable the test). I have also checked that disabling numexpr in pandas is straightforward (though for performance reasons, I'd prefer not to), and that pandas 1.5.x is also affected (by both bugs).
Bug#1037726: marked as done (libengine-gost-openssl: ftbfs with GCC-13)
Your message dated Mon, 14 Aug 2023 21:38:58 + with message-id and subject line Bug#1037726: fixed in libengine-gost-openssl 3.0.2-1 has caused the Debian Bug report #1037726, regarding libengine-gost-openssl: 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.) -- 1037726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037726 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libengine-gost-openssl Version: 3.0.1-2 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/libengine-gost-openssl_3.0.1-2_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 [...] cd /<>/obj-x86_64-linux-gnu/libprov && /usr/bin/cmake -E cmake_link_script CMakeFiles/libprov.dir/link.txt --verbose=1 [ 26%] Building C object CMakeFiles/gost_core.dir/gost_asn1.c.o /usr/bin/cc -DHAVE_ADDCARRY_U64 -DL_ENDIAN -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-error=deprecated-declarations -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Werror -Wall -Wno-unused-parameter -Wno-unused-function -Wno-missing-braces -Wno-error=unknown-pragmas -Wno-error=pragmas -Wno-deprecated-declarations -std=gnu90 -MD -MT CMakeFiles/gost_core.dir/gost_asn1.c.o -MF CMakeFiles/gost_core.dir/gost_asn1.c.o.d -o CMakeFiles/gost_core.dir/gost_asn1.c.o -c /<>/gost_asn1.c make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' [ 27%] Linking C executable bin/test_digest [ 28%] Building C object CMakeFiles/test_tlstree.dir/test_tlstree.c.o /usr/bin/cmake -E cmake_link_script CMakeFiles/test_digest.dir/link.txt --verbose=1 /usr/bin/cc -DHAVE_ADDCARRY_U64 -DL_ENDIAN -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-error=deprecated-declarations -Wdate-time -D_FORTIFY_SOURCE=2 -Werror -Wall -Wno-unused-parameter -Wno-unused-function -Wno-missing-braces -Wno-error=unknown-pragmas -Wno-error=pragmas -Wno-deprecated-declarations -std=gnu90 -MD -MT CMakeFiles/test_tlstree.dir/test_tlstree.c.o -MF CMakeFiles/test_tlstree.dir/test_tlstree.c.o.d -o CMakeFiles/test_tlstree.dir/test_tlstree.c.o -c /<>/test_tlstree.c /usr/bin/ar qc libprov.a CMakeFiles/libprov.dir/err.c.o /usr/bin/ranlib libprov.a make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' /usr/bin/cc -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-error=deprecated-declarations -Wdate-time -D_FORTIFY_SOURCE=2 -Wl,-z,relro CMakeFiles/test_digest.dir/test_digest.c.o -o bin/test_digest /usr/lib/x86_64-linux-gnu/libcrypto.so [ 28%] Built target test_ciphers [ 30%] Building C object CMakeFiles/gost_core.dir/gost_crypt.c.o /usr/bin/cc -DHAVE_ADDCARRY_U64 -DL_ENDIAN -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-error=deprecated-declarations -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -Werror -Wall -Wno-unused-parameter -Wno-unused-function -Wno-missing-braces -Wno-error=unknown-pragmas -Wno-error=pragmas -Wno-deprecated-declarations -std=gnu90 -MD -MT CMakeFiles/gost_core.dir/gost_crypt.c.o -MF CMakeFiles/gost_core.dir/gost_crypt.c.o.d -o CMakeFiles/gost_core.dir/gost_crypt.c.o -c /<>/gost_crypt.c [ 30%] Built target libprov [ 31%] Building C object CMakeFiles/gost_core.dir/gost_keywrap.c.o /usr/bin/cc -DHAVE_ADDCARRY_U64 -DL_ENDIAN -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wno-error=deprecated-declarations -Wdate-time
Bug#1042171: marked as done (imath: FTBFS: dh_install: error: missing files, aborting)
Your message dated Mon, 14 Aug 2023 22:50:46 +0200 with message-id and subject line Re: Bug#1042171: imath: FTBFS: dh_install: error: missing files, aborting has caused the Debian Bug report #1042171, regarding imath: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1042171: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042171 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- 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. Relevant part (hopefully): > make[1]: Entering directory '/<>' > # See #1004067 > sed -i -e "s/FATAL_ERROR/STATUS/g" > debian/tmp/usr/lib/x86_64-linux-gnu/cmake/Imath/ImathConfig.cmake > sed -i -e "s/FATAL_ERROR/STATUS/g" > debian/tmp/usr/lib/x86_64-linux-gnu/cmake/Imath/ImathTargets.cmake > dh_numpy3 --package=python3-imath > dh_install -plibimath-3-1-29 > debian/tmp/usr/lib/x86_64-linux-gnu/libImath-3_1.so.29.5.0 > dh_install -plibimath-3-1-29 > debian/tmp/usr/lib/x86_64-linux-gnu/libImath-3_1.so.29 > dh_install -plibimath-dev debian/tmp/usr/lib/x86_64-linux-gnu/libImath-3_1.so > dh_install -plibimath-dev debian/tmp/usr/lib/x86_64-linux-gnu/libImath.so > dh_install -plibimath-dev debian/tmp/usr/include > dh_install -plibimath-dev debian/tmp/usr/lib/x86_64-linux-gnu/cmake/ > dh_install -plibimath-dev debian/tmp/usr/lib/x86_64-linux-gnu/pkgconfig/ > dh_install -ppython3-imath > debian/tmp/usr/lib/x86_64-linux-gnu/libPyImath_Python3_*-3_1.so > dh_install -ppython3-imath > debian/tmp/usr/lib/x86_64-linux-gnu/libPyImath_Python3_*-3_1.so.29 > dh_install -ppython3-imath > debian/tmp/usr/lib/x86_64-linux-gnu/libPyImath_Python3_*-3_1.so.29.5.0 > dh_install -ppython3-imath debian/tmp/usr/lib/python3/dist-packages/imath.so > dh_install: warning: Cannot find (any matches for) > "debian/tmp/usr/lib/python3/dist-packages/imath.so" (tried in ., debian/tmp) > > dh_install: warning: python3-imath missing files: > debian/tmp/usr/lib/python3/dist-packages/imath.so > dh_install: error: missing files, aborting > make[1]: *** [debian/rules:70: override_dh_install-arch] Error 25 The full build log is available from: http://qa-logs.debian.net/2023/07/26/imath_3.1.6-1_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 --- Dear maintainer, On 2023-08-13 19:01, Aurelien Jarno wrote: > 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. The bug has finally been fixed globally in debhelper 13.11.5, so the package now builds fine again. I have therefore cancelled the NMU and I am closing the bug with this mail. Regards Aurelien -- Aurelien Jarno GPG:
Bug#1037816: marked as done (parsinsert: ftbfs with GCC-13)
Your message dated Mon, 14 Aug 2023 20:37:09 + with message-id and subject line Bug#1037816: fixed in parsinsert 1.04-13 has caused the Debian Bug report #1037816, regarding parsinsert: 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.) -- 1037816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:parsinsert Version: 1.04-12 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/parsinsert_1.04-12_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 [...] == Insertion: [ 93086] [ 1173 sites] 0 [100%] [136346][Bacteria;Actinobacteria;Actinobacteria;Acidimicrobidae;Acidimicrobiales;Acidimicrobineae;Acidimicrobiaceae;Acidimicrobium] 0 ( 0 diffs,0 partials,0 indels) [Bacteria;Actinobacteria;Actinobacteria;Acidimicrobidae;Acidimicrobiales;Acidimicrobineae;Acidimicrobiaceae;Acidimicrobium] Assigned Taxonomy:[Bacteria;Actinobacteria;Actinobacteria;Acidimicrobidae;Acidimicrobiales;Acidimicrobineae;Acidimicrobiaceae;Acidimicrobium] Correct Taxonomy:[Archaea;Euryarchaeota;Thermoplasmata;Thermoplasmatales;Thermoplasmataceae;Thermoplasma] == Insertion: [ 93354] [ 1218 sites] 0 [100%] [136346][Bacteria;Actinobacteria;Actinobacteria;Acidimicrobidae;Acidimicrobiales;Acidimicrobineae;Acidimicrobiaceae;Acidimicrobium] 0 ( 0 diffs,0 partials,0 indels) [Bacteria;Actinobacteria;Actinobacteria;Acidimicrobidae;Acidimicrobiales;Acidimicrobineae;Acidimicrobiaceae;Acidimicrobium] Assigned Taxonomy:[Bacteria;Actinobacteria;Actinobacteria;Acidimicrobidae;Acidimicrobiales;Acidimicrobineae;Acidimicrobiaceae;Acidimicrobium] Correct Taxonomy:[Bacteria;Bacteroidetes;Sphingobacteria;Sphingobacteriales] == Insertion: [9475] [ 1283 sites] 0 [100%] [136346][Bacteria;Actinobacteria;Actinobacteria;Acidimicrobidae;Acidimicrobiales;Acidimicrobineae;Acidimicrobiaceae;Acidimicrobium] 0 ( 0 diffs,0 partials,0 indels) [Bacteria;Actinobacteria;Actinobacteria;Acidimicrobidae;Acidimicrobiales;Acidimicrobineae;Acidimicrobiaceae;Acidimicrobium] Assigned Taxonomy:[Bacteria;Actinobacteria;Actinobacteria;Acidimicrobidae;Acidimicrobiales;Acidimicrobineae;Acidimicrobiaceae;Acidimicrobium] Correct Taxonomy:[Bacteria;Proteobacteria;Gammaproteobacteria;Pasteurellales;Pasteurellaceae;Actinobacillus] == Insertion: [ 95741] [ 1280 sites] 0 [100%] [136346][Bacteria;Actinobacteria;Actinobacteria;Acidimicrobidae;Acidimicrobiales;Acidimicrobineae;Acidimicrobiaceae;Acidimicrobium] 0 ( 0 diffs,0 partials,0 indels) [Bacteria;Actinobacteria;Actinobacteria;Acidimicrobidae;Acidimicrobiales;Acidimicrobineae;Acidimicrobiaceae;Acidimicrobium] Assigned Taxonomy:[Bacteria;Actinobacteria;Actinobacteria;Acidimicrobidae;Acidimicrobiales;Acidimicrobineae;Acidimicrobiaceae;Acidimicrobium] Correct Taxonomy:[Bacteria;Proteobacteria;Alphaproteobacteria;Rhizobiales;Rhodobiaceae;Parvibaculum] ==
Bug#1049370: RM: zeitgeist-sharp -- RoQA; leaf package
Source: zeitgeist-sharp Severity: serious Version: 0.8.0.0-5.1 X-Debbugs-Cc: hyper...@debian.org zeitgeist-sharp is not used 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#1049369: RM: notify-sharp-3.0 -- RoQA; leaf package
Source: notify-sharp-3.0 Severity: serious Version: 3.0.3-3.1 X-Debbugs-Cc: hyper...@debian.org notify-sharp-3.0 is not used 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#1037816: marked as pending in parsinsert
Control: tag -1 pending Hello, Bug #1037816 in parsinsert 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/parsinsert/-/commit/cdb1ed695c967874b4fdb9732841c5bbd8d8edb7 d/rules: drop compiler optimization to -O1. This used to be done only on a handful of cpu architectures in the past, but since gcc-13, precision errors also affect amd64. Closes: #1037816 (this message was generated automatically) -- Greetings https://bugs.debian.org/1037816
Processed: Bug#1037816 marked as pending in parsinsert
Processing control commands: > tag -1 pending Bug #1037816 [src:parsinsert] parsinsert: ftbfs with GCC-13 Added tag(s) pending. -- 1037816: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037816 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: forward
Processing commands for cont...@bugs.debian.org: > forwarded 1042132 https://github.com/ruby-gnome/ruby-gnome/commit/396d2d Bug #1042132 [src:ruby-gnome] ruby-gnome: FTBFS: rbglib_bookmarkfile.c:39:1: error: static declaration of ‘g_bookmark_file_get_type’ follows non-static declaration Set Bug forwarded-to-address to 'https://github.com/ruby-gnome/ruby-gnome/commit/396d2d'. > End of message, stopping processing here. Please contact me if you need assistance. -- 1042132: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042132 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#850735: marked as done (the: FTBFS if ncurses5-config is not present)
Your message dated Mon, 14 Aug 2023 20:12:48 +0200 with message-id and subject line Really closing #850735 has caused the Debian Bug report #850735, regarding the: FTBFS if ncurses5-config is not present 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.) -- 850735: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: the Version: 3.3~rc1-3 User: ncur...@packages.debian.org Usertags: ncurses5-config The ncurses development packages are going to see a change after the Stretch release, ncurses5-config will be replaced by ncurses6-config. Your package FTBFS if ncurses5-config is not present on the build system. From my pbuilder log: , | checking for ncurses5-config... no | checking for location of ncurses.h header file... found in /usr/include | checking for location of ncurses library file... configure: error: Cannot find curses library file: ncurses; cannot configure | debian/rules:23: recipe for target 'stamp-configure' failed | make: *** [stamp-configure] Error 1 | dpkg-buildpackage: error: debian/rules build gave error exit status 2 ` It would seem that the checks in common/accommon.m4 need to be adjusted and the configure script regenerated. However, as your package does not currently run autoreconf to do so, nor does it use debhelper which would make it feasible to run dh_autoreconf from debian/rules, I'm afraid I cannot come up with a patch. :-( --- End Message --- --- Begin Message --- Version: 3.3~rc1-3.2 Format: 1.8 Date: Fri, 04 Aug 2023 23:54:22 +0200 Source: the Architecture: source Version: 3.3~rc1-3.2 Distribution: unstable Urgency: medium Maintainer: Alen Zekulic Changed-By: Chris Hofstaedtler Changes: the (3.3~rc1-3.2) unstable; urgency=medium . * Non-maintainer upload. * Patch configure, common/accommon.m4 to use ncurses6-config instead of ncurses5-config. Adjust Build-Depends to libncurses-dev. (Closees: #850735) * Turn off custom compression in debian/source/options.--- End Message ---
Processed: [bts-link] source package src:vimix
Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package src:vimix > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting user to debian-bts-l...@lists.debian.org (was debian-bts-l...@lists.debian.org). > # remote status report for #1037883 (http://bugs.debian.org/1037883) > # Bug title: vimix: ftbfs with GCC-13 > # * https://github.com/brunoherbelin/vimix/issues/100 > # * remote status changed: open -> closed > # * closed upstream > tags 1037883 + fixed-upstream Bug #1037883 [src:vimix] vimix: ftbfs with GCC-13 Added tag(s) fixed-upstream. > usertags 1037883 - status-open Usertags were: status-open. There are now no usertags set. > usertags 1037883 + status-closed There were no usertags set. Usertags are now: status-closed. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037883: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037883 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1028567: marked as done (acetoneiso: should not download and run random binaries off the internet)
Your message dated Mon, 14 Aug 2023 16:03:55 +
with message-id
and subject line Bug#1028567: fixed in acetoneiso 2.4-4
has caused the Debian Bug report #1028567,
regarding acetoneiso: should not download and run random binaries off the
internet
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.)
--
1028567: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: acetoneiso
Version: 2.4-3
Severity: serious
Tags: security
While looking through the code to see about replacing youtube-dl
(#1024231), I noticed the following in acetoneiso/sources/utube.h's
metacafe() function:
if (system ("cd $HOME/.acetoneiso/;wget
> /dev/null
2>&1")) {
yutubbodl.setPermissions(QFile::ReadOwner | QFile::WriteOwner |
QFile::ExeOwner | QFile::ExeGroup | QFile::ReadGroup | QFile::ReadOther
| QFile::ExeOther);
[...]
QFile utube_file( acetone_bin.path() + "/metacafe-dl");
[...]
UTube->start( utube_file.fileName(), QStringList() << "-o" <<
file << text );
Perhaps I'm wrong, but this appears to download and run whatever
is. That web
server no longer appears to be reachable, but that could be anything
and is not guaranteed to be DFSG-compliant and could even do something
malicious - we don't know.
That should probably be patched out of the program.
--- End Message ---
--- Begin Message ---
Source: acetoneiso
Source-Version: 2.4-4
Done: Bastian Germann
We believe that the bug you reported is fixed in the latest version of
acetoneiso, 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.
Bastian Germann (supplier of updated acetoneiso 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: Mon, 14 Aug 2023 17:05:46 +0200
Source: acetoneiso
Architecture: source
Version: 2.4-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group
Changed-By: Bastian Germann
Closes: 889752 1024231 1028567
Changes:
acetoneiso (2.4-4) unstable; urgency=medium
.
* QA upload
* Suggest yt-dlp (Closes: #1024231)
* Drop Vcs fields
* Neutralize the MetaCafe download (Closes: #1028567)
.
[ Dmitry Shachnev ]
* debian/rules: Export QMAKE that is set by cdbs. This is needed for
lrelease to work properly on cross builds (Closes: #889752)
Checksums-Sha1:
9e5f9cfb8e62abf576a0372bb08358e8bb98c6ed 1612 acetoneiso_2.4-4.dsc
7dae76273b2cdd5ecf5cc26b5c2d6d6b6857212a 244156 acetoneiso_2.4-4.debian.tar.xz
19b4492446b3ca4563f8608c823601e798c3fb2a 15157
acetoneiso_2.4-4_source.buildinfo
Checksums-Sha256:
a7130e5e891cf846940ab1d2768636f9b671c4671a471afc952da32c23408a52 1612
acetoneiso_2.4-4.dsc
a37e2f7581e78b34c815503ca11cdfae4810d2943af1ff68212192a90ad59124 244156
acetoneiso_2.4-4.debian.tar.xz
8af56b8c20344faf5cd7e03ab7411eb3ac1721938d852e904aadc521ed7d768a 15157
acetoneiso_2.4-4_source.buildinfo
Files:
8a4d804c9e15a32854f918d0d42b1482 1612 otherosfs optional acetoneiso_2.4-4.dsc
137b4f009dce7856ab42bf699f9a6adb 244156 otherosfs optional
acetoneiso_2.4-4.debian.tar.xz
752a8f790dd424ee340347c71c2953e5 15157 otherosfs optional
acetoneiso_2.4-4_source.buildinfo
-BEGIN PGP SIGNATURE-
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmTaS1AQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFLeaC/4i3AZqapu0RNkcZsf1zIPSOqBysCIO+Y9y
TXWmLVhVJdva4jEO9VRUb2op5Og12/u8JeyF1TgBhMV5CX9pNAqkyqhSq0BXWV4W
OftfM0Yin2ngUBV+NOc1L4et3YM5M6Lc/r1TYhLl93rRcrtK9Mm+lOv3aTWgbT/N
VWsLaYVg5jA8gIAu2VYqSofGzyUcnjAfwUlPqTkBg+dLndFU8SKoR0IyFG+Ytqyi
OPR7lZ3bBZ7vfi0qeVum12/O2QwFgZPCWDS8dUiXIVHgJATBoGW8efJh8dhykGHB
7dxJ92vCo8s/uvJLzVmJ48TM4xqFaKnnsgDVxSZK12EzoZI954kyxm1LCCBbWXfh
Rt5y4WKqtZ4j1ZX6PPelfp0AdYY+pmN1mIYCsIcUbMzZTxPKG6sjpG2+A0x4eLtA
hTPVLS3eLe/TK3LJmSKtw9sxQaEuIWsSQZrGZcFOnyni9NErtPanZJadsTyplqGa
5OlVHd7oy2Qyr7RGU3Y2G4HgOLsCrhg=
=OF4C
-END PGP SIGNATURE End Message ---
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 Mon, 14 Aug 2023 15:04:41 + with message-id and subject line Bug#1037742: fixed in libssw 1.2.5-1 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.2.5-1 Done: Andreas Tille 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. Andreas Tille (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: SHA256 Format: 1.8 Date: Sat, 15 Jul 2023 12:56:57 +0200 Source: libssw Architecture: source Version: 1.2.5-1 Distribution: experimental Urgency: medium Maintainer: Debian
Bug#1037742: marked as done (libssw: ftbfs with GCC-13)
Your message dated Mon, 14 Aug 2023 15:04:41 + with message-id and subject line Bug#1037742: fixed in libssw 1.2.5-1 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#1037731: marked as done (libncl: ftbfs with GCC-13)
Your message dated Mon, 14 Aug 2023 14:39:45 + with message-id and subject line Bug#1042131: fixed in libncl 2.1.21+git20210811.b1213a7-5 has caused the Debian Bug report #1042131, regarding libncl: 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.) -- 1042131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libncl Version: 2.1.21+git20210811.b1213a7-4 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/libncl_2.1.21+git20210811.b1213a7-4_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.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIcSt4pairIKc9NxsStringESt10_Select1stIS3_ESt4lessIcESaIS3_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS3_ERS1_@Base 2.1.18 (optional)_ZNSt8_Rb_treeIccSt9_IdentityIcESt4lessIcESaIcEE16_M_insert_uniqueIRKcEESt4pairISt17_Rb_tree_iteratorIcEbEOT_@Base 2.1.21+git20171002.4becff7 - _ZNSt8_Rb_treeIccSt9_IdentityIcESt4lessIcESaIcEE24_M_get_insert_unique_posERKc@Base 2.1.18 - _ZNSt8_Rb_treeIccSt9_IdentityIcESt4lessIcESaIcEE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIcERKc@Base 2.1.18 - _ZNSt8_Rb_treeIiSt4pairIKiNSt7__cxx114listIP8NxsBlockSaIS5_St10_Select1stIS8_ESt4lessIiESaIS8_EE24_M_get_insert_unique_posERS1_@Base 2.1.21+git20190531.feceb81 - _ZNSt8_Rb_treeIiSt4pairIKiNSt7__cxx114listIP8NxsBlockSaIS5_St10_Select1stIS8_ESt4lessIiESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS1_@Base 2.1.18 - (optional)_ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.1.21+git20171002.4becff7 +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIccSt9_IdentityIcESt4lessIcESaIcEE24_M_get_insert_unique_posERKc@Base 2.1.18 +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIccSt9_IdentityIcESt4lessIcESaIcEE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIcERKc@Base 2.1.18 +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIiSt4pairIKiNSt7__cxx114listIP8NxsBlockSaIS5_St10_Select1stIS8_ESt4lessIiESaIS8_EE24_M_get_insert_unique_posERS1_@Base 2.1.21+git20190531.feceb81 +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIiSt4pairIKiNSt7__cxx114listIP8NxsBlockSaIS5_St10_Select1stIS8_ESt4lessIiESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS1_@Base 2.1.18 +#MISSING: 2.1.21+git20210811.b1213a7-4# (optional)_ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.1.21+git20171002.4becff7 _ZNSt8_Rb_treeIiiSt9_IdentityIiESt4lessIiESaIiEE16_M_insert_uniqueIRKiEESt4pairISt17_Rb_tree_iteratorIiEbEOT_@Base 2.1.18 _ZNSt8_Rb_treeIiiSt9_IdentityIiESt4lessIiESaIiEE16_M_insert_uniqueIiEESt4pairISt17_Rb_tree_iteratorIiEbEOT_@Base 2.1.18 - _ZNSt8_Rb_treeIiiSt9_IdentityIiESt4lessIiESaIiEE24_M_get_insert_unique_posERKi@Base 2.1.18 - _ZNSt8_Rb_treeIiiSt9_IdentityIiESt4lessIiESaIiEE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIiERKi@Base 2.1.18 +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIiiSt9_IdentityIiESt4lessIiESaIiEE24_M_get_insert_unique_posERKi@Base 2.1.18 +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIiiSt9_IdentityIiESt4lessIiESaIiEE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIiERKi@Base 2.1.18
Bug#1042131: marked as done (libncl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Mon, 14 Aug 2023 14:39:45 + with message-id and subject line Bug#1042131: fixed in libncl 2.1.21+git20210811.b1213a7-5 has caused the Debian Bug report #1042131, regarding libncl: 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.) -- 1042131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libncl Version: 2.1.21+git20210811.b1213a7-4 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 \ > --movedev "debian/tmp/usr/include/ncl/*.h" usr/include/ncl \ > --movedev "debian/tmp/usr/lib/*/pkgconfig/*.pc" > usr/lib/x86_64-linux-gnu/pkgconfig \ > debian/tmp/usr/lib/*/libncl.so > Library package automatic movement utility > set -e > install -d -m 755 debian/libncl-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libncl2/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libncl.a > debian/libncl-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libncl.la > debian/libncl-dev/usr/lib/x86_64-linux-gnu || true > mv debian/tmp/usr/lib/x86_64-linux-gnu/libncl.so > debian/libncl-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libncl.so.2 > debian/libncl2/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libncl.so.2.0.0 > debian/libncl2/usr/lib/x86_64-linux-gnu > PKGDEV=libncl-dev > PKGSHL=libncl2 > install -d -m 755 debian/libncl-dev/usr/include/ncl > mv debian/tmp/usr/include/ncl/*.h debian/libncl-dev/usr/include/ncl > install -d -m 755 debian/libncl-dev/usr/lib/x86_64-linux-gnu/pkgconfig > mv debian/tmp/usr/lib/*/pkgconfig/*.pc > debian/libncl-dev/usr/lib/x86_64-linux-gnu/pkgconfig > rm -f debian/tmp/usr/include/ncl/nxsblock.cpp > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_installman >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/libncl2/DEBIAN/symbols doesn't match > completely debian/libncl2.symbols.amd64 > --- debian/libncl2.symbols.amd64 (libncl2_2.1.21+git20210811.b1213a7-4_amd64) > +++ dpkg-gensymbols69MeWU 2023-07-26 19:21:48.602263023 + > @@ -201,8 +201,8 @@ > _ZN17NxsUnalignedBlockD2Ev@Base 2.1.18 > _ZN17ProcessedNxsToken14ParseSimpleCmdERKSt6vectorIS_SaIS_EEb@Base 2.1.18 > > _ZN17ProcessedNxsToken16IncrementNotLastERN9__gnu_cxx17__normal_iteratorIPKS_St6vectorIS_SaIS_RKS7_PKc@Base > 2.1.18 > - _ZN17ProcessedNxsTokenD1Ev@Base 2.1.18 > - _ZN17ProcessedNxsTokenD2Ev@Base 2.1.18 > +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZN17ProcessedNxsTokenD1Ev@Base > 2.1.18 > +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZN17ProcessedNxsTokenD2Ev@Base > 2.1.18 > _ZN17PublicNexusReader10AddFactoryEP15NxsBlockFactory@Base 2.1.18 > _ZN17PublicNexusReader12ClearContentEv@Base 2.1.18 > > _ZN17PublicNexusReader12RegisterTaxaERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS6_EE@Base > 2.1.18 > @@ -377,8 +377,8 @@ > _ZN21NxsTaxaBlockSurrogate21HandleLinkTaxaCommandER8NxsToken@Base 2.1.18 > _ZN21NxsTaxaBlockSurrogate30CopyTaxaBlockSurrogateContentsERKS_@Base 2.1.18 > > _ZN21NxsTaxaBlockSurrogate32SurrogateSwapEquivalentTaxaBlockEP15NxsTaxaBlockAPI@Base > 2.1.18 > - _ZN22NxsFullTreeDescriptionD1Ev@Base 2.1.18 > - _ZN22NxsFullTreeDescriptionD2Ev@Base 2.1.18 > +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZN22NxsFullTreeDescriptionD1Ev@Base > 2.1.18 > +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZN22NxsFullTreeDescriptionD2Ev@Base > 2.1.18 > _ZN22NxsGeneticCodesManagerC1Ev@Base 2.1.18 > _ZN22NxsGeneticCodesManagerC2Ev@Base 2.1.18 > > _ZN23NxsLabelToIndicesMapper14AppendNewLabelERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 2.1.18 > @@ -462,8 +462,8 @@ >
Bug#1042131: marked as done (libncl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Mon, 14 Aug 2023 14:39:45 + with message-id and subject line Bug#1037731: fixed in libncl 2.1.21+git20210811.b1213a7-5 has caused the Debian Bug report #1037731, regarding libncl: 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.) -- 1037731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libncl Version: 2.1.21+git20210811.b1213a7-4 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 \ > --movedev "debian/tmp/usr/include/ncl/*.h" usr/include/ncl \ > --movedev "debian/tmp/usr/lib/*/pkgconfig/*.pc" > usr/lib/x86_64-linux-gnu/pkgconfig \ > debian/tmp/usr/lib/*/libncl.so > Library package automatic movement utility > set -e > install -d -m 755 debian/libncl-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libncl2/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libncl.a > debian/libncl-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libncl.la > debian/libncl-dev/usr/lib/x86_64-linux-gnu || true > mv debian/tmp/usr/lib/x86_64-linux-gnu/libncl.so > debian/libncl-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libncl.so.2 > debian/libncl2/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libncl.so.2.0.0 > debian/libncl2/usr/lib/x86_64-linux-gnu > PKGDEV=libncl-dev > PKGSHL=libncl2 > install -d -m 755 debian/libncl-dev/usr/include/ncl > mv debian/tmp/usr/include/ncl/*.h debian/libncl-dev/usr/include/ncl > install -d -m 755 debian/libncl-dev/usr/lib/x86_64-linux-gnu/pkgconfig > mv debian/tmp/usr/lib/*/pkgconfig/*.pc > debian/libncl-dev/usr/lib/x86_64-linux-gnu/pkgconfig > rm -f debian/tmp/usr/include/ncl/nxsblock.cpp > make[1]: Leaving directory '/<>' >dh_installdocs >dh_installchangelogs >dh_installman >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/libncl2/DEBIAN/symbols doesn't match > completely debian/libncl2.symbols.amd64 > --- debian/libncl2.symbols.amd64 (libncl2_2.1.21+git20210811.b1213a7-4_amd64) > +++ dpkg-gensymbols69MeWU 2023-07-26 19:21:48.602263023 + > @@ -201,8 +201,8 @@ > _ZN17NxsUnalignedBlockD2Ev@Base 2.1.18 > _ZN17ProcessedNxsToken14ParseSimpleCmdERKSt6vectorIS_SaIS_EEb@Base 2.1.18 > > _ZN17ProcessedNxsToken16IncrementNotLastERN9__gnu_cxx17__normal_iteratorIPKS_St6vectorIS_SaIS_RKS7_PKc@Base > 2.1.18 > - _ZN17ProcessedNxsTokenD1Ev@Base 2.1.18 > - _ZN17ProcessedNxsTokenD2Ev@Base 2.1.18 > +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZN17ProcessedNxsTokenD1Ev@Base > 2.1.18 > +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZN17ProcessedNxsTokenD2Ev@Base > 2.1.18 > _ZN17PublicNexusReader10AddFactoryEP15NxsBlockFactory@Base 2.1.18 > _ZN17PublicNexusReader12ClearContentEv@Base 2.1.18 > > _ZN17PublicNexusReader12RegisterTaxaERKSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS6_EE@Base > 2.1.18 > @@ -377,8 +377,8 @@ > _ZN21NxsTaxaBlockSurrogate21HandleLinkTaxaCommandER8NxsToken@Base 2.1.18 > _ZN21NxsTaxaBlockSurrogate30CopyTaxaBlockSurrogateContentsERKS_@Base 2.1.18 > > _ZN21NxsTaxaBlockSurrogate32SurrogateSwapEquivalentTaxaBlockEP15NxsTaxaBlockAPI@Base > 2.1.18 > - _ZN22NxsFullTreeDescriptionD1Ev@Base 2.1.18 > - _ZN22NxsFullTreeDescriptionD2Ev@Base 2.1.18 > +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZN22NxsFullTreeDescriptionD1Ev@Base > 2.1.18 > +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZN22NxsFullTreeDescriptionD2Ev@Base > 2.1.18 > _ZN22NxsGeneticCodesManagerC1Ev@Base 2.1.18 > _ZN22NxsGeneticCodesManagerC2Ev@Base 2.1.18 > > _ZN23NxsLabelToIndicesMapper14AppendNewLabelERNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 2.1.18 > @@ -462,8 +462,8 @@ >
Bug#1037731: marked as done (libncl: ftbfs with GCC-13)
Your message dated Mon, 14 Aug 2023 14:39:45 + with message-id and subject line Bug#1037731: fixed in libncl 2.1.21+git20210811.b1213a7-5 has caused the Debian Bug report #1037731, regarding libncl: 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.) -- 1037731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037731 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libncl Version: 2.1.21+git20210811.b1213a7-4 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/libncl_2.1.21+git20210811.b1213a7-4_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.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIcSt4pairIKc9NxsStringESt10_Select1stIS3_ESt4lessIcESaIS3_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS3_ERS1_@Base 2.1.18 (optional)_ZNSt8_Rb_treeIccSt9_IdentityIcESt4lessIcESaIcEE16_M_insert_uniqueIRKcEESt4pairISt17_Rb_tree_iteratorIcEbEOT_@Base 2.1.21+git20171002.4becff7 - _ZNSt8_Rb_treeIccSt9_IdentityIcESt4lessIcESaIcEE24_M_get_insert_unique_posERKc@Base 2.1.18 - _ZNSt8_Rb_treeIccSt9_IdentityIcESt4lessIcESaIcEE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIcERKc@Base 2.1.18 - _ZNSt8_Rb_treeIiSt4pairIKiNSt7__cxx114listIP8NxsBlockSaIS5_St10_Select1stIS8_ESt4lessIiESaIS8_EE24_M_get_insert_unique_posERS1_@Base 2.1.21+git20190531.feceb81 - _ZNSt8_Rb_treeIiSt4pairIKiNSt7__cxx114listIP8NxsBlockSaIS5_St10_Select1stIS8_ESt4lessIiESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS1_@Base 2.1.18 - (optional)_ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.1.21+git20171002.4becff7 +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIccSt9_IdentityIcESt4lessIcESaIcEE24_M_get_insert_unique_posERKc@Base 2.1.18 +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIccSt9_IdentityIcESt4lessIcESaIcEE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIcERKc@Base 2.1.18 +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIiSt4pairIKiNSt7__cxx114listIP8NxsBlockSaIS5_St10_Select1stIS8_ESt4lessIiESaIS8_EE24_M_get_insert_unique_posERS1_@Base 2.1.21+git20190531.feceb81 +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIiSt4pairIKiNSt7__cxx114listIP8NxsBlockSaIS5_St10_Select1stIS8_ESt4lessIiESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS1_@Base 2.1.18 +#MISSING: 2.1.21+git20210811.b1213a7-4# (optional)_ZNSt8_Rb_treeIiSt4pairIKiiESt10_Select1stIS2_ESt4lessIiESaIS2_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS2_ERS1_@Base 2.1.21+git20171002.4becff7 _ZNSt8_Rb_treeIiiSt9_IdentityIiESt4lessIiESaIiEE16_M_insert_uniqueIRKiEESt4pairISt17_Rb_tree_iteratorIiEbEOT_@Base 2.1.18 _ZNSt8_Rb_treeIiiSt9_IdentityIiESt4lessIiESaIiEE16_M_insert_uniqueIiEESt4pairISt17_Rb_tree_iteratorIiEbEOT_@Base 2.1.18 - _ZNSt8_Rb_treeIiiSt9_IdentityIiESt4lessIiESaIiEE24_M_get_insert_unique_posERKi@Base 2.1.18 - _ZNSt8_Rb_treeIiiSt9_IdentityIiESt4lessIiESaIiEE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIiERKi@Base 2.1.18 +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIiiSt9_IdentityIiESt4lessIiESaIiEE24_M_get_insert_unique_posERKi@Base 2.1.18 +#MISSING: 2.1.21+git20210811.b1213a7-4# _ZNSt8_Rb_treeIiiSt9_IdentityIiESt4lessIiESaIiEE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIiERKi@Base 2.1.18
Bug#1049351: RM: viewnior -- RoQA; unmaintained; depends on gtk2
Source: viewnior Severity: serious Version: 1.6-1 viewnior does not seem to be used a lot. 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#1043002: pdm: Please replace python3-pep517 with python3-pyproject-hooks in Depends/Build-Depends
On August 14, 2023 12:28:30 PM UTC, Andreas Tille wrote: >Control: tags -1 pending > >Hi, > >I've fixed the issue reported in this bug[1]. > >In addition I've took the chance to upload pdm to its latest upstream >version. When doing so I realised that build time tests are basically >ignored. This was mainly due to the removal of artefacts that are used >for testing. I admit I do not see any reason to remove those data >files - in Debian R team this kind of data files which is just used for >testing is accepted. Thus I took the freedom to re-introduce these >files and was running the tests in d/rules. Unfortunately there is >quite a number of tests failing > > 54 failed, 620 passed, 1 xfailed, 3 rerun in 228.94s (0:03:48) > > >(see Salsa CI[2]) > >I'd like to stress that to run those tests at all I needed a patch[3] >since BaseProvider can't be simply imported from findpython. > >Before I upload I'd like to ask for reviewing this patch and opinions >about the test suite errors. While these possibly occure in previous >versions (which I did not tested) we might consider ignoring just the >failing tests. I need to admit that I did not went through the list of >single failures - may be there is a chance of easy fixes for some of >them. I simply wanted to discuss the reintroduction of the artifacts >and my patch first. > With the exception of future_fstrings those are all binary without source. That's a problem. It's probably okay if you add the corresponding source somewhere in the package. I do think it's odd that pdm would need poetry-core in its test suit. Scott K
Bug#1037719: marked as done (libbpp-popgen: ftbfs with GCC-13)
Your message dated Mon, 14 Aug 2023 13:50:21 + with message-id and subject line Bug#1042144: fixed in libbpp-popgen 2.4.1-9 has caused the Debian Bug report #1042144, regarding libbpp-popgen: 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.) -- 1042144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-popgen 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-popgen_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 [...] _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base 2.4.1 - (optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base 2.4.1 +#MISSING: 2.4.1-8# (optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_mESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_mESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base 2.4.1 - (optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_mESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base 2.4.1 - (optional)_ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOiEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - (optional)_ZNSt8_Rb_treeIiSt4pairIKidESt10_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_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 - (optional)_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_treeImSt4pairIKmN3bpp28MultilocusGenotypeStatistics6FstatsEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmN3bpp28MultilocusGenotypeStatistics6FstatsEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmN3bpp28MultilocusGenotypeStatistics7VarCompEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 -
Bug#1042144: marked as done (libbpp-popgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Mon, 14 Aug 2023 13:50:21 + with message-id and subject line Bug#1042144: fixed in libbpp-popgen 2.4.1-9 has caused the Debian Bug report #1042144, regarding libbpp-popgen: 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.) -- 1042144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042144 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-popgen 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-popgen-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-popgen8/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.a > debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.so > debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.so.8 > debian/libbpp-popgen8/usr/lib/x86_64-linux-gnu > mv > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.so.8.0.0 > debian/libbpp-popgen8/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-popgen-dev > PKGSHL=libbpp-popgen8 > install -d -m 755 debian/libbpp-popgen-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-popgen-dev/usr/include > install -d -m 755 debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-popgen-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 libraries disappeared in the symbols file: > libbpp-popgen.so.8 > dpkg-gensymbols: warning: the generated symbols file is empty > --- debian/symbols (libbpp-popgen-dev_2.4.1-8_amd64) > +++ dpkg-gensymbolsrEJ7jM 2023-07-26 19:15:39.179875906 + > @@ -1,1361 +0,0 @@ > -libbpp-popgen.so.8 libbpp-popgen8 #MINVER# > - _ZN3bpp10Individual11addSequenceEmRKNS_8SequenceE@Base 2.4.1 > - _ZN3bpp10Individual11setGenotypeERKNS_18MultilocusGenotypeE@Base 2.4.1 > - _ZN3bpp10Individual11setLocalityEPKNS_8LocalityIdEE@Base 2.4.1 > - _ZN3bpp10Individual12initGenotypeEm@Base 2.4.1 > - _ZN3bpp10Individual12setSequencesERKNS_20MapSequenceContainerE@Base 2.4.1 > - _ZN3bpp10Individual14deleteGenotypeEv@Base 2.4.1 > - > _ZN3bpp10Individual20deleteSequenceByNameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 2.4.1 > - _ZN3bpp10Individual20getMonolocusGenotypeEm@Base 2.4.1 > - _ZN3bpp10Individual20setMonolocusGenotypeEmRKNS_17MonolocusGenotypeE@Base > 2.4.1 > - _ZN3bpp10Individual24deleteSequenceAtPositionEm@Base 2.4.1 > - > _ZN3bpp10Individual30setMonolocusGenotypeByAlleleIdEmSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EERKNS_9LocusInfoE@Base > 2.4.1 > - > _ZN3bpp10Individual31setMonolocusGenotypeByAlleleKeyEmSt6vectorImSaImEE@Base > 2.4.1 > - _ZN3bpp10Individual4setXEd@Base 2.4.1 > - _ZN3bpp10Individual4setYEd@Base 2.4.1 > - > _ZN3bpp10Individual5setIdERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 2.4.1 > - _ZN3bpp10Individual6setSexEt@Base 2.4.1 > - _ZN3bpp10Individual7setDateERKNS_4DateE@Base 2.4.1 > - _ZN3bpp10Individual8setCoordERKNS_7Point2DIdEE@Base 2.4.1 > - _ZN3bpp10Individual8setCoordEdd@Base 2.4.1 > - > _ZN3bpp10IndividualC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 2.4.1 > - > _ZN3bpp10IndividualC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKNS_4DateERKNS_7Point2DIdEEPNS_8LocalityIdEEt@Base > 2.4.1 > - _ZN3bpp10IndividualC1ERKS0_@Base 2.4.1 > - _ZN3bpp10IndividualC1Ev@Base 2.4.1 > - > _ZN3bpp10IndividualC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 2.4.1 > -
Bug#1042144: marked as done (libbpp-popgen: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)
Your message dated Mon, 14 Aug 2023 13:50:21 + with message-id and subject line Bug#1037719: fixed in libbpp-popgen 2.4.1-9 has caused the Debian Bug report #1037719, regarding libbpp-popgen: 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.) -- 1037719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libbpp-popgen 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-popgen-dev/usr/lib/x86_64-linux-gnu > install -d -m 755 debian/libbpp-popgen8/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.a > debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.so > debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu > mv /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.so.8 > debian/libbpp-popgen8/usr/lib/x86_64-linux-gnu > mv > /<>/debian/tmp/usr/lib/x86_64-linux-gnu/libbpp-popgen.so.8.0.0 > debian/libbpp-popgen8/usr/lib/x86_64-linux-gnu > PKGDEV=libbpp-popgen-dev > PKGSHL=libbpp-popgen8 > install -d -m 755 debian/libbpp-popgen-dev/usr/include > mv debian/tmp/usr/include/Bpp debian/libbpp-popgen-dev/usr/include > install -d -m 755 debian/libbpp-popgen-dev/usr/lib/x86_64-linux-gnu > mv debian/tmp/usr/lib/x86_64-linux-gnu/cmake > debian/libbpp-popgen-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 libraries disappeared in the symbols file: > libbpp-popgen.so.8 > dpkg-gensymbols: warning: the generated symbols file is empty > --- debian/symbols (libbpp-popgen-dev_2.4.1-8_amd64) > +++ dpkg-gensymbolsrEJ7jM 2023-07-26 19:15:39.179875906 + > @@ -1,1361 +0,0 @@ > -libbpp-popgen.so.8 libbpp-popgen8 #MINVER# > - _ZN3bpp10Individual11addSequenceEmRKNS_8SequenceE@Base 2.4.1 > - _ZN3bpp10Individual11setGenotypeERKNS_18MultilocusGenotypeE@Base 2.4.1 > - _ZN3bpp10Individual11setLocalityEPKNS_8LocalityIdEE@Base 2.4.1 > - _ZN3bpp10Individual12initGenotypeEm@Base 2.4.1 > - _ZN3bpp10Individual12setSequencesERKNS_20MapSequenceContainerE@Base 2.4.1 > - _ZN3bpp10Individual14deleteGenotypeEv@Base 2.4.1 > - > _ZN3bpp10Individual20deleteSequenceByNameERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 2.4.1 > - _ZN3bpp10Individual20getMonolocusGenotypeEm@Base 2.4.1 > - _ZN3bpp10Individual20setMonolocusGenotypeEmRKNS_17MonolocusGenotypeE@Base > 2.4.1 > - _ZN3bpp10Individual24deleteSequenceAtPositionEm@Base 2.4.1 > - > _ZN3bpp10Individual30setMonolocusGenotypeByAlleleIdEmSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS7_EERKNS_9LocusInfoE@Base > 2.4.1 > - > _ZN3bpp10Individual31setMonolocusGenotypeByAlleleKeyEmSt6vectorImSaImEE@Base > 2.4.1 > - _ZN3bpp10Individual4setXEd@Base 2.4.1 > - _ZN3bpp10Individual4setYEd@Base 2.4.1 > - > _ZN3bpp10Individual5setIdERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 2.4.1 > - _ZN3bpp10Individual6setSexEt@Base 2.4.1 > - _ZN3bpp10Individual7setDateERKNS_4DateE@Base 2.4.1 > - _ZN3bpp10Individual8setCoordERKNS_7Point2DIdEE@Base 2.4.1 > - _ZN3bpp10Individual8setCoordEdd@Base 2.4.1 > - > _ZN3bpp10IndividualC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 2.4.1 > - > _ZN3bpp10IndividualC1ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEERKNS_4DateERKNS_7Point2DIdEEPNS_8LocalityIdEEt@Base > 2.4.1 > - _ZN3bpp10IndividualC1ERKS0_@Base 2.4.1 > - _ZN3bpp10IndividualC1Ev@Base 2.4.1 > - > _ZN3bpp10IndividualC2ERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base > 2.4.1 > -
Bug#1037719: marked as done (libbpp-popgen: ftbfs with GCC-13)
Your message dated Mon, 14 Aug 2023 13:50:21 + with message-id and subject line Bug#1037719: fixed in libbpp-popgen 2.4.1-9 has caused the Debian Bug report #1037719, regarding libbpp-popgen: 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.) -- 1037719: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037719 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:libbpp-popgen 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-popgen_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 [...] _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base 2.4.1 - (optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base 2.4.1 +#MISSING: 2.4.1-8# (optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_iESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_mESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base 2.4.1 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_mESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base 2.4.1 - (optional)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_mESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base 2.4.1 - (optional)_ZNSt8_Rb_treeIiSt4pairIKidESt10_Select1stIS2_ESt4lessIiESaIS2_EE22_M_emplace_hint_uniqueIJRKSt21piecewise_construct_tSt5tupleIJOiEESD_IJESt17_Rb_tree_iteratorIS2_ESt23_Rb_tree_const_iteratorIS2_EDpOT_@Base 2.4.1 - (optional)_ZNSt8_Rb_treeIiSt4pairIKidESt10_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_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 - (optional)_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_treeImSt4pairIKmN3bpp28MultilocusGenotypeStatistics6FstatsEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmN3bpp28MultilocusGenotypeStatistics6FstatsEESt10_Select1stIS5_ESt4lessImESaIS5_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS5_ERS1_@Base 2.4.1 - _ZNSt8_Rb_treeImSt4pairIKmN3bpp28MultilocusGenotypeStatistics7VarCompEESt10_Select1stIS5_ESt4lessImESaIS5_EE24_M_get_insert_unique_posERS1_@Base 2.4.1 -
Bug#1038920: python3-certbot-dns-gandi: Update from Debian 11 -> 12 leaves certificate updates broken
On Fri, 30 Jun 2023 03:24:00 + Harlan Lieberman-Berg wrote: On Fri, Jun 23, 2023 at 6:24 AM Norbert Preining wrote: > with the update of certbot and the DNS Gandi plugin, the command line > arguments for requesting a certificate have changed. […] > Do you still have a host that's in the buggy state, or did you fix them all with the workaround? Because it's going to be fixed in a preinst, I'd like more testing (and more eyes) on it than I normally would, just for caution's sake. Hello, I "bumped into" this bug on a server too. This server is still in "buggy state". Certificate is valid for more than 30days from now. Can I test a new package version instead of making changes manually ? Regards, Fernando
Bug#1042131: marked as pending in libncl
Control: tag -1 pending Hello, Bug #1042131 in libncl 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/libncl/-/commit/6b73e6331a9f0c2538f5d85b70c96fc6d95917d3 Update symbols for gcc-13. Closes: #1037731, #1042131 (this message was generated automatically) -- Greetings https://bugs.debian.org/1042131
Processed: Bug#1042131 marked as pending in libncl
Processing control commands: > tag -1 pending Bug #1042131 [src:libncl] libncl: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below Bug #1037731 [src:libncl] libncl: ftbfs with GCC-13 Ignoring request to alter tags of bug #1042131 to the same tags previously set Ignoring request to alter tags of bug #1037731 to the same tags previously set -- 1037731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037731 1042131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Bug#1037731 marked as pending in libncl
Processing control commands: > tag -1 pending Bug #1037731 [src:libncl] libncl: ftbfs with GCC-13 Bug #1042131 [src:libncl] libncl: 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. -- 1037731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037731 1042131: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042131 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1037731: marked as pending in libncl
Control: tag -1 pending Hello, Bug #1037731 in libncl 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/libncl/-/commit/6b73e6331a9f0c2538f5d85b70c96fc6d95917d3 Update symbols for gcc-13. Closes: #1037731, #1042131 (this message was generated automatically) -- Greetings https://bugs.debian.org/1037731
Processed: Re: Bug#1041731: groff-base: "-" mapped as HYPHEN
Processing control commands: > severity -1 serious Bug #1041731 [groff-base] groff-base: "-" mapped as HYPHEN Bug #1043196 [groff-base] tmux: Manpages are broken because of unnecessary utf8 characters Severity set to 'serious' from 'important' Severity set to 'serious' from 'important' -- 1041731: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041731 1043196: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043196 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: Re: pdm: Please replace python3-pep517 with python3-pyproject-hooks in Depends/Build-Depends
Processing control commands: > tags -1 pending Bug #1043002 [src:pdm] pdm: Please replace python3-pep517 with python3-pyproject-hooks in Depends/Build-Depends Added tag(s) pending. -- 1043002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1043002: pdm: Please replace python3-pep517 with python3-pyproject-hooks in Depends/Build-Depends
Control: tags -1 pending Hi, I've fixed the issue reported in this bug[1]. In addition I've took the chance to upload pdm to its latest upstream version. When doing so I realised that build time tests are basically ignored. This was mainly due to the removal of artefacts that are used for testing. I admit I do not see any reason to remove those data files - in Debian R team this kind of data files which is just used for testing is accepted. Thus I took the freedom to re-introduce these files and was running the tests in d/rules. Unfortunately there is quite a number of tests failing 54 failed, 620 passed, 1 xfailed, 3 rerun in 228.94s (0:03:48) (see Salsa CI[2]) I'd like to stress that to run those tests at all I needed a patch[3] since BaseProvider can't be simply imported from findpython. Before I upload I'd like to ask for reviewing this patch and opinions about the test suite errors. While these possibly occure in previous versions (which I did not tested) we might consider ignoring just the failing tests. I need to admit that I did not went through the list of single failures - may be there is a chance of easy fixes for some of them. I simply wanted to discuss the reintroduction of the artifacts and my patch first. Kind regards Andreas. [1] https://salsa.debian.org/python-team/packages/pdm/-/commit/2691b62c20944e0d9ca2326cb99e196d954b2735 [2] https://salsa.debian.org/python-team/packages/pdm/-/jobs/4555215 [3} https://salsa.debian.org/python-team/packages/pdm/-/blob/master/debian/patches/0002_fix_import.patch -- http://fam-tille.de
Bug#1049328: Reverting nested groups feature in Debian's GOsa²
Hi, > However, group nesting is not a feature that can be used with posixGroup > objectClass based LDAP objects (as the objectClass / schema does not support > group nesting). I really have a huge question mark about what upstream's > intention for this feature was/is... It is not a feature, but definitely possible using dynlist (we did this at Teckids before abandonning LDAP): https://www.openldap.org/faq/data/cache/1209.html Maybe GOSa expects something like that to be in place? -nik
Bug#1043559: Confirm
Hi all, I can confirm this bug: - Debian Sid (up to date) - Cinnamon desktop Reverting back to 44.0-2 solves the problem. -- Hilsen/Regards Michael Rasmussen Get my public GnuPG keys: michael rasmussen cc https://keys.openpgp.org/vks/v1/by-fingerprint/A1306C5094B5E31B7721A3A66F4844C7CA7501AA mir datanom net https://keys.openpgp.org/vks/v1/by-fingerprint/0C14CD9479667E848770C8F98417B6C5E1BB093F mir miras org https://keys.openpgp.org/vks/v1/by-fingerprint/5F71405B571CB8EE2A414A4FC77C11E049A06E66 -- 'During times of universal deceit, telling the truth becomes a revolutionary act.' -George Orwell /usr/games/fortune -es says: Debian Hint #24: If you would like to thank a maintainer for handling an issue, check out reportbug --kudos. pgpFbcKSkZC7P.pgp Description: OpenPGP digital signature
Bug#1049331: python3-blockdiag: fails with Pil 10
Package: python3-blockdiag
Version: 2.0.1+dfsg-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Hi,
i don't use it directly, but via python3-sphinxcontrib.seqdiag, but that must
not
matter. Instead of producing image, it produces warning:
WARNING: dot code 'seqdiag {...}': 'ImageDraw' object has no attribute
'textsize'
AFAIK, the 'textsize' attribute was removed from PIL. It is reported to to
upstream
already (not by me), see https://github.com/blockdiag/seqdiag/issues/63
By that, the package is not usable at all.
regards
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Versions of packages python3-blockdiag depends on:
ii python33.11.4-5+b1
ii python3-docutils 0.19+dfsg-6
ii python3-funcparserlib 1.0.0-0.2
ii python3-pil10.0.0-1
ii python3-pkg-resources 68.0.0-1
ii python3-reportlab 4.0.4-9
ii python3-webcolors 1.11.1-1
-- no debconf information
Bug#1049330: python3-seqdiag: fails with Pil 10
Package: python3-seqdiag
Version: 2.0.0+dfsg-1
Severity: grave
Tags: upstream
Justification: renders package unusable
Hi,
i don't use it directly, but via python3-sphinxcontrib.seqdiag, but that must
not
matter. Instead of producing image, it produces warning:
WARNING: dot code 'seqdiag {...}': 'ImageDraw' object has no attribute
'textsize'
AFAIK, the 'textsize' attribute was removed from PIL. It is reported to to
upstream
already (not by me), see https://github.com/blockdiag/seqdiag/issues/63
By that, the package is not usable at all.
regards
-- System Information:
Debian Release: trixie/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Versions of packages python3-seqdiag depends on:
ii python33.11.4-5+b1
ii python3-blockdiag 2.0.1+dfsg-1
Bug#1042889: vm: autopkgtest fails against Emacs 29.1
Sean Whitton writes ("Bug#1042889: vm: autopkgtest fails against Emacs 29.1"):
> vm's autopkgtest fails with Emacs 29.1, which latter is now in sid.
>
> https://ci.debian.net/packages/v/vm/testing/amd64/
The regression was indeed caused solely by upstream renaming the
variable that disables byte compilation, from
native-comp-deferred-compilation-deny-list
to
native-comp-jit-compilation-deny-list
ISTM that making that change without also honouring the old setting
was an obviously bad idea. Upstream set us up for this failure.
Anyway, I have fixed this issue in vm, by handling both variables.
I expect the new vm package to migrate quickly.
I see that there are other packages with failing tests, preventing
emacs from migrating. I haven't looked at them, but some of them may
be similarly afflicted.
Thanks,
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#1049328: Reverting nested groups feature in Debian's GOsa²
Hi all, Here comes a short explanation of the most severe blocker we had finally for releasing Debian Edu (after Guido fixed loads of other issues). The underlying problem of #1049328 [RESOLVED] is that upstream coded a nested group feature into the groups plugin of GOsa². However, group nesting is not a feature that can be used with posixGroup objectClass based LDAP objects (as the objectClass / schema does not support group nesting). I really have a huge question mark about what upstream's intention for this feature was/is... The outcome of this "feature" was that creating posixGroup in pre-versions of Debian Edu 12 (and with it primary group creation during user creation) was entirely broken. The approach for resolving this in Debian Edu has been to identify a range of upstream commits bringing in this new (bogus, imho) "feature" into GOsa² 2.8.x and reverting these identified commits (which did't always revert exactly but needed manual adjustments per commit/revert). The reverts bring back the posixGroup handling as known from Debian Edu 11 (basically, i.e. the posixGroup handling from GOsa² 2.7.5). As the architectural design really leaves this huge question mark behind, the issue will be brought up upstream, as well (once we have Debian Edu up and running again). light+love Mike -- mike gabriel aka sunweaver (Debian Developer) mobile: +49 (1520) 1976 148 landline: +49 (4351) 486 14 27 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: sunwea...@debian.org, http://sunweavers.net pgppoJExONpfN.pgp Description: Digitale PGP-Signatur
Processed: Re: Bug#1039699: Adding students/teachers with gosa fails due to LDAP and postcreate command errors
Processing control commands: > clone -1 -2 Bug #1039699 [src:gosa] Adding students/teachers with gosa fails due to LDAP and postcreate command errors Bug 1039699 cloned as bug 1049328 > retitle -1 Adding users fails in postcreate command Bug #1039699 [src:gosa] Adding students/teachers with gosa fails due to LDAP and postcreate command errors Changed Bug title to 'Adding users fails in postcreate command' from 'Adding students/teachers with gosa fails due to LDAP and postcreate command errors'. > severity -1 important Bug #1039699 [src:gosa] Adding users fails in postcreate command Severity set to 'important' from 'normal' > found -1 2.8~git20230203.10abe45+dfsg-1+deb12u1 Bug #1039699 [src:gosa] Adding users fails in postcreate command Marked as found in versions gosa/2.8~git20230203.10abe45+dfsg-1+deb12u1. > retitle -2 Adding users fails due to broken class_groups.inc Bug #1049328 [src:gosa] Adding students/teachers with gosa fails due to LDAP and postcreate command errors Changed Bug title to 'Adding users fails due to broken class_groups.inc' from 'Adding students/teachers with gosa fails due to LDAP and postcreate command errors'. > severity -2 critical Bug #1049328 [src:gosa] Adding users fails due to broken class_groups.inc Severity set to 'critical' from 'normal' > found -2 2.8~git20230203.10abe45+dfsg-1+deb12u1 Bug #1049328 [src:gosa] Adding users fails due to broken class_groups.inc Marked as found in versions gosa/2.8~git20230203.10abe45+dfsg-1+deb12u1. -- 1039699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039699 1049328: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049328 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1032647: Keeping 525.105.17-1 for bookworm?
On Tue, 1 Aug 2023 19:07:01 +0200 Andreas Beckmann wrote: > At some point we will be updating bookworm to the 535 series which is a > new LTSB branch and supported for the lifetime of bookworm. > But that is not yet in sid or even experimental. > > > Andreas > > > Hi Andreas, when do you think 535 drivers will be available in Sid/experimental? I'm on Trixie and i manually installed 530.41 drivers. I want to upgrade my video card with a 4060ti but it is supported since 535, i could use Official Nvidia drivers but i prefer using Debian packages. Regards Attilio
Processed: pandas FTBFS with numexpr 2.8.5
Processing control commands: > forwarded -1 https://github.com/pandas-dev/pandas/issues/54449 Bug #1049326 [python3-numexpr] pandas FTBFS with numexpr 2.8.5 Set Bug forwarded-to-address to 'https://github.com/pandas-dev/pandas/issues/54449'. -- 1049326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1049326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1049326: pandas FTBFS with numexpr 2.8.5
Package: python3-numexpr Version: 2.8.5-1 Severity: serious Control: forwarded -1 https://github.com/pandas-dev/pandas/issues/54449 (actually they found it first) I only have actual logs for 2.0.x, but I suspect 1.5.x is also affected. As a short term fix, it may be possible to disable pandas' numexpr support, but I haven't yet had time to try that. It's also possible that as this is a security feature, it should be forced through ignoring the breakage, but I don't know enough to have a meaningful opinion.
Bug#1042532: mediawiki: Vendoring a few javascript library without source
severity 1042532 normal tags 1042532 wontfix thanks Hi, On 7/31/23 07:23, roucaries bastien wrote: hi, Le lun. 31 juil. 2023 à 08:27, Kunal Mehta a écrit : These are in the preferred form for modification so I don't think there's any issue here, but please correct me if I'm wrong. MediaWiki often patches these libraries (e.g. jquery.ui) in this format hence IMO meeting the "preferred form of the work for making modifications to it" requirement of the GPL. No https://sources.debian.org/src/mediawiki/1%3A1.39.4-2/resources/lib/pako/ is webpacked in order to be transformed in es5 No source available before webpack IANAL, but as I understand it, there are two licenses to consider here: pako's MIT license (aka Expat) and MediaWiki's GPL v2 or later license. The pako_deflate.es5.js file contains the MIT license information/attribution, so we're in compliance for that. MediaWiki's GPL v2 requires source code to be in "preferred form of the work for making modifications to it". In the context of MediaWiki, this is in the preferred form, since that's how we plan to (and do) modify it. If you want to patch MediaWiki, having the pre-transpiled sources is going to be way more work than the source we're providing right now. And the proof is that (AFAIK) MediaWiki devs will just patch these sources directly, they don't go to the upstream sources, adjust those, and then generate a patch. So I don't see a DFSG issue. And do not stick to lastest jquery is a security problem. Are you sure you have closed all the CVE ? The ones that affect MediaWiki, I believe so. Upstream MediaWiki has at least one or two jQuery team members as core developers who follow that not to mention the Wikimedia Foundation's security team. with my javascript hat, I believe that working with upstream to improve the testing (using if needed selenium) will improve the security of mediawiki by using packaged and up to date js There is already upstream selenium-based testing, but using the latest version of everything isn't always a feature. In all the case it decrease the burden from a security point of view No, it really doesn't, it just shifts it elsewhere. The more deviations Debian makes, the less we can rely on upstream's QA processes for ensuring we're shipping working software, which will more likely slow down security updates. Since bundling is permitted by policy, we plan to continue doing it. -- Kunal
Processed: Re: Bug#1042532: mediawiki: Vendoring a few javascript library without source
Processing commands for cont...@bugs.debian.org: > severity 1042532 normal Bug #1042532 [src:mediawiki] mediawiki: Vendoring a few javascript library without source Severity set to 'normal' from 'serious' > tags 1042532 wontfix Bug #1042532 [src:mediawiki] mediawiki: Vendoring a few javascript library without source Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 1042532: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042532 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
