Processed: Re: Bug#970009: libreoffice: Libreoffice crashes when dragged into extended monitor then clicked

2020-09-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 970009 important Bug #970009 [libreoffice] libreoffice: Libreoffice crashes when dragged into extended monitor then clicked Severity set to 'important' from 'serious' > tag 970009 + moreinfo Bug #970009 [libreoffice] libreoffice: Libreof

Bug#970009: libreoffice: Libreoffice crashes when dragged into extended monitor then clicked

2020-09-09 Thread Rene Engelhard
severity 970009 important tag 970009 + moreinfo tag 970009 + unreproducible thanks Am 10.09.20 um 06:30 schrieb hyiltiz: > Package: libreoffice > Version: 1:7.0.1-1+b1 > Severity: serious Nonsense. It's not a RC bug and no policy violation. Please use proper bug severities. > This has alre

Bug#970009: libreoffice: Libreoffice crashes when dragged into extended monitor then clicked

2020-09-09 Thread hyiltiz
Package: libreoffice Version: 1:7.0.1-1+b1 Severity: serious Tags: upstream Justification: usability X-Debbugs-Cc: hyil...@gmail.com This has already been patched in upstream in version 7.1.0. Please upgrade that version as current version makes the working environment completely unstable. https:

Bug#969894: nvidia-legacy-390xx-driver: X will not start with nvidia-legacy-390.xx driver and 5.8 kernel

2020-09-09 Thread Jiri Kanicky
This issue has been resolved with new nvidia-kernel-dkms version 450.66-1 -- Jiri

Bug#969848: marked as done (myrescue: autopkgtest should be marked superficial)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Thu, 10 Sep 2020 02:23:58 + with message-id and subject line Bug#969848: fixed in myrescue 0.9.8-3 has caused the Debian Bug report #969848, regarding myrescue: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has bee

Processed: Bug#969848 marked as pending in myrescue

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #969848 [src:myrescue] myrescue: autopkgtest should be marked superficial Added tag(s) pending. -- 969848: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969848 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#969848: marked as pending in myrescue

2020-09-09 Thread Giovani Augusto Ferreira
Control: tag -1 pending Hello, Bug #969848 in myrescue 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/pkg-security-team/myrescue/-/commit/b4703fcb08ba4c8c1fe77

Bug#965298: marked as done (gst-plugins-bad1.0 cannot be built in testing.)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Thu, 10 Sep 2020 02:26:51 +0100 with message-id <0f7c4056-f8c9-c5e2-d5d2-7bdd36aaf...@p10link.net> and subject line re: gst-plugins-bad1.0 cannot be built in testing. has caused the Debian Bug report #965298, regarding gst-plugins-bad1.0 cannot be built in testing. to be marked a

Bug#962725: marked as done (gst-plugins-bad1.0: depend on cruft package libsrt-dev)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Thu, 10 Sep 2020 02:22:43 +0100 with message-id and subject line re: gst-plugins-bad1.0: depend on cruft package libsrt-dev has caused the Debian Bug report #962725, regarding gst-plugins-bad1.0: depend on cruft package libsrt-dev to be marked as done. This means that you claim

Bug#968993: marked as done (lilypond: CVE-2020-17353)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Thu, 10 Sep 2020 01:04:31 + with message-id and subject line Bug#968993: fixed in lilypond 2.20.0-2 has caused the Debian Bug report #968993, regarding lilypond: CVE-2020-17353 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#966353: marked as done (FTBFS: guile segfaults when run to collect docs)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Thu, 10 Sep 2020 01:04:31 + with message-id and subject line Bug#966353: fixed in lilypond 2.20.0-2 has caused the Debian Bug report #966353, regarding FTBFS: guile segfaults when run to collect docs to be marked as done. This means that you claim that the problem has been

Bug#969845: marked as done (missidentify: autopkgtest should be marked superficial)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Thu, 10 Sep 2020 00:49:06 + with message-id and subject line Bug#969845: fixed in missidentify 1.0-11 has caused the Debian Bug report #969845, regarding missidentify: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem

Bug#969845: marked as pending in missidentify

2020-09-09 Thread Giovani Augusto Ferreira
Control: tag -1 pending Hello, Bug #969845 in missidentify 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/pkg-security-team/missidentify/-/commit/4cccf3d0d31fc

Processed: Bug#969845 marked as pending in missidentify

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #969845 [src:missidentify] missidentify: autopkgtest should be marked superficial Added tag(s) pending. -- 969845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969845 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#966982: marked as done (wand: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Thu, 10 Sep 2020 00:04:24 + with message-id and subject line Bug#966982: fixed in wand 0.6.2-1 has caused the Debian Bug report #966982, regarding wand: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 to be marked as

Bug#966982: Uploading disabling that test to DELAYED/2

2020-09-09 Thread Thomas Goirand
On 9/9/20 2:57 PM, Håvard Flaget Aasen wrote: > On Tue, 8 Sep 2020 16:27:20 +0200 Thomas Goirand wrote: >> On 9/8/20 2:01 PM, Håvard Flaget Aasen wrote: >>> On Tue, 8 Sep 2020 13:40:25 +0200 Thomas Goirand wrote: Hi, Since nobody seem to care about this, I've uploaded disabling tha

Bug#969803: marked as done (awscli: autopkgtest should be marked superficial)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Sep 2020 23:18:29 + with message-id and subject line Bug#969803: fixed in awscli 1.18.135-1 has caused the Debian Bug report #969803, regarding awscli: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has been

Processed: Bug#969803 marked as pending in awscli

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #969803 [src:awscli] awscli: autopkgtest should be marked superficial Added tag(s) pending. -- 969803: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969803 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#969803: marked as pending in awscli

2020-09-09 Thread Noah Meyerhans
Control: tag -1 pending Hello, Bug #969803 in awscli 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/cloud-team/awscli/-/commit/4520ece3337f4e73d5323651fd1c453c

Processed: your mail

2020-09-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 968884 20.08.1-1 Bug #968884 [src:elisa-player] elisa-player FTBFS: elisaqmltests (Failed) The source 'elisa-player' and version '20.08.1-1' do not appear to match any binary packages Marked as fixed in versions elisa-player/20.08.1-1. > En

Processed: retitle 969768 to libio-socket-ip-perl: do not release with bullseye

2020-09-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Fix typo in package name in bug title > retitle 969768 libio-socket-ip-perl: do not release with bullseye Bug #969768 [libio-socket-ip-perl] lib-io-socket-ip-perl: do not release with bullseye Changed Bug title to 'libio-socket-ip-perl: do not

Bug#957746: ramond: diff for NMU version 0.5-4.1

2020-09-09 Thread Sudip Mukherjee
Control: tags 957746 + patch Control: tags 957746 + pending -- Dear maintainer, I've prepared an NMU for ramond (versioned as 0.5-4.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru ramond-0.5/debian/changelog ramond-0.5/debian/change

Processed: ramond: diff for NMU version 0.5-4.1

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > tags 957746 + patch Bug #957746 [src:ramond] ramond: ftbfs with GCC-10 Added tag(s) patch. > tags 957746 + pending Bug #957746 [src:ramond] ramond: ftbfs with GCC-10 Added tag(s) pending. -- 957746: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957746 Debian Bu

Bug#957144: dnshistory: diff for NMU version 1.3-2.1

2020-09-09 Thread Sudip Mukherjee
Control: tags 957144 + patch Control: tags 957144 + pending -- Dear maintainer, I've prepared an NMU for dnshistory (versioned as 1.3-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -u dnshistory-1.3/debian/changelog dnshistory-1.3/deb

