Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

Some questions from upstream, with my commentary added... How busy is this sustem? Is it just a simple client or also a server? If server, how busy? From the stack trace, the server side is trying to decode a NTS cookie. Is this box setup as a NTS server? That needs a certificate and key so

Bug#1037576: marked as done (android-platform-tools: ftbfs with GCC-13)

Your message dated Sun, 23 Jul 2023 05:05:17 + with message-id and subject line Bug#1037576: fixed in android-platform-tools 33.0.3-2 has caused the Debian Bug report #1037576, regarding android-platform-tools: ftbfs with GCC-13 to be marked as done. This means that you claim that the

Bug#1041592: marked as done (bugs.debian.org: unattended-upgrades removed bind9 and other packages)

Your message dated Sat, 22 Jul 2023 21:45:41 -0700 with message-id <20230723044541.4w673zz63nvmh...@qor.donarmstrong.com> and subject line Re: Bug#1041592: bugs.debian.org: unattended-upgrades removed bind9 and other packages has caused the Debian Bug report #1041592, regarding bugs.debian.org:

Bug#1040850: marked as done (python-coverage autopkg test fail with setuptools 68)

Your message dated Sun, 23 Jul 2023 04:49:41 + with message-id and subject line Bug#1040850: fixed in python-coverage 7.2.7+dfsg1-1 has caused the Debian Bug report #1040850, regarding python-coverage autopkg test fail with setuptools 68 to be marked as done. This means that you claim that

Processed: libxml-light-ocaml-dev: undeclared file conflict with libxml-light-ocaml (<= 2.4-1+b4) on /usr/lib/ocaml/xml-light/META

Processing control commands: > affects -1 + libxml-light-ocaml Bug #1041751 [libxml-light-ocaml-dev] libxml-light-ocaml-dev: undeclared file conflict with libxml-light-ocaml (<= 2.4-1+b4) on /usr/lib/ocaml/xml-light/META Added indication that 1041751 affects libxml-light-ocaml -- 1041751:

Bug#1041751: libxml-light-ocaml-dev: undeclared file conflict with libxml-light-ocaml (<= 2.4-1+b4) on /usr/lib/ocaml/xml-light/META

Package: libxml-light-ocaml-dev Version: 2.5-1 Severity: serious Control: affects -1 + libxml-light-ocaml libxml-light-ocaml-dev introduces an undeclared file conflict with libxml-light-ocaml up to version 2.4-1+b4 on the file /lib/ocaml/xml-light/META. This may result in an unpack error at

Bug#1037575: marked as done (android-platform-external-boringssl: ftbfs with GCC-13)

Your message dated Sun, 23 Jul 2023 04:19:05 + with message-id and subject line Bug#1037575: fixed in android-platform-external-boringssl 13.0.0+r24-3 has caused the Debian Bug report #1037575, regarding android-platform-external-boringssl: ftbfs with GCC-13 to be marked as done. This means

Processed: tagging 1037568

Processing commands for cont...@bugs.debian.org: > tags 1037568 + experimental Bug #1037568 [src:actor-framework] actor-framework: ftbfs with GCC-13 Added tag(s) experimental. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037568:

Processed: found 1037568 in 0.18.6-1

Processing commands for cont...@bugs.debian.org: > found 1037568 0.18.6-1 Bug #1037568 [src:actor-framework] actor-framework: ftbfs with GCC-13 Marked as found in versions actor-framework/0.18.6-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1037568:

Bug#1038603: libisl23 0.25-1: amd64/i386 baseline violation: uses BMI instructions)

Package: libisl23 Followup-For: Bug #1038603 X-Debbugs-Cc: Debian GCC Maintainers , debian-rele...@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 While the issue has been resolved in isl 0.26-3, which was uploaded to unstable on 2023-06-19, nothing has been done for the stable

Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386

