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

2024-02-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1063668 nvidia-kernel-dkms Bug #1063668 [src:nvidia-graphics-drivers] linux-image-6.1.0-18-amd64: Nvidia 525.147.05-4 issues Bug reassigned from package 'src:nvidia-graphics-drivers' to 'nvidia-kernel-dkms'. Ignoring request to alter fo

Bug#1043602: marked as done (cadical: Fails to build source after successful build)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sun, 11 Feb 2024 04:34:07 + with message-id and subject line Bug#1043602: fixed in cadical 1.7.4-1 has caused the Debian Bug report #1043602, regarding cadical: Fails to build source after successful build to be marked as done. This means that you claim that the problem has

Bug#1008088: marked as done (minder: Arrows going through entrys (visual))

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sun, 11 Feb 2024 12:23:33 +0800 with message-id and subject line has caused the Debian Bug report #1008088, regarding minder: Arrows going through entrys (visual) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it

Processed: RFS: html2text/2.2.3-2 -- advanced HTML to text converter

2024-02-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1061187 Bug #1061187 [sponsorship-requests] RFS: html2text/2.2.3-2 -- advanced HTML to text converter Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1061187: https://bugs.debian.org/cgi-bi

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

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sun, 11 Feb 2024 01:20:46 + with message-id and subject line Bug#1063363: fixed in nvidia-graphics-drivers 535.54.03-1 has caused the Debian Bug report #1063363, regarding nvidia-graphics-drivers: autopkgtest needs update for new version of linux to be marked as done. This

Bug#963701: marked as done (html2text: Please package the new upstream version (2.0.0)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sun, 11 Feb 2024 01:04:26 + with message-id and subject line Bug#963701: fixed in html2text 2.2.3-2 has caused the Debian Bug report #963701, regarding html2text: Please package the new upstream version (2.0.0 to be marked as done. This means that you claim that the problem

Processed: RFP: llama.cpp -- Port of Facebook's LLaMA model in C/C++

2024-02-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1063674 Bug #1063674 [wnpp] RFP: llama.cpp -- Port of Facebook's LLaMA model in C/C++ Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1063674: https://bugs.debian.org/cgi-bin/bugreport.cgi?b

Bug#1063607: marked as done (igraph: FTBFS on i386: test::igraph_hrg (Failed))

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 22:05:56 + with message-id and subject line Bug#1063607: fixed in igraph 0.10.9+ds-2 has caused the Debian Bug report #1063607, regarding igraph: FTBFS on i386: test::igraph_hrg (Failed) to be marked as done. This means that you claim that the problem has b

Bug#1061751: marked as done (python-django-debug-toolbar ftbfs with Python 3.12 as default)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 21:26:38 + with message-id and subject line Bug#1061751: fixed in python-django-debug-toolbar 1:4.3-1 has caused the Debian Bug report #1061751, regarding python-django-debug-toolbar ftbfs with Python 3.12 as default to be marked as done. This means that yo

Bug#967535: marked as done (ibus-chewing: depends on deprecated GTK 2)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 16:24:04 -0500 with message-id and subject line Re: ibus-chewing: depends on deprecated GTK 2 has caused the Debian Bug report #967535, regarding ibus-chewing: depends on deprecated GTK 2 to be marked as done. This means that you claim that the problem has bee

Bug#998095: marked as done (lxc-templates: lxc-create using alpine template fails with mknod error)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 19:13:30 + with message-id and subject line Bug#998095: fixed in lxc-templates 3.0.4.79.g84b0597-1 has caused the Debian Bug report #998095, regarding lxc-templates: lxc-create using alpine template fails with mknod error to be marked as done. This means th

Bug#960169: marked as done (lxc-templates: Fails to install when /var/lib/lxc is a symlink)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 19:13:30 + with message-id and subject line Bug#960169: fixed in lxc-templates 3.0.4.79.g84b0597-1 has caused the Debian Bug report #960169, regarding lxc-templates: Fails to install when /var/lib/lxc is a symlink to be marked as done. This means that you c