Processed: dnshistory: diff for NMU version 1.3-2.1

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > tags 957144 + patch Bug #957144 [src:dnshistory] dnshistory: ftbfs with GCC-10 Added tag(s) patch. > tags 957144 + pending Bug #957144 [src:dnshistory] dnshistory: ftbfs with GCC-10 Added tag(s) pending. -- 957144: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=

Bug#969288: r-cran-htmltools: fix autopkgtest failure

2020-09-09 Thread Lucas Kanashiro
Hi, The attached patch fixes the autopkgtest failure. Thanks in advance for considering the patch! -- Lucas Kanashiro --- a/tests/testthat/test-colors.R +++ b/tests/testthat/test-colors.R @@ -1,10 +1,16 @@ context("test-colors") -colors_bad <- readLines(test_path("colors-bad.txt")) -colors_

Bug#969991: src:ruby-diff-lcs: fails to migrate to testing for too long: causes autopkgtest regressions

2020-09-09 Thread Paul Gevers
Source: ruby-diff-lcs Version: 1.3-1 Severity: serious Control: close -1 1.4.4-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 968628 968629 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are

Processed: src:ruby-diff-lcs: fails to migrate to testing for too long: causes autopkgtest regressions

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.4.4-1 Bug #969991 [src:ruby-diff-lcs] src:ruby-diff-lcs: fails to migrate to testing for too long: causes autopkgtest regressions Marked as fixed in versions ruby-diff-lcs/1.4.4-1. Bug #969991 [src:ruby-diff-lcs] src:ruby-diff-lcs: fails to migrate to tes

Bug#969576: nextcloud-desktop: Main window not visible/constructable

2020-09-09 Thread Stefano Zacchiroli
On Wed, Sep 09, 2020 at 07:24:04PM +0200, Paul van Tilburg wrote: > I have to reaffirm that I used an iterative approach to install each of > these to get rid of all warnings and have the main interface appear. > I'm afraid that all dependencies listed above seem necessary, maybe > you had the oth

Bug#969576: nextcloud-desktop: Main window not visible/constructable

2020-09-09 Thread Paul van Tilburg
On Wed, 2020-09-09 at 15:58 +0200, Stefano Zacchiroli wrote > > After installing the following packages, I can see the main window > > again(although it still disappears on me sometimes): > > * qml-module-qtquick-layouts* qml-module-qtquick-controls2* qml- > > module-qtgraphicaleffects* qml-module

Bug#969825: marked as done (extsmail: autopkgtest should be marked superficial)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Sep 2020 17:18:23 + with message-id and subject line Bug#969825: fixed in extsmail 2.4-2 has caused the Debian Bug report #969825, regarding extsmail: autopkgtest should be marked superficial to be marked as done. This means that you claim that the problem has been

Bug#969972: Gimp fails to start

2020-09-09 Thread Simon McVittie
Control: reassign -1 libllvm7,libllvm9,libllvm10 Control: forcemerge 852746 -1 Control: affects 852746 + gimp On Thu, 10 Sep 2020 at 00:34:02 +1000, Nikolai Lusan wrote: > On startup GIMP gives the following error: > > $ gimp-2.10 > Gtk-Message: 00:20:39.212: Failed to load module "t

Processed: Re: Bug#969972: Gimp fails to start

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 libllvm7,libllvm9,libllvm10 Bug #969972 [gimp] Gimp fails to start Bug reassigned from package 'gimp' to 'libllvm7,libllvm9,libllvm10'. No longer marked as found in versions gimp/2.10.20-1. Ignoring request to alter fixed versions of bug #969972 to the sa

Bug#966982: Uploading disabling that test to DELAYED/2

2020-09-09 Thread Håvard Flaget Aasen
On Tue, 8 Sep 2020 16:27:20 +0200 Thomas Goirand wrote: > On 9/8/20 2:01 PM, Håvard Flaget Aasen wrote: > > On Tue, 8 Sep 2020 13:40:25 +0200 Thomas Goirand wrote: > >> Hi, > >> > >> Since nobody seem to care about this, I've uploaded disabling that > >> failing test to DELAYED/2. Indeed, to me,

