Bug#955167: marked as done (r-cran-sf: autopkgtest regression)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sun, 12 Apr 2020 08:06:51 +0200 with message-id and subject line has caused the Debian Bug report #955167, regarding r-cran-sf: autopkgtest regression to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Bug#922595: marked as done (FTBFS due to PDF compilation failure (against Opencv 4.0.1))

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sun, 12 Apr 2020 01:35:05 + with message-id and subject line Bug#922595: fixed in sdaps 1.9.8-0.1 has caused the Debian Bug report #922595, regarding FTBFS due to PDF compilation failure (against Opencv 4.0.1) to be marked as done. This means that you claim that the problem

Bug#953540: marked as done (aspectc++: FTBFS on armel)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 22:48:34 + with message-id and subject line Bug#953540: fixed in aspectc++ 1:2.2+git20200405-1 has caused the Debian Bug report #953540, regarding aspectc++: FTBFS on armel to be marked as done. This means that you claim that the problem has been dealt with

Bug#938476: shedskin: Python2 removal in sid/bullseye

2020-04-11 Thread Moritz Mühlenhoff
On Mon, Sep 30, 2019 at 07:24:07PM +0200, Paul Boddie wrote: > The principal developer has indicated to me that given the policy here, he > and > I will just have to accept that the package will be removed. However, I won't > be tagging or retitling anything. If someone else responsible for this

Processed: py2removal bugs severity updates - 2020-04-11 21:36:25.159880+00:00

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # This is an automated script, part of the effort for the removal of Python 2 > from bullseye > # * https://wiki.debian.org/Python/2Removal > # * http://sandrotosi.me/debian/py2removal/index.html > # See https://lists.debian.org/debian-devel-an

Processed: reassign 956476 to libio-async-ssl-perl, tagging 956159, tagging 956265, tagging 956451 ...

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 956476 libio-async-ssl-perl 0.22-2 Bug #956476 [libnet-async-ssl-perl] libnet-async-ssl-perl: long description contains boilerplate from dh-make-perl Warning: Unknown package 'libnet-async-ssl-perl' Bug reassigned from package 'libnet-as

Bug#956358: openafs-modules-dkms: piuparts failure on package installation

2020-04-11 Thread Benjamin Kaduk
severity 956358 important tags 956358 + moreinfo thanks On Fri, Apr 10, 2020 at 11:30:10AM +0300, Adrian Bunk wrote: > > https://piuparts.debian.org/sid/source/o/openafs.html > > ... > Loading new openafs-1.8.6pre1 DKMS files... > It is likely that 4.19.0-8-amd64 belongs to a chroot's host >

Processed: Re: Bug#956358: openafs-modules-dkms: piuparts failure on package installation

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 956358 important Bug #956358 [openafs-modules-dkms] openafs-modules-dkms: piuparts failure on package installation Severity set to 'important' from 'serious' > tags 956358 + moreinfo Bug #956358 [openafs-modules-dkms] openafs-modules-dkm

Bug#956483: ignition-math: FTBFS during binary-indep build

2020-04-11 Thread Andreas Beckmann
Source: ignition-math Version: 6.4.0+ds-1 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, ignition-math FTBFS during an arch-indep build (dpkg-buildpackage -A), i.e. the arch:any package libignition-math-eigen3-dev does not get built: debian/rules override_dh_insta

Bug#936802: kmer: Python2 removal in sid/bullseye

2020-04-11 Thread Andreas Tille
Hi Liubov, On Sat, Apr 11, 2020 at 07:41:34PM +0200, Liubov Chuprikova wrote: > As I mentioned during today's Jitsi meeting, kmer builds and all the tests > passed in a clean sbuild schroot. Should we close the bug and make a > release then? Thanks for checking and confirming - I just did so. Ki

Bug#942404: marked as done (discosnp: flaky autopkgtest: discoRes_k_31_c_auto_D_100_P_1_b_0_coherent.fa: No such file or directory)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 21:50:47 +0200 with message-id and subject line Re: Tests seem to work again has caused the Debian Bug report #942404, regarding discosnp: flaky autopkgtest: discoRes_k_31_c_auto_D_100_P_1_b_0_coherent.fa: No such file or directory to be marked as done. This m

Processed: reassign 955668 to libpango1.0-dev

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 955668 libpango1.0-dev Bug #955668 [pango1.0] libgaminggear: FTBFS: pango-coverage.h:28:10: fatal error: hb.h: No such file or directory Bug reassigned from package 'pango1.0' to 'libpango1.0-dev'. Ignoring request to alter found version

Bug#937784: python-gevent: diff for NMU version 1.4.0-1.2

2020-04-11 Thread Sandro Tosi
On Sat, Apr 11, 2020 at 3:21 PM László Böszörményi (GCS) wrote: > > On Sat, Apr 11, 2020 at 2:12 AM Sandro Tosi wrote: > > I've prepared an NMU for python-gevent (versioned as 1.4.0-1.2). The diff > > is attached to this message. > You know, I still don't get why immediate NMU was necessary. Wh

Bug#937784: python-gevent: diff for NMU version 1.4.0-1.2

2020-04-11 Thread GCS
On Sat, Apr 11, 2020 at 2:12 AM Sandro Tosi wrote: > I've prepared an NMU for python-gevent (versioned as 1.4.0-1.2). The diff > is attached to this message. You know, I still don't get why immediate NMU was necessary. Why don't give some time to the maintainer to respond. > Please consider main

Bug#956260: [Debichem-devel] Bug#956260: bkchem: should this package be removed?

2020-04-11 Thread Sandro Tosi
> To my opinion, bkchem is the best simple program for drawing chemical > skeletal formulae. > As a chemist I use it all the time. It would really be a pity if it > disappears from Debian. that's good to know and thanks for sharing this. The situation is that every major Linux distributions are r

Processed: jp: name conflict of /usr/bin/jp with sat-xmpp-jp

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 954443 serious Bug #954443 [jp] jp: name conflict of /usr/bin/jp with sat-xmpp-jp Severity set to 'serious' from 'normal' > retitle 904742 jp: name conflict of /usr/bin/jp with sat-xmpp-jp Bug #904742 [jp] jp: /usr/bin/jp is already used

Bug#942404: Tests seem to work again

2020-04-11 Thread Liubov Chuprikova
Hi Paul, I tried hard but wasn't able to reproduce the bug (in a clean chroot). Even for the stable version (2.3.0-2) tests are passing (several times in a row). Looking at the debci logs [1], tests are passing for quite some time. Do you think, it makes sense to keep it longer? Best regards, Liu

Processed: bug used for two issues

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 940491 -1 Bug #940491 [src:meep] src:meep: missing several Breaks+Replaces Bug 940491 cloned as bug 956474 > End of message, stopping processing here. Please contact me if you need assistance. -- 940491: https://bugs.debian.org/cgi-bin/bug

Bug#954530: marked as done (python-trollius: FTBFS: tests failed)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:22:30 + with message-id and subject line Bug#956425: Removed package(s) from unstable has caused the Debian Bug report #954530, regarding python-trollius: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt

Bug#938229: marked as done (python-trollius: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:22:30 + with message-id and subject line Bug#956425: Removed package(s) from unstable has caused the Debian Bug report #938229, regarding python-trollius: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem ha

Bug#955641: marked as done (qevercloud still FTBFS with upcoming doxygen 1.8.15)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:20:24 + with message-id and subject line Bug#955641: fixed in qevercloud 3.0.3+ds-6 has caused the Debian Bug report #955641, regarding qevercloud still FTBFS with upcoming doxygen 1.8.15 to be marked as done. This means that you claim that the problem h

Bug#936420: marked as done (django-ratelimit: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:18:10 + with message-id and subject line Bug#956466: Removed package(s) from unstable has caused the Debian Bug report #936420, regarding django-ratelimit: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem h

Bug#937403: marked as done (pycassa: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:18:37 + with message-id and subject line Bug#956468: Removed package(s) from unstable has caused the Debian Bug report #937403, regarding pycassa: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Bug#806355: marked as done (django-ratelimit: FTBFS with Django 1.9)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:18:10 + with message-id and subject line Bug#956466: Removed package(s) from unstable has caused the Debian Bug report #806355, regarding django-ratelimit: FTBFS with Django 1.9 to be marked as done. This means that you claim that the problem has been de

Bug#939995: marked as done (libltcsmpte: no reverse dependencies - remove from the archive?)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:15:08 + with message-id and subject line Bug#956432: Removed package(s) from unstable has caused the Debian Bug report #939995, regarding libltcsmpte: no reverse dependencies - remove from the archive? to be marked as done. This means that you claim that

Bug#938612: marked as done (sx: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:17:04 + with message-id and subject line Bug#956444: Removed package(s) from unstable has caused the Debian Bug report #938612, regarding sx: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#937635: marked as done (python-cdd: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:17:25 + with message-id and subject line Bug#956445: Removed package(s) from unstable has caused the Debian Bug report #937635, regarding python-cdd: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has bee

Bug#956472: atitvout: Consider removing this package

2020-04-11 Thread Boyuan Yang
Source: atitvout Version: 0.4-13 Severity: serious Tags: sid bullseye X-Debbugs-CC: r...@gna.org Dear Debian atitvout maintainer, The upstream of atitvout was not active since 2003 (!). Besides, this package saw no upload in Debian since 2009. It is also an i386-only package currently. As a res

Bug#938947: marked as done (mpris-remote: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:13:32 + with message-id and subject line Bug#956422: Removed package(s) from unstable has caused the Debian Bug report #938947, regarding mpris-remote: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has b

Bug#936467: marked as done (editobj: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:13:10 + with message-id and subject line Bug#956421: Removed package(s) from unstable has caused the Debian Bug report #936467, regarding editobj: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Bug#950080: marked as done (kwartz-client: modifies conffiles (policy 10.7.3): /etc/kwartz-cloud.conf)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 18:05:12 + with message-id and subject line Bug#950080: fixed in kwartz-client 1.5-1 has caused the Debian Bug report #950080, regarding kwartz-client: modifies conffiles (policy 10.7.3): /etc/kwartz-cloud.conf to be marked as done. This means that you cla

Bug#936802: kmer: Python2 removal in sid/bullseye

2020-04-11 Thread Liubov Chuprikova
Hi Andreas, As I mentioned during today's Jitsi meeting, kmer builds and all the tests passed in a clean sbuild schroot. Should we close the bug and make a release then? Regards, Liubov

Bug#954611: marked as done (genwqe-user: FTBFS: hw_defs.h:36:21: error: static declaration of ‘gettid’ follows non-static declaration)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 17:34:31 + with message-id and subject line Bug#954611: fixed in genwqe-user 4.0.18-3.1 has caused the Debian Bug report #954611, regarding genwqe-user: FTBFS: hw_defs.h:36:21: error: static declaration of ‘gettid’ follows non-static declaration to be marke

Bug#954547: marked as done (sipxtapi: FTBFS: os/linux/OsTaskLinux.cpp:52:19: error: ‘int gettid()’ was declared ‘extern’ and later ‘static’ [-fpermissive])

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 17:24:05 + with message-id and subject line Bug#954547: fixed in sipxtapi 3.3.0~test17-3.1 has caused the Debian Bug report #954547, regarding sipxtapi: FTBFS: os/linux/OsTaskLinux.cpp:52:19: error: ‘int gettid()’ was declared ‘extern’ and later ‘static’ [-

Bug#936802: marked as done (kmer: Python2 removal in sid/bullseye)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 16:52:25 + with message-id and subject line Bug#936802: fixed in kmer 0~20150903+r2013-7 has caused the Debian Bug report #936802, regarding kmer: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been deal

Bug#955668: libgaminggear: FTBFS: pango-coverage.h:28:10: fatal error: hb.h: No such file or directory

2020-04-11 Thread Pierre-Elliott Bécue
Le vendredi 03 avril 2020 à 21:37:34+0200, Lucas Nussbaum a écrit : > [snip] libpango1.0-dev should depend on libharfbuzz-dev, but it doesn't. This bug seems to be in src:pango1.0, and therefore I reassign it. Dear pango1.0 maintainers, please fix the dependencies of libpango1.0-dev. With best r

Processed: reassign 955668 to pango1.0

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 955668 pango1.0 Bug #955668 [src:libgaminggear] libgaminggear: FTBFS: pango-coverage.h:28:10: fatal error: hb.h: No such file or directory Bug reassigned from package 'src:libgaminggear' to 'pango1.0'. No longer marked as found in versio

Bug#954656: nyx: does not start/work

2020-04-11 Thread Taowa Munene-Tardif
Sorry for my previous messages, neomutt decided to send those messages when I clicked "reply" in the BTS web interface :/. On Sun, Mar 22, 2020 at 12:49:45PM +0100, Gordon Shumway wrote: > Dear Maintainer, > >* Starting nyx shows the same error as reported related to python3-stem > bug

Bug#956280: marked as done (shapelib: change in ronn 0.9.0 breaks generation of manpages)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 15:53:52 + with message-id and subject line Bug#956280: fixed in shapelib 1.5.0-2 has caused the Debian Bug report #956280, regarding shapelib: change in ronn 0.9.0 breaks generation of manpages to be marked as done. This means that you claim that the probl

Bug#954656: nyx: does not start/work

2020-04-11 Thread Taowa
On Sun, 22 Mar 2020 12:49:45 +0100 Gordon Shumway wrote: > Package: nyx > Version: 2.1.0-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > >* Starting nyx shows the same error as reported related to python3-stem > bug #953863 >* Installing upst

Bug#954656: nyx: does not start/work

2020-04-11 Thread Taowa
On Sun, 22 Mar 2020 12:49:45 +0100 Gordon Shumway wrote: > Package: nyx > Version: 2.1.0-2 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > >* Starting nyx shows the same error as reported related to python3-stem > bug #953863 >* Installing upst

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

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 14:42:35 + with message-id and subject line Bug#954616: fixed in python-aioopenssl 0.5.1-1 has caused the Debian Bug report #954616, regarding python-aioopenssl: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13 to b

Bug#956450: marked as pending in libreoffice

2020-04-11 Thread Rene Engelhard
Control: tag -1 pending Hello, Bug #956450 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/15aa

Bug#956450: marked as pending in libreoffice

2020-04-11 Thread Rene Engelhard
Control: tag -1 pending Hello, Bug #956450 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/15aa

Processed: Bug#956450 marked as pending in libreoffice

2020-04-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #956450 [libreoffice-common] libreoffice-common: Upgrade fail because of Application.xba file conflict with libreoffice-base Ignoring request to alter tags of bug #956450 to the same tags previously set -- 956450: https://bugs.debian.org/cgi-bin

Processed: Bug#956450 marked as pending in libreoffice

2020-04-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #956450 [libreoffice-common] libreoffice-common: Upgrade fail because of Application.xba file conflict with libreoffice-base Ignoring request to alter tags of bug #956450 to the same tags previously set -- 956450: https://bugs.debian.org/cgi-bin

Bug#956450: libreoffice-common: Upgrade fail because of Application.xba file conflict with libreoffice-base

2020-04-11 Thread Rene Engelhard
Hi, On Sat, Apr 11, 2020 at 03:11:46PM +0200, Petter Reinholdtsen wrote: > [Rene Engelhard] > > I think if it was a generic problem this would have been reported > > LOOONG go: > > No idea if it is a generic problem, but we ran into it on two different > machines, one yesterday and one today, whe

Bug#956450: libreoffice-common: Upgrade fail because of Application.xba file conflict with libreoffice-base

2020-04-11 Thread Petter Reinholdtsen
[Rene Engelhard] > I think if it was a generic problem this would have been reported > LOOONG go: No idea if it is a generic problem, but we ran into it on two different machines, one yesterday and one today, when we decided to migrate the two machines to bullseye, so it is not a very rare probl

Bug#954521: marked as done (golang-github-go-errors-errors: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/go-errors/errors returned exit code 1)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 13:21:02 + with message-id and subject line Bug#954521: fixed in golang-github-go-errors-errors 1.0.1-4 has caused the Debian Bug report #954521, regarding golang-github-go-errors-errors: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=o

Bug#956441: marked as done (cyrus-imapd: autopkgtests failure)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 12:49:44 + with message-id and subject line Bug#956441: fixed in cyrus-imapd 3.0.13-5 has caused the Debian Bug report #956441, regarding cyrus-imapd: autopkgtests failure to be marked as done. This means that you claim that the problem has been dealt with.

Bug#956450: libreoffice-common: Upgrade fail because of Application.xba file conflict with libreoffice-base

2020-04-11 Thread Rene Engelhard
found 956450 1:6.4.0~beta1-2 tag 956450 + pending thanks Hi, On Sat, Apr 11, 2020 at 02:09:47PM +0200, Petter Reinholdtsen wrote: > Upgrading a KDE desktop from from buster to bullseye using 'apt > dist-upgrade' fail because apt aborts halfway in the process when trying > to unpack libreoffice-co

Bug#954497: marked as done (siconos: FTBFS: cc: error: 654: No such file or directory)

2020-04-11 Thread Debian Bug Tracking System
Your message dated Sat, 11 Apr 2020 14:44:28 +0200 with message-id <20200411124428.ga3...@angband.pl> and subject line fixed has caused the Debian Bug report #954497, regarding siconos: FTBFS: cc: error: 654: No such file or directory to be marked as done. This means that you claim that the proble

Processed: Bug#956450 marked as pending in libreoffice

2020-04-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #956450 [libreoffice-common] libreoffice-common: Upgrade fail because of Application.xba file conflict with libreoffice-base Ignoring request to alter tags of bug #956450 to the same tags previously set -- 956450: https://bugs.debian.org/cgi-bin

Bug#956450: marked as pending in libreoffice

2020-04-11 Thread Rene Engelhard
Control: tag -1 pending Hello, Bug #956450 in libreoffice 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/libreoffice-team/libreoffice/libreoffice/-/commit/15aa

Processed: Re: Bug#956450: libreoffice-common: Upgrade fail because of Application.xba file conflict with libreoffice-base

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 956450 1:6.4.0~beta1-2 Bug #956450 [libreoffice-common] libreoffice-common: Upgrade fail because of Application.xba file conflict with libreoffice-base Marked as found in versions libreoffice/1:6.4.0~beta1-2. > tag 956450 + pending Bug #956

Processed: tags 952200 pending

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 952200 pending Bug #952200 [src:libvirt-dbus] libvirt-dbus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 952

Processed: Re: Bug#956166: gnome-shell-extension-easyscreencast: please check compatibility with GNOME Shell 3.36.x

2020-04-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 grave Bug #956166 [gnome-shell-extension-easyscreencast] gnome-shell-extension-easyscreencast: please check compatibility with GNOME Shell 3.36.x Severity set to 'grave' from 'normal' > retitle -1 gnome-shell-extension-easyscreencast: uninstallable in u

Processed: gnome-shell-extension-appindicator: uninstallable in unstable: please update for GNOME Shell 3.36.x

2020-04-11 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 33-1 Bug #956451 [gnome-shell-extension-appindicator] gnome-shell-extension-appindicator: uninstallable in unstable: please update for GNOME Shell 3.36.x Marked as fixed in versions gnome-shell-extension-appindicator/33-1. -- 956451: https://bugs.debian.

Bug#956451: gnome-shell-extension-appindicator: uninstallable in unstable: please update for GNOME Shell 3.36.x

2020-04-11 Thread Simon McVittie
Package: gnome-shell-extension-appindicator Version: 30-2 Severity: grave Tags: sid bullseye Justification: unusable in a pure unstable system Control: fixed -1 33-1 GNOME Shell 3.36.x is now in unstable, making gnome-shell-extension-appindicator uninstallable. Please upload the experimental versi

Bug#956450: libreoffice-common: Upgrade fail because of Application.xba file conflict with libreoffice-base

2020-04-11 Thread Petter Reinholdtsen
Package: libreoffice-common Version: 1:6.4.2-3 Severity: serious Setting RC severity because this break 'apt dist-upgrade' and leave the machine in a problematic state. Did not find an existing report, but might have missed one among the pile in bts. Upgrading a KDE desktop from from buster to

Bug#956324: python-biopython: FTBFS on mipsel

2020-04-11 Thread Peter Cock
I agree this is most likely a clustalo error. I think the first two examples use temporary input files created during the Biopython tests. However, the third failing example ought to be useful in isolation: clustalo -i Fasta/f002 --guidetree-out temp_test.dnd -o temp_test.aln --outfmt clustal --fo

Processed: clone bug to track babel-loader optimization

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 956211 -1 Bug #956211 {Done: Pirate Praveen } [gitlab] nodejs 10 segfaults when running webpack on gitlab 12.9.2 - FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory Bug 956211 cloned a

Processed (with 1 error): Re: [Pkg-privacy-maintainers] Bug#944823: it's same as #942901 and the workaround shared by Paul works.

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 944823 Bug #944823 [torbrowser-launcher] Failure to open shm and ggx failures. Marked Bug as done > forcemerge 944823 942901 Bug #944823 {Done: Roger Shimizu } [torbrowser-launcher] Failure to open shm and ggx failures. Bug #942901 {Done: R

Processed: freecad: diff for NMU version 0.18.4+dfsg2-1.1

2020-04-11 Thread Debian Bug Tracking System
Processing control commands: > tags 953721 + patch Bug #953721 [src:freecad] freecad: FTBFS with Python 3.8 Added tag(s) patch. > tags 953721 + pending Bug #953721 [src:freecad] freecad: FTBFS with Python 3.8 Added tag(s) pending. -- 953721: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=9537

Processed (with 1 error): Re: [Pkg-privacy-maintainers] Bug#944823: it's same as #942901 and the workaround shared by Paul works.

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 944823 942901 Bug #944823 [torbrowser-launcher] Failure to open shm and ggx failures. Bug #944823 [torbrowser-launcher] Failure to open shm and ggx failures. Added tag(s) upstream and fixed-upstream. Bug #942901 {Done: Roger Shimizu } [

Bug#953721: freecad: diff for NMU version 0.18.4+dfsg2-1.1

2020-04-11 Thread Tobias Frost
Control: tags 953721 + patch Control: tags 953721 + pending Dear maintainer, I've prepared an NMU for freecad (versioned as 0.18.4+dfsg2-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru freecad-0.18.4+dfsg2/debian/changelog freecad-

Bug#953852: marked as pending in ardentryst

2020-04-11 Thread Reiner Herrmann
Control: tag -1 pending Hello, Bug #953852 in ardentryst 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/games-team/ardentryst/-/commit/05d5bdb5e4b8f308e06acd2b

Processed: Bug#953852 marked as pending in ardentryst

2020-04-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #953852 [ardentryst] ardentryst: should this package be removed? Added tag(s) pending. -- 953852: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953852 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Re: Bug#953999: iwyu: FTBFS on armel

2020-04-11 Thread Debian Bug Tracking System
Processing control commands: > block 953784 by -1 Bug #953784 {Done: Sylvestre Ledru } [src:iwyu] src:iwyu: fails to migrate to testing for too long 953784 was blocked by: 953999 953784 was not blocking any bugs. Ignoring request to alter blocking bugs of bug #953784 to the same blocks previousl

Processed: Re: Bug#953999: iwyu: FTBFS on armel

2020-04-11 Thread Debian Bug Tracking System
Processing control commands: > block 953784 by -1 Bug #953784 {Done: Sylvestre Ledru } [src:iwyu] src:iwyu: fails to migrate to testing for too long 953784 was not blocked by any bugs. 953784 was not blocking any bugs. Added blocking bug(s) of 953784: 953999 > reassign -1 ftp.debian.org Bug #9539