On 22 July 2023 at 21:45, Paul Gevers wrote: | Source: lme4 | Version: 1.1-31-1 | Severity: serious | Control: close -1 1.1-34-1 | X-Debbugs-CC: debia...@lists.debian.org | Tags: sid trixie | User: release.debian@packages.debian.org | Usertags: out-of-sync | | Dear maintainer(s), | | The

Bug#1037827: marked as done (qscintilla2: ftbfs with GCC-13)

Your message dated Sat, 22 Jul 2023 20:56:25 + with message-id and subject line Bug#1037827: fixed in qscintilla2 2.14.1+dfsg-1 has caused the Debian Bug report #1037827, regarding qscintilla2: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt

Processed: Bug#1041341 marked as pending in html5lib

Processing control commands: > tag -1 pending Bug #1041341 [src:html5lib] html5lib: FTBFS on unstable Added tag(s) pending. -- 1041341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041341 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1041341: marked as pending in html5lib

Control: tag -1 pending Hello, Bug #1041341 in html5lib reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Re: Bug#1038422: ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000]

Processing commands for cont...@bugs.debian.org: > forwarded 1038422 https://gitlab.com/NTPsec/ntpsec/-/issues/794 Bug #1038422 [ntpsec] ntpsec: ntpd segmentation fault in libcrypto.so[7f6d3ecc5000+278000] Set Bug forwarded-to-address to 'https://gitlab.com/NTPsec/ntpsec/-/issues/794'. > End of

Bug#1041738: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386

Source: lme4 Version: 1.1-31-1 Severity: serious Control: close -1 1.1-34-1 X-Debbugs-CC: debia...@lists.debian.org Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing

Processed: src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386

Processing control commands: > close -1 1.1-34-1 Bug #1041738 [src:lme4] src:lme4: fails to migrate to testing for too long: causes timeout in autopkgtests on i386 Marked as fixed in versions lme4/1.1-34-1. Bug #1041738 [src:lme4] src:lme4: fails to migrate to testing for too long: causes

Bug#1041388: marked as done (libclang-rt-17-dev: ships /usr/lib/llvm-17/lib/clang/17/lib/wasi/libclang_rt.builtins-wasm*.a, already in libclang-rt-17-dev-wasm*)

Your message dated Sat, 22 Jul 2023 19:43:31 + with message-id and subject line Bug#1041388: fixed in llvm-toolchain-snapshot 1:17~++20230721092305+2ce662c5d596-1~exp1 has caused the Debian Bug report #1041388, regarding libclang-rt-17-dev: ships

Bug#932501: [pkg-apparmor] BTS housekeeping and severity adjustments

Hello, Am Freitag, 21. Juli 2023, 15:05:52 CEST schrieb Stefano Rivera: > > severity 932501 serious > > I'm wondering if this bug should really be serious. Squid's apparmor > config is shipped disabled, so one has to manually enable it to > trigger this bug. > > I would have gone for

Processed: reopen #1037603 closed by error

Processing commands for cont...@bugs.debian.org: > reopen 1037603 Bug #1037603 {Done: Sebastien Jodogne } [src:civetweb] civetweb: ftbfs with GCC-13 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add them. Bug

Bug#999977: qxw: depends on obsolete pcre3 library

On Sat, 22 Jul 2023 16:14:06 +0200, Bastian Germann wrote: > I suggest to remove the package. I do not think upstream will deal with > this. qxw’s usage of pcre seems simple enough, I’ll try to come up with a patch. Regards, Stephen pgpJ5rnX7z89K.pgp Description: OpenPGP digital signature

Processed: bug 1041722 is forwarded to https://github.com/ValveSoftware/steam-for-linux/issues/9805

Processing commands for cont...@bugs.debian.org: > forwarded 1041722 https://github.com/ValveSoftware/steam-for-linux/issues/9805 Bug #1041722 [steam-installer] steam is incompatible with libgudev 238-2 Set Bug forwarded-to-address to

Bug#1041722: steam is incompatible with libgudev 238-2

forwarded -1 https://github.com/ValveSoftware/steam-for-linux/issues/9805 thanks Am Samstag, dem 22.07.2023 um 18:46 +0100 schrieb Simon McVittie: > On Sat, 22 Jul 2023 at 17:43:56 +0200, Felix Zielcke wrote: > > Steam crashes on startup with libgudev 238-2 currently in unstable. > > Debian has

Processed: Re: Bug#1041511: ntfs-3g: Undocumented dependency on libbrotli-dev

Processing control commands: > tags -1 +unreproducible +wontfix Bug #1041511 [src:ntfs-3g] ntfs-3g: Undocumented dependency on libbrotli-dev Added tag(s) unreproducible. Bug #1041511 [src:ntfs-3g] ntfs-3g: Undocumented dependency on libbrotli-dev Added tag(s) wontfix. > severity -1 normal Bug

Bug#1041511: ntfs-3g: Undocumented dependency on libbrotli-dev

Control: tags -1 +unreproducible +wontfix Control: severity -1 normal On Thu, Jul 20, 2023 at 3:57 AM Theodoric Stier wrote: > Source: ntfs-3g > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) [...] > This package build fails

Bug#1037827: marked as pending in qscintilla2

Control: tag -1 pending Hello, Bug #1037827 in qscintilla2 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Processed: Bug#1037827 marked as pending in qscintilla2

Processing control commands: > tag -1 pending Bug #1037827 [src:qscintilla2] qscintilla2: ftbfs with GCC-13 Added tag(s) pending. -- 1037827: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: r-cran-clock: autopkgtest failure on 32bit

Processing control commands: > severity -1 serious Bug #1028111 [src:r-cran-clock] r-cran-clock: autopkgtest failure on 32bit Severity set to 'serious' from 'important' -- 1028111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028111 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1037623: marked as done (dolfinx-mpc: ftbfs with GCC-13)

Your message dated Sat, 22 Jul 2023 17:49:01 + with message-id and subject line Bug#1037623: fixed in dolfinx-mpc 0.6.1-3 has caused the Debian Bug report #1037623, regarding dolfinx-mpc: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1041722: steam is incompatible with libgudev 238-2

On Sat, 22 Jul 2023 at 17:43:56 +0200, Felix Zielcke wrote: > Steam crashes on startup with libgudev 238-2 currently in unstable. Debian has no control over what's in the proprietary Steam client, so please report this sort of thing to .

Bug#1040830: marked as done (iperf3: CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3 memory allocation hazard and crash)

Your message dated Sat, 22 Jul 2023 17:17:38 + with message-id and subject line Bug#1040830: fixed in iperf3 3.9-1+deb11u1 has caused the Debian Bug report #1040830, regarding iperf3: CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3 memory allocation hazard and crash to be marked as done.

Bug#1040830: marked as done (iperf3: CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3 memory allocation hazard and crash)

Your message dated Sat, 22 Jul 2023 17:17:08 + with message-id and subject line Bug#1040830: fixed in iperf3 3.12-1+deb12u1 has caused the Debian Bug report #1040830, regarding iperf3: CVE-2023-38403: ESNET-SECADV-2023-0001: iperf3 memory allocation hazard and crash to be marked as done.

Bug#1040179: marked as done (rmlint-gui: invalid Python version number breaks other packages)

Your message dated Sat, 22 Jul 2023 16:02:11 + with message-id and subject line Bug#1040179: fixed in rmlint 2.9.0-2.3+deb12u1 has caused the Debian Bug report #1040179, regarding rmlint-gui: invalid Python version number breaks other packages to be marked as done. This means that you claim

Bug#1041722: steam is incompatible with libgudev 238-2

Package: steam-installer Version: 1:1.0.0.78~ds-2 Severity: grave Steam crashes on startup with libgudev 238-2 currently in unstable. libgudev 237-2 from testing works fine with Steam. Console only shows this for the crash: Assertion 'device' failed at

Bug#1041674: with attachment

with attachment --- a/Makefile.am 2023-07-21 22:53:36.152522891 + +++ b/Makefile.am 2023-07-22 00:12:21.796916350 + @@ -58,6 +58,8 @@ libfakeroot.lo:libfakeroot.c wrapdef.h wrapstruct.h wraptmpf.h +libfakeroot_time64.c:wrapped.h + fakerootconfig.h: ./config.status CONFIG_FILES=

Bug#999977: qxw: depends on obsolete pcre3 library

I suggest to remove the package. I do not think upstream will deal with this.

Processed: Re: Broken due to missed udev dependencies

Processing commands for cont...@bugs.debian.org: > severity 1041703 important Bug #1041703 [libgudev-1.0-0] Broken due to missed udev dependencies Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 1041703:

Bug#1041703: Broken due to missed udev dependencies

severity 1041703 important thanks Martin Steigerwald - 22.07.23, 15:41:41 CEST: > severity 1041703 grave > thanks > > Justification: Renders X unusable, renders fwupdmgr unusable On the other hand Sid should have libudev1 254~rc2-3. Even testing should have 253.5-1 already. Ah and I see Klaus

Bug#1041703: Broken due to missed udev dependencies

Working package for AMD64: https://ftp.debian.org/debian/pool/main/libg/libgudev/libgudev-1.0-0_237-2_amd64.deb -- Martin

Processed: Re: Broken due to missed udev dependencies

Processing commands for cont...@bugs.debian.org: > severity 1041703 grave Bug #1041703 [libgudev-1.0-0] Broken due to missed udev dependencies Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1041703:

Processed: dolfin: libdolfin needs ABI bump

Processing control commands: > affects -1 python3-mshr Bug #1041705 [src:dolfin] dolfin: libdolfin needs ABI bump Added indication that 1041705 affects python3-mshr -- 1041705: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041705 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1041705: dolfin: libdolfin needs ABI bump

Source: dolfin Version: 2019.2.0~legacy20230609.8b85e9d.ar-2 Severity: serious Justification: Policy 8.6.2 Control: affects -1 python3-mshr The accumulation of git changes and gcc-13 fixes has apparently introduced an ABI inconsistency in libdolfin.so, such that mshr can no longer be imported in

Bug#1041674: simple dependancy between wrapped.h and libfakeroot_time64.c fixes the build issue

as per the attached patch, a simple dependancy on wrapped.h against libfakeroot_time64.c fixes the issue.

Bug#1041683: marked as done (undeclared file conflict between fabio-viewer and python3-fabio)

Your message dated Sat, 22 Jul 2023 12:27:30 + with message-id and subject line Bug#1041683: fixed in python-fabio 2023.6.0-3 has caused the Debian Bug report #1041683, regarding undeclared file conflict between fabio-viewer and python3-fabio to be marked as done. This means that you claim

Bug#1039635: marked as done (r-bioc-biomart: autopkgtest failure with r-base (4.3.1-1))

Your message dated Sat, 22 Jul 2023 12:28:00 + with message-id and subject line Bug#1039635: fixed in r-bioc-biomart 2.56.1+dfsg-1 has caused the Debian Bug report #1039635, regarding r-bioc-biomart: autopkgtest failure with r-base (4.3.1-1) to be marked as done. This means that you claim

Bug#1039501: marked as done (r-bioc-biomart: autopkgtest regression: Failure ('test_ensembl_ssl_settings.R:71'))

Your message dated Sat, 22 Jul 2023 12:28:00 + with message-id and subject line Bug#1039501: fixed in r-bioc-biomart 2.56.1+dfsg-1 has caused the Debian Bug report #1039501, regarding r-bioc-biomart: autopkgtest regression: Failure ('test_ensembl_ssl_settings.R:71') to be marked as done.

Bug#1037851: marked as done (rumur: ftbfs with GCC-13)

Your message dated Sat, 22 Jul 2023 12:28:24 + with message-id and subject line Bug#1037851: fixed in rumur 2023.05.21-1 has caused the Debian Bug report #1037851, regarding rumur: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1034852: marked as done (r-bioc-annotationhub: autopkgtest regression: download failed)