Processed: severity of 969979 is important

2020-09-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 969979 important Bug #969979 [src:linux] linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system Severity set to 'important' from 'critical' > thanks Stopping processing here. Please contact me if you need assis

Bug#969979: linux-image-4.19.0-6-amd64: checkarray on degraded RAID array crashes the system

2020-09-09 Thread Seb
Package: src:linux Version: 4.19.67-2+deb10u2 Severity: critical Justification: breaks the whole system Dear Maintainer, This machine runs a six-disks RAID10 array with mdadm. This morning, cat /sys/block/md2/md/mismatch_cnt reported 128, indicating errors on the array. This may be link

Bug#968693: marked as done (libredis-perl FTBFS on IPV6-only buildds)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Sep 2020 16:04:49 + with message-id and subject line Bug#968693: fixed in libredis-perl 2:1.9980-2 has caused the Debian Bug report #968693, regarding libredis-perl FTBFS on IPV6-only buildds to be marked as done. This means that you claim that the problem has been

Bug#968693: marked as pending in libredis-perl

2020-09-09 Thread gregor herrmann
Control: tag -1 pending Hello, Bug #968693 in libredis-perl 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/perl-team/modules/packages/libredis-perl/-/commit/3c

Processed: Bug#968693 marked as pending in libredis-perl

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #968693 [src:libredis-perl] libredis-perl FTBFS on IPV6-only buildds Added tag(s) pending. -- 968693: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968693 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#966353: FTBFS: guile segfaults when run to collect docs

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + pending Bug #966353 [src:lilypond] FTBFS: guile segfaults when run to collect docs Added tag(s) pending. -- 966353: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966353 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#966353: FTBFS: guile segfaults when run to collect docs

2020-09-09 Thread Anthony Fok
Control: tags -1 + pending Hi Stuart and Adrian, Thank you for your reports! On Sat, Sep 5, 2020 at 10:03 AM Adrian Bunk wrote: > > On Mon, Jul 27, 2020 at 09:09:45PM +1000, Stuart Prescott wrote: > >... > > guile segfaults as soon as it is started (with or without docs on stdin). > > The backt

Bug#969967: libtest-tcp-perl: bogus dependency libio-socket-ip-perl (>= 0.39-3~)

2020-09-09 Thread gregor herrmann
On Wed, 09 Sep 2020 15:17:58 +0200, Vincent Lefevre wrote: > Package: libtest-tcp-perl > Version: 2.22-2 > Severity: serious > > libtest-tcp-perl 2.22-2 depends on libio-socket-ip-perl (>= 0.39-3~), > but libio-socket-ip-perl, as bundled with perl 5.30, will not be in > bullseye. See > > https

Bug#968308: src:cgview: fails to migrate to testing for too long: autopkgtest failure

2020-09-09 Thread Pierre Gruet
Hi Andreas, Le 09/09/2020 à 13:48, Andreas Tille a écrit : > Control: tags -1 help > > Hi, > > I wonder why this > > ... > autopkgtest [16:10:05]: test run-unit-test: [--- > [warning] /usr/bin/cgview: No java runtime was found > autopkgtest [16:10:06]: test run-unit-test: --

Processed: severity of 969576 is serious

2020-09-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 969576 serious Bug #969576 [nextcloud-desktop] nextcloud-desktop: Main window not visible/constructable Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 969576:

Bug#969972: Gimp fails to start

2020-09-09 Thread Nikolai Lusan
Package: gimp Version: 2.10.20-1 Severity: grave On startup GIMP gives the following error: $ gimp-2.10 Gtk-Message: 00:20:39.212: Failed to load module "topmenu-gtk-module" : CommandLine Error: Option 'polly' registered more than once! LLVM ERROR: inconsistency

Bug#961492: Ping: Any Perl programmer able to fix dh-update-R (Was: Bug#961492: routine-update removes required dependencies)

2020-09-09 Thread Andreas Tille
Control: tags -1 help Ping on this topic. This bug is really nasty and I do not have any spare cycles to tackle this. Kind regards Andreas. On Mon, May 25, 2020 at 11:29:54AM +0200, Andreas Tille wrote: > Hi, > > On Mon, May 25, 2020 at 11:21:48AM +0200, Andreas Tille wrote: > > The

Processed: Ping: Any Perl programmer able to fix dh-update-R (Was: Bug#961492: routine-update removes required dependencies)

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #961492 [dh-r] dh-update-R removes non-R dependencies" Added tag(s) help. -- 961492: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961492 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#969967: libtest-tcp-perl: bogus dependency libio-socket-ip-perl (>= 0.39-3~)

2020-09-09 Thread Vincent Lefevre
Package: libtest-tcp-perl Version: 2.22-2 Severity: serious libtest-tcp-perl 2.22-2 depends on libio-socket-ip-perl (>= 0.39-3~), but libio-socket-ip-perl, as bundled with perl 5.30, will not be in bullseye. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969768 -- System Information: De

Processed: Re: Bug#966521: gnome-remote-desktop: to have g-r-d working with Gnome 3.36, you need to have g-r-d >= 0.1.8

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #966521 [gnome-remote-desktop] gnome-remote-desktop: to have g-r-d working with Gnome 3.36, you need to have g-r-d >= 0.1.8 Severity set to 'grave' from 'normal' -- 966521: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966521 Debian Bug T

Processed: Re: src:cgview: fails to migrate to testing for too long: autopkgtest failure

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #968308 [src:cgview] src:cgview: fails to migrate to testing for too long: autopkgtest failure Added tag(s) help. -- 968308: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968308 Debian Bug Tracking System Contact ow...@bugs.debian.org with pro

Bug#969228: marked as done (glaurung: Segmentation fault caused by out of bounds access)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Sep 2020 11:49:15 + with message-id and subject line Bug#969228: fixed in glaurung 2.2-4 has caused the Debian Bug report #969228, regarding glaurung: Segmentation fault caused by out of bounds access to be marked as done. This means that you claim that the problem

Bug#968308: src:cgview: fails to migrate to testing for too long: autopkgtest failure

2020-09-09 Thread Andreas Tille
Control: tags -1 help Hi, I wonder why this ... autopkgtest [16:10:05]: test run-unit-test: [--- [warning] /usr/bin/cgview: No java runtime was found autopkgtest [16:10:06]: test run-unit-test: ---] autopkgtest [16:10:06]: test run-unit-test: - - - - - -

Processed: forcibly merging 967938 969926

2020-09-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 967938 969926 Bug #967938 [src:glibc] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent Bug #967940 [src:glibc] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent Bug #967938 [src:glibc] libc6: systemd-sysusers SEGV d

Bug#969926: glibc: Parsing of /etc/gshadow can return bad pointers causing segfaults in applications

2020-09-09 Thread Aurelien Jarno
control: forcemerge 967938 969926 Hi, On 2020-09-09 02:58, Bernd Zeimetz wrote: > Source: glibc > Version: 2.28-10 > Severity: serious > Tags: security upstream patch > X-Debbugs-Cc: Debian Security Team > > Hi, > > we are running into the bug > https://sourceware.org/bugzilla/show_bug.cgi?id=

Processed (with 1 error): Re: Bug#969926: glibc: Parsing of /etc/gshadow can return bad pointers causing segfaults in applications

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > forcemerge 967938 969926 Bug #967938 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent Bug #967940 [libc6] libc6: systemd-sysusers SEGV due to glibc bug in fgetgsent Unable to merge bugs because: package of #969926 is 'src:glibc' not 'libc6' Failed t

Processed: Re: Bug#969867: sane-frontends: autopkgtest should be marked superficial

2020-09-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 969867 wishlist Bug #969867 [src:sane-frontends] sane-frontends: autopkgtest should be marked superficial Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 969867:

Processed: Re: Bug#969834: ipmitool: autopkgtest should be marked superficial

2020-09-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 969834 wishlist Bug #969834 [src:ipmitool] ipmitool: autopkgtest should be marked superficial Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 969834: https://bugs

Processed: Re: Bug#969819: dmidecode: autopkgtest should be marked superficial

2020-09-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 969819 wishlist Bug #969819 [src:dmidecode] dmidecode: autopkgtest should be marked superficial Severity set to 'wishlist' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 969819: https://bu

Bug#949613: marked as done (python-uncertainties-doc: missing Breaks+Replaces: python-uncertainties)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Sep 2020 09:48:33 + with message-id and subject line Bug#949613: fixed in uncertainties 3.1.4-1 has caused the Debian Bug report #949613, regarding python-uncertainties-doc: missing Breaks+Replaces: python-uncertainties to be marked as done. This means that you cla

Bug#969565: Bogus upper bound

2020-09-09 Thread Luca Boccassi
On Mon, 7 Sep 2020 09:41:28 +0200 Tristan Seligmann wrote: > I think the upper bound is just bogus and should be removed. Upstream > seems to have added it under the assumption that cryptography follows > semver, but it does not: 2.9 to 3.0 offers the same compatibility > guarantees as 2.8 to 2.9

Bug#969948: marked as done ([debian buster] [xbase-clients] The following packages have unmet dependencies:)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Wed, 9 Sep 2020 11:33:24 +0200 with message-id <20200909093324.GC4722@jcristau-z4> and subject line Re: Bug#969948: [debian buster] [xbase-clients] The following packages have unmet dependencies: has caused the Debian Bug report #969948, regarding [debian buster] [xbase-clients]

Bug#957443: GCC-10 bug triggered by libint2

2020-09-09 Thread Tiziano Müller
As I wrote in https://github.com/evaleev/libint/issues/173#issuecomment-664846938 this is actually a regression in GCC-10 and will be fixed in 10.3, see also https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95889 -- Tiziano Müller University of Zurich Department of Chemistry Winterthurerstrasse 19

Bug#969948: [debian buster] [xbase-clients] The following packages have unmet dependencies:

2020-09-09 Thread Jean-Marc LACROIX
Julien, Indeed, it is not possible to install this package, because I put a rule of no installation in the APT preference file following dark stories of Nvidia drivers ... Afterdeleting the /etc/apt/preferences.d/preferences_debian_v_1

Bug#963088: bppsuite: autopkgtest failure on arm64: precision issue in reference data

2020-09-09 Thread Andreas Tille
Control: tags -1 upstream Control: forwarded -1 Julien Dutheil Hi Julien, could you please relax the check a bit to let this test pass also on arm64? Kind regards Andreas. On Thu, Jun 18, 2020 at 09:12:17PM +0200, Paul Gevers wrote: > Source: bppsuite > Version: 2.4.1-2 > X-Debbugs-CC:

Processed: Re: Bug#963088: bppsuite: autopkgtest failure on arm64: precision issue in reference data

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #963088 [src:bppsuite] bppsuite: autopkgtest failure on arm64: precision issue in reference data Added tag(s) upstream. > forwarded -1 Julien Dutheil Bug #963088 [src:bppsuite] bppsuite: autopkgtest failure on arm64: precision issue in referen

Processed: Re: Bug#963088: bppsuite: autopkgtest failure on arm64: precision issue in reference data

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > tags -1 upstream Bug #963088 [src:bppsuite] bppsuite: autopkgtest failure on arm64: precision issue in reference data Ignoring request to alter tags of bug #963088 to the same tags previously set > forwarded -1 Julien Dutheil Bug #963088 [src:bppsuite] bppsuite: au

Bug#969948: [debian buster] [xbase-clients] The following packages have unmet dependencies:

2020-09-09 Thread Julien Cristau
On Wed, Sep 09, 2020 at 11:07:23AM +0200, Jean-Marc LACROIX wrote: > > ansible@vm-buster-amd64-190:~$ sudo apt install -y libgl1-mesa-dri > Reading package lists... Done > Building dependency tree > Reading state information... Done > Some packages could not be installed. This may mean that you ha

Bug#969948: [debian buster] [xbase-clients] The following packages have unmet dependencies:

2020-09-09 Thread Jean-Marc LACROIX
Le 09/09/2020 à 10:53, Julien Cristau a écrit : Control: tag -1 moreinfo unreproducible On Wed, Sep 09, 2020 at 10:23:53AM +0200, Jean-Marc LACROIX wrote: Package: xbase-clients Version: 3.2-2 That is not the version of xbase-clients in any Debian release as far as I can tell. Severity: g

Processed: Re: Bug#969948: [debian buster] [xbase-clients] The following packages have unmet dependencies:

2020-09-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 moreinfo unreproducible Bug #969948 [xbase-clients] [debian buster] [xbase-clients] The following packages have unmet dependencies: Added tag(s) moreinfo and unreproducible. -- 969948: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969948 Debian Bug Trac

Bug#969948: [debian buster] [xbase-clients] The following packages have unmet dependencies:

2020-09-09 Thread Julien Cristau
Control: tag -1 moreinfo unreproducible On Wed, Sep 09, 2020 at 10:23:53AM +0200, Jean-Marc LACROIX wrote: > Package: xbase-clients > Version: 3.2-2 That is not the version of xbase-clients in any Debian release as far as I can tell. > Severity: grave > > Dear maintainers, > > It seems there i

Bug#968339: Reopening for mips/s390x failures

2020-09-09 Thread Vasyl Gello
Control: reopen ! I am reopening this bug as mipsel test failures are caused by ld.gold usage filed separately.

Bug#969948: [debian buster] [xbase-clients] The following packages have unmet dependencies:

2020-09-09 Thread Jean-Marc LACROIX
Package: xbase-clients Version: 3.2-2 Severity: grave Dear maintainers, It seems there is a dependancy issue (?) when trying to install xbase-clients Debian buster 10.5 package. The installation in done on one LXC container running with sysvinit, and without droping any Posix 1003.2 capabilit

Bug#966972: marked as done (in-toto: FTBFS: ValueError: SSH supports only 1024 bit DSA keys)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Wed, 9 Sep 2020 08:18:35 + with message-id <20200909081835.ge26...@layer-acht.org> and subject line Re: Bug#966972: [in-toto-dev] in-toto is marked for autoremoval from testing has caused the Debian Bug report #966972, regarding in-toto: FTBFS: ValueError: SSH supports only

Processed: tagging 969788

2020-09-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 969788 + moreinfo upstream Bug #969788 [nextcloud-desktop] nextcloud-desktop: Upgrade removed part of configuration Added tag(s) moreinfo and upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 969788:

Bug#969788: nextcloud-desktop: Upgrade removed part of configuration

2020-09-09 Thread Markus Frosch
tags -1 + moreinfo upstream thanks On Tue, 08 Sep 2020 08:29:17 +0200 Erwan David wrote: > Package: nextcloud-desktop > Version: 3.0.1-1 > Severity: grave > Justification: causes non-serious data loss > > I had 3 synchronized folders, after upgrade I had only the first defined, configuration of

Bug#954855: marked as done (php7.4-enchant: Please switch from enchant(1) to enchant-2)

2020-09-09 Thread Debian Bug Tracking System
Your message dated Wed, 09 Sep 2020 07:03:55 + with message-id and subject line Bug#954855: fixed in php7.4 7.4.10-1 has caused the Debian Bug report #954855, regarding php7.4-enchant: Please switch from enchant(1) to enchant-2 to be marked as done. This means that you claim that the problem