Bug#974090: [Pkg-fonts-devel] Bug#974090: fonts-gfs-artemisia breaks lcdf-typetools autopkgtest: lots of failures

2020-11-10 Thread Fabian Greffrath
Am 2020-11-09 20:58, schrieb Paul Gevers: # Failed test 'Testing stderr' # at debian/tests/cfftot1.t line 24. # got: 'cfftot1: /usr/share/fonts/truetype/artemisia/GFSArtemisia.otf: No such file or directory This is looking for an opentype font in the truetype directory, which is

Bug#974192: mpfrc++: invalid maintainer address

2020-11-10 Thread Ansgar
Source: mpfrc++ Version: 3.6.8+ds-1 Severity: serious X-Debbugs-Cc: Jerome Benoit The maintainer address is invalid, see below. Ansgar > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered to one or more of its > recipients. This

Processed: reassign 947437 to src:flang

2020-11-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 947437 src:flang Bug #947437 [flang] flang: Please update to llvm-9 Bug reassigned from package 'flang' to 'src:flang'. No longer marked as found in versions 20190329-5. Ignoring request to alter fixed versions of bug #947437 to the same

Bug#974076: marked as done (igv: FTBFS error: module not found: junit4)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Nov 2020 06:48:55 + with message-id and subject line Bug#974076: fixed in igv 2.6.3+dfsg-2 has caused the Debian Bug report #974076, regarding igv: FTBFS error: module not found: junit4 to be marked as done. This means that you claim that the problem has been dealt

Bug#973999: armnn: FTBFS: error: no matching function for call to ‘arm_compute::PoolingLayerInfo::PoolingLayerInfo(const arm_compute::PoolingType&)’

2020-11-10 Thread Wookey
This will be due to the fact that v20.08 of arm-compute library was accepted on 5th Nov. armnn now needs to be upgraded to 20.08 as well to get a matching API. a 20.08 armnn package is in preparation and should be uploaded in a week or two. The dependencies should probably be tightened to

Bug#974169: marked as done (packer FTBFS on IPV6-only buildds)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Nov 2020 03:04:33 + with message-id and subject line Bug#974169: fixed in packer 1.6.5+dfsg-3 has caused the Debian Bug report #974169, regarding packer FTBFS on IPV6-only buildds to be marked as done. This means that you claim that the problem has been dealt with.

Bug#974169: marked as pending in packer

2020-11-10 Thread Shengjing Zhu
Control: tag -1 pending Hello, Bug #974169 in packer 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:

Processed: Bug#974169 marked as pending in packer

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

Bug#919412: marked as done (rng-tools: Build-Depends on cruft package libgcrypt11-dev)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Nov 2020 02:41:43 + with message-id and subject line Bug#919412: fixed in rng-tools 5migrate1 has caused the Debian Bug report #919412, regarding rng-tools: Build-Depends on cruft package libgcrypt11-dev to be marked as done. This means that you claim that the

Bug#915689: marked as done (prevent from migrating to testing)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Nov 2020 02:41:43 + with message-id and subject line Bug#915689: fixed in rng-tools 5migrate1 has caused the Debian Bug report #915689, regarding prevent from migrating to testing to be marked as done. This means that you claim that the problem has been dealt with.

Bug#951799: marked as done (rng-tools: No longer supports some options)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Nov 2020 02:41:44 + with message-id and subject line Bug#951799: fixed in rng-tools 5migrate1 has caused the Debian Bug report #951799, regarding rng-tools: No longer supports some options to be marked as done. This means that you claim that the problem has been

Bug#973072:

2020-11-10 Thread Michael Hudson-Doyle
it's easy to fix the base64 related failures (patch attached) but then the build hangs for me. --- a/kubernetes/config/kube_config.py +++ b/kubernetes/config/kube_config.py @@ -97,7 +97,7 @@ if use_data_if_no_file: if self._base64_file_content: self._file =

Bug#973061:

2020-11-10 Thread Michael Hudson-Doyle
This trivial fix seems to fix the problem: diff -Nru nototools-0.2.13/debian/rules nototools-0.2.13/debian/rules --- nototools-0.2.13/debian/rules 2020-09-29 11:11:13.0 +1300 +++ nototools-0.2.13/debian/rules 2020-11-11 14:13:22.0 +1300 @@ -22,3 +22,4 @@ override_dh_auto_clean:

Bug#973056: marked as done (sphinx-tabs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Nov 2020 01:19:59 + with message-id and subject line Bug#973056: fixed in sphinx-tabs 1.2.1+ds-2 has caused the Debian Bug report #973056, regarding sphinx-tabs: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit

Bug#972967: marked as done (vmemcache FTBFS on armel/mipsel/powerpc: undefined reference to `__atomic_fetch_add_8')

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 23:38:17 + with message-id and subject line Bug#972967: fixed in vmemcache 0.8.1-2 has caused the Debian Bug report #972967, regarding vmemcache FTBFS on armel/mipsel/powerpc: undefined reference to `__atomic_fetch_add_8' to be marked as done. This means

Bug#961155: marked as done (pod2pdf: needs build and runtime dependencies on libpod-parser-perl)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 23:37:55 + with message-id and subject line Bug#961155: fixed in pod2pdf 0.42-5.1 has caused the Debian Bug report #961155, regarding pod2pdf: needs build and runtime dependencies on libpod-parser-perl to be marked as done. This means that you claim that

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

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 23:38:08 + with message-id and subject line Bug#973057: fixed in python-py 1.9.0-2 has caused the Debian Bug report #973057, regarding python-py: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.9 3.8" returned exit code 13

Bug#973165: marked as done (pyflakes: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 23:08:09 + with message-id and subject line Bug#973165: fixed in pyflakes 2.2.0-2 has caused the Debian Bug report #973165, regarding pyflakes: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13 to

Bug#961154: marked as done (debarchiver: needs a build dependency on libpod-parser-perl)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 23:03:36 + with message-id and subject line Bug#961154: fixed in debarchiver 0.11.5+nmu1 has caused the Debian Bug report #961154, regarding debarchiver: needs a build dependency on libpod-parser-perl to be marked as done. This means that you claim that

Processed: Bug#973165 marked as pending in pyflakes

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #973165 [src:pyflakes] pyflakes: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.9 3.8" returned exit code 13 Added tag(s) pending. -- 973165: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973165 Debian Bug

Bug#973165: marked as pending in pyflakes

2020-11-10 Thread Michael Hudson-Doyle
Control: tag -1 pending Hello, Bug #973165 in pyflakes 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#961154: debarchiver: diff for NMU version 0.11.5+nmu1

2020-11-10 Thread Dominic Hargreaves
Control: tags 961154 + patch Control: tags 961154 + pending Dear maintainer, I've prepared an NMU for debarchiver (versioned as 0.11.5+nmu1) and uploaded it to DELAYED/0. Please feel free to tell me if I should delay it longer. Regards. diff -Nru debarchiver-0.11.5/debian/changelog

Processed: debarchiver: diff for NMU version 0.11.5+nmu1

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > tags 961154 + patch Bug #961154 [debarchiver] debarchiver: needs a build dependency on libpod-parser-perl Added tag(s) patch. > tags 961154 + pending Bug #961154 [debarchiver] debarchiver: needs a build dependency on libpod-parser-perl Added tag(s) pending. --

Bug#966914: bgzf.c:415: error: undefined reference to 'compressBound'

2020-11-10 Thread Étienne Mollier
Control: tag -1 pending Hello, I managed to get the 'compressBound' symbol available to that bgzf.c intermediate file by modifying the meson.build file to add a dependency to the 'zlib'. With this fix, the build goes through, finally. :) I also made an unrelated change flagged by lintian

Bug#966914: bgzf.c:415: error: undefined reference to 'compressBound'

2020-11-10 Thread Étienne Mollier
Control: tag -1 pending Hello, I managed to get the 'compressBound' symbol available to that bgzf.c intermediate file by modifying the meson.build file to add a dependency to the 'zlib'. With this fix, the build goes through, finally. :) I also made an unrelated change flagged by lintian

Processed: bgzf.c:415: error: undefined reference to 'compressBound'

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #966914 [src:sambamba] sambamba: FTBFS: collect2: error: ld returned 1 exit status Ignoring request to alter tags of bug #966914 to the same tags previously set -- 966914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966914 Debian Bug

Processed: bgzf.c:415: error: undefined reference to 'compressBound'

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #966914 [src:sambamba] sambamba: FTBFS: collect2: error: ld returned 1 exit status Added tag(s) pending. -- 966914: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966914 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#973254: marked as done (pacemaker: CVE-2020-25654)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 22:34:18 + with message-id and subject line Bug#973254: fixed in pacemaker 2.0.5~rc2-1 has caused the Debian Bug report #973254, regarding pacemaker: CVE-2020-25654 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#961154: debarchiver: needs a build dependency on libpod-parser-perl

2020-11-10 Thread Dominic Hargreaves
Having just discussed this a bit more with the release team, I'll do an NMU now since it's a trivial change. Best Dominci On Sun, Nov 08, 2020 at 06:13:44PM +, Dominic Hargreaves wrote: > Hi, > > Could you please upload this soon? We've just kicked off the transition > so this will prevent

Bug#974096: golang-github-c-bata-go-prompt: autopkgtest regression: cannot use (type *unix.Termios) as type *syscall.Termios in argument to termios.Tcgetattr

2020-11-10 Thread Aloïs Micard
On 10/11/2020 20:55, Paul Gevers wrote: Hi Aloïs, On 10-11-2020 00:38, Aloïs Micard wrote: I've uploaded a new version of golang-github-pkg-term [1], and by doing so, broke the build of golang-github-c-bata-go-prompt [2] & golang-github-jaguilar-vt100 [3]. Ack. So, the new

Processed: unblock 968912 with 974016

2020-11-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unblock 968912 with 974016 Bug #968912 [release.debian.org] transition: perl 5.32 968912 was blocked by: 974061 961155 972274 974058 968913 974016 964902 961152 960863 974143 961208 974134 974021 974063 974170 961157 974055 972275 961154 968912

Bug#942135: Сannot install Perl 5.30.0-6 without deleting the libgtk2-perl package

2020-11-10 Thread Dominic Hargreaves
On Tue, Nov 10, 2020 at 09:03:42AM +0100, intrigeri wrote: > Hi, > > Dominic Hargreaves (2020-11-09): > > A year on, it seems there's almost no realistic prospect of this > > package coming back. Shall we remove it from sid? > > Thank you for caring! > > Quoting the plan I proposed #912860: "I

Bug#974143: marked as done (libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 22:04:14 + with message-id and subject line Bug#974143: fixed in libencode-arabic-perl 14.2-2 has caused the Debian Bug report #974143, regarding libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration

Bug#974016: mrs: FTBFS with libzeep-dev 5.0.0-1: "Checking for libzeep...libzeep is not installed"

2020-11-10 Thread Sebastian Ramacher
Hi Marten On 2020-11-10 07:42:45 +0100, Maarten L. Hekkelman wrote: > Hi Andreas, > > To avoid confusion, we're talking about three tools here: libzeep, mrc and > mrs. > > mrc is a simple resource compiler, is now compatible and bug free, builds on > all architectures and should be kept. I

Bug#974167: fetchmail: OpenSSL reported error: key too small

2020-11-10 Thread GCS
Control: severity -1 normal On Tue, Nov 10, 2020 at 10:30 PM Francesco Potortì wrote: > fetchmail can no longer download mail from some servers. In the logfile > it reports: > > fetchmail: OpenSSL reported: error:141A318A:SSL > routines:tls_process_ske_dhe:dh key too small > fetchmail: SSL

Processed: Re: Bug#974167: fetchmail: OpenSSL reported error: key too small

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #974167 [fetchmail] fetchmail: OpenSSL reported error: key too small Severity set to 'normal' from 'grave' -- 974167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974167 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: clone

2020-11-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 974143 -1 Bug #974143 [libencode-arabic-perl] libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator Bug 974143 cloned as bug 974170 968912 was blocked by: 974134 974058 974016

Processed: Bug#974143 marked as pending in libencode-arabic-perl

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #974143 [libencode-arabic-perl] libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator Added tag(s) pending. -- 974143: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974143

Bug#974143: marked as pending in libencode-arabic-perl

2020-11-10 Thread Dominic Hargreaves
Control: tag -1 pending Hello, Bug #974143 in libencode-arabic-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:

Bug#974169: packer FTBFS on IPV6-only buildds

2020-11-10 Thread Adrian Bunk
Source: packer Version: 1.6.4+dfsg-3 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=packer=amd64=1.6.4%2Bdfsg-3=1601828399=0 ... --- FAIL: TestStepHTTPIPDiscover_Run (0.00s) ... dh_auto_test: error: cd _build && go test -vet=off -v -p 4 github.com/hashicorp/packer

Processed: fixed 967194 1.0.8-1

2020-11-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 967194 1.0.8-1 Bug #967194 {Done: Russell Stuart } [src:pam-python] pam-python: Unversioned Python removal in sid/bullseye Ignoring request to alter fixed versions of bug #967194 to the same values previously set > End of message,

Bug#974168: bioperl-run: autopkgtest failure

2020-11-10 Thread Adrian Bunk
Source: bioperl-run Version: 1.7.3-4 Severity: serious https://ci.debian.net/packages/b/bioperl-run/ ... # Can't locate File/Sort.pm in @INC (you may need to install the File::Sort module) (@INC contains: ../../.. /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.30.3

Bug#974167: fetchmail: OpenSSL reported error: key too small

2020-11-10 Thread Francesco Potortì
Package: fetchmail Version: 6.4.13-1 Severity: grave X-Debbugs-Cc: none, Francesco Potortì fetchmail can no longer download mail from some servers. In the logfile it reports: fetchmail: OpenSSL reported: error:141A318A:SSL routines:tls_process_ske_dhe:dh key too small fetchmail: SSL

Bug#964693: marked as done (qpxtool: FTBFS: include/device.h:434:12: error: ‘QIODevice’ has not been declared)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 20:56:41 + with message-id and subject line Bug#964693: fixed in qpxtool 0.8.1-1 has caused the Debian Bug report #964693, regarding qpxtool: FTBFS: include/device.h:434:12: error: ‘QIODevice’ has not been declared to be marked as done. This means that

Bug#974150: marked as done (Noto Mono looks completely different after upgrade)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 20:55:04 + with message-id and subject line Bug#974150: fixed in fonts-noto 20201109-1 has caused the Debian Bug report #974150, regarding Noto Mono looks completely different after upgrade to be marked as done. This means that you claim that the problem

Processed: severity of 973254 is grave

2020-11-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 973254 grave Bug #973254 [src:pacemaker] pacemaker: CVE-2020-25654 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 973254:

Bug#974150: marked as pending in fonts-noto

2020-11-10 Thread Jonas Smedegaard
Control: tag -1 pending Hello, Bug #974150 in fonts-noto 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#974162: plast: binary-all FTBFS

2020-11-10 Thread Adrian Bunk
Source: plast Version: 2.3.2+dfsg-2 Severity: serious Tags: ftbfs https://buildd.debian.org/status/fetch.php?pkg=plast=all=2.3.2%2Bdfsg-2=1605032084=0 ... dh_missing: error: missing files, aborting The following debhelper tools have reported what they installed (with files per package)

Processed: Bug#974150 marked as pending in fonts-noto

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #974150 [fonts-noto-mono] Noto Mono looks completely different after upgrade Added tag(s) pending. -- 974150: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974150 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#972137: marked as done (r-bioc-tcgabiolinks: autopkgtest regression)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 22:31:17 +0200 with message-id <20201110203117.GA26402@localhost> and subject line Re: Bug#972137: r-bioc-tcgabiolinks: autopkgtest regression has caused the Debian Bug report #972137, regarding r-bioc-tcgabiolinks: autopkgtest regression to be marked as done.

Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526

2020-11-10 Thread Maarten L. Hekkelman
Op 10-11-2020 om 16:21 schreef Andrey Rahmatullin: Running 7 test cases... started daemon at port 5923 terminate called after throwing an instance of 'boost::wrapexcept' what(): resolve: Host not found (authoritative) Looks like it tries to resolve something, and that usually implies

Bug#974150: [Pkg-fonts-devel] Bug#974150: Noto Mono looks completely different after upgrade

2020-11-10 Thread Steinar H. Gunderson
On Tue, Nov 10, 2020 at 08:34:10PM +0100, Jonas Smedegaard wrote: > Would you still find it relevant to pin the old font even if the new one > works but simply uses different visual style? Yes. I find the new one fairly unreadable as a terminal font. > Source for Debian package is

Bug#973630: marked as done (fetchmail: OpenSSL library mismatch)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 20:54:22 +0100 with message-id and subject line Re: Bug#973472: fetchmail: Fails to connect using SSL has caused the Debian Bug report #973472, regarding fetchmail: OpenSSL library mismatch to be marked as done. This means that you claim that the problem has

Bug#974036: marked as done (Fails to build on mips64el)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 19:55:16 + with message-id and subject line Bug#974036: fixed in squeekboard 1.10.0-2 has caused the Debian Bug report #974036, regarding Fails to build on mips64el to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#974096: golang-github-c-bata-go-prompt: autopkgtest regression: cannot use (type *unix.Termios) as type *syscall.Termios in argument to termios.Tcgetattr

2020-11-10 Thread Paul Gevers
Hi Aloïs, On 10-11-2020 00:38, Aloïs Micard wrote: > I've uploaded a new version of golang-github-pkg-term [1], and by > doing so, broke the build of golang-github-c-bata-go-prompt [2] & > golang-github-jaguilar-vt100 [3]. Ack. So, the new golang-github-pkg-term Breaks the version of

Bug#973472: marked as done (fetchmail: Fails to connect using SSL)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 20:54:22 +0100 with message-id and subject line Re: Bug#973472: fetchmail: Fails to connect using SSL has caused the Debian Bug report #973472, regarding fetchmail: Fails to connect using SSL to be marked as done. This means that you claim that the problem

Bug#974150: [Pkg-fonts-devel] Bug#974150: Noto Mono looks completely different after upgrade

2020-11-10 Thread Jonas Smedegaard
Quoting Steinar H. Gunderson (2020-11-10 20:08:14) > On Tue, Nov 10, 2020 at 07:46:55PM +0100, Jonas Smedegaard wrote: > > Why the severity? > > > > Visual changes does not seem reason release-critical to me. > > > > "completely broken" need more than a vague suspicion, IMHO. > > Feel free to

Bug#974150: [Pkg-fonts-devel] Bug#974150: Noto Mono looks completely different after upgrade

2020-11-10 Thread Steinar H. Gunderson
On Tue, Nov 10, 2020 at 07:46:55PM +0100, Jonas Smedegaard wrote: > Why the severity? > > Visual changes does not seem reason release-critical to me. > > "completely broken" need more than a vague suspicion, IMHO. Feel free to downgrade. The background for the severity: I installed the package

Bug#973508: marked as done (bazel-bootstrap FTBFS)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 19:03:25 + with message-id and subject line Bug#973508: fixed in bazel-bootstrap 3.4.0+ds-2 has caused the Debian Bug report #973508, regarding bazel-bootstrap FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526

2020-11-10 Thread gregor herrmann
On Tue, 10 Nov 2020 20:21:10 +0500, Andrey Rahmatullin wrote: > > >> what(): resolve: Host not found (authoritative) > Looks like it tries to resolve something, and that usually implies > Internet access, as otherwise you could just connect to localhost? > Accessing the Internet is forbidden

Bug#937234: pam-python/libpam-mklocaluser/debian-edu-config python3 migration.

2020-11-10 Thread Moritz Mühlenhoff
On Sat, Sep 19, 2020 at 06:00:05PM +0100, peter green wrote: > The debian python maintainers are trying to phase out python 2. > > python 2 has been granted a stay of execution as some important software > requires it to build. In Bullseye Python 2 will only be supported for build deps (using

Bug#974150: [Pkg-fonts-devel] Bug#974150: Noto Mono looks completely different after upgrade

2020-11-10 Thread Jonas Smedegaard
Hi Steinar, Quoting Steinar H. Gunderson (2020-11-10 18:42:02) > Package: fonts-noto-mono > Version: 20201027-3 > Severity: grave Why the severity? Visual changes does not seem reason release-critical to me. "completely broken" need more than a vague suspicion, IMHO. > For unknown reasons,

Bug#974021: marked as done (kvirc FTBFS: error: aggregate ‘QPainterPath sP’ has incomplete type and cannot be defined)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 18:03:49 + with message-id and subject line Bug#974021: fixed in kvirc 4:5.0.0+dfsg-4 has caused the Debian Bug report #974021, regarding kvirc FTBFS: error: aggregate ‘QPainterPath sP’ has incomplete type and cannot be defined to be marked as done. This

Bug#974150: Noto Mono looks completely different after upgrade

2020-11-10 Thread Steinar H. Gunderson
Package: fonts-noto-mono Version: 20201027-3 Severity: grave Hi, For unknown reasons, Noto Mono looks completely different after I upgraded my unstable machines recently, to the point that it's not the same font anymore (for one, it has serifs). This affects multiple machines, both rxvt-unicode

Bug#943037: git-hub: Python2 removal in sid/bullseye

2020-11-10 Thread Leandro Lucarella
New major version is compatible with Python3, please see https:// github.com/sociomantic-tsunami/git-hub/releases/tag/v2.0.1 for the current latest release. -- Leandro Lucarella (Luca) https://llucax.com signature.asc Description: This is a digitally signed message part.

Bug#973123: marked as done (idzebra: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 16:50:04 + with message-id and subject line Bug#973123: fixed in idzebra 2.2.2-1 has caused the Debian Bug report #973123, regarding idzebra: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be marked as done. This means that

Bug#974143: libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator

2020-11-10 Thread gregor herrmann
On Tue, 10 Nov 2020 15:26:43 +, Niko Tyni wrote: > Given the transliteration lists are built dynamically in the code, maybe > the thing to do is just to insert some "no warnings 'misc'" declarations > to suppress the warnings. Some random notes: 1) popcon: installed: 9 = vote: 1 + old: 7 +

Bug#974147: marked as done (Script doesn't start due to /usr/bin/python being obsolete: must use /usr/bin/python2 instead)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 17:24:07 +0100 with message-id <460916417ee5208abee138ce2933da30f1cb60d0.ca...@debian.org> and subject line Severity downgrade - not in Sid has caused the Debian Bug report #974147, regarding Script doesn't start due to /usr/bin/python being obsolete: must use

Processed: Re: golang-github-shenwei356-bwt: FTBFS: unsatisfiable build dependency

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > severity -1 minor Bug #965114 [golang-github-shenwei356-bwt] golang-github-shenwei356-bwt: FTBFS: unsatisfiable build dependency Severity set to 'minor' from 'serious' -- 965114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965114 Debian Bug Tracking System

Bug#965114: golang-github-shenwei356-bwt: FTBFS: unsatisfiable build dependency

2020-11-10 Thread Nilesh Patra
Control: severity -1 minor On Tue, 10 Nov 2020 21:39:40 +0530 Nilesh Patra wrote: > sbuild (Debian sbuild) 0.79.1 (22 April 2020) on debian > > ++ > | golang-github-shenwei356-bwt

Processed: block 895037 with 974146

2020-11-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 895037 with 974146 Bug #895037 [src:libappindicator] libappindicator: deprecated in Debian; AppIndicator based applications, please switch to Ayatana (App)Indicator(s) 895037 was blocked by: 956779 956762 906026 956770 956767 956764 956765

Bug#974147: Script doesn't start due to /usr/bin/python being obsolete: must use /usr/bin/python2 instead

2020-11-10 Thread Daniel Leidert
Package: gtk-recordmydesktop Version: 0.3.8-4.1 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The application fails to start in Sid due to /usr/bin/python not existing (anymore). I've asked on the #deian-python channel and got told that using /usr/bin/python is a bug and when

Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526

2020-11-10 Thread Andrey Rahmatullin
On Tue, Nov 10, 2020 at 05:17:26PM +0200, Juhani Numminen wrote: > Hi, > > Maarten L. Hekkelman as the package maintainer asked for my help with bug > #973526 > but I have to forward his request to debian-mentors. > > The package libzeep failed to build on amd64, apparently because of a SIGABRT

Bug#974144: Fails under wayland and fails trying to select a window

2020-11-10 Thread Daniel Leidert
Package: kazam Version: 1.4.5-4 Severity: grave -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 I tried kazam. First the errors shown on the command line clearly indicate that it is not supposed to work with wayland: (kazam:89108): Wnck-WARNING **: 16:47:15.482: libwnck is designed to work in

Processed: Bug#974063 marked as pending in postgresql

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure Ignoring request to alter tags of bug #974063 to the same tags previously set -- 974063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974063 Debian Bug Tracking System

Bug#974063: marked as pending in postgresql

2020-11-10 Thread Christoph Berg
Control: tag -1 pending Hello, Bug #974063 in postgresql 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#974063: marked as pending in postgresql

2020-11-10 Thread Christoph Berg
Control: tag -1 pending Hello, Bug #974063 in postgresql 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:

Processed: Bug#974063 marked as pending in postgresql

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure Ignoring request to alter tags of bug #974063 to the same tags previously set -- 974063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974063 Debian Bug Tracking System

Bug#974063: marked as pending in postgresql

2020-11-10 Thread Christoph Berg
Control: tag -1 pending Hello, Bug #974063 in postgresql 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:

Processed: Bug#974063 marked as pending in postgresql

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure Ignoring request to alter tags of bug #974063 to the same tags previously set -- 974063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974063 Debian Bug Tracking System

Bug#974143: libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator

2020-11-10 Thread Niko Tyni
Package: libencode-arabic-perl Version: 14.2-1 Severity: serious User: debian-p...@lists.debian.org Usertags: perl-5.32-transition Control: block 968912 with -1 Control: affects -1 libelixirfm-perl It looks like Perl 5.32 caused a regression in the libencode-arabic-perl (and transitively

Processed: libencode-arabic-perl: autopkgtest regression with Perl 5.32: Useless use of /d modifier in transliteration operator

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > block 968912 with -1 Bug #968912 [release.debian.org] transition: perl 5.32 968912 was blocked by: 961157 961154 972275 974134 974021 960863 968913 974055 974063 964902 974016 961208 961155 974061 961152 972274 974058 968912 was not blocking any bugs. Added

Processed: unblock 974029 with 961154

2020-11-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unblock 974029 with 961154 Bug #974029 [src:perl] perl: add breaks on packages which were missing libpod-parser-perl deps 974029 was blocked by: 961155 961154 974029 was not blocking any bugs. Removed blocking bug(s) of 974029: 961154 > thanks

Bug#970136: marked as done (fcitx5-hangul: icon clashes with fcitx-hangul)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 15:18:37 + with message-id and subject line Bug#970136: fixed in fcitx5-hangul 5.0.0-1 has caused the Debian Bug report #970136, regarding fcitx5-hangul: icon clashes with fcitx-hangul to be marked as done. This means that you claim that the problem has

Bug#973115: marked as done (cfgrib: FTBFS: tests failed)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 15:18:20 + with message-id and subject line Bug#973115: fixed in cfgrib 0.9.8.4-2 has caused the Debian Bug report #973115, regarding cfgrib: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#973084: marked as done (docker.io: FTBFS: vendor/github.com/spf13/cobra/doc/man_docs.go:26:2: cannot find package "github.com/cpuguy83/go-md2man/md2man")

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 15:18:29 + with message-id and subject line Bug#973084: fixed in docker.io 19.03.13+dfsg1-4 has caused the Debian Bug report #973084, regarding docker.io: FTBFS: vendor/github.com/spf13/cobra/doc/man_docs.go:26:2: cannot find package

Bug#973526: marked as done (libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test")

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 15:18:53 + with message-id and subject line Bug#973526: fixed in libzeep 5.0.1-1 has caused the Debian Bug report #973526, regarding libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test" to be marked as done. This means that you claim that

Bug#972776: marked as done (talloc ftbfs with python3.9)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 15:19:11 + with message-id and subject line Bug#972776: fixed in talloc 2.3.1-2 has caused the Debian Bug report #972776, regarding talloc ftbfs with python3.9 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#973526: FTBFS due to SIGABRT while running HTTP server tests, bug #973526

2020-11-10 Thread Juhani Numminen
Hi, Maarten L. Hekkelman as the package maintainer asked for my help with bug #973526 but I have to forward his request to debian-mentors. The package libzeep failed to build on amd64, apparently because of a SIGABRT during its HTTP server test.

Bug#962615: sylfilter: glib error prevent filter working

2020-11-10 Thread Hideki Yamane
control: tags -1 - a11y control: notfound -1 0.8-6 control: severity -1 important Not sure what reason, sylfilter's db was corrupt and it was not introduced in this version, and it doesn't always happen so downgrade severity. -- Regards, Hideki Yamane henrich @

Processed: Re: sylfilter: glib error prevent filter working

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > tags -1 - a11y Bug #962615 [sylfilter] sylfilter: glib error prevent filter working Removed tag(s) a11y. > notfound -1 0.8-6 Bug #962615 [sylfilter] sylfilter: glib error prevent filter working No longer marked as found in versions sylfilter/0.8-6. > severity -1

Bug#974063: marked as pending in postgresql

2020-11-10 Thread Christoph Berg
Control: tag -1 pending Hello, Bug #974063 in postgresql 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:

Processed: Bug#974063 marked as pending in postgresql

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure Ignoring request to alter tags of bug #974063 to the same tags previously set -- 974063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974063 Debian Bug Tracking System

Bug#974134: marked as done (libdbd-csv-perl: test suite fails with libdbi-perl 1.643-3)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 15:04:19 + with message-id and subject line Bug#974134: fixed in libdbd-csv-perl 0.5500-2 has caused the Debian Bug report #974134, regarding libdbd-csv-perl: test suite fails with libdbi-perl 1.643-3 to be marked as done. This means that you claim that

Bug#970138: marked as done (fcitx5-skk: icon conflict with fcitx-skk)

2020-11-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Nov 2020 15:03:54 + with message-id and subject line Bug#970138: fixed in fcitx5-skk 5.0.0-1 has caused the Debian Bug report #970138, regarding fcitx5-skk: icon conflict with fcitx-skk to be marked as done. This means that you claim that the problem has been dealt

Bug#972776: marked as pending in talloc

2020-11-10 Thread Mathieu Parent
Control: tag -1 pending Hello, Bug #972776 in talloc 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#974063: marked as pending in postgresql

2020-11-10 Thread Christoph Berg
Control: tag -1 pending Hello, Bug #974063 in postgresql 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:

Processed: Bug#974063 marked as pending in postgresql

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #974063 [src:postgresql-13] postgresql-13: FTBFS: timetz test failure Ignoring request to alter tags of bug #974063 to the same tags previously set -- 974063: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974063 Debian Bug Tracking System

Processed: Bug#972776 marked as pending in talloc

2020-11-10 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #972776 [src:talloc] talloc ftbfs with python3.9 Added tag(s) pending. -- 972776: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972776 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: Add the help tag

2020-11-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 973526 +help Bug #973526 [src:libzeep] libzeep: FTBFS: 2 failures are detected in the test module "HTTP_Test" Added tag(s) help. > kthxbye Stopping processing here. Please contact me if you need assistance. -- 973526:

  1   2   >