Bug#966655: Orthanc and all its plugins are getting removed from testing

2020-08-09 Thread Sébastien Jodogne
Dear all, Because of the bug #966655 [1], and because of the fact that orthanc-1.7.2+dfsg-2 is pending in the NEW queue [2], I cannot commit the fix regarding the missing build dependency on tzdata until the NEW packages get accepted. But, as #966655 is tagged as serious, the entire Orthanc

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

2020-08-09 Thread Peter Colberg
Hi Ralph, On Thu, Aug 06, 2020 at 03:38:33PM -0700, Ralph Giles wrote: > 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. Please feel free to go ahead with backporting acmetool and needed golang

Bug#966575: grub-pc: error: symbol `grub_calloc' not found.

2020-08-09 Thread Karl Schmidt
Triggered this with an apt upgrade dist-upgrade APT::Default-Release "buster"; grub-pc 2.02+dfsg1-20+deb10u2 ,.,. This system had mirrored drives - Had to boot off a thumbdrive - enter rescue - when it asked for the boot drive - had to tell it to build raid - then select the raid (

Processed: bug 966985 is forwarded to https://github.com/mozilla/bleach/issues/543

2020-08-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 966985 https://github.com/mozilla/bleach/issues/543 Bug #966985 [src:python-bleach] python-bleach: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 Set Bug forwarded-to-address to

Processed: py2removal bugs severity updates - 2020-08-10 02:34:03.162662+00:00

2020-08-09 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

Bug#939259: webcheck: Python2 removal in sid/bullseye

2020-08-09 Thread Sandro Tosi
that sounds good, i've opened #968160 to remove webcheck from Debian; it can be re-introduced once its python3 port is completed On Sun, Aug 9, 2020 at 10:10 AM Arthur de Jong wrote: > > On Mon, 2020-07-27 at 00:42 -0400, Sandro Tosi wrote: > > 9 months have passed and i dont see any progress on

Bug#966908: marked as done (mailfilter: FTBFS: rc.tab.c:173:10: fatal error: rc.tab.h: No such file or directory)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Mon, 10 Aug 2020 00:18:39 + with message-id and subject line Bug#966908: fixed in mailfilter 0.8.7-1 has caused the Debian Bug report #966908, regarding mailfilter: FTBFS: rc.tab.c:173:10: fatal error: rc.tab.h: No such file or directory to be marked as done. This means

Bug#968157: src:haskell-cborg: testsuite fails due to bus errors on armhf

2020-08-09 Thread Clint Adams
Package: src:haskell-cborg Version: 0.2.3.0-1 Severity: serious Unlike some other armhf bus errors, this problem does not go away when compiler optimization is disabled.

Bug#963772: marked as done (nodejs breaks node-leveldown autopkgtest: Test: require Aborted)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 23:03:28 + with message-id and subject line Bug#966008: fixed in nodejs 14.7.0~dfsg-1 has caused the Debian Bug report #966008, regarding nodejs breaks node-leveldown autopkgtest: Test: require Aborted to be marked as done. This means that you claim that

Bug#967032: marked as done (nodejs: Unversioned Python removal in sid/bullseye)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 23:03:28 + with message-id and subject line Bug#967032: fixed in nodejs 14.7.0~dfsg-1 has caused the Debian Bug report #967032, regarding nodejs: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#963935: marked as done (node-modern-syslog: missing versioned dependency relation?: modern-syslog/build/Release/core.node',was compiled against a different Node.js version)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 23:03:28 + with message-id and subject line Bug#966008: fixed in nodejs 14.7.0~dfsg-1 has caused the Debian Bug report #966008, regarding node-modern-syslog: missing versioned dependency relation?: modern-syslog/build/Release/core.node',was compiled

Bug#966008: marked as done (libnode72 needs Breaks: libnode64)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 23:03:28 + with message-id and subject line Bug#966008: fixed in nodejs 14.7.0~dfsg-1 has caused the Debian Bug report #966008, regarding libnode72 needs Breaks: libnode64 to be marked as done. This means that you claim that the problem has been dealt

Bug#963769: marked as done (nodejs breaks node-iconv-lite autopkgtest: malloc(): invalid next size (unsorted))

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 23:03:28 + with message-id and subject line Bug#966008: fixed in nodejs 14.7.0~dfsg-1 has caused the Debian Bug report #966008, regarding nodejs breaks node-iconv-lite autopkgtest: malloc(): invalid next size (unsorted) to be marked as done. This means

Bug#963065: marked as done (nodejs breaks node-encoding autopkgtest: Encoding not recognized: 'ISO-2022-JP' (searched as: 'iso2022jp'))

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 23:03:28 + with message-id and subject line Bug#966008: fixed in nodejs 14.7.0~dfsg-1 has caused the Debian Bug report #966008, regarding nodejs breaks node-encoding autopkgtest: Encoding not recognized: 'ISO-2022-JP' (searched as: 'iso2022jp') to be

Bug#967017: marked as done (request-tracker4: FTBFS: GPG test failures)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 22:33:58 + with message-id and subject line Bug#967017: fixed in request-tracker4 4.4.4-2 has caused the Debian Bug report #967017, regarding request-tracker4: FTBFS: GPG test failures to be marked as done. This means that you claim that the problem has

Processed: hardinfo: diff for NMU version 0.5.1+git20180227-2.1

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

Bug#957327: hardinfo: diff for NMU version 0.5.1+git20180227-2.1

2020-08-09 Thread Sudip Mukherjee
Control: tags 957327 + patch Control: tags 957327 + pending Dear maintainer, I've prepared an NMU for hardinfo (versioned as 0.5.1+git20180227-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru

Bug#957981: marked as done (xgammon: ftbfs with GCC-10)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 21:03:35 + with message-id and subject line Bug#957981: fixed in xgammon 0.99.1128-4 has caused the Debian Bug report #957981, regarding xgammon: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#943302: zsnapd: Python2 removal in sid/bullseye

2020-08-09 Thread Andreas Beckmann
Followup-For: Bug #943302 Control: found -1 0.8.11h-2 zsnapd FTBFS in a minimal up-to-date sid chroot due to some more changes in the python ecosystem: fakeroot debian/rules clean dh clean dh_auto_clean dh_auto_clean: warning: Please use the third-party "pybuild" build system instead of

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

2020-08-09 Thread Debian Bug Tracking System
Processing control commands: > found -1 0.8.11h-2 Bug #943302 {Done: Matthew Grant } [src:zsnapd] zsnapd: Python2 removal in sid/bullseye Marked as found in versions zsnapd/0.8.11h-2; no longer marked as fixed in versions zsnapd/0.8.11h-2 and reopened. -- 943302:

Bug#966653: gitlab: [BUG] Segmentation fault at 0x0000000000000000

2020-08-09 Thread Antoine Le Gonidec
I got bitten by the same crash during a system upgrade from Buster 10.4 to Buster 10.5, on a system using the Buster Fasttrack repositories. Reverting the older versions of the following packages allowed me to avoid the crash: - ruby-google-protobuf:amd64=3.11.4-5+fto10+1 -

Bug#968149: mysql-router-dbgsym,mysql-server-core-8.0-dbgsym: file conflict due to shared build-id

2020-08-09 Thread Andreas Beckmann
Package: mysql-router-dbgsym,mysql-server-core-8.0-dbgsym Version: 8.0.20-1~exp1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install because it tries to overwrite other packages files. >From the attached

Bug#957286: marked as done (gnomekiss: ftbfs with GCC-10)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 19:33:28 + with message-id and subject line Bug#957286: fixed in gnomekiss 2.0-6.1 has caused the Debian Bug report #957286, regarding gnomekiss: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#966653: See if the same error comes with gitlab 13.2.3 which I just uploaded

2020-08-09 Thread Pirate Praveen
From the previous comment on this bug, it appears to be caused by ruby-google-protobuf and ruby-grpc. Can you try the new gitlab version I just uploaded?

Bug#957684: marked as done (pick: ftbfs with GCC-10)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 17:49:00 + with message-id and subject line Bug#957684: fixed in pick 2.0.2-1.1 has caused the Debian Bug report #957684, regarding pick: 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#957928: marked as done (welcome2l: ftbfs with GCC-10)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 17:34:13 + with message-id and subject line Bug#957928: fixed in welcome2l 3.04-27.1 has caused the Debian Bug report #957928, regarding welcome2l: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#968130: Acknowledgement (iwd: Doesn't start at boot for beowulf)

2020-08-09 Thread Job Bautista
Ah shoot, sorry, please close this bug. I sent it to the wrong address... Sent with ProtonMail Secure Email. ‐‐‐ Original Message ‐‐‐ On Sunday, August 9, 2020 8:57 PM, Debian Bug Tracking System wrote: > Thank you for filing a new Bug report with Debian. > > You can follow progress

Bug#957515: marked as done (macopix: ftbfs with GCC-10)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 17:00:09 + with message-id and subject line Bug#957515: fixed in macopix 3.4.0+dfsg.1-1 has caused the Debian Bug report #957515, regarding macopix: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#968130: iwd: Doesn't start at boot for beowulf

2020-08-09 Thread Job Bautista
Package: iwd Version: 0.14-2 Severity: grave Tags: patch Justification: renders package unusable iwd 0.14-2 doesn't get started by init. I have to manually start it. This can be fixed easily by adding an sysvinit script at the debian directory. I have a fix available at

Processed: closing 961203

2020-08-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 961203 2.13.0-1 Bug #961203 [src:ensmallen] ensmallen FTBFS on armel/armhf/mipsel: test failure Marked as fixed in versions ensmallen/2.13.0-1. Bug #961203 [src:ensmallen] ensmallen FTBFS on armel/armhf/mipsel: test failure Marked Bug as

Bug#968047: marked as done (texlive-fonts-extra-links: missing Breaks+Replaces: texlive-fonts-extra (<< 2020.20200804))

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:52:49 + with message-id and subject line Bug#968047: fixed in texlive-extra 2020.20200804-2 has caused the Debian Bug report #968047, regarding texlive-fonts-extra-links: missing Breaks+Replaces: texlive-fonts-extra (<< 2020.20200804) to be marked as

Bug#967912: marked as done (texlive-luatex: file conflict with old texlive-latex-extra package)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:50:34 + with message-id and subject line Bug#967912: fixed in texlive-base 2020.20200804-2 has caused the Debian Bug report #967912, regarding texlive-luatex: file conflict with old texlive-latex-extra package to be marked as done. This means that you

Bug#963658: marked as done (urwid: FTBFS with Sphinx 3.1: Theme error: An error happened in rendering the page index.)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:35:59 + with message-id and subject line Bug#963658: fixed in urwid 2.1.1-1 has caused the Debian Bug report #963658, regarding urwid: FTBFS with Sphinx 3.1: Theme error: An error happened in rendering the page index. to be marked as done. This means

Bug#957460: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables to be

Bug#957459: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables to be

Bug#957461: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables to be

Bug#957458: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables to be

Bug#957457: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables to be

Bug#957290: marked as done (gnuais: ftbfs with GCC-10)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:35:05 + with message-id and subject line Bug#957290: fixed in gnuais 0.3.3-9 has caused the Debian Bug report #957290, regarding gnuais: 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#957456: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables to be

Bug#957455: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables to be

Bug#957453: marked as done (libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:35:52 + with message-id and subject line Bug#957453: fixed in libomxil-bellagio 0.9.3-5 has caused the Debian Bug report #957453, regarding libomxil-bellagio-dev: /usr/include/bellagio/omx_reference_resource_manager.h defines global variables to be

Bug#963658: marked as pending in urwid

2020-08-09 Thread Jochen Sprickerhof
Control: tag -1 pending Hello, Bug #963658 in urwid 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#963658 marked as pending in urwid

2020-08-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #963658 [src:urwid] urwid: FTBFS with Sphinx 3.1: Theme error: An error happened in rendering the page index. Added tag(s) pending. -- 963658: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=963658 Debian Bug Tracking System Contact

Bug#966171: marked as done (ydpdict: FTBFS with GCC 10: multiple definition of ... due to -fno-common)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:20:15 + with message-id and subject line Bug#966171: fixed in ydpdict 1.0.3-1 has caused the Debian Bug report #966171, regarding ydpdict: FTBFS with GCC 10: multiple definition of ... due to -fno-common to be marked as done. This means that you claim

Bug#968106: [Debian-on-mobile-maintainers] Bug#968106: phosh: Shell doesn't start

2020-08-09 Thread Guido Günther
Hi, On Sat, Aug 08, 2020 at 08:09:24PM +0200, Michel Le Bihan via Debian-on-mobile-maintainers wrote: > Package: phosh > Version: 0.4.3-1 > Severity: grave > Justification: renders package unusable > > Hello, > > On a freshly created Debian sid live system: > ``` > sudo mmdebstrap

Bug#966437: marked as done (bambam: autopkgtest failure with imagemagick 8:6.9.11.24+dfsg-1)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:03:29 + with message-id and subject line Bug#966437: fixed in bambam 1.0.2+dfsg-1 has caused the Debian Bug report #966437, regarding bambam: autopkgtest failure with imagemagick 8:6.9.11.24+dfsg-1 to be marked as done. This means that you claim that

Bug#966438: marked as done (src:bambam: Autopkgtest fail wiht newer imagemagick*)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:03:29 + with message-id and subject line Bug#966437: fixed in bambam 1.0.2+dfsg-1 has caused the Debian Bug report #966437, regarding src:bambam: Autopkgtest fail wiht newer imagemagick* to be marked as done. This means that you claim that the problem

Bug#966437: marked as done (bambam: autopkgtest failure with imagemagick 8:6.9.11.24+dfsg-1)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:03:29 + with message-id and subject line Bug#966438: fixed in bambam 1.0.2+dfsg-1 has caused the Debian Bug report #966438, regarding bambam: autopkgtest failure with imagemagick 8:6.9.11.24+dfsg-1 to be marked as done. This means that you claim that

Bug#966438: marked as done (src:bambam: Autopkgtest fail wiht newer imagemagick*)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 15:03:29 + with message-id and subject line Bug#966438: fixed in bambam 1.0.2+dfsg-1 has caused the Debian Bug report #966438, regarding src:bambam: Autopkgtest fail wiht newer imagemagick* to be marked as done. This means that you claim that the problem

Processed: py2removal bugs severity updates - 2020-08-09 14:34:05.556198+00:00

2020-08-09 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

Bug#939259: webcheck: Python2 removal in sid/bullseye

2020-08-09 Thread Arthur de Jong
On Mon, 2020-07-27 at 00:42 -0400, Sandro Tosi wrote: > 9 months have passed and i dont see any progress on this porting to > python3: last commits on https://arthurdejong.org/git/webcheck are > from 2013 (!) > > Are you still interested in this program (which you wrote)? should we > just remove

Bug#966085: gitlab contains git bundles with non-free code, unlisted code

2020-08-09 Thread Pirate Praveen
Since there are many templates here, I have started https://git.fosscommunity.in/debian-ruby/TaskTracker/-/issues/168 to track status of each template.

Bug#968131: hdate-applet FTBFS with gcc-10

2020-08-09 Thread Helmut Grohne
Source: hdate-applet Version: 0.15.11-3 Severity: serious Tags: ftbfs hdate-applet fails to build from source in unstable: | gcc -g -O2 -ffile-prefix-map=/build/1st/hdate-applet-0.15.11=. -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro -o ghcal ghcal-main.o

Processed: Re: Bug#510368: libgamin0: libfam shlib dependency wrongly set to libfam0

2020-08-09 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #510368 [libgamin0] libgamin0: libfam shlib dependency wrongly set to libfam0 Severity set to 'serious' from 'important' -- 510368: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=510368 Debian Bug Tracking System Contact

Bug#967118: 0ad: Unversioned Python removal in sid/bullseye

2020-08-09 Thread Simon McVittie
Control: forwarded 936101 https://trac.wildfiregames.com/ticket/5694 Control: tags 936101 + upstream Note that "unversioned Python removal" is not the same as "Python 2 removal". At this point it seems likely that Python 2 will remain in the Debian archive for bullseye, but with a drastically

Processed: bug 956967 is forwarded to https://trac.wildfiregames.com/changeset/23794

2020-08-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 956967 https://trac.wildfiregames.com/changeset/23794 Bug #956967 [src:0ad] 0ad: FTBFS with gcc-10: undefined reference to `_xmlNode* FArchiveXML::AddPhysicsParameter(_xmlNode*, char const*, FCDParameterAnimatableT&)' Set Bug

Processed (with 1 error): unarchive 968130

2020-08-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 968130 Bug #968130 {Done: Job Bautista } [iwd] iwd: Doesn't start at boot for beowulf Unarchived Bug 968130 > tags 968130 = invalid Unknown tag/s: invalid. Recognized are: patch wontfix moreinfo unreproducible help security upstream

Processed: bug 963636 is forwarded to https://lore.kernel.org/lkml/20200809132327.GA145573@eldamar.local/T/#u

2020-08-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 963636 > https://lore.kernel.org/lkml/20200809132327.GA145573@eldamar.local/T/#u Bug #963636 [src:linux] linux: FTBFS with Sphinx 3.1: Could not import extension cdomain (exception: cannot import name 'c_funcptr_sig_re' from

Processed: archive 968130

2020-08-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > archive 968130 Bug #968130 {Done: Job Bautista } [iwd] iwd: Doesn't start at boot for beowulf archived 968130 to archive/30 (from 968130) > End of message, stopping processing here. Please contact me if you need assistance. -- 968130:

Bug#968130: marked as done (iwd: Doesn't start at boot for beowulf)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 13:00:46 + with message-id and subject line Close 968130 has caused the Debian Bug report #968130, regarding iwd: Doesn't start at boot for beowulf to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Processed: tagging 963636

2020-08-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 963636 + upstream Bug #963636 [src:linux] linux: FTBFS with Sphinx 3.1: Could not import extension cdomain (exception: cannot import name 'c_funcptr_sig_re' from 'sphinx.domains.c' (/usr/lib/python3/dist-packages/sphinx/domains/c.py))

Bug#968127: view3dscene: FTBFS with fpc 3.2.0

2020-08-09 Thread Graham Inggs
Source: view3dscene Version: 3.18.0-4 Severity: serious Tags: ftbfs bullseye sid X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net Hi Maintainer As can be seen on reproducible builds [1], this package FTBFS since the upload of fpc 3.2.0+dfsg-5 to unstable. I've copied what I hope is the

Bug#968126: mricron: FTBFS with fpc 3.2.0

2020-08-09 Thread Graham Inggs
Source: mricron Version: 0.20140804.1~dfsg.1-3 Severity: serious Tags: ftbfs bullseye sid X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net Hi Maintainer As can be seen on reproducible builds [1], this package FTBFS since the upload of fpc 3.2.0+dfsg-5 to unstable. I've copied what I hope

Bug#957587: marked as done (ncrack: ftbfs with GCC-10)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 12:04:34 + with message-id and subject line Bug#957587: fixed in ncrack 0.7+debian-2 has caused the Debian Bug report #957587, regarding ncrack: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#968125: hedgewars: FTBFS with fpc 3.2.0

2020-08-09 Thread Graham Inggs
Source: hedgewars Version: 1.0.0-9 Severity: serious Tags: ftbfs bullseye sid X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net Hi Maintainer As can be seen on reproducible builds [1], this package FTBFS since the upload of fpc 3.2.0+dfsg-5 to unstable. I've copied what I hope is the

Bug#968124: diffoscope: FTBFS with fpc 3.2.0

2020-08-09 Thread Graham Inggs
Source: diffoscope Version: 155 Severity: serious Tags: ftbfs sid X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net Hi Maintainer As can be seen on reproducible builds [1], this package FTBFS since the upload of fpc 3.2.0+dfsg-5 to unstable. I've copied what I hope is the relevant part of

Bug#968121: ddrescueview: FTBFS with fpc 3.2.0

2020-08-09 Thread Graham Inggs
Source: ddrescueview Version: 0.4~alpha3-3 Severity: serious Tags: ftbfs bullseye sid X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net Hi Maintainer As can be seen on reproducible builds [1], this package FTBFS since the upload of fpc 3.2.0+dfsg-5 to unstable. I've copied what I hope is

Processed: Bumping Sphinx v3 bugs severities to RC

2020-08-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Sphinx 3.2 is in unstable now > severity 963633 serious Bug #963633 {Done: Dmitry Shachnev } [src:breathe] breathe: FTBFS with Sphinx 3.1: TypeError: __init__() takes 2 positional arguments but 3 were given Bug #963638 {Done: Dmitry Shachnev

Bug#968120: castle-game-engine: FTBFS with fpc 3.2.0

2020-08-09 Thread Graham Inggs
Source: castle-game-engine Version: 6.4+dfsg1-4 Severity: serious Tags: ftbfs bullseye sid X-Debbugs-CC: pkg-pascal-de...@alioth-lists.debian.net Hi Maintainer As can be seen on reproducible builds [1], this package FTBFS since the upload of fpc 3.2.0+dfsg-5 to unstable. I've copied what I hope

Bug#958010: marked as done (yubikey-personalization: ftbfs with GCC-10)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 11:49:51 + with message-id and subject line Bug#958010: fixed in yubikey-personalization 1.20.0-2.1 has caused the Debian Bug report #958010, regarding yubikey-personalization: ftbfs with GCC-10 to be marked as done. This means that you claim that the

Bug#966606: marked as done (yubikey-personalization: patch for newer json-c)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 11:49:51 + with message-id and subject line Bug#966606: fixed in yubikey-personalization 1.20.0-2.1 has caused the Debian Bug report #966606, regarding yubikey-personalization: patch for newer json-c to be marked as done. This means that you claim that the

Bug#966604: marked as done (libu2f-server: patch for newer json-c)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 11:33:34 + with message-id and subject line Bug#966604: fixed in libu2f-server 1.1.0-3.1 has caused the Debian Bug report #966604, regarding libu2f-server: patch for newer json-c to be marked as done. This means that you claim that the problem has been

Bug#966859: marked as done (libu2f-host: FTBFS: u2fmisc.c:117:55: error: 'FALSE' undeclared (first use in this function))

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 11:33:29 + with message-id and subject line Bug#966602: fixed in libu2f-host 1.1.10-1.1 has caused the Debian Bug report #966602, regarding libu2f-host: FTBFS: u2fmisc.c:117:55: error: 'FALSE' undeclared (first use in this function) to be marked as done.

Processed: 0ad

2020-08-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 967118 https://trac.wildfiregames.com/ticket/5694 Bug #967118 [src:0ad] 0ad: Unversioned Python removal in sid/bullseye Set Bug forwarded-to-address to 'https://trac.wildfiregames.com/ticket/5694'. > tags 967118 upstream Bug #967118

Bug#967118: 0ad: Unversioned Python removal in sid/bullseye

2020-08-09 Thread Ludovic Rousseau
I tried to rebuild 0ad without python installed. The build fails with: [...] Building SpiderMonkey... SpiderMonkey build options: --enable-shared-js --disable-tests --without-intl-api --enable-shared-js --disable-tests --without-intl-api [...] checking for full perl installation... yes checking

Bug#966602: marked as done (libu2f-host: patch for newer json-c)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 11:33:29 + with message-id and subject line Bug#966602: fixed in libu2f-host 1.1.10-1.1 has caused the Debian Bug report #966602, regarding libu2f-host: patch for newer json-c to be marked as done. This means that you claim that the problem has been dealt

Bug#966887: marked as done (libu2f-server: FTBFS: core.c:480:58: error: ‘FALSE’ undeclared (first use in this function))

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 11:33:34 + with message-id and subject line Bug#966604: fixed in libu2f-server 1.1.0-3.1 has caused the Debian Bug report #966604, regarding libu2f-server: FTBFS: core.c:480:58: error: ‘FALSE’ undeclared (first use in this function) to be marked as done.

Bug#957580: marked as done (ncdu: ftbfs with GCC-10)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 11:18:32 + with message-id and subject line Bug#957580: fixed in ncdu 1.15.1-1 has caused the Debian Bug report #957580, regarding ncdu: 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#957430: closing 957430

2020-08-09 Thread PICCA Frederic-Emmanuel
close 957430 6.5.1-3 thanks

Bug#957041: marked as done (bindfs: ftbfs with GCC-10)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 10:18:28 + with message-id and subject line Bug#957041: fixed in bindfs 1.14.7-1 has caused the Debian Bug report #957041, regarding bindfs: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: closing 957430

2020-08-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 957430 6.5.1-3 Bug #957430 [src:libccp4] libccp4: ftbfs with GCC-10 The source 'libccp4' and version '6.5.1-3' do not appear to match any binary packages Marked as fixed in versions libccp4/6.5.1-3. Bug #957430 [src:libccp4] libccp4: ftbfs

Bug#936326: marked as done (configparser: Python2 removal in sid/bullseye)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 9 Aug 2020 11:56:54 +0200 with message-id <05669e4d-f99e-de04-44c2-f75a40c84...@debian.org> and subject line Re: configparser: Python2 removal in sid/bullseye has caused the Debian Bug report #936326, regarding configparser: Python2 removal in sid/bullseye to be marked as

Processed: Re: octave-symbolic: FTBFS: ValueError: octoutput does not know how to export type

2020-08-09 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 2.9.0-3 Bug #964673 {Done: Rafael Laboissière } [src:octave-symbolic] octave-symbolic: FTBFS: ValueError: octoutput does not know how to export type Marked as fixed in versions octave-symbolic/2.9.0-3. -- 964673:

Bug#966949: marked as done (kjs: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 09:19:38 + with message-id and subject line Bug#966949: fixed in kjs 5.70.0-2 has caused the Debian Bug report #966949, regarding kjs: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be

Bug#957400: marked as done (khtml: ftbfs with GCC-10)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 08:48:49 + with message-id and subject line Bug#957400: fixed in khtml 5.70.0-2 has caused the Debian Bug report #957400, regarding khtml: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: tagging 966949

2020-08-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 966949 + pending Bug #966949 [src:kjs] kjs: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below Added tag(s) pending. > thanks Stopping processing here. Please contact me if you

Bug#957122: marked as done (davfs2: ftbfs with GCC-10)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 08:33:27 + with message-id and subject line Bug#957122: fixed in davfs2 1.6.0-1 has caused the Debian Bug report #957122, regarding davfs2: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: tagging 957400

2020-08-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 957400 + pending Bug #957400 [src:khtml] khtml: ftbfs with GCC-10 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 957400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957400 Debian

Bug#957401: marked as done (kcoreaddons: ftbfs with GCC-10)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 08:25:17 + with message-id and subject line Bug#957401: fixed in kcoreaddons 5.70.0-2 has caused the Debian Bug report #957401, regarding kcoreaddons: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with.

Processed: Re: Bug#967932 closed by Matthias Klose (Re: redland-bindings: FTBFS: lots of undefined reference errors from ld)

2020-08-09 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 1.0.17.1+dfsg-1.4 Bug #967932 {Done: Matthias Klose } [src:redland-bindings] redland-bindings: FTBFS: lots of undefined reference errors from ld Marked as fixed in versions redland-bindings/1.0.17.1+dfsg-1.4. -- 967932:

Bug#967932: closed by Matthias Klose (Re: redland-bindings: FTBFS: lots of undefined reference errors from ld)

2020-08-09 Thread Sven Joachim
Control: fixed -1 1.0.17.1+dfsg-1.4 On 2020-08-08 19:42 +, Matthias Klose wrote: > not sure what the bug submitter was trying, but 1.0.17.1+dfsg-1.4 just built > fine. I tried to build the package with sbuild in a sid chroot, which failed. Apparently some change in dh-python made it

Processed: tagging 957401

2020-08-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 957401 + pending Bug #957401 [src:kcoreaddons] kcoreaddons: ftbfs with GCC-10 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 957401:

Bug#967183: marked as done (node-crc: Unversioned Python removal in sid/bullseye)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 06:18:45 + with message-id and subject line Bug#967183: fixed in node-crc 3.8.0+ds-3 has caused the Debian Bug report #967183, regarding node-crc: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#966903: marked as done (gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such file or directory)

2020-08-09 Thread Debian Bug Tracking System
Your message dated Sun, 09 Aug 2020 06:18:40 + with message-id and subject line Bug#966903: fixed in gecode 6.2.0-5 has caused the Debian Bug report #966903, regarding gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such file or directory to be marked as

Bug#967183: marked as pending in node-crc

2020-08-09 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #967183 in node-crc 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#967183 marked as pending in node-crc

2020-08-09 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #967183 [src:node-crc] node-crc: Unversioned Python removal in sid/bullseye Added tag(s) pending. -- 967183: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967183 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems