Bug#1071866: marked as done (goldencheetah: unused build-dependency on libgcrypt20-dev)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sun, 26 May 2024 06:04:44 + with message-id and subject line Bug#1071866: fixed in goldencheetah 1:3.5-5 has caused the Debian Bug report #1071866, regarding goldencheetah: unused build-dependency on libgcrypt20-dev to be marked as done. This means that you claim that the p

Bug#1071867: marked as done (gogglesmm: unused build-dependency on libgcrypt20-dev)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sun, 26 May 2024 06:49:09 +0200 with message-id and subject line Re: Bug#1071867: gogglesmm: unused build-dependency on libgcrypt20-dev has caused the Debian Bug report #1071867, regarding gogglesmm: unused build-dependency on libgcrypt20-dev to be marked as done. This means t

Bug#997379: marked as done (ripe-atlas-tools: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet')

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 23:46:14 + with message-id and subject line Bug#997379: fixed in ripe-atlas-tools 2.3.0-3 has caused the Debian Bug report #997379, regarding ripe-atlas-tools: FTBFS: AttributeError: 'Sphinx' object has no attribute 'add_stylesheet' to be marked as done. T

Bug#1018481: marked as done (python-djvulibre: build-depends on python3-nose or uses it for autopkgtest)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 23:42:45 + with message-id and subject line Bug#1018481: fixed in python-djvulibre 0.9.0-4 has caused the Debian Bug report #1018481, regarding python-djvulibre: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that

Bug#1065925: marked as done (python-djvulibre: Please drop dependencies on python3-distutils)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 23:42:46 + with message-id and subject line Bug#1065925: fixed in python-djvulibre 0.9.0-4 has caused the Debian Bug report #1065925, regarding python-djvulibre: Please drop dependencies on python3-distutils to be marked as done. This means that you claim t

Bug#1070270: marked as done (riseup-vpn: client no longer works due to cert verification problem)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 22:17:10 + with message-id and subject line Bug#1070270: fixed in riseup-vpn 0.21.11+ds1-5+deb12u1 has caused the Debian Bug report #1070270, regarding riseup-vpn: client no longer works due to cert verification problem to be marked as done. This means that

Bug#1070851: marked as done (glib2.0: minor memory leak after fixing CVE-2024-34397)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 22:17:09 + with message-id and subject line Bug#1070851: fixed in glib2.0 2.74.6-2+deb12u3 has caused the Debian Bug report #1070851, regarding glib2.0: minor memory leak after fixing CVE-2024-34397 to be marked as done. This means that you claim that the p

Bug#1068821: marked as done (qemu: CVE-2024-3447)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 22:17:10 + with message-id and subject line Bug#1068821: fixed in qemu 1:7.2+dfsg-7+deb12u6 has caused the Debian Bug report #1068821, regarding qemu: CVE-2024-3447 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1068820: marked as done (qemu: CVE-2024-3446)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 22:17:10 + with message-id and subject line Bug#1068820: fixed in qemu 1:7.2+dfsg-7+deb12u6 has caused the Debian Bug report #1068820, regarding qemu: CVE-2024-3446 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1068819: marked as done (qemu: CVE-2024-26327 CVE-2024-26328)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 22:17:10 + with message-id and subject line Bug#1068819: fixed in qemu 1:7.2+dfsg-7+deb12u6 has caused the Debian Bug report #1068819, regarding qemu: CVE-2024-26327 CVE-2024-26328 to be marked as done. This means that you claim that the problem has been de

Bug#1071780: marked as done (sepp: FTBFS: ImportError: cannot import name '_convert_node_to_root_polytomy' from 'dendropy.datamodel.treemodel')

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 21:39:35 + with message-id and subject line Bug#1071780: fixed in sepp 4.5.1+really4.5.1+dfsg-6 has caused the Debian Bug report #1071780, regarding sepp: FTBFS: ImportError: cannot import name '_convert_node_to_root_polytomy' from 'dendropy.datamodel.treem

Bug#967806: marked as done (wmclockmon: depends on deprecated GTK 2)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 21:40:08 + with message-id and subject line Bug#967806: fixed in wmclockmon 1.0.0-1 has caused the Debian Bug report #967806, regarding wmclockmon: depends on deprecated GTK 2 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1070489: marked as done (rust-hypothesis FTBFS: test failures)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 21:39:23 + with message-id and subject line Bug#1070489: fixed in rust-hypothesis 0.11.1-3 has caused the Debian Bug report #1070489, regarding rust-hypothesis FTBFS: test failures to be marked as done. This means that you claim that the problem has been de

Bug#1071723: marked as done (pam-p11: FTBFS: configure.ac:70: error: possibly undefined macro: AC_MSG_ERROR)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 21:38:35 + with message-id and subject line Bug#1071723: fixed in pam-p11 0.6.0-2 has caused the Debian Bug report #1071723, regarding pam-p11: FTBFS: configure.ac:70: error: possibly undefined macro: AC_MSG_ERROR to be marked as done. This means that you

Bug#1061861: marked as done (libpam-ufpidentity: install PAM module into /usr)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 21:37:45 + with message-id and subject line Bug#1061861: fixed in libpam-ufpidentity 1.0-1.1 has caused the Debian Bug report #1061861, regarding libpam-ufpidentity: install PAM module into /usr to be marked as done. This means that you claim that the probl

Bug#1067395: marked as done (ITP: teraboxutility -- A python package for save file in TeraBox)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 21:18:26 + with message-id and subject line has caused the Debian Bug report #1067395, regarding ITP: teraboxutility -- A python package for save file in TeraBox to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1067948: marked as done (ITP: python-naked -- a command line application framework)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 21:09:41 + with message-id and subject line has caused the Debian Bug report #1067948, regarding ITP: python-naked -- a command line application framework to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#995245: marked as done (google-authenticator: Please update URL of upstream)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 20:41:30 + with message-id and subject line Bug#995245: fixed in google-authenticator 20191231-2.1 has caused the Debian Bug report #995245, regarding google-authenticator: Please update URL of upstream to be marked as done. This means that you claim that t

Bug#1068290: marked as done (python3-fastkml: ImportError since python3-pygeoif 1.4.0)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 20:40:58 + with message-id and subject line Bug#1068290: fixed in fastkml 0.12-4 has caused the Debian Bug report #1068290, regarding python3-fastkml: ImportError since python3-pygeoif 1.4.0 to be marked as done. This means that you claim that the problem h

Bug#1061492: marked as done (libpam-chroot: install PAM module into /usr)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 20:42:06 + with message-id and subject line Bug#1061492: fixed in libpam-chroot 0.9-5.3 has caused the Debian Bug report #1061492, regarding libpam-chroot: install PAM module into /usr to be marked as done. This means that you claim that the problem has bee

Bug#1018308: marked as done (anorack: build-depends on python3-nose or uses it for autopkgtest)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 20:40:50 + with message-id and subject line Bug#1018308: fixed in anorack 0.2.8-1 has caused the Debian Bug report #1018308, regarding anorack: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim that the

Bug#1061356: marked as done (google-authenticator: install PAM modules into /usr)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 20:41:30 + with message-id and subject line Bug#1061356: fixed in google-authenticator 20191231-2.1 has caused the Debian Bug report #1061356, regarding google-authenticator: install PAM modules into /usr to be marked as done. This means that you claim that

Bug#1064516: marked as done (ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 20:36:39 + with message-id and subject line Bug#1064516: fixed in ruby-rack 2.1.4-3+deb11u2 has caused the Debian Bug report #1064516, regarding ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146 to be marked as done. This means that you claim that the

Processed: src:traitlets: fails to migrate to testing for too long: causes issues in src:jupyter-notebook

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 5.14.3-1 Bug #1071907 [src:traitlets] src:traitlets: fails to migrate to testing for too long: causes issues in src:jupyter-notebook Marked as fixed in versions traitlets/5.14.3-1. Bug #1071907 [src:traitlets] src:traitlets: fails to migrate to testing for

Processed: src:mame: fails to migrate to testing for too long: FTBFS on armel

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.264+dfsg.1-1 Bug #1071906 [src:mame] src:mame: fails to migrate to testing for too long: FTBFS on armel Marked as fixed in versions mame/0.264+dfsg.1-1. Bug #1071906 [src:mame] src:mame: fails to migrate to testing for too long: FTBFS on armel Marked Bug

Processed: src:python-ppmd: fails to migrate to testing for too long: FTBFS on mips64el and ppc64el

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.5.0-1 Bug #1071905 [src:python-ppmd] src:python-ppmd: fails to migrate to testing for too long: FTBFS on mips64el and ppc64el Marked as fixed in versions python-ppmd/0.5.0-1. Bug #1071905 [src:python-ppmd] src:python-ppmd: fails to migrate to testing for

Bug#1064516: marked as done (ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 19:32:10 + with message-id and subject line Bug#1064516: fixed in ruby-rack 2.2.6.4-1+deb12u1 has caused the Debian Bug report #1064516, regarding ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146 to be marked as done. This means that you claim that t

Bug#1055474: marked as done (redmine: CVE-2023-47258 CVE-2023-47259 CVE-2023-47260)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 19:32:09 + with message-id and subject line Bug#1055474: fixed in redmine 5.0.4-5+deb12u1 has caused the Debian Bug report #1055474, regarding redmine: CVE-2023-47258 CVE-2023-47259 CVE-2023-47260 to be marked as done. This means that you claim that the pro

Bug#1071420: marked as done (linux-image-6.8.9-1-amd64: cannot mount btrfs root partition)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 21:20:46 +0200 with message-id and subject line Re: Bug#1071420: linux-image-6.8.9-1-amd64: cannot mount btrfs root partition has caused the Debian Bug report #1071420, regarding linux-image-6.8.9-1-amd64: cannot mount btrfs root partition to be marked as done.

Processed: close 1065074

2024-05-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1065074 252.24-1~deb12u1 Bug #1065074 [systemd-journal-remote] systemd-journal-remote: Version missmatch between bundled service and systemd version There is no source info for the package 'systemd-journal-remote' at version '252.24-1~deb1

Bug#1070359: marked as done (tabulate: too old for pandas 2.2)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 19:04:35 + with message-id and subject line Bug#1070359: fixed in python-tabulate 0.9.0-1 has caused the Debian Bug report #1070359, regarding tabulate: too old for pandas 2.2 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1013188: marked as done (packagesearch: doesn't seem to search descriptions)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 20:38:55 +0200 with message-id <8eca522765003030839653e543f3e09cac775005.ca...@gmx.net> and subject line Fixed by migration from libept to directly using libapt has caused the Debian Bug report #1013188, regarding packagesearch: doesn't seem to search description

Processed: close 1053482

2024-05-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1053482 252.24-1~deb12u1 Bug #1053482 [systemd-resolved] systemd-resolved: resolved can intermittingly fail AF_UNSPEC queries to CNAMEd domains There is no source info for the package 'systemd-resolved' at version '252.24-1~deb12u1' with a

Processed: Re: systemd-boot postinst update causes EFI crash

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > tags -1 -patch Bug #1043583 [systemd-boot] systemd-boot postinst update causes EFI crash Removed tag(s) patch. > tags -1 wontfix Bug #1043583 [systemd-boot] systemd-boot postinst update causes EFI crash Added tag(s) wontfix. > close -1 Bug #1043583 [systemd-boot] sys

Bug#1071786: marked as done (ITP: liblog-ger-perl -- lightweight, flexible logging framework)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 18:00:14 + with message-id and subject line Bug#1071786: fixed in liblog-ger-perl 0.042-1 has caused the Debian Bug report #1071786, regarding ITP: liblog-ger-perl -- lightweight, flexible logging framework to be marked as done. This means that you claim th

Bug#1071617: marked as done (ITP: cached-ipaddress -- Cache construction of IP address objects)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 18:00:11 + with message-id and subject line Bug#1071617: fixed in cached-ipaddress 0.3.0-1 has caused the Debian Bug report #1071617, regarding ITP: cached-ipaddress -- Cache construction of IP address objects to be marked as done. This means that you claim

Bug#1071583: marked as done (ITP: bluetooth-sensor-state-data -- Models for storing and converting Bluetooth Sensor State Data)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 18:00:11 + with message-id and subject line Bug#1071583: fixed in bluetooth-sensor-state-data 1.6.2-1 has caused the Debian Bug report #1071583, regarding ITP: bluetooth-sensor-state-data -- Models for storing and converting Bluetooth Sensor State Data to b

Bug#1056195: marked as done (ITP: bashacks -- collection of useful bash functions for programmers)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 18:00:10 + with message-id and subject line Bug#1056195: fixed in bashacks 1.5+git20231025.0f0d0eb-1 has caused the Debian Bug report #1056195, regarding ITP: bashacks -- collection of useful bash functions for programmers to be marked as done. This means t

Bug#1071203: marked as done (nicotine: GTK not found, fails to start.)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 17:04:32 + with message-id and subject line Bug#1071203: fixed in nicotine 3.3.4-1 has caused the Debian Bug report #1071203, regarding nicotine: GTK not found, fails to start. to be marked as done. This means that you claim that the problem has been dealt

Bug#1071540: marked as done (ITP: lua-vips -- A fast image processing library with low memory needs for Lua)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 17:00:12 + with message-id and subject line Bug#1071540: fixed in lua-vips 1.1.11-1 has caused the Debian Bug report #1071540, regarding ITP: lua-vips -- A fast image processing library with low memory needs for Lua to be marked as done. This means that yo

Bug#1071211: marked as done (ITP: brightnesspicker -- Graphical tool to set the screen brightness on Xorg)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 17:00:11 + with message-id and subject line Bug#1071211: fixed in brightnesspicker 1.0-1 has caused the Debian Bug report #1071211, regarding ITP: brightnesspicker -- Graphical tool to set the screen brightness on Xorg to be marked as done. This means that

Bug#1071486: marked as done (ITP: aiohappyeyeballs -- Happy Eyeballs connection helper for asyncio)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 17:00:10 + with message-id and subject line Bug#1071486: fixed in aiohappyeyeballs 2.3.2-1 has caused the Debian Bug report #1071486, regarding ITP: aiohappyeyeballs -- Happy Eyeballs connection helper for asyncio to be marked as done. This means that you c

Bug#1068669: marked as done (ITP: golang-github-mitchellh-hashstructure-v2 -- generate hash values for arbitrary values in Golang)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 17:00:11 + with message-id and subject line Bug#1068669: fixed in golang-github-mitchellh-hashstructure-v2 2.0.2-1 has caused the Debian Bug report #1068669, regarding ITP: golang-github-mitchellh-hashstructure-v2 -- generate hash values for arbitrary valu

Bug#1016694: marked as done (packages.debian.org uses favicon with white shadow)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 16:48:35 + with message-id <66521663982fc_28480f94c55...@godard.mail> and subject line Bug#1016694 fixed in www.debian.org has caused the Debian Bug report #1016694, regarding packages.debian.org uses favicon with white shadow to be marked as done. This mean

Bug#970286: marked as done (live-tools: please remove irl from uploaders)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 16:35:11 + with message-id and subject line Bug#970286: fixed in live-tools 1:20240525 has caused the Debian Bug report #970286, regarding live-tools: please remove irl from uploaders to be marked as done. This means that you claim that the problem has

Bug#1028627: marked as done (live-tools: Typo in a kernel parameter name)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 16:35:11 + with message-id and subject line Bug#1028627: fixed in live-tools 1:20240525 has caused the Debian Bug report #1028627, regarding live-tools: Typo in a kernel parameter name to be marked as done. This means that you claim that the problem has

Bug#1071735: marked as done (libxmlrpc-util-dev and libxmlrpc-util4 have an undeclared file conflict)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 16:21:54 + with message-id and subject line Bug#1071735: fixed in xmlrpc-c 1.59.03-3 has caused the Debian Bug report #1071735, regarding libxmlrpc-util-dev and libxmlrpc-util4 have an undeclared file conflict to be marked as done. This means that you clai

Bug#1042415: marked as done (ruby-aws-partitions: Package missing partitions.json)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 16:08:57 + with message-id and subject line Bug#1042415: fixed in ruby-aws-partitions 1.653.0-3 has caused the Debian Bug report #1042415, regarding ruby-aws-partitions: Package missing partitions.json to be marked as done. This means that you claim that th

Bug#1071707: marked as done (rustc: Add loong64 to the FAILURES_ALLOWED lists in d/rules)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 16:00:13 + with message-id and subject line Bug#1071707: fixed in rustc 1.72.1+dfsg1-1~exp1 has caused the Debian Bug report #1071707, regarding rustc: Add loong64 to the FAILURES_ALLOWED lists in d/rules to be marked as done. This means that you claim that

Bug#1071595: marked as done (cups: contortions needed to use duplex printing on HP Laserjet M402dn)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 17:39:13 +0200 with message-id <84121d42-f915-4b7b-8056-8cd643328...@alteholz.de> and subject line Re: Bug#1071595: it was a printer firmware problem has caused the Debian Bug report #1071595, regarding cups: contortions needed to use duplex printing on HP Laserj

Bug#1071750: marked as done (dnsdist: CVE-2024-25581)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 15:34:29 + with message-id and subject line Bug#1071750: fixed in dnsdist 1.9.4-1 has caused the Debian Bug report #1071750, regarding dnsdist: CVE-2024-25581 to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#1061386: marked as done (libxtensor-dev: Fails to install for arm64 arch on amd64)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 17:35:00 +0200 with message-id and subject line Re: libxtensor-dev: Fails to install for arm64 arch on amd64 has caused the Debian Bug report #1061386, regarding libxtensor-dev: Fails to install for arm64 arch on amd64 to be marked as done. This means that you

Bug#458838: marked as done (benchmarks: marking average)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 11:23:12 -0400 with message-id <4eeb8a606e62a374395bf567f189ca720a4e8b56.ca...@debian.org> and subject line Re: benchmarks: marking average has caused the Debian Bug report #458838, regarding benchmarks: marking average to be marked as done. This means that you

Bug#947159: marked as done (hardinfo segfaults when running benchmarks)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 11:20:08 -0400 with message-id <2877e9b491fcde2871f90b2ad2f5bd9b8fe8cb54.ca...@debian.org> and subject line Re: hardinfo segfaults when running benchmarks has caused the Debian Bug report #947159, regarding hardinfo segfaults when running benchmarks to be marked

Bug#1071834: marked as done (libxml2-dev: missing Depends on liblzma-dev and zlib1g-dev (used by pkg-config file))

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 15:20:10 + with message-id and subject line Bug#1071834: fixed in libxml2 2.12.7+dfsg-2 has caused the Debian Bug report #1071834, regarding libxml2-dev: missing Depends on liblzma-dev and zlib1g-dev (used by pkg-config file) to be marked as done. This mea

Bug#1071835: marked as done (libxml2-dev: pkgconfig libxml-2.0.pc has Requires.private: liblzma without (even indirect) dependeny on liblzma-dev)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 15:20:10 + with message-id and subject line Bug#1071834: fixed in libxml2 2.12.7+dfsg-2 has caused the Debian Bug report #1071834, regarding libxml2-dev: pkgconfig libxml-2.0.pc has Requires.private: liblzma without (even indirect) dependeny on liblzma-dev

Bug#458507: marked as done (improve benchmark-system)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 11:18:04 -0400 with message-id and subject line Re: improve benchmark-system has caused the Debian Bug report #458507, regarding improve benchmark-system to be marked as done. This means that you claim that the problem has been dealt with. If this is not the ca

Bug#455569: marked as done (hardinfo: Please add sorting to 'Computer>Kernel Modules', et al.)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 11:16:20 -0400 with message-id <669cd9122366ca0653b15f6ae3d697d3ab9777b1.ca...@debian.org> and subject line Re: hardinfo: Please add sorting to 'Computer>Kernel Modules', et al. has caused the Debian Bug report #455569, regarding hardinfo: Please add sorting to

Bug#523930: marked as done ([hardinfo] After some time it stops giving any kind of information)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 11:14:31 -0400 with message-id <5380d41e7e2e5e7a51dc99676c3ec1349fefca3c.ca...@debian.org> and subject line Re: [hardinfo] After some time it stops giving any kind of information has caused the Debian Bug report #523930, regarding [hardinfo] After some time it s

Bug#524844: marked as done (hardinfo: benchmark results unreadable)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 11:13:13 -0400 with message-id and subject line Re: hardinfo: benchmark results unreadable has caused the Debian Bug report #524844, regarding hardinfo: benchmark results unreadable to be marked as done. This means that you claim that the problem has been dealt

Processed: closing 872215

2024-05-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 872215 4.7.1-1.1 Bug #872215 [src:sosreport] sosreport: fdisk dependency needed The source 'sosreport' and version '4.7.1-1.1' do not appear to match any binary packages Marked as fixed in versions sosreport/4.7.1-1.1. Bug #872215 [src:sosr

Processed: closing 1067411

2024-05-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1067411 4.7.1-1.1 Bug #1067411 [sosreport] sosreport: Debian Unstable version is running behind with 3 years (new release 4.7.0) There is no source info for the package 'sosreport' at version '4.7.1-1.1' with architecture '' Unable to make

Processed: closing 1018639

2024-05-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1018639 4.7.1-1.1 Bug #1018639 [src:sosreport] sosreport: build-depends on python3-nose or uses it for autopkgtest The source 'sosreport' and version '4.7.1-1.1' do not appear to match any binary packages Marked as fixed in versions sosrep

Bug#585685: marked as done (hardinfo: Sometimes hangs when using "Devices->Storage". Missed dependencies.)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 11:09:19 -0400 with message-id <87ec55a889fc4390698508c06a747a953819af72.ca...@debian.org> and subject line Re: hardinfo: Sometimes hangs when using "Devices->Storage". Missed dependencies. has caused the Debian Bug report #585685, regarding hardinfo: Sometimes

Bug#999647: marked as done (squid-deb-proxy: Hompage and VCS control still actual?)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 15:05:49 + with message-id and subject line Bug#999647: fixed in squid-deb-proxy 0.8.16 has caused the Debian Bug report #999647, regarding squid-deb-proxy: Hompage and VCS control still actual? to be marked as done. This means that you claim that the probl

Bug#721122: marked as done (hardinfo: unable to generate or/and save reports)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 11:06:23 -0400 with message-id <48a3772ff3d67e8ad793013ac27a9cc9aa13ec4b.ca...@debian.org> and subject line Re: hardinfo: unable to generate or/and save reports has caused the Debian Bug report #721122, regarding hardinfo: unable to generate or/and save reports t

Bug#658985: marked as done (hardinfo: benchmark graphic bar lengths confusing and undocumented.)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 11:03:28 -0400 with message-id <86ab43e99d5499b03a47c5adef427f24bc0f64e6.ca...@debian.org> and subject line Re: hardinfo: benchmark graphic bar lengths confusing and undocumented. has caused the Debian Bug report #658985, regarding hardinfo: benchmark graphic ba

Bug#610596: marked as done (confusing error message on ipvsadm -L -6 -c)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 15:04:19 + with message-id and subject line Bug#610596: fixed in ipvsadm 1:1.31-3 has caused the Debian Bug report #610596, regarding confusing error message on ipvsadm -L -6 -c to be marked as done. This means that you claim that the problem has been dealt

Bug#1039239: marked as done (ipvsadm: ships sysv-init script without systemd unit)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 15:04:19 + with message-id and subject line Bug#1039239: fixed in ipvsadm 1:1.31-3 has caused the Debian Bug report #1039239, regarding ipvsadm: ships sysv-init script without systemd unit to be marked as done. This means that you claim that the problem has

Bug#572799: marked as done (hardinfo: dipslays SATA drives as SCSI)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 11:04:48 -0400 with message-id <7eea343a5a54069356038ad92d5a19921b3838fc.ca...@debian.org> and subject line Re: hardinfo: dipslays SATA drives as SCSI has caused the Debian Bug report #572799, regarding hardinfo: dipslays SATA drives as SCSI to be marked as done.

Bug#455568: marked as done (hardinfo: 'Storage>IDE Disks>CD-RW 52x24>Speeds' gives puzzling DVD speed.)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 11:01:54 -0400 with message-id and subject line Re: hardinfo: 'Storage>IDE Disks>CD-RW 52x24>Speeds' gives puzzling DVD speed. has caused the Debian Bug report #455568, regarding hardinfo: 'Storage>IDE Disks>CD-RW 52x24>Speeds' gives puzzling DVD speed. to be

Bug#446613: marked as done (gpu benchmark)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 11:00:22 -0400 with message-id <6a2887113313ca8ca0d6cad03958ed00d0ef80e8.ca...@debian.org> and subject line Re: gpu benchmark has caused the Debian Bug report #446613, regarding gpu benchmark to be marked as done. This means that you claim that the problem has b

Bug#492989: marked as done (hardinfo: doesn't use gnome preferred browser)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 10:54:19 -0400 with message-id <4a3872af94ba7ba7a529df91d3b33e79d3a5e8da.ca...@debian.org> and subject line Re: hardinfo: doesn't use gnome preferred browser has caused the Debian Bug report #492989, regarding hardinfo: doesn't use gnome preferred browser to be m

Bug#638951: marked as done (hardinfo: does not show usb devices)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 10:48:19 -0400 with message-id and subject line Re: hardinfo: does not show usb devices has caused the Debian Bug report #638951, regarding hardinfo: does not show usb devices to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1071818: marked as done (__lxcapi_create: 1760 Template "debian" not found on riscv64)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 22:47:22 +0800 with message-id and subject line Re: Bug#1071818: __lxcapi_create: 1760 Template "debian" not found on riscv64 has caused the Debian Bug report #1071818, regarding __lxcapi_create: 1760 Template "debian" not found on riscv64 to be marked as done

Bug#483136: marked as done ([hardinfo] shows only one temperature-sensor)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 10:45:18 -0400 with message-id <10eed5102ee25bf4358b2f2701fd54bb2744fe86.ca...@debian.org> and subject line Re: [hardinfo] shows only one temperature-sensor has caused the Debian Bug report #483136, regarding [hardinfo] shows only one temperature-sensor to be mar

Bug#486471: marked as done ([hardinfo] library for icons which are in hardinfo and tango?)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 10:44:01 -0400 with message-id <4643a8117e80e628d09bbaec6b6d679b5a2d8d38.ca...@debian.org> and subject line Re: Bug#486471: [hardinfo] library for icons which are in hardinfo and tango? has caused the Debian Bug report #486471, regarding [hardinfo] library for i

Bug#1018592: marked as done (python-u2flib-server: build-depends on python3-nose or uses it for autopkgtest)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 14:39:49 + with message-id and subject line Bug#1018592: fixed in python-u2flib-server 5.0.0-1.2 has caused the Debian Bug report #1018592, regarding python-u2flib-server: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This

Bug#1069763: marked as done (matrix-synapse: CVE-2024-31208)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 14:38:55 + with message-id and subject line Bug#1069763: fixed in matrix-synapse 1.103.0-2 has caused the Debian Bug report #1069763, regarding matrix-synapse: CVE-2024-31208 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#853749: marked as done (hardinfo gets segmentation fault)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 10:37:03 -0400 with message-id <3c9239d2750af820aa3e11eba15b76271a1ee752.ca...@debian.org> and subject line Re: hardinfo gets segmentation fault has caused the Debian Bug report #853749, regarding hardinfo gets segmentation fault to be marked as done. This means

Processed: Re: deal.ii: FTBFS: libgmp not linked, libdeal.ii.g.so.9.5.1: error: undefined reference to '__gmpn_neg'

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > tags -1 unreproducible Bug #1068464 [src:deal.ii] deal.ii: FTBFS: libgmp not linked, libdeal.ii.g.so.9.5.1: error: undefined reference to '__gmpn_neg' Added tag(s) unreproducible. > close -1 Bug #1068464 [src:deal.ii] deal.ii: FTBFS: libgmp not linked, libdeal.ii.g

Processed: src:python-watson-developer-cloud: fails to migrate to testing for too long: uploader built arch:all binary

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 8.0.0-1 Bug #1071857 [src:python-watson-developer-cloud] src:python-watson-developer-cloud: fails to migrate to testing for too long: uploader built arch:all binary Marked as fixed in versions python-watson-developer-cloud/8.0.0-1. Bug #1071857 [src:python

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

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.7.1-2 Bug #1071856 [src:alttab] src:alttab: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions alttab/1.7.1-2. Bug #1071856 [src:alttab] src:alttab: fails to migrate to testing for too long: autopkgtest regressio

Processed: src:matrix-synapse: fails to migrate to testing for too long: RC bug

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.103.0-1 Bug #1071854 [src:matrix-synapse] src:matrix-synapse: fails to migrate to testing for too long: RC bug Marked as fixed in versions matrix-synapse/1.103.0-1. Bug #1071854 [src:matrix-synapse] src:matrix-synapse: fails to migrate to testing for too

Processed: src:postsrsd: fails to migrate to testing for too long: FTBFS on armel and armhf

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.10-2.1 Bug #1071853 [src:postsrsd] src:postsrsd: fails to migrate to testing for too long: FTBFS on armel and armhf Marked as fixed in versions postsrsd/1.10-2.1. Bug #1071853 [src:postsrsd] src:postsrsd: fails to migrate to testing for too long: FTBFS o

Processed: src:python-uinput: fails to migrate to testing for too long: FTBFS on armel and armhf

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.0.1-1 Bug #1071852 [src:python-uinput] src:python-uinput: fails to migrate to testing for too long: FTBFS on armel and armhf Marked as fixed in versions python-uinput/1.0.1-1. Bug #1071852 [src:python-uinput] src:python-uinput: fails to migrate to testing

Processed: src:remmina: fails to migrate to testing for too long: unresolved RC bug

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.4.35+dfsg-2 Bug #1071851 [src:remmina] src:remmina: fails to migrate to testing for too long: unresolved RC bug Marked as fixed in versions remmina/1.4.35+dfsg-2. Bug #1071851 [src:remmina] src:remmina: fails to migrate to testing for too long: unresolve

Processed: src:python-dmidecode: fails to migrate to testing for too long: new autopkgtest fails everywhere

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.12.3-3 Bug #1071850 [src:python-dmidecode] src:python-dmidecode: fails to migrate to testing for too long: new autopkgtest fails everywhere Marked as fixed in versions python-dmidecode/3.12.3-3. Bug #1071850 [src:python-dmidecode] src:python-dmidecode: fa