Bug#953999: iwyu: FTBFS on armel

2020-04-11 Thread Adrian Bunk
Control: block 953784 by -1 Control: reassign -1 ftp.debian.org Control: severity -1 normal Control: retitle -1 M: iwyu [armel] -- ANAIS; no longer built on armel iwyu (8.0-4) unstable; urgency=medium * Disable support for armel. Fails to build and I don't think any one uses it on this arch

Processed: block 953787 with 949756

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 953787 with 949756 Bug #953787 [src:staticsite] src:staticsite: fails to migrate to testing for too long 953787 was not blocked by any bugs. 953787 was not blocking any bugs. Added blocking bug(s) of 953787: 949756 > thanks Stopping process

Bug#956280: shapelib: change in ronn 0.9.0 breaks generation of manpages

2020-04-11 Thread Cédric Boutillier
On Sat, Apr 11, 2020 at 06:20:13AM +0200, Sebastiaan Couwenberg wrote: > > pycsw required the same changes. Those are also ready in git. Ah... I was wondering why it was not listed by build-rdepends script (without parameters), but it is probably because it is in non-free. > You don't have to wa

Processed: severity of 956280 is serious

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 956280 serious Bug #956280 [src:shapelib] shapelib: change in ronn 0.9.0 breaks generation of manpages Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 956280: h

Bug#956441: cyrus-imapd: autopkgtests failure

2020-04-11 Thread Gianfranco Costamagna
Source: cyrus-imapd Version: 3.0.13-4 Severity: serious Hello, looks like the latest -4 upload is now failing its autopgktests https://ci.debian.net/packages/c/cyrus-imapd/ https://ci.debian.net/data/packages/unstable/amd64/c/cyrus-imapd/latest-autopkgtest/log.gz Not sure if this is the case, but

Processed: Re: Bug#956372: cbp2make: Binary missing after rebuild

2020-04-11 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #956372 [cbp2make] cbp2make: Binary missing after rebuild Severity set to 'serious' from 'normal' -- 956372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956372 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Bug#954727 marked as pending in docker.io

2020-04-11 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #954727 [src:docker.io] docker.io: FTBFS: dh_auto_test: error: cd .gopath && go test -vet=off -v -p 4 -short github.com/docker/docker/api [..] exit code 1 Added tag(s) pending. -- 954727: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954727

Bug#954727: marked as pending in docker.io

2020-04-11 Thread Dmitry Smirnov
Control: tag -1 pending Hello, Bug #954727 in docker.io 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/docker-team/docker/-/commit/c46915a0c060f68c2d821ebcaf61

Processed: tagging 951054, severity of 951054 is normal

2020-04-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 951054 + moreinfo unreproducible Bug #951054 [powertop] powertop: FTBFS, problem with aclocal: error: too many loops Added tag(s) unreproducible and moreinfo. > severity 951054 normal Bug #951054 [powertop] powertop: FTBFS, problem with aclo

Bug#951054: powertop: FTBFS, problem with aclocal: error: too many loops

2020-04-11 Thread Kan-Ru Chen
Hi, On Mon, Feb 10, 2020, at 7:29 PM, Laurent Bonnaud wrote: > Package: powertop > Version: 2.11-1 > Severity: serious > > > Dear Maintainer, > > here is the problem: > > $ apt -b source powertop I can not reproduce the FTBFS issue on my local machine or pbuilder. There is also no failure re

Bug#956423: [Pkg-javascript-devel] Bug#956423: node-request: deprecated upstream: should not be part of next stable Debian release

2020-04-11 Thread Xavier
Le 10/04/2020 à 23:44, Jonas Smedegaard a écrit : > Package: node-request > Version: 2.88.1-4 > Severity: grave > Justification: renders package unusable > > Upstream has deprecated this module: > https://github.com/request/request/issues/3142 > > It already has seen no new updates for a year, > a