Bug#997258: marked as done (tiddit: FTBFS: Translocation.cpp:13:74: error: taking address of rvalue [-fpermissive])

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 19:35:12 + with message-id and subject line Bug#997258: fixed in tiddit 2.12.1+dfsg-2 has caused the Debian Bug report #997258, regarding tiddit: FTBFS: Translocation.cpp:13:74: error: taking address of rvalue [-fpermissive] to be marked as done. This

Bug#955229: marked as done (ibus-input-pad: Migrate from /usr/lib/ibus to /usr/libexec)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sun, 31 Oct 2021 00:03:53 + with message-id and subject line Bug#955229: fixed in ibus-input-pad 1.4.99.20140916-1~exp1 has caused the Debian Bug report #955229, regarding ibus-input-pad: Migrate from /usr/lib/ibus to /usr/libexec to be marked as done. This means that you

Bug#997662: marked as done (lintian: Incorrect tag: package-contains-python-dot-directory for .egg-info directories)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 09:18:46 + with message-id and subject line Bug#997662: fixed in lintian 2.111.0 has caused the Debian Bug report #997662, regarding lintian: Incorrect tag: package-contains-python-dot-directory for .egg-info directories to be marked as done. This means

Bug#993662: marked as done (lintian: Please warn for source file that have This file was autogenerated or DO NOT EDIT BY HAND)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 09:18:46 + with message-id and subject line Bug#993662: fixed in lintian 2.111.0 has caused the Debian Bug report #993662, regarding lintian: Please warn for source file that have This file was autogenerated or DO NOT EDIT BY HAND to be marked as done.

Bug#941299: marked as done (Unable to boot the Buster installer in qemu/libvirt when using the Virtio graphic card)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 15:26:46 +0200 with message-id <20211030152646.e7f3b47e960e6d713ed12...@mailbox.org> and subject line Re: Bug#941299: Unable to boot the Buster installer in qemu/libvirt when using the Virtio graphic card has caused the Debian Bug report #941299, regarding

Bug#997188: marked as done (irqbalance: FTBFS: ui/ui.c:28:24: error: format not a string literal and no format arguments [-Werror=format-security])

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 13:35:34 + with message-id and subject line Bug#997188: fixed in irqbalance 1.8.0-1 has caused the Debian Bug report #997188, regarding irqbalance: FTBFS: ui/ui.c:28:24: error: format not a string literal and no format arguments [-Werror=format-security]

Bug#587699: marked as done (installation-reports: can't (install) update grub(2), grub-probe can' find /)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #587699, regarding installation-reports: can't (install) update grub(2), grub-probe can'

Bug#596877: marked as done (The last netinstall iso's don't install grub)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #596877, regarding The last netinstall iso's don't install grub to be marked as done.

Bug#588670: marked as done (installation-reports: generated grub.cfg has off-by-one error in --fs-uuid index in the search command)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #588670, regarding installation-reports: generated grub.cfg has off-by-one error in

Bug#611713: marked as done (installation-reports: Installation issue grub mixup between sata disk and pata disk)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #611713, regarding installation-reports: Installation issue grub mixup between sata disk

Bug#612420: marked as done (installation-reports: Grub install error when installing from USB (Debian Squeeze))

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #612420, regarding installation-reports: Grub install error when installing from USB

Bug#557242: marked as done (debian-installer: current daily squeeze installer installs grub to mbr without asking the user)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #557242, regarding debian-installer: current daily squeeze installer installs grub to mbr

Bug#580461: marked as done (squeeze Alpha1 + GRUB1: Error 23. Error while parsing number)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #580461, regarding squeeze Alpha1 + GRUB1: Error 23. Error while parsing number to be

Bug#549703: marked as done ([i386][lenny] grub guesses wrong location for MBR?)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #549703, regarding [i386][lenny] grub guesses wrong location for MBR? to be marked as

Bug#618498: marked as done (grub-installer: grub-mkconfig does not pick up correct os-prober output when run from installer)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #618498, regarding grub-installer: grub-mkconfig does not pick up correct os-prober

Bug#621923: marked as done (installation-reports: GRUB fails to write when non-RAID disk is present with RAID1 /boot)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #621923, regarding installation-reports: GRUB fails to write when non-RAID disk is

Bug#639713: marked as done (debian-installer: grub-install fails during squeeze install if /boot is on raid and mdadm was not installed)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #639713, regarding debian-installer: grub-install fails during squeeze install if /boot

Bug#610116: marked as done (grub incorrectly installed when specifying empty grub-installer/bootdev)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #610116, regarding grub incorrectly installed when specifying empty

Bug#520361: marked as done (Wrong configuration for GRUB 2 chain-loading Windows)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #520361, regarding Wrong configuration for GRUB 2 chain-loading Windows to be marked as

Bug#544949: marked as done (Package: grub-installer after installation: Unable to install GRUB in (hd0))

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #544949, regarding Package: grub-installer after installation: Unable to install GRUB in

Bug#647267: marked as done (debian-installer: grub-install tries to install on the wrong drive)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #647267, regarding debian-installer: grub-install tries to install on the wrong drive to

Bug#659116: marked as done (debian-installer: GRUB fails to be installed on machine with IDE and SATA disk)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #659116, regarding debian-installer: GRUB fails to be installed on machine with IDE and

Bug#609939: marked as done (base: squeeze beta2 amd64 install fail in Acer3820: grub can't be installed)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #609939, regarding base: squeeze beta2 amd64 install fail in Acer3820: grub can't be

Bug#984042: marked as done (dssp: ftbfs with GCC-11)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:00:13 + with message-id and subject line Bug#984093: fixed in libcifpp 1.0.1-4 has caused the Debian Bug report #984093, regarding dssp: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#984200: marked as done (libpdb-redo: ftbfs with GCC-11)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:00:13 + with message-id and subject line Bug#984093: fixed in libcifpp 1.0.1-4 has caused the Debian Bug report #984093, regarding libpdb-redo: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#974813: marked as done (oclgrind: Please upgrade to llvm-toolchain-11)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:00:15 + with message-id and subject line Bug#974793: fixed in oclgrind 21.10-1 has caused the Debian Bug report #974793, regarding oclgrind: Please upgrade to llvm-toolchain-11 to be marked as done. This means that you claim that the problem has been

Bug#984093: marked as done (libcifpp: ftbfs with GCC-11)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:00:13 + with message-id and subject line Bug#984093: fixed in libcifpp 1.0.1-4 has caused the Debian Bug report #984093, regarding libcifpp: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#993324: marked as done (libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:00:11 + with message-id and subject line Bug#993324: fixed in gsl 2.7+dfsg-3 has caused the Debian Bug report #993324, regarding libgsl25: ABI breakage: removed symbol gsl_linalg_QR_TR_decomp to be marked as done. This means that you claim that the

Bug#987436: marked as done (libcifpp: [INTL:pt_BR] Brazilian Portuguese debconf templates translation)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:00:13 + with message-id and subject line Bug#987436: fixed in libcifpp 1.0.1-4 has caused the Debian Bug report #987436, regarding libcifpp: [INTL:pt_BR] Brazilian Portuguese debconf templates translation to be marked as done. This means that you claim

Bug#994551: marked as done (libcifpp1: please split off static files to separate package)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:00:13 + with message-id and subject line Bug#994551: fixed in libcifpp 1.0.1-4 has caused the Debian Bug report #994551, regarding libcifpp1: please split off static files to separate package to be marked as done. This means that you claim that the

Bug#987666: marked as done ([INTL:es] Spanish translation of the debconf template)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:00:13 + with message-id and subject line Bug#987666: fixed in libcifpp 1.0.1-4 has caused the Debian Bug report #987666, regarding [INTL:es] Spanish translation of the debconf template to be marked as done. This means that you claim that the problem has

Bug#984369: marked as done (tortoize: ftbfs with GCC-11)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:00:13 + with message-id and subject line Bug#984093: fixed in libcifpp 1.0.1-4 has caused the Debian Bug report #984093, regarding tortoize: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed: RFS: rednotebook/2.22+ds-3~bpo11+1 -- Modern desktop diary and personal journaling tool

2021-10-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 998089 Bug #998089 [sponsorship-requests] RFS: rednotebook/2.22+ds-3~bpo11+1 -- Modern desktop diary and personal journaling tool Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 998089:

Bug#898923: marked as done (halibut: doesn't properly handle file starting with an empty line)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 23:48:22 + with message-id and subject line Bug#898923: fixed in halibut 1.3-1 has caused the Debian Bug report #898923, regarding halibut: doesn't properly handle file starting with an empty line to be marked as done. This means that you claim that the

Bug#898928: marked as done (halibut: crashes when generating chm or html (with a non-resolving cross-reference))

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 23:48:22 + with message-id and subject line Bug#898928: fixed in halibut 1.3-1 has caused the Debian Bug report #898928, regarding halibut: crashes when generating chm or html (with a non-resolving cross-reference) to be marked as done. This means that

Bug#997122: marked as done (assembly-stats: FTBFS: fastq_unittest.cpp:53:78: error: taking address of rvalue [-fpermissive])

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 20:33:47 + with message-id and subject line Bug#997122: fixed in assembly-stats 1.0.1+ds-5 has caused the Debian Bug report #997122, regarding assembly-stats: FTBFS: fastq_unittest.cpp:53:78: error: taking address of rvalue [-fpermissive] to be marked as

Bug#997820: marked as done (python3-trezor: Depends: python3-click (< 8) but 8.0.2-1 is to be installed)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sun, 31 Oct 2021 02:35:53 + with message-id and subject line Bug#997820: fixed in python-trezor 0.12.4-1 has caused the Debian Bug report #997820, regarding python3-trezor: Depends: python3-click (< 8) but 8.0.2-1 is to be installed to be marked as done. This means that

Bug#982333: marked as done (libcifpp: [INTL:pt] Portuguese translation - debconf messages)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:00:13 + with message-id and subject line Bug#982333: fixed in libcifpp 1.0.1-4 has caused the Debian Bug report #982333, regarding libcifpp: [INTL:pt] Portuguese translation - debconf messages to be marked as done. This means that you claim that the

Bug#974793: marked as done (oclgrind: Please upgrade to llvm-toolchain-11)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:00:15 + with message-id and subject line Bug#974793: fixed in oclgrind 21.10-1 has caused the Debian Bug report #974793, regarding oclgrind: Please upgrade to llvm-toolchain-11 to be marked as done. This means that you claim that the problem has been

Bug#984995: marked as done (packaging-tutorial: [INTL:pt_BR] Brazilian Portuguese templates translation)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 20:34:56 + with message-id and subject line Bug#984995: fixed in packaging-tutorial 0.28 has caused the Debian Bug report #984995, regarding packaging-tutorial: [INTL:pt_BR] Brazilian Portuguese templates translation to be marked as done. This means that

Bug#984825: marked as done (packaging-tutorial: [INTL:nl] Dutch translation for the packaging-tutorial package's documentation)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 20:34:56 + with message-id and subject line Bug#984825: fixed in packaging-tutorial 0.28 has caused the Debian Bug report #984825, regarding packaging-tutorial: [INTL:nl] Dutch translation for the packaging-tutorial package's documentation to be marked as

Bug#997758: marked as done (nose: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 220))

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 20:34:51 + with message-id and subject line Bug#997758: fixed in nose 1.3.7-8 has caused the Debian Bug report #997758, regarding nose: FTBFS: There is a syntax error in your configuration file: invalid syntax (conf.py, line 220) to be marked as done.

Processed: src:node-toidentifier: fails to migrate to testing for too long: uploader built arch:all binaries

2021-10-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.0.0-4 Bug #998136 [src:node-toidentifier] src:node-toidentifier: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions node-toidentifier/1.0.0-4. Bug #998136 [src:node-toidentifier] src:node-toidentifier:

Bug#981881: marked as done (packaging-tutorial: [INTL:nl] Dutch po file for the packaging-tutorial package's documentation)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 20:34:56 + with message-id and subject line Bug#981881: fixed in packaging-tutorial 0.28 has caused the Debian Bug report #981881, regarding packaging-tutorial: [INTL:nl] Dutch po file for the packaging-tutorial package's documentation to be marked as

Bug#983571: marked as done (packaging-tutorial: [INTL:pt] Update on Portuguese translation of MANPAGE)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 20:34:56 + with message-id and subject line Bug#983571: fixed in packaging-tutorial 0.28 has caused the Debian Bug report #983571, regarding packaging-tutorial: [INTL:pt] Update on Portuguese translation of MANPAGE to be marked as done. This means that

Processed: src:node-xdg-basedir: fails to migrate to testing for too long: uploader built arch:all binaries

2021-10-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.0.0-2 Bug #998135 [src:node-xdg-basedir] src:node-xdg-basedir: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions node-xdg-basedir/3.0.0-2. Bug #998135 [src:node-xdg-basedir] src:node-xdg-basedir: fails

Bug#997471: marked as done (loguru: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 21:06:42 + with message-id and subject line Bug#997471: fixed in loguru 0.5.3-4 has caused the Debian Bug report #997471, regarding loguru: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 to be

Processed: src:node-yamlish: fails to migrate to testing for too long: uploader built arch:all binaries

2021-10-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.0.7-3 Bug #998131 [src:node-yamlish] src:node-yamlish: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions node-yamlish/0.0.7-3. Bug #998131 [src:node-yamlish] src:node-yamlish: fails to migrate to

Processed: src:python-parameterized: fails to migrate to testing for too long: autopkgtest regression

2021-10-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.8.1-1 Bug #998137 [src:python-parameterized] src:python-parameterized: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions python-parameterized/0.8.1-1. Bug #998137 [src:python-parameterized]

Processed: src:browser-request: fails to migrate to testing for too long: uploader built arch:all binaries

2021-10-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.3.3-4 Bug #998139 [src:browser-request] src:browser-request: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions browser-request/0.3.3-4. Bug #998139 [src:browser-request] src:browser-request: fails to

Processed: src:rust-utf-8: fails to migrate to testing for too long: autopkgtest regression

2021-10-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.7.6-1 Bug #998138 [src:rust-utf-8] src:rust-utf-8: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions rust-utf-8/0.7.6-1. Bug #998138 [src:rust-utf-8] src:rust-utf-8: fails to migrate to testing for too long:

Processed: RFS: ghostwriter/2.0.2-2 -- Distraction-free, themeable Markdown editor

2021-10-30 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 998127 Bug #998127 [sponsorship-requests] RFS: ghostwriter/2.0.2-2 -- Distraction-free, themeable Markdown editor Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 998127:

Bug#984279: marked as done (openzwave: ftbfs with GCC-11)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 21:49:42 + with message-id and subject line Bug#984279: fixed in openzwave 1.6.1914+ds-1 has caused the Debian Bug report #984279, regarding openzwave: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#998115: marked as done (lintian: false positive: "unknown-field Description" in source package)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 21:17:36 -0700 with message-id and subject line Re: Bug#998115: lintian: false positive: "unknown-field Description" in source package has caused the Debian Bug report #998115, regarding lintian: false positive: "unknown-field Description" in source package

Bug#995123: marked as done (cyrus-sasl2 FTBFS: sphinx: AttributeError: 'CyrusManualPageBuilder' object has no attribute 'settings')

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 21:33:31 + with message-id and subject line Bug#995123: fixed in cyrus-sasl2 2.1.27+dfsg-2.2 has caused the Debian Bug report #995123, regarding cyrus-sasl2 FTBFS: sphinx: AttributeError: 'CyrusManualPageBuilder' object has no attribute 'settings' to be

Bug#902814: marked as done (input-pad: Please package new version and switch upstream project)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sun, 31 Oct 2021 00:19:00 + with message-id and subject line Bug#902814: fixed in input-pad 1.0.99.20210817-1 has caused the Debian Bug report #902814, regarding input-pad: Please package new version and switch upstream project to be marked as done. This means that you

Bug#997461: marked as done (target-factory: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sun, 31 Oct 2021 00:19:09 + with message-id and subject line Bug#997461: fixed in target-factory 1.4-2 has caused the Debian Bug report #997461, regarding target-factory: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff

Bug#955650: marked as done (python-tablib: FTBFS: E NotImplementedError: DataFrame Format requires `pandas` to be installed. Try `pip install tablib[pandas]`.)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sun, 31 Oct 2021 06:42:30 +0100 with message-id and subject line Re: Bug#955650: python-tablib: FTBFS: E NotImplementedError: DataFrame Format requires `pandas` to be installed. Try `pip install tablib[pandas]`. has caused the Debian Bug report #955650, regarding

Bug#990722: marked as done (RFS: cool-retro-term/1.1.1+git20210605-1 -- terminal emulator which mimics old screens)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 10:17:22 +0200 with message-id <93a29e89-dc75-a29c-9129-1c34b1cfa...@debian.org> and subject line Re: RFS: cool-retro-term/1.1.1+git20210605-1 -- terminal emulator which mimics old screens has caused the Debian Bug report #990722, regarding RFS:

Bug#995317: marked as done (apertium broken on s390x due to missing endianness definition)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 12:03:35 + with message-id and subject line Bug#995317: fixed in apertium 3.7.2-1 has caused the Debian Bug report #995317, regarding apertium broken on s390x due to missing endianness definition to be marked as done. This means that you claim that the

Bug#995805: marked as done (nx-libs: Add riscv64 support)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 12:03:56 + with message-id and subject line Bug#995805: fixed in nx-libs 2:3.5.99.26-5 has caused the Debian Bug report #995805, regarding nx-libs: Add riscv64 support to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#997233: marked as done (loudgain: FTBFS: ld: cannot find -lz)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 12:03:50 + with message-id and subject line Bug#997233: fixed in loudgain 0.6.8+ds-2 has caused the Debian Bug report #997233, regarding loudgain: FTBFS: ld: cannot find -lz to be marked as done. This means that you claim that the problem has been dealt

Processed: src:rust-bumpalo: fails to migrate to testing for too long: autopkgtest regression

2021-10-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.7.0-2 Bug #998111 [src:rust-bumpalo] src:rust-bumpalo: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions rust-bumpalo/3.7.0-2. Bug #998111 [src:rust-bumpalo] src:rust-bumpalo: fails to migrate to testing for

Processed: src:reqwest: fails to migrate to testing for too long: upload built arch:all binaries

2021-10-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.6.0-3 Bug #998112 [src:reqwest] src:reqwest: fails to migrate to testing for too long: upload built arch:all binaries Marked as fixed in versions reqwest/0.6.0-3. Bug #998112 [src:reqwest] src:reqwest: fails to migrate to testing for too long: upload

Bug#913159: marked as done (task-kannada-desktop: uninstallable on mips and mipsel)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:14:21 +0200 with message-id <20211030181421.dca8b82f05e51092b9950...@mailbox.org> and subject line Re: Bug#913159: task-kannada-desktop: uninstallable on mips and mipsel has caused the Debian Bug report #913159, regarding task-kannada-desktop: uninstallable

Bug#997502: marked as done (pyresample: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 09:48:40 + with message-id and subject line Bug#997502: fixed in pyresample 1.22.0-1 has caused the Debian Bug report #997502, regarding pyresample: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.9 returned exit code 13 to

Bug#997119: marked as done (symfony: FTBFS: tests failed variable (T_VARIABLE))

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 14:50:32 + with message-id and subject line Bug#997119: fixed in php-psr-link 1.1.0+really1.0.0-1 has caused the Debian Bug report #997119, regarding symfony: FTBFS: tests failed variable (T_VARIABLE) to be marked as done. This means that you claim that

Bug#500079: marked as done (Missing root option for other detected Linux OS on dmraid)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #500079, regarding Missing root option for other detected Linux OS on dmraid to be marked

Bug#516392: marked as done (debian-installer: unbootable system after install)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #516392, regarding debian-installer: unbootable system after install to be marked as done.

Bug#292513: marked as done (debian-installer: grub doesn't update mbr on both disk)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #292513, regarding debian-installer: grub doesn't update mbr on both disk to be marked as

Bug#255116: marked as done (grub: fails to mark partition active)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #229128, regarding grub: fails to mark partition active to be marked as done. This means

Bug#229128: marked as done (Problems installin to something else than MBR)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #229128, regarding Problems installin to something else than MBR to be marked as done.

Bug#252009: marked as done (LILO/GRUB problems when root is on RAID1)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #292513, regarding LILO/GRUB problems when root is on RAID1 to be marked as done. This

Bug#310798: marked as done (grub and software raid)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #292513, regarding grub and software raid to be marked as done. This means that you claim

Bug#391489: marked as done (grub-installer: Raid 1 /boot installations.)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #292513, regarding grub-installer: Raid 1 /boot installations. to be marked as done. This

Bug#463842: marked as done (mention highpoint/grub conflict in D-I errata)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #463842, regarding mention highpoint/grub conflict in D-I errata to be marked as done.

Bug#578338: marked as done (debian-installer: grub-install fails to md0)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #292513, regarding debian-installer: grub-install fails to md0 to be marked as done. This

Bug#489006: marked as done (debian-installer: After grub software raid installation, machine fails to boot with first drive removed or blanked.)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #292513, regarding debian-installer: After grub software raid installation, machine fails

Bug#582367: marked as done (installation-report: Unable to install grub-pc on LVM/RAID5)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #292513, regarding installation-report: Unable to install grub-pc on LVM/RAID5 to be

Bug#416986: marked as done (raise timeout when other OS is detected)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #416986, regarding raise timeout when other OS is detected to be marked as done. This

Bug#489005: marked as done (debian-installer: Grub unconditionally set to use serial console when an install takes place via the serial port.)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #489005, regarding debian-installer: Grub unconditionally set to use serial console when

Bug#497168: marked as done (grub-installer cant change grub settings)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #497168, regarding grub-installer cant change grub settings to be marked as done. This

Bug#498831: marked as done (grub-installer: fails the first time on Asus P55T2P4 motherboard)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #498831, regarding grub-installer: fails the first time on Asus P55T2P4 motherboard to be

Bug#998096: marked as done (RFS: pelican/4.7.1+dfsg-1.1 [NMU] -- blog aware, static website generator)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 13:09:47 +0200 with message-id <0fb3e4a4-3b29-ff71-5c97-5958dfce8...@gmx.de> and subject line Re: RFS: pelican/4.6.0+dfsg-1.1 [NMU] -- blog aware, static website generator has caused the Debian Bug report #998096, regarding RFS: pelican/4.7.1+dfsg-1.1 [NMU] --

Bug#998103: marked as done (RFS: loudgain/0.6.8+ds-2 [RC] -- ReplayGain 2.0 loudness normalizer)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 13:40:36 +0200 with message-id <1af7c55e-fe1d-f9e3-b79e-2ceb62823...@debian.org> and subject line Re: RFS: loudgain/0.6.8+ds-2 [RC] -- ReplayGain 2.0 loudness normalizer has caused the Debian Bug report #998103, regarding RFS: loudgain/0.6.8+ds-2 [RC] --

Bug#998062: marked as done (Allow using dbus-broker if the user installed it)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 15:33:34 + with message-id and subject line Bug#998062: fixed in at-spi2-core 2.42.0-2 has caused the Debian Bug report #998062, regarding Allow using dbus-broker if the user installed it to be marked as done. This means that you claim that the problem has

Bug#997186: marked as done (nast: FTBFS: ncurses/n_nast.c:686:46: error: format not a string literal and no format arguments [-Werror=format-security])

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 09:03:29 + with message-id and subject line Bug#997186: fixed in nast 0.2.0-9 has caused the Debian Bug report #997186, regarding nast: FTBFS: ncurses/n_nast.c:686:46: error: format not a string literal and no format arguments [-Werror=format-security] to

Bug#970964: marked as done (pymupdf: autopkgtest must be marked superficial)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 10:03:33 + with message-id and subject line Bug#970964: fixed in pymupdf 1.19.1+ds1-1 has caused the Debian Bug report #970964, regarding pymupdf: autopkgtest must be marked superficial to be marked as done. This means that you claim that the problem has

Processed: src:osmnx: fails to migrate to testing for too long: autopkgtest regression

2021-10-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.1.1+ds-4 Bug #998113 [src:osmnx] src:osmnx: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions osmnx/1.1.1+ds-4. Bug #998113 [src:osmnx] src:osmnx: fails to migrate to testing for too long: autopkgtest

Processed: src:simile-timeline: fails to migrate to testing for too long: uploader built arch:all binaries

2021-10-30 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.3.0+dfsg1-6 Bug #998107 [src:simile-timeline] src:simile-timeline: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions simile-timeline/2.3.0+dfsg1-6. Bug #998107 [src:simile-timeline]

Bug#806849: marked as done (debian-installer: d-i fails to install grub2 correctly for efi system using encrypted LVM)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #806164, regarding debian-installer: d-i fails to install grub2 correctly for efi system

Bug#806164: marked as done (grub-installer: too much hardcoding of device names, fails with /dev/nvme*)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #806164, regarding grub-installer: too much hardcoding of device names, fails with

Bug#690592: marked as done (installation-reports: Grub video mode incorrect after efi installation)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #690592, regarding installation-reports: Grub video mode incorrect after efi installation

Bug#699456: marked as done (cdimage.debian.org: grub fails to install if HD is not /dev/sda)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #699456, regarding cdimage.debian.org: grub fails to install if HD is not /dev/sda to be

Bug#702731: marked as done (/usr/lib/grub/i386-pc/grub-install: grub-install always tries to write to sda)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #702731, regarding /usr/lib/grub/i386-pc/grub-install: grub-install always tries to write

Bug#703901: marked as done (debian-installer: GRUB should allow detailed configure for MD RAID)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #703901, regarding debian-installer: GRUB should allow detailed configure for MD RAID to

Bug#707604: marked as done (debian-installer: Should warn if disk with GPT doesn't contain bios-grub partition)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #707604, regarding debian-installer: Should warn if disk with GPT doesn't contain

Bug#711330: marked as done (grub-installer: grub-install.postinst stuck while 20microsoft tries to probe a windows 7 on second disk (KVM))

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #711330, regarding grub-installer: grub-install.postinst stuck while 20microsoft tries to

Bug#729411: marked as done (grub-pc: attempts to install to mmcblk0 rather than sda)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #729411, regarding grub-pc: attempts to install to mmcblk0 rather than sda to be marked as

Bug#771467: marked as done (First boot after installation fails on Macbooks with 32-bit EFI)

2021-10-30 Thread Debian Bug Tracking System
Your message dated Sat, 30 Oct 2021 18:30:54 +0200 with message-id <20211030183054.906cb9aac22395d0f32a6...@mailbox.org> and subject line Mass-closing old grub-installer bugs has caused the Debian Bug report #771467, regarding First boot after installation fails on Macbooks with 32-bit EFI to be

  1   2   >