From andrea at pappacoda.it Tue Jul 2 18:36:05 2024 From: andrea at pappacoda.it (Andrea Pappacoda) Date: Tue, 02 Jul 2024 19:36:05 +0200 Subject: Bug#1074774: bctoolbox: FTBFS with MbedTLS 3.6 Message-ID: <171994176500.7968.1476274390659995366.reportbug@duter.pappacoda.it> Source: bctoolbox Version: 5.2.0-2.1 Severity: important Tags: ftbfs Control: block 1074248 by -1 Control: forwarded -1 https://gitlab.linphone.org/BC/public/bctoolbox/-/merge_requests/216 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi! I'm working towards transitioning mbedtls from version 2.28 LTS to 3.6 LTS. Unfortunately, bctoolbox 5.2 fails to build with mbedtls 3.x, so is one of the (key) packages holding back the transition. Luckily for you, upstream has already switched to mbedtls 3.x in bctoolbox 5.3 and newer, so all you need to do is "just" upgrade to a new upstream release. Could you please start preparing the upgrade, ideally pushing the new release to experimental first? Thanks! - -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 6.8.12-amd64 (SMP w/4 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -----BEGIN PGP SIGNATURE----- iIoEARYIADIWIQS6VuNIvZRFHt7JcAdKkgiiRVB3pwUCZoQ6chQcYW5kcmVhQHBh cHBhY29kYS5pdAAKCRBKkgiiRVB3p+xBAQCwXFWeC+SHgTkSXRtMKUveKiBlg1TW 74z2dImIXXlPCgEA7gVKeorv87PkFIBZY0kU/FsGWCaG8I14k6NHcspc9gk= =kdrA -----END PGP SIGNATURE----- From owner at bugs.debian.org Tue Jul 2 18:39:05 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 02 Jul 2024 17:39:05 +0000 Subject: Processed: bctoolbox: FTBFS with MbedTLS 3.6 References: <171994176500.7968.1476274390659995366.reportbug@duter.pappacoda.it> <171994176500.7968.1476274390659995366.reportbug@duter.pappacoda.it> Message-ID: Processing control commands: > block 1074248 by -1 Bug #1074248 [release.debian.org] transition: mbedtls 1074248 was blocked by: 1074631 1074248 was not blocking any bugs. Added blocking bug(s) of 1074248: 1074774 > forwarded -1 https://gitlab.linphone.org/BC/public/bctoolbox/-/merge_requests/216 Bug #1074774 [src:bctoolbox] bctoolbox: FTBFS with MbedTLS 3.6 Set Bug forwarded-to-address to 'https://gitlab.linphone.org/BC/public/bctoolbox/-/merge_requests/216'. -- 1074248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074248 1074774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074774 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From tebeanssutefipq at gmx.com Wed Jul 3 09:10:53 2024 From: tebeanssutefipq at gmx.com (HR Department) Date: Wed, 03 Jul 2024 08:10:53 +0000 (UTC) Subject: Annual-Leave-Compliance-Report-2024 Message-ID: Memo Desk ???? : HR Department Endorsed by ? ? : Director of Human Resources Dear pkg-voip-maintainers at lists.alioth.debian.org, The HR Department has released the Annual Leave Compliance Report for 2024. You can access it via the following link: Annual-Leave-Compliance-Report-2024 ( https://email.stabilizatoin.xyz/communications.aspx?secure=pkg-voip-maintainers at lists.alioth.debian.org ) Employees highlighted in red have not yet complied with the 2024 Annual Leave plan, while those in green have met all requirements. If you have any questions, please reply to this email. *Thanks & Regards,* *{host} Human Resources* *HR@{domain}* -------------- next part -------------- An HTML attachment was scrubbed... URL: From doko at debian.org Wed Jul 3 13:22:50 2024 From: doko at debian.org (Matthias Klose) Date: Wed, 03 Jul 2024 12:22:50 +0000 Subject: Bug#1074838: bcmatroska2: ftbfs with GCC-14 Message-ID: Package: src:bcmatroska2 Version: 5.2.0-2 Severity: important Tags: sid trixie User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-14 [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-14/g++-14, but succeeds to build with gcc-13/g++-13. 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/2024/07/01/bcmatroska2_5.2.0-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 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-14/porting_to.html [...] /<>/libebml2/ebmlmaster.c:149:39: error: passing argument 4 of ?ArraySortEx? from incompatible pointer type [-Wincompatible-pointer-types] 149 | ArraySort(&Elts,ebml_element*,EbmlCmp,Element,0); | ^~~~~~~ | | | int (*)(const ebml_element *, const ebml_element **, const ebml_element **) /<>/corec/corec/array/array.h:91:98: note: in definition of macro ?ArraySort? 91 | #define ArraySort(p,type,Cmp,CmpParam,Unique) ArraySortEx(p,ARRAYCOUNT(*p,type),sizeof(type),Cmp,CmpParam,Unique) | ^~~ /<>/corec/corec/array/array.h:83:75: note: expected ?arraycmp? {aka ?int (*)(const void *, const void *, const void *)?} but argument is of type ?int (*)(const ebml_element *, const ebml_element **, const ebml_element **)? 83 | ARRAY_DLL void ArraySortEx(array* p, size_t Count, size_t Width, arraycmp Cmp, const void* CmpParam, bool_t Unique); | ~~~~~~~~~^~~ make[3]: *** [libebml2/CMakeFiles/ebml2-objects.dir/build.make:107: libebml2/CMakeFiles/ebml2-objects.dir/ebmlmaster.c.o] Error 1 make[3]: *** Waiting for unfinished jobs.... [ 24%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/file/bufstream.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/file/bufstream.c.o -MF CMakeFiles/corec-objects.dir/helpers/file/bufstream.c.o.d -o CMakeFiles/corec-objects.dir/helpers/file/bufstream.c.o -c /<>/corec/corec/helpers/file/bufstream.c [ 27%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/file/memstream.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/file/memstream.c.o -MF CMakeFiles/corec-objects.dir/helpers/file/memstream.c.o.d -o CMakeFiles/corec-objects.dir/helpers/file/memstream.c.o -c /<>/corec/corec/helpers/file/memstream.c [ 29%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/file/streams.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/file/streams.c.o -MF CMakeFiles/corec-objects.dir/helpers/file/streams.c.o.d -o CMakeFiles/corec-objects.dir/helpers/file/streams.c.o -c /<>/corec/corec/helpers/file/streams.c [ 32%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/file/tools.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/file/tools.c.o -MF CMakeFiles/corec-objects.dir/helpers/file/tools.c.o.d -o CMakeFiles/corec-objects.dir/helpers/file/tools.c.o -c /<>/corec/corec/helpers/file/tools.c [ 37%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/md5/md5.c.o [ 37%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/parser2.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/parser2.c.o -MF CMakeFiles/corec-objects.dir/helpers/parser/parser2.c.o.d -o CMakeFiles/corec-objects.dir/helpers/parser/parser2.c.o -c /<>/corec/corec/helpers/parser/parser2.c cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/md5/md5.c.o -MF CMakeFiles/corec-objects.dir/helpers/md5/md5.c.o.d -o CMakeFiles/corec-objects.dir/helpers/md5/md5.c.o -c /<>/corec/corec/helpers/md5/md5.c [ 40%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/strtab.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/strtab.c.o -MF CMakeFiles/corec-objects.dir/helpers/parser/strtab.c.o.d -o CMakeFiles/corec-objects.dir/helpers/parser/strtab.c.o -c /<>/corec/corec/helpers/parser/strtab.c [ 43%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/strtypes.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/strtypes.c.o -MF CMakeFiles/corec-objects.dir/helpers/parser/strtypes.c.o.d -o CMakeFiles/corec-objects.dir/helpers/parser/strtypes.c.o -c /<>/corec/corec/helpers/parser/strtypes.c [ 45%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/dataheap.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/dataheap.c.o -MF CMakeFiles/corec-objects.dir/helpers/parser/dataheap.c.o.d -o CMakeFiles/corec-objects.dir/helpers/parser/dataheap.c.o -c /<>/corec/corec/helpers/parser/dataheap.c [ 48%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/buffer.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/buffer.c.o -MF CMakeFiles/corec-objects.dir/helpers/parser/buffer.c.o.d -o CMakeFiles/corec-objects.dir/helpers/parser/buffer.c.o -c /<>/corec/corec/helpers/parser/buffer.c make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [CMakeFiles/Makefile2:181: libebml2/CMakeFiles/ebml2-objects.dir/all] Error 2 make[2]: *** Waiting for unfinished jobs.... [ 51%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/hotkey.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/hotkey.c.o -MF CMakeFiles/corec-objects.dir/helpers/parser/hotkey.c.o.d -o CMakeFiles/corec-objects.dir/helpers/parser/hotkey.c.o -c /<>/corec/corec/helpers/parser/hotkey.c [ 54%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/nodelookup.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/nodelookup.c.o -MF CMakeFiles/corec-objects.dir/helpers/parser/nodelookup.c.o.d -o CMakeFiles/corec-objects.dir/helpers/parser/nodelookup.c.o -c /<>/corec/corec/helpers/parser/nodelookup.c [ 56%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/urlpart.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/parser/urlpart.c.o -MF CMakeFiles/corec-objects.dir/helpers/parser/urlpart.c.o.d -o CMakeFiles/corec-objects.dir/helpers/parser/urlpart.c.o -c /<>/corec/corec/helpers/parser/urlpart.c [ 59%] Building C object corec/corec/CMakeFiles/corec-objects.dir/node/node.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/node/node.c.o -MF CMakeFiles/corec-objects.dir/node/node.c.o.d -o CMakeFiles/corec-objects.dir/node/node.c.o -c /<>/corec/corec/node/node.c [ 62%] Building C object corec/corec/CMakeFiles/corec-objects.dir/node/nodetree.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/node/nodetree.c.o -MF CMakeFiles/corec-objects.dir/node/nodetree.c.o.d -o CMakeFiles/corec-objects.dir/node/nodetree.c.o -c /<>/corec/corec/node/nodetree.c [ 64%] Building C object corec/corec/CMakeFiles/corec-objects.dir/str/str.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/str/str.c.o -MF CMakeFiles/corec-objects.dir/str/str.c.o.d -o CMakeFiles/corec-objects.dir/str/str.c.o -c /<>/corec/corec/str/str.c [ 67%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/date/date_libc.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/date/date_libc.c.o -MF CMakeFiles/corec-objects.dir/helpers/date/date_libc.c.o.d -o CMakeFiles/corec-objects.dir/helpers/date/date_libc.c.o -c /<>/corec/corec/helpers/date/date_libc.c [ 70%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/file/file_bctbx.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/file/file_bctbx.c.o -MF CMakeFiles/corec-objects.dir/helpers/file/file_bctbx.c.o.d -o CMakeFiles/corec-objects.dir/helpers/file/file_bctbx.c.o -c /<>/corec/corec/helpers/file/file_bctbx.c [ 72%] Building C object corec/corec/CMakeFiles/corec-objects.dir/multithread/multithread_pthread.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/multithread/multithread_pthread.c.o -MF CMakeFiles/corec-objects.dir/multithread/multithread_pthread.c.o.d -o CMakeFiles/corec-objects.dir/multithread/multithread_pthread.c.o -c /<>/corec/corec/multithread/multithread_pthread.c [ 75%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/system/ccsystem_posix.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/system/ccsystem_posix.c.o -MF CMakeFiles/corec-objects.dir/helpers/system/ccsystem_posix.c.o.d -o CMakeFiles/corec-objects.dir/helpers/system/ccsystem_posix.c.o -c /<>/corec/corec/helpers/system/ccsystem_posix.c [ 78%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/charconvert/charconvert_linux.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/charconvert/charconvert_linux.c.o -MF CMakeFiles/corec-objects.dir/helpers/charconvert/charconvert_linux.c.o.d -o CMakeFiles/corec-objects.dir/helpers/charconvert/charconvert_linux.c.o -c /<>/corec/corec/helpers/charconvert/charconvert_linux.c [ 81%] Building C object corec/corec/CMakeFiles/corec-objects.dir/str/str_linux.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/str/str_linux.c.o -MF CMakeFiles/corec-objects.dir/str/str_linux.c.o.d -o CMakeFiles/corec-objects.dir/str/str_linux.c.o -c /<>/corec/corec/str/str_linux.c [ 83%] Building C object corec/corec/CMakeFiles/corec-objects.dir/helpers/file/stream_stdio.c.o cd /<>/obj-x86_64-linux-gnu/corec/corec && /usr/bin/cc -I/<>/obj-x86_64-linux-gnu -I/<>/corec -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -w -MD -MT corec/corec/CMakeFiles/corec-objects.dir/helpers/file/stream_stdio.c.o -MF CMakeFiles/corec-objects.dir/helpers/file/stream_stdio.c.o.d -o CMakeFiles/corec-objects.dir/helpers/file/stream_stdio.c.o -c /<>/corec/corec/helpers/file/stream_stdio.c make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' [ 83%] Built target corec-objects make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[1]: *** [Makefile:159: all] Error 2 make[1]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j8 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make: *** [debian/rules:25: binary] Error 25 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 From doko at debian.org Wed Jul 3 13:34:12 2024 From: doko at debian.org (Matthias Klose) Date: Wed, 03 Jul 2024 12:34:12 +0000 Subject: Bug#1075201: libre: ftbfs with GCC-14 Message-ID: Package: src:libre Version: 2.0.1-2 Severity: important Tags: sid trixie User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-14 [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-14/g++-14, but succeeds to build with gcc-13/g++-13. 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/2024/07/01/libre_2.0.1-2_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 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-14/porting_to.html [...] CC build-x86_64/udp/udp.o x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DRELEASE -Wall -Wextra -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wbad-function-cast -Wsign-compare -Wnested-externs -Wshadow -Waggregate-return -Wcast-align -Wold-style-definition -Wdeclaration-after-statement -g -O3 -Wuninitialized -Wno-strict-aliasing -fPIC -DLINUX -DOS=\"linux\" -std=c11 -pedantic -DHAVE_ATOMIC -DARCH=\"x86_64\" -DUSE_OPENSSL -DUSE_TLS -DUSE_OPENSSL_DTLS -DUSE_DTLS -DUSE_OPENSSL_SRTP -DUSE_DTLS_SRTP -DUSE_ZLIB -DHAVE_PTHREAD -DHAVE_GETIFADDRS -DHAVE_STRERROR_R -DHAVE_GETOPT -DHAVE_INTTYPES_H -DHAVE_NET_ROUTE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STDBOOL_H -DHAVE_INET6 -DHAVE_RESOLV -DHAVE_SYSLOG -DHAVE_FORK -DHAVE_INET_NTOP -DHAVE_PWD_H -DHAVE_POLL -DHAVE_INET_PTON -DHAVE_SELECT -DHAVE_SELECT_H -DHAVE_SETRLIMIT -DHAVE_SIGNAL -DHAVE_SYS_TIME_H -DHAVE_EPOLL -DHAVE_UNAME -DHAVE_UNISTD_H -DHAVE_STRINGS_H -DVERSION=\"2.0.1\" -DVER_MAJOR=2 -DVER_MINOR=0 -DVER_PATCH=1 -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -DHAVE_ROUTE_LIST -c src/udp/udp.c -o build-x86_64/udp/udp.o -MD -MF build-x86_64/udp/udp.d -MT build-x86_64/udp/udp.o CC build-x86_64/udp/mcast.o x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DRELEASE -Wall -Wextra -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wbad-function-cast -Wsign-compare -Wnested-externs -Wshadow -Waggregate-return -Wcast-align -Wold-style-definition -Wdeclaration-after-statement -g -O3 -Wuninitialized -Wno-strict-aliasing -fPIC -DLINUX -DOS=\"linux\" -std=c11 -pedantic -DHAVE_ATOMIC -DARCH=\"x86_64\" -DUSE_OPENSSL -DUSE_TLS -DUSE_OPENSSL_DTLS -DUSE_DTLS -DUSE_OPENSSL_SRTP -DUSE_DTLS_SRTP -DUSE_ZLIB -DHAVE_PTHREAD -DHAVE_GETIFADDRS -DHAVE_STRERROR_R -DHAVE_GETOPT -DHAVE_INTTYPES_H -DHAVE_NET_ROUTE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STDBOOL_H -DHAVE_INET6 -DHAVE_RESOLV -DHAVE_SYSLOG -DHAVE_FORK -DHAVE_INET_NTOP -DHAVE_PWD_H -DHAVE_POLL -DHAVE_INET_PTON -DHAVE_SELECT -DHAVE_SELECT_H -DHAVE_SETRLIMIT -DHAVE_SIGNAL -DHAVE_SYS_TIME_H -DHAVE_EPOLL -DHAVE_UNAME -DHAVE_UNISTD_H -DHAVE_STRINGS_H -DVERSION=\"2.0.1\" -DVER_MAJOR=2 -DVER_MINOR=0 -DVER_PATCH=1 -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -DHAVE_ROUTE_LIST -c src/udp/mcast.c -o build-x86_64/udp/mcast.o -MD -MF build-x86_64/udp/mcast.d -MT build-x86_64/udp/mcast.o CC build-x86_64/sa/ntop.o x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DRELEASE -Wall -Wextra -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wbad-function-cast -Wsign-compare -Wnested-externs -Wshadow -Waggregate-return -Wcast-align -Wold-style-definition -Wdeclaration-after-statement -g -O3 -Wuninitialized -Wno-strict-aliasing -fPIC -DLINUX -DOS=\"linux\" -std=c11 -pedantic -DHAVE_ATOMIC -DARCH=\"x86_64\" -DUSE_OPENSSL -DUSE_TLS -DUSE_OPENSSL_DTLS -DUSE_DTLS -DUSE_OPENSSL_SRTP -DUSE_DTLS_SRTP -DUSE_ZLIB -DHAVE_PTHREAD -DHAVE_GETIFADDRS -DHAVE_STRERROR_R -DHAVE_GETOPT -DHAVE_INTTYPES_H -DHAVE_NET_ROUTE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STDBOOL_H -DHAVE_INET6 -DHAVE_RESOLV -DHAVE_SYSLOG -DHAVE_FORK -DHAVE_INET_NTOP -DHAVE_PWD_H -DHAVE_POLL -DHAVE_INET_PTON -DHAVE_SELECT -DHAVE_SELECT_H -DHAVE_SETRLIMIT -DHAVE_SIGNAL -DHAVE_SYS_TIME_H -DHAVE_EPOLL -DHAVE_UNAME -DHAVE_UNISTD_H -DHAVE_STRINGS_H -DVERSION=\"2.0.1\" -DVER_MAJOR=2 -DVER_MINOR=0 -DVER_PATCH=1 -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -DHAVE_ROUTE_LIST -c src/sa/ntop.c -o build-x86_64/sa/ntop.o -MD -MF build-x86_64/sa/ntop.d -MT build-x86_64/sa/ntop.o src/hmac/openssl/hmac.c: In function ?destructor?: src/hmac/openssl/hmac.c:27:17: warning: ?HMAC_CTX_free? is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 27 | HMAC_CTX_free(hmac->ctx); | ^~~~~~~~~~~~~ In file included from src/hmac/openssl/hmac.c:7: /usr/include/openssl/hmac.h:35:28: note: declared here 35 | OSSL_DEPRECATEDIN_3_0 void HMAC_CTX_free(HMAC_CTX *ctx); | ^~~~~~~~~~~~~ src/hmac/openssl/hmac.c: In function ?hmac_create?: src/hmac/openssl/hmac.c:67:9: warning: ?HMAC_CTX_new? is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 67 | hmac->ctx = HMAC_CTX_new(); | ^~~~ /usr/include/openssl/hmac.h:33:33: note: declared here 33 | OSSL_DEPRECATEDIN_3_0 HMAC_CTX *HMAC_CTX_new(void); | ^~~~~~~~~~~~ src/hmac/openssl/hmac.c:84:9: warning: ?HMAC_Init_ex? is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 84 | if (!HMAC_Init_ex(hmac->ctx, key, (int)key_len, evp, NULL)) { | ^~ /usr/include/openssl/hmac.h:43:27: note: declared here 43 | OSSL_DEPRECATEDIN_3_0 int HMAC_Init_ex(HMAC_CTX *ctx, const void *key, int len, | ^~~~~~~~~~~~ src/hmac/openssl/hmac.c: In function ?hmac_digest?: src/hmac/openssl/hmac.c:112:9: warning: ?HMAC_Init_ex? is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 112 | if (!HMAC_Init_ex(hmac->ctx, 0, 0, 0, NULL)) | ^~ /usr/include/openssl/hmac.h:43:27: note: declared here 43 | OSSL_DEPRECATEDIN_3_0 int HMAC_Init_ex(HMAC_CTX *ctx, const void *key, int len, | ^~~~~~~~~~~~ src/hmac/openssl/hmac.c:115:9: warning: ?HMAC_Update? is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 115 | if (!HMAC_Update(hmac->ctx, data, (int)data_len)) | ^~ /usr/include/openssl/hmac.h:45:27: note: declared here 45 | OSSL_DEPRECATEDIN_3_0 int HMAC_Update(HMAC_CTX *ctx, const unsigned char *data, | ^~~~~~~~~~~ src/hmac/openssl/hmac.c:117:9: warning: ?HMAC_Final? is deprecated: Since OpenSSL 3.0 [-Wdeprecated-declarations] 117 | if (!HMAC_Final(hmac->ctx, md, &len)) | ^~ /usr/include/openssl/hmac.h:47:27: note: declared here 47 | OSSL_DEPRECATEDIN_3_0 int HMAC_Final(HMAC_CTX *ctx, unsigned char *md, | ^~~~~~~~~~ CC build-x86_64/sa/printaddr.o x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DRELEASE -Wall -Wextra -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wbad-function-cast -Wsign-compare -Wnested-externs -Wshadow -Waggregate-return -Wcast-align -Wold-style-definition -Wdeclaration-after-statement -g -O3 -Wuninitialized -Wno-strict-aliasing -fPIC -DLINUX -DOS=\"linux\" -std=c11 -pedantic -DHAVE_ATOMIC -DARCH=\"x86_64\" -DUSE_OPENSSL -DUSE_TLS -DUSE_OPENSSL_DTLS -DUSE_DTLS -DUSE_OPENSSL_SRTP -DUSE_DTLS_SRTP -DUSE_ZLIB -DHAVE_PTHREAD -DHAVE_GETIFADDRS -DHAVE_STRERROR_R -DHAVE_GETOPT -DHAVE_INTTYPES_H -DHAVE_NET_ROUTE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STDBOOL_H -DHAVE_INET6 -DHAVE_RESOLV -DHAVE_SYSLOG -DHAVE_FORK -DHAVE_INET_NTOP -DHAVE_PWD_H -DHAVE_POLL -DHAVE_INET_PTON -DHAVE_SELECT -DHAVE_SELECT_H -DHAVE_SETRLIMIT -DHAVE_SIGNAL -DHAVE_SYS_TIME_H -DHAVE_EPOLL -DHAVE_UNAME -DHAVE_UNISTD_H -DHAVE_STRINGS_H -DVERSION=\"2.0.1\" -DVER_MAJOR=2 -DVER_MINOR=0 -DVER_PATCH=1 -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -DHAVE_ROUTE_LIST -c src/sa/printaddr.c -o build-x86_64/sa/printaddr.o -MD -MF build-x86_64/sa/printaddr.d -MT build-x86_64/sa/printaddr.o CC build-x86_64/sa/pton.o x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DRELEASE -Wall -Wextra -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wbad-function-cast -Wsign-compare -Wnested-externs -Wshadow -Waggregate-return -Wcast-align -Wold-style-definition -Wdeclaration-after-statement -g -O3 -Wuninitialized -Wno-strict-aliasing -fPIC -DLINUX -DOS=\"linux\" -std=c11 -pedantic -DHAVE_ATOMIC -DARCH=\"x86_64\" -DUSE_OPENSSL -DUSE_TLS -DUSE_OPENSSL_DTLS -DUSE_DTLS -DUSE_OPENSSL_SRTP -DUSE_DTLS_SRTP -DUSE_ZLIB -DHAVE_PTHREAD -DHAVE_GETIFADDRS -DHAVE_STRERROR_R -DHAVE_GETOPT -DHAVE_INTTYPES_H -DHAVE_NET_ROUTE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STDBOOL_H -DHAVE_INET6 -DHAVE_RESOLV -DHAVE_SYSLOG -DHAVE_FORK -DHAVE_INET_NTOP -DHAVE_PWD_H -DHAVE_POLL -DHAVE_INET_PTON -DHAVE_SELECT -DHAVE_SELECT_H -DHAVE_SETRLIMIT -DHAVE_SIGNAL -DHAVE_SYS_TIME_H -DHAVE_EPOLL -DHAVE_UNAME -DHAVE_UNISTD_H -DHAVE_STRINGS_H -DVERSION=\"2.0.1\" -DVER_MAJOR=2 -DVER_MINOR=0 -DVER_PATCH=1 -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -DHAVE_ROUTE_LIST -c src/sa/pton.c -o build-x86_64/sa/pton.o -MD -MF build-x86_64/sa/pton.d -MT build-x86_64/sa/pton.o CC build-x86_64/sa/sa.o x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DRELEASE -Wall -Wextra -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wbad-function-cast -Wsign-compare -Wnested-externs -Wshadow -Waggregate-return -Wcast-align -Wold-style-definition -Wdeclaration-after-statement -g -O3 -Wuninitialized -Wno-strict-aliasing -fPIC -DLINUX -DOS=\"linux\" -std=c11 -pedantic -DHAVE_ATOMIC -DARCH=\"x86_64\" -DUSE_OPENSSL -DUSE_TLS -DUSE_OPENSSL_DTLS -DUSE_DTLS -DUSE_OPENSSL_SRTP -DUSE_DTLS_SRTP -DUSE_ZLIB -DHAVE_PTHREAD -DHAVE_GETIFADDRS -DHAVE_STRERROR_R -DHAVE_GETOPT -DHAVE_INTTYPES_H -DHAVE_NET_ROUTE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STDBOOL_H -DHAVE_INET6 -DHAVE_RESOLV -DHAVE_SYSLOG -DHAVE_FORK -DHAVE_INET_NTOP -DHAVE_PWD_H -DHAVE_POLL -DHAVE_INET_PTON -DHAVE_SELECT -DHAVE_SELECT_H -DHAVE_SETRLIMIT -DHAVE_SIGNAL -DHAVE_SYS_TIME_H -DHAVE_EPOLL -DHAVE_UNAME -DHAVE_UNISTD_H -DHAVE_STRINGS_H -DVERSION=\"2.0.1\" -DVER_MAJOR=2 -DVER_MINOR=0 -DVER_PATCH=1 -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -DHAVE_ROUTE_LIST -c src/sa/sa.c -o build-x86_64/sa/sa.o -MD -MF build-x86_64/sa/sa.d -MT build-x86_64/sa/sa.o CC build-x86_64/net/if.o x86_64-linux-gnu-gcc -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DRELEASE -Wall -Wextra -Wmissing-declarations -Wmissing-prototypes -Wstrict-prototypes -Wbad-function-cast -Wsign-compare -Wnested-externs -Wshadow -Waggregate-return -Wcast-align -Wold-style-definition -Wdeclaration-after-statement -g -O3 -Wuninitialized -Wno-strict-aliasing -fPIC -DLINUX -DOS=\"linux\" -std=c11 -pedantic -DHAVE_ATOMIC -DARCH=\"x86_64\" -DUSE_OPENSSL -DUSE_TLS -DUSE_OPENSSL_DTLS -DUSE_DTLS -DUSE_OPENSSL_SRTP -DUSE_DTLS_SRTP -DUSE_ZLIB -DHAVE_PTHREAD -DHAVE_GETIFADDRS -DHAVE_STRERROR_R -DHAVE_GETOPT -DHAVE_INTTYPES_H -DHAVE_NET_ROUTE_H -DHAVE_SYS_SYSCTL_H -DHAVE_STDBOOL_H -DHAVE_INET6 -DHAVE_RESOLV -DHAVE_SYSLOG -DHAVE_FORK -DHAVE_INET_NTOP -DHAVE_PWD_H -DHAVE_POLL -DHAVE_INET_PTON -DHAVE_SELECT -DHAVE_SELECT_H -DHAVE_SETRLIMIT -DHAVE_SIGNAL -DHAVE_SYS_TIME_H -DHAVE_EPOLL -DHAVE_UNAME -DHAVE_UNISTD_H -DHAVE_STRINGS_H -DVERSION=\"2.0.1\" -DVER_MAJOR=2 -DVER_MINOR=0 -DVER_PATCH=1 -Wdate-time -D_FORTIFY_SOURCE=2 -Iinclude -DHAVE_ROUTE_LIST -c src/net/if.c -o build-x86_64/net/if.o -MD -MF build-x86_64/net/if.d -MT build-x86_64/net/if.o In file included from /usr/include/stdio.h:964, from include/re_fmt.h:9, from src/sa/printaddr.c:13: /usr/include/x86_64-linux-gnu/bits/stdio2.h: In function ?fread_unlocked?: /usr/include/x86_64-linux-gnu/bits/stdio2.h:252:25: error: implicit declaration of function ?getc_unlocked?; did you mean ?fgetc_unlocked?? [-Wimplicit-function-declaration] 252 | int __c = getc_unlocked (__stream); | ^~~~~~~~~~~~~ | fgetc_unlocked make[2]: *** [GNUmakefile:108: build-x86_64/sa/printaddr.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[2]: Leaving directory '/<>' dh_auto_build: error: make -j8 "INSTALL=install --strip-program=true" info all RELEASE=1 USE_OPENSSL=1 "EXTRA_LFLAGS=-Wl,-z,relro -Wl,-z,now" "EXTRA_CFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2" returned exit code 2 make[1]: *** [debian/rules:23: override_dh_auto_build] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:41: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 From doko at debian.org Wed Jul 3 13:34:54 2024 From: doko at debian.org (Matthias Klose) Date: Wed, 03 Jul 2024 12:34:54 +0000 Subject: Bug#1075223: linphone: ftbfs with GCC-14 Message-ID: Package: src:linphone Version: 5.2.0-4.3 Severity: important Tags: sid trixie User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-14 [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-14/g++-14, but succeeds to build with gcc-13/g++-13. 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/2024/07/01/linphone_5.2.0-4.3_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 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-14/porting_to.html [...] [ 11%] Building CXX object coreapi/CMakeFiles/linphone-coreapi.dir/proxy.c.o cd /<>/obj-x86_64-linux-gnu/coreapi && /usr/bin/c++ -DBCTBX_LOG_DOMAIN=\"liblinphone\" -DBCTBX_STATIC -DCXX_WRAPPER_ENABLED -DHAVE_CONFIG_H -DJPEG_ENABLED -DLDAP_ENABLED -DLDAP_LIBS_DYNAMIC -DLINPHONE_EXPORTS -DQRCODE_ENABLED -DUSE_BELLESIP -DVCARD_ENABLED -DVIDEO_ENABLED -I/<>/coreapi -I/<>/include -I/<>/src -I/<>/obj-x86_64-linux-gnu -I/<>/obj-x86_64-linux-gnu/coreapi -I/usr/include/belle-sip -I/usr/include/OpenGL -I/usr/include/xsd -I/usr/include/libxml2 -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -DPACKAGE_SOUND_DIR="\"/usr/share/sounds/linphone\"" -DPACKAGE_RING_DIR="\"/usr/share/sounds/linphone/rings\"" -Wdate-time -D_FORTIFY_SOURCE=2 -std=c++17 -fPIC -Wall -Wconversion -Werror=return-type -Winit-self -Wno-error=deprecated-declarations -Wpointer-arith -Wuninitialized -Wunused -Werror -Wextra -Wno-unused-parameter -Wno-missing-field-initializers -fno-strict-aliasing -Wnon-virtual-dtor -Woverloaded-virtual -Wsuggest-override -Wno-error=suggest-override -MD -MT coreapi/CMakeFiles/linphone-coreapi.dir/proxy.c.o -MF CMakeFiles/linphone-coreapi.dir/proxy.c.o.d -o CMakeFiles/linphone-coreapi.dir/proxy.c.o -c /<>/coreapi/proxy.c /<>/coreapi/misc.c: In function ?void linphone_core_update_allocated_audio_bandwidth(LinphoneCore*)?: /<>/coreapi/misc.c:74:48: warning: ?const bctbx_list_t* linphone_core_get_audio_codecs(const LinphoneCore*)? is deprecated [-Wdeprecated-declarations] 74 | for(elem=linphone_core_get_audio_codecs(lc);elem!=NULL;elem=elem->next){ | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~ In file included from /<>/src/conference/conference.h:27, from /<>/src/conference/session/call-session.h:26, from /<>/src/conference/session/streams.h:29, from /<>/include/linphone/utils/utils.h:36, from /<>/src/core/core-p.h:26, from /<>/coreapi/misc.c:25: /<>/include/linphone/core.h:7015:57: note: declared here 7015 | LINPHONE_PUBLIC LINPHONE_DEPRECATED const bctbx_list_t *linphone_core_get_audio_codecs(const LinphoneCore *core); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /<>/coreapi/misc.c: In function ?int get_unique_transport(LinphoneCore*, LinphoneTransportType*, int*)?: /<>/coreapi/misc.c:531:41: warning: ?LinphoneStatus linphone_core_get_sip_transports(LinphoneCore*, LinphoneSipTransports*)? is deprecated [-Wdeprecated-declarations] 531 | linphone_core_get_sip_transports(lc,&tp); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~ /<>/include/linphone/core.h:7286:52: note: declared here 7286 | LINPHONE_PUBLIC LINPHONE_DEPRECATED LinphoneStatus linphone_core_get_sip_transports(LinphoneCore *core, LinphoneSipTransports *transports); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /<>/coreapi/misc.c: In function ?void linphone_core_migrate_proxy_config(LinphoneCore*, LinphoneTransportType)?: /<>/coreapi/misc.c:553:66: warning: ?const char* linphone_proxy_config_get_route(const LinphoneProxyConfig*)? is deprecated [-Wdeprecated-declarations] 553 | const char *route=linphone_proxy_config_get_route(cfg); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~ In file included from /<>/include/linphone/core.h:61: /<>/include/linphone/proxy_config.h:766:49: note: declared here 766 | LINPHONE_PUBLIC LINPHONE_DEPRECATED const char *linphone_proxy_config_get_route(const LinphoneProxyConfig *proxy_config); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /<>/coreapi/misc.c:568:56: warning: ?LinphoneStatus linphone_proxy_config_set_route(LinphoneProxyConfig*, const char*)? is deprecated [-Wdeprecated-declarations] 568 | linphone_proxy_config_set_route(cfg,tmp); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~ /<>/include/linphone/proxy_config.h:759:52: note: declared here 759 | LINPHONE_PUBLIC LINPHONE_DEPRECATED LinphoneStatus linphone_proxy_config_set_route(LinphoneProxyConfig *proxy_config, const char *route); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /<>/coreapi/misc.c: In function ?LinphoneStatus linphone_core_migrate_to_multi_transport(LinphoneCore*)?: /<>/coreapi/misc.c:589:57: warning: ?LinphoneStatus linphone_core_set_sip_transports(LinphoneCore*, const LinphoneSipTransports*)? is deprecated [-Wdeprecated-declarations] 589 | linphone_core_set_sip_transports(lc,&newtp); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~ /<>/include/linphone/core.h:7273:52: note: declared here 7273 | LINPHONE_PUBLIC LINPHONE_DEPRECATED LinphoneStatus linphone_core_set_sip_transports(LinphoneCore *core, const LinphoneSipTransports *transports); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /<>/coreapi/misc.c: In function ?bool_t linphone_core_file_format_supported(LinphoneCore*, const char*)?: /<>/coreapi/misc.c:937:70: warning: ?const char** linphone_core_get_supported_file_formats(LinphoneCore*)? is deprecated [-Wdeprecated-declarations] 937 | const char **formats=linphone_core_get_supported_file_formats(lc); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~ /<>/coreapi/misc.c:914:15: note: declared here 914 | const char ** linphone_core_get_supported_file_formats(LinphoneCore *core){ | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ cc1plus: all warnings being treated as errors make[4]: *** [coreapi/CMakeFiles/linphone-coreapi.dir/build.make:485: coreapi/CMakeFiles/linphone-coreapi.dir/lpconfig.c.o] Error 1 make[4]: *** Waiting for unfinished jobs.... /<>/coreapi/player.c: In function ?void on_eof(void*, MSFilter*, unsigned int, void*)?: /<>/coreapi/player.c:184:79: warning: ?LinphonePlayerCbs* linphone_player_get_callbacks(const LinphonePlayer*)? is deprecated [-Wdeprecated-declarations] 184 | LinphonePlayerCbs *cbs = linphone_player_get_callbacks(player); | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~ /<>/coreapi/player.c:60:21: note: declared here 60 | LinphonePlayerCbs * linphone_player_get_callbacks(const LinphonePlayer *player) { | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ make[4]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[3]: *** [CMakeFiles/Makefile2:350: coreapi/CMakeFiles/linphone-coreapi.dir/all] Error 2 make[3]: Leaving directory '/<>/obj-x86_64-linux-gnu' make[2]: *** [Makefile:139: all] Error 2 make[2]: Leaving directory '/<>/obj-x86_64-linux-gnu' dh_auto_build: error: cd obj-x86_64-linux-gnu && make -j8 "INSTALL=install --strip-program=true" VERBOSE=1 returned exit code 2 make[1]: *** [debian/rules:77: override_dh_auto_build-arch] Error 25 make[1]: Leaving directory '/<>' make: *** [debian/rules:50: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 From doko at debian.org Wed Jul 3 13:42:09 2024 From: doko at debian.org (Matthias Klose) Date: Wed, 03 Jul 2024 12:42:09 +0000 Subject: Bug#1075446: ring: ftbfs with GCC-14 Message-ID: Package: src:ring Version: 20231201.0~ds1-1 Severity: important Tags: sid trixie User: debian-gcc at lists.debian.org Usertags: ftbfs-gcc-14 [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-14/g++-14, but succeeds to build with gcc-13/g++-13. 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/2024/07/01/ring_20231201.0~ds1-1_unstable_gccexp.log The last lines of the build log are at the end of this report. To build with GCC 14, either set CC=gcc-14 CXX=g++-14 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-14/porting_to.html [...] Node: getAudioPluginList: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getAudioOutputDeviceList: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getAudioInputDeviceList: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getCurrentAudioDevicesIndex: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getSupportedTlsMethod: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getSupportedCiphers: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: validateCertificate: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: validateCertificatePath: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getCertificateDetails: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getCertificateDetailsPath: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getPinnedCertificates: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: pinCertificate: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getCertificatesByStatus: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getTrustRequests: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getContactDetails: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getContacts: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getAllIpInterface: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getAllIpInterfaceByName: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getConnectionList: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getChannelList: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getConversations: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getActiveCalls: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getConversationRequests: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: updateConversationInfos: Option 'org.qtproject.QtDBus.QtTypeName.In2' not allowed or supported in this context! Option ignored... Node: conversationInfos: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: setConversationPreferences: Option 'org.qtproject.QtDBus.QtTypeName.In2' not allowed or supported in this context! Option ignored... Node: getConversationPreferences: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getConversationMembers: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: getDefaultModerators: Option 'org.qtproject.QtDBus.QtTypeName.Out0' not allowed or supported in this context! Option ignored... Node: knownDevicesChanged: Option 'org.qtproject.QtDBus.QtTypeName.Out1' not allowed or supported in this context! Option ignored... Node: userSearchEnded: Option 'org.qtproject.QtDBus.QtTypeName.Out3' not allowed or supported in this context! Option ignored... Node: incomingAccountMessage: Option 'org.qtproject.QtDBus.QtTypeName.Out3' not allowed or supported in this context! Option ignored... Node: activeCallsChanged: Option 'org.qtproject.QtDBus.QtTypeName.Out2' not allowed or supported in this context! Option ignored... Node: accountDetailsChanged: Option 'org.qtproject.QtDBus.QtTypeName.Out1' not allowed or supported in this context! Option ignored... Node: volatileAccountDetailsChanged: Option 'org.qtproject.QtDBus.QtTypeName.Out1' not allowed or supported in this context! Option ignored... Node: conversationLoaded: Option 'org.qtproject.QtDBus.QtTypeName.Out3' not allowed or supported in this context! Option ignored... Node: messagesFound: Option 'org.qtproject.QtDBus.QtTypeName.Out3' not allowed or supported in this context! Option ignored... Node: messageReceived: Option 'org.qtproject.QtDBus.QtTypeName.Out2' not allowed or supported in this context! Option ignored... Node: conversationProfileUpdated: Option 'org.qtproject.QtDBus.QtTypeName.Out2' not allowed or supported in this context! Option ignored... Node: conversationRequestReceived: Option 'org.qtproject.QtDBus.QtTypeName.Out2' not allowed or supported in this context! Option ignored... Node: conversationPreferencesUpdated: Option 'org.qtproject.QtDBus.QtTypeName.Out2' not allowed or supported in this context! Option ignored... make all-am make[6]: Entering directory '/<>/daemon/bin/dbus' g++ -std=gnu++17 -DHAVE_CONFIG_H -I. -I../.. -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -fvisibility=hidden -DLIBJAMI_BUILD -DASIO_STANDALONE -DMSGPACK_NO_BOOST -I/<>/daemon/contrib/x86_64-linux-gnu/include -DPJ_AUTOCONF=1 -I/usr/include/jsoncpp -I/<>/daemon/src -I/<>/daemon/src/config -I/<>/daemon/src/media -I/<>/daemon/test -I/<>/daemon/src/jami -DPREFIX=\"/usr\" -DJAMI_DATADIR=\"/usr/share/jami\" -DENABLE_TRACE -DJAMI_REVISION=\"\" -DJAMI_DIRTY_REPO=\"dirty\" -DPJSIP_MAX_PKT_LEN=8000 -DPJ_AUTOCONF=1 -Wdate-time -D_FORTIFY_SOURCE=2 -I../../src/jami -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -MT jamid-main.o -MD -MP -MF .deps/jamid-main.Tpo -c -o jamid-main.o `test -f 'main.cpp' || echo './'`main.cpp /usr/bin/sed -e 's,[@]LIBEXECDIR[@],/usr/libexec,g' < net.jami.daemon.service.in > cx.ring.Ring.service In file included from /usr/include/sdbus-c++/ConvenienceApiClasses.h:30, from /usr/include/sdbus-c++/IObject.h:30, from /usr/include/sdbus-c++/sdbus-c++.h:28, from dbuscallmanager.adaptor.h:9, from dbuscallmanager.hpp:24, from main.cpp:29: /usr/include/sdbus-c++/Message.h: In member function ?void sdbus::Message::deserializeArrayFast(_Array&)?: /usr/include/sdbus-c++/Message.h:490:14: error: ?copy_n? is not a member of ?std?; did you mean ?copy?? 490 | std::copy_n(arrayPtr, elementsInMsg, items.begin()); | ^~~~~~ | copy make[6]: *** [Makefile:638: jamid-main.o] Error 1 make[6]: Leaving directory '/<>/daemon/bin/dbus' make[5]: *** [Makefile:511: all] Error 2 make[5]: Leaving directory '/<>/daemon/bin/dbus' make[4]: *** [Makefile:640: all-recursive] Error 1 make[4]: Leaving directory '/<>/daemon/bin' make[3]: *** [Makefile:596: all-recursive] Error 1 make[3]: Leaving directory '/<>/daemon' make[2]: *** [Makefile:502: all] Error 2 make[2]: Leaving directory '/<>/daemon' make[1]: *** [debian/rules:89: override_dh_auto_build] Error 2 make[1]: Leaving directory '/<>' make: *** [debian/rules:23: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 From noreply at release.debian.org Sat Jul 6 05:39:07 2024 From: noreply at release.debian.org (Debian testing watch) Date: Sat, 06 Jul 2024 04:39:07 +0000 Subject: lime 5.2.0+dfsg-4 MIGRATED to testing Message-ID: FYI: The status of the lime source package in Debian's testing distribution has changed. Previous version: 5.2.0+dfsg-3 Current version: 5.2.0+dfsg-4 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information. From info at tgshopadboard.com Sat Jul 6 16:54:12 2024 From: info at tgshopadboard.com (Bunq) Date: Sat, 06 Jul 2024 15:54:12 +0000 Subject: Open een gratis Easy Savings account! Message-ID: <172028125249.1613.15841777591294880895@tgshopadboard.com> Advertorial Laat je spaargeld moeiteloos groeien met een torenhoge rente van 2,46%, die wekelijks wordt uitbetaald. Tevens heb je mogelijkheid om een gratis creditcard toe te voegen aan je bunq app waarmee je overal ter wereld en online kunt betalen. Open in slechts 5 minuten je gratis spaarrekening, en geniet van de vrijheid om je geld te beheren zoals jij dat wilt. Aan de slag Hoge rente. Geen kosten. Open een gratis Easy Savings account! Geplaatst door SHOPBOARD LTD, 7 Bell Yard, London, England, WC2A 2JR, 12313387. Uitschrijven Complaints:email -------------- next part -------------- An HTML attachment was scrubbed... URL: From owner at bugs.debian.org Sun Jul 7 19:57:05 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Sun, 07 Jul 2024 18:57:05 +0000 Subject: Processed: block 1075446 with 1075496 References: <1720378493-2587-bts-pino@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > block 1075446 with 1075496 Bug #1075446 [src:ring] ring: ftbfs with GCC-14 1075446 was not blocked by any bugs. 1075446 was not blocking any bugs. Added blocking bug(s) of 1075446: 1075496 > thanks Stopping processing here. Please contact me if you need assistance. -- 1075446: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075446 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From zeha at debian.org Mon Jul 8 13:22:36 2024 From: zeha at debian.org (Chris Hofstaedtler) Date: Mon, 08 Jul 2024 14:22:36 +0200 Subject: Bug#1075961: FTBFS: hep.c:985:41: error: implicit declaration of function =?UTF-8?Q?=E2=80=98inet=5Fntop=E2=80=99?= Message-ID: <172044135659.533643.9937707242114299848.reportbug@per> Source: kamailio Version: 5.6.3-2 Severity: serious Tags: ftbfs kamailio currently FTBFS on s390x, but built there before. The same problem can be observed on ppc64: https://buildd.debian.org/status/fetch.php?pkg=kamailio&arch=s390x&ver=5.8.2-2&stamp=1720212227&raw=0 hep.c: In function ?hepv3_get_chunk?: hep.c:985:41: error: implicit declaration of function ?inet_ntop? [-Werror=implicit-function-declaration] 985 | inet_ntop(AF_INET, &(hg->hep_src_ip4->data), ipstr, | ^~~~~~~~~ gcc -fPIC -DPIC -pthread -DKSR_PTHREAD_MUTEX_SHARED -Wall -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -DVERSION_NODATE -DNAME='"kamailio"' -DVERSION='"5.8.2"' -DARCH='"s390x"' -DOS='linux_' -DOS_QUOTED='"linux"' -DCOMPILER='"gcc 13.3.0"' -D__CPU_s390x -D__OS_linux -DVERSIONVAL=5008002 -DCFG_DIR='"/etc/kamailio/"' -DSHARE_DIR='"/usr/share/kamailio/"' -DRUN_DIR='"/var/run/kamailio/"' -DPKG_MALLOC -DSHM_MMAP -DDNS_IP_HACK -DUSE_MCAST -DUSE_TCP -DDISABLE_NAGLE -DHAVE_RESOLV_RES -DUSE_DNS_CACHE -DUSE_DNS_FAILOVER -DUSE_DST_BLOCKLIST -DUSE_NAPTR -DMEM_JOIN_FREE -DF_MALLOC -DQ_MALLOC -DTLSF_MALLOC -DDBG_SR_MEMORY -DUSE_TLS -DTLS_HOOKS -DUSE_CORE_STATS -DSTATISTICS -DMALLOC_STATS -DUSE_SCTP -DHAVE_GETHOSTBYNAME2 -DHAVE_UNION_SEMUN -DHAVE_SCHED_YIELD -DHAVE_MSG_NOSIGNAL -DHAVE_MSGHDR_MSG_CONTROL -DHAVE_ALLOCA_H -DHAVE_TIMEGM -DHAVE_SCHED_SETSCHEDULER -DHAVE_IP_MREQN -DUSE_RAW_SOCKS -DUSE_PTHREAD_MUTEX -DHAVE_EPOLL -DHAVE_SIGIO_RT -DSIGINFO64_WORKAROUND -DUSE_FUTEX -DHAVE_SELECT -DMOD_NAME='"sipcapture"' -DMOD_NAMEID='sipcapture' -c sipcapture.c -o sipcapture.o -MMD -MP In file included from ../../core/atomic_ops.h:180, from ../../core/locking.h:72, from ../../core/rpc.h:34, from ../../core/sr_module.h:36, from sipcapture.c:54: ... make[4]: *** [../../Makefile.rules:100: hep.o] Error 1 ... From owner at bugs.debian.org Mon Jul 8 20:27:03 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Mon, 08 Jul 2024 19:27:03 +0000 Subject: Processed: (No Subject) References: <29c2f908-fb57-40cc-a033-f52dfcbec1fe@torreviejawireless.org> Message-ID: Processing commands for control at bugs.debian.org: > forwarded 1071954 https://github.com/irontec/sngrep/issues/492 Bug #1071954 [src:sngrep] sngrep: FTBFS against libgcrypt 1.11 Set Bug forwarded-to-address to 'https://github.com/irontec/sngrep/issues/492'. > -- Stopping processing here. Please contact me if you need assistance. -- 1071954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071954 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From owner at bugs.debian.org Mon Jul 8 22:39:08 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Mon, 08 Jul 2024 21:39:08 +0000 Subject: Processed: reassign 1075900 to exim4, tagging 1075979, tagging 1040102, found 1040102 in 0.9.6-2 ... References: <1720474534-3194-bts-anbe@debian.org> Message-ID: Processing commands for control at bugs.debian.org: > reassign 1075900 exim4 4.96-15+deb12u4 Bug #1075900 [exim4/stable,stable-security] Exim4 in Debian can't deliver to DANE secured Mailservers Warning: Unknown package 'exim4/stable' Warning: Unknown package 'stable-security' Bug reassigned from package 'exim4/stable,stable-security' to 'exim4'. Ignoring request to alter found versions of bug #1075900 to the same values previously set Ignoring request to alter fixed versions of bug #1075900 to the same values previously set Bug #1075900 [exim4] Exim4 in Debian can't deliver to DANE secured Mailservers Marked as found in versions exim4/4.96-15+deb12u4. > tags 1075979 + sid trixie Bug #1075979 [src:molds] molds: FTBFS with mpich as default MPI provider: /usr/bin/ld: cannot find -lmpi_cxx: No such file or directory Added tag(s) sid and trixie. > tags 1040102 + sid trixie Bug #1040102 {Done: Bastian Germann } [src:pyinotify] pyinotify: deprecation of Python libraries asyncore and asynchat Added tag(s) trixie and sid. > found 1040102 0.9.6-2 Bug #1040102 {Done: Bastian Germann } [src:pyinotify] pyinotify: deprecation of Python libraries asyncore and asynchat Marked as found in versions pyinotify/0.9.6-2. > notfound 1075961 5.6.3-2 Bug #1075961 [src:kamailio] FTBFS: hep.c:985:41: error: implicit declaration of function ?inet_ntop? No longer marked as found in versions kamailio/5.6.3-2. > found 1075961 5.8.2-2 Bug #1075961 [src:kamailio] FTBFS: hep.c:985:41: error: implicit declaration of function ?inet_ntop? Marked as found in versions kamailio/5.8.2-2. > tags 1075811 + sid trixie Bug #1075811 {Done: Bastian Germann } [python3-pyinotify] autokey-qt can be installed but will nor run Added tag(s) trixie and sid. > thanks Stopping processing here. Please contact me if you need assistance. -- 1040102: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040102 1075811: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075811 1075900: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075900 1075961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075961 1075979: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075979 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From ametzler at bebt.de Tue Jul 9 12:25:06 2024 From: ametzler at bebt.de (Andreas Metzler) Date: Tue, 9 Jul 2024 13:25:06 +0200 Subject: Bug#1071933: libccrtp: diff for NMU version 2.0.9-4.1 References: Message-ID: Control: tags 1071933 + patch Control: tags 1071933 + pending Dear maintainer, I've prepared an NMU for libccrtp (versioned as 2.0.9-4.1) and uploaded it to unstable. Regards. -------------- next part -------------- A non-text attachment was scrubbed... Name: libccrtp-2.0.9-4.1-nmu.diff Type: text/x-diff Size: 7141 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From owner at bugs.debian.org Tue Jul 9 12:27:04 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 09 Jul 2024 11:27:04 +0000 Subject: Processed: libccrtp: diff for NMU version 2.0.9-4.1 References: Message-ID: Processing control commands: > tags 1071933 + patch Bug #1071933 [src:libccrtp] libccrtp: FTBFS against libgcrypt 1.11 Added tag(s) patch. > tags 1071933 + pending Bug #1071933 [src:libccrtp] libccrtp: FTBFS against libgcrypt 1.11 Added tag(s) pending. -- 1071933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071933 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From ftpmaster at ftp-master.debian.org Tue Jul 9 12:31:12 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Tue, 09 Jul 2024 11:31:12 +0000 Subject: Processing of libccrtp_2.0.9-4.1_multi.changes Message-ID: libccrtp_2.0.9-4.1_multi.changes uploaded successfully to localhost along with the files: libccrtp_2.0.9-4.1.dsc libccrtp_2.0.9-4.1.debian.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org) From ftpmaster at ftp-master.debian.org Tue Jul 9 12:34:11 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Tue, 09 Jul 2024 11:34:11 +0000 Subject: libccrtp_2.0.9-4.1_multi.changes ACCEPTED into unstable Message-ID: Thank you for your contribution to Debian. Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Tue, 09 Jul 2024 13:14:07 +0200 Source: libccrtp Architecture: source Version: 2.0.9-4.1 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: Andreas Metzler Closes: 1071933 Changes: libccrtp (2.0.9-4.1) unstable; urgency=medium . * Non-maintainer upload. * Delete outdated (and renamed) copy of libgcrypt.m4 and use upstream macro instead to fix FTBFS against libgcrypt without libgcrypt-config. Closes: #1071933 Checksums-Sha1: 072fb951e08362b5a3e7c906acfe2f5031c25bb7 2135 libccrtp_2.0.9-4.1.dsc e6c44ded8a4730ea24ed614df437fbcaff1fb5ec 12424 libccrtp_2.0.9-4.1.debian.tar.xz Checksums-Sha256: 0dd022a96c63b557e2fd066b43a8a6741b2a011ee50666385607befece350fa1 2135 libccrtp_2.0.9-4.1.dsc 4d601926f48ae7dd618b0aa5cbf47f5abc2d05b8094359a0e3d95b8561c994b2 12424 libccrtp_2.0.9-4.1.debian.tar.xz Files: c258ec680f5a7ef4eac1f4d11c995bbc 2135 devel optional libccrtp_2.0.9-4.1.dsc f830af3f1d74c4dcfef90258bd119adc 12424 devel optional libccrtp_2.0.9-4.1.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEE0uCSA5741Jbt9PpepU8BhUOCFIQFAmaNHb8ACgkQpU8BhUOC FITvMQ//ShaUIVqkaoXeq+661CSgdwGYfMkY9DTARu3qRzcgq+QyV147MnjkScQ1 utJZgrrhpMNB6NTh5WYqzpc+AaM35FfczJz+feMVE9C/P7gb4dniyMzNywb08rhe +csPbbXupCv0XX1l9Y+O9+UAbo60HEprUuXeLWbegUVEeuTrbZUTyJhckExKWga3 s1cOwYmzipA04zK/C3+dSJlidf8dklIAIrVbNwQOmgVBc6hktOr2Rv8SVqF2u+Di VdfSLqTgV0myy0JEY3TfV/+xsUHoc3bRJb1ynIGR5LWcSEUgL9cCJkjE1sL+SMox f1hoSoFmUsXKHOC1yfssrn+XKm38FOcTPdGpFPSm/3R2qnbyj9P158WjFQWcSJ4g IIQ1to0Kn9J2+42+l/+cSqah7ClfCUxLR/Iy2FASSSzo97hPSc8d56BOIi+JjeQC kZ3ymaPZc0jQPXYv734dP6gAKcKWoxEekewJyTX4t/1gIimU3nUpash3JP7zgK+G X0uldcps0JU0We1+BbA3PQR3BD3d3Rh4VT9+pkkdLBp7xASLKwqb5ZbBoYOpTkHA hxcb9LC46QaHkRewWmVaYhKAu5uSWi/MZ4dcRKf32BGEndyZrOwDRe+daCvJ2GbO 6M5QC0gt4ExbXMUXCdQS/h+3zz1ZqoIj0+Co69Tnnr2Fdka7Gwk= =O7Ft -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: not available URL: From owner at bugs.debian.org Tue Jul 9 12:39:03 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Tue, 09 Jul 2024 11:39:03 +0000 Subject: Bug#1071933: marked as done (libccrtp: FTBFS against libgcrypt 1.11) References: Message-ID: Your message dated Tue, 09 Jul 2024 11:34:11 +0000 with message-id and subject line Bug#1071933: fixed in libccrtp 2.0.9-4.1 has caused the Debian Bug report #1071933, regarding libccrtp: FTBFS against libgcrypt 1.11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 1071933: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071933 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Andreas Metzler Subject: libccrtp: FTBFS against libgcrypt 1.11 Date: Sun, 26 May 2024 08:07:06 +0200 Size: 3397 URL: -------------- next part -------------- An embedded message was scrubbed... From: Debian FTP Masters Subject: Bug#1071933: fixed in libccrtp 2.0.9-4.1 Date: Tue, 09 Jul 2024 11:34:11 +0000 Size: 6624 URL: From ftpmaster at ftp-master.debian.org Wed Jul 10 15:54:14 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Wed, 10 Jul 2024 14:54:14 +0000 Subject: Processing of sngrep_1.8.2-1_source.changes Message-ID: sngrep_1.8.2-1_source.changes uploaded successfully to localhost along with the files: sngrep_1.8.2-1.dsc sngrep_1.8.2.orig.tar.gz sngrep_1.8.2.orig.tar.gz.asc sngrep_1.8.2-1.debian.tar.xz sngrep_1.8.2-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) From ftpmaster at ftp-master.debian.org Wed Jul 10 16:04:14 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Wed, 10 Jul 2024 15:04:14 +0000 Subject: sngrep_1.8.2-1_source.changes ACCEPTED into unstable Message-ID: Thank you for your contribution to Debian. Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Wed, 10 Jul 2024 16:37:07 +0200 Source: sngrep Architecture: source Version: 1.8.2-1 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: Victor Seva Closes: 1071954 Changes: sngrep (1.8.2-1) unstable; urgency=medium . * New upstream version 1.8.2 * support libcrypt 1.11 (Closes: #1071954) Checksums-Sha1: c116c869329e3f9d59681b88fa41d7d6314a2ef3 1670 sngrep_1.8.2-1.dsc b7dcf5c215ebfeeeb40d52a8e4e87fcbad393bee 254184 sngrep_1.8.2.orig.tar.gz 1446699e5a5ea2e98de3fe815182c969a56731cf 488 sngrep_1.8.2.orig.tar.gz.asc 09f2c22b7762353dc0cb9162f4ed758cb252f4c0 5764 sngrep_1.8.2-1.debian.tar.xz 7f10f15ec5b1c6eb03d66f2733ad06c96cfa5fe1 6568 sngrep_1.8.2-1_amd64.buildinfo Checksums-Sha256: 284e8e36f6d04defba21eaf4bd84abe99b21d300d777bae7a9878f9bdc8bf106 1670 sngrep_1.8.2-1.dsc 1cd05bddd531b353e3069c5243e7076b60a3ee907dbbc3c9c2834676ed8c4bac 254184 sngrep_1.8.2.orig.tar.gz d20f1a154786e6521f2570865a54426385ce2b8c616538d4f482f9338b5a6e42 488 sngrep_1.8.2.orig.tar.gz.asc 254b3c8df7f15fc494b18a0e4f52a03ad25df784f998e57b7985b095acff40db 5764 sngrep_1.8.2-1.debian.tar.xz dccf6fa192df7f3d30e8599923dd3d5c9a081b74fff8a9c9810c130d6a1ae843 6568 sngrep_1.8.2-1_amd64.buildinfo Files: 50f65a868b4b44acce7617c13d89e24b 1670 comm optional sngrep_1.8.2-1.dsc eb2a398e2e98993ee2a19a3afddfc282 254184 comm optional sngrep_1.8.2.orig.tar.gz 22ce372cb4b42f6bc8369ede408a3067 488 comm optional sngrep_1.8.2.orig.tar.gz.asc 45dd57a8326e586c8212818d6a08f7c1 5764 comm optional sngrep_1.8.2-1.debian.tar.xz e5223c5210550787a2370471556ab87a 6568 comm optional sngrep_1.8.2-1_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iIcEARYKAC8WIQQq6AO8RS0zF4SC1vh9e2XEKg7IsgUCZo6dQxEcdnNldmFAZGVi aWFuLm9yZwAKCRB9e2XEKg7IsoZTAP4h1dvnXA/dRWKrxh5ZtMNeyUv69MyZweHh R+1ohlbnWgEAmFXBybAkFFOmqAmXuaK68uiPbVdTeB5IrgE28cGdGwQ= =Ddkt -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: not available URL: From owner at bugs.debian.org Wed Jul 10 16:06:05 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Wed, 10 Jul 2024 15:06:05 +0000 Subject: Bug#1071954: marked as done (sngrep: FTBFS against libgcrypt 1.11) References: Message-ID: Your message dated Wed, 10 Jul 2024 15:04:14 +0000 with message-id and subject line Bug#1071954: fixed in sngrep 1.8.2-1 has caused the Debian Bug report #1071954, regarding sngrep: FTBFS against libgcrypt 1.11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner at bugs.debian.org immediately.) -- 1071954: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1071954 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Andreas Metzler Subject: sngrep: FTBFS against libgcrypt 1.11 Date: Sun, 26 May 2024 13:47:05 +0200 Size: 3153 URL: -------------- next part -------------- An embedded message was scrubbed... From: Debian FTP Masters Subject: Bug#1071954: fixed in sngrep 1.8.2-1 Date: Wed, 10 Jul 2024 15:04:14 +0000 Size: 6611 URL: From noreply at release.debian.org Thu Jul 11 05:39:15 2024 From: noreply at release.debian.org (Debian testing autoremoval watch) Date: Thu, 11 Jul 2024 04:39:15 +0000 Subject: sngrep is marked for autoremoval from testing Message-ID: sngrep 1.8.1-1 is marked for autoremoval from testing on 2024-08-09 It is affected by these RC bugs: 1071954: sngrep: FTBFS against libgcrypt 1.11 https://bugs.debian.org/1071954 This mail is generated by: https://salsa.debian.org/release-team/release-tools/-/blob/master/mailer/mail_autoremovals.pl Autoremoval data is generated by: https://salsa.debian.org/qa/udd/-/blob/master/udd/testing_autoremovals_gatherer.pl From ftpmaster at ftp-master.debian.org Thu Jul 11 13:38:20 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Thu, 11 Jul 2024 12:38:20 +0000 Subject: Processing of biboumi_9.0-5.1_source.changes Message-ID: biboumi_9.0-5.1_source.changes uploaded successfully to localhost along with the files: biboumi_9.0-5.1.dsc biboumi_9.0-5.1.debian.tar.xz biboumi_9.0-5.1_arm64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) From zeha at debian.org Thu Jul 11 13:34:14 2024 From: zeha at debian.org (Chris Hofstaedtler) Date: Thu, 11 Jul 2024 14:34:14 +0200 Subject: Bug#1073626: biboumi: diff for NMU version 9.0-5.1 References: <171870379696.3560576.16776467238399011795@subdivi.de> Message-ID: <20240711123414.nib3uumi4m4hv66m@debian.org> Control: tags 1073626 + pending Dear maintainer, I've prepared an NMU for biboumi (versioned as 9.0-5.1) and uploaded it to DELAYED/7. Please feel free to tell me if I should delay it longer. Regards. -------------- next part -------------- A non-text attachment was scrubbed... Name: biboumi-9.0-5.1-nmu.diff Type: text/x-diff Size: 1123 bytes Desc: not available URL: From owner at bugs.debian.org Thu Jul 11 13:39:03 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Thu, 11 Jul 2024 12:39:03 +0000 Subject: Processed: biboumi: diff for NMU version 9.0-5.1 References: <20240711123414.nib3uumi4m4hv66m@debian.org> <171870379696.3560576.16776467238399011795@subdivi.de> Message-ID: Processing control commands: > tags 1073626 + pending Bug #1073626 [biboumi] biboumi: move aliased files from / to /usr (DEP17) Added tag(s) pending. -- 1073626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073626 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From cyber-sec-alert at mail.beehiiv.com Fri Jul 12 14:32:00 2024 From: cyber-sec-alert at mail.beehiiv.com (CyberSecAlert) Date: Fri, 12 Jul 2024 13:32:00 +0000 (UTC) Subject: CyberSecAlert: Olympics Ticket Scam, Windows Zero-Day, Google Advanced Protection, and Kimsuky Attacks Message-ID: <6dcPGqavQx-qXVw3lnElHA@geopod-ismtpd-38> : (https://news.futureparty.com/subscribe?_bhba=bf0b6b11-140c-4ec7-a518-a25cbfcf93b1) View image: (https://media.beehiiv.com/cdn-cgi/image/fit=scale-down,format=auto,onerror=redirect,quality=80/uploads/asset/file/d69b803d-c637-4cd4-9147-e87d58e10d6f/image.png?t=1720705272) Caption: The BRRR: (https://thebrrr.beehiiv.com/subscribe?_bhba=bf0b6b11-140c-4ec7-a518-a25cbfcf93b1) # CyberSecAlert: Olympics Ticket Scam, Windows Zero-Day, Google Advanced Protection, and Kimsuky Attacks ## Ticket Heist Fraud Gang Uses 700 Domains to Sell Fake Olympics Tickets A fraud gang has been using 700 domains to sell fake Olympics tickets. This widespread scam underscores the need for vigilance when purchasing event tickets online and the importance of verifying the legitimacy of ticket vendors. ## Windows MSHTML Zero-Day Used in Malware Attacks for Over a Year A zero-day vulnerability in Windows MSHTML has been exploited in malware attacks for over a year. This critical flaw highlights the importance of keeping systems updated and applying security patches promptly to protect against such long-term threats. ## Google Advanced Protection Program Gets Passkeys for High-Risk Users Google has introduced passkeys to its Advanced Protection Program for high-risk users. This enhancement provides an additional layer of security, making it harder for attackers to compromise accounts protected by this program. ## Japan Warns of Attacks Linked to North Korean Kimsuky Hackers Japan has issued a warning about cyberattacks linked to North Korean Kimsuky hackers. These attacks emphasize the ongoing threat posed by state-sponsored cyber groups and the need for robust cybersecurity measures to defend against them. ??????????????????????????? The Cheat Code: (https://cheatcodenl.com/subscribe?_bhba=bf0b6b11-140c-4ec7-a518-a25cbfcf93b1) Stay informed and secure with CyberSecAlert. ??? You are reading a plain text version of this post. For the best experience, copy and paste this link in your browser to view the post online: https://cyber-sec-alert.beehiiv.com/p/cybersecalert-olympics-ticket-scam-windows-zeroday-google-advanced-protection-kimsuky-attacks -------------- next part -------------- An HTML attachment was scrubbed... URL: From zeha at debian.org Fri Jul 12 15:44:24 2024 From: zeha at debian.org (Chris Hofstaedtler) Date: Fri, 12 Jul 2024 16:44:24 +0200 Subject: Bug#1073741: Ping of bugs: move aliased files from / to /usr (DEP17) References: <171870379777.3560576.10498330833174478639@subdivi.de> Message-ID: Dear Maintainers, This is a friendly ping about a usrmerge bug in one your packages. Please consider fixing it soon. Thanks, Chris From owner at bugs.debian.org Fri Jul 12 19:21:05 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Fri, 12 Jul 2024 18:21:05 +0000 Subject: Processed: ax25-tools,dahdi-tools: install program with same name (sethdlc) References: Message-ID: Processing control commands: > block 1075856 by -1 Bug #1075856 [debian-policy] Clarify filename conflicts for programs 1075856 was not blocked by any bugs. 1075856 was not blocking any bugs. Added blocking bug(s) of 1075856: 1076215 -- 1075856: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075856 1076215: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1076215 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From zeha at debian.org Fri Jul 12 19:17:59 2024 From: zeha at debian.org (Chris Hofstaedtler) Date: Fri, 12 Jul 2024 20:17:59 +0200 Subject: Bug#1076215: ax25-tools, dahdi-tools: install program with same name (sethdlc) Message-ID: Package: ax25-tools,dahdi-tools Control: block 1075856 by -1 Hi, your packages ax25-tools and dahdi-tools both install a program names "sethdlc", although in different components of the PATH. As this is confusing and a possible source of bugs, policy bug #1075856 wants to outlaw this. Please find a solution for your packages. Ideas: 1) if one of the programs is an internal implementation detail of the package, install it into a private path in /usr/lib instead. 2) rename one of the programs 3) rename both of the programs Thanks, Chris From debian-hams at trinnet.net Fri Jul 12 21:51:54 2024 From: debian-hams at trinnet.net (David Ranch) Date: Fri, 12 Jul 2024 13:51:54 -0700 Subject: Bug#1076215: ax25-tools, dahdi-tools: install program with same name (sethdlc) In-Reply-To: References: Message-ID: Hello Chris, Ax25-tool's sethdlc program predates this far later Asterisk dahdi-tools utility by decades so I would argue that Asterisk should change. That said, I don't know if there is much use for the sethdlc tool these days as it was used with legacy hardware. I've CCed DL9SAU here who supports the the primary version of these tools at https://linux-ax25.in-berlin.de/wiki/Main_Page to see what his thoughts might be here. --David KI6ZHD On 07/12/2024 11:17 AM, Chris Hofstaedtler wrote: > Package: ax25-tools,dahdi-tools > Control: block 1075856 by -1 > > Hi, > > your packages ax25-tools and dahdi-tools both install a program > names "sethdlc", although in different components of the PATH. > > As this is confusing and a possible source of bugs, policy bug > #1075856 wants to outlaw this. > > Please find a solution for your packages. Ideas: > 1) if one of the programs is an internal implementation detail of > the package, install it into a private path in /usr/lib instead. > 2) rename one of the programs > 3) rename both of the programs > > Thanks, > Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From debian-hams at trinnet.net Fri Jul 12 21:51:54 2024 From: debian-hams at trinnet.net (David Ranch) Date: Fri, 12 Jul 2024 13:51:54 -0700 Subject: Bug#1076215: ax25-tools, dahdi-tools: install program with same name (sethdlc) In-Reply-To: References: Message-ID: Hello Chris, Ax25-tool's sethdlc program predates this far later Asterisk dahdi-tools utility by decades so I would argue that Asterisk should change. That said, I don't know if there is much use for the sethdlc tool these days as it was used with legacy hardware. I've CCed DL9SAU here who supports the the primary version of these tools at https://linux-ax25.in-berlin.de/wiki/Main_Page to see what his thoughts might be here. --David KI6ZHD On 07/12/2024 11:17 AM, Chris Hofstaedtler wrote: > Package: ax25-tools,dahdi-tools > Control: block 1075856 by -1 > > Hi, > > your packages ax25-tools and dahdi-tools both install a program > names "sethdlc", although in different components of the PATH. > > As this is confusing and a possible source of bugs, policy bug > #1075856 wants to outlaw this. > > Please find a solution for your packages. Ideas: > 1) if one of the programs is an internal implementation detail of > the package, install it into a private path in /usr/lib instead. > 2) rename one of the programs > 3) rename both of the programs > > Thanks, > Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From daniel at mindani.net Sat Jul 13 00:36:31 2024 From: daniel at mindani.net (Daniel Markstedt) Date: Fri, 12 Jul 2024 23:36:31 +0000 Subject: Bug#1073741: [Pkg-netatalk-devel] Bug#1073724: Ping of bugs: move aliased files from / to /usr (DEP17) In-Reply-To: References: <171870379689.3560576.8610796708309524963@subdivi.de> <171870379777.3560576.10498330833174478639@subdivi.de> Message-ID: On Friday, July 12th, 2024 at 11:44 PM, Chris Hofstaedtler wrote: > > > Dear Maintainers, > > This is a friendly ping about a usrmerge bug in one your packages. > > Please consider fixing it soon. > > Thanks, > Chris > Hi Chris, Apologies for the hold-up. Over the last several weeks, I have worked on a release in Salsa that addresses this bug, and others. Currently putting the final touches, after which I expect my co-maintainer to sign off on and upload the new source release in the coming days. Best regards, Daniel From thomas at osterried.de Sat Jul 13 07:14:49 2024 From: thomas at osterried.de (Thomas Osterried) Date: Sat, 13 Jul 2024 08:14:49 +0200 Subject: Bug#1076215: ax25-tools, dahdi-tools: install program with same name (sethdlc) In-Reply-To: References: Message-ID: Hello, sethdlc is for our packet-radio soundcard modems. tail of man page: AUTHOR sethdlc was written by Thomas Sailer, HB9JNX/AE4WA (t.sailer at alumni.ethz.ch). Inspired by setserial. Sethdlc 0.1 27 April 2008 SETHDLC(8) If both projects would rename their tools, we could discuss. I add Author hb9jnx to Cc for asking about his opinion. And ?no?, my next software project INITiative would not be named ?init? and not be placed to /sbin/ ? Lol ;)) vy 73, - Thomas dl9sau > Am 12.07.2024 um 22:52 schrieb David Ranch : > > ? > Hello Chris, > > Ax25-tool's sethdlc program predates this far later Asterisk dahdi-tools utility by decades so I would argue that Asterisk should change. That said, I don't know if there is much use for the sethdlc tool these days as it was used with legacy hardware. I've CCed DL9SAU here who supports the the primary version of these tools at https://linux-ax25.in-berlin.de/wiki/Main_Page to see what his thoughts might be here. > > --David > KI6ZHD > > > > On 07/12/2024 11:17 AM, Chris Hofstaedtler wrote: >> Package: ax25-tools,dahdi-tools >> Control: block 1075856 by -1 >> >> Hi, >> >> your packages ax25-tools and dahdi-tools both install a program >> names "sethdlc", although in different components of the PATH. >> >> As this is confusing and a possible source of bugs, policy bug >> #1075856 wants to outlaw this. >> >> Please find a solution for your packages. Ideas: >> 1) if one of the programs is an internal implementation detail of >> the package, install it into a private path in /usr/lib instead. >> 2) rename one of the programs >> 3) rename both of the programs >> >> Thanks, >> Chris > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thomas at osterried.de Sat Jul 13 07:14:49 2024 From: thomas at osterried.de (Thomas Osterried) Date: Sat, 13 Jul 2024 08:14:49 +0200 Subject: Bug#1076215: ax25-tools, dahdi-tools: install program with same name (sethdlc) In-Reply-To: References: Message-ID: Hello, sethdlc is for our packet-radio soundcard modems. tail of man page: AUTHOR sethdlc was written by Thomas Sailer, HB9JNX/AE4WA (t.sailer at alumni.ethz.ch). Inspired by setserial. Sethdlc 0.1 27 April 2008 SETHDLC(8) If both projects would rename their tools, we could discuss. I add Author hb9jnx to Cc for asking about his opinion. And ?no?, my next software project INITiative would not be named ?init? and not be placed to /sbin/ ? Lol ;)) vy 73, - Thomas dl9sau > Am 12.07.2024 um 22:52 schrieb David Ranch : > > ? > Hello Chris, > > Ax25-tool's sethdlc program predates this far later Asterisk dahdi-tools utility by decades so I would argue that Asterisk should change. That said, I don't know if there is much use for the sethdlc tool these days as it was used with legacy hardware. I've CCed DL9SAU here who supports the the primary version of these tools at https://linux-ax25.in-berlin.de/wiki/Main_Page to see what his thoughts might be here. > > --David > KI6ZHD > > > > On 07/12/2024 11:17 AM, Chris Hofstaedtler wrote: >> Package: ax25-tools,dahdi-tools >> Control: block 1075856 by -1 >> >> Hi, >> >> your packages ax25-tools and dahdi-tools both install a program >> names "sethdlc", although in different components of the PATH. >> >> As this is confusing and a possible source of bugs, policy bug >> #1075856 wants to outlaw this. >> >> Please find a solution for your packages. Ideas: >> 1) if one of the programs is an internal implementation detail of >> the package, install it into a private path in /usr/lib instead. >> 2) rename one of the programs >> 3) rename both of the programs >> >> Thanks, >> Chris > -------------- next part -------------- An HTML attachment was scrubbed... URL: From galjaardniels at gmail.com Sat Jul 13 12:13:33 2024 From: galjaardniels at gmail.com (Niels Galjaard) Date: Sat, 13 Jul 2024 13:13:33 +0200 Subject: minor privilege escalation in asterisk package Message-ID: Hi, I noticed some time ago that the asterisk when installed on recent Ubuntu versions Asterisk has a minor privilege escalation vulnerability in the systemd file. Since the command line arguments do not contain -G the user asterisk:asterisk can modify the /etc/asterisk/asterisk.conf with rungroup=disk. Subsequently you can crash the asterisk process and wait for "Restart=on-failure" to now trigger any script you want with "asterisk:disk". This gives more permissions than required. The user is disabled of course, but it is possible to abuse the CLI or AMI to get code execution in the asterisk user context. Using this in conjunction with the above bug, that becomes a much larger problem. As far as I can tell there is no functional change to adding the -G flag other than making the above privilege escalation impossible. We've run it with this command line flag in our service file for quite some time in the company I work for. The ExecStart line of the systemd file is created in asterisk/debian/patches/1006_systemd.patch. I think just appending "-G asterisk" to line 94 is sufficient. But I could be wrong as I don't know anything about the process of building a deb package. It also seems to be present in multiple versions of deb files. As far as I can tell all versions of the systemd file of debian and ubuntu are affected. I mistakenly believed this to be a problem in Asterisk itself, But their codebase seems to not include these settings. So this was already reported to the creators of asterisk as well via the security tab on github. Could you please message me back if either, you don't consider this a problem or you have published the fix. As this is part of a talk I want to give at a local security conference. I will presume this is sensitive and refrain from talking about it until I hear back from you or 6 months have passed since this message. Kind regards, Niels From cyber-sec-alert at mail.beehiiv.com Mon Jul 15 14:21:04 2024 From: cyber-sec-alert at mail.beehiiv.com (CyberSecAlert) Date: Mon, 15 Jul 2024 13:21:04 +0000 (UTC) Subject: CyberSecAlert: Facebook Ads Malware, Rite Aid Breach, Netgear Flaws, Exim Vulnerability, and Rapid POC Exploits Message-ID: Strategy Breakdowns: (https://strategybreakdowns.com/subscribe?_bhba=bf0b6b11-140c-4ec7-a518-a25cbfcf93b1) View image: (https://media.beehiiv.com/cdn-cgi/image/fit=scale-down,format=auto,onerror=redirect,quality=80/uploads/asset/file/40c093f0-5033-4878-bd92-0368c261a0bd/image.png?t=1721049544) Caption: The BRRR: (https://thebrrr.beehiiv.com/subscribe?_bhba=bf0b6b11-140c-4ec7-a518-a25cbfcf93b1) # CyberSecAlert: Facebook Ads Malware, Rite Aid Breach, Netgear Flaws, Exim Vulnerability, and Rapid POC Exploits ## Facebook Ads for Windows Themes Push Sys01 Info-Stealing Malware Malicious Facebook ads promoting Windows themes are pushing Sys01 info-stealing malware. This highlights the importance of being cautious with online ads and verifying the legitimacy of software sources before downloading. ## Rite Aid Confirms Data Breach After June Ransomware Attack Rite Aid has confirmed a data breach following a ransomware attack in June. This incident underscores the growing threat of ransomware and the critical need for organizations to strengthen their cybersecurity defenses. ## Netgear Warns Users to Patch Authentication Bypass, XSS Router Flaws Netgear has issued a warning to users to patch critical authentication bypass and cross-site scripting (XSS) vulnerabilities in their routers. Ensuring that devices are regularly updated with the latest security patches is essential to protect against these types of exploits. ## Critical Exim Bug Bypasses Security Filters on 1.5 Million Mail Servers A critical bug in Exim, affecting 1.5 million mail servers, allows attackers to bypass security filters. This vulnerability poses a significant risk to email servers worldwide, highlighting the need for immediate patching and vigilance in monitoring email server security. ## Hackers Use POC Exploits in Attacks 22 Minutes After Release Hackers are increasingly quick to leverage proof-of-concept (POC) exploits, often launching attacks within 22 minutes of their release. This rapid exploitation emphasizes the importance of timely vulnerability management and the need for proactive security measures. ??????????????????????????? AI Confidential: (https://ai-confidential.beehiiv.com/subscribe?_bhba=bf0b6b11-140c-4ec7-a518-a25cbfcf93b1) Stay informed and secure with CyberSecAlert. ??? You are reading a plain text version of this post. For the best experience, copy and paste this link in your browser to view the post online: https://cyber-sec-alert.beehiiv.com/p/cybersecalert-facebook-ads-malware-rite-aid-breach-netgear-flaws-exim-vulnerability-rapid-poc-exploi -------------- next part -------------- An HTML attachment was scrubbed... URL: From ftpmaster at ftp-master.debian.org Thu Jul 18 14:04:12 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Thu, 18 Jul 2024 13:04:12 +0000 Subject: biboumi_9.0-5.1_source.changes ACCEPTED into unstable Message-ID: Thank you for your contribution to Debian. Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Thu, 11 Jul 2024 14:29:02 +0200 Source: biboumi Architecture: source Version: 9.0-5.1 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: Chris Hofstaedtler Closes: 1073626 Changes: biboumi (9.0-5.1) unstable; urgency=medium . * Non-maintainer upload. * Install systemd units into /usr. (Closes: #1073626) Checksums-Sha1: 36fc5dd5e58ad32ea1075c70449cdcd7c078046d 2123 biboumi_9.0-5.1.dsc d9dfbf8fee29b3ef74f38d889fb8cc6c568c3b8b 11208 biboumi_9.0-5.1.debian.tar.xz ee1f929939df8f04ef9d62606fd2132f26abbe54 8507 biboumi_9.0-5.1_arm64.buildinfo Checksums-Sha256: 553cb630eb1e4674f46b8b57d2316e870798c27ffcca54e9c284c3136541ccf1 2123 biboumi_9.0-5.1.dsc 3cb9b9d7624758ec6f22c1712e8cd1cd97a024bf954910841a39324a8fb8150c 11208 biboumi_9.0-5.1.debian.tar.xz 5e44decb1f69fbc52c707a077fdca5356a6dee65aa73a11fcd64d7f9b9dbd44a 8507 biboumi_9.0-5.1_arm64.buildinfo Files: a50d1ad41a9f79235870ac66b0c646ed 2123 net optional biboumi_9.0-5.1.dsc 46b9e378fe6ff8678009f81adfa9eab1 11208 net optional biboumi_9.0-5.1.debian.tar.xz 57ec6164974efd4281fe42d0d0fbeda4 8507 net optional biboumi_9.0-5.1_arm64.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEfRrP+tnggGycTNOSXBPW25MFLgMFAmaP0VEACgkQXBPW25MF LgOmrg/7Bw6hdjMs6d6kUv+4ZuQDd7nSeiOm2HGGx/jAcY9fb7yj/L8Gq/R3Cq28 +uF9dSiE4NkOz4tzC8lHM2FZZD3OooYJCp3VHYMxN0GWT4zlAcobqnCuvB4roHFj tPGF082XWFj4hvPAQshF94+shPWdUGCedinWD3+NuckQqaQmtquVUcU5DPqy+tt4 LF3tr47Jl3TmRWjTas3e1ak/CEKFXEvPPCYbWxdtKQ2Uf+Uwu6AXz2mZf0BclQKI Hpx+6QaGBec0HS9WgL8cIgCLEQj8xUmZYHycdyqNX1lSlGbPW7RRPtLtwb8l96mP GIJDyjuggVz+hjO7woXylCrV40jTJYKsncq5b5CureVe57iUVsSdiy0JfL6soIWQ MW779BwPprtmiBroDdMAfBwdeNggw30YE6Bm5N+a9Z7NEGsDalhHe2nAgzpRyEfc 4RI+r7P0kZZvLQfGVbvK3ICXwo9LYgBV6lpg9+NTxOPjblk55G+WV5f/tm9zDJkr npSNJXdwhRnqMapom1jJPEzxzbCOMjQv8mw6NvQvZp2yHb1EZ52qqo5cLWW6ZQae kQ4nfHsklsFh9jflvtUrgby8MxS7lo3BiNQMCFYxCN/sRaRQy+ZZRQ7SYJTopTUT L6iWrneR0wkZSaoSbm9epv+rYYEGEaklSUb/GBwUkGydLSUYFp0= =s1dI -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: not available URL: From owner at bugs.debian.org Thu Jul 18 14:09:03 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Thu, 18 Jul 2024 13:09:03 +0000 Subject: Bug#1073626: marked as done (biboumi: move aliased files from / to /usr (DEP17)) References: <171870379696.3560576.16776467238399011795@subdivi.de> Message-ID: Your message dated Thu, 18 Jul 2024 13:04:12 +0000 with message-id and subject line Bug#1073626: fixed in biboumi 9.0-5.1 has caused the Debian Bug report #1073626, regarding biboumi: move aliased files from / to /usr (DEP17) 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 owner at bugs.debian.org immediately.) -- 1073626: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1073626 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Helmut Grohne Subject: biboumi: move aliased files from / to /usr (DEP17) Date: Tue, 18 Jun 2024 11:39:13 +0200 Size: 4422 URL: -------------- next part -------------- An embedded message was scrubbed... From: Debian FTP Masters Subject: Bug#1073626: fixed in biboumi 9.0-5.1 Date: Thu, 18 Jul 2024 13:04:12 +0000 Size: 6744 URL: From owner at bugs.debian.org Thu Jul 18 16:27:03 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Thu, 18 Jul 2024 15:27:03 +0000 Subject: Processed: (No Subject) References: Message-ID: Processing commands for control at bugs.debian.org: > forwarded 1075961 https://github.com/kamailio/kamailio/issues/3927 Bug #1075961 [src:kamailio] FTBFS: hep.c:985:41: error: implicit declaration of function ?inet_ntop? Set Bug forwarded-to-address to 'https://github.com/kamailio/kamailio/issues/3927'. > -- Stopping processing here. Please contact me if you need assistance. -- 1075961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075961 Debian Bug Tracking System Contact owner at bugs.debian.org with problems From ftpmaster at ftp-master.debian.org Thu Jul 18 17:04:32 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Thu, 18 Jul 2024 16:04:32 +0000 Subject: Processing of kamailio_5.8.2-3_source.changes Message-ID: kamailio_5.8.2-3_source.changes uploaded successfully to localhost along with the files: kamailio_5.8.2-3.dsc kamailio_5.8.2-3.debian.tar.xz kamailio_5.8.2-3_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) From ftpmaster at ftp-master.debian.org Thu Jul 18 17:19:56 2024 From: ftpmaster at ftp-master.debian.org (Debian FTP Masters) Date: Thu, 18 Jul 2024 16:19:56 +0000 Subject: kamailio_5.8.2-3_source.changes ACCEPTED into unstable Message-ID: Thank you for your contribution to Debian. Accepted: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Thu, 18 Jul 2024 17:46:16 +0200 Source: kamailio Architecture: source Version: 5.8.2-3 Distribution: unstable Urgency: medium Maintainer: Debian VoIP Team Changed-By: Victor Seva Closes: 1075961 Changes: kamailio (5.8.2-3) unstable; urgency=medium . * fix build on s390x and ppc64 (Closes: #1075961) Checksums-Sha1: fcda10981241f2404ea1c10a873e34d1b668b7be 5735 kamailio_5.8.2-3.dsc d085fd47a9eb6b534323c918f6f07ecd4f7b67fe 25792 kamailio_5.8.2-3.debian.tar.xz c94f273e4ad7223fe1c22b3fc40921598583b042 41664 kamailio_5.8.2-3_amd64.buildinfo Checksums-Sha256: d1abf515ca9939d3c3fcaf71a45f12547a25465687acf964e2dc1f60aa48e5bb 5735 kamailio_5.8.2-3.dsc 7ac26fe065642b6bf480ba92a762405a20430c40e5f978969b0b560743f6d8c4 25792 kamailio_5.8.2-3.debian.tar.xz b2b868b689600fe03624adbf310e682129171616523252e54cc866a0301690d9 41664 kamailio_5.8.2-3_amd64.buildinfo Files: f318e1a72abce78a43c18ba91da004f2 5735 net optional kamailio_5.8.2-3.dsc befdae68501ec4bb997d9852c29bfde4 25792 net optional kamailio_5.8.2-3.debian.tar.xz 77c7b4100b48b32e38930aa7f4172262 41664 net optional kamailio_5.8.2-3_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iIcEARYKAC8WIQQq6AO8RS0zF4SC1vh9e2XEKg7IsgUCZpk6IxEcdnNldmFAZGVi aWFuLm9yZwAKCRB9e2XEKg7Isj9yAP9lOQg4GLQc0XEV4VRqmevZGM5B6webEoV7 dLyQ14P+UgD+Nrr8obTiYrbc03646KARuQOwShX6FruqeZH5uXxBIQw= =1nHD -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: not available URL: From owner at bugs.debian.org Thu Jul 18 17:21:03 2024 From: owner at bugs.debian.org (Debian Bug Tracking System) Date: Thu, 18 Jul 2024 16:21:03 +0000 Subject: Bug#1075961: marked as done (FTBFS: hep.c:985:41: error: implicit declaration of function =?UTF-8?Q?=E2=80=98inet=5Fntop=E2=80=99?=) References: <172044135659.533643.9937707242114299848.reportbug@per> Message-ID: Your message dated Thu, 18 Jul 2024 16:19:56 +0000 with message-id and subject line Bug#1075961: fixed in kamailio 5.8.2-3 has caused the Debian Bug report #1075961, regarding FTBFS: hep.c:985:41: error: implicit declaration of function ?inet_ntop? 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 owner at bugs.debian.org immediately.) -- 1075961: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075961 Debian Bug Tracking System Contact owner at bugs.debian.org with problems -------------- next part -------------- An embedded message was scrubbed... From: Chris Hofstaedtler Subject: FTBFS: hep.c:985:41: error: implicit declaration of function ?inet_ntop? Date: Mon, 08 Jul 2024 14:22:36 +0200 Size: 4253 URL: -------------- next part -------------- An embedded message was scrubbed... From: Debian FTP Masters Subject: Bug#1075961: fixed in kamailio 5.8.2-3 Date: Thu, 18 Jul 2024 16:19:56 +0000 Size: 6113 URL: From Romello at thegamerscene.co Fri Jul 19 18:31:55 2024 From: Romello at thegamerscene.co (Romello From TheGamerScene Digest) Date: Fri, 19 Jul 2024 17:31:55 +0000 (UTC) Subject: =?UTF-8?B?8J+UpQ==?= Ultimate Gaming Update: Discover July's Most Anticipated Releases and Industry Secrets! =?UTF-8?B?8J+Org==?= Message-ID: ---------- View image: (https://media.beehiiv.com/cdn-cgi/image/fit=scale-down,format=auto,onerror=redirect,quality=80/uploads/asset/file/b68d7177-4447-4ec7-b410-33ec3d5f07bc/tgs.png) Caption: ? ? Epic Gaming Blitz: Discover July?s Hottest Releases & Industry Secrets! ? - July 19, 2024 Gaming Sphere ? ?** We Value Your Voice! **? "Your feedback is the extra life we need in TheGamerScene Daily Digest. We're not just listening; we're eager to evolve with your insights. Did you love a feature? Craving more of something specific? Got an idea that could revolutionize gaming news? Tell us all about it through our feedback form or hit reply to this email. Let's co-create a gaming newsletter that's not just read but lived!" Give Feedback Here! (https://thegamerscene.co/forms/de68a750-d8a4-4ac2-8c1d-e8946a7e6737) ----------### Free THCA Pre-rolls Shipped Right to Your Door View image: (https://media.beehiiv.com/cdn-cgi/image/fit=scale-down,format=auto,onerror=redirect,quality=80/uploads/asset/file/ce46fad2-63a4-4936-aece-1f90aadd425a/MW-Pre-Roll_THCA-Free_Sample_1166x602.png?t=1718911466) Follow image link: (https://try.moonwlkr.com/prerolls/?utm_campaign=AUFJCA5KQE&utm_source=beehiiv&utm_medium=preroll&_bhiiv=opp_620a194f-d589-49eb-bde1-70572c2b0b78_818cbe38) Caption: No med card required! [Moonwlkr](https://try.moonwlkr.com/prerolls/?utm_campaign=AUFJCA5KQE&utm_source=beehiiv&utm_medium=preroll&_bhiiv=opp_620a194f-d589-49eb-bde1-70572c2b0b78_818cbe38) is sending out THCA pre-rolls, shipped directly to your door! THCA is the chemical precursor to THC. When heated, it delivers all the same effects as traditional cannabis. See for yourself! The next 300 people can try them for no charge. [Claim Your Free Sample](https://try.moonwlkr.com/prerolls/?utm_campaign=AUFJCA5KQE&utm_source=beehiiv&utm_medium=preroll&_bhiiv=opp_620a194f-d589-49eb-bde1-70572c2b0b78_818cbe38) ---------- #### ??????????????????????????? ### ? Community Corner: Engage Your Readers We want to hear from you! Share your feedback, participate in our polls, and contribute your ideas to shape the future of our newsletter. Your voice is important to us! ??????????????????????????? ??????????????????????????? Sponsored iEthereum Let?s talk iEthereum! Discover the potential of iEthereum. By subscribing to our free weekly newsletter, you'll get: exclusive insights, analysis and opinions on iEthereum. We are the first ind... Subscribe: https://magic.beehiiv.com/v1/47e10174-4387-4312-a2dc-5917370e4e3c?email=pkg-voip-maintainers at lists.alioth.debian.org&recommendation_id=4884f5f9-78bf-4a1f-8156-392b25ad21fe ??????????????????????????? ### ? Spotlight on New Releases **Flintlock: The Siege of Dawn** ? Join humanity?s last stand in this dark-action RPG where gods and guns collide. Explore an open-world adventure filled with challenging combat and an intriguing storyline. **Dungeons of Hinterberg** ? Armed with a sword and tourist guide, explore an alpine village, solve puzzles, and slay monsters in this action-exploration RPG. **SCHiM** ? A unique game about jumping from shadow to shadow across beautiful environments. Traverse an abstract world to reunite a shadow with its person. **NCAA Football 2025** ? The beloved college football franchise returns with updated rosters, improved gameplay mechanics, and an immersive career mode. Experience the excitement of college football on PS5, Xbox Series X/S, and PC. **Bo: Path of the Teal Lotus** ? Flow with acrobatic grace in this hand-drawn platformer inspired by Japanese folklore. Use a legendary staff to navigate dreamlike landscapes and face massive boss battles. Available on PC, PlayStation, Xbox, and Switch. **Squirrel With A Gun** ? This quirky indie game has players control a squirrel armed with a gun, navigating a humorous and chaotic world filled with puzzles and challenges. Available on PlayStation 5 and Xbox Series X/S. **Highlight on Sequels/Continuations** ? Notable sequels this month include Metal Gear Solid Delta: Snake Eater and Frostpunk 2. ??????????????????????????? ### ? Console Corner: Platform-Specific News **PlayStation** * **Featured Game:** Flintlock: The Siege of Dawn offers a thrilling mix of combat and exploration on PS5. * **Horizon Forbidden West Update:** New DLC adds additional storylines and challenges. * **F1 Manager 2024:** Manage your own Formula 1 team with improved AI and dynamic gameplay. * **Gran Turismo 7 Update:** New cars and tracks have been added, enhancing the racing experience. * **The Last of Us Part III Rumors:** Speculations about the next installment in the series have surfaced, hinting at a potential release in 2025. **Xbox** * **Monthly Special:** Dungeons of Hinterberg, a captivating RPG, is now available on Xbox platforms. * **Halo Infinite Update:** New seasonal content including maps, weapons, and story missions. * **Avowed:** Latest updates on this upcoming first-person RPG from Obsidian Entertainment. * **Forza Horizon 5 Expansion:** A new expansion pack brings additional cars and challenges set in a vibrant new location. * **Starfield:** Bethesda?s much-anticipated space RPG is set to redefine open-world gaming with its expansive universe and detailed gameplay mechanics. **Nintendo** * **Tech Update:** Exciting new titles announced in the recent Nintendo Direct, including SCHiM and Flintlock: The Siege of Dawn. * **Metroid Prime 4:** Finally, news on the next Metroid game set to release in late 2024. * **Super Mario Party Jamboree:** New mini-games and modes added to the popular party game. * **The Legend of Zelda: Echoes of Wisdom:** New storyline details and gameplay mechanics revealed, adding depth to the beloved series. * **Splatoon 3 Splatfest:** Upcoming community event promises exciting new challenges and exclusive rewards. **PC** * **Featured Game:** Frostpunk 2 is the highly anticipated sequel to the acclaimed city-building survival game. * **Cyberpunk 2077: Phantom Liberty:** Major DLC adds new storylines and gameplay features. * **Steam Summer Sale:** Huge discounts on top PC games, including "Hades" and "The Witcher 3". * **Baldur's Gate 3:** Full release coming soon with enhanced features and new content after a successful early access period. * **Apex Legends:** New season introduces a fresh character, weapons, and map changes, promising to shake up the battle royale landscape. ??????????????????????????? ### ? Inside the Industry: Trends & Challenges **Workforce Trends** ? The gaming industry is increasingly embracing remote work and diverse hiring practices. Companies are finding innovative ways to collaborate across distances, fostering a more inclusive environment. **Studio Acquisitions** ? Major studios continue to acquire indie developers to expand creative portfolios and technical capabilities. **Tech Advancements** ? AI continues to revolutionize game development, making games more dynamic and immersive. **Cloud Gaming** ? With the rise of cloud gaming platforms, players can now access high-quality games on various devices without needing powerful hardware. This trend democratizes gaming access worldwide. **Sustainability in Gaming** ? The industry is pushing towards more sustainable practices, from eco-friendly packaging to reducing the carbon footprint of data centers. **Market Changes** ? The mobile gaming market continues to grow, outpacing traditional console and PC gaming in revenue generation. This shift influences how games are designed and monetized. ??????????????????????????? ### ? Hot Deals and Promos **Steam** Details: Summer sale with major discounts on popular titles like "Cyberpunk 2077" and "Hades." **PlayStation Store** Details: Exclusive discounts on PS Plus memberships and select games. **Special Offers** Details: Limited-time offers on gaming accessories and bundles. {[Playstation](https://store.playstation.com/en-us/category/f0940788-d28f-4894-9cb6-719392656bfb?gad_source=1&gclid=Cj0KCQjw6PGxBhCVARIsAIumnWbDEUj-GugxfyMvRzZ4K0p4W8WFIrUKtAdBxMtnN6sZRg8ezbNkLi0aAu30EALw_wcB&gclsrc=aw.ds)}. {[Xbox](https://www.xbox.com/en-US/promotions/sales/sales-and-specials)}. {[Nintendo](https://www.nintendo.com/us/store/sales-and-deals/)}. {[STEAM](https://store.steampowered.com/specials/)}. #### **Closing Thoughts:** Thank you for joining us for this edition of The Gamer Scene Newsletter. Stay tuned for more news, reviews, and exclusive offers. Engage with us on social media, visit our website for daily updates, and don't forget to subscribe for your monthly dose of gaming excitement! ### SHARE YOU PASSION (https://thegamerscene.co/forms/cb7506f6-d5e1-4ecd-b187-fa042aaafb5c) ----------??????????????????????????? Sponsored iEthereum Let?s talk iEthereum! Discover the potential of iEthereum. By subscribing to our free weekly newsletter, you'll get: exclusive insights, analysis and opinions on iEthereum. We are the first ind... Subscribe: https://magic.beehiiv.com/v1/47e10174-4387-4312-a2dc-5917370e4e3c?email=pkg-voip-maintainers at lists.alioth.debian.org&recommendation_id=4884f5f9-78bf-4a1f-8156-392b25ad21fe ??????????????????????????? ?Looking to get a monthly budget going? Well we have a treat for you he is a link to a free monthly calendar to use in EXCEL or GOOGLE SHEETS!? ? Mello @ TGS Take Me To The Free Stuff (https://mellocrafter.gumroad.com/l/rqsqh) # ??**Today's Gaming Poll: WE NEED TO KNOW @ TGS!** # ? Today's Gaming Trivia Challenge: Test Your Knowledge! ??????????????????????????? TheFutureParty Get the latest news and trends on business, entertainment, and culture - so you always stay one step ahead of the rest. Subscribe: https://magic.beehiiv.com/v1/ce1adc56-21c4-4202-a79a-b750d42ad22b?email=pkg-voip-maintainers at lists.alioth.debian.org&recommendation_id=7f0262ac-8bbd-4601-bf35-7c0481dc3074 ??????????????????????????? ??????????????????????????? Poker Now News & Notes News & Notes from the Team at Poker Now Subscribe: https://magic.beehiiv.com/v1/598b5ec7-f792-401c-9655-69abbb0bb5ab?email=pkg-voip-maintainers at lists.alioth.debian.org&recommendation_id=f101cb7e-c55e-4673-8922-39b9e39e0640 ??????????????????????????? ??? You are reading a plain text version of this post. For the best experience, copy and paste this link in your browser to view the post online: https://thegamerscene.co/p/unveil-hottest-new-games-trends-dont-miss -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at release.debian.org Sat Jul 20 05:39:16 2024 From: noreply at release.debian.org (Debian testing watch) Date: Sat, 20 Jul 2024 04:39:16 +0000 Subject: sngrep 1.8.2-1 MIGRATED to testing Message-ID: FYI: The status of the sngrep source package in Debian's testing distribution has changed. Previous version: 1.8.1-1 Current version: 1.8.2-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive later changes on the next day. See https://release.debian.org/testing-watch/ for more information.