Bug#988632: audacity: The main drawing area (sound wave) do not refresh

Package: audacity Version: 2.4.2~dfsg0-4 Severity: grave Tags: newcomer Justification: renders package unusable X-Debbugs-Cc: poming...@gmail.com Hello, I've just install audacity 2.4.2~dfsg0-4. However, it is not useful since the drawing area (the sound wave display) does not refresh. To be more

Bug#988428: marked as done (mariadb-10.5: CVE-2021-2154 CVE-2021-2166)

Your message dated Mon, 17 May 2021 03:03:45 + with message-id and subject line Bug#988428: fixed in mariadb-10.5 1:10.5.10-1 has caused the Debian Bug report #988428, regarding mariadb-10.5: CVE-2021-2154 CVE-2021-2166 to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#988217: bootefi causes boot failure with boot.scr

Processing control commands: > severity 988217 serious Bug #988217 [u-boot-sunxi] bootefi causes boot failure with boot.scr Severity set to 'serious' from 'important' -- 988217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988217 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 985142 89.0.4389.114-1~deb10u1 Bug #985142 {Done: Michel Le Bihan } [chromium] chromium: CVE-2021-21193 (RCE) in Blink Marked as fixed in versions chromium/89.0.4389.114-1~deb10u1. > fixed 987358 90.0.4430.85-1~deb10u1 Bug #987358 {Done: Mi

Bug#988562: marked as done (Fails to build due to unspecified debhelper compatibility level)

Your message dated Sun, 16 May 2021 23:18:31 + with message-id and subject line Bug#988562: fixed in broadcom-sta 6.30.223.271-16.1 has caused the Debian Bug report #988562, regarding Fails to build due to unspecified debhelper compatibility level to be marked as done. This means that you cla

Bug#988562: broadcom-sta: diff for NMU version 6.30.223.271-16.1

Control: tags 988562 + patch Control: tags 988562 + pending Dear maintainer, I've prepared an NMU for broadcom-sta (versioned as 6.30.223.271-16.1) and uploaded it. The changes are attached as a debdiff, but you can also merge the "debian" branch of

Processed: broadcom-sta: diff for NMU version 6.30.223.271-16.1

Processing control commands: > tags 988562 + patch Bug #988562 [broadcom-sta-source] Fails to build due to unspecified debhelper compatibility level Added tag(s) patch. > tags 988562 + pending Bug #988562 [broadcom-sta-source] Fails to build due to unspecified debhelper compatibility level Added

Bug#988558: marked as done (Fails to build against Linux version 5.3+)

Your message dated Sun, 16 May 2021 23:04:03 + with message-id and subject line Bug#988558: fixed in leds-alix 0.0.1-1.3 has caused the Debian Bug report #988558, regarding Fails to build against Linux version 5.3+ to be marked as done. This means that you claim that the problem has been deal

Bug#988564: marked as done (Fails to build for Linux 5.6+)

Your message dated Sun, 16 May 2021 22:51:16 + with message-id and subject line Bug#988564: fixed in vpb-driver 4.2.61-1.2 has caused the Debian Bug report #988564, regarding Fails to build for Linux 5.6+ to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: leds-alix: diff for NMU version 0.0.1-1.3

Processing control commands: > tags 988558 + pending Bug #988558 [src:leds-alix] Fails to build against Linux version 5.3+ Added tag(s) pending. -- 988558: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988558 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#988558: leds-alix: diff for NMU version 0.0.1-1.3

Control: tags 988558 + pending Dear maintainer, I've prepared an NMU for leds-alix (versioned as 0.0.1-1.3) and uploaded it. Ben. -- Ben Hutchings Never attribute to conspiracy what can adequately be explained by stupidity. diff -u leds-alix-0.0.1/debian/changelog leds-alix-0.0.1/debian/change

Bug#987537: RM: scrollz -- RoQA unmaintained, dead upstream, has security issues

On Mon, May 03, 2021 at 07:58:06AM +0200, Tobias Frost wrote: > I just gave upstream a pointer to the ircii code that fixes this CVE. Maybe > they have tested it? I reached out via email yesterday and I'm awaiting a response. > (MIA Team hat partly on) That sounds a bit like the package should b

Bug#983533: marked as done ([vinagre] black screen when launching RDP session)

Your message dated Sun, 16 May 2021 21:33:30 + with message-id and subject line Bug#983533: fixed in vinagre 3.22.0-8.1 has caused the Debian Bug report #983533, regarding [vinagre] black screen when launching RDP session to be marked as done. This means that you claim that the problem has be

Bug#988604: plocate: autopkgtest regression: plocate and mlocate can't be co-installed anymore

On Sun, May 16, 2021 at 10:46:30PM +0200, Paul Gevers wrote: >> Thanks for noticing. Given how annoying everything in autopkgtest is, >> perhaps the easiest thing is just deleting the tests. (1.1.7-3 wouldn't >> migrate to bullseye, then, but that's fine.) > As it stands, you'd only need to remove

Bug#988604: plocate: autopkgtest regression: plocate and mlocate can't be co-installed anymore

Hi Steinar, On 16-05-2021 21:41, Steinar H. Gunderson wrote: > On Sun, May 16, 2021 at 09:17:57PM +0200, Paul Gevers wrote: >> With a recent upload of plocate the autopkgtest of plocate fails in >> testing when that autopkgtest is run with the binary packages of plocate >> from unstable. It passes

Bug#988604: plocate: autopkgtest regression: plocate and mlocate can't be co-installed anymore

On Sun, May 16, 2021 at 09:17:57PM +0200, Paul Gevers wrote: > With a recent upload of plocate the autopkgtest of plocate fails in > testing when that autopkgtest is run with the binary packages of plocate > from unstable. It passes when run with only packages from testing. In > tabular form: Than

Bug#986012: marked as done (fatrace: autopkgtest regression: ^rm(.*): D /tmp/autopkgtest-lxc.yky1gevw/downtmp/build.jzI/src$ not found in log)

Your message dated Sun, 16 May 2021 19:18:30 + with message-id and subject line Bug#986012: fixed in fatrace 0.16.2-2 has caused the Debian Bug report #986012, regarding fatrace: autopkgtest regression: ^rm(.*): D /tmp/autopkgtest-lxc.yky1gevw/downtmp/build.jzI/src$ not found in log to be mar

Bug#988604: plocate: autopkgtest regression: plocate and mlocate can't be co-installed anymore

Source: plocate Version: 1.1.7-2 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of plocate the autopkgtest of plocate fails in testing when that autopkgtest is run with the binary packages o

Bug#986012: fatrace: autopkgtest regression: ^rm(.*): D /tmp/autopkgtest-lxc.yky1gevw/downtmp/build.jzI/src$ not found in log

Control: tag -1 pending Paul Gevers [2021-03-27 21:43 +0100]: > https://ci.debian.net/data/autopkgtest/testing/amd64/f/fatrace/11288159/log.gz > > autopkgtest [23:08:44]: test fatrace-currentmount: [--- > ^rm(.*): D /tmp/autopkgtest-lxc.yky1gevw/downtmp/build.jzI/src$ not > fo

Processed: Re: Bug#986012: fatrace: autopkgtest regression: ^rm(.*): D /tmp/autopkgtest-lxc.yky1gevw/downtmp/build.jzI/src$ not found in log

Processing control commands: > tag -1 pending Bug #986012 [src:fatrace] fatrace: autopkgtest regression: ^rm(.*): D /tmp/autopkgtest-lxc.yky1gevw/downtmp/build.jzI/src$ not found in log Added tag(s) pending. -- 986012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986012 Debian Bug Tracking

Bug#988565: marked as done (slapd-contrib: smbk5pwd crashes when enabling krb5 (again))

Your message dated Sun, 16 May 2021 17:48:28 + with message-id and subject line Bug#988565: fixed in openldap 2.4.57+dfsg-3 has caused the Debian Bug report #988565, regarding slapd-contrib: smbk5pwd crashes when enabling krb5 (again) to be marked as done. This means that you claim that the p

Bug#975270: rdiff-backup: Can't talk to the version from buster

Hello, Gregor Zattler, le dim. 16 mai 2021 18:50:42 +0200, a ecrit: > * Samuel Thibault [13. Mai. 2021]: > > Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit: > >> I recently found out that my backup has broken for months. > > > > Not for month, but this does break my backups now that I

Bug#975270: rdiff-backup: Can't talk to the version from buster

Hi Samuel, debian developers, * Samuel Thibault [13. Mai. 2021]: > Control: severity -1 serious > > Kurt Roeckx, le jeu. 19 nov. 2020 20:40:05 +0100, a ecrit: >> I recently found out that my backup has broken for months. > > Not for month, but this does break my backups now that I try to upgrade >

