Bug#978310: umockdev: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1

2020-12-26 Thread Martin Pitt
Control: tag -1 fixed-upstream pending Control: forwarded -1 https://github.com/martinpitt/umockdev/issues/115 Hello Lucas, Lucas Nussbaum [2020-12-26 22:57 +0100]: > > Bail out! ERROR:../tests/test-umockdev.c:1135:t_testbed_usb_lsusb: > > assertion failed (exit_status == 0): (256 == 0) I

Bug#978317: marked as done (node-json-stringify-safe: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 18)

2020-12-26 Thread Debian Bug Tracking System
 --- Source: node-json-stringify-safe Version: 5.0.1+repack-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > d

Processed: Re: Bug#978310: umockdev: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 fixed-upstream pending Bug #978310 [src:umockdev] umockdev: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=4 ninja test returned exit code 1 Added tag(s) pending and fixed-upstream. > forwarded -1

Bug#978171: aptitude: FTBFS: pkgcachegen.h:32:10: fatal error: xxhash.h: No such file or directory

2020-12-26 Thread Sven Joachim
On 2020-12-26 23:15 +0100, Axel Beckert wrote: > Sven Joachim wrote: >> > Looks like a missing dependency on libxxhash-dev on a first glance. >> > >> > Will check if that helps. (And I wonder where that one got lost.) >> >> It did not get lost, rather I suppose that the latest apt upload >>

Processed: tagging 978171

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 978171 - confirmed Bug #978171 [libapt-pkg-dev] aptitude: FTBFS: pkgcachegen.h:32:10: fatal error: xxhash.h: No such file or directory Bug #978187 [libapt-pkg-dev] python-apt: FTBFS: pkgcachegen.h:32:10: fatal error: xxhash.h: No such file

Bug#978317: marked as pending in node-json-stringify-safe

2020-12-26 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #978317 in node-json-stringify-safe 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#978317 marked as pending in node-json-stringify-safe

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978317 [src:node-json-stringify-safe] node-json-stringify-safe: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 18 Added tag(s) pending. -- 978317: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978317

Processed: tagging xxhash.h bugs

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 978171 - moreinfo Bug #978171 [src:aptitude] aptitude: FTBFS: pkgcachegen.h:32:10: fatal error: xxhash.h: No such file or directory Removed tag(s) moreinfo. > reassign 978171 libapt-pkg-dev Bug #978171 [src:aptitude] aptitude: FTBFS:

Bug#978022: libopenmpi3 Runtime failure opal_pmix_base_select failed

2020-12-26 Thread Lucas Nussbaum
Hi, On 24/12/20 at 17:16 +0100, Michael Banck wrote: > Package: libopenmpi3 > Version: 3.1.3-11 > Severity: serious > > Even with the fixed libpmix2_4.0.0~rc1-2, I am getting runtime failures > trying to run MPI programs, e.g. the nwchem autopkgtests all fail like > this: A simple way to

Bug#978299: marked as done (node-lie: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 2)

2020-12-26 Thread Debian Bug Tracking System
+dfsg-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > C

Bug#978299: marked as pending in node-lie

2020-12-26 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #978299 in node-lie 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#978299 marked as pending in node-lie

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978299 [src:node-lie] node-lie: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 2 Added tag(s) pending. -- 978299: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978299 Debian Bug Tracking System Contact

Bug#978313: marked as done (node-postgres: FTBFS: dh_auto_test: error: cd ./buffer-writer && sh -ex ../debian/nodejs/buffer-writer/test returned exit code 1)

2020-12-26 Thread Debian Bug Tracking System
 Message --- Source: node-postgres Version: 7.14.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-b

Processed: Bug#978313 marked as pending in node-postgres

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978313 [src:node-postgres] node-postgres: FTBFS: dh_auto_test: error: cd ./buffer-writer && sh -ex ../debian/nodejs/buffer-writer/test returned exit code 1 Added tag(s) pending. -- 978313:

Bug#978313: marked as pending in node-postgres

2020-12-26 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #978313 in node-postgres 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#978321: marked as done (node-vinyl: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

2020-12-26 Thread Debian Bug Tracking System
: 2.2.1-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > dpkg-buildpackage > - > > C

Bug#978373: marked as done (node-deep-eql: FTBFS: Error: module type-detect in /<> not found)

2020-12-26 Thread Debian Bug Tracking System
erious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > dh_auto_build > browserify-lite ./

Bug#978321: marked as pending in node-vinyl

2020-12-26 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #978321 in node-vinyl 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#978321 marked as pending in node-vinyl

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

Bug#978333: marked as done (node-filesize: FTBFS: Error: Cannot find module '@babel/core')

2020-12-26 Thread Debian Bug Tracking System
Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > grunt babel uglify > Loading &

Bug#978373: marked as pending in node-deep-eql

2020-12-26 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #978373 in node-deep-eql 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#978373 marked as pending in node-deep-eql

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978373 [src:node-deep-eql] node-deep-eql: FTBFS: Error: module type-detect in /<> not found Added tag(s) pending. -- 978373: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978373 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Bug#978333: marked as pending in node-filesize

2020-12-26 Thread Xavier Guimard
Control: tag -1 pending Hello, Bug #978333 in node-filesize 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#978333 marked as pending in node-filesize

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978333 [src:node-filesize] node-filesize: FTBFS: Error: Cannot find module '@babel/core' Added tag(s) pending. -- 978333: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978333 Debian Bug Tracking System Contact ow...@bugs.debian.org with

Processed: src:chasquid: fails to migrate to testing for too long: Build-Depends on non-migrating package

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.5-1 Bug #978413 [src:chasquid] src:chasquid: fails to migrate to testing for too long: Build-Depends on non-migrating package Marked as fixed in versions chasquid/1.5-1. Bug #978413 [src:chasquid] src:chasquid: fails to migrate to testing for too long:

Bug#978413: src:chasquid: fails to migrate to testing for too long: Build-Depends on non-migrating package

2020-12-26 Thread Paul Gevers
Source: chasquid Version: 1.3-1 Severity: serious Control: close -1 1.5-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 961814 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync

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

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.4.7-1 Bug #978412 [src:picolibc] src:picolibc: fails to migrate to testing for too long: maintainer built arch:all binaries Marked as fixed in versions picolibc/1.4.7-1. Bug #978412 [src:picolibc] src:picolibc: fails to migrate to testing for too long:

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

2020-12-26 Thread Paul Gevers
Source: picolibc Version: 1.4.6-1 Severity: serious Control: close -1 1.4.7-1 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are out-of-sync between testing

Bug#973747: marked as pending in python-firehose

2020-12-26 Thread Nilesh Patra
Control: tag -1 pending Hello, Bug #973747 in python-firehose 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#973747 marked as pending in python-firehose

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #973747 [src:python-firehose] python-firehose: FTBFS with python 3.9: AttributeError: module 'plistlib' has no attribute 'readPlist' Added tag(s) pending. -- 973747: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973747 Debian Bug Tracking

Processed: src:golang-gopkg-lxc-go-lxc.v2: fails to migrate to testing for too long: maintainer built arch:all binary

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.0+git20201012.d1943fb-1 Bug #978411 [src:golang-gopkg-lxc-go-lxc.v2] src:golang-gopkg-lxc-go-lxc.v2: fails to migrate to testing for too long: maintainer built arch:all binary Marked as fixed in versions

Bug#978411: src:golang-gopkg-lxc-go-lxc.v2: fails to migrate to testing for too long: maintainer built arch:all binary

2020-12-26 Thread Paul Gevers
Source: golang-gopkg-lxc-go-lxc.v2 Version: 0.0+git20190625.f4822c6-1 Severity: serious Control: close -1 0.0+git20201012.d1943fb-1 Tags: sid bullseye pending User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), As recently announced [1], the Release Team now

Processed: src:pipemeter: fails to migrate to testing for too long: FTBFS everywhere

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.1.4-1 Bug #978410 [src:pipemeter] src:pipemeter: fails to migrate to testing for too long: FTBFS everywhere The source 'pipemeter' and version '1.1.4-1' do not appear to match any binary packages Marked as fixed in versions pipemeter/1.1.4-1. Bug

Bug#978410: src:pipemeter: fails to migrate to testing for too long: FTBFS everywhere

2020-12-26 Thread Paul Gevers
Source: pipemeter Version: 1.1.3-1 Severity: serious Control: close -1 1.1.4-1 Tags: sid bullseye User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 972958 Dear maintainer(s), As recently announced [1], the Release Team now considers packages that are

Bug#976913: golang-github-henrydcase-nobs: FTBFS on ppc64el (arch:all-only src pkg): dh_auto_build: error: cd obj-powerpc64le-linux-gnu && go install -trimpath -v -p 160

2020-12-26 Thread Roger Shimizu
forwarded -1 https://github.com/henrydcase/nobs/issues/37 from upstream: > only x86-64 and aarch64 is currently supported. why would you need i386 > exactly? So currently maybe we can only build for amd64 and arm64. Cheers, -- Roger Shimizu, GMT +9 Tokyo PGP/GPG: 4096R/6C6ACD6417B3ACB1

Processed: Re: Bug#978236: otb: FTBFS: unsatisfiable build-dependency: libnifti-dev (versioned dep on a virtual pkg?)

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 978236 src:insighttoolkit4 Bug #978236 [src:otb] otb: FTBFS: unsatisfiable build-dependency: libnifti-dev (versioned dep on a virtual pkg?) Bug reassigned from package 'src:otb' to 'src:insighttoolkit4'. No longer marked as found in

Bug#978236: otb: FTBFS: unsatisfiable build-dependency: libnifti-dev (versioned dep on a virtual pkg?)

2020-12-26 Thread Sebastiaan Couwenberg
reassign 978236 src:insighttoolkit4 found 978236 insighttoolkit4/4.13.3withdata-dfsg1-3 affects 978236 src:otb thanks On 12/26/20 10:40 PM, Lucas Nussbaum wrote: >> The following packages have unmet dependencies: >> libinsighttoolkit4-dev : Depends: libnifti-dev This is not an issue in otb, but

Bug#958117: uglifyjs: dead code: keep away from bullseye

2020-12-26 Thread Jonas Smedegaard
Quoting Jonas Smedegaard (2020-04-18 19:02:15) > UglifyJS 2 is dead upstream (no code commit since June 2017). > > These packages will *not* be part of Bullseye: > > src:uglifyjs > libjs-uglify > node-uglify > > Projects now using UglifyJS 2 can either upgrade to UglifyJS 3 or > migrate to

Bug#977649: marked as done (bumped SONAME without name change)

2020-12-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 04:03:28 + with message-id and subject line Bug#977649: fixed in kimageannotator 0.4.0-2 has caused the Debian Bug report #977649, regarding bumped SONAME without name change to be marked as done. This means that you claim that the problem has been dealt

Bug#977988: marked as done (/usr/bin/spectacle: does not start (libkImageAnnotator.so.0.3.2 not found))

2020-12-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 04:03:28 + with message-id and subject line Bug#977649: fixed in kimageannotator 0.4.0-2 has caused the Debian Bug report #977649, regarding /usr/bin/spectacle: does not start (libkImageAnnotator.so.0.3.2 not found) to be marked as done. This means that

Bug#977900: node-autoprefixer: FTBFS: ENOENT: no such file or directory, open 'path'

2020-12-26 Thread Akshay S Dinesh
A few observations. 1) The commit https://github.com/rollup/plugins/commit/1459cf0ab5e5eb7beee46f52bc4dbbb88d3e4335#diff-c68d63c5e10e04a850c0ea8abd479dbb77c794b3aadecf91483dcf3df96156df which prevents exceptions from being silently ignored maybe the reason why this is starting to err. 2)

Processed: tagging 976539

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 976539 + fixed-upstream Bug #976539 [src:elinks] elinks: FTBFS: ! Undefined control sequence. Added tag(s) fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 976539:

Bug#978355: marked as done (tuxfootball: FTBFS: error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.19 but the autoconf macros are from gettext version 0.20)

2020-12-26 Thread Debian Bug Tracking System
with problems --- Begin Message --- Source: tuxfootball Version: 0.3.1-6 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#977988: /usr/bin/spectacle: does not start (libkImageAnnotator.so.0.3.2 not found)

2020-12-26 Thread Boyuan Yang
X-Debbugs-CC: p...@debian.org On Wed, 23 Dec 2020 23:51:57 +0100 Pino Toscano wrote: > reassign 977988 src:kimageannotator > forcemerge 977649 977988 > thanks > > In data mercoledì 23 dicembre 2020 22:26:13 CET, Dominik George ha scritto: > > Package: kde-spectacle > > Version: 20.12.0-1 > >

Processed: Bug#978355 marked as pending in tuxfootball

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978355 [src:tuxfootball] tuxfootball: FTBFS: error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.19 but the autoconf macros are from gettext version 0.20 Added tag(s) pending. -- 978355:

Bug#978355: marked as pending in tuxfootball

2020-12-26 Thread TANIGUCHI Takaki
Control: tag -1 pending Hello, Bug #978355 in tuxfootball 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#978401: ibus-libpinyin: FTBFS on armel, armhf and mipsel: lua test failure

2020-12-26 Thread Boyuan Yang
Control: severity -1 important 在 2020-12-26星期六的 18:48 -0500,Boyuan Yang写道: > Source: ibus-libpinyin > Version: 1.12.0-2 > Severity: serious > Tags: ftbfs sid > > As shown on > https://buildd.debian.org/status/package.php?p=ibus-libpinyin , > currently ibus-libpinyin FTBFS on armel armhf and

Processed: Re: Bug#978401: ibus-libpinyin: FTBFS on armel, armhf and mipsel: lua test failure

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > severity -1 important Bug #978401 [src:ibus-libpinyin] ibus-libpinyin: FTBFS on armel, armhf and mipsel: lua test failure Severity set to 'important' from 'serious' -- 978401: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978401 Debian Bug Tracking System

Processed: bug 976539 is forwarded to https://github.com/rkd77/elinks/issues/82

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 976539 https://github.com/rkd77/elinks/issues/82 Bug #976539 [src:elinks] elinks: FTBFS: ! Undefined control sequence. Set Bug forwarded-to-address to 'https://github.com/rkd77/elinks/issues/82'. > thanks Stopping processing here.

Bug#975574: marked as done (libgs9: possible ABI breakage with testing/bullseyes version (9.52.1~dfsg-1))

2020-12-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 03:53:01 +0100 with message-id <160903758190.2559074.10114454951831344...@auryn.jones.dk> and subject line Re: Bug#977754: evince does not display EPS or PS files anymore and shows "Loading..." forever has caused the Debian Bug report #977754, regarding libgs9:

Bug#975387: marked as done (wrong size check for display_callback_v2_s struct)

2020-12-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 03:53:01 +0100 with message-id <160903758190.2559074.10114454951831344...@auryn.jones.dk> and subject line Re: Bug#977754: evince does not display EPS or PS files anymore and shows "Loading..." forever has caused the Debian Bug report #977754, regarding wrong

Bug#977754: marked as done (wrong size check for display_callback_v2_s struct)

2020-12-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 03:53:01 +0100 with message-id <160903758190.2559074.10114454951831344...@auryn.jones.dk> and subject line Re: Bug#977754: evince does not display EPS or PS files anymore and shows "Loading..." forever has caused the Debian Bug report #977754, regarding wrong

Bug#978362: marked as done (node-eslint-plugin-node: FTBFS: tests failed)

2020-12-26 Thread Debian Bug Tracking System
: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > NODE_PATH=debian/node_modules eslint

Bug#972806: marked as done (mbedtls security advisories: local side channel attacks)

2020-12-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 02:49:04 + with message-id and subject line Bug#972806: fixed in mbedtls 2.16.9-0.1 has caused the Debian Bug report #972806, regarding mbedtls security advisories: local side channel attacks to be marked as done. This means that you claim that the problem

Bug#978163: go-dep: Not release with bullseye

2020-12-26 Thread Hilko Bengen
* Shengjing Zhu: > dep is deprecated by upstream. The upstream repo is now read-only. > Users should have migrated to Go modules. I agree. Not because I think that the Go Modules concept is generally more sensible, but because it has caused the go-dep project to stop. > I was thinking just to

Processed: Bug#978362 marked as pending in node-eslint-plugin-node

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978362 [src:node-eslint-plugin-node] node-eslint-plugin-node: FTBFS: tests failed Added tag(s) pending. -- 978362: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978362 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#978362: marked as pending in node-eslint-plugin-node

2020-12-26 Thread Jonas Smedegaard
Control: tag -1 pending Hello, Bug #978362 in node-eslint-plugin-node 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#978189: marked as done (bazel-bootstrap: FTBFS: FetchGrpc.java:3: error: cannot find symbol)

2020-12-26 Thread Debian Bug Tracking System
: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > mkdir -p /<>/debian/ccache

Processed: Re: Bug#978189: bazel-bootstrap: FTBFS: FetchGrpc.java:3: error: cannot find symbol

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #978189 [src:bazel-bootstrap] bazel-bootstrap: FTBFS: FetchGrpc.java:3: error: cannot find symbol Added tag(s) pending. -- 978189: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978189 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#978189: bazel-bootstrap: FTBFS: FetchGrpc.java:3: error: cannot find symbol

2020-12-26 Thread Olek Wojnar
Control: tag -1 pending Hi Lucas, On Sat, Dec 26, 2020 at 4:39 PM Lucas Nussbaum wrote: > Source: bazel-bootstrap > Version: 3.4.0+ds-2 > Severity: serious > Justification: FTBFS on amd64 > Tags: bullseye sid ftbfs > Usertags: ftbfs-20201226 ftbfs-bullseye > > Hi, >

Processed (with 4 errors): Re: Bug#912941: mozjs52: No longer maintained upstream

2020-12-26 Thread Debian Bug Tracking System
Processing control commands: > clone -1 -2 Bug #912941 [src:mozjs52] mozjs52: No longer maintained upstream Bug 912941 cloned as bug 978404 No valid blocking bug(s) given; not doing anything Failed to clone 912941: Unknown/archived blocking bug(s):912940. > retitle -2 RM: mozjs52 -- ROM;

Bug#912941: mozjs52: No longer maintained upstream

2020-12-26 Thread Simon McVittie
Control: clone -1 -2 Control: retitle -2 RM: mozjs52 -- ROM; superseded by mozjs78, no reverse dependencies remain Control: severity -2 normal Control: reassign -2 ftp.debian.org On Sat, 26 Dec 2020 at 23:46:48 +0100, Aurelien Jarno wrote: > I confirm that nothing else is using this package

Bug#978184: marked as done (xfce4-wavelan-plugin: FTBFS: collect2: error: ld returned 1 exit status)

2020-12-26 Thread Debian Bug Tracking System
Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=link gcc -pthread >

Bug#974011: xmille: Incorrect license/copyright for xmille

2020-12-26 Thread Keith Packard
Steven Robbins writes: > On Saturday, December 26, 2020 12:50:58 A.M. CST Keith Packard wrote: > >> I've tagged version '1.0' of this repository and created some (not >> finished) debian packaging for it. This version has imported the mille >> sources from 'upstream' which include copyright

Bug#978315: dasher: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

2020-12-26 Thread Samuel Thibault
Santiago Vila, le dim. 27 déc. 2020 00:59:23 +0100, a ecrit: > On Sun, Dec 27, 2020 at 12:29:01AM +0100, Samuel Thibault wrote: > > Lucas Nussbaum, le sam. 26 déc. 2020 22:52:15 +0100, a ecrit: > > > > INTLTOOL_EXTRACT="/usr/bin/intltool-extract" > > > > XGETTEXT="/usr/bin/xgettext" srcdir=.

Bug#978399: marked as done (libogg contains RFC released under a non-free license)

2020-12-26 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 01:05:19 +0100 with message-id and subject line Re: libogg: diff for NMU version 1.3.4-0.1 has caused the Debian Bug report #978399, regarding libogg contains RFC released under a non-free license to be marked as done. This means that you claim that the

Bug#978399: libogg: diff for NMU version 1.3.4-0.1

