Bug#963291: marked as done (nss-pem: FTBFS: pfind.c:279:10: error: ‘CKO_NETSCAPE_TRUST’ undeclared (first use in this function); did you mean ‘CKO_NSS_TRUST’?)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 15:50:16 + with message-id and subject line Bug#963291: fixed in nss-pem 1.0.6-1 has caused the Debian Bug report #963291, regarding nss-pem: FTBFS: pfind.c:279:10: error: ‘CKO_NETSCAPE_TRUST’ undeclared (first use in this function); did you mean

Bug#968022: sequitur-g2p: Unversioned Python removal in sid/bullseye

2020-08-06 Thread Andreas Beckmann
Source: sequitur-g2p Version: 0+r1668.r3-1 Severity: serious User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html

Processed: Bug#964541 marked as pending in flatpak

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #964541 [flatpak] flatpak: Wrong argument order for clone syscall seccomp filter on s390x Added tag(s) pending. -- 964541: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964541 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#964541: marked as pending in flatpak

2020-08-06 Thread Simon McVittie
Control: tag -1 pending Hello, Bug #964541 in flatpak 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#964541: marked as done (flatpak: Wrong argument order for clone syscall seccomp filter on s390x)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 22:33:39 + with message-id and subject line Bug#964541: fixed in flatpak 1.8.1-2 has caused the Debian Bug report #964541, regarding flatpak: Wrong argument order for clone syscall seccomp filter on s390x to be marked as done. This means that you claim

Processed: squidguard: diff for NMU version 1.6.0-1.1

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > tags 957841 + patch Bug #957841 [src:squidguard] squidguard: ftbfs with GCC-10 Added tag(s) patch. > tags 957841 + pending Bug #957841 [src:squidguard] squidguard: ftbfs with GCC-10 Added tag(s) pending. -- 957841:

Bug#957841: squidguard: diff for NMU version 1.6.0-1.1

2020-08-06 Thread Sudip Mukherjee
Control: tags 957841 + patch Control: tags 957841 + pending Dear maintainer, I've prepared an NMU for squidguard (versioned as 1.6.0-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru squidguard-1.6.0/debian/changelog

Processed: Bug#885265 marked as pending in chirp

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #885265 [src:chirp] chirp: Depends on unmaintained pygtk Ignoring request to alter tags of bug #885265 to the same tags previously set -- 885265: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885265 Debian Bug Tracking System Contact

Bug#885265: marked as pending in chirp

2020-08-06 Thread Christoph Berg
Control: tag -1 pending Hello, Bug #885265 in chirp 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#936299: marked as pending in chirp

2020-08-06 Thread Christoph Berg
Control: tag -1 pending Hello, Bug #936299 in chirp 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#936299 marked as pending in chirp

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #936299 [src:chirp] chirp: Python2 removal in sid/bullseye Ignoring request to alter tags of bug #936299 to the same tags previously set -- 936299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=936299 Debian Bug Tracking System Contact

Bug#954189: Upload approval for acmetool 0.2 in buster-backports

2020-08-06 Thread Ralph Giles
Hi, I wanted to request approval from the maintainer team to upload the acmetool 0.2.1-2 package currently in testing/unstable to buster- backports. The version currently in buster (0.0.63) only supports the deprecated ACME v1 protocol, which no longer works for new registrations, and will stop

Processed: Re: ifplugd: ftbfs with GCC-10

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + patch Bug #957355 [src:ifplugd] ifplugd: ftbfs with GCC-10 Added tag(s) patch. -- 957355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957355 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#885265: [py3] some fixes to get chirpw running with python3, Fixes #7431

2020-08-06 Thread Christoph Berg
Re: Arturo Borrero Gonzalez > I tested chirp from the upstream mercurial repository (py3 branch) today in > Debian testing bullseye, and I got it working with python3 with the attached > patch. Hi Arturo, thanks for picking this up. I had done some python3 hacking on chirp earlier this year,

Bug#957034: marked as done (bandwidthd: ftbfs with GCC-10)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 21:18:27 + with message-id and subject line Bug#957034: fixed in bandwidthd 2.0.1+cvs20090917-12 has caused the Debian Bug report #957034, regarding bandwidthd: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been

Bug#936299: marked as done (chirp: Python2 removal in sid/bullseye)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 21:18:33 + with message-id and subject line Bug#936299: fixed in chirp 1:20200227+py3+20200213-1 has caused the Debian Bug report #936299, regarding chirp: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#885265: marked as done (chirp: Depends on unmaintained pygtk)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 21:18:33 + with message-id and subject line Bug#885265: fixed in chirp 1:20200227+py3+20200213-1 has caused the Debian Bug report #885265, regarding chirp: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has

Bug#957355: ifplugd: ftbfs with GCC-10

2020-08-06 Thread Luis Paulo Linares
Control: tags -1 + patch Hi, the attached patch fixes the FTBFS with GCC 10. Regards, -- Luis Paulo (lpfll) diff -Nru ifplugd-0.28/debian/patches/09_fix-ftbfs-with-gcc10.patch ifplugd-0.28/debian/patches/09_fix-ftbfs-with-gcc10.patch ---

Bug#968027: dino-im: FTBFS: error: [...]/xmpp-vala/src/glib_fixes.vapi not found

2020-08-06 Thread Andreas Beckmann
Source: dino-im Version: 0.1.0+20200623.717d0b7-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) dino-im/experimental FTBFS on all architectures: https://buildd.debian.org/status/package.php?p=dino-im=experimental dh_auto_build -a

Bug#963871: marked as done (emacs-websocket: FTBFS without external DNS)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 23:18:30 + with message-id and subject line Bug#963871: fixed in emacs-websocket 1.12+18.g5aaf9d1-1 has caused the Debian Bug report #963871, regarding emacs-websocket: FTBFS without external DNS to be marked as done. This means that you claim that the

Bug#968030: e17: FTBFS during combined arch+indep build

2020-08-06 Thread Andreas Beckmann
Source: e17 Version: 0.24.2-3 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) Hi, e17/experimental FTBFS during a combined binary arch+indep build (i.e. the default dpkg-buildpackage mode), while it succeeds during separate arch and

Bug#966500: marked as done (python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6))

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 23:19:29 + with message-id and subject line Bug#966500: fixed in notcurses 1.6.11+dfsg.1-1 has caused the Debian Bug report #966500, regarding python3-notcurses: missing Breaks+Replaces: notcurses-bin (<< 1.6) to be marked as done. This means that you

Bug#968013: swi-prolog: time bomb in swi-prolog-test, and failing autopkgtest

2020-08-06 Thread Julien Cristau
Package: swi-prolog Severity: serious X-Debbugs-Cc: jcris...@debian.org Hi, swi-prolog autopkgtests are currently failing: https://ci.debian.net/data/autopkgtest/testing/amd64/s/swi-prolog/6535300/log.gz >From what I can tell, there's a step in the build process to generate test certs, which

Bug#957360: RFS: Bug#957360: insighttoolkit4: ftbfs with GCC-10

2020-08-06 Thread Étienne Mollier
Control: tag -1 pending Good day, This night's build of insighttoolkit 4.13.3 in the clean chroot went through, and test suite validated without particular issues. I pushed the part of my work fixing #957360 on Salsa: https://salsa.debian.org/med-team/insighttoolkit As is, it may not

Bug#967121: marked as done (bitz-server: Unversioned Python removal in sid/bullseye)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 16:23:45 + with message-id and subject line Bug#966418: Removed package(s) from unstable has caused the Debian Bug report #967121, regarding bitz-server: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the

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

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 17:35:07 + with message-id and subject line Bug#967054: Removed package(s) from unstable has caused the Debian Bug report #937970, regarding python-omniorb: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#899676: marked as done (python-omniorb: Invalid maintainer address pkg-corba-de...@lists.alioth.debian.org)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 17:35:07 + with message-id and subject line Bug#967054: Removed package(s) from unstable has caused the Debian Bug report #899676, regarding python-omniorb: Invalid maintainer address pkg-corba-de...@lists.alioth.debian.org to be marked as done. This

Bug#966779: marked as done (python-ntlm: Unversioned Python removal in sid/bullseye)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 17:33:22 + with message-id and subject line Bug#966802: Removed package(s) from unstable has caused the Debian Bug report #937959, regarding python-ntlm: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the

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

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 17:33:22 + with message-id and subject line Bug#966802: Removed package(s) from unstable has caused the Debian Bug report #937959, regarding python-ntlm: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#967232: xscreensaver: Unversioned Python removal in sid/bullseye

2020-08-06 Thread Tormod Volden
I think this is solely through the build dependency on libglade2-dev so this will be solved by xscreensaver getting rid of this dependency (bug #967892) or by libglade2 getting rid of its python dependency (bug #895517): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895517#14

Bug#964637: node-rollup: FTBFS: dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code 1

2020-08-06 Thread Xavier
Control: reassign -1 node-typescript-types FTBFS is due to @types/node which was upgraded to version 14.0.14 while we run nodejs 12

Bug#957043: marked as done (bitz-server: ftbfs with GCC-10)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 16:23:45 + with message-id and subject line Bug#966418: Removed package(s) from unstable has caused the Debian Bug report #957043, regarding bitz-server: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt

Bug#968023: munin: Unversioned Python removal in sid/bullseye

2020-08-06 Thread Andreas Beckmann
Source: munin Version: 2.999.14-1 Severity: serious User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html We will

Bug#967997: rdiff-backup: maintainer address invalid

2020-08-06 Thread Otto Kekäläinen
While researching this I only found packages that list the old group email: Maintainer: Python Applications Packaging Team - https://salsa.debian.org/python-team/applications/nitrotool/-/blob/master/debian/control -

Processed: tagging 966853

2020-08-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 966853 + fixed-upstream Bug #966853 [src:gophernicus] gophernicus: FTBFS: ld: file.o:/usr/include/tcpd.h:115: multiple definition of `deny_severity'; gophernicus.o:/usr/include/tcpd.h:115: first defined here Added tag(s) fixed-upstream. >

Bug#966870: marked as done (nsis: FTBFS: ld: build/urelease/halibut/bk_xhtml.o:./Docs/src/bin/halibut/halibut.h:272: multiple definition of `version'; build/urelease/halibut/biblio.o:./Docs/src/bin/ha

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 16:04:25 + with message-id and subject line Bug#966870: fixed in nsis 3.05-4 has caused the Debian Bug report #966870, regarding nsis: FTBFS: ld: build/urelease/halibut/bk_xhtml.o:./Docs/src/bin/halibut/halibut.h:272: multiple definition of `version';

Processed: Re: node-rollup: FTBFS: dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code 1

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 node-typescript-types Bug #964637 [src:node-rollup] node-rollup: FTBFS: dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code 1 Bug reassigned from package 'src:node-rollup' to 'node-typescript-types'. No longer marked as found

Bug#957820: marked as done (snap: ftbfs with GCC-10)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 19:03:55 + with message-id and subject line Bug#957820: fixed in snap 2013-11-29-10 has caused the Debian Bug report #957820, regarding snap: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#964637: [Pkg-javascript-devel] Bug#964637: node-rollup: FTBFS: dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code 1

2020-08-06 Thread Xavier
Le 06/08/2020 à 20:51, Xavier a écrit : > Control: reassign -1 node-typescript-types > > FTBFS is due to @types/node which was upgraded to version 14.0.14 while > we run nodejs 12 It's time to move @types/node from src:typescript-types to src:nodejs

Processed: tagging 966171

2020-08-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 966171 + fixed-upstream Bug #966171 [src:ydpdict] ydpdict: FTBFS with GCC 10: multiple definition of ... due to -fno-common Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#967178: marked as done (mrtrix: Unversioned Python removal in sid/bullseye)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 16:16:43 + with message-id and subject line Bug#966326: Removed package(s) from unstable has caused the Debian Bug report #967178, regarding mrtrix: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#949478: marked as done (browser-plugin-freshplayer-pepperflash might be useless now)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 17:21:14 + with message-id and subject line Bug#966474: Removed package(s) from unstable has caused the Debian Bug report #949478, regarding browser-plugin-freshplayer-pepperflash might be useless now to be marked as done. This means that you claim that

Bug#947288: marked as done (freshplayerplugin: FTBFS: No package 'libdrm' found)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 17:21:14 + with message-id and subject line Bug#966474: Removed package(s) from unstable has caused the Debian Bug report #947288, regarding freshplayerplugin: FTBFS: No package 'libdrm' found to be marked as done. This means that you claim that the

Bug#885265: [py3] some fixes to get chirpw running with python3, Fixes #7431

2020-08-06 Thread Arturo Borrero Gonzalez
Hi there! I tested chirp from the upstream mercurial repository (py3 branch) today in Debian testing bullseye, and I got it working with python3 with the attached patch. I was able to download the image from a baofeng UV-5RA, modify it and the upload it again. Please, consider merging the

Bug#960120: different error during build

2020-08-06 Thread Paolo Greppi
With this build: https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/915568#L2420 I get a different error while building: [17:58:12] Starting 'build'... 2420[17:58:13] Error: [BABEL] /builds/js-team/node-yarnpkg/debian/output/node-yarnpkg-1.22.4/src/api.js: Cannot find module

Bug#957645: marked as done (oroborus: ftbfs with GCC-10)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 19:19:58 + with message-id and subject line Bug#957645: fixed in oroborus 2.0.20+nmu1 has caused the Debian Bug report #957645, regarding oroborus: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#966702: marked as done (mongo-cxx-driver: maintainer address bounces)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 6 Aug 2020 15:13:22 -0400 with message-id <20200806191322.gf13...@connexer.com> and subject line Re: Bug#966702: mongo-cxx-driver: maintainer address bounces has caused the Debian Bug report #966702, regarding mongo-cxx-driver: maintainer address bounces to be marked as

Bug#968019: enhanceio: Unversioned Python removal in sid/bullseye

2020-08-06 Thread Andreas Beckmann
Source: enhanceio Version: 0+git20190417.5815670-1 Severity: serious Tags: sid bullseye User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in

Bug#968024: netpbm-free: Unversioned Python removal in sid/bullseye

2020-08-06 Thread Andreas Beckmann
Source: netpbm-free Version: 2:10.78.05-0.1 Severity: serious User: debian-pyt...@lists.debian.org Usertags: py2unversioned Python2 becomes end-of-live upstream, and Debian aims to remove Python2 from the distribution, as discussed in https://lists.debian.org/debian-python/2019/07/msg00080.html

Processed: Bug#957587 marked as pending in ncrack

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

Bug#957587: marked as pending in ncrack

2020-08-06 Thread Marcos Fouces
Control: tag -1 pending Hello, Bug #957587 in ncrack 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#957798: marked as done (silversearcher-ag: ftbfs with GCC-10)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 18:18:30 + with message-id and subject line Bug#957798: fixed in silversearcher-ag 2.2.0+git20200805-1 has caused the Debian Bug report #957798, regarding silversearcher-ag: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem

Bug#957995: marked as done (xscorch: ftbfs with GCC-10)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 19:34:06 + with message-id and subject line Bug#957995: fixed in xscorch 0.2.1-1+nmu4 has caused the Debian Bug report #957995, regarding xscorch: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Re: zsnapd: Python2 removal in sid/bullseye

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #943302 [src:zsnapd] zsnapd: Python2 removal in sid/bullseye Severity set to 'serious' from 'normal' -- 943302: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943302 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#967955: marked as done (golang-github-unknwon-cae: CVE-2020-7664)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 17:19:32 + with message-id and subject line Bug#966453: Removed package(s) from unstable has caused the Debian Bug report #967955, regarding golang-github-unknwon-cae: CVE-2020-7664 to be marked as done. This means that you claim that the problem has been

Bug#967956: marked as done (golang-github-unknwon-cae: CVE-2020-7668)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 17:19:32 + with message-id and subject line Bug#966453: Removed package(s) from unstable has caused the Debian Bug report #967956, regarding golang-github-unknwon-cae: CVE-2020-7668 to be marked as done. This means that you claim that the problem has been

Bug#956975: marked as done (acfax: ftbfs with GCC-10)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 17:31:13 + with message-id and subject line Bug#966658: Removed package(s) from unstable has caused the Debian Bug report #956975, regarding acfax: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: affects 964637

2020-08-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 964637 rollup Bug #964637 [src:node-rollup] node-rollup: FTBFS: dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code 1 Added indication that 964637 affects rollup > thanks Stopping processing here. Please

Processed: RFS: Bug#957360: insighttoolkit4: ftbfs with GCC-10

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

Processed: tagging 967173, tagging 968019, tagging 957599, tagging 967032, found 967032 in 14.4.0~dfsg-2

2020-08-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 967173 + experimental Bug #967173 [src:mediaelement] mediaelement: Unversioned Python removal in sid/bullseye Added tag(s) experimental. > tags 968019 = Bug #968019 [src:enhanceio] enhanceio: Unversioned Python removal in sid/bullseye

Bug#957698: marked as done (pommed: ftbfs with GCC-10)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 20:25:57 + with message-id and subject line Bug#957698: fixed in pommed 1.39~dfsg-5.1 has caused the Debian Bug report #957698, regarding pommed: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: owner 957122

2020-08-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > owner 957122 woodrow.s...@gmail.com Bug #957122 [src:davfs2] davfs2: ftbfs with GCC-10 Owner recorded as woodrow.s...@gmail.com. > thanks Stopping processing here. Please contact me if you need assistance. -- 957122:

Bug#968030: marked as done (e17: FTBFS during combined arch+indep build)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 05:33:27 + with message-id and subject line Bug#968030: fixed in e17 0.24.2-4 has caused the Debian Bug report #968030, regarding e17: FTBFS during combined arch+indep build to be marked as done. This means that you claim that the problem has been dealt

Bug#957710: marked as done (proxychains: ftbfs with GCC-10)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 04:49:08 + with message-id and subject line Bug#957710: fixed in proxychains 3.1-9 has caused the Debian Bug report #957710, regarding proxychains: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#957347: marked as done (hydra: ftbfs with GCC-10)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 03:04:09 + with message-id and subject line Bug#957347: fixed in hydra 9.1-1 has caused the Debian Bug report #957347, regarding hydra: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#968030: e17: FTBFS during combined arch+indep build

2020-08-06 Thread Ross Vandegrift
On Fri, Aug 07, 2020 at 01:17:29AM +0200, Andreas Beckmann wrote: > e17/experimental FTBFS during a combined binary arch+indep build (i.e. the > default dpkg-buildpackage mode), while it succeeds during separate arch and > indep builds (dpkg-buildpackage -B, dpkg-buildpackage -A; as done by the >

Bug#967964: marked as pending in unison

2020-08-06 Thread Stéphane Glondu
Control: tag -1 pending Hello, Bug #967964 in unison 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#967964 marked as pending in unison

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #967964 [unison-2.48] unison-2.48: file conflict with unison -4 Added tag(s) pending. -- 967964: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967964 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#966939: marked as done (fdb: FTBFS: dh_sphinxdoc: error: debian/python-fdb-doc/usr/share/doc/python-fdb-doc/html/search.html does not load searchindex.js)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 6 Aug 2020 09:37:49 +0200 with message-id <20200806073749.GA321521@pisco.westfalen.local> and subject line Re: fdb: FTBFS: dh_sphinxdoc: error: debian/python-fdb-doc/usr/share/doc/python-fdb-doc/html/search.html does not load searchindex.js has caused the Debian Bug

Bug#966692: stunnel4: FTBFS because of test hang

2020-08-06 Thread Peter Pentchev
On Thu, Aug 06, 2020 at 03:23:08AM +0200, Michał Mirosław wrote: > On Thu, Aug 06, 2020 at 03:10:55AM +0200, Michał Mirosław wrote: > > On Thu, Aug 06, 2020 at 02:39:42AM +0200, Michał Mirosław wrote: > > > On Thu, Aug 06, 2020 at 03:16:35AM +0300, Peter Pentchev wrote: > > > > On Thu, Aug 06,

Bug#936873: libhdate: diff for NMU version 1.6.02-2.1

2020-08-06 Thread Boruch Baum
On 2020-08-06 02:13, Lior Kaplan wrote: >We're still alive/here Excellent to hear! >and any help is much appreciated Contact me (off this thread) with details of anything I can be of help. -- hkp://keys.gnupg.net CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0

Bug#957806: marked as done (skypat: ftbfs with GCC-10)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 07:33:34 + with message-id and subject line Bug#957806: fixed in skypat 3.1.1-4 has caused the Debian Bug report #957806, regarding skypat: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#967964: marked as done (unison-2.48: file conflict with unison -4)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 07:33:41 + with message-id and subject line Bug#967964: fixed in unison-2.48 2.48.4-6 has caused the Debian Bug report #967964, regarding unison-2.48: file conflict with unison -4 to be marked as done. This means that you claim that the problem has been

Bug#963737: ilias...@debian.org

2020-08-06 Thread Ilias Tsitsimpis
On Thu, Aug 06, 2020 at 11:42AM, peter green wrote: > hi, highlighting-kate was just removed from testing at your request, but > carettah still build-depends on it in both testing and > unstable. > > Should I go ahead and file a rc bug against carettah Good catch. I open an RC bug against

Bug#967953: ifupdown2

2020-08-06 Thread Julien Fortin
Hi Christoph, On Thu, Aug 6, 2020 at 12:27 PM Christoph Egger wrote: > > Hi > > > We are now looking for a new debian sponsor to upload our latest > > version to the debian repository. > > I guess I can help there for now but better don't rely on me for long-term > sponsoring. What exactly

Bug#966996: marked as done (python-cytoolz: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 07:48:29 + with message-id and subject line Bug#966996: fixed in python-cytoolz 0.10.1-2 has caused the Debian Bug report #966996, regarding python-cytoolz: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2 to be marked as

Bug#963362: marked as pending in guice

2020-08-06 Thread Emmanuel Bourg
Control: tag -1 pending Hello, Bug #963362 in guice 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#963362 marked as pending in guice

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #963362 [src:guice] guice: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project guice-throwingproviders: Compilation failure Added tag(s) pending. -- 963362:

Processed: Re: jimfs: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project jimfs: Compilation failure

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > tags -1 help Bug #963396 [src:jimfs] jimfs: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project jimfs: Compilation failure Added tag(s) help. -- 963396:

Bug#963396: jimfs: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project jimfs: Compilation failure

2020-08-06 Thread Andreas Tille
Control: tags -1 help Hi, I was running routine-update on jimfs repository since it seems to lack some love (not even Salsa URLs in VCS-fields) but the build error remains (for sure since I did not changed the code). I've checked upstream[1] which says: 1.1 @cgdecker released this on Feb

Processed: Bug#963443 marked as pending in apache-curator

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #963443 [src:apache-curator] apache-curator: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project curator-framework: Compilation failure: Compilation failure: Added

Bug#967953: ifupdown2

2020-08-06 Thread Christoph Egger
Hi > We are now looking for a new debian sponsor to upload our latest > version to the debian repository. I guess I can help there for now but better don't rely on me for long-term sponsoring. What exactly would you want uploaded? Do you have the package somewhere? or github HEAD? Christoph

Bug#963443: marked as done (apache-curator: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project curator-framework: Compilati

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 10:33:28 + with message-id and subject line Bug#963443: fixed in apache-curator 2.7.1-3 has caused the Debian Bug report #963443, regarding apache-curator: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile

Bug#963737: ilias...@debian.org

2020-08-06 Thread peter green
Ilias Tsitsimpis wrote: We should make sure that anyone using this package has migrated to skylighting and then remove it. hi, highlighting-kate was just removed from testing at your request, but carettah still build-depends on it in both testing and unstable. Should I go ahead and file a rc

Processed: Re: Bug#964541: flatpak: Wrong argument order for clone syscall seccomp filter on s390x

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + upstream Bug #964541 [flatpak] flatpak: Wrong argument order for clone syscall seccomp filter on s390x Added tag(s) upstream. > clone -1 -2 -3 Bug #964541 [flatpak] flatpak: Wrong argument order for clone syscall seccomp filter on s390x Bug 964541 cloned

Bug#964541: flatpak: Wrong argument order for clone syscall seccomp filter on s390x

2020-08-06 Thread Simon McVittie
Control: tags -1 + upstream Control: clone -1 -2 -3 Control: unblock 964150 by -2 Control: unblock 964150 by -3 Control: forwarded -1 https://github.com/flatpak/flatpak/pull/3777 Control: severity -2 normal Control: reassign -2 src:webkit2gtk 2.28.4-1 Control: retitle -2 webkit2gtk: Wrong argument

Bug#967991: glirc, build-depends on package which is not in testing

2020-08-06 Thread peter green
Package: glirc Version: 2.35-1 Severity: serious Justification: rc policy: "packages must be buildable within the same release" glirc can no longer be built in testing because haskell-regex-tdfa is no longer present in testing. Ilias Tsitsimpis has filed a bug report against the package saying

Processed: cloning 966765, retitle -1 to obs-build: update to the latest upstream version ...

2020-08-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 966765 -1 Bug #966765 [src:obs-build] obs-build: Unversioned Python removal in sid/bullseye Bug 966765 cloned as bug 967976 > retitle -1 obs-build: update to the latest upstream version Bug #967976 [src:obs-build] obs-build: Unversioned

Bug#954684: marked as pending in ant-contrib

2020-08-06 Thread Emmanuel Bourg
Control: tag -1 pending Hello, Bug #954684 in ant-contrib 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#954684 marked as pending in ant-contrib

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #954684 [src:ant-contrib] ant-contrib: FTBFS: tests failed Added tag(s) pending. -- 954684: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954684 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#963385: marked as pending in airlift-airline

2020-08-06 Thread Emmanuel Bourg
Control: tag -1 pending Hello, Bug #963385 in airlift-airline 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#963385 marked as pending in airlift-airline

2020-08-06 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #963385 [src:airlift-airline] airlift-airline: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project airline: Compilation failure Added tag(s) pending. -- 963385:

Processed: severity of 804267 is serious

2020-08-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 804267 serious Bug #804267 [mercurial-crecord] mercurial-crecord: remove mercurial-crecord from the archive Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#957032: marked as done (ayatana-indicator-printers: ftbfs with GCC-10)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 12:48:31 + with message-id and subject line Bug#957032: fixed in ayatana-indicator-printers 0.1.10-1 has caused the Debian Bug report #957032, regarding ayatana-indicator-printers: ftbfs with GCC-10 to be marked as done. This means that you claim that the

Bug#967965: marked as done (astropy: FTBFS with scipy 1.5: [doctest] astropy.stats.funcs.binom_conf_interval failed)

2020-08-06 Thread Debian Bug Tracking System
Your message dated Thu, 06 Aug 2020 13:03:29 + with message-id and subject line Bug#967965: fixed in astropy 4.0.1+post1-4 has caused the Debian Bug report #967965, regarding astropy: FTBFS with scipy 1.5: [doctest] astropy.stats.funcs.binom_conf_interval failed to be marked as done. This

Processed: Re: Bug#967991: glirc, build-depends on package which is not in testing

2020-08-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 967991 2.35-1 Bug #967991 [glirc] glirc, build-depends on package which is not in testing No longer marked as found in versions glirc/2.35-1. > found 967991 2.32-1 Bug #967991 [glirc] glirc, build-depends on package which is not in

Bug#967997: rdiff-backup: maintainer address invalid

2020-08-06 Thread Ansgar
Source: rdiff-backup Version: 2.0.5-1 Severity: serious X-Debbugs-Cc: o...@debian.org The maintainer address is invalid, see below. Ansgar Forwarded Message > This message was created automatically by mail delivery software. > > A message that you sent could not be delivered

Bug#966972: [in-toto-dev] Bug#966972: in-toto: FTBFS: ValueError: SSH supports only 1024 bit DSA keys

2020-08-06 Thread Holger Levsen
hey Lukas, On Thu, Aug 06, 2020 at 02:03:00PM +0200, Lukas Puehringer wrote: > FYI: https://github.com/secure-systems-lab/securesystemslib/pull/264 fixes the > issue upstream. nice. once it's released we should get this new version into unstable! -- cheers, Holger

Bug#967999: ruby-data-migrate: ftbfs and autopkgtest failure with rails 6

2020-08-06 Thread Pirate Praveen
Package: ruby-data-migrate Version: 5.3.1-1 Severity: serious User: pkg-ruby-extras-maintain...@lists.alioth.debian.org Usertags: rails6-transition Hi, This package's autopkgtest and rebuilds failed with rails 6. There is new upstream version which fixes this issue. Relevant errors,

Bug#967991: glirc, build-depends on package which is not in testing

2020-08-06 Thread Clint Adams
On Thu, Aug 06, 2020 at 11:20:00AM +0100, peter green wrote: > glirc can no longer be built in testing because haskell-regex-tdfa is no > longer > present in testing. Ilias Tsitsimpis has filed a bug report against the > package > saying he intends to remove it and asked the release team to

  1   2   >