Bug#1055869: marked as done (lxc-templates: nedd upgrade from upstream for templates issue)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 19:13:30 + with message-id and subject line Bug#1055869: fixed in lxc-templates 3.0.4.79.g84b0597-1 has caused the Debian Bug report #1055869, regarding lxc-templates: nedd upgrade from upstream for templates issue to be marked as done. This means that you

Bug#1036640: marked as done (debian template's help lists archived releases that are not installable)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 19:13:30 + with message-id and subject line Bug#1036640: fixed in lxc-templates 3.0.4.79.g84b0597-1 has caused the Debian Bug report #1036640, regarding debian template's help lists archived releases that are not installable to be marked as done. This mean

Bug#1063662: marked as done (bleachbit: Depends on transitional policykit-1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 20:05:24 +0100 with message-id <01fde021-50ac-47d5-8eb8-3eb4e7d39...@tiscali.it> and subject line close fixed bug has caused the Debian Bug report #1063662, regarding bleachbit: Depends on transitional policykit-1 to be marked as done. This means that you claim

Processed: RFS: mini-httpd/1.30-8 -- Small HTTP server

2024-02-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1062805 Bug #1062805 [sponsorship-requests] RFS: mini-httpd/1.30-8 -- Small HTTP server Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1062805: https://bugs.debian.org/cgi-bin/bugreport.cgi

Bug#1063640: marked as done (adwaita-icon-theme: cursor theme not found)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 18:23:54 + with message-id and subject line Bug#1063640: fixed in mutter 44.8-3 has caused the Debian Bug report #1063640, regarding adwaita-icon-theme: cursor theme not found to be marked as done. This means that you claim that the problem has been dealt w

Bug#1061792: marked as done (mini-httpd: Update of mini-httpd still breaks default web page if it is not index.html)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 18:22:57 + with message-id and subject line Bug#1061792: fixed in mini-httpd 1.30-8 has caused the Debian Bug report #1061792, regarding mini-httpd: Update of mini-httpd still breaks default web page if it is not index.html to be marked as done. This means

Bug#1058440: marked as done (python-aiosmtpd: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 18:24:12 + with message-id and subject line Bug#1058440: fixed in python-aiosmtpd 1.4.4.post2-1 has caused the Debian Bug report #1058440, regarding python-aiosmtpd: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as don

Bug#1056454: marked as done (python-smtpd's autopkg tests fail with Python 3.12)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 18:24:12 + with message-id and subject line Bug#1056454: fixed in python-aiosmtpd 1.4.4.post2-1 has caused the Debian Bug report #1056454, regarding python-smtpd's autopkg tests fail with Python 3.12 to be marked as done. This means that you claim that the

Bug#1043530: marked as done (Please ship uasyncio and mip)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 18:22:36 + with message-id and subject line Bug#1043530: fixed in micropython 1.22.1+ds-1 has caused the Debian Bug report #1043530, regarding Please ship uasyncio and mip to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1042992: marked as done (micropython FTBFS with gcc 13)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 18:22:36 + with message-id and subject line Bug#1042992: fixed in micropython 1.22.1+ds-1 has caused the Debian Bug report #1042992, regarding micropython FTBFS with gcc 13 to be marked as done. This means that you claim that the problem has been dealt with

Bug#1033479: marked as done (minissdpd: Service fails to start on boot with "Error parsing address/mask...")

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 18:23:10 + with message-id and subject line Bug#1033479: fixed in minissdpd 1.6.0-2 has caused the Debian Bug report #1033479, regarding minissdpd: Service fails to start on boot with "Error parsing address/mask..." to be marked as done. This means that yo

Bug#1032721: marked as done ([INTL:ro] Romanian debconf templates translation of minissdpd)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 18:23:10 + with message-id and subject line Bug#1032721: fixed in minissdpd 1.6.0-2 has caused the Debian Bug report #1032721, regarding [INTL:ro] Romanian debconf templates translation of minissdpd to be marked as done. This means that you claim that the p

Bug#1063215: marked as done (gp-saml-gui: package depends on openconnect, but openconnect not strictly necessary)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 18:03:54 + with message-id and subject line Bug#1063215: fixed in gp-saml-gui 0.0~git20230507-3 has caused the Debian Bug report #1063215, regarding gp-saml-gui: package depends on openconnect, but openconnect not strictly necessary to be marked as done. T

Bug#1063590: marked as done (debian-reference-common: debian-reference and mkindexhtml are broken)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 17:25:02 + with message-id and subject line Bug#1063590: fixed in debian-reference 2.114 has caused the Debian Bug report #1063590, regarding debian-reference-common: debian-reference and mkindexhtml are broken to be marked as done. This means that you clai

Bug#1063416: marked as done (libgit2: CVE-2024-24577: Arbitrary code execution due to heap corruption in `git_index_add`)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 17:18:07 + with message-id and subject line Bug#1063416: fixed in libgit2 1.1.0+dfsg.1-4+deb11u2 has caused the Debian Bug report #1063416, regarding libgit2: CVE-2024-24577: Arbitrary code execution due to heap corruption in `git_index_add` to be marked as

Bug#1063415: marked as done (libgit2: CVE-2024-24575: Denial of service attack in `git_revparse_single`)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 17:17:18 + with message-id and subject line Bug#1063415: fixed in libgit2 1.5.1+ds-1+deb12u1 has caused the Debian Bug report #1063415, regarding libgit2: CVE-2024-24575: Denial of service attack in `git_revparse_single` to be marked as done. This means th

Bug#1063416: marked as done (libgit2: CVE-2024-24577: Arbitrary code execution due to heap corruption in `git_index_add`)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 17:17:18 + with message-id and subject line Bug#1063416: fixed in libgit2 1.5.1+ds-1+deb12u1 has caused the Debian Bug report #1063416, regarding libgit2: CVE-2024-24577: Arbitrary code execution due to heap corruption in `git_index_add` to be marked as don

Bug#1025084: marked as done (ruby-graphlient fails to rebuild after updating ruby-faraday to upstream)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 21:33:44 +0530 with message-id and subject line Re: ruby-graphlient fails to rebuild after updating ruby-faraday to upstream has caused the Debian Bug report #1025084, regarding ruby-graphlient fails to rebuild after updating ruby-faraday to upstream to be mar

Bug#984976: marked as done (mumble: Keyboard shortcuts can't be assigned)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 16:48:53 +0100 with message-id <4098367.1e1Y7FCuV0@bagend> and subject line Re: mumble: Keyboard shortcuts can't be assigned has caused the Debian Bug report #984976, regarding mumble: Keyboard shortcuts can't be assigned to be marked as done. This means that yo

Bug#1063609: marked as done (texstudio_4.7.2+ds-1_all-buildd.changes REJECTED)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 15:19:59 + with message-id and subject line Bug#1063609: fixed in texstudio 4.7.2+ds-2 has caused the Debian Bug report #1063609, regarding texstudio_4.7.2+ds-1_all-buildd.changes REJECTED to be marked as done. This means that you claim that the problem has

Bug#1063632: marked as done (spirv-llvm-translator-17 FTBFS: error: ‘CapabilityLongConstantCompositeINTEL’ was not declared in this scope)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 15:07:12 + with message-id and subject line Bug#1063632: fixed in spirv-llvm-translator-17 17.0.0-4 has caused the Debian Bug report #1063632, regarding spirv-llvm-translator-17 FTBFS: error: ‘CapabilityLongConstantCompositeINTEL’ was not declared in this s

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

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 15:00:29 + with message-id and subject line Bug#1062770: fixed in raft 0.22.0-1 has caused the Debian Bug report #1062770, regarding raft: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been dealt

Bug#1063603: marked as done (composer: CVE-2024-24821)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Bug#1063603: fixed in composer 2.7.1-1 has caused the Debian Bug report #1063603, regarding composer: CVE-2024-24821 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1063035: marked as done (bookworm-pu: package xen/4.17.3+10-g091466ba55-1~deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1063035, regarding bookworm-pu: package xen/4.17.3+10-g091466ba55-1~deb12u1 to be marked as done. This means that you claim that the problem has been dealt with

Bug#1063434: marked as done (src:389-ds-base: fails to migrate to testing for too long: FTBFS on 32 bits)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:10:16 + with message-id and subject line Bug#1063434: fixed in 389-ds-base 2.4.4+dfsg1-3 has caused the Debian Bug report #1063434, regarding src:389-ds-base: fails to migrate to testing for too long: FTBFS on 32 bits to be marked as done. This means th

