Bug#1003490: u-boot: FTBFS on arch:all with qemu-ppce500 target

2022-01-25 Thread Aurelien Jarno
On 2022-01-25 19:04, Vagrant Cascadian wrote: > On 2022-01-25, Vagrant Cascadian wrote: > > On 2022-01-15, Aurelien Jarno wrote: > >> On 2022-01-11 16:40, Vagrant Cascadian wrote: > >>> On 2022-01-11, Lennart Sorensen wrote: > >>> > On Mon, Jan 10, 2022 at 05:10:04PM -0800, Vagrant Cascadian wrote:

Bug#990201: singularity-container: CVE-2021-33622

2022-01-25 Thread Andreas Tille
Hi, just for the record: This CVE is fixed only in the Pro edition[1] but there is no record that the CE edition which we can package is fixed yet. Kind regards Andreas. [1] https://support.sylabs.io/support/solutions/articles/4287130-3-5-8-security-release-cve-2021-33622- -- htt

Bug#998749: firmware-misc-nonfree: i915 freezes randomly in X especially when playing videos

2022-01-25 Thread Michael Prokop
severity 998749 important thanks Hi, * Jonibek Ander uulu [Sun Nov 07, 2021 at 09:45:52PM +0600]: > Package: firmware-misc-nonfree > Version: 20210315-3 > Severity: grave > Justification: renders package unusable I'd assume this bug report needs further information so it can be handled by the k

Processed: Re: Bug#998749: firmware-misc-nonfree: i915 freezes randomly in X especially when playing videos

2022-01-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 998749 important Bug #998749 [firmware-misc-nonfree] firmware-misc-nonfree: i915 freezes randomly in X especially when playing videos Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you n

Bug#999011: marked as done (rig: missing required debian/rules targets build-arch and/or build-indep)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Wed, 26 Jan 2022 05:50:13 + with message-id and subject line Bug#999011: fixed in rig 1.11-1.1 has caused the Debian Bug report #999011, regarding rig: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim that

Bug#965802: marked as done (rig: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Wed, 26 Jan 2022 05:50:13 + with message-id and subject line Bug#965802: fixed in rig 1.11-1.1 has caused the Debian Bug report #965802, regarding rig: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the problem

Bug#995356: python-parameterized: autopkgtest regression: AssertionError in tearDownModule

2022-01-25 Thread Sandro Tosi
> If nobody is going to fix this issue, I am going to upload the package > removing the autopkgtest soon. I took your NMU diff and made it a team upload, thanks! > This issue is blocking migration to > testing for too long. The package can't be easily removed because it's a > key package. is the

Bug#1003490: u-boot: FTBFS on arch:all with qemu-ppce500 target

2022-01-25 Thread Vagrant Cascadian
On 2022-01-25, Vagrant Cascadian wrote: > On 2022-01-15, Aurelien Jarno wrote: >> On 2022-01-11 16:40, Vagrant Cascadian wrote: >>> On 2022-01-11, Lennart Sorensen wrote: >>> > On Mon, Jan 10, 2022 at 05:10:04PM -0800, Vagrant Cascadian wrote: >>> >> Something in the toolchain recently changed whic

Bug#1000435: Matplotlib crashes on mips64el in lines.py

2022-01-25 Thread YunQiang Su
Sandro Tosi 于2022年1月26日周三 05:16写道: > > > It is due to gcc-11 of mips64el. > > > > -O1, -O2 may generate bad code, while -O0 and -O3 works well. > > As a workaround: we can: > > > > The attachment is a workaround patch. > > is there a bug against gcc-11 that i can track so that i dont have to > kee

Bug#1003490: u-boot: FTBFS on arch:all with qemu-ppce500 target

2022-01-25 Thread Vagrant Cascadian
A bug in Debian is causing a build failure of the qemu-ppce500 target: https://bugs.debian.org/1003490 I've CCed u-boot in case they're not aware of the issue. Some background follows... On 2022-01-15, Aurelien Jarno wrote: > On 2022-01-11 16:40, Vagrant Cascadian wrote: >> On 2022-01-11, Len

Bug#1004311: [PATCH] add_cmake_libbpf_enabled_option.patch: Only check the macro HAVE_BPF

2022-01-25 Thread Ben Hutchings
Control: tag -1 patch The patch add_cmake_libbpf_enabled_option.patch is indeed the problem, because it doesn't consistently use the same macro name. The fix is below. If you're not able to upload with this today, can I please NMU to unblock linux? Ben. --- a/debian/patches/add_cmake_libbpf_en

Processed: [PATCH] add_cmake_libbpf_enabled_option.patch: Only check the macro HAVE_BPF

2022-01-25 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #1004311 [pahole] pahole segfaults during kernel build Added tag(s) patch. -- 1004311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1002090: marked as done (gr-soapy: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create')

2022-01-25 Thread Debian Bug Tracking System
Your message dated Wed, 26 Jan 2022 00:39:24 + with message-id and subject line Bug#1004322: Removed package(s) from unstable has caused the Debian Bug report #1002090, regarding gr-soapy: FTBFS: ./obj-x86_64-linux-gnu/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create' to b

Bug#1000818: marked as done (python3-ulmo: if rebuilt now, missing python3-suds dependency)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Wed, 26 Jan 2022 00:36:38 + with message-id and subject line Bug#1000818: fixed in python-ulmo 0.8.8+dfsg1-1 has caused the Debian Bug report #1000818, regarding python3-ulmo: if rebuilt now, missing python3-suds dependency to be marked as done. This means that you claim th

Bug#1001371: pytest-twisted: (autopkgtest) needs update for python3.10: E {'warnings': 2} != {'warnings': 1}

2022-01-25 Thread peter green
The upstream report at https://github.com/pytest-dev/pytest-twisted/issues/146 was closed as the additional warning is produced by Twisted. The Twisted fix isn't merged yet. It looks like the twisted fix has now been merged upstream, does it make sense to apply it as a patch to the Debian twiste

Bug#1003275: marked as done (mir: FTBFS: /<>/src/client/lttng/input_receiver_report.cpp:80:1: internal compiler error: maximum number of generated reload insns per insn achieved (90))

2022-01-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jan 2022 23:04:14 + with message-id and subject line Bug#1003275: fixed in mir 1.8.2+dfsg-1 has caused the Debian Bug report #1003275, regarding mir: FTBFS: /<>/src/client/lttng/input_receiver_report.cpp:80:1: internal compiler error: maximum number of generated re

Bug#997053: marked as done (ganeti FTBFS: doc/index.rst:94:duplicated entry found in toctree: design-location)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jan 2022 22:48:50 + with message-id and subject line Bug#997053: fixed in ganeti 3.0.1-3 has caused the Debian Bug report #997053, regarding ganeti FTBFS: doc/index.rst:94:duplicated entry found in toctree: design-location to be marked as done. This means that you

Bug#993559: marked as done (ganeti-3.0 unable to remove a dpkg-divert during postrm when 2.16 is still there)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jan 2022 22:48:50 + with message-id and subject line Bug#993559: fixed in ganeti 3.0.1-3 has caused the Debian Bug report #993559, regarding ganeti-3.0 unable to remove a dpkg-divert during postrm when 2.16 is still there to be marked as done. This means that you c

Bug#1003979: marked as done (arachne-pnr build-depends on removed package)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jan 2022 22:25:23 + with message-id <1a6a09f8-ecf2-6fdc-80d1-299cdf38c...@p10link.net> and subject line Re: arachne-pnr build-depends on removed package has caused the Debian Bug report #1003979, regarding arachne-pnr build-depends on removed package to be marked as d

Bug#1003981: marked as done (nextpnr build-depends on removed package)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jan 2022 22:25:23 + with message-id <1a6a09f8-ecf2-6fdc-80d1-299cdf38c...@p10link.net> and subject line Re: arachne-pnr build-depends on removed package has caused the Debian Bug report #1003981, regarding nextpnr build-depends on removed package to be marked as done.

Bug#1000774: marked as done (python3-matplotlib: Segfault on mips64el in draw)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jan 2022 22:19:39 + with message-id and subject line Bug#1000435: fixed in matplotlib 3.5.1-2 has caused the Debian Bug report #1000435, regarding python3-matplotlib: Segfault on mips64el in draw to be marked as done. This means that you claim that the problem has b

Bug#1000435: marked as done (Matplotlib crashes on mips64el in lines.py)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jan 2022 22:19:39 + with message-id and subject line Bug#1000435: fixed in matplotlib 3.5.1-2 has caused the Debian Bug report #1000435, regarding Matplotlib crashes on mips64el in lines.py to be marked as done. This means that you claim that the problem has been de

Bug#1000435: marked as pending in matplotlib

2022-01-25 Thread Sandro Tosi
Control: tag -1 pending Hello, Bug #1000435 in matplotlib reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/python-team/packages/matplotlib/-/commit/39ef996d3ceef

Processed: Bug#1000435 marked as pending in matplotlib

2022-01-25 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1000435 [src:matplotlib] Matplotlib crashes on mips64el in lines.py Bug #1000774 [src:matplotlib] python3-matplotlib: Segfault on mips64el in draw Added tag(s) pending. Added tag(s) pending. -- 1000435: https://bugs.debian.org/cgi-bin/bugreport.

Processed: affects 1004311

2022-01-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1004311 + src:linux Bug #1004311 [pahole] pahole segfaults during kernel build Added indication that 1004311 affects src:linux > thanks Stopping processing here. Please contact me if you need assistance. -- 1004311: https://bugs.debian.o

Bug#999240: sc: missing required debian/rules targets build-arch and/or build-indep

2022-01-25 Thread Adam Majer
On 1/25/22 18:48, Ying-Chun Liu (PaulLiu) wrote: I've updated debian/rules and fixes this bug. I'll wait for 10 days if no other comments. You are more than welcome to upload without delay queue. The patch looks good, especially the work you did to isolate the messages from the format parser

Bug#1003979: arachne-pnr build-depends on removed package

2022-01-25 Thread Nilesh Patra
Hi peter, On Tue, 18 Jan 2022 21:10:35 + peter green wrote: > Package: arachne-pnr > Version: 0.1+20190728gitc40fb22-2 > Tags: bookworm, sid > Severity: serious > > arachne-pnr build-depends on fpga-icestorm-chipdb which is no longer built by > the fpga-icestorm source package, Admittedly,

Bug#1004194: marked as done (loguru: CVE-2022-0329)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jan 2022 21:26:18 + with message-id and subject line Bug#1004194: fixed in loguru 0.5.3-5 has caused the Debian Bug report #1004194, regarding loguru: CVE-2022-0329 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: update bts with meta info

2022-01-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1002532 src:ruby-pygments.rb 1.2.1-2 Bug #1002532 {Done: Mattia Rizzolo } [src:pygments, src:ruby-pygments.rb] pygments breaks ruby-pygments.rb autopkgtest: UTF-8 != ASCII-8BIT Bug reassigned from package 'src:pygments, src:ruby-pygment

Processed: tagging 1004285, tagging 1004340, tagging 1002246

2022-01-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1004285 + sid bookworm Bug #1004285 [davical] davical: problems after upgrade to php 8, calendar clients reports "500" Added tag(s) sid and bookworm. > tags 1004340 + experimental Bug #1004340 {Done: Sebastian Dröge } [src:pitivi] pitivi: F

Bug#1000435: Matplotlib crashes on mips64el in lines.py

2022-01-25 Thread Sandro Tosi
> It is due to gcc-11 of mips64el. > > -O1, -O2 may generate bad code, while -O0 and -O3 works well. > As a workaround: we can: > > The attachment is a workaround patch. is there a bug against gcc-11 that i can track so that i dont have to keep this workaround forever but just until it's fixed in

Bug#1000435: Matplotlib crashes on mips64el in lines.py

2022-01-25 Thread Nilesh Patra
Sandro, Looks like Yunqiang has a patch that fixed the problem. Can you add this patch and upload? Would you allow them to NMU? (See the mail below) Thanks, -Nilesh On Tue, 25 Jan 2022 16:58:34 +0800 Yunqiang Su wrote: > On Sat, 22 Jan 2022 18:23:13 +0800 YunQiang Su wrote: > > On Sat, 22 Jan

Bug#1004360: src:astroscrappy: fails to migrate to testing for too long: FTBFS on mipsel and autopkgtest regression

2022-01-25 Thread Paul Gevers
Source: astroscrappy Version: 1.0.8-1 Severity: serious Control: close -1 1.1.0-1 Tags: sid bookworm ftbfs User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1001491 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing

Processed: src:astroscrappy: fails to migrate to testing for too long: FTBFS on mipsel and autopkgtest regression

2022-01-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.1.0-1 Bug #1004360 [src:astroscrappy] src:astroscrappy: fails to migrate to testing for too long: FTBFS on mipsel and autopkgtest regression Marked as fixed in versions astroscrappy/1.1.0-1. Bug #1004360 [src:astroscrappy] src:astroscrappy: fails to migra

Processed: update bts with meta info

2022-01-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1004087 src:img2pdf 0.4.2-1 Bug #1004087 {Done: Johannes Schauer Marin Rodrigues } [src:pillow, src:img2pdf] pillow breaks img2pdf autopkgtest: TypeError: object is not an array Bug reassigned from package 'src:pillow, src:img2pdf' to '

Bug#983985: bctoolbox: ftbfs with GCC-11

2022-01-25 Thread Dennis Filder
X-Debbugs-CC: Andrea Pappacoda , Bastian Germann On Tue, Jan 25, 2022 at 07:07:44PM +0100, Bastian Germann wrote: > Do you mean the NMU that was uploaded at > https://mentors.debian.net/package/bctoolbox? > That was not uploaded by me. No, I actually meant the mediastreamer2 NMU last November,

Processed: Re: pahole segfaults during kernel build

2022-01-25 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #1004311 [pahole] pahole segfaults during kernel build Severity set to 'serious' from 'normal' -- 1004311: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004311 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: archiving 1002175

2022-01-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > archive 1002175 Bug #1002175 {Done: Andrej Shadura } [src:docker-compose] docker-compose: FTBFS: AttributeError: 'NoneType' object has no attribute 'split' archived 1002175 to archive/75 (from 1002175) > thanks Stopping processing here. Please

Bug#983985: bctoolbox: ftbfs with GCC-11

2022-01-25 Thread Bastian Germann
X-Debbugs-CC: Andrea Pappacoda On Tue, 25 Jan 2022 18:13:01 +0100 Dennis Filder wrote: X-Debbugs-CC: Bastian Germann On Mon, Jan 24, 2022 at 08:18:02PM +0100, Bastian Germann wrote: > Upstream has that fixed with > https://gitlab.linphone.org/BC/public/bctoolbox/-/commit/9ac0e412c45bf28d028

Bug#999240: sc: missing required debian/rules targets build-arch and/or build-indep

2022-01-25 Thread Ying-Chun Liu (PaulLiu)
Hi all, I've updated debian/rules and fixes this bug. I'll wait for 10 days if no other comments. And then start the NMU process. The NMU will be uploaded to DELAY/10. Attachment is the debdiff. The following changes are made:   * Change debhelper compat version from 5 to 11. (Closes: #99924

Bug#1004356: ruby-gitlab-license-finder: missing Breaks+Replaces: ruby-license-finder (<< 6)

2022-01-25 Thread Andreas Beckmann
Package: ruby-gitlab-license-finder Version: 6.14.2.1-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files without declaring a Breaks+Replaces relation.

Bug#983985: bctoolbox: ftbfs with GCC-11

2022-01-25 Thread Dennis Filder
X-Debbugs-CC: Bastian Germann On Mon, Jan 24, 2022 at 08:18:02PM +0100, Bastian Germann wrote: > Upstream has that fixed with > https://gitlab.linphone.org/BC/public/bctoolbox/-/commit/9ac0e412c45bf28d02829e9d912342359714f638 Thanks for the effort (and the NMU). I'm currently in the process of

Bug#997367: virt-manager: FTBFS: AssertionError: Command was: ./virt-xml test-for-virtxml --print-diff --define --add-device --host-device usb_device_4b3_4485_noserial --connect __virtinst_test__test:

2022-01-25 Thread Fabio Fantoni
Hi, I saw that remain few days for autoremoval from testing I prepared an MR with some upstream patch that solve current FTBFS with some tests and another small fix for a crash case: https://salsa.debian.org/libvirt-team/virt-manager/-/merge_requests/12 can someone merge it and do a new build

Bug#1004340: marked as done (pitivi: FTBFS in unstable and testing)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jan 2022 14:36:25 + with message-id and subject line Bug#1004340: fixed in pitivi 2021.05-1 has caused the Debian Bug report #1004340, regarding pitivi: FTBFS in unstable and testing to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1004340: pitivi: FTBFS in unstable and testing

2022-01-25 Thread Graham Inggs
Source: pitivi Version: 2020.09.2-3 Severity: serious Tags: ftbfs bookworm sid Hi Maintainer Since sometime around January 15, pitivi started to FTBFS in unstable [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian

Bug#1004337: marked as done (glade: FTBFS in unstable and testing)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jan 2022 12:18:40 + with message-id and subject line Bug#1004337: fixed in glade 3.38.2-7 has caused the Debian Bug report #1004337, regarding glade: FTBFS in unstable and testing to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1004337: marked as pending in glade

2022-01-25 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #1004337 in glade reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/glade/-/commit/8ce10c43b346eba48c5c21fde103d4004

Processed: Bug#1004337 marked as pending in glade

2022-01-25 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1004337 [src:glade] glade: FTBFS in unstable and testing Added tag(s) pending. -- 1004337: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1004337: glade: FTBFS in unstable and testing

2022-01-25 Thread Graham Inggs
Source: glade Version: 3.38.2-6 Severity: serious Tags: ftbfs bookworm sid Hi Maintainer Since sometime around January 13, glade started to FTBFS in unstable [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://tests.reproducible-builds.org/debian/rb-p

Bug#1004087: marked as done (pillow breaks img2pdf autopkgtest: TypeError: object is not an array)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jan 2022 11:33:45 + with message-id and subject line Bug#1004087: fixed in img2pdf 0.4.2-2 has caused the Debian Bug report #1004087, regarding pillow breaks img2pdf autopkgtest: TypeError: object is not an array to be marked as done. This means that you claim that

Bug#1003661: marked as done (Pillow claims GIF frame to be mode RGB instead of P)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jan 2022 11:33:45 + with message-id and subject line Bug#1003661: fixed in img2pdf 0.4.2-2 has caused the Debian Bug report #1003661, regarding Pillow claims GIF frame to be mode RGB instead of P to be marked as done. This means that you claim that the problem has b

Bug#995242: isc-dhcp-server: omshell returns inconsistent results or segfaults

2022-01-25 Thread Andrea Turbiglio
I temporarily switched our servers to the source package version of isc-dhcp-server (4.4.2) and the same issue doesn't happens, so I assume this is a problem with the Debian version of the package. The servers are now running on Debian 11 without issues (the only problematic package in the trans

Processed: closing 1003875

2022-01-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1003875 2.33-3 Bug #1003875 [src:glibc] binutils - autopktest fails on ppc64el: Error: unrecognized opcode: `vspltisb' Bug #1003847 [src:glibc] binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others) Igno

Processed: found 1003847 in 2.29-1, fixed 1003847 in 2.33-3

2022-01-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1003847 2.29-1 Bug #1003847 {Done: Aurelien Jarno } [src:glibc] binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others) Bug #1003875 {Done: Aurelien Jarno } [src:glibc] binutils - autopktest fails on ppc

Processed: reassign 1003847 to src:glibc, forcibly merging 1003847 1003875

2022-01-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1003847 src:glibc Bug #1003847 {Done: Aurelien Jarno } [glibc] binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others) Bug reassigned from package 'glibc' to 'src:glibc'. No longer marked as found in v

Processed (with 1 error): forcibly merging 1003847 1003875

2022-01-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1003847 1003875 Bug #1003847 {Done: Aurelien Jarno } [glibc] binutils breaks glibc autopkgtest on ppc64el: unrecognized opcode: `vspltisb' (and others) Unable to merge bugs because: package of #1003875 is 'src:glibc' not 'glibc' Faile

Processed: tagging 1004272, severity of 1004272 is critical, affects 1004272

2022-01-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1004272 + security Bug #1004272 [src:binutils] binutils: missing RELRO header Added tag(s) security. > severity 1004272 critical Bug #1004272 [src:binutils] binutils: missing RELRO header Severity set to 'critical' from 'serious' > affects 10

Bug#1000435: Matplotlib crashes on mips64el in lines.py

2022-01-25 Thread Yunqiang Su
On Sat, 22 Jan 2022 18:23:13 +0800 YunQiang Su wrote: > On Sat, 22 Jan 2022 17:06:00 +0800 YunQiang Su wrote: >> On Tue, 23 Nov 2021 08:08:23 +0100 Ole Streicher wrote: >>> Source: matplotlib >>> Severity: serious >>> Version: 3.5.0-1 >>> Control: affects -1 yt >>> Control: affects -1 astropy >>

Bug#1003897: marked as done (acpi: ACPI errors at startup)

2022-01-25 Thread Debian Bug Tracking System
Your message dated Tue, 25 Jan 2022 09:32:10 +0100 with message-id and subject line Re: Bug#1003897: acpi: ACPI errors at startup has caused the Debian Bug report #1003897, regarding acpi: ACPI errors at startup to be marked as done. This means that you claim that the problem has been dealt with.