Processed: src:creduce: fails to migrate to testing for too long: blocked by Build-Depends

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.11.0~20240312-1 Bug #1071849 [src:creduce] src:creduce: fails to migrate to testing for too long: blocked by Build-Depends Marked as fixed in versions creduce/2.11.0~20240312-1. Bug #1071849 [src:creduce] src:creduce: fails to migrate to testing for too

Processed: src:cvise: fails to migrate to testing for too long: blocked by Build-Depends

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.10.0-1 Bug #1071846 [src:cvise] src:cvise: fails to migrate to testing for too long: blocked by Build-Depends Marked as fixed in versions cvise/2.10.0-1. Bug #1071846 [src:cvise] src:cvise: fails to migrate to testing for too long: blocked by Build-Depen

Bug#1071831: marked as done (rust-rio - upcoming quick-xml update)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 13:50:41 + with message-id and subject line Bug#1071831: fixed in rust-rio 0.8.4-1 has caused the Debian Bug report #1071831, regarding rust-rio - upcoming quick-xml update to be marked as done. This means that you claim that the problem has been dealt with

Bug#1018381: marked as done (isbnlib: build-depends on python3-nose or uses it for autopkgtest)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 13:50:29 + with message-id and subject line Bug#1018381: fixed in isbnlib 3.10.14-0.1 has caused the Debian Bug report #1018381, regarding isbnlib: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim that

Processed: src:libfiu: fails to migrate to testing for too long: FTBFS on armel and armhf

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.2-2 Bug #1071844 [src:libfiu] src:libfiu: fails to migrate to testing for too long: FTBFS on armel and armhf Marked as fixed in versions libfiu/1.2-2. Bug #1071844 [src:libfiu] src:libfiu: fails to migrate to testing for too long: FTBFS on armel and armh

Bug#1064772: marked as done (pymupdf: FTBFS: fitz.i.c:3343:5: error: conflicting types for ‘fz_pixmap_size’; have ‘int(fz_context *, fz_pixmap *)’)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 13:37:59 + with message-id and subject line Bug#1064772: fixed in pymupdf 1.24.2+ds1-1 has caused the Debian Bug report #1064772, regarding pymupdf: FTBFS: fitz.i.c:3343:5: error: conflicting types for ‘fz_pixmap_size’; have ‘int(fz_context *, fz_pixmap *)’

Processed: src:r-cran-pracma: fails to migrate to testing for too long: uploader built arch:all binary

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.4.4-2 Bug #1071843 [src:r-cran-pracma] src:r-cran-pracma: fails to migrate to testing for too long: uploader built arch:all binary Marked as fixed in versions r-cran-pracma/2.4.4-2. Bug #1071843 [src:r-cran-pracma] src:r-cran-pracma: fails to migrate to t

Processed: src:rust-gsettings-macro: fails to migrate to testing for too long: Build-Depends not available

2024-05-25 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.2.0-2 Bug #1071842 [src:rust-gsettings-macro] src:rust-gsettings-macro: fails to migrate to testing for too long: Build-Depends not available The source 'rust-gsettings-macro' and version '0.2.0-2' do not appear to match any binary packages Marked as fix

Bug#1071734: marked as done (libsingular4m4n0 has an undeclared file conflict)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 13:20:58 + with message-id and subject line Bug#1071734: fixed in singular 1:4.4.0+ds-4 has caused the Debian Bug report #1071734, regarding libsingular4m4n0 has an undeclared file conflict to be marked as done. This means that you claim that the problem ha

Bug#886280: marked as done (hardinfo: Change icon in .desktop file)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 13:19:35 + with message-id and subject line Bug#886280: fixed in hardinfo 2.1.2+git20240525-1 has caused the Debian Bug report #886280, regarding hardinfo: Change icon in .desktop file to be marked as done. This means that you claim that the problem has bee

Bug#1071759: marked as done (firebird4.0 FTBFS with libre2-dev 20240501)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 13:04:24 + with message-id and subject line Bug#1071759: fixed in firebird4.0 4.0.4.3010.ds6-4 has caused the Debian Bug report #1071759, regarding firebird4.0 FTBFS with libre2-dev 20240501 to be marked as done. This means that you claim that the problem h

Bug#1071416: marked as done (gogglesmm: FTBFS for armel, x390x and more)

2024-05-25 Thread Debian Bug Tracking System
Your message dated Sat, 25 May 2024 12:04:12 + with message-id and subject line Bug#1071416: fixed in gogglesmm 1.2.5-4 has caused the Debian Bug report #1071416, regarding gogglesmm: FTBFS for armel, x390x and more to be marked as done. This means that you claim that the problem has been dea

  1   2   >