Bug#1017148: marked as done (soci: FTBFS: catch.hpp:6490:33: error: size of array ‘altStackMem’ is not an integral constant-expression)

Your message dated Sun, 25 Sep 2022 05:48:33 + with message-id and subject line Bug#1017148: fixed in soci 4.0.3-1 has caused the Debian Bug report #1017148, regarding soci: FTBFS: catch.hpp:6490:33: error: size of array ‘altStackMem’ is not an integral constant-expression to be marked as

Bug#1020679: notfound 1020679 in 0.4.7+ds-3, closing 1020679

notfound 1020679 0.4.7+ds-3 close 1020679 thanks

Processed: notfound 1020679 in 0.4.7+ds-3, closing 1020679

Processing commands for cont...@bugs.debian.org: > notfound 1020679 0.4.7+ds-3 Bug #1020679 [golang-github-opensuse-umoci-dev] umoci makes singularity-container FTBFS No longer marked as found in versions umoci/0.4.7+ds-3. > close 1020679 Bug #1020679 [golang-github-opensuse-umoci-dev] umoci

Processed: Re: singularity-container: FTBFS: make[2]: *** [Makefile:181: singularity] Error 2

Processing control commands: > notfound -1 umoci/0.4.7+ds-3 Bug #1020208 [singularity-container] umoci makes singularity-container FTBFS No longer marked as found in versions umoci/0.4.7+ds-3. -- 1020208: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020208 Debian Bug Tracking System

Bug#1020208: singularity-container: FTBFS: make[2]: *** [Makefile:181: singularity] Error 2

Control: notfound -1 umoci/0.4.7+ds-3 On Sun, Sep 25, 2022 at 11:34 AM Nilesh Patra wrote: > > Control: found -1 singularity-container/3.10.2+ds2-3 > Control: found -1 umoci/0.4.7+ds-3 > Control: retitle -1 umoci makes singularity-container FTBFS > > I tried with golang-github-opensuse-umoci-dev

Processed: Reassign

Processing commands for cont...@bugs.debian.org: > clone 1020208 -1 Bug #1020208 [singularity-container] umoci makes singularity-container FTBFS Bug 1020208 cloned as bug 1020679 > reassign -1 golang-github-opensuse-umoci-dev 0.4.7+ds-3 Bug #1020679 [singularity-container] umoci makes

Bug#1020677: httraqt: Segfault upon mirroring initiation

Package: httraqt Version: 1.4.9-5 Severity: grave Justification: renders package unusable As written: I cannot use the package to complete any mirroring operation. The program crashes a seccond after you start the mirroring, before any of the download statistics are displayed (though the

Processed: Reassign

Processing commands for cont...@bugs.debian.org: > reassign 1020208 singularity-container umoci Bug #1020208 [src:singularity-container] umoci makes singularity-container FTBFS Bug reassigned from package 'src:singularity-container' to 'singularity-container'. No longer marked as found in

Bug#1020208: singularity-container: FTBFS: make[2]: *** [Makefile:181: singularity] Error 2

Control: found -1 singularity-container/3.10.2+ds2-3 Control: found -1 umoci/0.4.7+ds-3 Control: retitle -1 umoci makes singularity-container FTBFS I tried with golang-github-opensuse-umoci-dev version 0.4.7+ds-2 in my schroot, and it builds fine there. On upgrading and building, it chokes. This

Processed: Re: Bug#1017979: mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc.

Processing commands for cont...@bugs.debian.org: > affects 1017979 - src:mozjs102 Bug #1017979 [src:mozjs91] mozjs91: FTBFS on armel with gcc 12: multiple definition of `__sync_fetch_and_add_4' etc. Removed indication that 1017979 affects src:mozjs102 > End of message, stopping processing here.

Processed: Re: singularity-container: FTBFS: make[2]: *** [Makefile:181: singularity] Error 2

Processing control commands: > found -1 singularity-container/3.10.2+ds2-3 Bug #1020208 [src:singularity-container] singularity-container: FTBFS: make[2]: *** [Makefile:181: singularity] Error 2 Ignoring request to alter found versions of bug #1020208 to the same values previously set > found

Bug#1020652: [Pkg-openssl-devel] Bug#1020652: openssl: tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254:

Also, where’s the NEWS entry apt-listchanges would have mailed me to document this change in behaviour? (Might as well place the documentation I requested in the previous eMail there, so others will also find it.) bye, //mirabilos -- 22:20⎜ The crazy that persists in his craziness becomes a

Bug#1020652: [Pkg-openssl-devel] Bug#1020652: openssl: tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254:

Kurt Roeckx dixit: >On Sat, Sep 24, 2022 at 10:34:19PM +0200, Thorsten Glaser wrote: >> $ openssl s_client -CApath /etc/ssl/certs -connect www.mirbsd.org:443 >> -legacy_renegotiation -tls1 > >TLS 1.0 is not supported by default because it's insecure. You need >to change the security level to 0,

Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system

I can confirm updating the microcode by installing the intel-microcode package and rebooting does indeed mitigate this issue. An LXC container that was previously bricked due to update now starts and seems to behave fully normally. [0.00] microcode: microcode updated early to revision

Bug#1020652: marked as done (openssl: tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254:)

Your message dated Sun, 25 Sep 2022 02:08:31 +0200 with message-id and subject line Re: [Pkg-openssl-devel] Bug#1020652: openssl: tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254: has caused the Debian Bug report #1020652, regarding openssl:

Bug#1020013: marked as done (wine: FTBFS: unsatisfiable build-dependency: unicode-data (< 15) but 15.0.0-1 is to be installed)

Your message dated Sat, 24 Sep 2022 23:56:02 + with message-id and subject line Bug#1020013: fixed in wine 7.0~repack-8 has caused the Debian Bug report #1020013, regarding wine: FTBFS: unsatisfiable build-dependency: unicode-data (< 15) but 15.0.0-1 is to be installed to be marked as done.

Bug#1017106: marked as done (vkd3d: build depends on strictly versioned arch:all binary of itself)

Your message dated Sat, 24 Sep 2022 23:55:05 + with message-id and subject line Bug#1017106: fixed in vkd3d 1.2-15 has caused the Debian Bug report #1017106, regarding vkd3d: build depends on strictly versioned arch:all binary of itself to be marked as done. This means that you claim that

Processed: bug 1017313 is forwarded to https://www.postfix.org/announcements/postfix-3.6.5.html

Processing commands for cont...@bugs.debian.org: > forwarded 1017313 https://www.postfix.org/announcements/postfix-3.6.5.html Bug #1017313 [src:postfix] postfix: FTBFS: unistd.h:363:13: error: conflicting types for ‘closefrom’; have ‘void(int)’ Set Bug forwarded-to-address to

Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system

Hello, sorry for delayed response, I've managed to collect and analyze a few coredump files with valid symbols (I installed libc6-dbg and dpkg-dev, and pointed gdb at Debian's debuginfod server, also used apt-get source to get the sources for libc6). It seems there are at least 3-4 distinct

Bug#1020642: webkit2gtk: FTBFS on mipsel: virtual memory exhausted

On Sat, Sep 24, 2022 at 06:39:25PM +0100, Simon McVittie wrote: > webkit2gtk repeatedly failed to compile on the mipsel buildds: > > : > > FAILED: > >

Bug#1014868: python3-pyaudio: needs patch for python 3.10

Thanks Thomas. Indeed, upstream PyAudio 0.2.12 fixes the issue with Python 3.10. I have also updated the packaging, and I am working with Felipe Sateler to get it uploaded. Thanks, Hubert

Bug#1020652: openssl: tls_process_key_exchange:internal error:../ssl/statem/statem_clnt.c:2254:

Package: openssl Version: 3.0.5-4 Severity: serious Justification: does not work any more X-Debbugs-Cc: t...@mirbsd.de $ openssl s_client -CApath /etc/ssl/certs -connect www.mirbsd.org:443 -legacy_renegotiation -tls1 CONNECTED(0003) depth=2 C = US, O = Internet Security Research Group, CN =

Bug#1013876: Please close if fixed to migrate to testing

Hi! On Fri, 2022-09-23 at 13:27:31 +, Amr Ibrahim wrote: > On Mon, 27 Jun 2022 07:21:33 +0200 Bruno Kleinert > wrote: > > thanks for the report. Something else in 1.8.0 is bugging me that may > > be related to upstream's jQuery removal. I'm expecting upstream may > > release 1.8.1 soonish.

Bug#1020125: marked as done (apscheduler: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 --system=custom "--test-args={interpreter} setup.py test" returned exit co

Your message dated Sat, 24 Sep 2022 18:34:52 + with message-id and subject line Bug#1020125: fixed in apscheduler 3.9.1-2 has caused the Debian Bug report #1020125, regarding apscheduler: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.10 --system=custom

Processed: Python 3.10 incompatibility should be severe

Processing commands for cont...@bugs.debian.org: > severity 1014868 grave Bug #1014868 [python3-pyaudio] python3-pyaudio: needs patch for python 3.10 Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1014868:

Bug#1020642: webkit2gtk: FTBFS on mipsel: virtual memory exhausted

Source: webkit2gtk Version: 2.38.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-m...@lists.debian.org User: debian-m...@lists.debian.org Usertags: mipsel webkit2gtk repeatedly failed to compile on the mipsel

Bug#1017618: marked as done (nautilus-share: Incompatible with Nautilus 43)

Your message dated Sat, 24 Sep 2022 17:13:32 + with message-id and subject line Bug#1017618: fixed in nautilus-share 0.7.5-0.1 has caused the Debian Bug report #1017618, regarding nautilus-share: Incompatible with Nautilus 43 to be marked as done. This means that you claim that the problem

Bug#1020031: marked as done (khmer: FTBFS: ld: cannot find build/temp.linux-x86_64-3.10/src/khmer/_cpy_khmer.o: No such file or directory)

Your message dated Sat, 24 Sep 2022 17:09:32 + with message-id and subject line Bug#1020031: fixed in khmer 3.0.0~a3+dfsg-4 has caused the Debian Bug report #1020031, regarding khmer: FTBFS: ld: cannot find build/temp.linux-x86_64-3.10/src/khmer/_cpy_khmer.o: No such file or directory to be

Bug#1020447: marked as done (src:aircrack-ng: fails to migrate to testing for too long: not build on s390x)

Your message dated Sat, 24 Sep 2022 17:04:55 + with message-id and subject line Bug#1020447: fixed in aircrack-ng 1:1.7-5 has caused the Debian Bug report #1020447, regarding src:aircrack-ng: fails to migrate to testing for too long: not build on s390x to be marked as done. This means that

Bug#1019579: marked as done (Missing pre-compiled file in dependency packages lead to 'trying to overwrite file' errors)

Your message dated Sat, 24 Sep 2022 17:07:19 + with message-id and subject line Bug#1019579: fixed in dh-raku 0.13 has caused the Debian Bug report #1019579, regarding Missing pre-compiled file in dependency packages lead to 'trying to overwrite file' errors to be marked as done. This means

Bug#983982: marked as done (bazel-bootstrap: ftbfs with GCC-11)

Your message dated Sat, 24 Sep 2022 17:00:13 + with message-id and subject line Bug#983982: fixed in bazel-bootstrap 3.5.1+ds-5~exp2 has caused the Debian Bug report #983982, regarding bazel-bootstrap: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has

Bug#1019891: marked as done (mycli: Always crashes at runtime because the module 'sqlglot' is missing)

Your message dated Sat, 24 Sep 2022 17:00:43 + with message-id and subject line Bug#1019891: fixed in sqlglot 6.0.4-1 has caused the Debian Bug report #1019891, regarding mycli: Always crashes at runtime because the module 'sqlglot' is missing to be marked as done. This means that you claim

Bug#1020441: marked as done (linux: autopkgtest needs update for new version of gcc-11)

Your message dated Sat, 24 Sep 2022 17:00:17 + with message-id and subject line Bug#1019749: fixed in linux 5.19.11-1 has caused the Debian Bug report #1019749, regarding linux: autopkgtest needs update for new version of gcc-11 to be marked as done. This means that you claim that the

Bug#1019749: marked as done (linux autopkg tests fail with stderr output, blocking gcc-11)

Your message dated Sat, 24 Sep 2022 17:00:17 + with message-id and subject line Bug#1019749: fixed in linux 5.19.11-1 has caused the Debian Bug report #1019749, regarding linux autopkg tests fail with stderr output, blocking gcc-11 to be marked as done. This means that you claim that the

Bug#1020437: clisp FTBFS with PARI 2.15.0

On Wed, Sep 21, 2022 at 09:23:00PM +0300, Adrian Bunk wrote: > Source: clisp > Version: 1:2.49.20210628.gitde01f0f-2 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/logs.php?pkg=clisp=1%3A2.49.20210628.gitde01f0f-2%2Bb1 To build with PARI 2.15.0-2, please apply the

Processed (with 1 error): your mail

Processing commands for cont...@bugs.debian.org: > severity 1020639 important Bug #1020639 [pdfarranger] pdfarranger: libqpdf 11 require pdfarranger 1.9.1 Severity set to 'important' from 'grave' > Lowering serverity because pdfarranger as NOT YET been removed from testing Unknown command or

Bug#1017313: postfix: FTBFS: unistd.h:363:13: error: conflicting types for ‘closefrom’; have ‘void(int)’

On Saturday, September 24, 2022 5:40:20 AM EDT Christian Göttsche wrote: > control: tags -1 fixed-upstream > > The issue is fixed upstream in version 3.6.5[1]. > > [1]: https://www.postfix.org/announcements/postfix-3.6.5.html Thanks. I'm way behind on updating postfix. I'll try to find the

Bug#1020639: (no subject)

severity 1020639 important Lowering serverity because pdfarranger as NOT YET been removed from testing

Bug#1020639: pdfarranger: libqpdf 11 require pdfarranger 1.9.1

Package: pdfarranger Version: 1.8.2-1 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: jeromerob...@gmx.com Dear Maintainer, pdfarranger depends on pikepdf. pikepdf 5.1.1 FTBS with libqpdf 11: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019694

Processed (with 1 error): reassign 1019687 to dh-raku, merging 1019579 1019687, affects 1019687

Processing commands for cont...@bugs.debian.org: > reassign 1019687 dh-raku Bug #1019687 [raku-meta6] raku-meta6: trying to overwrite '/usr/lib/perl6/vendor/precomp/A234FA60C249CF61DEFEC1FD7D434DF2D0D597D5/0F/0F5CCC81E3EDCF1EE7139F2E5E72A089F34C3091', which is also in package raku-license-spdx

Processed: reassign 1019579 to dh-raku ..., affects 1019579

Processing commands for cont...@bugs.debian.org: > reassign 1019579 dh-raku Bug #1019579 [raku-json-unmarshal] raku-json-unmarshal: trying to overwrite '/usr/lib/perl6/vendor/precomp/C847F303DB03DE97DCB92EFEE90C0526E0D4FDF0/C1/C1DA909DAD9BF713751A74EBF038C545A1EA6ECC', which is also in package

Processed: Bug#1020031 marked as pending in khmer

Processing control commands: > tag -1 pending Bug #1020031 [src:khmer] khmer: FTBFS: ld: cannot find build/temp.linux-x86_64-3.10/src/khmer/_cpy_khmer.o: No such file or directory Added tag(s) pending. -- 1020031: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020031 Debian Bug Tracking

Bug#1020031: marked as pending in khmer

Control: tag -1 pending Hello, Bug #1020031 in khmer 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:

Bug#1020102: marked as done (golang-github-mattn-go-runewidth: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 8 github.com/mattn/go-runewidth returned exit code 1)

Your message dated Sat, 24 Sep 2022 13:49:05 + with message-id and subject line Bug#1020102: fixed in golang-github-mattn-go-runewidth 0.0.13-3 has caused the Debian Bug report #1020102, regarding golang-github-mattn-go-runewidth: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v

Processed: found 1014982 in 3.17.0-3

Processing commands for cont...@bugs.debian.org: > found 1014982 3.17.0-3 Bug #1014982 {Done: Markus Koschany } [src:apache-jena] apache-jena: CVE-2021-33192 CVE-2021-39239 CVE-2022-28890 Marked as found in versions apache-jena/3.17.0-3. > thanks Stopping processing here. Please contact me if

Processed: bug 1020161 is forwarded to https://github.com/golang/go/issues/55849

Processing commands for cont...@bugs.debian.org: > forwarded 1020161 https://github.com/golang/go/issues/55849 Bug #1020161 [src:golang-golang-x-net] golang-golang-x-net: FTBFS: make: *** [debian/rules:11: binary] Error 25 Set Bug forwarded-to-address to

Bug#1014982: marked as done (apache-jena: CVE-2021-33192 CVE-2021-39239 CVE-2022-28890)

Your message dated Sat, 24 Sep 2022 12:50:55 + with message-id and subject line Bug#1014982: fixed in apache-jena 4.5.0-1 has caused the Debian Bug report #1014982, regarding apache-jena: CVE-2021-33192 CVE-2021-39239 CVE-2022-28890 to be marked as done. This means that you claim that the

Bug#1019994: marked as done (wheel: FTBFS: error: invalid command 'bdist_wheel')

Your message dated Sat, 24 Sep 2022 12:05:16 + with message-id and subject line Bug#1019994: fixed in wheel 0.37.1-3 has caused the Debian Bug report #1019994, regarding wheel: FTBFS: error: invalid command 'bdist_wheel' to be marked as done. This means that you claim that the problem has

Bug#1020095: marked as done (emacs-buttercup: FTBFS: make[1]: *** [Makefile:16: test-docs] Error 255)

Your message dated Sat, 24 Sep 2022 11:49:37 + with message-id and subject line Bug#1020095: fixed in emacs-buttercup 1.26-1 has caused the Debian Bug report #1020095, regarding emacs-buttercup: FTBFS: make[1]: *** [Makefile:16: test-docs] Error 255 to be marked as done. This means that you

Bug#1020110: marked as done (kaptive: FTBFS: make[1]: *** [debian/rules:12: override_dh_auto_clean] Error 25)

Your message dated Sat, 24 Sep 2022 11:49:54 + with message-id and subject line Bug#1020110: fixed in kaptive 2.0.3-2 has caused the Debian Bug report #1020110, regarding kaptive: FTBFS: make[1]: *** [debian/rules:12: override_dh_auto_clean] Error 25 to be marked as done. This means that

Bug#1020375: closing 1020375

On Fri, Sep 23, 2022 at 10:18:22PM -0700, Dima Kogan wrote: > close 1020375 > thanks > > I uploaded 1.0+1git91f4b1-4 that explicitly state that no arch-indep > tests are defined. This appears to have made the arch-indep builds > happy The arch-indep build is happy due to the binary you

Bug#1020147: marked as done (ueberzug: FTBFS: make[1]: *** [debian/rules:19: override_dh_auto_build] Error 25)

Your message dated Sat, 24 Sep 2022 11:34:40 + with message-id and subject line Bug#1020147: fixed in ueberzug 18.1.9-3 has caused the Debian Bug report #1020147, regarding ueberzug: FTBFS: make[1]: *** [debian/rules:19: override_dh_auto_build] Error 25 to be marked as done. This means that

Bug#1020619: libstdc++-arm-none-eabi-newlib: Fails to install because of incorrect versioned depency on gcc-arm-none-eabi

Package: libstdc++-arm-none-eabi-newlib Version: 15:10.3-2021.07-4+20 Severity: serious Justification: Policy 2.2.1 This package depends on gcc-arm-none-eabi (= 15:10.3-2021.07-4), however the latter version does not exist in main because there has been a binNMU, so the version present is

Processed: src:openlibm: fails to migrate to testing for too long: FTBFS on armhf and mips64el

Processing control commands: > close -1 0.8.1+dfsg-2 Bug #1020617 [src:openlibm] src:openlibm: fails to migrate to testing for too long: FTBFS on armhf and mips64el Marked as fixed in versions openlibm/0.8.1+dfsg-2. Bug #1020617 [src:openlibm] src:openlibm: fails to migrate to testing for too

Bug#1020617: src:openlibm: fails to migrate to testing for too long: FTBFS on armhf and mips64el

Source: openlibm Version: 0.7.0+dfsg-2 Severity: serious Control: close -1 0.8.1+dfsg-2 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than

Bug#1017313: postfix: FTBFS: unistd.h:363:13: error: conflicting types for ‘closefrom’; have ‘void(int)’

control: tags -1 fixed-upstream The issue is fixed upstream in version 3.6.5[1]. [1]: https://www.postfix.org/announcements/postfix-3.6.5.html

Processed: Re: Bug#1017313: postfix: FTBFS: unistd.h:363:13: error: conflicting types for ‘closefrom’; have ‘void(int)’

Processing control commands: > tags -1 fixed-upstream Bug #1017313 [src:postfix] postfix: FTBFS: unistd.h:363:13: error: conflicting types for ‘closefrom’; have ‘void(int)’ Added tag(s) fixed-upstream. -- 1017313: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1017313 Debian Bug Tracking

Processed: incorrect formatting in /usr/share/pari/pari.desc

Processing control commands: > block 1020437 by -1 Bug #1020437 [src:clisp] clisp FTBFS with PARI 2.15.0 1020437 was not blocked by any bugs. 1020437 was not blocking any bugs. Added blocking bug(s) of 1020437: 1020613 -- 1020437: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1020437

Bug#1020082: marked as done (scons: FTBFS: make: *** [debian/rules:10: binary] Error 25)

Your message dated Sat, 24 Sep 2022 07:50:48 + with message-id and subject line Bug#1020082: fixed in scons 4.4.0+dfsg-1 has caused the Debian Bug report #1020082, regarding scons: FTBFS: make: *** [debian/rules:10: binary] Error 25 to be marked as done. This means that you claim that the

Bug#1020009: marked as done (jupyter-server: FTBFS: ModuleNotFoundError: No module named 'setuptools')

Your message dated Sat, 24 Sep 2022 07:50:22 + with message-id and subject line Bug#1020009: fixed in jupyter-server 1.18.1-2 has caused the Debian Bug report #1020009, regarding jupyter-server: FTBFS: ModuleNotFoundError: No module named 'setuptools' to be marked as done. This means that

Bug#1015733: marked as done (ghc: ABI reproducibility broken in 9.0.2)

Your message dated Sat, 24 Sep 2022 07:50:11 + with message-id and subject line Bug#1015733: fixed in ghc 9.0.2-4 has caused the Debian Bug report #1015733, regarding ghc: ABI reproducibility broken in 9.0.2 to be marked as done. This means that you claim that the problem has been dealt

Bug#1020061: marked as done (mkdocs-material-extensions: FTBFS: ModuleNotFoundError: No module named 'setuptools')

Your message dated Sat, 24 Sep 2022 07:19:07 + with message-id and subject line Bug#1020061: fixed in mkdocs-material-extensions 1.0.3-2 has caused the Debian Bug report #1020061, regarding mkdocs-material-extensions: FTBFS: ModuleNotFoundError: No module named 'setuptools' to be marked as

Bug#1019855: Fwd: libc6: immediately crashes with SIGILL on 4th gen Intel Core CPUs (seems related to AVX2 instructions), bricking the whole system

Hi Aurelien, On Tue, Sep 20, 2022 at 11:20:26PM +0200, Aurelien Jarno wrote: > Have you been able to progress on that? Do you need some help for a > specific step? For what it’s worth, I’ve upgraded libc6 on my Haswell system (Xeon E3-1245v3) and everything seems to be working fine. Regards,

Bug#1020592: [Pkg-javascript-devel] Bug#1020592: nodejs: Testsuite is using smoil keys

On 23 September 2022 21:18:26 UTC, "Jérémy Lal" wrote: >I'll upload nodejs 18.9.1 this week-end, along with a/your fix for that >issue. Thank you. > >Jérémy -- Sebastian

Processed: Re: assaultcube-data: difficult copyright situation

Processing control commands: > tags -1 pending Bug #1018969 [assaultcube-data] assaultcube-data: difficult copyright situation Added tag(s) pending. -- 1018969: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018969 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1018969: assaultcube-data: difficult copyright situation

Control: tags -1 pending On Fri, 2 Sep 2022 20:59:56 +0200 Tobias Frost wrote: > X-Debbugs-CC: 935...@bugs.debian.org > Package: assaultcube-data > Version: 1.2.0.2.1-3 > Severity: serious > Justification: Policy 2.2.3 > Control: affects -1 assaultcube > > When I was looking into updating