Processed: reassign 953727 to xdebug

Processing commands for cont...@bugs.debian.org: > reassign 953727 xdebug 2.9.2+2.8.1+2.5.5-1 Bug #953727 [src:xdebug, src:php-codecoverage] xdebug breaks php-codecoverage autopkgtest: Class 'DOMDocument' not found Bug reassigned from package 'src:xdebug, src:php-codecoverage' to 'xdebug'. No lon

Processed: reassign 953727 to xdebug

Processing commands for cont...@bugs.debian.org: > # Problem with incomplete php7.4 installation on testing and part of unstable. > reassign 953727 xdebug 2.9.2+2.8.1+2.5.5-1 Bug #953727 [xdebug] xdebug breaks php-codecoverage autopkgtest: Class 'DOMDocument' not found Ignoring request to reassig

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tags 954673 + confirmed Bug #954673 [src:swi-prolog] swi-prolog: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) confirmed. > thanks Stopping processing here. Please contact me if you need assistance. -- 954

Bug#954826: libgcc-8-dev: depends on unavailable version of libgcc-s1

Package: libgcc-8-dev Version: 8.4.0-2 Severity: grave The latest version of gcc-8 is not installable because libgcc-8-dev depends on libgcc-s1 (>= 1:8.4.0-2), but the version of libgcc-s1 in the archive does not have an epoch and is therefore too low to fulfill this requirement. The same holds f

Bug#937404: marked as done (pycha: Python2 removal in sid/bullseye)

Your message dated Tue, 24 Mar 2020 03:53:13 + with message-id and subject line Bug#954752: Removed package(s) from unstable has caused the Debian Bug report #937404, regarding pycha: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dea

Bug#885468: marked as done (pycha: Depends on unmaintained pygtk)

Your message dated Tue, 24 Mar 2020 03:53:13 + with message-id and subject line Bug#954752: Removed package(s) from unstable has caused the Debian Bug report #885468, regarding pycha: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has been dealt

Bug#953777: Incorrect fix [Was: php-doctrine-cache_1.10.0-4_source.changes ACCEPTED into unstable]

Control: reopen -1 Control: reassign -1 php-apcu Control: found -1 5.1.18+4.0.11-1 Le 23/03/2020 à 09:13, Ondřej Surý a écrit : > I disagree that all of the added dependencies are wrong. […] > The autopkgtest needs to at least depend on php-cli. Yet, the autopkgtest does not call php-cli. Instea

Processed: Re: Incorrect fix [Was: php-doctrine-cache_1.10.0-4_source.changes ACCEPTED into unstable]

Processing control commands: > reopen -1 Bug #953777 {Done: =?utf-8?b?T25kxZllaiBTdXLDvQ==?= } [src:php-apcu, src:php-doctrine-cache] php-apcu breaks php-doctrine-cache autopkgtest: Class 'DOMDocument' not found 'reopen' may be inappropriate when a bug has been closed with a version; all fixed v

Bug#942565: marked as done (cross-toolchain-base-mipsen_8_all.changes REJECTED)

Your message dated Tue, 24 Mar 2020 01:49:27 + with message-id and subject line Bug#942565: fixed in cross-toolchain-base-mipsen 10 has caused the Debian Bug report #942565, regarding cross-toolchain-base-mipsen_8_all.changes REJECTED to be marked as done. This means that you claim that the p

Bug#936358: marked as done (cwiid: Python2 removal in sid/bullseye)

Your message dated Tue, 24 Mar 2020 00:49:22 + with message-id and subject line Bug#936358: fixed in cwiid 0.6.00+svn201-5 has caused the Debian Bug report #936358, regarding cwiid: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#942981: marked as done (cwiid: Python2 removal in sid/bullseye)

Your message dated Tue, 24 Mar 2020 00:49:22 + with message-id and subject line Bug#936358: fixed in cwiid 0.6.00+svn201-5 has caused the Debian Bug report #936358, regarding cwiid: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#951893: subversion FTBFS with swig 4.0.1

On Mon, Mar 23, 2020 at 12:50:42PM -0300, Lucas Kanashiro wrote: > diff -Nru subversion-1.13.0/debian/control > subversion-1.13.0.new/debian/control > --- subversion-1.13.0/debian/control 2020-01-19 10:59:14.0 -0300 > +++ subversion-1.13.0.new/debian/control 2020-03-23 11:39:46.47467

Bug#954698: marked as forwarded (serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>)

Your message dated Mon, 23 Mar 2020 20:08:00 -0400 with message-id <20200324000800.nznabbxy6jg67sxa@localhost> has caused the report #954698, regarding serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199> to be marked as havi

Bug#954698: serf: FTBFS: 1) test_ssltunnel_basic_auth_server_has_keepalive_off: test/test_context.c:2138: expected <0> but was <120199>

Looping in upstream: On Sun, Mar 22, 2020 at 02:57:54PM +0100, Lucas Nussbaum wrote: > Version: 1.3.9-8 This is the same version of the serf package that's been in Debian since 2019/12/31, so something else seems to have changed. > [...] > During a rebuild of all packages in sid, your package fa

Bug#954812: [Python-modules-team] Bug#954812: pythonmagick: autopkgtest regression: cannot import name '_PythonMagick'

The problem here is that py3versions -r falls back to supported versions when no X-Python3-Versions header field is present in debian/control and pythonmagic is only built for the current version: https://packages.debian.org/sid/amd64/python3-pythonmagick/filelist (shows only python3.8 objects)

Bug#954585: marked as done (should.js: FTBFS: dh_auto_test: error: cd ./should-equal && sh -e ../debian/nodejs/should-equal/test returned exit code 1)

Your message dated Mon, 23 Mar 2020 20:56:56 + with message-id and subject line Bug#954585: fixed in should.js 13.2.3~dfsg-3 has caused the Debian Bug report #954585, regarding should.js: FTBFS: dh_auto_test: error: cd ./should-equal && sh -e ../debian/nodejs/should-equal/test returned exit c

Processed: closing 916873

Processing commands for cont...@bugs.debian.org: > close 916873 Bug #916873 [python-twisted-core] python-twisted-core: Incorrect versioned dependency on python-attr Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 916873: https://bugs.debian.org

Processed: r-cran-rlang breaks r-cran-ggplot2 autopkgtest: `out` not identical to `exp`

Processing control commands: > found -1 r-cran-rlang/0.4.5-1 Bug #954813 [src:r-cran-rlang, src:r-cran-ggplot2] r-cran-rlang breaks r-cran-ggplot2 autopkgtest: `out` not identical to `exp` Marked as found in versions r-cran-rlang/0.4.5-1. > found -1 r-cran-ggplot2/3.2.1+dfsg-2 Bug #954813 [src:r-

Bug#954813: r-cran-rlang breaks r-cran-ggplot2 autopkgtest: `out` not identical to `exp`

Source: r-cran-rlang, r-cran-ggplot2 Control: found -1 r-cran-rlang/0.4.5-1 Control: found -1 r-cran-ggplot2/3.2.1+dfsg-2 Severity: serious Tags: sid bullseye X-Debbugs-CC: debian...@lists.debian.org User: debian...@lists.debian.org Usertags: breaks needs-update Dear maintainer(s), With a recent

Bug#954812: pythonmagick: autopkgtest regression: cannot import name '_PythonMagick'

Source: pythonmagick Version: 0.9.19-6 X-Debbugs-CC: debian...@lists.debian.org Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), With a recent upload of pythonmagick the autopkgtest of pythonmagick fails in testing when that autopkgtest is run with the b

Bug#953098: xscreensaver: Crashes with XIO: fatal IO error

Jens, can you please also attach an Xorg log from the crash? If I understand the original report right, the X session continued otherwise as normal, so I guess the X server didn't crash. It could have run out of memory temporarily, or xscreensaver requested something out of reach, like loads of mem

Bug#953777:

