Bug#942702: marked as done (bs1770gain --help misspells --suppress-progress)

Your message dated Sat, 18 Sep 2021 06:33:32 + with message-id and subject line Bug#942702: fixed in bs1770gain 0.8.3-1 has caused the Debian Bug report #942702, regarding bs1770gain --help misspells --suppress-progress to be marked as done. This means that you claim that the problem has been

Bug#993202: marked as done (gnome-shell-extension-weather: does not declare compatibility with GNOME Shell 40)

Your message dated Sat, 18 Sep 2021 06:18:37 + with message-id and subject line Bug#993202: fixed in gnome-shell-extension-weather 0.0~git20210509.d714eb1-1 has caused the Debian Bug report #993202, regarding gnome-shell-extension-weather: does not declare compatibility with GNOME Shell 40 t

Bug#983222: marked as done (python-cartopy: FTBFS with PROJ 8.0.0)

Your message dated Sat, 18 Sep 2021 06:18:58 + with message-id and subject line Bug#983222: fixed in python-cartopy 0.20.0+dfsg-1~exp1 has caused the Debian Bug report #983222, regarding python-cartopy: FTBFS with PROJ 8.0.0 to be marked as done. This means that you claim that the problem has

Bug#990907: marked as done (gnome-shell-extension-weather: Homepage in debian/control points to defunct location)

Your message dated Sat, 18 Sep 2021 06:18:37 + with message-id and subject line Bug#990907: fixed in gnome-shell-extension-weather 0.0~git20210509.d714eb1-1 has caused the Debian Bug report #990907, regarding gnome-shell-extension-weather: Homepage in debian/control points to defunct locatio

Bug#990418: marked as done (SSL handshake failed when loading openweathermap data)

Your message dated Sat, 18 Sep 2021 06:18:37 + with message-id and subject line Bug#990418: fixed in gnome-shell-extension-weather 0.0~git20210509.d714eb1-1 has caused the Debian Bug report #990418, regarding SSL handshake failed when loading openweathermap data to be marked as done. This me

Bug#950897: marked as done (gopher FTCBFS: does not pass --host to ./configure)

Your message dated Sat, 18 Sep 2021 06:18:50 + with message-id and subject line Bug#950897: fixed in gopher 3.0.17.3+nmu1 has caused the Debian Bug report #950897, regarding gopher FTCBFS: does not pass --host to ./configure to be marked as done. This means that you claim that the problem has

Bug#978822: marked as done (gopher: ftbfs with autoconf 2.70)

Your message dated Sat, 18 Sep 2021 06:18:50 + with message-id and subject line Bug#978822: fixed in gopher 3.0.17.3+nmu1 has caused the Debian Bug report #978822, regarding gopher: ftbfs with autoconf 2.70 to be marked as done. This means that you claim that the problem has been dealt with.

Processed: closing 994585

Processing commands for cont...@bugs.debian.org: > close 994585 Bug #994585 [release.debian.org] nmu: ricochet-im_1.1.4-3+b5 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 994585: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994585 Debian

Bug#994256: marked as done (django-axes: autopkgtest needs update for new version of python-django: warnings changed)

Your message dated Sat, 18 Sep 2021 03:18:43 + with message-id and subject line Bug#994256: fixed in django-axes 5.24.0-1 has caused the Debian Bug report #994256, regarding django-axes: autopkgtest needs update for new version of python-django: warnings changed to be marked as done. This me

Bug#956354: marked as done (libuser: Please stop using deprecated and headers)

Your message dated Sat, 18 Sep 2021 02:35:12 + with message-id and subject line Bug#956354: fixed in libuser 1:0.63~dfsg-1 has caused the Debian Bug report #956354, regarding libuser: Please stop using deprecated and headers to be marked as done. This means that you claim that the problem

Bug#984732: marked as done (libuser: Please package new upstream release (0.63))

Your message dated Sat, 18 Sep 2021 02:35:12 + with message-id and subject line Bug#984732: fixed in libuser 1:0.63~dfsg-1 has caused the Debian Bug report #984732, regarding libuser: Please package new upstream release (0.63) to be marked as done. This means that you claim that the problem h

Bug#992922: marked as done (gpgme1.0 FTBFS on 32bit: segfault during tests)

Your message dated Sat, 18 Sep 2021 01:33:53 + with message-id and subject line Bug#992922: fixed in gpgme1.0 1.16.0-1.1 has caused the Debian Bug report #992922, regarding gpgme1.0 FTBFS on 32bit: segfault during tests to be marked as done. This means that you claim that the problem has been

Bug#994543: marked as done (Workaround glibc bug BZ#26401 (regression in lchmod and fchmodat when /proc is not mounted))

Your message dated Fri, 17 Sep 2021 23:48:42 + with message-id and subject line Bug#994543: fixed in rsync 3.2.3-7 has caused the Debian Bug report #994543, regarding Workaround glibc bug BZ#26401 (regression in lchmod and fchmodat when /proc is not mounted) to be marked as done. This means

Bug#970680: marked as done (vim/indent|syntax/cmake.vim)

Your message dated Sat, 18 Sep 2021 01:01:02 +0200 with message-id <20210917230102.yc3us7dnmvmk6...@mail.gaussglocke.de> and subject line Re: vim/indent|syntax/cmake.vim has caused the Debian Bug report #970680, regarding vim/indent|syntax/cmake.vim to be marked as done. This means that you claim

Bug#994389: marked as done (openimageio: building against OpenVDB 8 silently drops OpenVDB aupport)

Your message dated Fri, 17 Sep 2021 23:04:45 + with message-id and subject line Bug#994389: fixed in openimageio 2.2.18.0+dfsg-1 has caused the Debian Bug report #994389, regarding openimageio: building against OpenVDB 8 silently drops OpenVDB aupport to be marked as done. This means that you

Bug#948505: marked as done (devhelp: GTKMM 3.0 doc not working on devhelp)

Your message dated Fri, 17 Sep 2021 18:55:02 -0400 with message-id and subject line Re: devhelp: GTKMM 3.0 doc not working on devhelp has caused the Debian Bug report #948505, regarding devhelp: GTKMM 3.0 doc not working on devhelp to be marked as done. This means that you claim that the problem

Bug#722279: marked as done (devhelp: Error accessing gtkmm-3.0 reference manual)

Your message dated Fri, 17 Sep 2021 18:55:02 -0400 with message-id and subject line Re: devhelp: GTKMM 3.0 doc not working on devhelp has caused the Debian Bug report #948505, regarding devhelp: Error accessing gtkmm-3.0 reference manual to be marked as done. This means that you claim that the p

Bug#935852: marked as done (linux-image-5.2.0-2-amd64: Heavy static noise on headphone jack snd_hda_intel)

Your message dated Fri, 17 Sep 2021 14:42:53 -0700 (PDT) with message-id <61450bdd.1c69fb81.55c71.5...@mx.google.com> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #935852, regarding linux-image-5.2.0-2-amd64: Heavy static noise on headphone

Bug#984733: marked as done (ITS: libuser)

Your message dated Fri, 17 Sep 2021 19:34:20 + with message-id and subject line Bug#984733: fixed in libuser 1:0.62~dfsg-1 has caused the Debian Bug report #984733, regarding ITS: libuser to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#918049: marked as done (psi: main window is empty when restored after being hidden)

Your message dated Fri, 17 Sep 2021 21:57:37 +0300 with message-id <219011631905...@mail.yandex.ru> and subject line Re: psi: main window is empty when restored after being hidden has caused the Debian Bug report #918049, regarding psi: main window is empty when restored after being hidden to be ma

Bug#994524: marked as done (pycurl accesses the internet during the build)

Your message dated Fri, 17 Sep 2021 18:33:34 + with message-id and subject line Bug#994524: fixed in pycurl 7.44.1-3 has caused the Debian Bug report #994524, regarding pycurl accesses the internet during the build to be marked as done. This means that you claim that the problem has been deal

Bug#986208: marked as done (wireless-regdb: Please update wireless-regdb to 2020-11-20)

Your message dated Fri, 17 Sep 2021 17:33:50 + with message-id and subject line Bug#986208: fixed in wireless-regdb 2021.08.28-1 has caused the Debian Bug report #986208, regarding wireless-regdb: Please update wireless-regdb to 2020-11-20 to be marked as done. This means that you claim that

Bug#992207: marked as done (Freeradius postgresql mod broken in Bullseye)

Your message dated Fri, 17 Sep 2021 17:32:08 + with message-id and subject line Bug#992207: fixed in freeradius 3.0.21+dfsg-2.2+deb11u1 has caused the Debian Bug report #992207, regarding Freeradius postgresql mod broken in Bullseye to be marked as done. This means that you claim that the pro

Bug#992036: marked as done (freeradius 3.0.x crashes with "attempting double-free")

Your message dated Fri, 17 Sep 2021 17:32:08 + with message-id and subject line Bug#992036: fixed in freeradius 3.0.21+dfsg-2.2+deb11u1 has caused the Debian Bug report #992036, regarding freeradius 3.0.x crashes with "attempting double-free" to be marked as done. This means that you claim th

Bug#994474: marked as done (please update recommends on openblas)

Your message dated Fri, 17 Sep 2021 16:48:27 + with message-id and subject line Bug#994474: fixed in altree 1.3.2-1 has caused the Debian Bug report #994474, regarding please update recommends on openblas to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#968935: marked as done (Syntax warnings printed to stdout when importing python3-xlsxwriter in Python 3.8.5...)

Your message dated Fri, 17 Sep 2021 16:03:43 + with message-id and subject line Bug#976862: fixed in xlsxwriter 3.0.1-1 has caused the Debian Bug report #976862, regarding Syntax warnings printed to stdout when importing python3-xlsxwriter in Python 3.8.5... to be marked as done. This means

Bug#976862: marked as done (python3-plaso: log2timeline.py and image_export.py throw many Python 3.9 SyntaxWarnings)

Your message dated Fri, 17 Sep 2021 16:03:43 + with message-id and subject line Bug#976862: fixed in xlsxwriter 3.0.1-1 has caused the Debian Bug report #976862, regarding python3-plaso: log2timeline.py and image_export.py throw many Python 3.9 SyntaxWarnings to be marked as done. This means

Bug#976862: marked as done (python3-plaso: log2timeline.py and image_export.py throw many Python 3.9 SyntaxWarnings)

Your message dated Fri, 17 Sep 2021 16:03:43 + with message-id and subject line Bug#968935: fixed in xlsxwriter 3.0.1-1 has caused the Debian Bug report #968935, regarding python3-plaso: log2timeline.py and image_export.py throw many Python 3.9 SyntaxWarnings to be marked as done. This means

Bug#968935: marked as done (Syntax warnings printed to stdout when importing python3-xlsxwriter in Python 3.8.5...)

Your message dated Fri, 17 Sep 2021 16:03:43 + with message-id and subject line Bug#968935: fixed in xlsxwriter 3.0.1-1 has caused the Debian Bug report #968935, regarding Syntax warnings printed to stdout when importing python3-xlsxwriter in Python 3.8.5... to be marked as done. This means

Bug#966164: marked as done (python3-xlsxwriter: Homepage URL is not working.)

Your message dated Fri, 17 Sep 2021 16:03:43 + with message-id and subject line Bug#966164: fixed in xlsxwriter 3.0.1-1 has caused the Debian Bug report #966164, regarding python3-xlsxwriter: Homepage URL is not working. to be marked as done. This means that you claim that the problem has bee

Bug#989769: marked as done (libstatgen FTCBFS: debian/rules uses the build architecture compiler as a make default)

Your message dated Fri, 17 Sep 2021 15:34:22 + with message-id and subject line Bug#989769: fixed in libstatgen 1.0.15-1 has caused the Debian Bug report #989769, regarding libstatgen FTCBFS: debian/rules uses the build architecture compiler as a make default to be marked as done. This means

Bug#993843: marked as done (zsh-static segfaults immediately)

Your message dated Fri, 17 Sep 2021 15:19:33 + with message-id and subject line Bug#993843: fixed in zsh 5.8-10 has caused the Debian Bug report #993843, regarding zsh-static segfaults immediately to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#978913: marked as done (uisp: ftbfs with autoconf 2.70)

Your message dated Fri, 17 Sep 2021 15:19:23 + with message-id and subject line Bug#978913: fixed in uisp 20050207-4.4 has caused the Debian Bug report #978913, regarding uisp: ftbfs with autoconf 2.70 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#965856: marked as done (uisp: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Fri, 17 Sep 2021 15:19:23 + with message-id and subject line Bug#965856: fixed in uisp 20050207-4.4 has caused the Debian Bug report #965856, regarding uisp: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the pr

Bug#529148: marked as done (uisp: please upgrade your watch file)

Your message dated Fri, 17 Sep 2021 15:19:23 + with message-id and subject line Bug#529148: fixed in uisp 20050207-4.4 has caused the Debian Bug report #529148, regarding uisp: please upgrade your watch file to be marked as done. This means that you claim that the problem has been dealt with.

Bug#984363: marked as done (therion: ftbfs with GCC-11)

Your message dated Fri, 17 Sep 2021 14:37:43 + with message-id and subject line Bug#984363: fixed in therion 6.0.2ds1-1 has caused the Debian Bug report #984363, regarding therion: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Processed (with 1 error): closing 988219

Processing commands for cont...@bugs.debian.org: > Version: 0.59.1-1 Unknown command or malformed arguments to command. > close 988219 Bug #988219 [meson] meson: Move package into unstable Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. --

Processed: closing 951191

Processing commands for cont...@bugs.debian.org: > close 951191 2.32-3 Bug #951191 [src:glibc] Backport /proc-based lchmod/fchmodat emulation Marked as fixed in versions glibc/2.32-3. Bug #951191 [src:glibc] Backport /proc-based lchmod/fchmodat emulation Marked Bug as done > thanks Stopping proces

Bug#993511: marked as done (spdlog: FTBFS with glibc 2.34)

Your message dated Fri, 17 Sep 2021 13:20:13 + with message-id and subject line Bug#993511: fixed in spdlog 1:1.8.5+ds-3 has caused the Debian Bug report #993511, regarding spdlog: FTBFS with glibc 2.34 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#989021: marked as done (rxvt-unicode: new usptream version available: 9.26)

Your message dated Fri, 17 Sep 2021 09:11:25 -0400 with message-id <20210917131125.kxw25yocq5gwo...@zeta.rak.ac> and subject line Re: Bug#989021: rxvt-unicode: new usptream version available: 9.26 has caused the Debian Bug report #989021, regarding rxvt-unicode: new usptream version available: 9.2

Bug#994475: marked as done (wannier90 autopkgtest needs to be adapted for lapack 3.10)

Your message dated Fri, 17 Sep 2021 12:35:37 + with message-id and subject line Bug#994475: fixed in wannier90 3.1.0+ds-5 has caused the Debian Bug report #994475, regarding wannier90 autopkgtest needs to be adapted for lapack 3.10 to be marked as done. This means that you claim that the prob

Bug#994522: marked as done (crash in rendering strikethroughs)

Your message dated Fri, 17 Sep 2021 11:05:19 + with message-id and subject line Bug#994522: fixed in pango1.0 1.48.10+ds1-1 has caused the Debian Bug report #994522, regarding crash in rendering strikethroughs to be marked as done. This means that you claim that the problem has been dealt wit

Bug#677824: marked as done (cmake-data: fails to find libgtest; libgtest-dev package no longer distributes statically compiled libraries)

Your message dated Fri, 17 Sep 2021 12:51:13 +0200 with message-id <20210917105113.2652775lpofoz...@mail.gaussglocke.de> and subject line Re: cmake-data: fails to find libgtest; libgtest-dev package no longer distributes statically compiled libraries has caused the Debian Bug report #677824, regar

Processed: your mail

Processing commands for cont...@bugs.debian.org: > close #994526 Bug #994526 {Done: 4epteh...@list.ru} [celluloid] celluloid: Request new 0.21 upstream version Bug 994526 is already marked as done; not doing anything. > End of message, stopping processing here. Please contact me if you need assi

Bug#994526: marked as done (celluloid: Request new 0.21 upstream version)

Your message dated Fri, 17 Sep 2021 13:34:17 +0300 with message-id <1631874857.696365...@f126.i.mail.ru> and subject line has caused the Debian Bug report #994526, regarding celluloid: Request new 0.21 upstream version to be marked as done. This means that you claim that the problem has been deal

Bug#984351: marked as done (squid: ftbfs with GCC-11)

Your message dated Fri, 17 Sep 2021 10:22:17 + with message-id and subject line Bug#984351: fixed in squid 5.1-2 has caused the Debian Bug report #984351, regarding squid: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not th

Bug#944442: marked as done (squid: Crashes when listening to audio stream over the Squid proxy)

Your message dated Fri, 17 Sep 2021 10:22:17 + with message-id and subject line Bug#943692: fixed in squid 5.1-2 has caused the Debian Bug report #943692, regarding squid: Crashes when listening to audio stream over the Squid proxy to be marked as done. This means that you claim that the prob

Bug#970025: marked as done (squid: configuration reads *~ files from /etc/squid/conf.d)

Your message dated Fri, 17 Sep 2021 10:22:17 + with message-id and subject line Bug#970025: fixed in squid 5.1-2 has caused the Debian Bug report #970025, regarding squid: configuration reads *~ files from /etc/squid/conf.d to be marked as done. This means that you claim that the problem has

Bug#943692: marked as done (squid: crash on bug #4823 : assertion failed: stmem.cc:98: "lowestOffset () <= target_offset")

Your message dated Fri, 17 Sep 2021 10:22:17 + with message-id and subject line Bug#943692: fixed in squid 5.1-2 has caused the Debian Bug report #943692, regarding squid: crash on bug #4823 : assertion failed: stmem.cc:98: "lowestOffset () <= target_offset" to be marked as done. This means

Bug#993372: marked as done (atomicparsley: CVE-2021-37231 - stack-buffer overflow in APar_readX in src/extract.cpp)

Your message dated Fri, 17 Sep 2021 09:34:13 + with message-id and subject line Bug#993372: fixed in atomicparsley 20210715.151551.e7ad03a-1 has caused the Debian Bug report #993372, regarding atomicparsley: CVE-2021-37231 - stack-buffer overflow in APar_readX in src/extract.cpp to be marked

Bug#993366: marked as done (atomicparsley: CVE-2021-37232 - stack overflow in APar_read64 in src/extract.cpp)

Your message dated Fri, 17 Sep 2021 09:34:13 + with message-id and subject line Bug#993366: fixed in atomicparsley 20210715.151551.e7ad03a-1 has caused the Debian Bug report #993366, regarding atomicparsley: CVE-2021-37232 - stack overflow in APar_read64 in src/extract.cpp to be marked as don

Bug#987034: marked as done (display github page in Homepage tag)

Your message dated Fri, 17 Sep 2021 09:34:13 + with message-id and subject line Bug#987034: fixed in atomicparsley 20210715.151551.e7ad03a-1 has caused the Debian Bug report #987034, regarding display github page in Homepage tag to be marked as done. This means that you claim that the problem

Bug#782187: marked as done (atomicparsley build on kFreeBSD)

Your message dated Fri, 17 Sep 2021 09:34:13 + with message-id and subject line Bug#782187: fixed in atomicparsley 20210715.151551.e7ad03a-1 has caused the Debian Bug report #782187, regarding atomicparsley build on kFreeBSD to be marked as done. This means that you claim that the problem has

Bug#994525: marked as done (rubberband FTBFS on armel: selected processor does not support `fmrx r3,fpscr' in ARM mode)

Your message dated Fri, 17 Sep 2021 09:12:00 + with message-id and subject line Bug#994525: fixed in rubberband 1.9.2-3 has caused the Debian Bug report #994525, regarding rubberband FTBFS on armel: selected processor does not support `fmrx r3,fpscr' in ARM mode to be marked as done. This me

Bug#888096: marked as done (archive.debian.org: add wheezy to archive.d.o)

Your message dated Fri, 17 Sep 2021 11:10:26 +0200 with message-id and subject line Re: Bug#888096: archive.debian.org: add wheezy to archive.d.o has caused the Debian Bug report #888096, regarding archive.debian.org: add wheezy to archive.d.o to be marked as done. This means that you claim that

Bug#980859: marked as done (sylpheed: Hang when displaying specific message)

Your message dated Fri, 17 Sep 2021 09:26:33 +0200 with message-id and subject line Re: Bug #980859 has caused the Debian Bug report #980859, regarding sylpheed: Hang when displaying specific message to be marked as done. This means that you claim that the problem has been dealt with. If this is