Your message dated Sat, 22 Jul 2023 12:27:51 + with message-id and subject line Bug#1034852: fixed in r-bioc-annotationhub 3.8.0+dfsg-1 has caused the Debian Bug report #1034852, regarding r-bioc-annotationhub: autopkgtest regression: download failed to be marked as done. This means that you

Bug#1041499: meson: glib2.0 FTBFS on mips64el: "native build" but then "Can not run test applications in this cross environment"

On Wed, 19 Jul 2023 at 20:12:08 +0100, Simon McVittie wrote: > On mips64el, Meson seems confused about whether this is a native or > cross build. At first, it correctly reports that this is a native build: ... > but then later, cc.run() fails: > > > ../../../meson.build:1127:14: ERROR: Can not

Bug#1039714: fixed in gobject-introspection 1.76.1-3

Hello Simon, thanks for your support! Cheers, Thomas

Processed: affects 1041633

Processing commands for cont...@bugs.debian.org: > affects 1041633 src:qgis Bug #1041633 [src:cmake] cmake: FindPython.cmake returns /usr/local/lib/python3.11/dist-packages for Python_SITEARCH Added indication that 1041633 affects src:qgis > thanks Stopping processing here. Please contact me if

Bug#1037851: Your mail

On Sat, 22 Jul 2023 11:36:10 +1000 Matthew Fernandez wrote: Btw, why does this bug not appear when searching for bugs against the package? https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=rumur Because it is reported for the source package (replace ?pkg=rumur with ?src=rumur).

Processed: src:libchemistry-opensmiles-perl: fails to migrate to testing for too long: causes autopkgtest regression

Processing control commands: > close -1 0.8.6-1 Bug #1041691 [src:libchemistry-opensmiles-perl] src:libchemistry-opensmiles-perl: fails to migrate to testing for too long: causes autopkgtest regression Marked as fixed in versions libchemistry-opensmiles-perl/0.8.6-1. Bug #1041691

Bug#1041691: src:libchemistry-opensmiles-perl: fails to migrate to testing for too long: causes autopkgtest regression

Source: libchemistry-opensmiles-perl Version: 0.8.5-1 Severity: serious Control: close -1 0.8.6-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for

Bug#1037593: binutils-avr: ftbfs with GCC-13

Upstream has fixed this via https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=5b429b870767e2107bcc7d5d849e04d6901b5912 Thanks for uploading the fix. Unfortunately, it looks like the buildds are still choking on it: https://buildd.debian.org/status/package.php?p=binutils-avr #

Processed: src:golang-github-grpc-ecosystem-grpc-gateway: fails to migrate to testing for too long: FTBFS & autopkgtest regression

Processing control commands: > close -1 1.16.0-2 Bug #1041688 [src:golang-github-grpc-ecosystem-grpc-gateway] src:golang-github-grpc-ecosystem-grpc-gateway: fails to migrate to testing for too long: FTBFS & autopkgtest regression Marked as fixed in versions

Bug#1041688: src:golang-github-grpc-ecosystem-grpc-gateway: fails to migrate to testing for too long: FTBFS & autopkgtest regression

Source: golang-github-grpc-ecosystem-grpc-gateway Version: 1.6.4-2 Severity: serious Control: close -1 1.16.0-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1038870 Dear maintainer(s), The Release Team considers packages that are

Processed: src:accountsservice: fails to migrate to testing for too long: FTBFS

Processing control commands: > close -1 23.13.9-2 Bug #1041687 [src:accountsservice] src:accountsservice: fails to migrate to testing for too long: FTBFS The source 'accountsservice' and version '23.13.9-2' do not appear to match any binary packages Marked as fixed in versions

Bug#1041687: src:accountsservice: fails to migrate to testing for too long: FTBFS

Source: accountsservice Version: 22.08.8-6 Severity: serious Control: close -1 23.13.9-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1038865 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing