Bug#943302: marked as done (zsnapd: Python2 removal in sid/bullseye)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 04:18:33 + with message-id and subject line Bug#943302: fixed in zsnapd 0.8.11h-2 has caused the Debian Bug report #943302, regarding zsnapd: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Processed: fvwm-crystal: Python2 removal in sid/bullseye - reopen 945673

2020-08-07 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #945673 {Done: Vincent Bernat } [src:fvwm-crystal] fvwm-crystal: Python2 removal in sid/bullseye Bug #966735 {Done: Vincent Bernat } [src:fvwm-crystal] fvwm-crystal: Unversioned Python removal in sid/bullseye 'reopen' may be inappropriate when a bug

Bug#965288: r-cran-findpython: Python2 removal in sid/bullseye - reopen 965288

2020-08-07 Thread Sandro Tosi
Control: reopen -1 This bug was closed, but the package has still some dependencies towards Python2 packages, in details: (source:r-cran-findpython)Testsuite-Triggers->python (binary:r-cran-findpython)Recommends->python Re-opening, so that they can be taken care of.

Processed: r-cran-findpython: Python2 removal in sid/bullseye - reopen 965288

2020-08-07 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #965288 {Done: "Michael R. Crusoe" } [src:r-cran-findpython] r-cran-findpython: Python2 removal in sid/bullseye Bug reopened Ignoring request to alter fixed versions of bug #965288 to the same values previously set -- 965288:

Bug#945673: fvwm-crystal: Python2 removal in sid/bullseye - reopen 945673

2020-08-07 Thread Sandro Tosi
Control: reopen -1 This bug was closed, but the package has still some dependencies towards Python2 packages, in details: (binary:fvwm-crystal)Depends->python2 Re-opening, so that they can be taken care of.

Bug#967202: marked as done (python-magcode-core: Unversioned Python removal in sid/bullseye)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 01:33:24 + with message-id and subject line Bug#967202: fixed in python-magcode-core 1.5.4-2 has caused the Debian Bug report #967202, regarding python-magcode-core: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim

Processed: Re: Bug#946046: not fixed

2020-08-07 Thread Debian Bug Tracking System
Processing control commands: > tags -1 - wontfix Bug #946046 [unison-all] unison-all should also depend on the old unison version, compatible with Debian 10 Removed tag(s) wontfix. > severity -1 serious Bug #946046 [unison-all] unison-all should also depend on the old unison version, compatible

Processed: Re: Bug#946046: not fixed

2020-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 946046 wishlist Bug #946046 [unison-all] unison-all should also depend on the old unison version, compatible with Debian 10 Severity set to 'wishlist' from 'grave' > tags 946046 + wontfix Bug #946046 [unison-all] unison-all should also

Bug#946046: not fixed

2020-08-07 Thread Stéphane Glondu
severity 946046 wishlist tags 946046 + wontfix thanks Le 07/08/2020 à 22:24, Vincent Lefevre a écrit : > This is not sufficient to synchronize with Debian 10 (buster). > It depends only on unison, which depends on unison-2.48, and > with the latest version of unison-2.48, I get lots of errors: >

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-07 Thread Thorsten Glaser
On Fri, 7 Aug 2020, Pierre Gruet wrote: > I suggest using the enclosed patch, which allows the build to succeed by > overriding the ``test'' method of Predicate. The ``apply'' method > provided by upstream has to be kept as it is used by the ``test'' method. But why? This amount of redundancy

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-07 Thread Pierre Gruet
Hi Andreas, Le 07/08/2020 à 13:40, Andreas Tille a écrit : > Hi Thorsten, > > On Thu, Aug 06, 2020 at 04:04:22PM +0200, Thorsten Glaser wrote: >> On Thu, 6 Aug 2020, Andreas Tille wrote: >> >>> [ERROR] >>> /build/jimfs-1.1/jimfs/src/main/java/com/google/common/jimfs/PathService.java:[290,30]

Bug#946046: not fixed

2020-08-07 Thread Vincent Lefevre
On 2020-08-07 22:24:10 +0200, Vincent Lefevre wrote: > This is not sufficient to synchronize with Debian 10 (buster). > It depends only on unison, which depends on unison-2.48, and > with the latest version of unison-2.48, I get lots of errors: > > Failed: Server: Fatal error during unmarshaling

Bug#967089: closing 967089, closing 967092, closing 967094, closing 967100, closing 967103, closing 967104 ...

2020-08-07 Thread Jochen Sprickerhof
close 967089 close 967092 close 967094 close 967100 close 967103 close 967104 close 967106 close 967108 thanks Tested using sbuild, most probably fixed by osgi-core 7.0.0-2.

Processed: Bug#946046 not fixed

2020-08-07 Thread Debian Bug Tracking System
Processing control commands: > reopen -1 Bug #946046 {Done: =?utf-8?q?St=C3=A9phane_Glondu?= } [unison-all] unison-all should also depend on the old unison version, compatible with Debian 10 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be

Bug#946046: not fixed

2020-08-07 Thread Vincent Lefevre
Control: reopen -1 Control: found -1 2.48.4+2 On 2020-08-05 07:51:04 +, Debian Bug Tracking System wrote: > This is an automatic notification regarding your Bug report > which was filed against the unison-all package: > > #946046: unison-all should also depend on the old unison version,

Processed: closing 967089, closing 967092, closing 967094, closing 967100, closing 967103, closing 967104 ...

2020-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 967089 Bug #967089 [src:jboss-xnio] jboss-xnio: FTBFS: [ERROR] Failed to execute goal on project xnio-api: Could not resolve dependencies for project org.jboss.xnio:xnio-api:jar:3.8.1.Final: Cannot access central

Bug#968066: haskell-hgettext: autopkgtest fails with newer version of ghc

2020-08-07 Thread Paul Gevers
Source: haskell-hgettext Version: 0.1.31.0-5 Severity: serious X-Debbugs-CC: debian...@lists.debian.org, g...@packages.debian.org Tags: sid bullseye User: debian...@lists.debian.org Usertags: needs-update Control: affects -1 src:ghc Dear maintainer(s), With a recent upload of ghc the autopkgtest

Processed: haskell-hgettext: autopkgtest fails with newer version of ghc

2020-08-07 Thread Debian Bug Tracking System
Processing control commands: > affects -1 src:ghc Bug #968066 [src:haskell-hgettext] haskell-hgettext: autopkgtest fails with newer version of ghc Added indication that 968066 affects src:ghc -- 968066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968066 Debian Bug Tracking System Contact

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

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 19:34:07 + with message-id and subject line Bug#966995: fixed in mplcursors 0.3-3 has caused the Debian Bug report #966995, regarding mplcursors: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13 to be

Bug#957487: libzstd: ftbfs with GCC-10

2020-08-07 Thread Andreas Tille
Control: severity -1 normal The FTBFS issue was fixed (thanks to Sudip Mukherjee[1]) but I leave the bug open until upstream has found a solution for https://github.com/facebook/zstd/issues/2204 Than the current means (-fno-strict-aliasing) should be reverted. Kind regards Andreas.

Processed: Re: Bug#957487: libzstd: ftbfs with GCC-10

2020-08-07 Thread Debian Bug Tracking System
Processing control commands: > severity -1 normal Bug #957487 [src:libzstd] libzstd: ftbfs with GCC-10 Severity set to 'normal' from 'serious' -- 957487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957487 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#957206: EXTERNAL: New upstream version available (Was: Bug#957206: fis-gtm: ftbfs with GCC-10)

2020-08-07 Thread Shah, Amul
Andreas, Thanks for the ping. We have a fix, just not enough time in a day. :( Amul -Original Message- From: Andreas Tille Sent: Friday, August 07, 2020 4:15 AM To: 957206-mainto...@bugs.debian.org; Shah, Amul Subject: EXTERNAL: New upstream version available (Was: Bug#957206: fis-gtm:

Bug#957258: marked as done (gbatnav: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 19:03:26 + with message-id and subject line Bug#957258: fixed in gbatnav 1.0.4cvs20051004-6 has caused the Debian Bug report #957258, regarding gbatnav: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with.

Processed: gnomekiss: diff for NMU version 2.0-6.1

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

Bug#957286: gnomekiss: diff for NMU version 2.0-6.1

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

Bug#957959: marked as done (wmxres: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 18:03:39 + with message-id and subject line Bug#957959: fixed in wmxres 1.2-10.2 has caused the Debian Bug report #957959, regarding wmxres: 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#964611: libqtpas: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

2020-08-07 Thread Paul Gevers
Hi, I am preparing an upload with the symbols file removed as there seems to be consensus that using symbols files for C++ projects in Debian isn't worth the effort. Paul signature.asc Description: OpenPGP digital signature

Bug#968048: marked as done (ax25-{,x}tools: both ship /usr/bin/smdiag and some more files)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 17:18:22 + with message-id and subject line Bug#968048: fixed in ax25-tools 0.0.10-rc5+git20190411+3595f87-3 has caused the Debian Bug report #968048, regarding ax25-{,x}tools: both ship /usr/bin/smdiag and some more files to be marked as done. This means

Bug#957684: pick: diff for NMU version 2.0.2-1.1

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

Processed: pick: diff for NMU version 2.0.2-1.1

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

Bug#968048: marked as pending in ax25-tools

2020-08-07 Thread Francois Marier
Control: tag -1 pending Hello, Bug #968048 in ax25-tools 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#968048 marked as pending in ax25-tools

2020-08-07 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #968048 [ax25-tools,ax25-xtools] ax25-{,x}tools: both ship /usr/bin/smdiag and some more files Added tag(s) pending. -- 968048: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968048 Debian Bug Tracking System Contact ow...@bugs.debian.org

Processed: welcome2l: diff for NMU version 3.04-27.1

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

Bug#957928: welcome2l: diff for NMU version 3.04-27.1

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

Processed: tagging 966923

2020-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 966923 + fixed-upstream Bug #966923 [meson] meson: 0.55.0 considers TAP "ok # SKIP" to be a failure Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 966923:

Bug#957487: libzstd: ftbfs with GCC-10

2020-08-07 Thread Sudip Mukherjee
Hi Andreas, On Fri, Aug 7, 2020 at 10:39 AM Andreas Tille wrote: > > Control: tags -1 help > > Hi, > > this issue is now RC and has not changed in current version 1.4.5. > > Any hint what to do? The attached patch is the easiest solution for now. But I will suggest raising an issue with

Bug#957523: marked as done (mcabber: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 16:19:00 + with message-id and subject line Bug#957523: fixed in mcabber 1.1.0-2 has caused the Debian Bug report #957523, regarding mcabber: 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#968056: nanoc: missing dependency on ruby-nanoc-cli

2020-08-07 Thread Antonio Terceiro
Package: nanoc Version: 4.11.14-1 Severity: serious Justification: missind dependency for normal operation Hello, thanks for updating nanoc. After upgrading from 4.11.0, nanoc now fails right away: 8<8<8<- $ nanoc Traceback (most

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-07 Thread Thorsten Glaser
On Fri, 7 Aug 2020, Andreas Tille wrote: > but this does not help much and the build issue remains. Erk… then I don’t know either. Sorry, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG

Bug#957230: Bug#966370: bsdmainutils: 12.1.3 removal of lorder breaks rdeps

2020-08-07 Thread Jessica Clarke
On 29 Jul 2020, at 09:04, Michael Meskes wrote: > > On Mon, Jul 27, 2020 at 03:01:31PM +0100, Jessica Clarke wrote: >> Package: bsdmainutils >> Version: 12.1.3 >> Severity: serious >> Control: affects -1 src:freebsd-buildutils src:freebsd-glue src:freebsd-libs >> >> Hi, >> The removal of lorder

Bug#957451: marked as done (libmawk: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 15:21:24 + with message-id and subject line Bug#957451: fixed in libmawk 1.0.2-3 has caused the Debian Bug report #957451, regarding libmawk: 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#966999: marked as done (python-hdf5storage: FTBFS: File "/usr/lib/python3/dist-packages/numpydoc/docscrape.py", line 324, in _parse_see_also ; raise ParseError("%s is not a item name" % line))

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 15:04:30 + with message-id and subject line Bug#966999: fixed in python-hdf5storage 0.1.15+git20200608.09dfc5f-1 has caused the Debian Bug report #966999, regarding python-hdf5storage: FTBFS: File "/usr/lib/python3/dist-packages/numpydoc/docscrape.py",

Bug#957650: marked as done (osmo-msc: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 14:55:08 + with message-id and subject line Bug#957650: fixed in osmo-msc 1.2.0-4 has caused the Debian Bug report #957650, regarding osmo-msc: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#957651: marked as done (osmo-bts: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 14:54:51 + with message-id and subject line Bug#957651: fixed in osmo-bts 0.8.1-3 has caused the Debian Bug report #957651, regarding osmo-bts: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#967190: marked as done (osmo-iuh: Unversioned Python removal in sid/bullseye)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 14:55:00 + with message-id and subject line Bug#967190: fixed in osmo-iuh 0.3.0-6 has caused the Debian Bug report #967190, regarding osmo-iuh: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#957613: marked as done (npd6: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 14:54:39 + with message-id and subject line Bug#957613: fixed in npd6 1.1.0-3 has caused the Debian Bug report #957613, regarding npd6: 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#957791: marked as done (siggen: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 14:56:02 + with message-id and subject line Bug#957791: fixed in siggen 2.3.10-10 has caused the Debian Bug report #957791, regarding siggen: 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#957652: marked as done (osmo-iuh: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 14:54:59 + with message-id and subject line Bug#957652: fixed in osmo-iuh 0.3.0-6 has caused the Debian Bug report #957652, regarding osmo-iuh: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#957634: marked as done (openbsc: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 14:54:44 + with message-id and subject line Bug#957634: fixed in openbsc 1.1.0-3 has caused the Debian Bug report #957634, regarding openbsc: 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#966886: marked as done (dirb: FTBFS: ld: dirb.o:./src/variables.h:18: multiple definition of `options'; crea_wordlist.o:./src/variables.h:18: first defined here)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 14:51:10 + with message-id and subject line Bug#966886: fixed in dirb 2.22+dfsg-5 has caused the Debian Bug report #966886, regarding dirb: FTBFS: ld: dirb.o:./src/variables.h:18: multiple definition of `options'; crea_wordlist.o:./src/variables.h:18:

Bug#957009: marked as done (arpalert: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 14:50:53 + with message-id and subject line Bug#957009: fixed in arpalert 2.0.12-4 has caused the Debian Bug report #957009, regarding arpalert: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: try to migrate

2020-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 960662 - bullseye - sid Bug #960662 {Done: Bastian Germann } [python-spyne] spyne: unsatisfiable dependency on lxml Removed tag(s) bullseye. Bug #960662 {Done: Bastian Germann } [python-spyne] spyne: unsatisfiable dependency on lxml

Processed: tagging 957496

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

Bug#964611: [Pkg-pascal-devel] Bug#964611: Bug#964611: libqtpas: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

2020-08-07 Thread Abou Al Montacir
Hi Peter, On Fri, 2020-08-07 at 11:08 +0100, peter green wrote: > > > +#MISSING: 2.6+2.0.8+dfsg-1# > > > _ZN7QVectorI6QPointE11reallocDataEii6QFlagsIN10QArrayData16AllocationOptionEE@Base > > > 2.6~alpha > > c++filt -n decodes this to > QVector::reallocData(int, int, QFlags) > This looks like

Bug#965352: libopenmpi3: breaks tests in client programs

2020-08-07 Thread Drew Parsons
Package: libopenmpi3 Version: 4.0.4-2 Followup-For: Bug #965352 Control: forwarded -1 https://bitbucket.org/mpi4py/mpi4py/issues/171 Calling on mpi4py upstream for advice.

Processed: Re: libopenmpi3: breaks tests in client programs

2020-08-07 Thread Debian Bug Tracking System
Processing control commands: > forwarded -1 https://bitbucket.org/mpi4py/mpi4py/issues/171 Bug #965352 [libopenmpi3] libopenmpi3: breaks tests in client programs Set Bug forwarded-to-address to 'https://bitbucket.org/mpi4py/mpi4py/issues/171'. -- 965352:

Bug#957511: marked as done (luakit: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 13:03:42 + with message-id and subject line Bug#957511: fixed in luakit 1:2.1+git2020.08.04-1 has caused the Debian Bug report #957511, regarding luakit: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt

Bug#966756: marked as done (libwfut: Unversioned Python removal in sid/bullseye)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 13:00:14 + with message-id and subject line Bug#936939: fixed in libwfut 0.2.3-7 has caused the Debian Bug report #936939, regarding libwfut: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#936939: marked as done (libwfut: Python2 removal in sid/bullseye)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 13:00:14 + with message-id and subject line Bug#936939: fixed in libwfut 0.2.3-7 has caused the Debian Bug report #936939, regarding libwfut: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#957391: marked as done (kaccounts-integration: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 13:00:12 + with message-id and subject line Bug#957391: fixed in kaccounts-integration 4:20.07.90-1 has caused the Debian Bug report #957391, regarding kaccounts-integration: ftbfs with GCC-10 to be marked as done. This means that you claim that the

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

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 13:00:17 + with message-id and subject line Bug#966920: fixed in spoa 3.4.0-1 has caused the Debian Bug report #966920, regarding spoa: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below to be

Processed: tagging 952319

2020-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 952319 + buster Bug #952319 {Done: Giuseppe Sacco } [src:hylafax] hylafax: FTBFS: Incompatible TIFF Library. Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 952319:

Processed: unarchiving 952319

2020-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 952319 Bug #952319 {Done: Giuseppe Sacco } [src:hylafax] hylafax: FTBFS: Incompatible TIFF Library. Unarchived Bug 952319 > thanks Stopping processing here. Please contact me if you need assistance. -- 952319:

Bug#966438: src:bambam: Autopkgtest fail wiht newer imagemagick*

2020-08-07 Thread Marcin Owsiany
Bastien, the screenshot is there, in the artifact tarball from autopkgtest. I had some free time today and took a look at this in some detail. The problem is indeed in the changed output format from "convert", bambam is working as expected. I have a fix ready and hope to upload it this weekend

Bug#957693: marked as done (pmacct: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 12:19:34 + with message-id and subject line Bug#957693: fixed in pmacct 1.7.5-1 has caused the Debian Bug report #957693, regarding pmacct: 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#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-07 Thread Andreas Tille
Hi Thorsten, On Thu, Aug 06, 2020 at 04:04:22PM +0200, Thorsten Glaser wrote: > On Thu, 6 Aug 2020, Andreas Tille wrote: > > > [ERROR] > > /build/jimfs-1.1/jimfs/src/main/java/com/google/common/jimfs/PathService.java:[290,30] > > error: is not abstract > > and does not override abstract

Bug#967017: [request-tracker-maintainers] Bug#967017: Bug#967017: request-tracker4: FTBFS: can't exec /usr/bin/gpg

2020-08-07 Thread Andrew Ruthven
On Mon, 2020-08-03 at 15:48 +0100, Dominic Hargreaves wrote: > This seems related to changes in libgnupg-interface-perl, which on > the > face of it is ignoring the instruction to use 'gpg1' (configured via > the test_gnupg_interface_gpg1.diff patch). I can't immediately see > why > that's

Bug#968048: ax25-{,x}tools: both ship /usr/bin/smdiag and some more files

2020-08-07 Thread Andreas Beckmann
Package: ax25-tools,ax25-xtools Version: 0.0.10-rc5+git20190411+3595f87-2 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

Bug#957508: marked as done (luola: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 11:33:42 + with message-id and subject line Bug#957508: fixed in luola 1.3.2-13 has caused the Debian Bug report #957508, regarding luola: 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#968047: texlive-fonts-extra-links: missing Breaks+Replaces: texlive-fonts-extra (<< 2020.20200804)

2020-08-07 Thread Andreas Beckmann
Package: texlive-fonts-extra-links Version: 2020.20200804-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it

Processed: yubikey-personalization: diff for NMU version 1.20.0-2.1

2020-08-07 Thread Debian Bug Tracking System
Processing control commands: > tags 958010 + pending Bug #958010 [src:yubikey-personalization] yubikey-personalization: ftbfs with GCC-10 Ignoring request to alter tags of bug #958010 to the same tags previously set > tags 966606 + pending Bug #966606 [src:yubikey-personalization]

Processed: yubikey-personalization: diff for NMU version 1.20.0-2.1

2020-08-07 Thread Debian Bug Tracking System
Processing control commands: > tags 958010 + pending Bug #958010 [src:yubikey-personalization] yubikey-personalization: ftbfs with GCC-10 Added tag(s) pending. > tags 966606 + pending Bug #966606 [src:yubikey-personalization] yubikey-personalization: patch for newer json-c Added tag(s) pending.

Processed: bug 957487 is forwarded to https://github.com/facebook/zstd/issues/2204

2020-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 957487 https://github.com/facebook/zstd/issues/2204 Bug #957487 [src:libzstd] libzstd: ftbfs with GCC-10 Set Bug forwarded-to-address to 'https://github.com/facebook/zstd/issues/2204'. > thanks Stopping processing here. Please contact

Bug#958010: yubikey-personalization: diff for NMU version 1.20.0-2.1

2020-08-07 Thread Sebastian Ramacher
Control: tags 958010 + pending Control: tags 966606 + pending Dear maintainer, I've prepared an NMU for yubikey-personalization (versioned as 1.20.0-2.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru

Bug#957487: libzstd: ftbfs with GCC-10

2020-08-07 Thread Reiner Herrmann
Control: forward -1 https://github.com/facebook/zstd/issues/2204 Hi, the issue seems to be known upstream. As a workaround (until it is fixed properly), the package could be compiled without the -Werror flag, as this turns compiler warnings into errors, which causes the build to fail. Regards,

Bug#966604: libu2f-server: diff for NMU version 1.1.0-3.1

2020-08-07 Thread Sebastian Ramacher
Control: tags 966604 + pending Dear maintainer, I've prepared an NMU for libu2f-server (versioned as 1.1.0-3.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru libu2f-server-1.1.0/debian/changelog

Processed: libu2f-server: diff for NMU version 1.1.0-3.1

2020-08-07 Thread Debian Bug Tracking System
Processing control commands: > tags 966604 + pending Bug #966604 [src:libu2f-server] libu2f-server: patch for newer json-c Bug #966887 [src:libu2f-server] libu2f-server: FTBFS: core.c:480:58: error: ‘FALSE’ undeclared (first use in this function) Added tag(s) pending. Added tag(s) pending. --

Bug#966602: libu2f-host: diff for NMU version 1.1.10-1.1

2020-08-07 Thread Sebastian Ramacher
Control: tags 966602 + pending Dear maintainer, I've prepared an NMU for libu2f-host (versioned as 1.1.10-1.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru libu2f-host-1.1.10/debian/changelog

Bug#968046: dh-python: missing Breaks+Replaces: python2 (<< 2.7.18)

2020-08-07 Thread Andreas Beckmann
Package: dh-python Version: 4.20200804 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package fails to upgrade from 'testing'. It installed fine in 'testing', then the upgrade to 'sid' fails because it tries to overwrite other

Processed: libu2f-host: diff for NMU version 1.1.10-1.1

2020-08-07 Thread Debian Bug Tracking System
Processing control commands: > tags 966602 + pending Bug #966602 [src:libu2f-host] libu2f-host: patch for newer json-c Bug #966859 [src:libu2f-host] libu2f-host: FTBFS: u2fmisc.c:117:55: error: 'FALSE' undeclared (first use in this function) Added tag(s) pending. Added tag(s) pending. --

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

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 10:18:35 + with message-id and subject line Bug#966187: fixed in d1x-rebirth 0.58.1-1.2 has caused the Debian Bug report #966187, regarding d1x-rebirth: FTBFS with GCC 10: multiple definition of ... due to -fno-common to be marked as done. This means that

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

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 10:18:41 + with message-id and subject line Bug#966188: fixed in d2x-rebirth 0.58.1-1.3 has caused the Debian Bug report #966188, regarding d2x-rebirth: FTBFS with GCC 10: multiple definition of ... due to -fno-common to be marked as done. This means that

Bug#964611: [Pkg-pascal-devel] Bug#964611: libqtpas: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below

2020-08-07 Thread peter green
+#MISSING: 2.6+2.0.8+dfsg-1# _ZN7QVectorI6QPointE11reallocDataEii6QFlagsIN10QArrayData16AllocationOptionEE@Base 2.6~alpha c++filt -n decodes this to QVector::reallocData(int, int, QFlags) This looks like an instantiation of a QT template that may or may not be included in the library as a

Bug#957487: libzstd: ftbfs with GCC-10

2020-08-07 Thread Andreas Tille
Control: tags -1 help Hi, this issue is now RC and has not changed in current version 1.4.5. Any hint what to do? Kind regards Andreas. On Fri, Apr 17, 2020 at 11:05:08AM +, Matthias Klose wrote: > Package: src:libzstd > Version: 1.4.4+dfsg-3 > Severity: normal > Tags: sid bullseye

Processed: Re: Bug#957487: libzstd: ftbfs with GCC-10

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

Bug#957071: marked as done (ccextractor: ftbfs with GCC-10)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 09:18:27 + with message-id and subject line Bug#957071: fixed in ccextractor 0.88+ds1-1 has caused the Debian Bug report #957071, regarding ccextractor: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#957206: New upstream version available (Was: Bug#957206: fis-gtm: ftbfs with GCC-10)

2020-08-07 Thread Andreas Tille
Hi Amul, the fis-gtm version currently in Debian does not build with gcc-10 as you can read below. I realised we are lagging behind several versions and I've updated Git repository to the latest upstream version. Unfortunately it has other build issues. Could you please have a look? Kind

Bug#968035: Cannot migrate to testing due to Breaks: mercurial-crecord (<= 0.20151121-2)

2020-08-07 Thread Laurent Bigonville
Source: mercurial Version: 5.4.1-2 Severity: serious Hello, mercurial cannot migrate to testing due to the Breaks against mercurial-crecord (<= 0.20151121-2) It is discussed here[0] that mercurial-crecord 0.20151121-2 is now a transitional package that is displaying a NEWS message during the

Processed: severity of 804267 is normal

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

Bug#966301: guile oom test fails on ppc64el

2020-08-07 Thread Sebastian Ramacher
Hi Rob On 2020-08-01 18:54:05 -0500, Rob Browning wrote: > Matthias Klose writes: > > > https://buildd.debian.org/status/fetch.php?pkg=guile-2.2=ppc64el=2.2.7%2B1-5.1=1595497537=0 > > > > Apparently this is known, and already reported by Debian: > >

Bug#967154: marked as done (kross-interpreters: Unversioned Python removal in sid/bullseye)

2020-08-07 Thread Debian Bug Tracking System
Your message dated Fri, 07 Aug 2020 06:18:28 + with message-id and subject line Bug#967154: fixed in kross-interpreters 4:20.04.3-2 has caused the Debian Bug report #967154, regarding kross-interpreters: Unversioned Python removal in sid/bullseye to be marked as done. This means that you

Processed: your mail

2020-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 968013 Jan Wielemaker Bug #968013 [swi-prolog] swi-prolog: time bomb in swi-prolog-test, and failing autopkgtest Set Bug forwarded-to-address to 'Jan Wielemaker '. > tag 968013 confirmed upstream Bug #968013 [swi-prolog] swi-prolog:

Processed: tagging 967154

2020-08-07 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 967154 + pending Bug #967154 [src:kross-interpreters] kross-interpreters: Unversioned Python removal in sid/bullseye Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 967154:

Bug#957451: Patch

2020-08-07 Thread Dima Kogan
Here's a patch to fix the issue: diff --git a/src/libmawk/vio_fifo.h b/src/libmawk/vio_fifo.h index f170c22..a2d751d 100644 --- a/src/libmawk/vio_fifo.h +++ b/src/libmawk/vio_fifo.h @@ -14,7 +14,7 @@ typedef struct mawk_vio_fifo_s { int eof_from_app; /* 1 if there won't be more