Bug#999252: marked as done (efax: missing required debian/rules targets build-arch and/or build-indep)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 May 2022 04:48:51 + with message-id and subject line Bug#999252: fixed in efax 1:0.9a-21 has caused the Debian Bug report #999252, regarding efax: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means that you claim

Bug#916253: marked as done (efax FTCBFS: builds for the wrong architecture)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 May 2022 04:48:51 + with message-id and subject line Bug#916253: fixed in efax 1:0.9a-21 has caused the Debian Bug report #916253, regarding efax FTCBFS: builds for the wrong architecture to be marked as done. This means that you claim that the problem has been

Bug#1010872: marked as done (efax: reproducible-builds: differing buildid in /usr/bin/efax and /usr/bin/efix)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 May 2022 04:48:51 + with message-id and subject line Bug#1010872: fixed in efax 1:0.9a-21 has caused the Debian Bug report #1010872, regarding efax: reproducible-builds: differing buildid in /usr/bin/efax and /usr/bin/efix to be marked as done. This means that you

Bug#1010864: marked as done (node-chokidar: flaky autopkgtest on most architectures:)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 May 2022 04:48:56 + with message-id and subject line Bug#1010864: fixed in node-chokidar 3.5.3-2 has caused the Debian Bug report #1010864, regarding node-chokidar: flaky autopkgtest on most architectures: to be marked as done. This means that you claim that the

Bug#1005979: marked as done (Please migrate away from dpatch)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 May 2022 04:48:51 + with message-id and subject line Bug#1005979: fixed in efax 1:0.9a-21 has caused the Debian Bug report #1005979, regarding Please migrate away from dpatch to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#943580: marked as done (dh_python3 doesn't recognize typing)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 20:27:57 -0700 with message-id <87czgjctvm@hope.eyrie.org> and subject line Re: Bug#943580: dh_python3 doesn't recognize typing has caused the Debian Bug report #943580, regarding dh_python3 doesn't recognize typing to be marked as done. This means that you

Bug#1010177: marked as done (r8168-dkms: dkms build failed on kernel 5.17)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 May 2022 02:37:06 + with message-id and subject line Bug#1010177: fixed in r8168 8.050.00-1 has caused the Debian Bug report #1010177, regarding r8168-dkms: dkms build failed on kernel 5.17 to be marked as done. This means that you claim that the problem has been

Bug#1010871: marked as done (dvbtune: reproducible-builds: embedded build paths in various binaries)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Thu, 12 May 2022 01:34:06 + with message-id and subject line Bug#1010871: fixed in dvbtune 0.5.ds-4 has caused the Debian Bug report #1010871, regarding dvbtune: reproducible-builds: embedded build paths in various binaries to be marked as done. This means that you claim

Bug#974959: marked as done (dynare: reproducible builds: autotools generated files contain variable paths and data)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 16:35:13 -0700 with message-id <87pmkjlk26.fsf@contorta> and subject line Re: Bug#974959: dynare: reproducible builds: autotools generated files contain variable paths and data has caused the Debian Bug report #974959, regarding dynare: reproducible builds:

Bug#1010870: marked as done (pidgin-blinklight: reproducible-builds: embedded build paths in various binaries)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 23:19:15 + with message-id and subject line Bug#1010870: fixed in pidgin-blinklight 0.11.1-5 has caused the Debian Bug report #1010870, regarding pidgin-blinklight: reproducible-builds: embedded build paths in various binaries to be marked as done. This

Bug#999100: marked as done (pidgin-blinklight: missing required debian/rules targets build-arch and/or build-indep)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 23:19:15 + with message-id and subject line Bug#999100: fixed in pidgin-blinklight 0.11.1-5 has caused the Debian Bug report #999100, regarding pidgin-blinklight: missing required debian/rules targets build-arch and/or build-indep to be marked as done.

Processed: closing 1008465

2022-05-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1008465 Bug #1008465 [src:python-fabio] python-fabio: FTBFS: Could not import extension nbsphinx (exception: No module named 'ipython_genutils') Marked Bug as done > thanks Stopping processing here. Please contact me if you need

Bug#1010607: marked as done (transition: libpodofo)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 22:40:02 +0200 with message-id and subject line Re: Bug#1010607: transition: libpodofo has caused the Debian Bug report #1010607, regarding transition: libpodofo to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1006568: marked as done (rauc: FTBFS with OpenSSL 3.0)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 22:19:06 +0200 with message-id <20220511201906.2iq2pny4mhbmd...@pengutronix.de> and subject line Re: Bug#1006568: rauc: FTBFS with OpenSSL 3.0 has caused the Debian Bug report #1006568, regarding rauc: FTBFS with OpenSSL 3.0 to be marked as done. This means

Bug#1010865: marked as done (RFS: opencpn/5.6.2+dfsg-1~bpo11+2 -- Open Source Chartplotter and Marine GPS Navigation Software)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 22:31:25 +0200 with message-id <2bcc2d94-91c0-b359-0d8c-dd7decc56...@debian.org> and subject line Re: RFS: opencpn/5.6.2+dfsg-1~bpo11+2 -- Open Source Chartplotter and Marine GPS Navigation Software has caused the Debian Bug report #1010865, regarding RFS:

Processed: src:pysph: fails to migrate to testing for too long: new build dependency not available on ppc64el and s390x

2022-05-11 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.0~b1-1 Bug #1010862 [src:pysph] src:pysph: fails to migrate to testing for too long: new build dependency not available on ppc64el and s390x Marked as fixed in versions pysph/1.0~b1-1. Bug #1010862 [src:pysph] src:pysph: fails to migrate to testing for

Bug#1009417: marked as done (saga: FTBFS: configure: error: cannot import Python module "distutils".)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 19:19:26 + with message-id and subject line Bug#1009417: fixed in saga 7.3.0+dfsg-8 has caused the Debian Bug report #1009417, regarding saga: FTBFS: configure: error: cannot import Python module "distutils". to be marked as done. This means that you

Bug#990888: marked as done (libnss-gw-name FTCBFS: builds for the build architecture)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:48:56 + with message-id and subject line Bug#990888: fixed in libnss-gw-name 0.3-4 has caused the Debian Bug report #990888, regarding libnss-gw-name FTCBFS: builds for the build architecture to be marked as done. This means that you claim that the

Bug#1010859: marked as done (libnss-gw-name: reproducible-builds: embedded build paths in libnss_gw_name.so.*)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:48:56 + with message-id and subject line Bug#1010859: fixed in libnss-gw-name 0.3-4 has caused the Debian Bug report #1010859, regarding libnss-gw-name: reproducible-builds: embedded build paths in libnss_gw_name.so.* to be marked as done. This means

Bug#1009910: marked as done (libnss-gw-name: Outdated VCS information, maybe move to salsa.d.o?)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:48:56 + with message-id and subject line Bug#1009910: fixed in libnss-gw-name 0.3-4 has caused the Debian Bug report #1009910, regarding libnss-gw-name: Outdated VCS information, maybe move to salsa.d.o? to be marked as done. This means that you claim

Bug#999566: marked as done (debian-policy: highlight source code examples)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:34:42 + with message-id and subject line Bug#999566: fixed in debian-policy 4.6.1.0 has caused the Debian Bug report #999566, regarding debian-policy: highlight source code examples to be marked as done. This means that you claim that the problem has

Bug#542288: marked as done (Versions for native packages, NMU's, and binary only uploads)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:34:42 + with message-id and subject line Bug#542288: fixed in debian-policy 4.6.1.0 has caused the Debian Bug report #542288, regarding Versions for native packages, NMU's, and binary only uploads to be marked as done. This means that you claim that the

Bug#850729: marked as done (debian-policy: Documenting special version number suffixes)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:34:42 + with message-id and subject line Bug#542288: fixed in debian-policy 4.6.1.0 has caused the Debian Bug report #542288, regarding debian-policy: Documenting special version number suffixes to be marked as done. This means that you claim that the

Bug#850729: marked as done (debian-policy: Documenting special version number suffixes)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:34:42 + with message-id and subject line Bug#850729: fixed in debian-policy 4.6.1.0 has caused the Debian Bug report #850729, regarding debian-policy: Documenting special version number suffixes to be marked as done. This means that you claim that the

Bug#1008480: marked as done (debian-policy: The mime-support package was split into media-types and mailcap)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:34:42 + with message-id and subject line Bug#1008480: fixed in debian-policy 4.6.1.0 has caused the Debian Bug report #1008480, regarding debian-policy: The mime-support package was split into media-types and mailcap to be marked as done. This means

Bug#999826: marked as done (debian-policy: fix Build-Depends footnote)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:34:42 + with message-id and subject line Bug#999826: fixed in debian-policy 4.6.1.0 has caused the Debian Bug report #999826, regarding debian-policy: fix Build-Depends footnote to be marked as done. This means that you claim that the problem has been

Bug#1010849: marked as done (DWARF support disabled during build / no symbolic stack traces or argument types)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:34:01 + with message-id and subject line Bug#1010849: fixed in bpftrace 0.14.1-5 has caused the Debian Bug report #1010849, regarding DWARF support disabled during build / no symbolic stack traces or argument types to be marked as done. This means that

Bug#998063: marked as done (debian-policy: New virtual package: {default-,}dbus-system-bus)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:34:42 + with message-id and subject line Bug#998063: fixed in debian-policy 4.6.1.0 has caused the Debian Bug report #998063, regarding debian-policy: New virtual package: {default-,}dbus-system-bus to be marked as done. This means that you claim that

Bug#992601: marked as done (Allow non-64-bit packages to install to /usr/lib64/ again)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:34:42 + with message-id and subject line Bug#992601: fixed in debian-policy 4.6.1.0 has caused the Debian Bug report #992601, regarding Allow non-64-bit packages to install to /usr/lib64/ again to be marked as done. This means that you claim that the

Bug#1010849: marked as done (DWARF support disabled during build / no symbolic stack traces or argument types)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:33:55 + with message-id and subject line Bug#1010849: fixed in bpftrace 0.14.1-4 has caused the Debian Bug report #1010849, regarding DWARF support disabled during build / no symbolic stack traces or argument types to be marked as done. This means that

Bug#542288: marked as done (Versions for native packages, NMU's, and binary only uploads)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:34:42 + with message-id and subject line Bug#850729: fixed in debian-policy 4.6.1.0 has caused the Debian Bug report #850729, regarding Versions for native packages, NMU's, and binary only uploads to be marked as done. This means that you claim that the

Bug#991461: marked as done (linux-image-5.10.0-8-armmp: [armhf] PHC not available with driver fec on i.MX6 SoC)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:00:09 + with message-id and subject line Bug#991461: fixed in linux 5.17.6-1 has caused the Debian Bug report #991461, regarding linux-image-5.10.0-8-armmp: [armhf] PHC not available with driver fec on i.MX6 SoC to be marked as done. This means that

Bug#940672: marked as done (Please add support for HP x2 210 PMIC and sound card)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:00:09 + with message-id and subject line Bug#940672: fixed in linux 5.17.6-1 has caused the Debian Bug report #940672, regarding Please add support for HP x2 210 PMIC and sound card to be marked as done. This means that you claim that the problem has

Bug#1009858: marked as done (linux: please consider building the modules necessary for the MNT Reform laptop)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 18:00:09 + with message-id and subject line Bug#1009858: fixed in linux 5.17.6-1 has caused the Debian Bug report #1009858, regarding linux: please consider building the modules necessary for the MNT Reform laptop to be marked as done. This means that you

Bug#1010822: marked as done (jupyter-client: autopkgtest regression: Unknown config option: asyncio_mode)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 17:19:17 + with message-id and subject line Bug#1010822: fixed in jupyter-client 7.3.0-3 has caused the Debian Bug report #1010822, regarding jupyter-client: autopkgtest regression: Unknown config option: asyncio_mode to be marked as done. This means that

Bug#930926: marked as done (bbrun FTCBFS: does not pass cross tools to make)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 16:03:56 + with message-id and subject line Bug#930926: fixed in bbrun 1.6-9 has caused the Debian Bug report #930926, regarding bbrun FTCBFS: does not pass cross tools to make to be marked as done. This means that you claim that the problem has been dealt

Bug#995462: marked as done (bbrun: fails to build on RISC-V)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 16:03:56 + with message-id and subject line Bug#995462: fixed in bbrun 1.6-9 has caused the Debian Bug report #995462, regarding bbrun: fails to build on RISC-V to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1010828: marked as done (bbrun: reproducible-builds: embedded build paths in /usr/bin/bbrun)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 16:03:56 + with message-id and subject line Bug#1010828: fixed in bbrun 1.6-9 has caused the Debian Bug report #1010828, regarding bbrun: reproducible-builds: embedded build paths in /usr/bin/bbrun to be marked as done. This means that you claim that the

Bug#1009461: marked as done (weasyprint: FTBFS: dh_usrlocal: error: debian/weasyprint/usr/local/bin/weasyprint is not a directory)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 15:35:59 + with message-id and subject line Bug#1009461: fixed in weasyprint 54.1-2 has caused the Debian Bug report #1009461, regarding weasyprint: FTBFS: dh_usrlocal: error: debian/weasyprint/usr/local/bin/weasyprint is not a directory to be marked as

Processed: Merge duplicates

2022-05-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1009411 src:ruby-i18n-inflector Bug #1009411 [ruby-i18n-inflector] ruby-i18n-inflector-rails: FTBFS: ERROR: Test "ruby3.0" failed: cannot load such file -- i18n/core_ext/hash Bug reassigned from package 'ruby-i18n-inflector' to

Bug#1009403: marked as done (libnetfilter-log-dev lost required dependencies on libnfnetlink-dev and libmnl-dev)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 15:04:02 + with message-id and subject line Bug#1009403: fixed in libnetfilter-log 1.0.2-3 has caused the Debian Bug report #1009403, regarding libnetfilter-log-dev lost required dependencies on libnfnetlink-dev and libmnl-dev to be marked as done. This

Bug#682246: marked as done (postfix: postsuper man pages needs update on -d example)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 15:50:50 +0200 with message-id <20220511135050.gx1...@rosa.stappers.it> and subject line Fixed upstream has caused the Debian Bug report #682246, regarding postfix: postsuper man pages needs update on -d example to be marked as done. This means that you claim

Bug#1009419: marked as done (cider: FTBFS: Config value: 'pages'. Error: The configuration option 'pages' was removed from MkDocs. Use 'nav' instead.)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 13:33:54 + with message-id and subject line Bug#1009419: fixed in cider 0.19.0+dfsg-3 has caused the Debian Bug report #1009419, regarding cider: FTBFS: Config value: 'pages'. Error: The configuration option 'pages' was removed from MkDocs. Use 'nav'

Bug#1006517: marked as done (openrct2: FTBFS with OpenSSL 3.0)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 11:06:46 + with message-id <4c790d5c9994396e5598e4a941d5361cde2393e9.ca...@calenhad.com> and subject line Re: Bug#1006517: openrct2: FTBFS with OpenSSL 3.0 has caused the Debian Bug report #1006517, regarding openrct2: FTBFS with OpenSSL 3.0 to be marked as

Bug#989034: marked as done (wifi-qr: Pointless package description)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 10:35:54 + with message-id and subject line Bug#989034: fixed in wifi-qr 0.2-2 has caused the Debian Bug report #989034, regarding wifi-qr: Pointless package description to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1010772: marked as done (partman-hfs: [INTL:nl] Dutch translation of debconf messages)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 10:34:57 + with message-id and subject line Bug#1010772: fixed in partman-hfs 2 has caused the Debian Bug report #1010772, regarding partman-hfs: [INTL:nl] Dutch translation of debconf messages to be marked as done. This means that you claim that the

Bug#1010262: marked as done (RFS: wifi-qr/0.2-2 -- WiFi Share and Connect with QR)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 12:21:54 +0200 with message-id and subject line Re: Bug#1010262: RFS: wifi-qr/0.2-2 -- WiFi Share and Connect with QR has caused the Debian Bug report #1010262, regarding RFS: wifi-qr/0.2-2 -- WiFi Share and Connect with QR to be marked as done. This means

Bug#1006246: marked as done (nodejs: FTBFS with OpenSSL 3.0)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 09:34:03 + with message-id and subject line Bug#1006246: fixed in nodejs 16.14.2+dfsg1-1 has caused the Debian Bug report #1006246, regarding nodejs: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#974503: marked as done (qpid-proton: autopkgtest must be marked superficial)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 08:23:09 + with message-id and subject line Bug#974503: fixed in qpid-proton 0.37.0-1 has caused the Debian Bug report #974503, regarding qpid-proton: autopkgtest must be marked superficial to be marked as done. This means that you claim that the problem

Bug#1006562: marked as done (qpid-proton: FTBFS with OpenSSL 3.0)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 08:23:09 + with message-id and subject line Bug#1006562: fixed in qpid-proton 0.37.0-1 has caused the Debian Bug report #1006562, regarding qpid-proton: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#1010835: marked as done (samba: testparm fails, lock directory /run/samba does not exist)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 08:23:33 + with message-id and subject line Bug#1010835: fixed in samba 2:4.16.1+dfsg-4 has caused the Debian Bug report #1010835, regarding samba: testparm fails, lock directory /run/samba does not exist to be marked as done. This means that you claim

Bug#1006513: marked as done (openpace: FTBFS with OpenSSL 3.0)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 07:49:00 + with message-id and subject line Bug#1006513: fixed in openpace 1.1.2+ds-1 has caused the Debian Bug report #1006513, regarding openpace: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#926300: marked as done (qpid-proton: please make the documentation build reproducibly)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 09:40:55 +0200 with message-id <45513437-218a-c030-5e28-7667b8619...@debian.org> and subject line Closing bug has caused the Debian Bug report #926300, regarding qpid-proton: please make the documentation build reproducibly to be marked as done. This means that

Bug#819345: marked as done (qpid-proton: CVE-2016-2166: reactor sends messages in clear if ssl is requested but not available)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 09:37:21 +0200 with message-id <6c4168fc-c4dd-1d28-bb87-aea252aee...@debian.org> and subject line This was fixed long ago has caused the Debian Bug report #819345, regarding qpid-proton: CVE-2016-2166: reactor sends messages in clear if ssl is requested but not

Bug#1006340: marked as done (dnsdist: FTBFS with OpenSSL 3.0)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 08:46:08 +0200 with message-id <20220511064608.jmhcoekut4teh...@zeha.at> and subject line fixed in 1.7.1 has caused the Debian Bug report #1006340, regarding dnsdist: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim that the problem has

Bug#1010817: marked as done (Ambiguity between intel-media-va-driver and i965-va-driver descriptions)

2022-05-11 Thread Debian Bug Tracking System
Your message dated Wed, 11 May 2022 08:20:31 +0200 with message-id and subject line Re: Bug#1010817: Ambiguity between intel-media-va-driver and i965-va-driver descriptions has caused the Debian Bug report #1010817, regarding Ambiguity between intel-media-va-driver and i965-va-driver