Bug#987353: CVE-2020-8903 CVE-2020-8907 CVE-2020-8933

On Thu, May 13, 2021 at 09:56:53PM +0100, Marcin Kulisz wrote: > > I hope that we're be able to change it, but for me fundamental > question is if Google is interested in participating in effort to > keep those packages in Debian main and if so what resources can be > committed to do so. From my

Bug#988326: marked as done (libboost-python-dev: Linking against boost_python requires the python version number ex: -lboost_python39)

Your message dated Sun, 16 May 2021 17:14:46 +0200 with message-id and subject line Re: Bug#988326: libboost-python-dev: Linking against boost_python requires the python version number ex: -lboost_python39 has caused the Debian Bug report #988326, regarding libboost-python-dev: Linking against b

Bug#988326: libboost-python-dev: Linking against boost_python requires the python version number ex: -lboost_python39

Control: tags -1 wontfix Hi, I am closing this bug. See an explanation above. Best regards Anton

Processed: Re: Bug#988326: libboost-python-dev: Linking against boost_python requires the python version number ex: -lboost_python39

Processing control commands: > tags -1 wontfix Bug #988326 [libboost-python-dev] libboost-python-dev: Linking against boost_python requires the python version number ex: -lboost_python39 Added tag(s) wontfix. -- 988326: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988326 Debian Bug Trackin

Processed: bug 983515 is forwarded to https://gitlab.gnome.org/World/OpenPaperwork/paperwork/-/issues/981

Processing commands for cont...@bugs.debian.org: > forwarded 983515 > https://gitlab.gnome.org/World/OpenPaperwork/paperwork/-/issues/981 Bug #983515 [src:paperwork] paperwork: autopkgtest armhf regression: Libinsane item->get_options() error: 0x4006, I/O Error (7) Set Bug forwarded-to-addre

Bug#986293: virtuoso-opensource: diff for NMU version 7.2.5.1+dfsg-3.1

Control: tags 982569 + pending Control: tags 982628 + pending Control: tags 983414 + pending Control: tags 986293 + patch Control: tags 986293 + pending Dear maintainer, I've prepared an NMU for virtuoso-opensource (versioned as 7.2.5.1+dfsg-3.1) and uploaded it to DELAYED/7. Please feel free to

Processed: virtuoso-opensource: diff for NMU version 7.2.5.1+dfsg-3.1

Processing control commands: > tags 982569 + pending Bug #982569 [virtuoso-opensource] virtuoso-opensource: [INTL:pt] Updated Portuguese translation - debconf messages Ignoring request to alter tags of bug #982569 to the same tags previously set > tags 982628 + pending Bug #982628 [virtuoso-opens

Processed: virtuoso-opensource: diff for NMU version 7.2.5.1+dfsg-3.1

Processing control commands: > tags 982569 + pending Bug #982569 [virtuoso-opensource] virtuoso-opensource: [INTL:pt] Updated Portuguese translation - debconf messages Ignoring request to alter tags of bug #982569 to the same tags previously set > tags 982628 + pending Bug #982628 [virtuoso-opens

Processed: virtuoso-opensource: diff for NMU version 7.2.5.1+dfsg-3.1

Processing control commands: > tags 982569 + pending Bug #982569 [virtuoso-opensource] virtuoso-opensource: [INTL:pt] Updated Portuguese translation - debconf messages Ignoring request to alter tags of bug #982569 to the same tags previously set > tags 982628 + pending Bug #982628 [virtuoso-opens

Processed: virtuoso-opensource: diff for NMU version 7.2.5.1+dfsg-3.1

Processing control commands: > tags 982569 + pending Bug #982569 [virtuoso-opensource] virtuoso-opensource: [INTL:pt] Updated Portuguese translation - debconf messages Added tag(s) pending. > tags 982628 + pending Bug #982628 [virtuoso-opensource] virtuoso-opensource: [INTL:de] updated German de

Bug#952067: marked as done (hpcc: FTBFS: mpi.h:322:57: error: expected expression before ‘_Static_assert’)

Your message dated Sun, 16 May 2021 13:18:38 + with message-id and subject line Bug#952067: fixed in hpcc 1.5.0-2.1 has caused the Debian Bug report #952067, regarding hpcc: FTBFS: mpi.h:322:57: error: expected expression before ‘_Static_assert’ to be marked as done. This means that you clai

Bug#988584: manpages-hu: Contains undistributable content - All rights reserved

Hello, Helge Kreutzmann schrieb am So., 16. Mai 2021, 12:27: > Package: manpages-hu > Version: 20010119-7 > Severity: serious > Justification: Policy 2.3 > X-Debbugs-Cc: Mario Blättermann > > Short: > man8/ssh.8 states: > .\" Copyright (c) 1995 Tatu Ylonen , Espoo, Finland > .\"

Processed: Re: Bug#988583: elpa-debian-el: Cannot report any bugs at all. It is broken.

Processing control commands: > tag -1 unreproducible Bug #988583 [elpa-debian-el] elpa-debian-el: Cannot report any bugs at all. It is broken. Added tag(s) unreproducible. > severity -1 normal Bug #988583 [elpa-debian-el] elpa-debian-el: Cannot report any bugs at all. It is broken. Severity se

Bug#988583: elpa-debian-el: Cannot report any bugs at all. It is broken.

Control: tag -1 unreproducible Control: severity -1 normal Salman Mohammadi writes: > Package: elpa-debian-el > Version: 37.10 > Severity: grave > Justification: renders package unusable > X-Debbugs-Cc: sal...@smoha.org > > Dear Maintainer, > > I cannot report any bugs using M-x debian-bug at al

Bug#988249: marked as done (golang-github-getkin-kin-openapi: flaky autopkgtest: output order changed)

Your message dated Sun, 16 May 2021 10:48:34 + with message-id and subject line Bug#988249: fixed in golang-github-getkin-kin-openapi 0.32.0-2 has caused the Debian Bug report #988249, regarding golang-github-getkin-kin-openapi: flaky autopkgtest: output order changed to be marked as done. T

Processed: Bug#988249 marked as pending in golang-github-getkin-kin-openapi

Processing control commands: > tag -1 pending Bug #988249 [src:golang-github-getkin-kin-openapi] golang-github-getkin-kin-openapi: flaky autopkgtest: output order changed Added tag(s) pending. -- 988249: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988249 Debian Bug Tracking System Contact

Bug#988249: marked as pending in golang-github-getkin-kin-openapi

Control: tag -1 pending Hello, Bug #988249 in golang-github-getkin-kin-openapi 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/go-team/packages/golang-github-g

Processed: bug 988249 is forwarded to https://github.com/getkin/kin-openapi/pull/278

Processing commands for cont...@bugs.debian.org: > forwarded 988249 https://github.com/getkin/kin-openapi/pull/278 Bug #988249 [src:golang-github-getkin-kin-openapi] golang-github-getkin-kin-openapi: flaky autopkgtest: output order changed Set Bug forwarded-to-address to 'https://github.com/getk

Bug#988584: manpages-hu: Contains undistributable content - All rights reserved

Package: manpages-hu Version: 20010119-7 Severity: serious Justification: Policy 2.3 X-Debbugs-Cc: Mario Blättermann Short: man8/ssh.8 states: .\" Copyright (c) 1995 Tatu Ylonen , Espoo, Finland .\"All rights reserved Long: The copyright situation is very unclear. I reviewed

Bug#988583: elpa-debian-el: Cannot report any bugs at all. It is broken.

Package: elpa-debian-el Version: 37.10 Severity: grave Justification: renders package unusable X-Debbugs-Cc: sal...@smoha.org Dear Maintainer, I cannot report any bugs using M-x debian-bug at all. After entering the bug summary, I get the following error message, and cannot correctly reach the pa

Bug#988243: marked as done (golang-github-ulikunitz-xz: CVE-2021-29482)

Your message dated Sun, 16 May 2021 09:18:29 + with message-id and subject line Bug#988243: fixed in golang-github-ulikunitz-xz 0.5.6-2 has caused the Debian Bug report #988243, regarding golang-github-ulikunitz-xz: CVE-2021-29482 to be marked as done. This means that you claim that the probl

Processed: Bug#988243 marked as pending in golang-github-ulikunitz-xz

Processing control commands: > tag -1 pending Bug #988243 [src:golang-github-ulikunitz-xz] golang-github-ulikunitz-xz: CVE-2021-29482 Added tag(s) pending. -- 988243: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988243 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#988243: marked as pending in golang-github-ulikunitz-xz

Control: tag -1 pending Hello, Bug #988243 in golang-github-ulikunitz-xz 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/go-team/packages/golang-github-ulikunit