Hi Ondřej, Le 23/03/2020 à 00:53, Debian FTP Masters a écrit : […] > Source: php-doctrine-cache […] > Maintainer: Debian PHP PEAR Maintainers […] >* The autopkgtest dependencies were underspecified (Closes: #953777) I had a quick look at the fix. It’s useless: phpunit already depend on php-c

Bug#953777: Incorrect fix [Was: php-doctrine-cache_1.10.0-4_source.changes ACCEPTED into unstable]

David, I disagree that all of the added dependencies are wrong. I believe you should declare all the dependencies that the autopkgtest requires and that was not full filled. The autopkgtest needs to at least depend on php-cli. Also the dependencies are already tight, it’s just that phpX.Y-foo a

Bug#952022: ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:

Am Montag, den 23.03.2020, 19:28 +0100 schrieb Daniel Leidert: [..] > Thanks. This actually brought me on the right track. I just uploaded the > fixed package. The last three messages (#31, #36, #41) were reported against the wrong package. They are related to #952024 instead. Please ignore them.

Processed: Bug#954774 marked as pending in mozjs68

Processing control commands: > tag -1 pending Bug #954774 [src:mozjs68] mozjs68: FTBFS on armel: rust/cargo using armv7-unknown-linux-gnueabi, should be armv5te-unknown-linux-gnueabi Added tag(s) pending. -- 954774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954774 Debian Bug Tracking Sy

Bug#954774: marked as pending in mozjs68

Control: tag -1 pending Hello, Bug #954774 in mozjs68 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: https://salsa.debian.org/gnome-team/mozjs68/-/commit/4df50ce5722aa5ba650a7e61e87ac0

Bug#954805: src:xapers: Fails autopkgtest due to test assumptions about paths

Package: src:xapers Version: 0.8.2-1.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) The following autopkgtest log extracted from [1] should be enough to show the problem. It is currently showing up as a regression for python3.8 as de

Bug#952024: marked as done (ruby-rspec-puppet: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:)

Your message dated Mon, 23 Mar 2020 18:51:26 + with message-id and subject line Bug#952024: fixed in ruby-rspec-puppet 2.7.8-2 has caused the Debian Bug report #952024, regarding ruby-rspec-puppet: FTBFS: ERROR: Test "ruby2.7" failed: LoadError: to be marked as done. This means that you claim

Bug#952022: ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:

Am Montag, den 23.03.2020, 18:13 +0100 schrieb Stig Sandbeck Mathisen: > Daniel Leidert writes: > > > Package: src:ruby-puppet-syntax > > Followup-For: Bug #952022 > > > > The formentioned issue can probably be closed by applying this patch: > > > > --- a/lib/rspec-puppet/support.rb > > +++ b/l

Bug#952024: marked as pending in ruby-rspec-puppet

Control: tag -1 pending Hello, Bug #952024 in ruby-rspec-puppet 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: https://salsa.debian.org/ruby-team/ruby-rspec-puppet/-/commit/ff287944323

Processed: Bug#952024 marked as pending in ruby-rspec-puppet

Processing control commands: > tag -1 pending Bug #952024 [src:ruby-rspec-puppet] ruby-rspec-puppet: FTBFS: ERROR: Test "ruby2.7" failed: LoadError: Added tag(s) pending. -- 952024: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=952024 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#954276: marked as done (cloud-init - RuntimeError: dictionary keys changed during iteration)

Your message dated Mon, 23 Mar 2020 18:04:13 + with message-id and subject line Bug#954276: fixed in cloud-init 20.1-2 has caused the Debian Bug report #954276, regarding cloud-init - RuntimeError: dictionary keys changed during iteration to be marked as done. This means that you claim that t

Processed: [bts-link] source package s3cmd

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package s3cmd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # https://bts-link-team.pages.debian.net/bts-link/ > # > user debian-bts-l...@lists.debian.org Setting u

Processed: tagging 954762

Processing commands for cont...@bugs.debian.org: > tags 954762 - security Bug #954762 [systraq] systraq: Annoying as Hell Removed tag(s) security. > thanks Stopping processing here. Please contact me if you need assistance. -- 954762: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954762 Debi

Bug#944197: HELP needed for uploading a new upstream version of the Rheolef package

I think I sponsored this package some time ago and I will try to have a look again. Anton Am Mo., 23. März 2020 um 18:33 Uhr schrieb Pierre Saramito : > > Hi Andreas Tille, > > > From Andreas: > > Currently I can only support Covid-19 related > > packages (which we try to assemble in Debian Med t

Bug#944197: HELP needed for uploading a new upstream version of the Rheolef package

Hi Pierre, On Mon, Mar 23, 2020 at 04:24:13PM +, Pierre Saramito wrote: > > Let me known if I could help the Debian Med team ? > I remain "confined" at home, but I could help (test pkg, ect) ? We'll about to post an announcement for the upcomming virtual COVID-19 hackathon. I admit I could

Bug#952061: Info received (Bug#952061: ibsim: FTBFS: umad2sim.c:110:30: error: ‘UMAD_DEV_DIR’ undeclared here (not in a function))

Hi, I had little time to work on this, but as it happened, I submitted a pull request with deb packaging (internal) to the Github project and tested its building. It builds indeed fine with rdma-core, it seems. -- Tzafrir

Bug#952022: ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:

Daniel Leidert writes: > Package: src:ruby-puppet-syntax > Followup-For: Bug #952022 > > The formentioned issue can probably be closed by applying this patch: > > --- a/lib/rspec-puppet/support.rb > +++ b/lib/rspec-puppet/support.rb > @@ -440,7 +440,7 @@ > end > > def escape_special_c

Bug#954729: src:mesa: X won't start after upgrading mesa

On 23.3.2020 18.25, Chow Loong Jin wrote: > On Mon, Mar 23, 2020 at 01:21:23PM +0200, Timo Aaltonen wrote: >> On 22.3.2020 20.02, Timo Aaltonen wrote: >>> On 22.3.2020 17.38, Chow Loong Jin wrote: Package: src:mesa Version: 20.0.2-1 Severity: critical Justification: breaks the w

Bug#944197: HELP needed for uploading a new upstream version of the Rheolef package

Hi Andreas Tille, From Andreas: Currently I can only support Covid-19 related packages (which we try to assemble in Debian Med team currently) Let me known if I could help the Debian Med team ? I remain "confined" at home, but I could help (test pkg, ect) ? please find some other sponsor fr

Processed: block 949187 with 951944 954461 954462 954467 954468 954469 954470 954471 954473 954474 954476 954477 954478 954479 954480 954481 954482 954483

Processing commands for cont...@bugs.debian.org: > block 949187 with 951944 954461 954462 954467 954468 954469 954470 954471 > 954473 954474 954476 954477 954478 954479 954480 954481 954482 954483 Bug #949187 [release.debian.org] transition: python3.8 949187 was blocked by: 950858 950842 950847 9

Bug#951893: subversion FTBFS with swig 4.0.1

On Sat, 22 Feb 2020 22:04:09 -0500 James McCoy wrote: > > I might need to wait for the next upstream release. FWIW, we applied the attached patch in Ubuntu to make src:subversion build against swig 3.0 for now. If you could apply this patch it'd be great because at the moment we are trying to reb

Bug#954723: marked as done (golang-github-mendersoftware-scopestack: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/mendersoftware/scopestack returned exit

Your message dated Mon, 23 Mar 2020 15:50:00 + with message-id and subject line Bug#954723: fixed in golang-github-mendersoftware-scopestack 0.0~git20180403.c2f5599-4 has caused the Debian Bug report #954723, regarding golang-github-mendersoftware-scopestack: FTBFS: dh_auto_test: error: cd o

Bug#953062: Update

So, with 2020.03+dfsg1-1 uploaded (which contains the Build-Depends on libqt5opengl5-desktop-dev, as appears to be the intended behavior), I still see the following on https://tracker.debian.org/pkg/meshlab: Migration status for meshlab (- to 2020.03+dfsg1-1): BLOCKED: Rejected/violates migration

Bug#952025: ruby-grape: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: spec = parsers(**options)[api_format]

Package: src:ruby-grape Followup-For: Bug #952025 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 This issue has already been fixed upstream. The patch probably was: https://github.com/ruby-grape/grape/commit/84320ad4aa1083b6d2dd396d697d0426c560e2a5.patch Release version 1.3.0 has this fix inclu

Processed: tagging 952025

Processing commands for cont...@bugs.debian.org: > tags 952025 + fixed-upstream Bug #952025 [src:ruby-grape] ruby-grape: FTBFS: ERROR: Test "ruby2.7" failed: Failure/Error: spec = parsers(**options)[api_format] Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact m

Bug#954529: marked as done (libgit2: FTBFS: ./build-debian-release/CMakeFiles/CMakeTmp/./build-debian-release/CMakeFiles/CMakeTmp/src.c:11: undefined reference to `pthread_create')

Your message dated Mon, 23 Mar 2020 14:57:30 + with message-id and subject line Bug#954529: fixed in libgit2 0.28.4+dfsg.1-4 has caused the Debian Bug report #954529, regarding libgit2: FTBFS: ./build-debian-release/CMakeFiles/CMakeTmp/./build-debian-release/CMakeFiles/CMakeTmp/src.c:11: und

Bug#952022: ruby-puppet-syntax: FTBFS: ERROR: Test "ruby2.7" failed: LoadError:

Package: src:ruby-puppet-syntax Followup-For: Bug #952022 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 The formentioned issue can probably be closed by applying this patch: - --- a/lib/rspec-puppet/support.rb +++ b/lib/rspec-puppet/support.rb @@ -440,7 +440,7 @@ end def escape_spe

Bug#954557: [Pkg-javascript-devel] Bug#954557: node-run-sequence: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1

Le 22/03/2020 à 09:21, Lucas Nussbaum a écrit : > Source: node-run-sequence > Version: 2.2.1-1 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20200321 ftbfs-bullseye > > Hi, > > During a rebuild of all packages in sid, your package failed to build

Bug#954789: weechat FTBFS against ruby 2.7

Source: weechat Version: 2.7.1-1 Severity: serious User pkg-ruby-extras-maintain...@lists.alioth.debian.org Usertags: ruby2.7-transition Dear Maintainer, We are removing ruby 2.5 support and src:weechat FTBFS against ruby 2.7, check this build log: https://buildd.debian.org/status/fetch.php?pkg

Processed: found 954715 in glibc/2.29-1

Processing commands for cont...@bugs.debian.org: > found 954715 glibc/2.29-1 Bug #954715 [src:glibc] glibc: FTBFS: tests failed: signal/tst-minsigstksz-1 signal/tst-minsigstksz-2 Marked as found in versions glibc/2.29-1. > thanks Stopping processing here. Please contact me if you need assistance

Processed: fix ftbfs bug metadata

Processing commands for cont...@bugs.debian.org: > # reassign missed affects > affects 950675 + src:ccfits Bug #950675 [doxygen] doxygen-latex is now useless, should be removed from the archive? Added indication that 950675 affects src:ccfits > # reassign from binary package to source package > r

Bug#954787: uwsgi FTBFS against ruby 2.7

Source: uwsgi Version: 2.0.18-8 Severity: serious User pkg-ruby-extras-maintain...@lists.alioth.debian.org Usertags: ruby2.7-transition Dear Maintainer, We are removing ruby 2.5 support and src:uwsgi FTBFS against ruby 2.7, check this build log: https://buildd.debian.org/status/fetch.php?pkg=uw

Bug#953645: Please package latest upstream earlyoom version 1.5 or set EARLYOOM_ARGS="-r 3600"

Hi, *rfjakob * released new earlyoom version 1.5, where most important change for most users is in /etc/default/earlyoom : changed EARLYOOM_ARGS="-r 3600" instead of EARLYOOM_ARGS="-r 60" see https://github.com/rfjakob/earlyoom/issues/177 Please package latest upstream

Bug#954785: libprelude FTBFS against ruby 2.7

Source: libprelude Version: 5.1.1-4 Severity: serious User pkg-ruby-extras-maintain...@lists.alioth.debian.org Usertags: ruby2.7-transition Dear Maintainer, We are removing ruby 2.5 support and src:libprelude FTBFS against ruby 2.7, check this build log: https://buildd.debian.org/status/fetch.p

Bug#954242: qgis-providers: postinst failure: free(): invalid pointer

Control: severity -1 important On 3/23/20 2:22 PM, Piotr Engelking wrote: > The bug is also present with glibc 2.30-2, from testing/unstable, with > no special configuration. Not on my system. I have libc6 (2.30-2) since 2020-03-14 06:59:08. qgis-provides was upgrade from 3.10.3+dfsg-1 to 3.10.

Processed: Re: Bug#954242: qgis-providers: postinst failure: free(): invalid pointer

Processing control commands: > severity -1 important Bug #954242 [qgis-providers] qgis-providers: postinst failure: free(): invalid pointer Severity set to 'important' from 'serious' -- 954242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954242 Debian Bug Tracking System Contact ow...@bug

Bug#954100: marked as done (Error: A deprecated csdestruct_derived typemap was found for vtkGDCMTesting)

Your message dated Mon, 23 Mar 2020 14:28:19 +0100 with message-id <0f0575b7188fe6ac64115ec322c6e182290a7f1b.ca...@gmail.com> and subject line Error: A deprecated csdestruct_derived typemap was found for vtkGDCMTesting has caused the Debian Bug report #954100, regarding Error: A deprecated csdestr

Processed: qgis-providers: postinst failure: free(): invalid pointer

Processing commands for cont...@bugs.debian.org: > severity 954242 serious Bug #954242 [qgis-providers] qgis-providers: postinst failure: free(): invalid pointer Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 954242: ht

Bug#954682: marked as done (rainbow.js: FTBFS: AssertionError [ERR_ASSERTION]: Task function must be specified)

Your message dated Mon, 23 Mar 2020 13:21:03 + with message-id and subject line Bug#954682: fixed in rainbow.js 2.1.4+ds-3 has caused the Debian Bug report #954682, regarding rainbow.js: FTBFS: AssertionError [ERR_ASSERTION]: Task function must be specified to be marked as done. This means t

Bug#954646: marked as done (node-fbjs: FTBFS: ln: failed to create symbolic link 'packages/fbjs/node_modules/4': File exists)

Your message dated Mon, 23 Mar 2020 13:20:08 + with message-id and subject line Bug#954646: fixed in node-fbjs 1.0.0-3 has caused the Debian Bug report #954646, regarding node-fbjs: FTBFS: ln: failed to create symbolic link 'packages/fbjs/node_modules/4': File exists to be marked as done. Th

Bug#954596: marked as done (node-bluebird: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1)

Your message dated Mon, 23 Mar 2020 12:55:56 + with message-id and subject line Bug#954596: fixed in node-bluebird 3.5.3+dfsg1-2 has caused the Debian Bug report #954596, regarding node-bluebird: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1 to be marked

Processed: Bug#954682 marked as pending in rainbow.js

Processing control commands: > tag -1 pending Bug #954682 [src:rainbow.js] rainbow.js: FTBFS: AssertionError [ERR_ASSERTION]: Task function must be specified Added tag(s) pending. -- 954682: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954682 Debian Bug Tracking System Contact ow...@bugs.d

Bug#954682: marked as pending in rainbow.js

Control: tag -1 pending Hello, Bug #954682 in rainbow.js 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: https://salsa.debian.org/js-team/rainbow.js/-/commit/52507ff23318142d05a87239bfd

Bug#954703: marked as done (libvirt-python: FTBFS: Missing type converters: virTypedParameterPtr *:1 virTypedParameterPtr:1)

Your message dated Mon, 23 Mar 2020 12:19:23 + with message-id and subject line Bug#954703: fixed in libvirt-python 6.1.0-1 has caused the Debian Bug report #954703, regarding libvirt-python: FTBFS: Missing type converters: virTypedParameterPtr *:1 virTypedParameterPtr:1 to be marked as done.

Processed: severity of 954334 is serious

Processing commands for cont...@bugs.debian.org: > severity 954334 serious Bug #954334 {Done: Laurent Bigonville } [gnome-music] gnome-music: Gnome music crashes at launch Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 954

Processed: closing 953719

Processing commands for cont...@bugs.debian.org: > close 953719 Bug #953719 [src:libhandy] src:libhandy: fails to migrate to testing for too long Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 953719: https://bugs.debian.org/cgi-bin/bugreport.

Processed: Bug#954596 marked as pending in node-bluebird

Processing control commands: > tag -1 pending Bug #954596 [src:node-bluebird] node-bluebird: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 954596: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954596 Debian Bug Tracking System

Bug#954596: marked as pending in node-bluebird

Control: tag -1 pending Hello, Bug #954596 in node-bluebird 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: https://salsa.debian.org/js-team/node-bluebird/-/commit/387cf66ae1e1cd1590d2e

Bug#952192: marked as done (golang-github-go-xorm-core: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/go-xorm/core returned exit code 1)

Your message dated Mon, 23 Mar 2020 12:04:10 + with message-id and subject line Bug#952192: fixed in golang-github-go-xorm-core 0.6.2-3 has caused the Debian Bug report #952192, regarding golang-github-go-xorm-core: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p

Bug#954705: marked as done (libjs-jsencrypt: FTBFS: AssertionError [ERR_ASSERTION]: Task function must be specified)

Your message dated Mon, 23 Mar 2020 12:04:16 + with message-id and subject line Bug#954705: fixed in libjs-jsencrypt 2.3.0+dfsg2-2 has caused the Debian Bug report #954705, regarding libjs-jsencrypt: FTBFS: AssertionError [ERR_ASSERTION]: Task function must be specified to be marked as done.

Bug#953698: marked as done (src:python-setoptconf: fails to migrate to testing for too long)

Your message dated Mon, 23 Mar 2020 13:03:45 +0100 with message-id <66393f95-ee42-f13b-1728-ab83ac901...@yahoo.no> and subject line close bug has caused the Debian Bug report #953698, regarding src:python-setoptconf: fails to migrate to testing for too long to be marked as done. This means that yo

Processed: closing 952132

Processing commands for cont...@bugs.debian.org: > close 952132 0.68.2+ds-1 Bug #952132 [rollup] vue-router.js: FTBFS: build-dependency not installable: rollup Marked as fixed in versions node-rollup/0.68.2+ds-1. Bug #952132 [rollup] vue-router.js: FTBFS: build-dependency not installable: rollup

Processed: affects 952132

Processing commands for cont...@bugs.debian.org: > affects 952132 src:vue-router.js Bug #952132 {Done: Adrian Bunk } [rollup] vue-router.js: FTBFS: build-dependency not installable: rollup Added indication that 952132 affects src:vue-router.js > thanks Stopping processing here. Please contact me

Processed: Bug#952192 marked as pending in golang-github-go-xorm-core

Processing control commands: > tag -1 pending Bug #952192 [src:golang-github-go-xorm-core] golang-github-go-xorm-core: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 4 github.com/go-xorm/core returned exit code 1 Added tag(s) pending. -- 952192: https://bugs.debi

Bug#952192: marked as pending in golang-github-go-xorm-core

Control: tag -1 pending Hello, Bug #952192 in golang-github-go-xorm-core 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: https://salsa.debian.org/go-team/packages/golang-github-go-xorm-

Processed: block 952210 with 953645

Processing commands for cont...@bugs.debian.org: > block 952210 with 953645 Bug #952210 {Done: Yangfl } [src:earlyoom] earlyoom: FTBFS: dh_auto_test: error: make -j4 test returned exit code 2 952210 was not blocked by any bugs. 952210 was not blocking any bugs. Added blocking bug(s) of 952210: 95

Processed: Move to the correct packages and merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 952129 node-boom Bug #952129 [src:node-cryptiles] node-cryptiles: FTBFS: unsatisfiable build-dependency: node-hapi-boom (>= 7.0.0) (versioned dep on a virtual pkg?) Bug reassigned from package 'src:node-cryptiles' to 'node-boom'. No long

Bug#954688: marked as done (with-simulated-input-el: FTBFS: Spies can only be created in ‘before-each’)

Your message dated Mon, 23 Mar 2020 11:36:27 + with message-id and subject line Bug#954688: fixed in with-simulated-input-el 2.4+git20200216.29173588-1 has caused the Debian Bug report #954688, regarding with-simulated-input-el: FTBFS: Spies can only be created in ‘before-each’ to be marked

Bug#954729: src:mesa: X won't start after upgrading mesa

On 22.3.2020 20.02, Timo Aaltonen wrote: > On 22.3.2020 17.38, Chow Loong Jin wrote: >> Package: src:mesa >> Version: 20.0.2-1 >> Severity: critical >> Justification: breaks the whole system >> >> Dear Maintainer, >> >>> * What led up to the situation? >> >> Upgraded mesa packages from 19.3.3-1 to

Bug#954776: jsxgraph fails to install

Package: jsxgraph Version: 1.3.5+dfsg1-4 Severity: serious Control: block 952307 by -1 https://piuparts.debian.org/sid/fail/jsxgraph_1.3.5+dfsg1-4.log ... Setting up python3 (3.8.2-1) ... /usr/lib/python3.8/subprocess.py:838: RuntimeWarning: line buffering (buffering=1) isn't supported in bin

Processed: jsxgraph fails to install

Processing control commands: > block 952307 by -1 Bug #952307 {Done: Georges Khaznadar } [src:jsxgraph] jsxgraph: FTBFS: Error: Error: ERROR: module path does not exist: /<>/src/../node_modules/almond/almond.js for module named: ../node_modules/almond/almond. Path is relative to: /<> 952307 was

Processed: tagging 952299

Processing commands for cont...@bugs.debian.org: > tags 952299 + patch Bug #952299 [src:golang-go-dbus] golang-go-dbus: FTBFS: failed to initialize build cache at /sbuild-nonexistent/.cache/go-build: mkdir /sbuild-nonexistent: permission denied Added tag(s) patch. > thanks Stopping processing he

Processed: Bug#954659 marked as pending in gjs

Processing control commands: > tag -1 pending Bug #954659 [src:gjs] FTBFS: gjs:JS / Gio unit test crashes after 5th TAP test Added tag(s) pending. -- 954659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954659 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#954659: marked as pending in gjs

Control: tag -1 pending Hello, Bug #954659 in gjs 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: https://salsa.debian.org/gnome-team/gjs/-/commit/04b932b97d4e7cdfd79a18bcd97bfb2fc0b1e2

Processed: tagging 952261

Processing commands for cont...@bugs.debian.org: > tags 952261 + fixed Bug #952261 {Done: =?utf-8?q?Jelmer_Vernoo=C4=B3?= } [src:isso] isso: FTBFS: /bin/sh: 1: git: not found Added tag(s) fixed. > thanks Stopping processing here. Please contact me if you need assistance. -- 952261: https://bugs

Processed: tagging 952256

Processing commands for cont...@bugs.debian.org: > tags 952256 + upstream Bug #952256 [src:cbmc] cbmc: FTBFS: cp: cannot stat '../../../lib/java-models-library/target/core-models.jar': No such file or directory Added tag(s) upstream. > thanks Stopping processing here. Please contact me if you n

Bug#953777: marked as done (php-apcu breaks php-doctrine-cache autopkgtest: Class 'DOMDocument' not found)

Your message dated Mon, 23 Mar 2020 10:53:07 + with message-id and subject line Bug#953777: fixed in php-doctrine-cache 1.10.0-4 has caused the Debian Bug report #953777, regarding php-apcu breaks php-doctrine-cache autopkgtest: Class 'DOMDocument' not found to be marked as done. This means

Bug#954774: mozjs68: FTBFS on armel: rust/cargo using armv7-unknown-linux-gnueabi, should be armv5te-unknown-linux-gnueabi

Source: mozjs68 Version: 68.5.0-2 Severity: serious Tags: ftbfs Justification: will break gjs and gnome-shell which previously worked X-Debbugs-Cc: debian-gtk-gn...@lists.debian.org Control: block 954422 by -1 mozjs68 FTBFS on armel: > checking for cargo... /usr/bin/cargo > checking rustc version.

Processed: mozjs68: FTBFS on armel: rust/cargo using armv7-unknown-linux-gnueabi, should be armv5te-unknown-linux-gnueabi

Processing control commands: > block 954422 by -1 Bug #954422 [release.debian.org] transition: GNOME 3.36 954422 was blocked by: 954659 954422 was not blocking any bugs. Added blocking bug(s) of 954422: 954774 -- 954422: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954422 954774: https://bu

Processed: bug 952227 is forwarded to https://github.com/go-gcfg/gcfg/issues/17

Processing commands for cont...@bugs.debian.org: > forwarded 952227 https://github.com/go-gcfg/gcfg/issues/17 Bug #952227 [src:golang-gopkg-gcfg.v1] golang-gopkg-gcfg.v1: FTBFS: dh_auto_test: error: cd _build && go test -vet=off -v -p 4 gopkg.in/gcfg.v1 gopkg.in/gcfg.v1/scanner gopkg.in/gcfg.v1/

Processed: tagging 952200

Processing commands for cont...@bugs.debian.org: > tags 952200 + fixed-upstream Bug #952200 [src:libvirt-dbus] libvirt-dbus: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need ass

Processed: tagging 952222

Processing commands for cont...@bugs.debian.org: > tags 95 + fixed Bug #95 {Done: Janos Lenart } [src:google-authenticator] google-authenticator: FTBFS: dh_auto_test: error: cd libpam && make -j4 test VERBOSE=1 returned exit code 2 Added tag(s) fixed. > thanks Stopping processing here.

Processed: tagging 952151

Processing commands for cont...@bugs.debian.org: > tags 952151 + fixed Bug #952151 {Done: Xavier Guimard } [src:node-boom] node-boom: FTBFS: unsatisfiable build-dependency: node-hapi-hoek (>= 8.0.0) (versioned dep on a virtual pkg?) Added tag(s) fixed. > thanks Stopping processing here. Please

Processed: block 952163 with 954740

Processing commands for cont...@bugs.debian.org: > block 952163 with 954740 Bug #952163 [src:keras] keras: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.8 3.7" returned exit code 13 952163 was not blocked by any bugs. 952163 was not blocking any bugs. Added blo

Processed: tagging 952190

Processing commands for cont...@bugs.debian.org: > tags 952190 + upstream Bug #952190 [src:gemma] gemma: FTBFS: dh_auto_test: error: make -j1 check returned exit code 2 Ignoring request to alter tags of bug #952190 to the same tags previously set > thanks Stopping processing here. Please contact

Processed: closing 952608

Processing commands for cont...@bugs.debian.org: > close 952608 Bug #952608 [src:php-defaults] src:php-defaults: Block transition until PECL extensions are rebuilt Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 952608: https://bugs.debian.org/

Processed: Re: azure-cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.7 3.8" returned exit code 13

Processing control commands: > retitle -1 python3-humanfriendly: humanfriendly.terminal module missing from > package Bug #954640 [src:azure-cli] azure-cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.7 3.8" returned exit code 13 Changed Bug title to 'python

Bug#954640: azure-cli: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.7 3.8" returned exit code 13

Control: retitle -1 python3-humanfriendly: humanfriendly.terminal module missing from package Control: reassign -1 python3-humanfriendly 8.1-1 On Sun, 22 Mar 2020 09:14:33 +0100 Lucas Nussbaum wrote: > Source: azure-cli > Version: 2.0.81+ds-3 > Severity: serious > Justification: FTBFS on amd64 >

Processed: fixed 954685 in 4.4.0-1

Processing commands for cont...@bugs.debian.org: > fixed 954685 4.4.0-1 Bug #954685 [src:node-rollup-plugin-babel] node-rollup-plugin-babel: FTBFS: dh_auto_test: error: /bin/sh -e debian/tests/pkg-js/test returned exit code 1 Marked as fixed in versions node-rollup-plugin-babel/4.4.0-1. > thanks

  1   2   >