Processed: Bug#1008380: confirmed and forwarded

Processing control commands: > tags -1 + confirmed Bug #1008380 [src:macromoleculebuilder] macromoleculebuilder: FTBFS: DensityMap.cpp:476:64: error: ‘gemmi::GridSetup’ has not been declared Added tag(s) confirmed. > forwarded -1 https://github.com/samuelflores/MMB/issues/24 Bug #1008380

Bug#1008380: confirmed and forwarded

Control: tags -1 + confirmed Control: forwarded -1 https://github.com/samuelflores/MMB/issues/24 Hello, gemmi::GridSetup has indeed disappeared in gemmi/0.5.3. I have forwarded the issue upstream. Andrius

Bug#1007894: marked as done (FTBFS: fails with pkg-js-tools dh_auto_build debian/nodejs/rxjs/build)

Your message dated Tue, 29 Mar 2022 05:34:01 + with message-id and subject line Bug#1007894: fixed in node-inquirer 8.2.1+~cs26.8.6-1 has caused the Debian Bug report #1007894, regarding FTBFS: fails with pkg-js-tools dh_auto_build debian/nodejs/rxjs/build to be marked as done. This means

Bug#1007894: marked as pending in node-inquirer

Control: tag -1 pending Hello, Bug #1007894 in node-inquirer 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#1007894 marked as pending in node-inquirer

Processing control commands: > tag -1 pending Bug #1007894 [node-inquirer] FTBFS: fails with pkg-js-tools dh_auto_build debian/nodejs/rxjs/build Added tag(s) pending. -- 1007894: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007894 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1008514: marked as done (FTBFS -- upstream test suite failure)

Your message dated Tue, 29 Mar 2022 04:49:03 + with message-id and subject line Bug#1008514: fixed in node-immutable 4.0.0-3 has caused the Debian Bug report #1008514, regarding FTBFS -- upstream test suite failure to be marked as done. This means that you claim that the problem has been

Processed: Re: Bug#1008493: gnome-control-center and gnome-settings-daemon version mismatch makes keyboard shortcuts fail

Processing control commands: > severity -1 serious Bug #1008493 {Done: Simon McVittie } [gnome-settings-daemon] gnome-control-center and gnome-settings-daemon version mismatch makes keyboard shortcuts fail Severity set to 'serious' from 'normal' -- 1008493:

Bug#1008316: in package dpkg marked as pending

Control: tag 1008316 pending Hi! Bug #1008316 in package dpkg reported by you has been fixed in the dpkg/dpkg.git Git repository. You can see the changelog below, and you can check the diff of the fix at: https://git.dpkg.org/cgit/dpkg/dpkg.git/diff/?id=48e33c406 --- dpkg-fsys-usrunmess:

Processed: Bug#1008316 in package dpkg marked as pending

Processing control commands: > tag 1008316 pending Bug #1008316 {Done: Guillem Jover } [dpkg] dpkg-fsys-usrunmess: Does not deal with untracked kernel modules Added tag(s) pending. -- 1008316: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008316 Debian Bug Tracking System Contact

Bug#1008478: marked as done (dpkg-fsys-usrunmess depends on umask 022)

Your message dated Tue, 29 Mar 2022 01:19:34 + with message-id and subject line Bug#1008478: fixed in dpkg 1.21.5 has caused the Debian Bug report #1008478, regarding dpkg-fsys-usrunmess depends on umask 022 to be marked as done. This means that you claim that the problem has been dealt

Bug#1008316: marked as done (dpkg-fsys-usrunmess: Does not deal with untracked kernel modules)

Your message dated Tue, 29 Mar 2022 01:19:34 + with message-id and subject line Bug#1008316: fixed in dpkg 1.21.5 has caused the Debian Bug report #1008316, regarding dpkg-fsys-usrunmess: Does not deal with untracked kernel modules to be marked as done. This means that you claim that the

Processed: reassign 1008283 to exim4-config, reassign 1008284 to exim4-config, tagging 903374 ...

Processing commands for cont...@bugs.debian.org: > reassign 1008283 exim4-config 4.95-4 Bug #1008283 [exim-config] Really confusing update-exim4.conf(8) man page Warning: Unknown package 'exim-config' Bug reassigned from package 'exim-config' to 'exim4-config'. No longer marked as found in

