Bug#937413: pycryptopp: Python2 removal in sid/bullseye

Hi Moritz, Moritz Mühlenhoff writes: > > Hi Vasudev, > > https://github.com/tahoe-lafs/pycryptopp/issues/36#issuecomment-504130020 > states: > > | The Tahoe-LAFS project has decided it is not interested in porting > | pycryptopp to Python 3. Instead, Tahoe-LAFS is switching to the > | "cryptogra

Processed: severity of 959828 is important

Processing commands for cont...@bugs.debian.org: > severity 959828 important Bug #959828 [systemctl] systemctl: `Provides: systemd`, but doesn't provide what systemd does Severity set to 'important' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 9

Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does

On Wednesday, 6 May 2020 8:28:09 AM AEST Ansgar wrote: > The last upload adds `Provides: systemd`, but `systemctl` obviously > doesn't provide the same (or similar) functionality as the `systemd` > package. It does provide similar functionality under certain circumstances such as inside applicati

Bug#938846: marked as done (xia: Python2 removal in sid/bullseye)

Your message dated Tue, 05 May 2020 23:48:13 + with message-id and subject line Bug#959796: Removed package(s) from unstable has caused the Debian Bug report #938846, regarding xia: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#938365: marked as done (ropemode: Python2 removal in sid/bullseye)

Your message dated Tue, 05 May 2020 23:49:04 + with message-id and subject line Bug#959824: Removed package(s) from unstable has caused the Debian Bug report #938365, regarding ropemode: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#959801: marked as done (ropemode: Consider removing it from Debian)

Your message dated Tue, 05 May 2020 23:49:04 + with message-id and subject line Bug#959824: Removed package(s) from unstable has caused the Debian Bug report #959801, regarding ropemode: Consider removing it from Debian to be marked as done. This means that you claim that the problem has been

Bug#959565: libjdom2-intellij-java: FTBFS: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':contrib:co

Control: reassign -1 libxalan2-java Control: found -1 2.7.2-3 Control: severity -1 important Control: affects -1 + libjdom2-intellij-java Control: retitle -1 libxalan2-java: xml-apis dependency left in the xalan:serializer pom The actual issue is with libxalan2-java, because the xalan:serializer

Processed: Re: Bug#959565: libjdom2-intellij-java: FTBFS: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configurati

Processing control commands: > reassign -1 libxalan2-java Bug #959565 [src:libjdom2-intellij-java] libjdom2-intellij-java: FTBFS: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':contrib:compileClas

Bug#959567: marked as done (dom4j: FTBFS: org.gradle.api.internal.artifacts.ivyservice.DefaultLenientConfiguration$ArtifactResolveException: Could not resolve all files for configuration ':testCompile

> Caused by: org.gradle.internal.resolve.ModuleVersionResolveException: Could > not resolve xml-apis:xml-apis:debian. > Required by: > project : > xalan:xalan:debian > xalan:serializer:debian The actual issue is with libxalan2-java, because the xalan:serializer pom depends on xml-apis but the

Bug#942988: displaycal: Python2 removal in sid/bullseye

Hey, just letting you know upstream is indeed still alive. As you have noticed, things take longer than expected, and not all is due to the move to Python3. While I appreciate the offer to help, at the moment it would make things harder to juggle for me. The reason there is no commits over at

Bug#959828: systemctl: `Provides: systemd`, but doesn't provide what systemd does

Package: systemctl Version: 1.4.4147-2 Severity: serious The last upload adds `Provides: systemd`, but `systemctl` obviously doesn't provide the same (or similar) functionality as the `systemd` package. As a random example, systemd-tmpfiles and other utilities are not provided by `systemctl`. An

Bug#959637: marked as done (beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev)

Your message dated Tue, 05 May 2020 22:03:36 + with message-id and subject line Bug#959637: fixed in beads 1.1.19+dfsg-1 has caused the Debian Bug report #959637, regarding beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev to be marked as done. This means that you claim tha

Bug#937413: pycryptopp: Python2 removal in sid/bullseye

On Fri, Aug 30, 2019 at 07:33:16AM +, Matthias Klose wrote: > Package: src:pycryptopp > Version: 0.7.1-4 > Severity: normal > Tags: sid bullseye > User: debian-pyt...@lists.debian.org > Usertags: py2removal > > Python2 becomes end-of-live upstream, and Debian aims to remove > Python2 from the

Bug#959582: marked as done (castle-game-engine: FTBFS: tries to write stuff to homedir?)

Your message dated Tue, 05 May 2020 20:34:10 + with message-id and subject line Bug#959582: fixed in castle-game-engine 6.4+dfsg1-3 has caused the Debian Bug report #959582, regarding castle-game-engine: FTBFS: tries to write stuff to homedir? to be marked as done. This means that you claim t

Bug#959697: marked as done (mpfi: FTBFS on arch where texinfo is not installed)

Your message dated Tue, 05 May 2020 20:35:15 + with message-id and subject line Bug#959697: fixed in mpfi 1.5.3+ds-4 has caused the Debian Bug report #959697, regarding mpfi: FTBFS on arch where texinfo is not installed to be marked as done. This means that you claim that the problem has been

Bug#939962: builds in git

Hi, Upstream moved to https://github.com/SKS-Keyserver/sks-keyserver git master builds with 4.08 : https://travis-ci.org/github/SKS-Keyserver/sks-keyserver/jobs/683544082 I will look to make a release --

Bug#955689: libcatmandu-filestore-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 255

On Fri, Apr 03, 2020 at 09:52:13PM +0200, Lucas Nussbaum wrote: > Source: libcatmandu-filestore-perl > Version: 1.13-2 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200402 ftbfs-bullseye > > # Error: Can't locate Data/UUID.pm in @INC (you m

Processed: libcatmandu-perl: 1.2011-1 breaks libcatmandu-filestore-perl

Processing control commands: > block -1 with 955689 Bug #959818 [libcatmandu-perl] libcatmandu-perl: 1.2011-1 breaks libcatmandu-filestore-perl 959818 was not blocked by any bugs. 959818 was not blocking any bugs. Added blocking bug(s) of 959818: 955689 -- 959818: https://bugs.debian.org/cgi-bi

Bug#959818: libcatmandu-perl: 1.2011-1 breaks libcatmandu-filestore-perl

