Bug#945718: Python 3 Version

2020-08-08 Thread Soren Stoutner
Does anyone know if there is a Python 3 version planned, or is this the end of life for ownCloud Dolphin integration? -- Soren Stoutner 623-262-6169 so...@stoutner.com

Bug#922396: [Pkg-mozext-maintainers] Bug#922396: Updated package / patch and status information

2020-08-08 Thread Ximin Luo
I was the last person to upload noscript in 2018. The reason why I haven't updated it since 2018 is because I've moved onto using umatrix personally and also maintaining it in debian. umatrix gives you more fine-grained permissions including cookies, XHR, etc, so you don't need to install a

Bug#967224: closing 967224

2020-08-08 Thread Ximin Luo
close 967224 3.5.20-1 thanks In fact I'm not sure why this bug was even filed, there is no python dependency. Unless you mean transitively through mozilla-devscripts, which you fixed a short while ago. But then the bug report should only have been on that package, since it takes a single fix

Bug#967230: closing 967230

2020-08-08 Thread Ximin Luo
close 967230 1.4.0+dfsg-1 thanks In fact I'm not sure why this bug was even filed, there is no python dependency. Unless you mean transitively through mozilla-devscripts, which you fixed a short while ago. But then the bug report should only have been on that package, since it takes a single

Processed: closing 967230

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 967230 1.4.0+dfsg-1 Bug #967230 [src:umatrix] umatrix: Unversioned Python removal in sid/bullseye Marked as fixed in versions umatrix/1.4.0+dfsg-1. Bug #967230 [src:umatrix] umatrix: Unversioned Python removal in sid/bullseye Marked Bug as

Processed: closing 967224

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 967224 Bug #967224 [src:tree-style-tab] tree-style-tab: Unversioned Python removal in sid/bullseye Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 967224:

Processed: closing 967224

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 967224 3.5.20-1 Bug #967224 {Done: Ximin Luo } [src:tree-style-tab] tree-style-tab: Unversioned Python removal in sid/bullseye The source 'tree-style-tab' and version '3.5.20-1' do not appear to match any binary packages Marked as fixed

Processed: Reopen #966903

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reopen 966903 Bug #966903 {Done: Kari Pahula } [src:gecode] gecode: FTBFS: gecode/flatzinc/parser.tab.cpp:526:10: fatal error: parser.tab.hpp: No such file or directory 'reopen' may be inappropriate when a bug has been closed with a version;

Bug#966472: marked as done (bcbio: B-D biobambam2 not available in testing)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 22:18:30 + with message-id and subject line Bug#966472: fixed in biobambam2 2.0.173+ds-1 has caused the Debian Bug report #966472, regarding bcbio: B-D biobambam2 not available in testing to be marked as done. This means that you claim that the problem has

Bug#957841: marked as done (squidguard: ftbfs with GCC-10)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 22:19:11 + with message-id and subject line Bug#957841: fixed in squidguard 1.6.0-1.1 has caused the Debian Bug report #957841, regarding squidguard: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#966470: marked as done (biobambam2: autopkgtest failures: Segmentation fault bamsormadup < SRR11728627.bam > SRR11728627.sorted.bam)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 22:18:30 + with message-id and subject line Bug#966470: fixed in biobambam2 2.0.173+ds-1 has caused the Debian Bug report #966470, regarding biobambam2: autopkgtest failures: Segmentation fault bamsormadup < SRR11728627.bam > SRR11728627.sorted.bam to be

Bug#968106: phosh: Shell doesn't start

