Bug#991800: altos FTBFS with the bookworm gcc-arm-none-eabi

2021-08-01 Thread Adrian Bunk
Source: altos Version: 1.9.6-1 Severity: serious Tags: ftbfs bookworm sid altos FTBFS with the bookworm gcc-arm-none-eabi that is already in unstable: https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/altos.html ... CC telegps-v0.3-1.9.7.elf /usr/lib/gcc/arm-none-eabi/10.2.1/

Bug#991648: marked as done (python-a38: FTBFS: AssertionError: "routines:CMS_verify:content verify error" does not match "b'Verification failure\n140224232826176:error:2E099064:CMS routines:cms_signer

2021-08-01 Thread Debian Bug Tracking System
Your message dated Mon, 02 Aug 2021 06:03:25 + with message-id and subject line Bug#991648: fixed in python-a38 0.1.3-2 has caused the Debian Bug report #991648, regarding python-a38: FTBFS: AssertionError: "routines:CMS_verify:content verify error" does not match "b'Verification failure\n14

Bug#991788: xfce4-settings: black screen after suspend when laptop lid is closed and re-opened

2021-08-01 Thread truetechie
Package: xfce4-settings Version: 4.16.0-1 Severity: critical On Debian and, by extension, Ubuntu, when suspending a laptop via closing the lid on XFCE, the screen stays black after resuming from suspend. The only way to "fix" the system is to blindly type "xrandr --auto" into a terminal or swit

Bug#991739: marked as done (GPSD time will jump back 1024 weeks at after week=2180 (23-October-2021))

2021-08-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Aug 2021 20:18:21 + with message-id and subject line Bug#991739: fixed in gpsd 3.22-4 has caused the Debian Bug report #991739, regarding GPSD time will jump back 1024 weeks at after week=2180 (23-October-2021) to be marked as done. This means that you claim that t

Bug#987441: s390x installation bugs

2021-08-01 Thread Valentin Vidic
On Sun, Aug 01, 2021 at 05:10:07PM +0200, Cyril Brulebois wrote: > Valentin Vidic (2021-08-01): > > No problem, I was not able to reproduce this reliably or get a core > > dump for this crash. It could just be an emulation problem with qemu > > or some timing issue for the first installer step. If

Processed: tagging 988707

2021-08-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 988707 + bookworm sid Bug #988707 {Done: A. Maitland Bottoms } [src:qthid-fcd-controller] qthid-fcd-controller: triggers lintian autoreject tag 'bogus-mail-host' Added tag(s) bookworm and sid. > thanks Stopping processing here. Please cont

Processed: found 989792 in 1.8.0-1

2021-08-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 989792 1.8.0-1 Bug #989792 [src:dqlite] dqlite assumes a kernel configured with 4kB page size Marked as found in versions dqlite/1.8.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 989792: https://bugs.

Processed: unarchiving 707803, found 707803 in 5.0.2-2.2+squeeze1, unarchiving 698631 ...

2021-08-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 707803 Bug #707803 {Done: Ivo De Decker } [bacula] bacula: copyright file missing after upgrade (policy 12.5) Unarchived Bug 707803 > found 707803 5.0.2-2.2+squeeze1 Bug #707803 {Done: Ivo De Decker } [bacula] bacula: copyright file mi

Processed: bullseye-ignore

2021-08-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # We're getting very close to the bullseye release. Although we'd > # (still) love to have these bugs fixed, let's focus on what absolutely > # needs fixing. > # I'm considering adding a release-notes section about some/most of > # these bugs > us

Processed: Re: Processed (with 1 error): document fail2ban brokenness in release-notes

2021-08-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 991781 fail2ban is broken with mail from bsd-mailx Bug #991781 [release-notes] fix for CVE-2021-32749 breaks systems with mail from bsd-mailx Changed Bug title to 'fail2ban is broken with mail from bsd-mailx' from 'fix for CVE-2021-32749

Processed (with 1 error): document fail2ban brokenness in release-notes

2021-08-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 991449 -1 Bug #991449 [fail2ban] fix for CVE-2021-32749 breaks systems with mail from bsd-mailx Bug 991449 cloned as bug 991781 > reassign -1 release-notes Bug #991781 [fail2ban] fix for CVE-2021-32749 breaks systems with mail from bsd-mai

Processed: tagging 991739

2021-08-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 991739 - bullseye-ignore Bug #991739 [gpsd] GPSD time will jump back 1024 weeks at after week=2180 (23-October-2021) Removed tag(s) bullseye-ignore. > thanks Stopping processing here. Please contact me if you need assistance. -- 991739: ht

Bug#991778: dlint: Dlint fails to find version number of dig

2021-08-01 Thread Patrik Schindler
Package: dlint Version: 1.4.0-8 Severity: grave Tags: patch Justification: renders package unusable On my Debian Buster system, dig fails to work with ;; This program requires DiG version 2.1 or newer, which I cannot find. Checking on this, I saw that the "ver" call in line 109 doesn't output a

Bug#987441: s390x installation bugs

2021-08-01 Thread Cyril Brulebois
Valentin Vidic (2021-08-01): > No problem, I was not able to reproduce this reliably or get a core > dump for this crash. It could just be an emulation problem with qemu > or some timing issue for the first installer step. If there is no > update on this problem I think we can even close it for no

Bug#987441: marked as done (debian-installer: D-I must get ready for Bullseye)

2021-08-01 Thread Debian Bug Tracking System
Your message dated Sun, 1 Aug 2021 16:35:48 +0200 with message-id <20210801143548.d7km2yzgm5qcf...@mraw.org> and subject line Re: Bug#987441: s390x installation bugs has caused the Debian Bug report #987441, regarding debian-installer: D-I must get ready for Bullseye to be marked as done. This mea

Processed: bullseye-ignore

2021-08-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # We're getting very close to the bullseye release. Although we'd > # (still) love to have these bugs fixed, let's focus on what absolutely > # needs fixing. > # I'm considering adding a release-notes section about some/most of > # these bugs > us

Processed: forcibly merging 991344 991770

2021-08-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 991344 991770 Bug #991344 [src:umatrix] umatrix: CVE-2021-36773: Denial of Service Bug #991770 [src:umatrix] umatrix: new upstream release (1.4.4) fixes security issue Severity set to 'grave' from 'wishlist' Added tag(s) upstream. Merg

Bug#991006: marked as done (openjdk-11-jre-dcevm: autopkgtest broken by openjdk-11 in unstable)

2021-08-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Aug 2021 13:48:52 + with message-id and subject line Bug#991006: fixed in openjdk-11-jre-dcevm 11.0.12+7-1 has caused the Debian Bug report #991006, regarding openjdk-11-jre-dcevm: autopkgtest broken by openjdk-11 in unstable to be marked as done. This means that yo

Bug#991006: marked as pending in openjdk-11-jre-dcevm

2021-08-01 Thread Emmanuel Bourg
Control: tag -1 pending Hello, Bug #991006 in openjdk-11-jre-dcevm 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/java-team/openjdk-11-jre-dcevm/-/commit/9ccd8

Processed: Bug#991006 marked as pending in openjdk-11-jre-dcevm

2021-08-01 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #991006 [src:openjdk-11-jre-dcevm] openjdk-11-jre-dcevm: autopkgtest broken by openjdk-11 in unstable Added tag(s) pending. -- 991006: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991006 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#989296: marked as done (missing dependencies and wrong path in the .cmake file)

2021-08-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Aug 2021 13:03:27 + with message-id and subject line Bug#989296: fixed in gdcm 3.0.8-2 has caused the Debian Bug report #989296, regarding missing dependencies and wrong path in the .cmake file to be marked as done. This means that you claim that the problem has bee

Bug#989289: marked as done (libpmix-dev: Should depend on libevent-dev)

2021-08-01 Thread Debian Bug Tracking System
Your message dated Sun, 01 Aug 2021 09:48:23 + with message-id and subject line Bug#989289: fixed in pmix 4.0.0-4.1 has caused the Debian Bug report #989289, regarding libpmix-dev: Should depend on libevent-dev to be marked as done. This means that you claim that the problem has been dealt wi

Bug#989289: pmix: diff for NMU version 4.0.0-4.1

2021-08-01 Thread Sebastian Ramacher
Dear maintainer, I've prepared an NMU for pmix (versioned as 4.0.0-4.1). The diff is attached to this message. Cheers -- Sebastian Ramacher diff -Nru pmix-4.0.0/debian/changelog pmix-4.0.0/debian/changelog --- pmix-4.0.0/debian/changelog 2021-01-20 18:30:05.0 +0100 +++ pmix-4.0.0/debian/

Processed: tagging 990345

2021-08-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # secrity issues that can be fixed later via a DSA > tags 990345 + bullseye-ignore Bug #990345 [src:zookeeper] zookeeper: various security issues Added tag(s) bullseye-ignore. > thanks Stopping processing here. Please contact me if you need assis