Bug#1063005: marked as done (bookworm-pu: package tzdata/2024a-0+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1063005, regarding bookworm-pu: package tzdata/2024a-0+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1062686: marked as done (bookworm-pu: package libdatetime-timezone-perl/1:2.60-1+2024a)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1062686, regarding bookworm-pu: package libdatetime-timezone-perl/1:2.60-1+2024a to be marked as done. This means that you claim that the problem has been dealt

Bug#1062660: marked as done (bookworm-pu: package pypy3/7.3.11+dfsg-2+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1062660, regarding bookworm-pu: package pypy3/7.3.11+dfsg-2+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1062475: marked as done (bookworm-pu: package debian-edu-fai/2024.02.01.2~deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1062475, regarding bookworm-pu: package debian-edu-fai/2024.02.01.2~deb12u1 to be marked as done. This means that you claim that the problem has been dealt with

Bug#1062469: marked as done (bookworm-pu: package debian-edu-config/2.12.44~deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1062469, regarding bookworm-pu: package debian-edu-config/2.12.44~deb12u1 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1062435: marked as done (bookworm-pu: package indent/2.2.12-4+deb12u3)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1062435, regarding bookworm-pu: package indent/2.2.12-4+deb12u3 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1062175: marked as done (bookworm-pu: package debian-edu-install/2.12.10~deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1062175, regarding bookworm-pu: package debian-edu-install/2.12.10~deb12u1 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1062233: marked as done (bookworm-pu: package debian-edu-doc/2.12.23~deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1062233, regarding bookworm-pu: package debian-edu-doc/2.12.23~deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1062063: marked as done (bookworm-pu: package monitoring-plugins/2.3.3-5+deb12u2)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1062063, regarding bookworm-pu: package monitoring-plugins/2.3.3-5+deb12u2 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1061624: marked as done (bookworm-pu: package postfix/3.7.9-0+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061624, regarding bookworm-pu: package postfix/3.7.9-0+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1062004: marked as done (bookworm-pu: package usb.ids/2024.01.20-0+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1062004, regarding bookworm-pu: package usb.ids/2024.01.20-0+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1061652: marked as done (bookworm-pu: package rss-glx/0.9.1-6.4+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061652, regarding bookworm-pu: package rss-glx/0.9.1-6.4+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1061587: marked as done (bookworm-pu: package systemd/252.22-1~deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061587, regarding bookworm-pu: package systemd/252.22-1~deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1061607: marked as done (bookworm-pu: package compton/compton_1-1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061607, regarding bookworm-pu: package compton/compton_1-1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1061579: marked as done (bookworm-pu: package libspreadsheet-parsexlsx-perl/0.27-3+deb12u2)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:22 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061579, regarding bookworm-pu: package libspreadsheet-parsexlsx-perl/0.27-3+deb12u2 to be marked as done. This means that you claim that the problem has been d

Bug#1061523: marked as done (bookworm-pu: package tzdata/2023d-0+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061523, regarding bookworm-pu: package tzdata/2023d-0+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1061549: marked as done (bookworm-pu: package dropbear/2022.83-1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061549, regarding bookworm-pu: package dropbear/2022.83-1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1061487: marked as done (bookworm-pu: package rpm/4.18.0+dfsg-1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061487, regarding bookworm-pu: package rpm/4.18.0+dfsg-1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1061473: marked as done (bookworm-pu: package tinyxml/2.6.2-6+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061473, regarding bookworm-pu: package tinyxml/2.6.2-6+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1061465: marked as done (bookworm-pu: package usbutils/014-1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061465, regarding bookworm-pu: package usbutils/014-1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1061407: marked as done (bookworm-pu: package debian-ports-archive-keyring/2024.01.05~deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061407, regarding bookworm-pu: package debian-ports-archive-keyring/2024.01.05~deb12u1 to be marked as done. This means that you claim that the problem has bee

Bug#1061291: marked as done (composer: recommends missing: php-curl)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Bug#1061291: fixed in composer 2.7.1-1 has caused the Debian Bug report #1061291, regarding composer: recommends missing: php-curl to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1061189: marked as done (bookworm-pu: package gnutls28/3.7.9-2+deb12u2)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061189, regarding bookworm-pu: package gnutls28/3.7.9-2+deb12u2 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1061176: marked as done (bookworm-pu: package tar/1.34+dfsg-1.2+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061176, regarding bookworm-pu: package tar/1.34+dfsg-1.2+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1061161: marked as done (bookworm-pu: package pypdf2/2.12.1-3)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1061161, regarding bookworm-pu: package pypdf2/2.12.1-3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#1060851: marked as done (bookworm-pu: package pypdf/3.4.1-1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1060851, regarding bookworm-pu: package pypdf/3.4.1-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#1060767: marked as done (bookworm-pu: package proftpd-mod-proxy/0.9.2-1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1060767, regarding bookworm-pu: package proftpd-mod-proxy/0.9.2-1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1060688: marked as done (bookworm-pu: package libspreadsheet-parsexlsx-perl/0.27-3+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1060688, regarding bookworm-pu: package libspreadsheet-parsexlsx-perl/0.27-3+deb12u1 to be marked as done. This means that you claim that the problem has been d

Bug#1060668: marked as done (bookworm-pu: package calibre/6.13.0+repack-2+deb12u3)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1060668, regarding bookworm-pu: package calibre/6.13.0+repack-2+deb12u3 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1060417: marked as done (bookworm-pu: package proftpd-dfsg/1.3.8+dfsg-4+deb12u3)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1060417, regarding bookworm-pu: package proftpd-dfsg/1.3.8+dfsg-4+deb12u3 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1060433: marked as done (bookworm-pu: package apktool/2.7.0+dfsg-6+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1060433, regarding bookworm-pu: package apktool/2.7.0+dfsg-6+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1060186: marked as done (bookworm-pu: libde265/1.0.11-1+deb12u2)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1060186, regarding bookworm-pu: libde265/1.0.11-1+deb12u2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#1060132: marked as done (bookworm-pu: package mate-settings-daemon/1.26.0-1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:21 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1060132, regarding bookworm-pu: package mate-settings-daemon/1.26.0-1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1060129: marked as done (bookworm-pu: package libmateweather/1.26.0-1.1+deb12u2)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1060129, regarding bookworm-pu: package libmateweather/1.26.0-1.1+deb12u2 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1060122: marked as done (bookworm-pu: package atril/1.26.0-2+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1060122, regarding bookworm-pu: package atril/1.26.0-2+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1059846: marked as done (bookworm-pu: package isl/0.25-1.1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1059846, regarding bookworm-pu: package isl/0.25-1.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the ca

Bug#1059705: marked as done (bookworm-pu: package pluma/1.26.0-1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1059705, regarding bookworm-pu: package pluma/1.26.0-1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1059696: marked as done (bookworm-pu: package mate-utils/1.26.0-1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1059696, regarding bookworm-pu: package mate-utils/1.26.0-1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1059694: marked as done (bookworm-pu: package filezilla/filezilla_3.63.0-1+deb12u3)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1059694, regarding bookworm-pu: package filezilla/filezilla_3.63.0-1+deb12u3 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1059656: marked as done (bookworm-pu: package espeak-ng/1.51+dfsg-10+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1059656, regarding bookworm-pu: package espeak-ng/1.51+dfsg-10+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1059609: marked as done (bookworm-pu: package engrampa/1.26.0-1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1059609, regarding bookworm-pu: package engrampa/1.26.0-1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1059524: marked as done (bookworm-pu: package mate-screensaver/1.26.1-1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1059524, regarding bookworm-pu: package mate-screensaver/1.26.1-1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1059402: marked as done (bookworm-pu: package postfix/3.7.6-0+deb12u2)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1059402, regarding bookworm-pu: package postfix/3.7.6-0+deb12u2 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1059522: marked as done (bookworm-pu: package caja/1.26.1-1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1059522, regarding bookworm-pu: package caja/1.26.1-1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#1059344: marked as done (bookworm-pu: package libdatetime-timezone-perl/1:2.60-1+2023d)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1059344, regarding bookworm-pu: package libdatetime-timezone-perl/1:2.60-1+2023d to be marked as done. This means that you claim that the problem has been dealt

Bug#1058615: marked as done (bookworm-pu: package node-yarnpkg/1.22.19+~cs24.27.18-2+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1058615, regarding bookworm-pu: package node-yarnpkg/1.22.19+~cs24.27.18-2+deb12u1 to be marked as done. This means that you claim that the problem has been dea

Bug#1059343: marked as done (bookworm-pu: package libfirefox-marionette-perl/1.35-1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1059343, regarding bookworm-pu: package libfirefox-marionette-perl/1.35-1+deb12u1 to be marked as done. This means that you claim that the problem has been deal

Bug#1059291: marked as done (bookworm-pu: package spip/4.1.9+dfsg-1+deb12u4)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1059291, regarding bookworm-pu: package spip/4.1.9+dfsg-1+deb12u4 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1059235: marked as done (bookworm-pu: package fish/3.6.0-3.1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1059235, regarding bookworm-pu: package fish/3.6.0-3.1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1058938: marked as done (bookworm-pu: package onionprobe/1.0.0+ds-2.1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1058938, regarding bookworm-pu: package onionprobe/1.0.0+ds-2.1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1058928: marked as done (bookworm-pu: package cryptsetup/2:2.6.1-4~deb12u2)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1058928, regarding bookworm-pu: package cryptsetup/2:2.6.1-4~deb12u2 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1058458: marked as done (bookworm-pu: package nextcloud-desktop/3.7.3-1+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:20 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1058458, regarding bookworm-pu: package nextcloud-desktop/3.7.3-1+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1057089: marked as done (bookworm-pu: package usrmerge/37~deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:19 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1057089, regarding bookworm-pu: package usrmerge/37~deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1057179: marked as done (bookworm-pu: package mariadb-10.6 1:10.11.6-0+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:19 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1057179, regarding bookworm-pu: package mariadb-10.6 1:10.11.6-0+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1057891: marked as done (bookworm-pu: package debian-edu-artwork/2.12.4-1~deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:19 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1056222, regarding bookworm-pu: package debian-edu-artwork/2.12.4-1~deb12u1 to be marked as done. This means that you claim that the problem has been dealt with

Bug#1056969: marked as done (bookworm-pu: package swupdate/2022.12+dfsg-4+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:19 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1056969, regarding bookworm-pu: package swupdate/2022.12+dfsg-4+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1056358: marked as done (bookworm-pu: package needrestart/3.6-4+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:19 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1056358, regarding bookworm-pu: package needrestart/3.6-4+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1056222: marked as done (bookworm-pu: package debian-edu-artwork/2.12.4-1~deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:19 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1056222, regarding bookworm-pu: package debian-edu-artwork/2.12.4-1~deb12u1 to be marked as done. This means that you claim that the problem has been dealt with

Bug#1055248: marked as done (bookworm-pu: pipewire/0.3.65-3+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:19 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1055248, regarding bookworm-pu: pipewire/0.3.65-3+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not t

Bug#1054488: marked as done (bookworm-pu: package netplan.io/0.106-2)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:19 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1054488, regarding bookworm-pu: package netplan.io/0.106-2 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1054466: marked as done (bookworm-pu: package localslackirc/1.17-1.1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:19 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1054466, regarding bookworm-pu: package localslackirc/1.17-1.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1042590: marked as done (django-session-security: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx')

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:32 + with message-id and subject line Bug#1042590: fixed in django-session-security 2.6.7+dfsg-1 has caused the Debian Bug report #1042590, regarding django-session-security: FTBFS with Sphinx 7.1, docutils 0.20: error: invalid command 'build_sphinx'

Bug#1054446: marked as done (bookworm-pu: package wolfssl/5.5.4-2+deb12u1)

2024-02-10 Thread Debian Bug Tracking System
Your message dated Sat, 10 Feb 2024 13:11:19 + with message-id and subject line Released with 12.5 has caused the Debian Bug report #1054446, regarding bookworm-pu: package wolfssl/5.5.4-2+deb12u1 to be marked as done. This means that you claim that the problem has been dealt with. If this is

  1   2   >