Processed: reassign 1063879 to nvidia-kernel-dkms, forcibly merging 1062932 1063879

2024-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1063879 nvidia-kernel-dkms Bug #1063879 [src:linux] linux-image-6.1.0-18-amd64: nvidia-drivers 525.147.05 do not compile against linux-image 6.1.0-18 Bug reassigned from package 'src:linux' to 'nvidia-kernel-dkms'. No longer marked as fo

Bug#1036480: marked as done (microbegps: please add autopkgtests (to add coverage for python3-matplotlib))

2024-02-13 Thread Debian Bug Tracking System
Your message dated Wed, 14 Feb 2024 07:34:03 + with message-id and subject line Bug#1036480: fixed in microbegps 1.0.0-6 has caused the Debian Bug report #1036480, regarding microbegps: please add autopkgtests (to add coverage for python3-matplotlib) to be marked as done. This means that you

Bug#907314: marked as done (unbound: exception in python module due to the dnameAsStr() function)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Wed, 14 Feb 2024 09:27:17 +0300 with message-id <557779dd-23e1-437c-b098-d7a303609...@tls.msk.ru> and subject line Re: Bug#907314: unbound: exception in python module due to the dnameAsStr() function has caused the Debian Bug report #907314, regarding unbound: exception in pytho

Bug#1056631: marked as done (unbound: Please package 1.19.0 release for DNS64 improvements)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Wed, 14 Feb 2024 09:08:07 +0300 with message-id and subject line closing bugs fixed by 1.19 upload has caused the Debian Bug report #1056631, regarding unbound: Please package 1.19.0 release for DNS64 improvements to be marked as done. This means that you claim that the problem

Bug#1051817: marked as done (unbound: local_datas without \4\n reuses last read buffer(?) and produces infinite error output)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Wed, 14 Feb 2024 09:08:07 +0300 with message-id and subject line closing bugs fixed by 1.19 upload has caused the Debian Bug report #1051817, regarding unbound: local_datas without \4\n reuses last read buffer(?) and produces infinite error output to be marked as done. This me

Bug#1051818: marked as done (unbound: floods journal (100%CPU unbound, 100%CPU sd-journald) with errors when it can't reply to control socket peer)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Wed, 14 Feb 2024 09:08:07 +0300 with message-id and subject line closing bugs fixed by 1.19 upload has caused the Debian Bug report #1051818, regarding unbound: floods journal (100%CPU unbound, 100%CPU sd-journald) with errors when it can't reply to control socket peer to be ma

Bug#650246: marked as done (swig: compile warnings in C++ wrappers for Python)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Wed, 14 Feb 2024 17:04:38 +1300 with message-id and subject line Re: Bug#650246: swig: compile warnings in C++ wrappers for Python has caused the Debian Bug report #650246, regarding swig: compile warnings in C++ wrappers for Python to be marked as done. This means that you cl

Bug#1061020: marked as done (libervia-pubsub: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_install] Error 25)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Wed, 14 Feb 2024 00:20:12 + with message-id and subject line Bug#1061020: fixed in libervia-pubsub 0.5.0~hg489-1 has caused the Debian Bug report #1061020, regarding libervia-pubsub: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_install] Error 25 to be marked as do

Bug#1014879: marked as done (Please do not depend on gnome-remote-desktop)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 23:49:07 + with message-id and subject line Bug#1014879: fixed in gnome-control-center 1:46~beta-1 has caused the Debian Bug report #1014879, regarding Please do not depend on gnome-remote-desktop to be marked as done. This means that you claim that the pro

Bug#1063865: marked as done (src:tailspin: unsatisfied build dependency in testing: librust-terminal-size-0.2+default-dev)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 23:19:19 + with message-id and subject line Bug#1063865: fixed in tailspin 3.0.0+dfsg-2 has caused the Debian Bug report #1063865, regarding src:tailspin: unsatisfied build dependency in testing: librust-terminal-size-0.2+default-dev to be marked as done.

Bug#1061816: marked as done (mmdebstrap-autopkgtest-build-qemu VM image cannot be updated with sbuild-qemu-update)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Wed, 14 Feb 2024 00:16:09 +0100 with message-id <20240214001609.757e795e64f040f5b7a5f...@paranoici.org> and subject line Re: Bug#1061816: Bug#1061636: mmdebstrap-autopkgtest-build-qemu VM image cannot be updated with sbuild-qemu-update has caused the Debian Bug report #1061816,

Bug#1060730: marked as done (/usr/share/doc/libneatvnc-dev/examples/png-server.c: depends on "../src/pngfb.c", which isn't distributed)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 22:34:14 + with message-id and subject line Bug#1060730: fixed in neatvnc 0.7.1+dfsg-2 has caused the Debian Bug report #1060730, regarding /usr/share/doc/libneatvnc-dev/examples/png-server.c: depends on "../src/pngfb.c", which isn't distributed to be marke

Bug#1060729: marked as done (/usr/lib/x86_64-linux-gnu/pkgconfig/neatvnc.pc: Requires libdrm, libdrm-dev isn't pulled in the dependency list)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 22:34:14 + with message-id and subject line Bug#1060729: fixed in neatvnc 0.7.1+dfsg-2 has caused the Debian Bug report #1060729, regarding /usr/lib/x86_64-linux-gnu/pkgconfig/neatvnc.pc: Requires libdrm, libdrm-dev isn't pulled in the dependency list to be

Bug#1063840: marked as done (RFS: python-airspeed/0.6.0-1 -- Python template engine)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 23:18:48 +0100 with message-id <1497ea6b-7d9e-4660-bafa-aaf6f13cf...@debian.org> and subject line Re: RFS: python-airspeed/0.6.0-1 -- Python template engine has caused the Debian Bug report #1063840, regarding RFS: python-airspeed/0.6.0-1 -- Python template engin

Bug#1063763: marked as done (RFS: python-shtab/1.6.5-1 -- Automagic shell tab completion for Python CLI applications)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 23:18:55 +0100 with message-id and subject line Re: RFS: python-shtab/1.6.5-1 -- Automagic shell tab completion for Python CLI applications has caused the Debian Bug report #1063763, regarding RFS: python-shtab/1.6.5-1 -- Automagic shell tab completion for Pyt

Bug#1045672: marked as done (yara: Fails to build source after successful build)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 22:08:26 + with message-id and subject line Bug#1045672: fixed in yara 4.5.0-1 has caused the Debian Bug report #1045672, regarding yara: Fails to build source after successful build to be marked as done. This means that you claim that the problem has been

Bug#1062057: marked as done (chipmunk: NMU diff for 64-bit time_t transition)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 22:45:59 +0100 with message-id <20240213214559.kqjw3vr5nhsnz...@notk.org> and subject line Re: updated analysis results (ABI is unaffected) has caused the Debian Bug report #1062057, regarding chipmunk: NMU diff for 64-bit time_t transition to be marked as done.

Bug#987012: marked as done (gsettings-desktop-schemas: Can you update to 40.0 version?)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 16:40:15 -0500 with message-id and subject line Re: gsettings-desktop-schemas: Can you update to 40.0 version? has caused the Debian Bug report #987012, regarding gsettings-desktop-schemas: Can you update to 40.0 version? to be marked as done. This means that

Bug#971426: marked as done (vte2.91: Please build vte WITH_SIXEL)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 16:38:49 -0500 with message-id and subject line Re: libvte-dev: Please consider enabling sixel support has caused the Debian Bug report #971426, regarding vte2.91: Please build vte WITH_SIXEL to be marked as done. This means that you claim that the problem has

Bug#1063845: marked as done (unbound: Package 1.19.1 to fix CVE-2023-50387 and CVE-2023-50868)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Wed, 14 Feb 2024 00:15:13 +0300 with message-id <7844e010-11fc-4eff-82fc-43218aecc...@tls.msk.ru> and subject line Re: Bug#1063845: unbound: Package 1.19.1 to fix CVE-2023-50387 and CVE-2023-50868 has caused the Debian Bug report #1063845, regarding unbound: Package 1.19.1 to fi

Bug#1063867: marked as done (engrampa: Depends on non-free package)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 20:49:11 + with message-id and subject line Bug#1063867: fixed in engrampa 1.26.2-3 has caused the Debian Bug report #1063867, regarding engrampa: Depends on non-free package to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1061028: marked as done (flask-restful: FTBFS: intersphinx inventory 'six/objects.inv' not fetchable due to : [Errno 2] No such file or directory: '/<>/docs

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 20:49:21 + with message-id and subject line Bug#1061028: fixed in flask-restful 0.3.10-1 has caused the Debian Bug report #1061028, regarding flask-restful: FTBFS: intersphinx inventory 'six/objects.inv' not fetchable due to : [Errno 2] No such file or dir

Processed: Re: Bug#1052129: acpica-unix: Failed to migrate to Testing; missing s390x build not properly handled

2024-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1052129 20230628-1 Bug #1052129 [src:acpica-unix] acpica-unix: Failed to migrate to Testing; missing s390x build not properly handled No longer marked as found in versions acpica-unix/20230628-1. > tags 1052129 - sid Bug #1052129 [src:ac

Processed (with 1 error): Re: python-django-health-check: please make the build reproducible

2024-02-13 Thread Debian Bug Tracking System
Processing control commands: > block -1 1057432 Unknown command or malformed arguments to command. > close -1 Bug #1026381 [src:python-django-health-check] python-django-health-check: please make the build reproducible Marked Bug as done -- 1026381: https://bugs.debian.org/cgi-bin/bugreport.cg

Processed (with 1 error): Re: python-iso8601: please make the build reproducible

2024-02-13 Thread Debian Bug Tracking System
Processing control commands: > block -1 1056291 Unknown command or malformed arguments to command. > close -1 Bug #1010279 [src:python-iso8601] python-iso8601: please make the build reproducible Marked Bug as done -- 1010279: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1010279 Debian Bug

Bug#1061636: marked as done (mmdebstrap-autopkgtest-build-qemu VM image cannot be updated with sbuild-qemu-update)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 19:19:46 + with message-id and subject line Bug#1061636: fixed in sbuild 0.85.5 has caused the Debian Bug report #1061636, regarding mmdebstrap-autopkgtest-build-qemu VM image cannot be updated with sbuild-qemu-update to be marked as done. This means that

Processed: src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x

2024-02-13 Thread Debian Bug Tracking System
Processing control commands: > close -1 8.7-1 Bug #1063864 [src:mediawiki2latex] src:mediawiki2latex: fails to migrate to testing for too long: not installable on armel, mips64el and s390x Marked as fixed in versions mediawiki2latex/8.7-1. Bug #1063864 [src:mediawiki2latex] src:mediawiki2latex: f

Processed: closing 999902

2024-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 02 1.2.3-1 Bug #02 [ruby-concurrent] ruby-concurrent: artefact gitignore file in package? Marked as fixed in versions ruby-concurrent/1.2.3-1. Bug #02 [ruby-concurrent] ruby-concurrent: artefact gitignore file in package? Marke

Bug#1063628: marked as done (ITP: python-command-runner -- a platform-agnostic external command execution library for python with extra goodies)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 19:00:12 + with message-id and subject line Bug#1063628: fixed in python-command-runner 1.6.0-1 has caused the Debian Bug report #1063628, regarding ITP: python-command-runner -- a platform-agnostic external command execution library for python with extra g

Bug#1063612: marked as done (ITP: corrosion -- Tool for integrating rust with an existing CMake project)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 19:00:11 + with message-id and subject line Bug#1063612: fixed in corrosion 0.4.7-1 has caused the Debian Bug report #1063612, regarding ITP: corrosion -- Tool for integrating rust with an existing CMake project to be marked as done. This means that you cl

Processed: RFS: astro/0.25.1-1 [ITP] -- Gemini web browser using shell script

2024-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1063861 Bug #1063861 [sponsorship-requests] RFS: astro/0.25.1-1 [ITP] -- Gemini web browser using shell script Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1063861: https://bugs.debian.o

Bug#1063843: marked as done (python3-electrum: Upgrade to Electrum 4.5.2 from 4.4.6 causes installation of texlive packages)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:49:04 + with message-id and subject line Bug#1063843: fixed in electrum 4.5.2+dfsg-2 has caused the Debian Bug report #1063843, regarding python3-electrum: Upgrade to Electrum 4.5.2 from 4.4.6 causes installation of texlive packages to be marked as done.

Bug#969981: marked as done (RM: acpitail -- RoQA; orphaned, abandoned upstream)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:45:16 + with message-id and subject line Bug#969981: Removed package(s) from unstable has caused the Debian Bug report #969981, regarding RM: acpitail -- RoQA; orphaned, abandoned upstream to be marked as done. This means that you claim that the problem

Bug#726249: marked as done (RM: snarf -- RoQA; orphaned; abandoned upstream)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:43:52 + with message-id and subject line Bug#726249: Removed package(s) from unstable has caused the Debian Bug report #726249, regarding RM: snarf -- RoQA; orphaned; abandoned upstream to be marked as done. This means that you claim that the problem has

Bug#375867: marked as done (snarf: progress bar goes nuts for 2G+ files)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:43:55 + with message-id and subject line Bug#726249: Removed package(s) from unstable has caused the Debian Bug report #375867, regarding snarf: progress bar goes nuts for 2G+ files to be marked as done. This means that you claim that the problem has bee

Bug#1063854: marked as done (RM: senlin -- ROM; unmaintained)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:42:03 + with message-id and subject line Bug#1063854: Removed package(s) from unstable has caused the Debian Bug report #1063854, regarding RM: senlin -- ROM; unmaintained to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1063850: marked as done (RM: freezer -- ROM; unmaintained)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:40:52 + with message-id and subject line Bug#1063850: Removed package(s) from unstable has caused the Debian Bug report #1063850, regarding RM: freezer -- ROM; unmaintained to be marked as done. This means that you claim that the problem has been dealt w

Bug#1063853: marked as done (RM: wims-moodle -- ROM; this package works only wil moodle version 2)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:41:27 + with message-id and subject line Bug#1063853: Removed package(s) from unstable has caused the Debian Bug report #1063853, regarding RM: wims-moodle -- ROM; this package works only wil moodle version 2 to be marked as done. This means that you cla

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

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:40:55 + with message-id and subject line Bug#1063850: Removed package(s) from unstable has caused the Debian Bug report #1026398, regarding freezer: [INTL:pt_BR] Brazilian Portuguese debconf templates translation to be marked as done. This means that yo

Bug#1060097: marked as done (pytorch: FBFS: /<>/aten/src/ATen/native/quantized/cpu/qlinear_prepack.cpp:249:103: error: cannot convert ‘dnnl::memory::data_type’ to ‘const ideep::dims&’ {ak

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:34:47 + with message-id and subject line Bug#1060097: fixed in pytorch 2.1.2+dfsg-2 has caused the Debian Bug report #1060097, regarding pytorch: FBFS: /<>/aten/src/ATen/native/quantized/cpu/qlinear_prepack.cpp:249:103: error: cannot convert ‘dnnl::memo

Bug#1063788: marked as done (RM: rust-libadwaita-sys/experimental -- ROM; wrongful upload)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:33:41 + with message-id and subject line Bug#1063788: Removed package(s) from experimental has caused the Debian Bug report #1063788, regarding RM: rust-libadwaita-sys/experimental -- ROM; wrongful upload to be marked as done. This means that you claim t

Bug#1063655: marked as done (RM: ruby-graphql-errors -- ROM; unmaintained upstream, incompatible with ruby-graphql 2.x)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:33:06 + with message-id and subject line Bug#1063655: Removed package(s) from unstable has caused the Debian Bug report #1063655, regarding RM: ruby-graphql-errors -- ROM; unmaintained upstream, incompatible with ruby-graphql 2.x to be marked as done. T

Bug#1063654: marked as done (ruby-graphql-errors - upstream dead and incompatible with ruby-graphql 2.x)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:33:09 + with message-id and subject line Bug#1063655: Removed package(s) from unstable has caused the Debian Bug report #1063654, regarding ruby-graphql-errors - upstream dead and incompatible with ruby-graphql 2.x to be marked as done. This means that

Bug#1061499: marked as done (libgssglue: disable gsasl-dovecot-gssapi-heimdal autopkgtests on armhf, re-enable them on i386)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 19:32:54 +0100 with message-id <875xys8bah@kaka.sjd.se> and subject line Re: Bug#1061499: libgssglue: disable gsasl-dovecot-gssapi-heimdal autopkgtests on armhf, re-enable them on i386 has caused the Debian Bug report #1061499, regarding libgssglue: disable

Bug#1063058: marked as done (RM: embassy-domainatrix [armel armhf i386 hppa m68k powerpc sh4] -- ROM; emboss-lib does not support of 32 bit architectures any more)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:26:30 + with message-id and subject line Bug#1063058: Removed package(s) from unstable has caused the Debian Bug report #1063058, regarding RM: embassy-domainatrix [armel armhf i386 hppa m68k powerpc sh4] -- ROM; emboss-lib does not support of 32 bit arc

Bug#1063059: marked as done (RM: embassy-domalign [armel armhf i386 hppa m68k powerpc sh4] -- ROM; emboss-lib does not support of 32 bit architectures any more)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:26:58 + with message-id and subject line Bug#1063059: Removed package(s) from unstable has caused the Debian Bug report #1063059, regarding RM: embassy-domalign [armel armhf i386 hppa m68k powerpc sh4] -- ROM; emboss-lib does not support of 32 bit archit

Bug#1063838: marked as done (tmux: new upstream released: tmux 3.4)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:23:43 + with message-id and subject line Bug#1063838: fixed in tmux 3.4-1 has caused the Debian Bug report #1063838, regarding tmux: new upstream released: tmux 3.4 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1063237: marked as done (tmux: crash when pasting into dead pane)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:23:43 + with message-id and subject line Bug#1063237: fixed in tmux 3.4-1 has caused the Debian Bug report #1063237, regarding tmux: crash when pasting into dead pane to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1063057: marked as done (RM: embassy-domsearch [armel armhf i386 hppa m68k powerpc sh4]] -- ROM; emboss-lib does not support of 32 bit architectures any more)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:26:07 + with message-id and subject line Bug#1063057: Removed package(s) from unstable has caused the Debian Bug report #1063057, regarding RM: embassy-domsearch [armel armhf i386 hppa m68k powerpc sh4]] -- ROM; emboss-lib does not support of 32 bit arch

Bug#1062620: marked as done (RM: libdvbpsi/experimental -- ROM; not involved in time_t transition)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:25:29 + with message-id and subject line Bug#1062620: Removed package(s) from experimental has caused the Debian Bug report #1062620, regarding RM: libdvbpsi/experimental -- ROM; not involved in time_t transition to be marked as done. This means that you

Bug#1062512: marked as done (RM: taglib-extras -- ROM; Unmaintained; Incompatible with taglib 2.x)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 18:24:58 + with message-id and subject line Bug#1062512: Removed package(s) from unstable has caused the Debian Bug report #1062512, regarding RM: taglib-extras -- ROM; Unmaintained; Incompatible with taglib 2.x to be marked as done. This means that you cla

Bug#1063804: marked as done (FTBFS: depmod: FATAL: could not search modules: No such file or directory)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 16:51:51 + with message-id and subject line Bug#1063749: fixed in kmod 31+20240202-2 has caused the Debian Bug report #1063749, regarding FTBFS: depmod: FATAL: could not search modules: No such file or directory to be marked as done. This means that you cl

Bug#1063749: marked as done (kmod: kernel build fails with 31+20240202-1)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 16:51:51 + with message-id and subject line Bug#1063749: fixed in kmod 31+20240202-2 has caused the Debian Bug report #1063749, regarding kmod: kernel build fails with 31+20240202-1 to be marked as done. This means that you claim that the problem has been d

Bug#1060263: marked as done (prometheus-pgbouncer-exporter: no-change upload needed for DEP17 M2)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 16:52:10 + with message-id and subject line Bug#1060263: fixed in prometheus-pgbouncer-exporter 1.7-3 has caused the Debian Bug report #1060263, regarding prometheus-pgbouncer-exporter: no-change upload needed for DEP17 M2 to be marked as done. This means t

Bug#1063564: marked as done (engrampa: transition from p7zip to 7zip)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 16:22:11 + with message-id and subject line Bug#1063564: fixed in engrampa 1.26.2-2 has caused the Debian Bug report #1063564, regarding engrampa: transition from p7zip to 7zip to be marked as done. This means that you claim that the problem has been dealt

Bug#1063558: marked as done (pgpainless 1.6.6 is available)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Mon, 12 Feb 2024 12:50:49 -0500 with message-id <87le7ppo5i@fifthhorseman.net> and subject line Re: Bug#1063558: pgpainless 1.6.6 is available has caused the Debian Bug report #1063558, regarding pgpainless 1.6.6 is available to be marked as done. This means that you claim t

Bug#1063695: marked as done (ufw: move files to /usr (DEP17))

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 15:53:10 + with message-id and subject line Bug#1063695: fixed in ufw 0.36.2-5 has caused the Debian Bug report #1063695, regarding ufw: move files to /usr (DEP17) to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#844989: marked as done (Provide debug symbols)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 15:49:14 + with message-id and subject line Bug#844989: fixed in dnsmasq 2.90-1 has caused the Debian Bug report #844989, regarding Provide debug symbols to be marked as done. This means that you claim that the problem has been dealt with. If this is not th

Bug#966505: marked as done (dnsmasq: machine-readable copyright file)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 15:49:14 + with message-id and subject line Bug#966505: fixed in dnsmasq 2.90-1 has caused the Debian Bug report #966505, regarding dnsmasq: machine-readable copyright file to be marked as done. This means that you claim that the problem has been dealt with

Bug#1034135: marked as done (dnsmasq: Add autopkgtest for dnsmasq)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 15:49:15 + with message-id and subject line Bug#1034135: fixed in dnsmasq 2.90-1 has caused the Debian Bug report #1034135, regarding dnsmasq: Add autopkgtest for dnsmasq to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1063551: marked as done (dnsmasq: install systemd units below /usr (DEP17))

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 15:49:15 + with message-id and subject line Bug#1063551: fixed in dnsmasq 2.90-1 has caused the Debian Bug report #1063551, regarding dnsmasq: install systemd units below /usr (DEP17) to be marked as done. This means that you claim that the problem has been

Bug#1050750: marked as done (dnsmasq: Move to a lua version != 5.2)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 15:49:15 + with message-id and subject line Bug#1050750: fixed in dnsmasq 2.90-1 has caused the Debian Bug report #1050750, regarding dnsmasq: Move to a lua version != 5.2 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1040923: marked as done (dnsmasq: D-Bus policy is installed in /etc instead of /usr)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 15:49:15 + with message-id and subject line Bug#1040923: fixed in dnsmasq 2.90-1 has caused the Debian Bug report #1040923, regarding dnsmasq: D-Bus policy is installed in /etc instead of /usr to be marked as done. This means that you claim that the problem

Bug#1007041: marked as done (dnsmasq: please consider upgrading to 3.0 source format)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 15:49:14 + with message-id and subject line Bug#1007041: fixed in dnsmasq 2.90-1 has caused the Debian Bug report #1007041, regarding dnsmasq: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the problem ha

Bug#1033165: marked as done (dnsmasq: CVE-2023-28450)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 15:49:14 + with message-id and subject line Bug#1033165: fixed in dnsmasq 2.90-1 has caused the Debian Bug report #1033165, regarding dnsmasq: CVE-2023-28450 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#770331: marked as done (graphite-web: aliasByNode() gets upset by 'odd' characters in data paths)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 16:20:15 +0100 with message-id and subject line graphite-web: aliasByNode() gets upset by 'odd' characters in data paths has caused the Debian Bug report #770331, regarding graphite-web: aliasByNode() gets upset by 'odd' characters in data paths to be marked a

Bug#1063802: marked as done (Update to latest release (1.2.x))

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 15:06:25 + with message-id and subject line Bug#1063802: fixed in ruby-concurrent 1.2.3-1 has caused the Debian Bug report #1063802, regarding Update to latest release (1.2.x) to be marked as done. This means that you claim that the problem has been dealt w

Bug#1062667: marked as done (rust-h2: Resource exhaustion vulnerability in h2 may lead to Denial of Service)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 15:06:34 + with message-id and subject line Bug#1062667: fixed in rust-h2 0.3.24-1 has caused the Debian Bug report #1062667, regarding rust-h2: Resource exhaustion vulnerability in h2 may lead to Denial of Service to be marked as done. This means that you

Bug#1029139: marked as done (Please include Java/JRuby native extension)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 15:06:25 + with message-id and subject line Bug#1029139: fixed in ruby-concurrent 1.2.3-1 has caused the Debian Bug report #1029139, regarding Please include Java/JRuby native extension to be marked as done. This means that you claim that the problem has be

Bug#1063704: marked as done (RFS: tiny-initramfs/0.1-5.1 [NMU] [RC] -- Minimalistic initramfs implementation (automation))

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 16:02:14 +0100 with message-id and subject line Re: Bug#1063704: RFS: tiny-initramfs/0.1-5.1 [NMU] [RC] -- Minimalistic initramfs implementation (automation) has caused the Debian Bug report #1063704, regarding RFS: tiny-initramfs/0.1-5.1 [NMU] [RC] -- Minimali

Bug#1057095: marked as done (runit trigger_sv missing services restart)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 14:46:00 + with message-id and subject line Bug#1057095: fixed in runit 2.1.2-57 has caused the Debian Bug report #1057095, regarding runit trigger_sv missing services restart to be marked as done. This means that you claim that the problem has been dealt w

Bug#1038301: marked as done (please drop transitional package runit-systemd from src:runit)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 14:46:00 + with message-id and subject line Bug#1038301: fixed in runit 2.1.2-57 has caused the Debian Bug report #1038301, regarding please drop transitional package runit-systemd from src:runit to be marked as done. This means that you claim that the prob

Bug#1057094: marked as done (runit: lsb 40-runit does not forward sysv nonstandard actions)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 14:46:00 + with message-id and subject line Bug#1057094: fixed in runit 2.1.2-57 has caused the Debian Bug report #1057094, regarding runit: lsb 40-runit does not forward sysv nonstandard actions to be marked as done. This means that you claim that the prob

Bug#1057098: marked as done (RFS: runit/2.1.2-57 -- system-wide service supervision)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 15:06:46 +0100 with message-id and subject line Re: Bug#1057098: RFS: runit/2.1.2-57 -- system-wide service supervision has caused the Debian Bug report #1057098, regarding RFS: runit/2.1.2-57 -- system-wide service supervision to be marked as done. This means

Bug#1063784: marked as done (rust-tower-http: fails to build its provided source)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 11:49:29 + with message-id and subject line Bug#1063784: fixed in rust-tower-http 0.4.4-2 has caused the Debian Bug report #1063784, regarding rust-tower-http: fails to build its provided source to be marked as done. This means that you claim that the probl

Bug#1063600: marked as done (open3d: FTBFS: embree3/rtcore.h: No such file or directory)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 12:34:38 +0200 with message-id and subject line Already fixed in experimental has caused the Debian Bug report #1063600, regarding open3d: FTBFS: embree3/rtcore.h: No such file or directory to be marked as done. This means that you claim that the problem has be

Processed: closing 1063833

2024-02-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1063833 4.2.0-1 Bug #1063833 [src:mpich] mpich: ftbfs in sid due to newer slurm-wlm Marked as fixed in versions mpich/4.2.0-1. Bug #1063833 [src:mpich] mpich: ftbfs in sid due to newer slurm-wlm Marked Bug as done > thanks Stopping processin

Bug#1063094: marked as done (ITP: python-rtf-tokenize -- Simple RTF tokenizer for python)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 10:00:10 + with message-id and subject line Bug#1063094: fixed in python-rtf-tokenize 1.0.0-1 has caused the Debian Bug report #1063094, regarding ITP: python-rtf-tokenize -- Simple RTF tokenizer for python to be marked as done. This means that you claim th

Bug#1063817: marked as done (debconf-copydb pipe writes to GLOB file instead of stdout)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 09:48:56 + with message-id and subject line Bug#1063817: fixed in debconf 1.5.86 has caused the Debian Bug report #1063817, regarding debconf-copydb pipe writes to GLOB file instead of stdout to be marked as done. This means that you claim that the problem

Bug#1063702: marked as done (xkb-data: german keyboard config fails)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 08:44:18 + with message-id and subject line Bug#1063702: fixed in xkeyboard-config 2.41-2 has caused the Debian Bug report #1063702, regarding xkb-data: german keyboard config fails to be marked as done. This means that you claim that the problem has been d

Bug#1052302: marked as done (Missing Depends/Recommends: bsdextrautils (hexdump))

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 08:44:06 + with message-id and subject line Bug#1052302: fixed in translate-shell 0.9.7.1-2 has caused the Debian Bug report #1052302, regarding Missing Depends/Recommends: bsdextrautils (hexdump) to be marked as done. This means that you claim that the pro

Bug#1063725: marked as done (xkb-data: keymap alias 'dvorak' no longer available)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 08:44:18 + with message-id and subject line Bug#1063725: fixed in xkeyboard-config 2.41-2 has caused the Debian Bug report #1063725, regarding xkb-data: keymap alias 'dvorak' no longer available to be marked as done. This means that you claim that the probl

Bug#1038304: marked as done (please drop transitional package chipmunk-dev from src:chipmunk)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 08:34:10 + with message-id and subject line Bug#1038304: fixed in chipmunk 7.0.3-6 has caused the Debian Bug report #1038304, regarding please drop transitional package chipmunk-dev from src:chipmunk to be marked as done. This means that you claim that the

Bug#1063706: marked as done (linux-image-6.1.0-18-amd64: nvidia-tesla-470 doesn't build in 6.1.0-18 kernel)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 08:32:10 + with message-id and subject line Bug#1063361: fixed in nvidia-graphics-drivers-tesla-470 470.223.02-4~deb12u1 has caused the Debian Bug report #1063361, regarding linux-image-6.1.0-18-amd64: nvidia-tesla-470 doesn't build in 6.1.0-18 kernel to b

Bug#1063361: marked as done (nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of linux)

2024-02-13 Thread Debian Bug Tracking System
Your message dated Tue, 13 Feb 2024 08:32:10 + with message-id and subject line Bug#1063361: fixed in nvidia-graphics-drivers-tesla-470 470.223.02-4~deb12u1 has caused the Debian Bug report #1063361, regarding nvidia-graphics-drivers-tesla-470: autopkgtest needs update for new version of lin