2020-08-08 Thread Michel Le Bihan
Package: phosh Version: 0.4.3-1 Severity: grave Justification: renders package unusable Hello, On a freshly created Debian sid live system: ``` sudo mmdebstrap --include=linux-image-amd64,live-boot,xserver-xorg-video- all,phosh --arch amd64 sid debian-live-root http://ftp.pl.debian.org/debian/

Bug#957188: marked as done (exiv2: ftbfs with GCC-10)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 22:05:43 + with message-id and subject line Bug#957188: fixed in exiv2 0.27.3-1 has caused the Debian Bug report #957188, regarding exiv2: 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#961856: marked as pending in kodi

2020-08-08 Thread Balint Reczey
Control: tag -1 pending Hello, Bug #961856 in kodi 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#961856 marked as pending in kodi

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

Bug#967205: No python package

2020-08-08 Thread Marcos Fouces
Hi! I think that rfdump package is not related with Python. I think there is a mistake. Greetings, Marcos

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

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 20:52:56 + with message-id and subject line Bug#966781: fixed in python-pam 0.4.2-13.3 has caused the Debian Bug report #966781, regarding python-pam: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#966792: marked as done (scid: Unversioned Python removal in sid/bullseye)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 20:53:03 + with message-id and subject line Bug#966792: fixed in scid 1:4.7.0+dfsg1-1.1 has caused the Debian Bug report #966792, regarding scid: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#967163: marked as done (libiptcdata: Unversioned Python removal in sid/bullseye)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 20:52:35 + with message-id and subject line Bug#967163: fixed in libiptcdata 1.0.5-2.2 has caused the Debian Bug report #967163, regarding libiptcdata: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#966753: marked as done (libiptcdata: Unversioned Python removal in sid/bullseye)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 20:52:35 + with message-id and subject line Bug#966753: fixed in libiptcdata 1.0.5-2.2 has caused the Debian Bug report #966753, regarding libiptcdata: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#936880: marked as done (libiptcdata: Python2 removal in sid/bullseye)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 20:52:35 + with message-id and subject line Bug#966753: fixed in libiptcdata 1.0.5-2.2 has caused the Debian Bug report #966753, regarding libiptcdata: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

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-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 20:52:12 + with message-id and subject line Bug#966903: fixed in gecode 6.2.0-4 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#966905: marked as done (minizinc: FTBFS: parser.tab.cpp:178:10: fatal error: parser.tab.hh: No such file or directory)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 20:52:41 + with message-id and subject line Bug#966905: fixed in minizinc 2.4.3-3 has caused the Debian Bug report #966905, regarding minizinc: FTBFS: parser.tab.cpp:178:10: fatal error: parser.tab.hh: No such file or directory to be marked as done. This

Bug#967175: marked as done (mozilla-devscripts: Unversioned Python removal in sid/bullseye)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 20:30:24 + with message-id and subject line Bug#967175: fixed in mozilla-devscripts 0.54.1 has caused the Debian Bug report #967175, regarding mozilla-devscripts: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim

Bug#957370: marked as done (ipv6toolkit: ftbfs with GCC-10)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 19:49:34 + with message-id and subject line Bug#957370: fixed in ipv6toolkit 2.0+ds.1-1 has caused the Debian Bug report #957370, regarding ipv6toolkit: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#967932: marked as done (redland-bindings: FTBFS: lots of undefined reference errors from ld)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 8 Aug 2020 21:39:38 +0200 with message-id <40d7978e-bb7b-759f-bc0e-a94d2772f...@debian.org> and subject line Re: redland-bindings: FTBFS: lots of undefined reference errors from ld has caused the Debian Bug report #967932, regarding redland-bindings: FTBFS: lots of

Bug#966210: marked as done (src:django-ranged-response: fails to migrate to testing for too long: maintainer built arch:all binary)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 19:34:11 + with message-id and subject line Bug#966210: fixed in django-ranged-response 0.2.0-4.1 has caused the Debian Bug report #966210, regarding src:django-ranged-response: fails to migrate to testing for too long: maintainer built arch:all binary to

Bug#957086: chordii: diff for NMU version 4.5.3+repack-0.2

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

Processed: chordii: diff for NMU version 4.5.3+repack-0.2

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

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

2020-08-08 Thread Abou Al Montacir
Hi Paul On Fri, 2020-08-07 at 15:16 +0200, Abou Al Montacir wrote: > I'm going to upload both FPC 3.2.0 and Lazarus 2.0.10. So maybe you can wait > until I upload them before fixing this? I've just pushed new sources for libqtpat 2.6+2.0.10+dfsg. I've verified in cowbuilder that we have the very

Bug#963394: marked as done (apper: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 18:48:34 + with message-id and subject line Bug#962567: fixed in debconf-kde 1.0.3-4 has caused the Debian Bug report #962567, regarding apper: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr

Bug#962567: marked as done (libdebconf-kde-dev misses dependencies)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 18:48:34 + with message-id and subject line Bug#962567: fixed in debconf-kde 1.0.3-4 has caused the Debian Bug report #962567, regarding libdebconf-kde-dev misses dependencies to be marked as done. This means that you claim that the problem has been dealt

Bug#963432: marked as done (muon: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_BUILD_TYPE=None -DCMAKE_INSTALL_SYSCONFDIR=/etc -DCMAKE_INSTALL_

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 18:48:34 + with message-id and subject line Bug#962567: fixed in debconf-kde 1.0.3-4 has caused the Debian Bug report #962567, regarding muon: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr

Bug#944401: marked as done (pgcli: does not start due to unmet psycopg2 requirement)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 8 Aug 2020 20:12:21 +0200 with message-id and subject line Re: pgcli: does not start due to unmet psycopg2 requirement has caused the Debian Bug report #944401, regarding pgcli: does not start due to unmet psycopg2 requirement to be marked as done. This means that you

Processed: tagging 962567

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 962567 + pending Bug #962567 [libdebconf-kde-dev] libdebconf-kde-dev misses dependencies Bug #963394 [libdebconf-kde-dev] apper: FTBFS: dh_auto_configure: error: cd obj-x86_64-linux-gnu && cmake -DCMAKE_INSTALL_PREFIX=/usr

Bug#960463: marked as done (mycli doesn't work the prompt-toolkit >= 3.0.0)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 18:03:42 + with message-id and subject line Bug#960463: fixed in mycli 1.22.2-0.1 has caused the Debian Bug report #960463, regarding mycli doesn't work the prompt-toolkit >= 3.0.0 to be marked as done. This means that you claim that the problem has been

Bug#966857: libtpms: FTBFS: tpm2/NVDynamic.c:126:10: error: ‘nvHandle’ may be used uninitialized in this function [-Werror=maybe-uninitialized]

2020-08-08 Thread Seunghun Han
Hi Lucas, On Mon, Aug 3, 2020 at 5:12 PM Lucas Nussbaum wrote: > > Source: libtpms > Version: 0.8.0~dev1-1.1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200802 ftbfs-bullseye > ... [snip] ... > > tpm2/NVDynamic.c: In function ‘NvNextByType’:

Bug#940793: marked as done (Please replace transitional dependency polkit-kde-1 with polkit-kde-agent-1)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 17:33:25 + with message-id and subject line Bug#940793: fixed in apper 1.0.0-3 has caused the Debian Bug report #940793, regarding Please replace transitional dependency polkit-kde-1 with polkit-kde-agent-1 to be marked as done. This means that you claim

Processed: tagging 946341, tagging 950631, tagging 957188

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 946341 + pending Bug #946341 [src:exiv2] exiv2: CVE-2019-17402 Added tag(s) pending. > tags 950631 + pending Bug #950631 [src:exiv2] exiv2: please mark one symbol as optional Added tag(s) pending. > tags 957188 + pending Bug #957188

Bug#966470: fix for #966470: biobambam2 autopkgtest failures

2020-08-08 Thread Étienne Mollier
Control: tags -1 pending Good day, I had a look at the autopkgtest failure affecting biobambam2, and since these segmentation faults were showing up only in my autopkgtest environment, and not when using the package directly on my system, it felt like a missing dependency. So I trapped system

Processed: fix for #966470: biobambam2 autopkgtest failures

2020-08-08 Thread Debian Bug Tracking System
Processing control commands: > tags -1 pending Bug #966470 [biobambam2] biobambam2: autopkgtest failures: Segmentation fault bamsormadup < SRR11728627.bam > SRR11728627.sorted.bam Added tag(s) pending. -- 966470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966470 Debian Bug Tracking

Bug#967150: closed by Debian FTP Masters (reply to tony mancill ) (Bug#967150: fixed in jython 2.7.2+repack1-2)

2020-08-08 Thread tony mancill
Hi Gilles, On Wed, Aug 05, 2020 at 11:36:05PM +, Debian Bug Tracking System wrote: > Date: Wed, 05 Aug 2020 16:01:50 -0700 > Source: jython > Architecture: source > Version: 2.7.2+repack1-2 > Distribution: experimental > Urgency: medium > Maintainer: Debian Java Maintainers > > Changed-By:

Processed: bug 966904 is forwarded to https://sourceforge.net/p/pfstools/bugs/48/

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 966904 https://sourceforge.net/p/pfstools/bugs/48/ Bug #966904 [src:pfstools] pfstools: FTBFS: array2d.h:173:9: error: ‘__assert_fail’ was not declared in this scope; did you mean ‘MagickCore::__assert_fail’? Set Bug

Bug#963396: marked as done (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-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 15:48:41 + with message-id and subject line Bug#963396: fixed in jimfs 1.1-6 has caused the Debian Bug report #963396, regarding jimfs: FTBFS: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on

Processed: Debian bugs #958005

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 958005 https://sourceforge.net/p/xtrkcad-fork/bugs/390/ Bug #958005 [src:xtrkcad] xtrkcad: ftbfs with GCC-10 Set Bug forwarded-to-address to 'https://sourceforge.net/p/xtrkcad-fork/bugs/390/'. > -- Stopping processing here. Please

Bug#966787: marked as done (redland-bindings: Unversioned Python removal in sid/bullseye)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 15:22:31 + with message-id and subject line Bug#966787: fixed in redland-bindings 1.0.17.1+dfsg-1.4 has caused the Debian Bug report #966787, regarding redland-bindings: Unversioned Python removal in sid/bullseye to be marked as done. This means that you

Bug#966740: marked as done (giella-core: Unversioned Python removal in sid/bullseye)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 15:03:32 + with message-id and subject line Bug#966740: fixed in giella-core 0.1.1~r129227+svn121148-2.1 has caused the Debian Bug report #966740, regarding giella-core: Unversioned Python removal in sid/bullseye to be marked as done. This means that you

Bug#964686: marked as done (node-ytdl-core: FTBFS: dh_auto_build: error: cd ./m3u8stream && sh -ex ../debian/nodejs/m3u8stream/build returned exit code 2)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 14:35:58 + with message-id and subject line Bug#964637: fixed in typescript-types 20200808-1 has caused the Debian Bug report #964637, regarding node-ytdl-core: FTBFS: dh_auto_build: error: cd ./m3u8stream && sh -ex ../debian/nodejs/m3u8stre

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

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 14:35:58 + with message-id and subject line Bug#964637: fixed in typescript-types 20200808-1 has caused the Debian Bug report #964637, regarding node-rollup: FTBFS: dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exi

Bug#961224: marked as done (python-cobra: test failures on s390x)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 14:35:46 + with message-id and subject line Bug#961224: fixed in python-cobra 0.18.1-2 has caused the Debian Bug report #961224, regarding python-cobra: test failures on s390x to be marked as done. This means that you claim that the problem has been dealt

Bug#964637: marked as pending in typescript-types

2020-08-08 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #964637 in typescript-types 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#964637 marked as pending in typescript-types

2020-08-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #964637 [node-typescript-types] node-rollup: FTBFS: dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code 1 Bug #964686 [node-typescript-types] node-ytdl-core: FTBFS: dh_auto_build: error: cd ./m3u8stream && sh -ex

Bug#961224: python-cobra: test failures on s390x

2020-08-08 Thread Andreas Tille
Hi, On Sat, May 23, 2020 at 02:56:22PM +0300, Adrian Bunk wrote: > [ debian-s390 added ] > > On Thu, May 21, 2020 at 05:03:19PM +0100, peter green wrote: > > Source: python-cobra > > Version: 0.18.0-1 > > Severity: serious > > > > Three of the last four builds of python-cobra on s390x have

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

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 12:33:28 + with message-id and subject line Bug#967032: fixed in nodejs 12.18.3~dfsg-4 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#968079: [Python-modules-team] Bug#968079: libapache2-mod-wsgi: Package is not installable. Needs older Python2.

2020-08-08 Thread Emmanuel Arias
Hi, That problem seems to be fixed on salsa, but I am waiting for a review. Cheers, Arias Emmanuel @eamanu http://eamanu.com El sáb., 8 de ago. de 2020 a la(s) 04:15, greylistd Python issue (n...@dagami.org) escribió: > > Package: libapache2-mod-wsgi > Version: 4.6.8-1+b1 > Severity: grave >

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

2020-08-08 Thread Michael Meskes
> > I'm surprised it is actually used as it was pointed out to me that > > the script > > has been non-functional for quite a while. > > I do recall having an issue with it at one point a few years back and > meaning to submit a patch to bsdmainutils to fix it, but resolved it > one way or

Processed: affects 964686

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 964686 node-ytdl-core Bug #964686 [node-typescript-types] node-ytdl-core: FTBFS: dh_auto_build: error: cd ./m3u8stream && sh -ex ../debian/nodejs/m3u8stream/build returned exit code 2 Bug #964637 [node-typescript-types] node-rollup:

Processed: affects 964637

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 964637 rollup Bug #964637 [node-typescript-types] node-rollup: FTBFS: dh_auto_build: error: cd ./. && sh -ex debian/nodejs/./build returned exit code 1 Bug #964686 [node-typescript-types] node-ytdl-core: FTBFS: dh_auto_build: error: cd

Processed: raise severity

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 953006 serious Bug #953006 [dbacl] Switch to current libreadline Severity set to 'serious' from 'normal' > End of message, stopping processing here. Please contact me if you need assistance. -- 953006:

Processed: reassign 964686 to node-typescript-types, forcibly merging 964686 964637

2020-08-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 964686 node-typescript-types Bug #964686 [src:node-ytdl-core] node-ytdl-core: FTBFS: dh_auto_build: error: cd ./m3u8stream && sh -ex ../debian/nodejs/m3u8stream/build returned exit code 2 Bug reassigned from package 'src:node-ytdl-core'

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-08 Thread Abou Al Montacir
Hi Paul, On Fri, 2020-08-07 at 19:55 +0200, Paul Gevers wrote: > Hi, > I am preparing an upload with the symbols file removed as there seems tobe > consensus that using symbols files for C++ projects in Debian isn'tworth the > effort. It will probably require to use 2.0.10 based libQtPas, as I'

Bug#946046: marked as done (unison-all should also depend on the old unison version, compatible with Debian 10)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 10:33:55 + with message-id and subject line Bug#946046: fixed in meta-unison 2.48.4+3 has caused the Debian Bug report #946046, regarding unison-all should also depend on the old unison version, compatible with Debian 10 to be marked as done. This means

Processed: Bug#946046 marked as pending in meta-unison

2020-08-08 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #946046 [unison-all] unison-all should also depend on the old unison version, compatible with Debian 10 Added tag(s) pending. -- 946046: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946046 Debian Bug Tracking System Contact

Bug#946046: marked as pending in meta-unison

2020-08-08 Thread Stéphane Glondu
Control: tag -1 pending Hello, Bug #946046 in meta-unison reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at:

Bug#946046: not fixed

2020-08-08 Thread Vincent Lefevre
On 2020-08-08 10:04:10 +0200, Stéphane Glondu wrote: > I still think it is useful to have a unison 2.48 compiled with OCaml > 4.08.1 around. Perhaps, but you should make sure that this version cannot be used together with buster's unison 2.48, because there are not compatible and can corrupt

Bug#946046: not fixed

2020-08-08 Thread Vincent Lefevre
On 2020-08-08 09:53:21 +0200, Stéphane Glondu wrote: > Le 08/08/2020 à 03:25, Vincent Lefevre a écrit : > > The wontfix does not make any sense. The unison-all package is > > described as follows: > > > > Description: file synchronization tool (all console versions) > > This is a metapackage

Processed: Re: catimg: ftbfs with GCC-10

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

Bug#957066: catimg: ftbfs with GCC-10

2020-08-08 Thread Étienne Mollier
Control: tags -1 fixed-upstream Control: tags -1 patch Greetings, The "master" branch of the upstream repository has a change that includes a fix for the failure to build from source with Gcc 10: https://github.com/posva/catimg/commit/05b946cc5cb96ffc36aea41dfcdac9ddbce2cb33 The patch

Bug#946046: not fixed

2020-08-08 Thread Stéphane Glondu
Le 08/08/2020 à 02:41, Vincent Lefevre a écrit : > unison-2.48 should have never been created: buster has a unison > package with version number 2.48.4-1, thus one has the impression > that this is compatible with unison-2.48, while this is not the > case. The package should have been named

Bug#946046: not fixed

2020-08-08 Thread Stéphane Glondu
Le 08/08/2020 à 03:25, Vincent Lefevre a écrit : > The wontfix does not make any sense. The unison-all package is > described as follows: > > Description: file synchronization tool (all console versions) > This is a metapackage that depends on all supported console versions > of Unison, a file

Bug#957217: marked as done (forked-daapd: ftbfs with GCC-10)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 07:33:30 + with message-id and subject line Bug#957217: fixed in forked-daapd 26.4+dfsg1-2 has caused the Debian Bug report #957217, regarding forked-daapd: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt

Bug#968079: libapache2-mod-wsgi: Package is not installable. Needs older Python2.

2020-08-08 Thread greylistd Python issue
Package: libapache2-mod-wsgi Version: 4.6.8-1+b1 Severity: grave Justification: renders package unusable Dear Maintainer, When trying to install the package, the following message is displayed: == begin Reading package lists... Done Building dependency tree Reading

Bug#957217: marked as pending in forked-daapd

2020-08-08 Thread Sebastian Ramacher
Control: tag -1 pending Hello, Bug #957217 in forked-daapd 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#966166: marked as done (src:v4l-utils: fails to migrate to testing for too long: maintainer built arch:all)

2020-08-08 Thread Debian Bug Tracking System
Your message dated Sat, 08 Aug 2020 07:05:48 + with message-id and subject line Bug#966166: fixed in v4l-utils 1.20.0-1.1 has caused the Debian Bug report #966166, regarding src:v4l-utils: fails to migrate to testing for too long: maintainer built arch:all to be marked as done. This means

Processed: Bug#957217 marked as pending in forked-daapd

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

Processed: tagging 957122

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

Bug#957217: forked-daapd: ftbfs with GCC-10

2020-08-08 Thread Sebastian Ramacher
On 2020-07-31 12:37:13 +0200, Gianfranco Costamagna wrote: > control: tags -1 patch > > > Description: Fix build with gcc-10 > Author: Gianfranco Costamagna > Last-Update: 2020-07-31 > > --- forked-daapd-26.4+dfsg1.orig/src/input.h > +++ forked-daapd-26.4+dfsg1/src/input.h > @@ -137,7 +137,7

Bug#968076: bind-dyndb-ldap FTBFS on 32bit: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘unsigned int’

2020-08-08 Thread Adrian Bunk
Source: bind-dyndb-ldap Version: 11.3-1 Severity: serious Tags: ftbfs https://buildd.debian.org/status/package.php?p=bind-dyndb-ldap=sid ... ../../src/syncrepl.c: In function ‘sync_task_add’: ../../src/syncrepl.c:460:15: error: format ‘%lu’ expects argument of type ‘long unsigned int’, but