Package: libcatmandu-perl Version: 1.2011-1 Severity: serious Control: block -1 with 955689 1.2011-1 in unstable dropped its dependency on libdata-uuid-perl, unmasking a missing dependency in libcatmandu-filestore-perl (#955689). This was noticed by autopkgtest checks, currently preventing testing

Bug#863650: Fix available

Hi, I submitted a patch for this issue upstream: https://github.com/pam-pgsql/pam-pgsql/pull/16 Jan

Processed: oggvideotools: Test dependency on pysycache-i18n that will likely be removed

Processing control commands: > block 912504 by -1 Bug #912504 [src:pysycache] pysycache: Please migrate to python3-pygame 912504 was not blocked by any bugs. 912504 was blocking: 937441 937695 Added blocking bug(s) of 912504: 959814 > block 937553 by -1 Bug #937553 [src:pysycache] pysycache: Pytho

Bug#959814: oggvideotools: Test dependency on pysycache-i18n that will likely be removed

Source: oggvideotools Version: 0.9.1-5 Severity: serious Tags: ftbfs bullseye sid Control: block 912504 by -1 Control: block 937553 by -1 pysycache-i18n will likely be removed due to #912504 and #937553. Options are to change yet again to another ogg for this test, or to remove this specific test

Bug#959587: python-biopython: FTBFS: AssertionError: False is not true

Control: tags -1 upstream Control: forwarded -1 Peter Cock Hi Peter, with the upload of ncbi-blast+ version 2.10 Biopython test is running into failures (see https://bugs.debian.org/959587#10 ) Could you please adjust the Biopython test suite accordingly? Kind regards Andreas. On

Processed: Re: Bug#959587: python-biopython: FTBFS: AssertionError: False is not true

Processing control commands: > tags -1 upstream Bug #959587 [src:python-biopython] python-biopython: FTBFS: AssertionError: False is not true Added tag(s) upstream. > forwarded -1 Peter Cock Bug #959587 [src:python-biopython] python-biopython: FTBFS: AssertionError: False is not true Set Bug fo

Bug#787599: marked as done (Some sources are not included in your package)

Your message dated Tue, 05 May 2020 18:33:25 + with message-id and subject line Bug#787599: fixed in ganglia-web 3.6.1-3.1 has caused the Debian Bug report #787599, regarding Some sources are not included in your package to be marked as done. This means that you claim that the problem has bee

Processed: src:libqtdbusmock: fails to migrate to testing for too long: FTBFS on all release archs

Processing control commands: > close -1 0.7+bzr49+repack1-4 Bug #959813 [src:libqtdbusmock] src:libqtdbusmock: fails to migrate to testing for too long: FTBFS on all release archs Marked as fixed in versions libqtdbusmock/0.7+bzr49+repack1-4. Bug #959813 [src:libqtdbusmock] src:libqtdbusmock: fai

Bug#959813: src:libqtdbusmock: fails to migrate to testing for too long: FTBFS on all release archs

Source: libqtdbusmock Version: 0.7+bzr49+repack1-3 Severity: serious Control: close -1 0.7+bzr49+repack1-4 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-s

Bug#959631: hy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.8 returned exit code 13

On Sun, 3 May 2020 at 06:12, Lucas Nussbaum wrote: > > ... > > === warnings summary > > === > > .pybuild/cpython3_3.8_hy/build/tests/native_tests/comprehensions.hy::test_fors[sfor] > > /<>/hy/models.py:133: RuntimeWarning: coroutine '' >

Processed: affects 959374

Processing commands for cont...@bugs.debian.org: > affects 959374 src:proteinortho Bug #959374 [src:diamond-aligner] diamond-aligner FTBFS on big endian Added indication that 959374 affects src:proteinortho > thanks Stopping processing here. Please contact me if you need assistance. -- 959374: h

Bug#939932: marked as done (varnish-modules: FTBFS after new varnish update)

Your message dated Tue, 05 May 2020 18:19:37 + with message-id and subject line Bug#939932: fixed in varnish-modules 0.16.0-1 has caused the Debian Bug report #939932, regarding varnish-modules: FTBFS after new varnish update to be marked as done. This means that you claim that the problem ha

Bug#959607: marked as done (mailscripts: FTBFS: imap-dl:94: error: Incompatible types in assignment (expression has type "Tuple[Literal['OK'], List[bytes]]", variable has type "Tuple[str, List[Union[b

Your message dated Tue, 05 May 2020 18:18:36 + with message-id and subject line Bug#959607: fixed in mailscripts 0.20-1 has caused the Debian Bug report #959607, regarding mailscripts: FTBFS: imap-dl:94: error: Incompatible types in assignment (expression has type "Tuple[Literal['OK'], List[b

Processed: Bug#959637: marked as done (beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev)

Processing commands for cont...@bugs.debian.org: > reopen 959637 Bug #959637 {Done: Filippo Rusconi } [src:beads] beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and y

Bug#954645: closed by Lucas Nussbaum (unreproducible FTBFS)

Control: tags -1 patch On Fri, 3 Apr 2020 21:40:10 +0200 Lucas Nussbaum wrote: > > I'm closing those bugs: those failures are no longer reproducible, > > checking again 12 hours later. Either they were caused by another > > package that was fixed in the meantime, or they are random failures. > >

Processed: Re: Bug#954645 closed by Lucas Nussbaum (unreproducible FTBFS)

Processing control commands: > tags -1 patch Bug #954645 [src:behave] behave: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.7 3.8" returned exit code 13 Added tag(s) patch. -- 954645: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954645 Debian Bug Tracking

Bug#959637: marked as done (beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev)

Your message dated Tue, 05 May 2020 16:33:44 + with message-id and subject line Bug#959637: fixed in libodsstream 0.7.8-1 has caused the Debian Bug report #959637, regarding beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev to be marked as done. This means that you claim th

Processed: Re: broadcom-sta-dkms: Wl driver 6.30.223.271 (r587334) failed with code 21

Processing control commands: > notfixed -1 6.30.223.271-14 Bug #959002 [broadcom-sta-dkms] broadcom-sta-dkms: Wl driver 6.30.223.271 (r587334) failed with code 21 No longer marked as fixed in versions broadcom-sta/6.30.223.271-14. > severity -1 important Bug #959002 [broadcom-sta-dkms] broadcom-s

Bug#959002: broadcom-sta-dkms: Wl driver 6.30.223.271 (r587334) failed with code 21

control: notfixed -1 6.30.223.271-14 control: severity -1 important Dear Gert, Please CC me when you reply. Thank you! > bullseye: > status installed broadcom-sta-dkms:all 6.30.223.271-14 > buster-backports: > status installed broadcom-sta-dkms:all 6.30.223.271-14~bpo10+1 > This also did not wor

Bug#959637: Please provide pristine-tar for libodsstream - or at least way to get upstream source (Was: Bug#959637: beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev)

Greetings, Andreas, I hope you are doing fine in these difficult times. On Tue, May 05, 2020 at 02:25:58PM +0200, Andreas Tille wrote: Hi Filippo, I tried to investigate this issue of beads: On Sun, May 03, 2020 at 02:34:20PM +0200, Lucas Nussbaum wrote: During a rebuild of all packages in s

Bug#959684: salt: CVE-2020-11651 and CVE-2020-11652

There are official patches from saltstack available here: 2018.3.x 2017.7.x 2016.x.x I requested them via https://www.saltstack.com/lp/request-patc

Bug#949222: Bug#959684: salt: CVE-2020-11651 and CVE-2020-11652

On Tue, 05 May 2020 at 17:37:53 +0200, Salvatore Bonaccorso wrote: > Do you have respective stretch and buster setups which you could > expose those packages to? Sorry, no: the owner of the machines I was looking at asked me to switch over to upstream's packages. smcv

Bug#959587: python-biopython: FTBFS: AssertionError: False is not true

Andreas Tille writes: > I've checked ncbi-blast+ and your last upload does not seem to be > pushed. AFAICT, it's all properly at https://salsa.debian.org/med-team/ncbi-blastplus. > Since there is a strong relation in time with your upload and this > FTBFS of biopython do you think that this cou

Bug#949222: Bug#959684: salt: CVE-2020-11651 and CVE-2020-11652

Hi Simon, On Tue, May 05, 2020 at 03:01:45PM +0100, Simon McVittie wrote: > On Mon, 04 May 2020 at 01:34:33 +0200, Guilhem Moulin wrote: > > CVE-2020-11651 > > CVE-2020-11652 > > I found myself needing to mitigate this for a salt deployment, so I > tried backporting the upstream patches to bu

Bug#959364: PR with patch

Oops, I was a bit careless. Let me clarify: the patch in my PR is not from the actual upstream for the package, but rather from the fork [1] linked to by Thomas Koch in #959729 [2]. [1] https://github.com/teleshoes/acpi_call [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959729#10

Bug#948706: greylistd: python3 version fails to start - conversion from python 2 very broken

Followup-For: Bug #948706 Package: greylistd Version: 0.8.8.8 Tags: patch Hi, I run into the very same problems while setting up a system. Since I found some spare cycles I looked at the code and made some patches. For simpler development I have set up a git repo and have import the packages foun

Bug#958798: marked as done (cpufreqd: FTBFs on ppc64el)

Your message dated Tue, 05 May 2020 14:48:31 + with message-id and subject line Bug#958798: fixed in cpufreqd 2.4.2-2.3 has caused the Debian Bug report #958798, regarding cpufreqd: FTBFs on ppc64el to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: The matplotlib problem was a temporary problem during the Python 3.7 -> 3.8 transiton

Processing commands for cont...@bugs.debian.org: > severity 955656 important Bug #955656 {Done: Andreas Tille } [src:python-cobra] python-cobra: FTBFS: E ModuleNotFoundError: No module named 'matplotlib' Severity set to 'important' from 'serious' > thanks Stopping processing here. Please conta

Bug#949222: Bug#959684: salt: CVE-2020-11651 and CVE-2020-11652

On Mon, 04 May 2020 at 01:34:33 +0200, Guilhem Moulin wrote: > CVE-2020-11651 > CVE-2020-11652 I found myself needing to mitigate this for a salt deployment, so I tried backporting the upstream patches to buster. The attached are not at all thoroughly-tested and should be reviewed carefully b

Bug#959801: ropemode: Consider removing it from Debian

Source: ropemode Severity: serious Version: 0.4-1 X-Debbugs-CC: python-modules-t...@lists.alioth.debian.org Package ropemode has been orphaned by its original maintainer and is python2- only. Perhaps it's time for us to have it removed from Debian. Package ropemode has no reverse dependencies or

Processed: Re: Bug#959783: util-linux: 2.35.1-1 FTBFS in pbuilder chroot: testsuite fails in misc/fallocate and misc/mountpoint

Processing control commands: > severity -1 important Bug #959783 [src:util-linux] util-linux: 2.35.1-1 FTBFS in pbuilder chroot: testsuite fails in misc/fallocate and misc/mountpoint Severity set to 'important' from 'serious' > tags -1 + upstream Bug #959783 [src:util-linux] util-linux: 2.35.1-1

Bug#959783: util-linux: 2.35.1-1 FTBFS in pbuilder chroot: testsuite fails in misc/fallocate and misc/mountpoint

Control: severity -1 important Control: tags -1 + upstream Hi Mark Hindley, thanks for your report. See below. * Mark Hindley [200505 13:27]: > Unfortunately the testsuite fails when building in a pbuilder/cowbuilder > chroot. In particular misc/fallocate and misc/mountpoint. > > The issues ap

Bug#938846: xia: Python2 removal in sid/bullseye

Hi, On 5/5/20 11:17 AM, Moritz Muehlenhoff wrote: See https://www.debian.org/doc/manuals/developers-reference/pkgs.html#removing-packages Thx for the link. I think the bug report has been sent. Bye. -- François Lafont

Bug#959587: python-biopython: FTBFS: AssertionError: False is not true

Hi Aaron, I've checked ncbi-blast+ and your last upload does not seem to be pushed. Since there is a strong relation in time with your upload and this FTBFS of biopython do you think that this could be connected: On Sun, May 03, 2020 at 02:43:59PM +0200, Lucas Nussbaum wrote: > > ===

Bug#959637: Please provide pristine-tar for libodsstream - or at least way to get upstream source (Was: Bug#959637: beads: FTBFS: build-dependency not installable: libodsstream-qt5-dev)

Hi Filippo, I tried to investigate this issue of beads: On Sun, May 03, 2020 at 02:34:20PM +0200, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. > ... > Relevant part (hopefully): > > The following packages have unmet dependencies: > > s

Bug#959590: marked as done (erlang-p1-tls: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile test returned exit code 2)

Your message dated Tue, 05 May 2020 11:48:25 + with message-id and subject line Bug#959590: fixed in erlang-p1-tls 1.1.5-2 has caused the Debian Bug report #959590, regarding erlang-p1-tls: FTBFS: dh_auto_test: error: make --no-print-directory -f /usr/share/dh-rebar/make/dh-rebar.Makefile tes

Bug#956675: cyvcf2: test failures on mipsel, ppc64el and s390x

Hi Adrian, On Tue, May 05, 2020 at 10:17:30AM +0300, Adrian Bunk wrote: > > Justification: fails to build from source (but built successfully in the > > past) > > > > cyvcf2 failed to build on mipsel (where it built before), > >... > > The mipsel failure is "FTBFS on Loongson", this needs black

Processed: found 956083 in 1.0-5

Processing commands for cont...@bugs.debian.org: > found 956083 1.0-5 Bug #956083 [autopostgresqlbackup] autopostgresqlbackup: Fails to detect when DB dumps fail, and saves useless backups Marked as found in versions autopostgresqlbackup/1.0-5. > thanks Stopping processing here. Please contact m

Processed: node-bash-match: Please remove dependency to node-cross-spawn

Processing control commands: > block 958403 by -1 Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does risky path mangling, and does it wrong in current release 5.1.0 958403 was blocked by: 959788 959786 959784 959789 959785 959787 958403 was not blocking any bugs. Added blo

Processed: node-bluebird: Please remove dependency to node-cross-spawn

Processing control commands: > block 958403 by -1 Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does risky path mangling, and does it wrong in current release 5.1.0 958403 was blocked by: 959785 959787 959784 959786 958403 was not blocking any bugs. Added blocking bug(s) o

Processed: npm: Please remove dependency to node-cross-spawn

Processing control commands: > block 958403 by -1 Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does risky path mangling, and does it wrong in current release 5.1.0 958403 was blocked by: 959784 959786 959787 959785 959788 958403 was not blocking any bugs. Added blocking b

Processed: node-fbjs: Please remove dependency to node-cross-spawn

Processing control commands: > block 958403 by -1 Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does risky path mangling, and does it wrong in current release 5.1.0 958403 was not blocked by any bugs. 958403 was not blocking any bugs. Added blocking bug(s) of 958403: 95978

Processed (with 1 error): Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 912504 src:pysycache Bug #912504 [pysycache] pysycache: Please migrate to python3-pygame Bug reassigned from package 'pysycache' to 'src:pysycache'. Ignoring request to alter found versions of bug #912504 to the same values previously se

Processed: node-foreground-child: Please remove dependency to node-cross-spawn

Processing control commands: > block 958403 by -1 Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does risky path mangling, and does it wrong in current release 5.1.0 958403 was blocked by: 959784 959786 959785 958403 was not blocking any bugs. Added blocking bug(s) of 95840

Processed: node-execa: Please remove dependency to node-cross-spawn

Processing control commands: > block 958403 by -1 Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does risky path mangling, and does it wrong in current release 5.1.0 958403 was blocked by: 959785 959784 958403 was not blocking any bugs. Added blocking bug(s) of 958403: 9597

Processed: node-node-sass: Please remove dependency to node-cross-spawn

Processing control commands: > block 958403 by -1 Bug #958403 [node-cross-spawn] node-cross-spawn: unneeded for Debian, does risky path mangling, and does it wrong in current release 5.1.0 958403 was blocked by: 959784 958403 was not blocking any bugs. Added blocking bug(s) of 958403: 959785 --

Bug#959783: util-linux: 2.35.1-1 FTBFS in pbuilder chroot: testsuite fails in misc/fallocate and misc/mountpoint

Source: util-linux Version: 2.35.1-1 Severity: serious Justification: FTBFS Tags: patch Dear Maintainer, Thanks for packaging the new version of util-linux. Unfortunately the testsuite fails when building in a pbuilder/cowbuilder chroot. In particular misc/fallocate and misc/mountpoint. The iss

Bug#959775: marked as done (pycsw: FTBFS with sphinx 2.4)

Your message dated Tue, 05 May 2020 10:33:43 + with message-id and subject line Bug#959775: fixed in pycsw 2.4.2+dfsg-3 has caused the Debian Bug report #959775, regarding pycsw: FTBFS with sphinx 2.4 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#958901: marked as done (qreator does not start properly)

Your message dated Tue, 05 May 2020 10:05:39 + with message-id and subject line Bug#958901: fixed in qreator 16.06.1-5 has caused the Debian Bug report #958901, regarding qreator does not start properly to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#955665: marked as done (ofxstatement-plugins: FTBFS: AssertionError: Failed doctest test for ofxstatement.plugins.tests.test_litas_esis.doctest_LitasEsisCsvStatementParser)

Your message dated Tue, 05 May 2020 10:05:19 + with message-id and subject line Bug#955665: fixed in ofxstatement-plugins 20200505 has caused the Debian Bug report #955665, regarding ofxstatement-plugins: FTBFS: AssertionError: Failed doctest test for

Processed: Re: Bug#959775: pycsw: FTBFS with sphinx 2.4

Processing control commands: > tags -1 upstream Bug #959775 [pycsw] pycsw: FTBFS with sphinx 2.4 Added tag(s) upstream. > forwarded -1 https://github.com/geopython/pycsw/issues/609 Bug #959775 [pycsw] pycsw: FTBFS with sphinx 2.4 Set Bug forwarded-to-address to 'https://github.com/geopython/pycsw/

Bug#959775: pycsw: FTBFS with sphinx 2.4

Control: tags -1 upstream Control: forwarded -1 https://github.com/geopython/pycsw/issues/609 Thanks for reporting this issue, I've forwarded it upstream. Perhaps the issue is easy to fix, if not the docs will be removed at least until this issue is fixed. Kind Regards, Bas -- GPG Key ID: 40

Bug#938846: xia: Python2 removal in sid/bullseye

On Tue, May 05, 2020 at 11:04:13AM +0200, François Lafont wrote: > Hi, > > On 5/4/20 10:54 PM, jmm@inutil.?Q?M=C3=BChlenhoff?= wrote: > > > Can you please file a removal bug (reportbug ftp.debian.org), then? It can > > still be reintroduced when ported to Python 3 at some point. > > Currently I

Bug#938846: xia: Python2 removal in sid/bullseye

Hi, On 5/4/20 10:54 PM, jmm@inutil.?Q?M=C3=BChlenhoff?= wrote: Can you please file a removal bug (reportbug ftp.debian.org), then? It can still be reintroduced when ported to Python 3 at some point. Currently I have no idea what is a "removal bug" but I'll search and proceed after work. Reg

Processed: Settings some additional flags to the closed bug...

Processing commands for cont...@bugs.debian.org: > tags 959540 wontfix Bug #959540 {Done: Ole Streicher } [src:scamp] scamp FTBFS on 32bit: test failures Added tag(s) wontfix. > severity 959540 normal Bug #959540 {Done: Ole Streicher } [src:scamp] scamp FTBFS on 32bit: test failures Severity set

Bug#959473: orthanc-dicomweb build-dependencies unsatisfiable on armel

Thanks for your in-depth analysis! As this problem is way too involved given my understanding of the Debian package management process, I have followed the simple path you provided by requesting the removal of the armel binaries of orthanc-dicomweb: https://bugs.debian.org/cgi-bin/bugreport.cgi?bu

Bug#959540: marked as done (scamp FTBFS on 32bit: test failures)

Your message dated Tue, 5 May 2020 10:38:13 +0200 with message-id and subject line Re: scamp FTBFS on 32bit: test failures has caused the Debian Bug report #959540, regarding scamp FTBFS on 32bit: test failures to be marked as done. This means that you claim that the problem has been dealt with.

Bug#959772: game-data-packager: FTBFS with inkscape 1.0

Control: tags -1 + pending On Tue, 05 May 2020 at 10:06:03 +0200, Andreas Beckmann wrote: > game-data-packager started to FTBFS with inkscape 1.0 I believe this is already fixed in git. smcv

Processed: Re: Bug#959772: game-data-packager: FTBFS with inkscape 1.0

Processing control commands: > tags -1 + pending Bug #959772 [src:game-data-packager] game-data-packager: FTBFS with inkscape 1.0 Added tag(s) pending. -- 959772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=959772 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#959772: game-data-packager: FTBFS with inkscape 1.0

Am 2020-05-05 10:06, schrieb Andreas Beckmann: Unknown option --export-png=out/wolf-common.png Unknown option --export-png=out/zork-inquisitor.png Unknown option --export-png=out/grimfandango.png Looks like this has been repleaced with the --export-type="png" option which doesn't take the file

Bug#959775: pycsw: FTBFS with sphinx 2.4

Package: pycsw Version: 2.4.2+dfsg-2 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, pycsw started to FTBFS when sphinx 2.4 reached sid: [...] PYTHONPATH=. http_proxy='127.0.0.1:9' sphinx-build -N -bhtml docs/ build/html # HTML generator Running Sphinx v2.4.3 making

Bug#959772: game-data-packager: FTBFS with inkscape 1.0

Source: game-data-packager Version: 64 Severity: serious Tags: ftbfs Justification: fails to build from source Hi, game-data-packager started to FTBFS with inkscape 1.0: [...] inkscape --export-png=out/wolf-common.png -w96 -h96 data/wolf-common.svg inkscape --export-png=out/grimfandango.png -w96

Processed: your mail

Processing commands for cont...@bugs.debian.org: > reassign 959364 acpi-call-dkms Bug #959364 [src:acpi-call] acpi-call-dkms: fails to build on kernel 5.6 Bug reassigned from package 'src:acpi-call' to 'acpi-call-dkms'. No longer marked as found in versions acpi-call/1.1.0-5. Ignoring request to a

Processed (with 1 error): your mail

Processing commands for cont...@bugs.debian.org: > severity 959729 serious Bug #959729 [acpi-call-dkms] Build error with kernel 5.6 Severity set to 'serious' from 'normal' > merge 959729 959364 Bug #959729 [acpi-call-dkms] Build error with kernel 5.6 Unable to merge bugs because: package of #95936

Bug#959364: PR with patch

I've cherry-picked the upstream fix as a patch in the gspr/bug-959364 branch of https://salsa.debian.org/gspr/acpi-call.git. It fixes the problem for me. A pull request for the maintainer follows. *** The following changes since commit 8474a4b865725bedc46a1be0b30dbc2a6b2df84c: Update changelo

Bug#959685: marked as done (security concerns for stable release)

Your message dated Tue, 5 May 2020 08:43:27 +0100 with message-id and subject line Re: Bug#959685: security concerns for stable release has caused the Debian Bug report #959685, regarding security concerns for stable release to be marked as done. This means that you claim that the problem has be

Processed: Problem is also in buster

Processing commands for cont...@bugs.debian.org: > tags 956020 buster Bug #956020 [mydumper] mydumper FTBFS on armel/armhf/mips/mipsel , needs to link against libm. Added tag(s) buster. > thanks Stopping processing here. Please contact me if you need assistance. -- 956020: https://bugs.debian.o

Bug#956675: cyvcf2: test failures on mipsel, ppc64el and s390x

On Tue, Apr 14, 2020 at 10:45:56AM +0200, Sebastian Ramacher wrote: > Source: cyvcf2 > Version: 0.11.6-2 > Severity: serious > Tags: ftbfs sid bullseye > Justification: fails to build from source (but built successfully in the past) > > cyvcf2 failed to build on mipsel (where it built before), >..

Processed: Merge with the root cause bug

Processing commands for cont...@bugs.debian.org: > reassign 954603 python3-humanfriendly Bug #954603 {Done: Andreas Tille } [src:cyvcf2] cyvcf2: FTBFS: dh_auto_test: error: pybuild --test --test-nose -i python{version} -p "3.7 3.8" returned exit code 13 Bug reassigned from package 'src:cyvcf2' t

Processed: closing 954607

Processing commands for cont...@bugs.debian.org: > close 954607 Bug #954607 [src:golang-github-twstrike-gotk3adapter] golang-github-twstrike-gotk3adapter: FTBFS: Errors while processing: libglib2.0-cil libgio-cil sbuild-build-depends-main-dummy golang-github-gotk3-gotk3-dev Marked Bug as done

Processed: bug 953289 is forwarded to gene...@discussion.soxr.p.re.sourceforge.net

Processing commands for cont...@bugs.debian.org: > forwarded 953289 gene...@discussion.soxr.p.re.sourceforge.net Bug #953289 [libsoxr0] ABI change in libsoxr 0.1.3 Set Bug forwarded-to-address to 'gene...@discussion.soxr.p.re.sourceforge.net'. > thanks Stopping processing here. Please contact me