2020-12-26 Thread Aurelien Jarno
On 2020-12-27 00:04, Simon McVittie wrote: > On Sun, 27 Dec 2020 at 00:45:43 +0100, Aurelien Jarno wrote: > > Looking at the licenses, both RFC included in the tarball are definitely > > non-free > > According to the replies to #894158, d/copyright contains permission to > distribute those RFCs

Bug#978399: libogg: diff for NMU version 1.3.4-0.1

2020-12-26 Thread Simon McVittie
On Sun, 27 Dec 2020 at 00:45:43 +0100, Aurelien Jarno wrote: > Looking at the licenses, both RFC included in the tarball are definitely > non-free According to the replies to #894158, d/copyright contains permission to distribute those RFCs under DFSG licenses, if I'm reading correctly. I would

Bug#978315: dasher: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

2020-12-26 Thread Santiago Vila
On Sun, Dec 27, 2020 at 12:29:01AM +0100, Samuel Thibault wrote: > Hello gettext maintainers, > > Lucas Nussbaum, le sam. 26 déc. 2020 22:52:15 +0100, a ecrit: > > During a rebuild of all packages in sid, your package failed to build > > on amd64. > > > > >

Bug#978368: marked as done (ibus-anthy: FTBFS: error: gettext infrastructure mismatch: using a Makefile.in.in from gettext version 0.19 but the autoconf macros are from gettext version 0.20)

2020-12-26 Thread Debian Bug Tracking System
with problems --- Begin Message --- Source: ibus-anthy Version: 1.5.11-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Processed: closing 978336

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 978336 21.0.0+20201226-2 Bug #978336 [src:picolisp] picolisp: FTBFS: flood -- Undefined The source 'picolisp' and version '21.0.0+20201226-2' do not appear to match any binary packages Marked as fixed in versions picolisp/21.0.0+2020122

Bug#974949: closed by Debian FTP Masters (reply to Axel Beckert ) (Bug#974949: fixed in systray-mdstat 1.2.0-2)

2020-12-26 Thread Axel Beckert
Ciao Francesco, Francesco Poli wrote: > >* Add hard dependency on virtual package notification-daemon. > > + Mention in README.Debian that not all notification-daemon > >implementations start up automatically upon user login. > > + Closes: #974949 > > Thank you Axel! :-)

Bug#978401: ibus-libpinyin: FTBFS on armel, armhf and mipsel: lua test failure

2020-12-26 Thread Boyuan Yang
Source: ibus-libpinyin Version: 1.12.0-2 Severity: serious Tags: ftbfs sid As shown on https://buildd.debian.org/status/package.php?p=ibus-libpinyin , currently ibus-libpinyin FTBFS on armel armhf and mipsel due to errors around Lua in tests:

Processed: Re: libogg: diff for NMU version 1.3.4-0.1

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > clone 894158 -1 Bug #894158 [src:libogg] libogg: new upstream release 1.3.3 Bug 894158 cloned as bug 978399 > retitle -1 libogg contains RFC released under a non-free license Bug #978399 [src:libogg] libogg: new upstream release 1.3.3 Changed Bug

Bug#978340: proftpd-mod-dnsbl: FTBFS: Cannot compile mod_dnsbl using prxs

2020-12-26 Thread Hilmar Preuße
Am 26.12.2020 um 23:08 teilte Lucas Nussbaum mit: Source: proftpd-mod-dnsbl Version: 0.1.5-5 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64

Bug#978379: marked as done (zhcon: FTBFS: configure:5812: error: possibly undefined macro: AM_INTL_SUBDIR (caused by gettext 0.19 -> 0.21?))

2020-12-26 Thread Debian Bug Tracking System
con Version: 1:0.2.6-17 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>' > tou

Bug#978217: marked as done (xfce4-xkb-plugin: FTBFS: xkb-plugin.h:47:60: error: unknown type name ‘XfcePanelTypeModule’)

2020-12-26 Thread Debian Bug Tracking System
Version: 1:0.8.1-2 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=compile

Bug#978315: dasher: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

2020-12-26 Thread Samuel Thibault
Hello gettext maintainers, Lucas Nussbaum, le sam. 26 déc. 2020 22:52:15 +0100, a ecrit: > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > INTLTOOL_EXTRACT="/usr/bin/intltool-extract" XGETTEXT="/usr/bin/xgettext" > > srcdir=. /usr/bin/intltool-update

Processed: Re: Bug#978369: apertium-eo-ca: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 978369 https://github.com/apertium/apertium-eo-ca/issues/2 Bug #978369 [src:apertium-eo-ca] apertium-eo-ca: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace) Set Bug forwarded-to-address to

Bug#978369: apertium-eo-ca: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)

2020-12-26 Thread Tino Didriksen
forwarded 978369 https://github.com/apertium/apertium-eo-ca/issues/2 thanks Fixed in upstream. -- Tino Didriksen

Processed: Re: Bug#978359: apertium-br-fr: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 978359 https://github.com/apertium/apertium-br-fr/issues/4 Bug #978359 [src:apertium-br-fr] apertium-br-fr: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace) Set Bug forwarded-to-address to

Bug#978359: apertium-br-fr: FTBFS: Error: Invalid dictionary (hint: entry on the right beginning with whitespace)

2020-12-26 Thread Tino Didriksen
forwarded 978359 https://github.com/apertium/apertium-br-fr/issues/4 thanks Fixed in upstream. -- Tino Didriksen

Bug#978262: marked as done (open-vm-tools: FTBFS: configure: error: gdk-pixbuf-xlib-2.0 not found. Please configure without X11 (using --without-x) or install the gdk-pixbuf-xlib-2.0 devel package.)

2020-12-26 Thread Debian Bug Tracking System
...@bugs.debian.org with problems --- Begin Message --- Source: open-vm-tools Version: 2:11.2.0-1 Severity: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant

Bug#978397: libudunits2-0: trying to overwrite '/usr/share/xml/udunits/udunits2-accepted.xml', which is also in package libudunits2-data 2.2.28-1

2020-12-26 Thread Axel Beckert
Hi, Axel Beckert wrote: > dpkg: error processing archive > /tmp/apt-dpkg-install-hDYr38/054-libudunits2-0_2.2.28-1_amd64.deb (--unpack): > trying to overwrite '/usr/share/xml/udunits/udunits2-accepted.xml', which is > also in package libudunits2-data 2.2.28-1 [...] > Seems as if either that

Bug#978315: dasher: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

2020-12-26 Thread Samuel Thibault
Samuel Thibault, le dim. 27 déc. 2020 00:13:55 +0100, a ecrit: > FTR, the file that poses problem is Testing/gtest/test/gtest_unittest.cc > This is not something that contains anything to be translated, we'd need > some option to just ignore Testing/ entirely. More precisely, it is line

Bug#978315: dasher: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

2020-12-26 Thread Samuel Thibault
FTR, the file that poses problem is Testing/gtest/test/gtest_unittest.cc This is not something that contains anything to be translated, we'd need some option to just ignore Testing/ entirely. Samuel

Processed: tagging 978171

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # Waiting for input from the APT developers if this is an issue in src:apt > tags 978171 + moreinfo Bug #978171 [src:aptitude] aptitude: FTBFS: pkgcachegen.h:32:10: fatal error: xxhash.h: No such file or directory Added tag(s) moreinfo. > thanks

Bug#978397: libudunits2-0: trying to overwrite '/usr/share/xml/udunits/udunits2-accepted.xml', which is also in package libudunits2-data 2.2.28-1

2020-12-26 Thread Axel Beckert
Package: libudunits2-0 Version: 2.2.28-1 Severity: serious Hi, upgrading libudunits2-0 from 2.2.26-5+b1 to 2.2.28-1 fails for me as follows: Preparing to unpack .../054-libudunits2-0_2.2.28-1_amd64.deb ... Unpacking libudunits2-0 (2.2.28-1) over (2.2.26-5+b1) ... dpkg: error processing archive

Processed: tagging 978325

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 978325 + confirmed Bug #978325 [src:libgit-repository-perl] libgit-repository-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Added tag(s) confirmed. > thanks Stopping processing here. Please contact me

Processed: bug 978325 is forwarded to https://rt.cpan.org/Ticket/Display.html?id=133951

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forwarded 978325 https://rt.cpan.org/Ticket/Display.html?id=133951 Bug #978325 [src:libgit-repository-perl] libgit-repository-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2 Set Bug forwarded-to-address to

Bug#978213: marked as done (xfce4-mount-plugin: FTBFS: collect2: error: ld returned 1 exit status)

2020-12-26 Thread Debian Bug Tracking System
: serious Justification: FTBFS on amd64 Tags: bullseye sid ftbfs Usertags: ftbfs-20201226 ftbfs-bullseye Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > /bin/bash ../libtool --tag=CC --mode=link gcc > -DPACKAGE_LOCALE_DIR=

Bug#912941: Cinnamon fix upstream and in salsa

2020-12-26 Thread Aurelien Jarno
On 2020-11-08 22:06, Bryan Quigley wrote: > This package is brought in by cinnamon through cjs. > > The cinnamon upstream project has been ported to mozjs78 in > https://github.com/linuxmint/cinnamon/pull/9624 > > And the switchover is included in an unreleased version in salsa - >

Processed: closing 978182

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 978182 0.5.2-1 Bug #978182 [src:xfce4-smartbookmark-plugin] xfce4-smartbookmark-plugin: FTBFS: collect2: error: ld returned 1 exit status The source 'xfce4-smartbookmark-plugin' and version '0.5.2-1' do not appear to match any binary

Bug#978182: closing 978182

2020-12-26 Thread Unit 193
close 978182 0.5.2-1 thanks This bug was fixed in 0.5.2-1, changelog included: xfce4-smartbookmark-plugin (0.5.2-1) unstable; urgency=medium . * Team upload. . [ Debian Janitor ] * Apply multi-arch hints. + xfce4-smartbookmark-plugin: Add Multi-Arch: same. . [ Unit 193 ]

Processed: affects 978258, merging 978258 978253

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 978258 src:bugwarrior Bug #978258 [src:taskw] taskw: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13 Added indication that 978258 affects src:bugwarrior > merge 978258 978253 Bug #978258

Bug#978058: marked as done (simgear FTBFS: error: cannot convert ‘boost::algorithm::split_iterator’ to ‘PathSplitIterator’)

2020-12-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Dec 2020 22:33:49 + with message-id and subject line Bug#978058: fixed in simgear 1:2020.3.5+dfsg-1 has caused the Debian Bug report #978058, regarding simgear FTBFS: error: cannot convert ‘boost::algorithm::split_iterator’ to ‘PathSplitIterator’ to be marked as

Bug#951891: marked as done (open-ath9k-htc-firmware FTBFS with binutils 2.34)

2020-12-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Dec 2020 22:33:42 + with message-id and subject line Bug#951891: fixed in open-ath9k-htc-firmware 1.4.0-106-gc583009+dfsg1-1 has caused the Debian Bug report #951891, regarding open-ath9k-htc-firmware FTBFS with binutils 2.34 to be marked as done. This means that

Bug#944169: marked as done (open-ath9k-htc-firmware: non-standard gcc/g++ used for build (gcc-8))

2020-12-26 Thread Debian Bug Tracking System
Your message dated Sat, 26 Dec 2020 22:33:42 + with message-id and subject line Bug#944169: fixed in open-ath9k-htc-firmware 1.4.0-106-gc583009+dfsg1-1 has caused the Debian Bug report #944169, regarding open-ath9k-htc-firmware: non-standard gcc/g++ used for build (gcc-8) to be marked as

Processed (with 1 error): merging 978258 978253

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > merge 978258 978253 Bug #978258 [src:taskw] taskw: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.9 returned exit code 13 Unable to merge bugs because: affects of #978253 is 'src:bugwarrior' not '' Failed to merge 978258: Did

Processed (with 1 error): reassign 978253 to src:taskw, merging 978249 978253, affects 978253

2020-12-26 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 978253 src:taskw Bug #978253 [src:bugwarrior] bugwarrior: FTBFS: ValueError: badly formed hexadecimal UUID string Bug reassigned from package 'src:bugwarrior' to 'src:taskw'. No longer marked as found in versions bugwarrior/1.7.0-3.

  1   2   3   4   >