Processed: src:python-fluids: fails to migrate to testing for too long: unresolved RC issues and blocked by numba

Processing control commands: > close -1 1.0.9-1 Bug #1008570 [src:python-fluids] src:python-fluids: fails to migrate to testing for too long: unresolved RC issues and blocked by numba Marked as fixed in versions python-fluids/1.0.9-1. Bug #1008570 [src:python-fluids] src:python-fluids: fails to

Bug#1008570: src:python-fluids: fails to migrate to testing for too long: unresolved RC issues and blocked by numba

Source: python-fluids Version: 0.1.78-3 Severity: serious Control: close -1 1.0.9-1 Tags: sid bookworm User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 60

Bug#1005032: marked as done (ruby-hamster: autopkgtest regression: output differ)

Your message dated Mon, 28 Mar 2022 20:49:55 +0200 with message-id <4aec0557-ff49-efa3-2ddd-6f715c972...@debian.org> and subject line Re: ruby-hamster: autopkgtest regression: output differ has caused the Debian Bug report #1005032, regarding ruby-hamster: autopkgtest regression: output differ to

Bug#1008462: marked as done (notmuch: FTBFS: dh_auto_test: error: make -j8 test VERBOSE=1 V=1 returned exit code 2)

Your message dated Mon, 28 Mar 2022 18:34:29 + with message-id and subject line Bug#1008462: fixed in notmuch 0.35-2 has caused the Debian Bug report #1008462, regarding notmuch: FTBFS: dh_auto_test: error: make -j8 test VERBOSE=1 V=1 returned exit code 2 to be marked as done. This means

Processed: Re: Bug#1008189: meson: gnome module incorrectly requires gtk4-update-icon-cache

Processing commands for cont...@bugs.debian.org: > affects 1008189 src:gnome-shell Bug #1008189 [src:meson] meson: gnome module incorrectly requires gtk4-update-icon-cache Added indication that 1008189 affects src:gnome-shell > affects 1008189 src:gnome-calendar Bug #1008189 [src:meson] meson:

Bug#1008265: CVE-2018-25032: zlib memory corruption on deflate

Hi Mark, On Sat, Mar 26, 2022 at 09:02:31AM +0100, Salvatore Bonaccorso wrote: > Hi Mark, > > On Sat, Mar 26, 2022 at 12:59:15AM +, Mark Brown wrote: > > On Fri, Mar 25, 2022 at 10:50:51PM +0100, Salvatore Bonaccorso wrote: > > > > > Here is a preliminary debdiff to address this. > > > >

Processed: Bug#1008514 marked as pending in node-immutable

Processing control commands: > tag -1 pending Bug #1008514 [node-immutable] FTBFS -- upstream test suite failure Added tag(s) pending. -- 1008514: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008514 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1008514: marked as pending in node-immutable

Control: tag -1 pending Hello, Bug #1008514 in node-immutable 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#1008467: marked as done (python-tasklib: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13)

Your message dated Mon, 28 Mar 2022 16:20:47 + with message-id and subject line Bug#1008467: fixed in python-tasklib 2.4.3-2 has caused the Debian Bug report #1008467, regarding python-tasklib: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

Bug#1004143: marked as done (libminion-backend-sqlite-perl: test failures with SQLite 3.37)

Your message dated Mon, 28 Mar 2022 16:04:31 + with message-id and subject line Bug#1004143: fixed in libminion-backend-sqlite-perl 5.0.6-2 has caused the Debian Bug report #1004143, regarding libminion-backend-sqlite-perl: test failures with SQLite 3.37 to be marked as done. This means that

Bug#1008519: marked as done (libminion-backend-sqlite-perl: Please reintroduce libminion-backend-sqlite-perl in testing)

Your message dated Mon, 28 Mar 2022 16:04:31 + with message-id and subject line Bug#1004143: fixed in libminion-backend-sqlite-perl 5.0.6-2 has caused the Debian Bug report #1004143, regarding libminion-backend-sqlite-perl: Please reintroduce libminion-backend-sqlite-perl in testing to be

Processed: severity of 1008562 is serious

Processing commands for cont...@bugs.debian.org: > severity 1008562 serious Bug #1008562 [gnome-shell-extension-weather] gnome-shell-extension-weather: does not declare compatibility with GNOME Shell 42 Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me

Processed: severity of 1008120 is serious, severity of 1008535 is serious, severity of 1008536 is serious ...

Processing commands for cont...@bugs.debian.org: > severity 1008120 serious Bug #1008120 [gnome-shell-extension-bluetooth-quick-connect] gnome-shell-extension-bluetooth-quick-connect: does not declare compatibility with GNOME Shell 42 Severity set to 'serious' from 'important' > severity

Processed: Bug#1004143 marked as pending in libminion-backend-sqlite-perl

Processing control commands: > tag -1 pending Bug #1004143 [src:libminion-backend-sqlite-perl] libminion-backend-sqlite-perl: test failures with SQLite 3.37 Bug #1008519 [src:libminion-backend-sqlite-perl] libminion-backend-sqlite-perl: Please reintroduce libminion-backend-sqlite-perl in

Bug#1004143: marked as pending in libminion-backend-sqlite-perl

Control: tag -1 pending Hello, Bug #1004143 in libminion-backend-sqlite-perl 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: reassign 1008519 to src:libminion-backend-sqlite-perl, forcibly merging 1004143 1008519

Processing commands for cont...@bugs.debian.org: > reassign 1008519 src:libminion-backend-sqlite-perl 5.0.4-1 Bug #1008519 [libminion-backend-sqlite-perl] libminion-backend-sqlite-perl: Please reintroduce libminion-backend-sqlite-perl in testing Bug reassigned from package

Bug#1008512: marked as done (FTBFS in upstream test suite)

Your message dated Mon, 28 Mar 2022 15:21:20 + with message-id and subject line Bug#1008512: fixed in node-https-proxy-agent 5.0.0+~cs8.0.0-4 has caused the Debian Bug report #1008512, regarding FTBFS in upstream test suite to be marked as done. This means that you claim that the problem has

Bug#1008514: FTBFS -- upstream test suite failure

Real error is: Transforming async functions is not implemented. Use `transforms: { asyncAwait: false }` to skip transformation and disable this error.

Bug#1008075: marked as done (0ad: Apply patches from Ubuntu to fix build with glibc 2.35 & python 3.10)

Your message dated Mon, 28 Mar 2022 14:49:39 + with message-id and subject line Bug#1008075: fixed in 0ad 0.0.25b-2 has caused the Debian Bug report #1008075, regarding 0ad: Apply patches from Ubuntu to fix build with glibc 2.35 & python 3.10 to be marked as done. This means that you claim

Processed: Bug#1008512 marked as pending in node-https-proxy-agent

Processing control commands: > tag -1 pending Bug #1008512 [node-https-proxy-agent] FTBFS in upstream test suite Added tag(s) pending. -- 1008512: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008512 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1008512: marked as pending in node-https-proxy-agent

Control: tag -1 pending Hello, Bug #1008512 in node-https-proxy-agent 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: your mail

Processing commands for cont...@bugs.debian.org: > close 1008213 Bug #1008213 [src:nix] nix: autopkgtest regression on armhf, i386 and ppc64el: not supported on ‘arm-linux’, refusing to evaluate. Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1008075: marked as pending in 0ad

Control: tag -1 pending Hello, Bug #1008075 in 0ad 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#1008075 marked as pending in 0ad

Processing control commands: > tag -1 pending Bug #1008075 [src:0ad] 0ad: Apply patches from Ubuntu to fix build with glibc 2.35 & python 3.10 Ignoring request to alter tags of bug #1008075 to the same tags previously set -- 1008075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008075

Bug#1008368: marked as done (pigx-rnaseq: FTBFS: configure: error: R package rmarkdown not found.)

Your message dated Mon, 28 Mar 2022 13:22:23 + with message-id and subject line Bug#1008368: fixed in pigx-rnaseq 0.0.19+ds-1 has caused the Debian Bug report #1008368, regarding pigx-rnaseq: FTBFS: configure: error: R package rmarkdown not found. to be marked as done. This means that you

Processed: Re: Bug#1008406: gnome-console: FTBFS: ../meson.build:122:6: ERROR: Program 'gtk4-update-icon-cache' not found or not executable

Processing commands for cont...@bugs.debian.org: > affects 1008189 src:gnome-console Bug #1008189 [src:meson] meson: gnome module incorrectly requires gtk4-update-icon-cache Added indication that 1008189 affects src:gnome-console > End of message, stopping processing here. Please contact me if

Bug#1008406: marked as done (gnome-console: FTBFS: ../meson.build:122:6: ERROR: Program 'gtk4-update-icon-cache' not found or not executable)

Your message dated Mon, 28 Mar 2022 14:59:34 +0200 with message-id and subject line Re: [Debian-on-mobile-maintainers] Bug#1008406: gnome-console: FTBFS: ../meson.build:122:6: ERROR: Program 'gtk4-update-icon-cache' not found or not executable has caused the Debian Bug report #1008406,

Bug#1008449: marked as done (libgetdata: FTBFS: dh_missing: warning: usr/local/lib/python3.10/dist-packages/pygetdata.cpython-310-x86_64-linux-gnu.so exists in debian/tmp but is not installed to anywh

Your message dated Mon, 28 Mar 2022 12:49:59 + with message-id and subject line Bug#1008449: fixed in libgetdata 0.11.0-3 has caused the Debian Bug report #1008449, regarding libgetdata: FTBFS: dh_missing: warning:

Processed: severity of 1008075 is serious, tagging 1008075

Processing commands for cont...@bugs.debian.org: > severity 1008075 serious Bug #1008075 [src:0ad] 0ad: Apply patches from Ubuntu to fix build with glibc 2.35 & python 3.10 Severity set to 'serious' from 'normal' > tags 1008075 + pending upstream fixed-upstream ftbfs patch Bug #1008075 [src:0ad]

Bug#1008526: gnome-documents: deprecated and unmaintained upstream

Source: gnome-documents Severity: serious Tags: wontfix User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gnome-documents is no longer maintained upstream. It has been archived which means GNOME is no longer accepting any code fixes, translations, or even bug reports for it

Bug#1008523: marked as done (caffeine: Multiple FHS violations: Ships /usr/VERSION and /usr/compile_translations.py)

Your message dated Mon, 28 Mar 2022 12:04:35 + with message-id and subject line Bug#1008523: fixed in caffeine 2.9.8-2 has caused the Debian Bug report #1008523, regarding caffeine: Multiple FHS violations: Ships /usr/VERSION and /usr/compile_translations.py to be marked as done. This means

Bug#1007733: marked as done (golang-github-getkin-kin-openapi: autopkgtest regression on armhf and i386:)

Your message dated Mon, 28 Mar 2022 12:05:37 + with message-id and subject line Bug#1007733: fixed in golang-github-getkin-kin-openapi 0.91.0-2 has caused the Debian Bug report #1007733, regarding golang-github-getkin-kin-openapi: autopkgtest regression on armhf and i386: to be marked as

Bug#1008316: dpkg-fsys-usrunmess breaks system boot

On 28/03/2022 12:35, Guillem Jover wrote: There was no printed error beside the arror from dkms postinst (virtualbox assumed it was running virtualized, and nvidia just failling): just a congratulation message. Diid not check the return value of the script  via echo $? Ok, so if the script

Processed: Re: Bug#1005858: gh,gitsome: File conflict, both ship /usr/bin/gh

Processing commands for cont...@bugs.debian.org: > severity 1005858 important Bug #1005858 {Done: Anthony Fok } [gh,gitsome] gh,gitsome: File conflict, both ship /usr/bin/gh Severity set to 'important' from 'serious' > reopen 1005858 Bug #1005858 {Done: Anthony Fok } [gh,gitsome] gh,gitsome:

Processed: Bug#1007733 Forwarded upstream

Processing commands for cont...@bugs.debian.org: > forwarded 1007733 https://github.com/getkin/kin-openapi/pull/516 Bug #1007733 [src:golang-github-getkin-kin-openapi] golang-github-getkin-kin-openapi: autopkgtest regression on armhf and i386: Set Bug forwarded-to-address to

Processed: bug 1008523 is forwarded to https://bugs.launchpad.net/debian/+source/caffeine/+bug/1966674

Processing commands for cont...@bugs.debian.org: > forwarded 1008523 > https://bugs.launchpad.net/debian/+source/caffeine/+bug/1966674 Bug #1008523 [caffeine] caffeine: Multiple FHS violations: Ships /usr/VERSION and /usr/compile_translations.py Set Bug forwarded-to-address to

Bug#1007733: marked as pending in golang-github-getkin-kin-openapi

Control: tag -1 pending Hello, Bug #1007733 in golang-github-getkin-kin-openapi 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#1007733 marked as pending in golang-github-getkin-kin-openapi

Processing control commands: > tag -1 pending Bug #1007733 [src:golang-github-getkin-kin-openapi] golang-github-getkin-kin-openapi: autopkgtest regression on armhf and i386: Added tag(s) pending. -- 1007733: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1007733 Debian Bug Tracking System

Bug#1008349: python-securesystemslib: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p "3.10 3.9" returned exit code 13

I created an issue in the upstream ticket tracker, including a likely explanation and possible solutions: https://github.com/secure-systems-lab/securesystemslib/issues/397 TLDR: The cause of the error seems to be a race

Bug#1008523: caffeine: Multiple FHS violations: Ships /usr/VERSION and /usr/compile_translations.py

Package: caffeine Version: 2.9.8-1 Severity: serious Justification: Policy §9.1.1 / FHS §4.1 and §4.11 By chance I stumbled upon the two unexpected files /usr/VERSION /usr/compile_translations.py and noticed that these both belong to caffeine. These two files definitely don't belong there.

Bug#1008316: dpkg-fsys-usrunmess breaks system boot

On Mon, 2022-03-28 at 09:34:35 +, Éric Valette wrote: > On 3/28/22 01:29, Guillem Jover wrote: > >> Invoquing the dkms postinstall script fails because it does not find > >> /lib/modules/x.y.z > >> > >> directories and rebooting without graphic drivers and other stff does not > >> work.

Bug#1008522: fenics-basix: build-depends on python3-numba which is not in testing and broken in unstable

Package: fenics-basix Version: 0.3.0-11 Severity: serious Justification: rc policy - "Packages must be buildable within the same release." Your package build-depends on python3-numba. Unfortunately numba is not ready for python 3.10, it has been removed from testing and since the recent upload

Processed: Re: Bug#1008156: telegram-desktop: Crash when switch account

Processing control commands: > tag -1 upstream Bug #1008156 [telegram-desktop] telegram-desktop: Crash when switch account Added tag(s) upstream. -- 1008156: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008156 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1008156: telegram-desktop: Crash when switch account

Control: tag -1 upstream On Ср, 2022-03-23 at 11:49 +0100, Stefano Callegari wrote: > after last upgrade, when I try to switch to my second Telegram account (added > before), the program crashes. This will be fixed somehow in the upcoming upstream release, 3.6.2. signature.asc Description:

Bug#1008520: cctbx hard-codes the python version in it's local patches

Package: src:cctbx Version: 2021.12+ds1-3 Severity: serious Tags: sid bookworm User: debian-pyt...@lists.debian.org Usertags: python3.10 cctbx hard-codes the python version in it's local patches, and thus breaks with python 3.10 as the default python version. Please don't do that.

Bug#1008316: dpkg-fsys-usrunmess breaks system boot

On 3/28/22 01:29, Guillem Jover wrote: > > >> >>Gobally the scripts does a very good job but it missed to copy >> /usr/lib/modules to >> >> /lib/modules on a self generated kernel that has modules build via dkms and >> a >> >> few

Bug#1008510: marked as done (FTBFS unsufficient coverage)

Your message dated Mon, 28 Mar 2022 09:18:36 + with message-id and subject line Bug#1008510: fixed in node-base64url 3.0.1-8 has caused the Debian Bug report #1008510, regarding FTBFS unsufficient coverage to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1008393: marked as done (golang-github-albenik-go-serial: autopkgtest regression on ppc64el: undefined: unix.TCGETS2)

Your message dated Mon, 28 Mar 2022 07:57:26 + with message-id and subject line Bug#1008393: fixed in golang-github-albenik-go-serial 2.5.0-2 has caused the Debian Bug report #1008393, regarding golang-github-albenik-go-serial: autopkgtest regression on ppc64el: undefined: unix.TCGETS2 to be

Processed: Bug#1008510 marked as pending in node-base64url

Processing control commands: > tag -1 pending Bug #1008510 [node-base64url] FTBFS unsufficient coverage Added tag(s) pending. -- 1008510: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008510 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1008510: marked as pending in node-base64url

Control: tag -1 pending Hello, Bug #1008510 in node-base64url 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: Re: Actually the issue is with SiSU and Ruby3

Processing commands for cont...@bugs.debian.org: > reassign 1008405 sisu Bug #1008405 [src:live-manual] live-manual: FTBFS: cp: cannot stat '/<>/build/manual/*': No such file or directory Bug reassigned from package 'src:live-manual' to 'sisu'. No longer marked as found in versions

Bug#1008405: Actually the issue is with SiSU and Ruby3

reassign 1008405 sisu found 1008405 7.2.0-1 retitle 1008405 "sisu-complete: fails to run with Ruby 3.0" affects 1008405 +live-manual thanks Dear maintainer of SiSU, On 26/03/2022 22:54, Lucas Nussbaum wrote: Source: live-manual Version: 2:20151217.1 Severity: serious Justification: FTBFS Tags:

Bug#1008513: marked as done (FTBFS unsufficient coverage)

Your message dated Mon, 28 Mar 2022 07:09:05 + with message-id and subject line Bug#1008513: fixed in node-ignore 5.2.0-2 has caused the Debian Bug report #1008513, regarding FTBFS unsufficient coverage to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1008382: meson 0.62 regression: gtk-doc targets in src:glib2.0 lose their dependencies

Hi Simon, On 28/03/22 at 00:55 +0100, Simon McVittie wrote: > Control: reassign -1 meson 0.62.0-1 > Control: retitle -1 meson 0.62 regression: gtk-doc targets in src:glib2.0 > lose their dependencies > Control: affects -1 + src:glib2.0 > > On Sat, 26 Mar 2022 at 21:44:54 +0100, Lucas Nussbaum

Processed: Bug#1008513 marked as pending in node-ignore

Processing control commands: > tag -1 pending Bug #1008513 [node-ignore] FTBFS unsufficient coverage Added tag(s) pending. -- 1008513: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008513 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1008513: marked as pending in node-ignore

Control: tag -1 pending Hello, Bug #1008513 in node-ignore 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#1008514: FTBFS -- upstream test suite failure

Package: node-immutable Version: 4.0.0-2 Severity: serious Tags: ftbfs Trying to build the package in an unstable sbuild, I get the following failure: + NODE_PATH=node_modules:/usr/share/nodejs jest --ci __tests__/ArraySeq.ts Error at Function.missingTransform

Bug#1008513: FTBFS unsufficient coverage

Package: node-ignore Version: 5.2.0-1 Severity: serious Tags: ftbfs Building the package in an unstable sbuild, I get: ERROR: Coverage for lines (92.3%) does not meet global threshold (100%) ERROR: Coverage for functions (91.66%) does not meet global threshold (100%) ERROR: Coverage for branches

Bug#1008512: FTBFS in upstream test suite

Package: node-https-proxy-agent Version: 5.0.0+~cs8.0.0-3 Severity: serious Tags: ftbfs Trying to rebuild the package in an unstable sbuild gives the following failure in upstream test suite: 1) HttpsProxyAgent "http" module should receive the 407 authorization code on the

Bug#1008511: FTBFS failures in the upstream test suite

Package: node-configurable-http-proxy Version: 4.5.0+~cs15.1.4-3 Severity: serious Tags: ftbfs Building the package in an unstable sbuild, I get failures: Randomized with seed 97263 Started ..F...06:23:50.587 [ConfigProxy] ESC[31merrorESC[39m: 404 GET /nope 06:23:50.860

Bug#1008510: FTBFS unsufficient coverage

Package: node-base64url Version: 3.0.1-7 Severity: serious Tags: ftbfs Trying to build the package in an unstable sbuild, the upstream test suite fails because it doesn't find a 100% coverage: ERROR: Coverage for lines (97.22%) does not meet global threshold (100%) ERROR: Coverage for branches

Bug#1008509: FTBFS - six upstream tests failing

Package: node-config Version: 3.3.7-1 Severity: serious Tags: ftbfs While rebuilding your package with an unstable sbuild, it failed at six points in the upstream test suite, with the same error: » An unexpected error was caught: TypeError: Cannot set property offset of [object Object]

Bug#1008508: marked as done (borgbackup: Uninstallable in Debian Unstable due dependency on python 3 < 3.10)

Your message dated Mon, 28 Mar 2022 08:09:27 +0200 with message-id <24be2ebc-f41a-c8f8-6664-27aae30b0...@debian.org> and subject line Re: Bug#1008508: borgbackup: Uninstallable in Debian Unstable due dependency on python 3 < 3.10 has caused the Debian Bug report #1008508, regarding borgbackup: