Bug#957548: marked as done (mlgmp: ftbfs with GCC-10)

Your message dated Thu, 13 Aug 2020 05:33:25 + with message-id and subject line Bug#957548: fixed in mlgmp 20021123-21 has caused the Debian Bug report #957548, regarding mlgmp: 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: Bug#957548 marked as pending in mlgmp

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

Bug#957548: marked as pending in mlgmp

Control: tag -1 pending Hello, Bug #957548 in mlgmp 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#968194: Upgrade to getmail6 which uses python3

Please use new upstream https://github.com/getmail6 release. It uses python3. Without upgrading, the getmail package is no longer installable on sid.

Processed: severity of 968194 is grave

Processing commands for cont...@bugs.debian.org: > severity 968194 grave Bug #968194 [getmail] Please upgrade to getmail6 which uses python3 Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 968194:

Bug#964591: marked as done (kodi FTBFS with libmicrohttpd 0.9.71)

Your message dated Wed, 12 Aug 2020 22:05:28 + with message-id and subject line Bug#964591: fixed in kodi 2:18.8+dfsg1-1 has caused the Debian Bug report #964591, regarding kodi FTBFS with libmicrohttpd 0.9.71 to be marked as done. This means that you claim that the problem has been dealt

Bug#961856: marked as done (kodi: baseline violation on i386)

Your message dated Wed, 12 Aug 2020 22:05:28 + with message-id and subject line Bug#961856: fixed in kodi 2:18.8+dfsg1-1 has caused the Debian Bug report #961856, regarding kodi: baseline violation on i386 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#965305: marked as done (ruby-kramdown: CVE-2020-14001)

Your message dated Wed, 12 Aug 2020 21:32:38 + with message-id and subject line Bug#965305: fixed in ruby-kramdown 1.17.0-1+deb10u1 has caused the Debian Bug report #965305, regarding ruby-kramdown: CVE-2020-14001 to be marked as done. This means that you claim that the problem has been

Bug#957717: [Help] pvm: ftbfs with GCC-10

Control: tags -1 patch Hi Andreas, This lead to the trail: > : error: 'pvmd' undeclared (first use in this function) > /build/pvm-3.4.6/src/ddpro.c:1031:14: note: in expansion of macro 'PVMDPATH' > 1031 | pvmdpath = PVMDPATH; > | ^~~~ Definition of PVMDPATH and friends

Processed: Re: [Help] pvm: ftbfs with GCC-10

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

Processed: src:mencal: fails to migrate to testing for too long: maintainer built arch:all binaries

Processing control commands: > close -1 3.0-5 Bug #968314 [src:mencal] src:mencal: fails to migrate to testing for too long: maintainer built arch:all binaries Marked as fixed in versions mencal/3.0-5. Bug #968314 [src:mencal] src:mencal: fails to migrate to testing for too long: maintainer

Bug#968314: src:mencal: fails to migrate to testing for too long: maintainer built arch:all binaries

Source: mencal Version: 3.0-4 Severity: serious Control: close -1 3.0-5 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and

Bug#968313: simpleburn: FTBFS: libcallbacks.a(callbacks.c.o):./obj-x86_64-linux-gnu/src/./src/simpleburn.h:57: multiple definition of `ui'

Source: simpleburn Version: 1.8.0-1 Severity: serious Tags: ftbfs sid bullseye Justification: fails to build from source (but built successfully in the past) | [100%] Linking C executable simpleburn | cd /<>/obj-x86_64-linux-gnu/src && /usr/bin/cmake -E cmake_link_script

Bug#968281: I cannot export alarms in Kalarm

This bug description looks like https://bugs.kde.org/show_bug.cgi?id=374337. This was fixed in KDE Applications 16.12.1. (The version you are reporting about is an earlier version, 16.04.3.) -- David Jarvie. KDE developer, KAlarm author.

Processed: src:austin: fails to migrate to testing for too long: FTBFS on armhf and mipsel

Processing control commands: > close -1 1.0.1-2 Bug #968309 [src:austin] src:austin: fails to migrate to testing for too long: FTBFS on armhf and mipsel Marked as fixed in versions austin/1.0.1-2. Bug #968309 [src:austin] src:austin: fails to migrate to testing for too long: FTBFS on armhf and

Bug#968309: src:austin: fails to migrate to testing for too long: FTBFS on armhf and mipsel

Source: austin Version: 1.0.0-1 Severity: serious Control: close -1 1.0.1-2 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and

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

Source: cgview Version: 0.0.20100111-4 Severity: serious Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing and unstable for more than 60

Processed: tagging 966894

Processing commands for cont...@bugs.debian.org: > tags 966894 + patch Bug #966894 [src:faucc] faucc: FTBFS: parse.tab.c:108:10: fatal error: parse.tab.h: No such file or directory Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 966894:

Bug#966894: faucc: FTBFS: parse.tab.c:108:10: fatal error: parse.tab.h: No such file or directory

Hi, fix is quite simple, patch attached, and already forwarded to upstream. As always, feel free to NMU. Cheers, Stefan. diff --git a/Makefile.am b/Makefile.am index 0541256..c2f7c49 100644 --- a/Makefile.am +++ b/Makefile.am @@ -35,7 +35,7 @@ cc1_SOURCES = parse.y \ cc1.c # Make sure

Bug#957380: istgt: diff for NMU version 0.4~20111008-3.1

On 12 Aug 2020, at 20:16, Sudip Mukherjee wrote: > > On Wed, Aug 12, 2020 at 8:04 PM Sudip Mukherjee > wrote: >> >> On Wed, Aug 12, 2020 at 7:54 PM Jessica Clarke wrote: >>> >>> On 12 Aug 2020, at 19:51, Sudip Mukherjee >>> wrote: HI Jess, On Wed, Aug 12, 2020 at 7:21

Bug#957761: marked as done (restartd: ftbfs with GCC-10)

Your message dated Wed, 12 Aug 2020 19:19:14 + with message-id and subject line Bug#957761: fixed in restartd 0.2.3-1.1 has caused the Debian Bug report #957761, regarding restartd: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#957380: istgt: diff for NMU version 0.4~20111008-3.1

On Wed, Aug 12, 2020 at 8:04 PM Sudip Mukherjee wrote: > > On Wed, Aug 12, 2020 at 7:54 PM Jessica Clarke wrote: > > > > On 12 Aug 2020, at 19:51, Sudip Mukherjee > > wrote: > > > > > > HI Jess, > > > > > > On Wed, Aug 12, 2020 at 7:21 PM Jessica Clarke wrote: > > >> > > >> On 12 Aug 2020, at

Bug#957380: istgt: diff for NMU version 0.4~20111008-3.1

On Wed, Aug 12, 2020 at 7:54 PM Jessica Clarke wrote: > > On 12 Aug 2020, at 19:51, Sudip Mukherjee wrote: > > > > HI Jess, > > > > On Wed, Aug 12, 2020 at 7:21 PM Jessica Clarke wrote: > >> > >> On 12 Aug 2020, at 19:15, Sudip Mukherjee > >> wrote: > >>> > >>> Control: tags 957380 + patch >

Bug#963662: marked as done (celery: FTBFS with Sphinx 3.1: Could not import extension celerydocs (exception: cannot import name 'NoUri' from 'sphinx.environment' (/usr/lib/python3/dist-packages/sphinx

Your message dated Wed, 12 Aug 2020 19:03:35 + with message-id and subject line Bug#963662: fixed in celery 4.4.6-1 has caused the Debian Bug report #963662, regarding celery: FTBFS with Sphinx 3.1: Could not import extension celerydocs (exception: cannot import name 'NoUri' from

Bug#957380: istgt: diff for NMU version 0.4~20111008-3.1

On 12 Aug 2020, at 19:51, Sudip Mukherjee wrote: > > HI Jess, > > On Wed, Aug 12, 2020 at 7:21 PM Jessica Clarke wrote: >> >> On 12 Aug 2020, at 19:15, Sudip Mukherjee wrote: >>> >>> Control: tags 957380 + patch >>> Control: tags 957380 + pending >>> >>> Dear maintainer, >>> >>> I've

Processed: Re: Bug#968300: doesn't build without real root

Processing control commands: > severity -1 normal Bug #968300 [systemd] doesn't build without real root Severity set to 'normal' from 'serious' > tags -1 unreproducible moreinfo Bug #968300 [systemd] doesn't build without real root Added tag(s) unreproducible and moreinfo. -- 968300:

Bug#957380: istgt: diff for NMU version 0.4~20111008-3.1

HI Jess, On Wed, Aug 12, 2020 at 7:21 PM Jessica Clarke wrote: > > On 12 Aug 2020, at 19:15, Sudip Mukherjee wrote: > > > > Control: tags 957380 + patch > > Control: tags 957380 + pending > > > > Dear maintainer, > > > > I've prepared an NMU for istgt (versioned as 0.4~20111008-3.1) and > >

Bug#968300: doesn't build without real root

Control: severity -1 normal Control: tags -1 unreproducible moreinfo Am 12.08.20 um 16:11 schrieb Marc Haber: > Package: systemd > Version: 241-7~deb10u4.1+0~zgSID+1 > Severity: serious > Tags: ftbfs > Justification: [buster] fails to build from source > The package obviously builds from source,

Bug#966575: Symbol `grub_calloc' not found: AWS instance

I've been affected by this issue on an AWS EC2 instance. The particular issue with AWS is that the device names may depend on the particular instance types; on newer hardware disks appear as NVMe devices, and on older hardware as /dev/xvd? or /dev/sd?. The Debian cloud instances have

Bug#957298: gom: diff for NMU version 0.30.2-9.1

Control: tags 957298 + patch Control: tags 957298 + pending Dear maintainer, I've prepared an NMU for gom (versioned as 0.30.2-9.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru gom-0.30.2/debian/changelog

Processed: gom: diff for NMU version 0.30.2-9.1

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

Bug#967192: marked as done (openttd-openmsx: Unversioned Python removal in sid/bullseye)

Your message dated Wed, 12 Aug 2020 18:33:27 + with message-id and subject line Bug#967192: fixed in openttd-openmsx 0.3.1-6 has caused the Debian Bug report #967192, regarding openttd-openmsx: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that

Bug#957380: istgt: diff for NMU version 0.4~20111008-3.1

On 12 Aug 2020, at 19:15, Sudip Mukherjee wrote: > > Control: tags 957380 + patch > Control: tags 957380 + pending > > Dear maintainer, > > I've prepared an NMU for istgt (versioned as 0.4~20111008-3.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I > should cancel it.

Bug#957380: istgt: diff for NMU version 0.4~20111008-3.1

Control: tags 957380 + patch Control: tags 957380 + pending Dear maintainer, I've prepared an NMU for istgt (versioned as 0.4~20111008-3.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should cancel it. -- Regards Sudip diff -Nru istgt-0.4~20111008/debian/changelog

Processed: istgt: diff for NMU version 0.4~20111008-3.1

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

Bug#967084: marked as done (golang-1.14: FTBFS with gcc-10 on arm64)

Your message dated Wed, 12 Aug 2020 17:48:31 + with message-id and subject line Bug#967084: fixed in golang-1.14 1.14.7-2 has caused the Debian Bug report #967084, regarding golang-1.14: FTBFS with gcc-10 on arm64 to be marked as done. This means that you claim that the problem has been

Processed: found 968302 in 1:2.3.4.1-5+deb10u2

Processing commands for cont...@bugs.debian.org: > found 968302 1:2.3.4.1-5+deb10u2 Bug #968302 [src:dovecot] src:dovecot: multiple dovecot CVEs Marked as found in versions dovecot/1:2.3.4.1-5+deb10u2. > thanks Stopping processing here. Please contact me if you need assistance. -- 968302:

Processed: fixed 968302 in 1:2.3.4.1-5+deb10u3

Processing commands for cont...@bugs.debian.org: > fixed 968302 1:2.3.4.1-5+deb10u3 Bug #968302 [src:dovecot] src:dovecot: multiple dovecot CVEs Marked as fixed in versions dovecot/1:2.3.4.1-5+deb10u3. > thanks Stopping processing here. Please contact me if you need assistance. -- 968302:

Bug#968302: src:dovecot: multiple dovecot CVEs

Package: src:dovecot Version: 1:2.3.10.1+dfsg1-2 Severity: grave Tags: security bullseye sid Justification: user security hole Multiple security issues have been identified in dovecot. These were addressed in stable with dovecot 1:2.3.4.1-5+deb10u3 (DSA 4745-1), but need to be tracked in

Bug#968300: doesn't build without real root

Package: systemd Version: 241-7~deb10u4.1+0~zgSID+1 Severity: serious Tags: ftbfs Justification: [buster] fails to build from source Hi, I am trying to do a local build of systemd 241 on buster to fix the capabilities issue (#964026). In this process, I have found out that systemd does need

Processed: bug 966698 is forwarded to https://github.com/mchehab/rasdaemon/issues/21

Processing commands for cont...@bugs.debian.org: > forwarded 966698 https://github.com/mchehab/rasdaemon/issues/21 Bug #966698 [rasdaemon] rasdaemon: fails to start by default under systemd due to EnvironmentFile=/etc/sysconfig/rasdaemon Bug #966717 [rasdaemon] rasdaemon: fails to start by

Bug#968246: marked as done (dnstwist: Autopkgtest failure due to depgrecation warning with dnspython 2.0.0)

Your message dated Wed, 12 Aug 2020 17:03:28 + with message-id and subject line Bug#968246: fixed in dnstwist 0~20200707-1 has caused the Debian Bug report #968246, regarding dnstwist: Autopkgtest failure due to depgrecation warning with dnspython 2.0.0 to be marked as done. This means that

Bug#968246: marked as pending in Dnstwist

Control: tag -1 pending Hello, Bug #968246 in Dnstwist 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#968246 marked as pending in Dnstwist

Processing control commands: > tag -1 pending Bug #968246 [dnstwist] dnstwist: Autopkgtest failure due to depgrecation warning with dnspython 2.0.0 Added tag(s) pending. -- 968246: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968246 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#957837: sprng: ftbfs with GCC-10

Hi, This patch fixes the build. Let me know if something else is needed: --- a/SRC/primes_32.c +++ b/SRC/primes_32.c @@ -7,7 +7,7 @@  #define NO  0  #define NPRIMES 1000   -int primes[NPRIMES]; +extern int primes[NPRIMES];    #ifdef __STDC__  int init_prime_32(void) Kind Regards, Nilesh

Bug#956887: marked as done (eliom FTBFS)

Your message dated Wed, 12 Aug 2020 15:33:25 + with message-id and subject line Bug#956887: fixed in eliom 6.12.1-1 has caused the Debian Bug report #956887, regarding eliom FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Bug#957029: ax25mail-utils is marked for autoremoval from testing

Re: David Ranch > I have built up a working Debian Sid image with GCC 10 and have reproduced > the issue with the "develop" branch of ax25mail-utils. I am working on > getting these issues resolved but how long do I have to get them addressed? > > On 08/11/2020 09:39 PM, Debian testing

Bug#944600: marked as done (FTBFS with OCaml 4.08.1 (safe strings))

Your message dated Wed, 12 Aug 2020 14:28:16 + with message-id and subject line Bug#944600: fixed in ocaml-melt 1.4.0-3 has caused the Debian Bug report #944600, regarding FTBFS with OCaml 4.08.1 (safe strings) to be marked as done. This means that you claim that the problem has been dealt

Bug#936336: coz-profiler: Python2 removal in sid/bullseye

[Lluís Vilanova] > Unfortunately I do not have upload privileges and couldn't find > anybody that would keep uploading them for coz. I've managed to fix my key problems, and can do the upload. Is it ready to go in? -- Happy hacking Petter Reinholdtsen

Processed: Bug#944600 marked as pending in ocaml-melt

Processing control commands: > tag -1 pending Bug #944600 [src:ocaml-melt] FTBFS with OCaml 4.08.1 (safe strings) Added tag(s) pending. -- 944600: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944600 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#944600: marked as pending in ocaml-melt

Control: tag -1 pending Hello, Bug #944600 in ocaml-melt 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#966869: marked as done (nfs-ganesha: FTBFS: ld: CMakeFiles/MainServices.dir/nfs_rpc_dispatcher_thread.c.o:./src/obj-x86_64-linux-gnu/MainNFSD/./src/include/nfs_init.h:53: multiple definition of `g

Your message dated Wed, 12 Aug 2020 13:33:31 + with message-id and subject line Bug#966869: fixed in nfs-ganesha 3.2-3 has caused the Debian Bug report #966869, regarding nfs-ganesha: FTBFS: ld:

Bug#957307: marked as done (grfcodec: ftbfs with GCC-10)

Your message dated Wed, 12 Aug 2020 13:18:28 + with message-id and subject line Bug#957307: fixed in grfcodec 6.0.6-5 has caused the Debian Bug report #957307, regarding grfcodec: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#939817: marked as done (FTBFS with OCaml 4.08.0)

Your message dated Wed, 12 Aug 2020 13:04:03 + with message-id and subject line Bug#939817: fixed in otags 4.05.1-2 has caused the Debian Bug report #939817, regarding FTBFS with OCaml 4.08.0 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#939817: marked as pending in otags

Control: tag -1 pending Hello, Bug #939817 in otags 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#939817 marked as pending in otags

Processing control commands: > tag -1 pending Bug #939817 [src:otags] FTBFS with OCaml 4.08.0 Added tag(s) pending. -- 939817: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939817 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#968273: marked as done (orthanc-doc: ships /usr/share/orthanc/plugins/libModalityWorklists.so, already in orthanc)

Your message dated Wed, 12 Aug 2020 12:33:36 + with message-id and subject line Bug#968273: fixed in orthanc 1.7.2+dfsg-4 has caused the Debian Bug report #968273, regarding orthanc-doc: ships /usr/share/orthanc/plugins/libModalityWorklists.so, already in orthanc to be marked as done. This

Bug#968273: marked as pending in orthanc

Control: tag -1 pending Hello, Bug #968273 in orthanc 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#968273 marked as pending in orthanc

Processing control commands: > tag -1 pending Bug #968273 [orthanc-doc] orthanc-doc: ships /usr/share/orthanc/plugins/libModalityWorklists.so, already in orthanc Added tag(s) pending. -- 968273: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968273 Debian Bug Tracking System Contact

Processed: Re: #957884 trousers: ftbfs with GCC-10

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

Bug#957884: #957884 trousers: ftbfs with GCC-10

Control: tags -1 +patch Hello there, my simple-tpm-pk11 package is threatened by a removal of testing because of the trousers FTBFS. So here comes a patch proposal (from an upstream patch over at https://sourceforge.net/p/trousers/trousers/ci/c9b8c4434f3b11bae4f7e72c3aec5b4f3459eecc/ ).

Bug#968210: statsmodels: arm* test failures/crashes

This doesn't crash when just that test file is run in statsmodels 0.11.1-3 qemu-armel, but this isn't 100% proof that -4 (rather than a dependency) caused it. -4 (built locally in qemu) doesn't crash that way either, which suggests this bug doesn't show up in qemu, and (given the lack of

Processed: ruby-kramdown 2 is in unstable now

Processing commands for cont...@bugs.debian.org: > severity 966020 serious Bug #966020 [jekyll] jekyll: ftbfs with ruby-kramdown 2.x in experimental Severity set to 'serious' from 'important' > severity 966021 serious Bug #966021 [rabbit] rabbit: autopkgtest fails with ruby-karmdown 2.x in

Processed: ruby-kramdown-parser-gfm: ftbfs with 2 test failures

Processing control commands: > affects -1 ruby-cucumber-core Bug #968280 [ruby-kramdown-parser-gfm] ruby-kramdown-parser-gfm: ftbfs with 2 test failures Added indication that 968280 affects ruby-cucumber-core -- 968280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968280 Debian Bug

Bug#968281: I cannot export alarms in Kalarm

Package: kalarm Version: 4:16.04.3-4~deb9u1 Severity: serious Tags: d-i I use only Xfce desktop. To install Kalarm I need to install the following additional dependencies: plasma-workspace and kdepim-runtime. Kalarm works well, except I cannot export selected alarms. Is some dependency missing?

Bug#968280: ruby-kramdown-parser-gfm: ftbfs with 2 test failures

Package: ruby-kramdown-parser-gfm Version: 1.1.0-1~exp1 Severity: serious Control: affects -1 ruby-cucumber-core On a clean sid chroot with ruby-karmdown 2.3.0-3 added, it fails with this error message. So reuploading this package to unstable is blocked and it results in ruby-cucumber-core

Bug#957190: marked as done (f2j: ftbfs with GCC-10)

Your message dated Wed, 12 Aug 2020 10:19:00 + with message-id and subject line Bug#957190: fixed in f2j 0.8.1+dfsg-5 has caused the Debian Bug report #957190, regarding f2j: 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#957190: [Help] f2j: ftbfs with GCC-10

On Wed, Aug 12, 2020 at 10:53:24AM +0100, Sudip Mukherjee wrote: > Try the attached patch. Thanks, this works Andreas. -- http://fam-tille.de

Bug#957694: pocl: ftbfs with GCC-10

Followup-For: Bug #957694 anti-autorm ping ... migration is currently blocked by gcc-defaults ...

Bug#957190: [Help] f2j: ftbfs with GCC-10

HI Andreas, On Wed, Aug 12, 2020 at 8:10 AM Andreas Tille wrote: > > Control: tags -1 help > > Hi, > > I think I've fixed part of the problem in Git[1]. Unfortunately there is a > remainig "multiple definition" issue where I have no idea how to fix it: Try the attached patch. -- Regards

Bug#968279: rust-gdb: ships /usr/share/rust-lldb/rust_types.py

Package: rust-gdb Version: 1.46.0~beta.2+dfsg1-1~exp4 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 log (scroll to the

Processed: problem is caused by grpc gem

Processing control commands: > reassign -1 ruby-grpc Bug #966653 [ruby-google-protobuf] gitlab: [BUG] Segmentation fault at 0x Bug reassigned from package 'ruby-google-protobuf' to 'ruby-grpc'. Ignoring request to alter found versions of bug #966653 to the same values previously

Bug#966653: problem is caused by grpc gem

Control: reassign -1 ruby-grpc Control: found -1 1.30.2-2 If I replace ruby-grpc package with grpc gem from rubygems.org, gitlab/gitaly crash is fixed.

Bug#968276: yi: FTBFS in sid (missing deps)

Source: yi Version: 0.18.0-2 Severity: serious Lots of yi related deps have been removed, yi still depends on them Installing build dependencies Reading package lists... Building dependency tree... Reading state information... Some packages could not be installed. This may mean that you have

Bug#968275: wtdbg2,wtdbg2-examples: both ship /usr/lib/wtdbg2/simd-dispatch

Package: wtdbg2,wtdbg2-examples Version: 2.5-5 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 log (scroll to the bottom...):

Bug#968274: libzorpll-7.0-4-dev: missing (unversioned) Breaks+Replaces: libzorpll-7.0-1-dev

Package: libzorpll-7.0-4-dev Version: 7.0.4.0-1 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 without declaring a Breaks+Replaces relation. See

Bug#968273: orthanc-doc: ships /usr/share/orthanc/plugins/libModalityWorklists.so, already in orthanc

Package: orthanc-doc Version: 1.7.2+dfsg-3 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 log (scroll to the bottom...):

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

On Wed, Aug 12, 2020 at 11:53, dragos.ja...@dynamicpuzzle.ro wrote: Hi I installed packages, but have another err: Installing node modules... yarn install v1.22.4 [1/5] Validating package.json... [2/5] Resolving packages... [3/5] Fetching packages... error An unexpected error occurred:

Bug#967180: marked as done (nifticlib: Unversioned Python removal in sid/bullseye)

Your message dated Wed, 12 Aug 2020 09:04:36 + with message-id and subject line Bug#967180: fixed in nifticlib 2.0.0+git186-g84740c2-1 has caused the Debian Bug report #967180, regarding nifticlib: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim

Bug#957717: [Help] pvm: ftbfs with GCC-10

Andreas Tille writes: > while I do not intend to maintain pvm personally some Debian Med package > depend from it. Thus I like to see bug #957717 fixed but I need help. Do people still use PVM for parallel computing? I thought it was replaced by MPI decades ago. If use of PVM is optional, I

Bug#957330: marked as done (hexchat-otr: ftbfs with GCC-10)

Your message dated Wed, 12 Aug 2020 08:49:15 + with message-id and subject line Bug#957330: fixed in hexchat-otr 0.2.2-3 has caused the Debian Bug report #957330, regarding hexchat-otr: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#962651: Reported yesterday

This issue was reported to upstream on 11 August 2020 (https://github.com/rst2pdf/rst2pdf/issues/895) and is being addressed. -- Rob Allen rst2pdf Project Lead https://rst2pdf.org

Processed: Forwarded bug #962651 to upstream

Processing commands for cont...@bugs.debian.org: > forwarded #962651 https://github.com/rst2pdf/rst2pdf/issues/895 > Bug #962651 [rst2pdf] rst2pdf depends and build depends on python3-pdfrw that might not be in bullseye Set Bug

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

On Wed, Aug 12, 2020 at 08:38, dragos.ja...@dynamicpuzzle.ro wrote: Hi Access violation persists. Tried to downgrade grpc, but have dependency problems. Use http://snapshot.debian.org/package/protobuf/3.11.4-5/ and http://snapshot.debian.org/package/grpc/1.26.0-3/ You need

Bug#957190: [Help] f2j: ftbfs with GCC-10

Control: tags -1 help Hi, I think I've fixed part of the problem in Git[1]. Unfortunately there is a remainig "multiple definition" issue where I have no idea how to fix it: ex.o f2jmain.o symtab.o codegen.o vcg_emitter.o dlist.o typecheck.o optimize.o globals.o f2jmem.o

Processed: [Help] f2j: ftbfs with GCC-10

Processing control commands: > tags -1 help Bug #957190 [src:f2j] f2j: ftbfs with GCC-10 Added tag(s) help. -- 957190: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957190 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957866: marked as done (tcsh: ftbfs with GCC-10)

Your message dated Wed, 12 Aug 2020 06:50:15 + with message-id and subject line Bug#957866: fixed in tcsh 6.21.00-1.1 has caused the Debian Bug report #957866, regarding tcsh: 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#957717: [Help] pvm: ftbfs with GCC-10

Hi, while I do not intend to maintain pvm personally some Debian Med package depend from it. Thus I like to see bug #957717 fixed but I need help. I commited some general packaging changes so you can find the last packaging state in Git[1]. When building this I get the following output: cc

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

Your message dated Wed, 12 Aug 2020 06:20:44 + with message-id and subject line Bug#968047: fixed in texlive-extra 2020.20200804-3 has caused the Debian Bug report #968047, regarding texlive-fonts-extra-links: missing Breaks+Replaces: texlive-fonts-extra (<< 2020.20200804) to be marked as