Bug#985040: qemu-system-data: too tight dependencies breaking on binNMUs

2021-03-11 Thread Sven Joachim
Package: qemu-system-data Version: 1:5.2+dfsg-6 Severity: serious The fix for #956377 has made the latest binNMU of qemu-system-x86 uninstallable: , | $ LANG=C apt -s install qemu-system-x86 | NOTE: This is only a simulation! | apt needs root privileges for real execution. | Keep

Bug#985004: gemma: flaky armhf autopkgtest: regularly times out after 2:47 h

2021-03-11 Thread Andreas Tille
Hi, I recommend to remove armhf from the list of architectures. This kind of software is possibly not used on armhf and upstream (in CC) will probably confirm this. Kind regards Andreas. On Thu, Mar 11, 2021 at 09:08:15PM +0100, Paul Gevers wrote: > Source: gemma > Version: 0.98.3+dfsg-1 >

Bug#983775: marked as done (libgrokj2k: Baseline violation on amd64/i386)

2021-03-11 Thread Debian Bug Tracking System
Your message dated Fri, 12 Mar 2021 04:03:26 + with message-id and subject line Bug#983775: fixed in libgrokj2k 7.6.6-2 has caused the Debian Bug report #983775, regarding libgrokj2k: Baseline violation on amd64/i386 to be marked as done. This means that you claim that the problem has been

Bug#983873: retroarch: Menu freezes shortly after start

2021-03-11 Thread Ryan Tandy
Control: tag -1 moreinfo Hello Pelle and thank you for reporting this retroarch issue. On Tue, 02 Mar 2021 16:10:32 +0100 Pelle wrote: When launching RetroArch, the menu freezes up instantly or after a couple of seconds. This isn't happening on my system. I can use the menu normally, launch

Processed: Re: retroarch: Menu freezes shortly after start

2021-03-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo Bug #983873 [retroarch] retroarch: Menu freezes shortly after start Added tag(s) moreinfo. -- 983873: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=983873 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#985033: debian/copyright is not up-to-date: coderay seems to have been relicensed under MIT license

2021-03-11 Thread Daniel Leidert
Source: coderay Version: 1.1.3-3 Severity: serious -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 It seem the coderay sources are now licensed under the MIT license and not under the LGPL license. debian/copyright seems to be outdated and wrong here. Regards, Daniel - -- System Information:

Bug#985004: gemma: flaky armhf autopkgtest: regularly times out after 2:47 h

2021-03-11 Thread Paul Gevers
Source: gemma Version: 0.98.3+dfsg-1 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), Your package has an autopkgtest, great. However, I looked into the history of your autopkgtest [1,2] and I

Processed: dkms now exports CC=

2021-03-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #984862 [iptables-netflow-dkms] iptables-netflow-dkms: module wants to build with gcc instead of kernel's compiler Severity set to 'important' from 'serious' -- 984862: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984862 Debian Bug

Processed: dkms now exports CC=

2021-03-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #945506 [openafs-modules-dkms] openafs-modules-dkms: module wants to build with gcc instead of kernel's compiler Severity set to 'important' from 'serious' -- 945506: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945506 Debian Bug

Bug#945506: dkms now exports CC=

2021-03-11 Thread Andreas Beckmann
Control: severity -1 important I've just added a patch to dkms to export the kernel compiler used for the headers as CC and the module build system automatically picks it up and therefore uses the "correct" compiler for the module. I'll attempt to get this unblocked for bullseye. Therefore

Bug#984962: marked as done (openmpi-bin: broken symlink: /usr/bin/mpijavac -> mpijavac.pl)

2021-03-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Mar 2021 19:33:23 + with message-id and subject line Bug#984962: fixed in openmpi 4.1.0-8 has caused the Debian Bug report #984962, regarding openmpi-bin: broken symlink: /usr/bin/mpijavac -> mpijavac.pl to be marked as done. This means that you claim that the

Bug#984931: git-el,elpa-magit: fails to install: /usr/lib/emacsen-common/packages/install/git emacs failed at /usr/lib/emacsen-common/lib.pl line 19, line 7.

2021-03-11 Thread David Bremner
David Bremner writes: > > As far as I can see, the problem is that the setup for elpa-magit and > git-el both call "emacs", but that does not exist until the > update-alternatives is called. So there seems to be a race condition > here where emacs-gtk (or whatever is providing /usr/bin/emacs)

Bug#983610: zint: CVE-2021-27799

2021-03-11 Thread Gunnar Wolf
tags -1 + patch,pending user debian-rele...@lists.debian.org usertags -1 + bsp-2021-03-latinoamerica thank you Hi, I have prepared this patch and will be performing an upload targetted at delayed/7-day. Dmitry, please do take a look at my proposed patch. I backported the commit I'm quoting in

Processed: Re: Bug#984859: CVE-2021-21381: flatpak: sandbox escape via special tokens in .desktop file (flatpak#4146)

2021-03-11 Thread Debian Bug Tracking System
Processing control commands: > retitle -1 CVE-2021-21381: flatpak: sandbox escape via special tokens in > .desktop file (flatpak#4146) Bug #984859 {Done: Simon McVittie } [flatpak] flatpak: sandbox escape via special tokens in .desktop file (flatpak#4146) Changed Bug title to 'CVE-2021-21381:

Bug#984859: CVE-2021-21381: flatpak: sandbox escape via special tokens in .desktop file (flatpak#4146)

2021-03-11 Thread Simon McVittie
Control: retitle -1 CVE-2021-21381: flatpak: sandbox escape via special tokens in .desktop file (flatpak#4146) On Tue, 09 Mar 2021 at 10:11:09 +, Simon McVittie wrote: > flatpak since 0.9.4 has a bug in the "file forwarding" feature, which can > be used by an attacker to gain access to files

Bug#984980: marked as done (libaqbanking44: Wrong message after sending an transaction)

2021-03-11 Thread Debian Bug Tracking System
Your message dated Thu, 11 Mar 2021 17:42:10 +0100 with message-id and subject line Re: Bug#984980: libaqbanking44: Wrong message after sending an transaction has caused the Debian Bug report #984980, regarding libaqbanking44: Wrong message after sending an transaction to be marked as done.

Processed (with 1 error): Set fixVersion

2021-03-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 984980 libaqbanking/6.2.9-1 Bug #984980 [libaqbanking44] libaqbanking44: Wrong message after sending an transaction Marked as found in versions libaqbanking/6.2.9-1. > done Unknown command or malformed arguments to command. > End of

Bug#979563: gitlab: my instance work great after upgrade to 13.5.6.1!

2021-03-11 Thread Pirate Praveen
On Mon, 11 Jan 2021 18:10:34 +0200 Dragos Jarca wrote: > Just to know, in previous version I have some trouble with licensee, and > I do the following to solve the problem: > > gitaly(13.4.6+dfsg1-2) and gitlab(13.4.7-2) have in Gemfile: > > gem 'rugged', '~> 0.28' > ... > gem 'licensee', '~>

Processed: Re: Bug#984980: libaqbanking44: Wrong message after sending an transaction

2021-03-11 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libaqbanking44 Bug #984980 [libaqbaning44] libaqbanking44: Wrong message after sending an transaction Warning: Unknown package 'libaqbaning44' Bug reassigned from package 'libaqbaning44' to 'libaqbanking44'. No longer marked as found in versions

Bug#984980: libaqbanking44: Wrong message after sending an transaction

2021-03-11 Thread Andrei POPESCU
Control: reassign -1 libaqbanking44 On Jo, 11 mar 21, 15:17:15, Mechtilde Stehmann wrote: > Package: libaqbaning44 > Version: 6.2.9-1 > severity: grave > > I get the message the transaction failed after entering PIN and TAN but > the transaction was executed. > > Upstream has already fixed it

Processed: Re: pre-approval: updating python-networkmanager to 2.2 (bugfix release) in bullseye

2021-03-11 Thread Debian Bug Tracking System
Processing control commands: > block 984983 by 984925 Bug #984983 [python3-networkmanager] python3-networkmanager: crashes on unknown device types (eg. wifi p2p) in >=bullseye 984983 was not blocked by any bugs. 984983 was not blocking any bugs. Added blocking bug(s) of 984983: 984925 --

Bug#983533: [vinagre] black screen when launching RDP session

2021-03-11 Thread Paul Gevers
Hi all, On Mon, 8 Mar 2021 13:04:07 + Simon McVittie wrote: > On Thu, 25 Feb 2021 at 19:04:49 +, Mike Gabriel wrote: > > I saw from other open > > bugs that vinagre upstream is scarcely maintained. Does it make sense to > > ship vinagre in Debian 11? > > I suspect there are people

Processed: tagging 984984

2021-03-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 984984 + pending Bug #984984 [src:hwloc-contrib] hwloc-contrib: FTBFS with latest nvidia-alternative Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 984984:

Bug#984984: hwloc-contrib: FTBFS with latest nvidia-alternative

2021-03-11 Thread Samuel Thibault
Source: hwloc-contrib Version: 2.4.1+dfsg-1 Severity: serious Justification: FTBFS With the new nvidia-alternative package which fixed shipping libnvidia-ml.so (see #984881), hwloc-contrib now FTBFS: dh_missing -a dh_missing: warning: usr/lib/x86_64-linux-gnu/hwloc/hwloc_nvml.so exists in

Bug#984983: python3-networkmanager: crashes on unknown device types (eg. wifi p2p) in >=bullseye

2021-03-11 Thread Andreas Henriksson
Package: python3-networkmanager Version: 2.1-2 Severity: serious Justification: Incompatibility with bullseye NM causes crashes enumerating devices etc. Dear Maintainer, I'm experiencing python3-networkmanager crashing with a simple test program like this: $ cat /tmp/test.py #!/usr/bin/python3

Bug#984982: plexus-languages: Build-Depends on no longer available libsisu-maven-plugin-java

2021-03-11 Thread Andreas Beckmann
Source: plexus-languages Version: 1.0.3-1 Severity: serious Tags: ftbfs Justification: fails to build from source User: debian...@lists.debian.org Usertags: piuparts plexus-languages/experimental Build-Depends on libsisu-maven-plugin-java which has been removed from sid. Andreas

Bug#984980: libaqbanking44: Wrong message after sending an transaction

2021-03-11 Thread Mechtilde Stehmann
Package: libaqbaning44 Version: 6.2.9-1 severity: grave I get the message the transaction failed after entering PIN and TAN but the transaction was executed. Upstream has already fixed it in version 6.2.10 -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy:

Processed: Bug#984966 marked as pending in apt

2021-03-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #984966 [src:apt] apt: flaky armhf autopkgtest: File has unexpected size (27 != 39). Mirror sync in progress? Added tag(s) pending. -- 984966: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984966 Debian Bug Tracking System Contact

Bug#984966: marked as pending in apt

2021-03-11 Thread David Kalnischkies
Control: tag -1 pending Hello, Bug #984966 in apt 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#984931: git-el,elpa-magit: fails to install: /usr/lib/emacsen-common/packages/install/git emacs failed at /usr/lib/emacsen-common/lib.pl line 19, line 7.

2021-03-11 Thread David Bremner
Andreas Beckmann writes: > Install git for emacs > install/git: Handling install of emacsen flavor emacs > install/git: Byte-compiling for emacs > + emacs -batch -q -no-site-file -f batch-byte-compile git.el git-blame.el > /usr/lib/emacsen-common/packages/install/git: 26: emacs: not

Processed: Re: Bug#984479: RFH

2021-03-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #984479 [fai-nfsroot] fai-nfsroot: fails to upgrade from 'buster': diversion clash Added tag(s) patch. -- 984479: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=984479 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#984479: RFH

2021-03-11 Thread Andreas Beckmann
Control: tag -1 patch On 07/03/2021 16.23, Thomas Lange wrote: You need to manually migrate the existing diversion to the new name. Can you please point me to examples how to do this? The attached patch fixes the buster->bullseye upgrade for me. Andreas >From

Bug#962921: Please fix spam for bullseye

2021-03-11 Thread Tiago Bortoletto Vaz
Hi, I'll have it done this weekend, thanks for reporting! Bests, On Tue, Mar 09, 2021 at 09:30:27AM -0800, Felix Lechner wrote: > Dear maintainer, > > The release team will accept this patch for bullseye. They raised the > bug status to "serious" after I asked on your behalf. Please upload a >

Bug#951988: libplacebo: FTBFS: (.text+0x8ee): undefined reference to `spvContextCreate'

2021-03-11 Thread Paul Gevers
Hi Simon, all, On Thu, 18 Feb 2021 10:26:44 + Simon McVittie wrote: > On Mon, 18 Jan 2021 at 11:27:35 +, Simon McVittie wrote: > > On Mon, 18 Jan 2021 at 10:54:30 +, Simon McVittie wrote: > > > Unfortunately, unlike #980369, I was not able to find a combination of > > > libraries

Bug#922981: tagging 922981 (ca-certificates-java: /etc/ca-certificates/update.d/jks-keystore doesn't update /etc/ssl/certs/java/cacerts)

2021-03-11 Thread Paul Gevers
Hi Andreas, On Tue, 23 Feb 2021 15:28:07 +0100 Andreas Beckmann wrote: > tags 922981 + pending - moreinfo > thanks Is it possible that we get this uploaded soon? If you have the fix ready, it would be good to have it sooner rather than later as we're in the freeze, so it gets a bit of exposure.

Bug#984966: apt: flaky armhf autopkgtest: File has unexpected size (27 != 39). Mirror sync in progress?

2021-03-11 Thread Paul Gevers
Source: apt Version: 2.2.0 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, sebast...@breakpoint.cc User: debian...@lists.debian.org Usertags: flaky Dear maintainer(s), Your package has an autopkgtest, great. However, it fails often on armhf [1]. Because the unstable-to-testing