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

2022-03-28 Thread Debian Bug Tracking System
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

Processed: closing 956940

2022-03-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 956940 Bug #956940 [cloud.debian.org] EC2 images should install compatibility symlinks for NVME drives Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 956940:

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

2022-03-28 Thread Debian Bug Tracking System
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

Bug#1006419: marked as done (Patch: build with pulseaudio)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Mar 2022 01:34:29 + with message-id and subject line Bug#1006419: fixed in freedv 1.7.0-2 has caused the Debian Bug report #1006419, regarding Patch: build with pulseaudio to be marked as done. This means that you claim that the problem has been dealt with. If this

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

2022-03-28 Thread Debian Bug Tracking System
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

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

2022-03-28 Thread Debian Bug Tracking System
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#261028: marked as done (libsasl2-modules-sql: sql format syntax doesn't differentiate NULL values)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Tue, 29 Mar 2022 01:03:11 +0200 with message-id and subject line Re: Progress on "sql format syntax doesn't differentiate NULL values" ? has caused the Debian Bug report #261028, regarding libsasl2-modules-sql: sql format syntax doesn't differentiate NULL values to be marked

Bug#1007793: marked as done (ovmf: edk2-stable202202 not working with QEMU NVMe)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 21:48:48 + with message-id and subject line Bug#1007793: fixed in edk2 2022.02-3 has caused the Debian Bug report #1007793, regarding ovmf: edk2-stable202202 not working with QEMU NVMe to be marked as done. This means that you claim that the problem has

Processed: Re: rnp: accepts weak cryptographic primitives

2022-03-28 Thread Debian Bug Tracking System
Processing control commands: > close 985907 0.16.0-1 Bug #985907 [src:rnp] rnp: accepts weak cryptographic primitives Marked as fixed in versions rnp/0.16.0-1. Bug #985907 [src:rnp] rnp: accepts weak cryptographic primitives Marked Bug as done -- 985907:

Bug#1008181: marked as done (spectre-meltdown-checker: False positive for CVE-2017-5715 due to failing to detect retpolines)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 20:38:46 + with message-id and subject line Bug#1008181: fixed in spectre-meltdown-checker 0.45-1 has caused the Debian Bug report #1008181, regarding spectre-meltdown-checker: False positive for CVE-2017-5715 due to failing to detect retpolines to be

Bug#1008493: marked as done (gnome-control-center and gnome-settings-daemon version mismatch makes keyboard shortcuts fail)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 20:35:24 + with message-id and subject line Bug#1008493: fixed in gnome-control-center 1:41.4-2 has caused the Debian Bug report #1008493, regarding gnome-control-center and gnome-settings-daemon version mismatch makes keyboard shortcuts fail to be marked

Bug#1008518: marked as done (nmu: libxxf86vm_1:1.1.4-1+b2)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 21:57:38 +0200 with message-id <7b74660b-e7b4-a025-d8d2-868f665af...@debian.org> and subject line Re: Bug#1008518: nmu: libxxf86vm_1:1.1.4-1+b2 has caused the Debian Bug report #1008518, regarding nmu: libxxf86vm_1:1.1.4-1+b2 to be marked as done. This means

Bug#1000714: marked as done (muparser: Please update to latest upstream version 2.3.2)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 19:50:49 + with message-id and subject line Bug#1000714: fixed in muparser 2.3.3-0.1 has caused the Debian Bug report #1000714, regarding muparser: Please update to latest upstream version 2.3.2 to be marked as done. This means that you claim that the

Bug#980964: marked as done (autopkgest-build-lxc uses old lxc configuration)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 19:49:04 + with message-id and subject line Bug#979450: fixed in autopkgtest 5.21 has caused the Debian Bug report #979450, regarding autopkgest-build-lxc uses old lxc configuration to be marked as done. This means that you claim that the problem has been

Bug#980965: marked as done (autopkgest-build-lxc uses old lxc configuration)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 19:49:04 + with message-id and subject line Bug#979450: fixed in autopkgtest 5.21 has caused the Debian Bug report #979450, regarding autopkgest-build-lxc uses old lxc configuration to be marked as done. This means that you claim that the problem has been

Bug#979450: marked as done (autopkgest-build-lxc uses old lxc configuration)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 19:49:04 + with message-id and subject line Bug#979450: fixed in autopkgtest 5.21 has caused the Debian Bug report #979450, regarding autopkgest-build-lxc uses old lxc configuration to be marked as done. This means that you claim that the problem has been

Bug#1008192: marked as done (libmojolicious-perl: Recommends of libmojolicious-perl contains build profile syntax)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 19:49:04 + with message-id and subject line Bug#1008192: fixed in autopkgtest 5.21 has caused the Debian Bug report #1008192, regarding libmojolicious-perl: Recommends of libmojolicious-perl contains build profile syntax to be marked as done. This means

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

2022-03-28 Thread Debian Bug Tracking System
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#1005032: marked as done (ruby-hamster: autopkgtest regression: output differ)

2022-03-28 Thread Debian Bug Tracking System
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)

2022-03-28 Thread Debian Bug Tracking System
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

Bug#1008516: marked as done (ITP: node-mj-context-menu -- reimplementation of MathJax context menu in TypeScript)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:00:19 + with message-id and subject line Bug#1008516: fixed in node-mj-context-menu 0.6.1+ds-1 has caused the Debian Bug report #1008516, regarding ITP: node-mj-context-menu -- reimplementation of MathJax context menu in TypeScript to be marked as done.

Bug#1008310: marked as done (ITP: uc-micro-py -- python port of uc.micro)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:00:22 + with message-id and subject line Bug#1008310: fixed in uc-micro-py 1.0.1-1 has caused the Debian Bug report #1008310, regarding ITP: uc-micro-py -- python port of uc.micro to be marked as done. This means that you claim that the problem has been

Bug#1008307: marked as done (ITP: sphinx-reredirects -- extension for Sphinx projects that handles redirects)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:00:22 + with message-id and subject line Bug#1008307: fixed in sphinx-reredirects 0.0.0+git20220326-1 has caused the Debian Bug report #1008307, regarding ITP: sphinx-reredirects -- extension for Sphinx projects that handles redirects to be marked as

Bug#1008248: marked as done (ITP: setcover -- Time/Memory Linear greedy set cover)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:00:22 + with message-id and subject line Bug#1008248: fixed in setcover 0.0~git20161128.b1de791-1 has caused the Debian Bug report #1008248, regarding ITP: setcover -- Time/Memory Linear greedy set cover to be marked as done. This means that you claim

Bug#1008233: marked as done (ITP: golang-github-jackc-pgtype -- Go types for over 70 PostgreSQL types)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:00:18 + with message-id and subject line Bug#1008233: fixed in golang-github-jackc-pgtype 1.10.0-1 has caused the Debian Bug report #1008233, regarding ITP: golang-github-jackc-pgtype -- Go types for over 70 PostgreSQL types to be marked as done. This

Bug#1008228: marked as done (ITP: golang-github-jackc-pgconn -- low-level PostgreSQL database driver)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:00:18 + with message-id and subject line Bug#1008228: fixed in golang-github-jackc-pgconn 1.11.0-1 has caused the Debian Bug report #1008228, regarding ITP: golang-github-jackc-pgconn -- low-level PostgreSQL database driver to be marked as done. This

Bug#1008182: marked as done (ITP: node-rewire -- Easy monkey-patching for node.js unit tests )

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:00:20 + with message-id and subject line Bug#1008182: fixed in node-rewire 6.0.0-1 has caused the Debian Bug report #1008182, regarding ITP: node-rewire -- Easy monkey-patching for node.js unit tests to be marked as done. This means that you claim that

Bug#1007988: marked as done (ITP: golang-github-iglou-eu-go-wildcard -- Fast and light wildcard pattern matching)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:00:17 + with message-id and subject line Bug#1007988: fixed in golang-github-iglou-eu-go-wildcard 1.0.3-1 has caused the Debian Bug report #1007988, regarding ITP: golang-github-iglou-eu-go-wildcard -- Fast and light wildcard pattern matching to be

Bug#1008144: marked as done (ITP: looktxt -- Convert free format text file into scientific data formats)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:00:19 + with message-id and subject line Bug#1008144: fixed in looktxt 1.4.1-1 has caused the Debian Bug report #1008144, regarding ITP: looktxt -- Convert free format text file into scientific data formats to be marked as done. This means that you

Bug#1007780: marked as done (ITP: golang-github-jackc-pgmock -- provides the ability to mock a PostgreSQL server)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:00:18 + with message-id and subject line Bug#1007780: fixed in golang-github-jackc-pgmock 0.0~git20210724.4ad1a82-1 has caused the Debian Bug report #1007780, regarding ITP: golang-github-jackc-pgmock -- provides the ability to mock a PostgreSQL server

Bug#1007721: marked as done (ITP: golang-github-badgerodon-peg -- Parsing Expression Grammar Parser in Go (library))

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:00:17 + with message-id and subject line Bug#1007721: fixed in golang-github-badgerodon-peg 0.0~git20130729.9e5f7f4-1 has caused the Debian Bug report #1007721, regarding ITP: golang-github-badgerodon-peg -- Parsing Expression Grammar Parser in Go

Bug#1000122: marked as done (gambas3: depends on obsolete pcre3 library)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:00:17 + with message-id and subject line Bug#1000122: fixed in gambas3 3.17.0-1 has caused the Debian Bug report #1000122, regarding gambas3: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been

Bug#1005377: marked as done (ITP: r-cran-jinjar -- GNU R template engine inspired by 'Jinja')

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:00:20 + with message-id and subject line Bug#1005377: fixed in r-cran-jinjar 0.1.0+dfsg-1 has caused the Debian Bug report #1005377, regarding ITP: r-cran-jinjar -- GNU R template engine inspired by 'Jinja' to be marked as done. This means that you

Bug#1006520: marked as done (pdns-recursor: FTBFS with OpenSSL 3.0)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 16:50:33 + with message-id and subject line Bug#1006520: fixed in pdns-recursor 4.6.1-1 has caused the Debian Bug report #1006520, regarding pdns-recursor: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been

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)

2022-03-28 Thread Debian Bug Tracking System
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#1008553: marked as done (libclass-dbi-perl: MySQL 5.7, "Can't get last insert id" error on inserting row)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 16:20:10 + with message-id and subject line Bug#1008553: fixed in libclass-dbi-perl 3.0.17-5 has caused the Debian Bug report #1008553, regarding libclass-dbi-perl: MySQL 5.7, "Can't get last insert id" error on inserting row to be marked as done. This

Bug#1008275: marked as done (libsane: Reinstate libieee1284 support for parallel printers)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 18:08:01 +0200 with message-id and subject line Re: Bug#1008275: libsane: Reinstate libieee1284 support for parallel printers has caused the Debian Bug report #1008275, regarding libsane: Reinstate libieee1284 support for parallel printers to be marked as

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

2022-03-28 Thread Debian Bug Tracking System
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

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

2022-03-28 Thread Debian Bug Tracking System
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#988647: marked as done (crash: please update to new upstream release)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 09:45:54 -0600 with message-id <20220328154412.zguygu67v2paw...@tazw.looney.xyz> and subject line Bug#988647: crash: please update to new upstream release has caused the Debian Bug report #988647, regarding crash: please update to new upstream release to be

Bug#1008552: marked as done (gnome-shell-extension-kimpanel: should presumably depend on gnome-shell)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 15:49:47 + with message-id and subject line Bug#1008552: fixed in gnome-shell-extension-kimpanel 0.0~git20220324.4502fe5-2 has caused the Debian Bug report #1008552, regarding gnome-shell-extension-kimpanel: should presumably depend on gnome-shell to be

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

2022-03-28 Thread Debian Bug Tracking System
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#1008175: marked as done ("-o sides=two-sided-long-edge always prints one-sided with lp & lpr")

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 16:08:22 +0100 with message-id <28032022154012.5a86bf6bb...@desktop.copernicus.org.uk> and subject line Re: Bug#1008175: -o sides=two-sided-long-edge always prints one-sided with lp & lpr has caused the Debian Bug report #1008175, regarding "-o

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

2022-03-28 Thread Debian Bug Tracking System
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

Bug#896907: marked as done (openjdk-8-jre-headless: Headless JRE package should not configure assistive technologies)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 15:42:28 +0100 with message-id and subject line Avez-vous besoin d'un prêt? has caused the Debian Bug report #896907, regarding openjdk-8-jre-headless: Headless JRE package should not configure assistive technologies to be marked as done. This means that you

Bug#859138: marked as done (java.lang.UnsupportedOperationException: The BROWSE action is not supported on the current platform!)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 15:42:28 +0100 with message-id and subject line Avez-vous besoin d'un prêt? has caused the Debian Bug report #859138, regarding java.lang.UnsupportedOperationException: The BROWSE action is not supported on the current platform! to be marked as done. This

Bug#819785: marked as done (openjdk-8-jre-headless: Debug information missing in JRE jars)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 15:42:28 +0100 with message-id and subject line Avez-vous besoin d'un prêt? has caused the Debian Bug report #819785, regarding openjdk-8-jre-headless: Debug information missing in JRE jars to be marked as done. This means that you claim that the problem has

Bug#760982: marked as done (openjdk-8 needs time zone data)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 15:42:20 +0100 with message-id and subject line Avez-vous besoin d'un prêt? has caused the Debian Bug report #760982, regarding openjdk-8 needs time zone data to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: your mail

2022-03-28 Thread Debian Bug Tracking System
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#1004907: marked as done (psi4: incorrect location for Python extension?)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 13:54:06 + with message-id and subject line Bug#1004907: fixed in psi4 1:1.3.2+dfsg-2.1 has caused the Debian Bug report #1004907, regarding psi4: incorrect location for Python extension? to be marked as done. This means that you claim that the problem has

Bug#1007883: marked as done (python3-sphinx: Dependent packages fail with 'no module named ipython_genutils')

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 16:45:08 +0300 with message-id and subject line Re: Bug#1007883: python3-sphinx: Dependent packages fail with 'no module named ipython_genutils' has caused the Debian Bug report #1007883, regarding python3-sphinx: Dependent packages fail with 'no module named

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

2022-03-28 Thread Debian Bug Tracking System
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

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

2022-03-28 Thread Debian Bug Tracking System
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

2022-03-28 Thread Debian Bug Tracking System
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:

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

2022-03-28 Thread Debian Bug Tracking System
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:)

2022-03-28 Thread Debian Bug Tracking System
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#998786: marked as done (cpm: bashism in configure script)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 11:05:10 + with message-id and subject line Bug#998786: fixed in cpm 0.32-1.4 has caused the Debian Bug report #998786, regarding cpm: bashism in configure script to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#949088: marked as done (cpm: FTBFS with libxml2 not shipping xml2-config)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 11:05:10 + with message-id and subject line Bug#949088: fixed in cpm 0.32-1.4 has caused the Debian Bug report #949088, regarding cpm: FTBFS with libxml2 not shipping xml2-config to be marked as done. This means that you claim that the problem has been

Bug#851594: marked as done (cpm: FTBFS if ncursesw5-config is not present)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 11:05:10 + with message-id and subject line Bug#851594: fixed in cpm 0.32-1.4 has caused the Debian Bug report #851594, regarding cpm: FTBFS if ncursesw5-config is not present to be marked as done. This means that you claim that the problem has been dealt

Bug#1004574: marked as done (rbdoom3bfg: FTBFS with ffmpeg 5.0)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 10:32:57 + with message-id and subject line Bug#1004574: fixed in rbdoom3bfg 1.4.0+dfsg-1 has caused the Debian Bug report #1004574, regarding rbdoom3bfg: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#1008506: marked as done (RFS: cpm/0.32-1.4 [NMU] -- Curses based password manager using PGP-encryption)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 11:56:47 +0200 with message-id and subject line Re: RFS: cpm/0.32-1.4 [NMU] -- Curses based password manager using PGP-encryption has caused the Debian Bug report #1008506, regarding RFS: cpm/0.32-1.4 [NMU] -- Curses based password manager using

Processed: RFS: sane-backends/1.1.1-5 -- API library for scanners

2022-03-28 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1008494 Bug #1008494 [sponsorship-requests] RFS: sane-backends/1.1.1-5 -- API library for scanners Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1008494:

Bug#942176: marked as done (sane-genesys: 4800 dpi color scan aborts using Canon LiDE 220)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 09:21:04 + with message-id and subject line Bug#942176: fixed in sane-backends 1.1.1-5 has caused the Debian Bug report #942176, regarding sane-genesys: 4800 dpi color scan aborts using Canon LiDE 220 to be marked as done. This means that you claim that

Bug#1008488: marked as done (Use --enable-parport-directio only on hurd-i386)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 09:21:04 + with message-id and subject line Bug#1008488: fixed in sane-backends 1.1.1-5 has caused the Debian Bug report #1008488, regarding Use --enable-parport-directio only on hurd-i386 to be marked as done. This means that you claim that the problem

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

2022-03-28 Thread Debian Bug Tracking System
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)

2022-03-28 Thread Debian Bug Tracking System
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

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

2022-03-28 Thread Debian Bug Tracking System
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#1008080: marked as done (Some sites do not work)

2022-03-28 Thread Debian Bug Tracking System
Your message dated Mon, 28 Mar 2022 08:44:28 +0200 with message-id <00df781d-4a77-4ae0-820f-53f087a18...@debian.org> and subject line Re: Some sites do not work has caused the Debian Bug report #1008080, regarding Some sites do not work to be marked as done. This means that you claim that the

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

2022-03-28 Thread Debian Bug Tracking System
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: