Processed: closing 1034746

2024-11-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1034746 Bug #1034746 [e2fsprogs] Bug: mk2efs/mkfs.ext4 does not create the correct amount of inodes if -i is specified with 640k to 832k Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 10

Processed: closing 1088429

2024-11-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1088429 11.0.7+dfsg-1 Bug #1088429 [src:php-codecoverage] php-codecoverage: move from twitter-bootstrap{3,4} to bootstrap-html (v5) Marked as fixed in versions php-codecoverage/11.0.7+dfsg-1. Bug #1088429 [src:php-codecoverage] php-codecove

Bug#1088388: marked as done (structure-synth: please remove obsolete Build-Depends: dh-buildinfo)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Thu, 28 Nov 2024 06:34:15 + with message-id and subject line Bug#1088388: fixed in structure-synth 1.5.0-7.1 has caused the Debian Bug report #1088388, regarding structure-synth: please remove obsolete Build-Depends: dh-buildinfo to be marked as done. This means that you cl

Bug#1088383: marked as done (knitpy: please remove obsolete Build-Depends: dh-buildinfo)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Thu, 28 Nov 2024 06:34:05 + with message-id and subject line Bug#1088383: fixed in knitpy 0.1.1~git20180430-4.1 has caused the Debian Bug report #1088383, regarding knitpy: please remove obsolete Build-Depends: dh-buildinfo to be marked as done. This means that you claim th

Bug#1079668: marked as done (ghostscript: Use nodoc and nocheck build profiles)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Thu, 28 Nov 2024 05:34:35 + with message-id and subject line Bug#1079668: fixed in ghostscript 10.04.0~dfsg-2 has caused the Debian Bug report #1079668, regarding ghostscript: Use nodoc and nocheck build profiles to be marked as done. This means that you claim that the prob

Bug#961909: marked as done (ghostscript: PDFA_def.ps references srgb.icc with relative path)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Thu, 28 Nov 2024 05:34:35 + with message-id and subject line Bug#961909: fixed in ghostscript 10.04.0~dfsg-2 has caused the Debian Bug report #961909, regarding ghostscript: PDFA_def.ps references srgb.icc with relative path to be marked as done. This means that you claim t

Bug#723712: marked as done (ghostscript: /etc/mailcap for ps2txt)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Thu, 28 Nov 2024 05:34:35 + with message-id and subject line Bug#723712: fixed in ghostscript 10.04.0~dfsg-2 has caused the Debian Bug report #723712, regarding ghostscript: /etc/mailcap for ps2txt to be marked as done. This means that you claim that the problem has been de

Bug#729709: marked as done (ghostscript: ps2epsi to stdout)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 23:05:24 -0600 with message-id <8499924.T7Z3S40VBb@riemann> and subject line Re: Bug#729709: ghostscript: ps2epsi to stdout has caused the Debian Bug report #729709, regarding ghostscript: ps2epsi to stdout to be marked as done. This means that you claim that th

Bug#700981: marked as done (ghostscript: ps2??? stdin stdout)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 22:01:25 -0600 with message-id <2249122.irdbgypaU6@riemann> and subject line Re: ghostscript: ps2??? stdin stdout has caused the Debian Bug report #700981, regarding ghostscript: ps2??? stdin stdout to be marked as done. This means that you claim that the proble

Bug#359821: marked as done (gs: Error: /ioerror in --image-- printing to epson R300 through cups (hp lj1200 works ok))

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 21:41:56 -0600 with message-id <2802179.mvXUDI8C0e@riemann> and subject line Re: gs: ghostcript dies when printing to epson r300, but not hp lj1200 has caused the Debian Bug report #359821, regarding gs: Error: /ioerror in --image-- printing to epson R300 throug

Bug#443957: marked as done (CUPS with gs-gpl doesn't print pdf pages with images)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 21:41:56 -0600 with message-id <2802179.mvXUDI8C0e@riemann> and subject line Re: gs: ghostcript dies when printing to epson r300, but not hp lj1200 has caused the Debian Bug report #359821, regarding CUPS with gs-gpl doesn't print pdf pages with images to be mar

Bug#437262: marked as done (gs: /ioerror in --image-- printing PDF with images)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 21:41:56 -0600 with message-id <2802179.mvXUDI8C0e@riemann> and subject line Re: gs: ghostcript dies when printing to epson r300, but not hp lj1200 has caused the Debian Bug report #359821, regarding gs: /ioerror in --image-- printing PDF with images to be marke

Bug#458008: marked as done (xpdf writes DCTDecodeFilter input without JPEG SOI marker (gs: ERROR: /ioerror in --image--))

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 21:41:56 -0600 with message-id <2802179.mvXUDI8C0e@riemann> and subject line Re: gs: ghostcript dies when printing to epson r300, but not hp lj1200 has caused the Debian Bug report #359821, regarding xpdf writes DCTDecodeFilter input without JPEG SOI marker (gs:

Bug#1088294: marked as done (clang-19: Bump version to 19.1.4)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 23:34:17 -0500 with message-id and subject line Re: clang-19: Bump version to 19.1.4 has caused the Debian Bug report #1088294, regarding clang-19: Bump version to 19.1.4 to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#370397: marked as done (gs-common: Any chance of ps2pdf16?)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 21:52:02 -0600 with message-id <6148674.lOV4Wx5bFT@riemann> and subject line Re: gs-common: Any chance of ps2pdf16? has caused the Debian Bug report #370397, regarding gs-common: Any chance of ps2pdf16? to be marked as done. This means that you claim that the pr

Processed: closing 1072566

2024-11-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1072566 Bug #1072566 [e2fsprogs] mke2fs: should not enable metadata_csum_seed and orphan_file by default in bookworm-backports Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1072566: htt

Processed: closing 1056145

2024-11-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1056145 1.47.1-1 Bug #1056145 [src:e2fsprogs] e2fsprogs: FTBFS on hurd-i386 Marked as fixed in versions e2fsprogs/1.47.1-1. Bug #1056145 [src:e2fsprogs] e2fsprogs: FTBFS on hurd-i386 Marked Bug as done > thanks Stopping processing here. Ple

Bug#1087798: marked as done (Putty 0.81-3 FTBS: make[1]: *** [debian/rules:24: execute_after_dh_auto_test-arch] Error 1)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Thu, 28 Nov 2024 01:36:10 + with message-id and subject line Bug#1087798: fixed in putty 0.82-1 has caused the Debian Bug report #1087798, regarding Putty 0.81-3 FTBS: make[1]: *** [debian/rules:24: execute_after_dh_auto_test-arch] Error 1 to be marked as done. This means

Processed: closing 1016675

2024-11-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1016675 1.46.3-1 Bug #1016675 [e2fsprogs] mke2fs: filesytem is corrupt if -D (direct io) is used (on an image file) Ignoring request to alter fixed versions of bug #1016675 to the same values previously set Bug #1016675 [e2fsprogs] mke2fs:

Processed: close 1088401

2024-11-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1088401 257~rc3-1 Bug #1088401 [systemd] systemd 257~rc2-3 fails There is no source info for the package 'systemd' at version '257~rc3-1' with architecture '' Unable to make a source version for version '257~rc3-1' Marked as fixed in versio

Bug#1087817: marked as done (systemd-boot-efi: please increase minimum sections in stub PE header on riscv64)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Thu, 28 Nov 2024 00:50:58 + with message-id and subject line Bug#1087817: fixed in systemd 257~rc3-1 has caused the Debian Bug report #1087817, regarding systemd-boot-efi: please increase minimum sections in stub PE header on riscv64 to be marked as done. This means that y

Bug#1087808: marked as done (systemd-ukify: should probably depend on systemd-boot-efi)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Thu, 28 Nov 2024 00:50:58 + with message-id and subject line Bug#1087808: fixed in systemd 257~rc3-1 has caused the Debian Bug report #1087808, regarding systemd-ukify: should probably depend on systemd-boot-efi to be marked as done. This means that you claim that the probl

Bug#1085160: marked as done (linux-sysctl-defaults: apply setting after installation)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Thu, 28 Nov 2024 00:50:58 + with message-id and subject line Bug#1085160: fixed in systemd 257~rc3-1 has caused the Debian Bug report #1085160, regarding linux-sysctl-defaults: apply setting after installation to be marked as done. This means that you claim that the problem

Bug#1083515: marked as done (ofxstatement: (build-)depends on deprecated module python3-pkg-resources)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 23:24:15 + with message-id and subject line Bug#1083515: fixed in ofxstatement 0.9.2-0.1 has caused the Debian Bug report #1083515, regarding ofxstatement: (build-)depends on deprecated module python3-pkg-resources to be marked as done. This means that you

Bug#1088281: marked as done (libgit2-1.8: libgit2 cannot connect to https remotes)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 22:50:36 + with message-id and subject line Bug#1088281: fixed in libgit2 1.8.4+ds-3 has caused the Debian Bug report #1088281, regarding libgit2-1.8: libgit2 cannot connect to https remotes to be marked as done. This means that you claim that the problem h

Bug#1087269: marked as done (Updating the rainbows Uploaders list)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 22:51:42 + with message-id and subject line Bug#1087269: fixed in rainbows 5.2.1-1 has caused the Debian Bug report #1087269, regarding Updating the rainbows Uploaders list to be marked as done. This means that you claim that the problem has been dealt with

Bug#1088298: marked as done (reportbug: cargo fails to clone repositories from github.com due to a TLS problem)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 22:50:36 + with message-id and subject line Bug#1088281: fixed in libgit2 1.8.4+ds-3 has caused the Debian Bug report #1088281, regarding reportbug: cargo fails to clone repositories from github.com due to a TLS problem to be marked as done. This means tha

Bug#1079374: marked as done (debootstrap: Needs to look through Provides)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 22:19:20 + with message-id and subject line Bug#1079374: fixed in debootstrap 1.0.138 has caused the Debian Bug report #1079374, regarding debootstrap: Needs to look through Provides to be marked as done. This means that you claim that the problem has been

Bug#1081832: marked as done (golang-nhooyr-websocket: upstream moved to github.com/coder/websocket)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 22:04:23 + with message-id and subject line Bug#1081832: fixed in golang-nhooyr-websocket 1.8.12-1 has caused the Debian Bug report #1081832, regarding golang-nhooyr-websocket: upstream moved to github.com/coder/websocket to be marked as done. This means th

Bug#1086844: marked as done (passt: apparmor profile breaks passt in libguestfs)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 21:49:18 + with message-id and subject line Bug#1086844: fixed in guestfs-tools 1.52.2-2 has caused the Debian Bug report #1086844, regarding passt: apparmor profile breaks passt in libguestfs to be marked as done. This means that you claim that the problem

Bug#1088391: marked as done (sctk: please remove obsolete Build-Depends: dh-buildinfo)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 21:07:30 + with message-id and subject line Bug#1088391: fixed in sctk 2.4.12+dfsg-1 has caused the Debian Bug report #1088391, regarding sctk: please remove obsolete Build-Depends: dh-buildinfo to be marked as done. This means that you claim that the probl

Bug#1088279: marked as done (cdimage.debian.org: Unable to assign 'mount point' in net-install for encrypted mapped devices)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 22:42:38 +0100 with message-id <20241127214238.7tyq6oycxtb4b...@mraw.org> and subject line Re: Bug#1088279: Bug report 1088279 has caused the Debian Bug report #1088279, regarding cdimage.debian.org: Unable to assign 'mount point' in net-install for encrypted ma

Bug#1087957: marked as done (needrestart reports services need to be restarted after they are restarted)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1088012: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1088012, regarding needrestart reports services need to be restarted after they are restarted to be marked as done. This means that you

Bug#1088047: marked as done (needrestart does not have sufficient information to restart LXC containers)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087958: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087958, regarding needrestart does not have sufficient information to restart LXC containers to be marked as done. This means that you

Bug#986265: marked as done (plasma-widgets-addons: Undo widget removal fails when timer finished notification is not dismissed)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 21:04:32 + with message-id and subject line (No Subject) has caused the Debian Bug report #986265, regarding plasma-widgets-addons: Undo widget removal fails when timer finished notification is not dismissed to be marked as done. This means that you claim

Bug#1045754: marked as done (sctk: Fails to build source after successful build)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 21:07:30 + with message-id and subject line Bug#1045754: fixed in sctk 2.4.12+dfsg-1 has caused the Debian Bug report #1045754, regarding sctk: Fails to build source after successful build to be marked as done. This means that you claim that the problem has

Bug#1066360: marked as done (sctk: FTBFS: align.c:933:15: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration])

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 21:07:30 + with message-id and subject line Bug#1066360: fixed in sctk 2.4.12+dfsg-1 has caused the Debian Bug report #1066360, regarding sctk: FTBFS: align.c:933:15: error: implicit declaration of function ‘getpid’ [-Werror=implicit-function-declaration] t

Bug#1087957: marked as done (needrestart reports services need to be restarted after they are restarted)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087958: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087958, regarding needrestart reports services need to be restarted after they are restarted to be marked as done. This means that you

Bug#1088333: marked as done (rust-libseccomp-sys: Add support for loongarch64)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:47:16 + with message-id and subject line Bug#1088333: fixed in rust-libseccomp-sys 0.2.1-2 has caused the Debian Bug report #1088333, regarding rust-libseccomp-sys: Add support for loongarch64 to be marked as done. This means that you claim that the prob

Bug#1087958: marked as done (needrestart reports services need to be restarted after they are restarted)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087917: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087917, regarding needrestart reports services need to be restarted after they are restarted to be marked as done. This means that you

Bug#1087117: marked as done (tombo: Python SyntaxWarning)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:49:17 + with message-id and subject line Bug#1087117: fixed in tombo 1.5.1-7 has caused the Debian Bug report #1087117, regarding tombo: Python SyntaxWarning to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1083801: marked as done (tombo: (build-)depends on deprecated module python3-pkg-resources)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:49:17 + with message-id and subject line Bug#1083801: fixed in tombo 1.5.1-7 has caused the Debian Bug report #1083801, regarding tombo: (build-)depends on deprecated module python3-pkg-resources to be marked as done. This means that you claim that the p

Bug#1088343: marked as done (rust-libseccomp: Add support for loongarch64)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:47:09 + with message-id and subject line Bug#1088343: fixed in rust-libseccomp 0.3.0-10 has caused the Debian Bug report #1088343, regarding rust-libseccomp: Add support for loongarch64 to be marked as done. This means that you claim that the problem has

Bug#1049071: marked as done (tombo: Fails to build source after successful build)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:49:17 + with message-id and subject line Bug#1049071: fixed in tombo 1.5.1-7 has caused the Debian Bug report #1049071, regarding tombo: Fails to build source after successful build to be marked as done. This means that you claim that the problem has bee

Bug#1088355: marked as done (pyfastx: missing versioned dependencies on python3)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:45:03 + with message-id and subject line Bug#1088355: fixed in pyfastx 2.1.0-3 has caused the Debian Bug report #1088355, regarding pyfastx: missing versioned dependencies on python3 to be marked as done. This means that you claim that the problem has be

Bug#1087958: marked as done (needrestart reports services need to be restarted after they are restarted)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1088012: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1088012, regarding needrestart reports services need to be restarted after they are restarted to be marked as done. This means that you

Bug#1088047: marked as done (needrestart does not have sufficient information to restart LXC containers)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1088012: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1088012, regarding needrestart does not have sufficient information to restart LXC containers to be marked as done. This means that you

Bug#1088358: marked as done (nbdkit: FTBFS: failing tests)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:11 + with message-id and subject line Bug#1088358: fixed in nbdkit 1.40.4-5 has caused the Debian Bug report #1088358, regarding nbdkit: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1088012: marked as done (needrestart: Always restarts all LXC containers)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1088047: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1088047, regarding needrestart: Always restarts all LXC containers to be marked as done. This means that you claim that the problem has b

Bug#1087957: marked as done (needrestart reports services need to be restarted after they are restarted)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1088047: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1088047, regarding needrestart reports services need to be restarted after they are restarted to be marked as done. This means that you

Bug#1088012: marked as done (needrestart: Always restarts all LXC containers)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087958: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087958, regarding needrestart: Always restarts all LXC containers to be marked as done. This means that you claim that the problem has b

Bug#1087958: marked as done (needrestart reports services need to be restarted after they are restarted)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1088047: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1088047, regarding needrestart reports services need to be restarted after they are restarted to be marked as done. This means that you

Bug#1087918: marked as done (needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1088047: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1088047, regarding needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4 to be marked as done. This means that y

Bug#1087917: marked as done (needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1088047: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1088047, regarding needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4 to be marked as done. This means that y

Bug#1088012: marked as done (needrestart: Always restarts all LXC containers)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1088012: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1088012, regarding needrestart: Always restarts all LXC containers to be marked as done. This means that you claim that the problem has b

Bug#1088047: marked as done (needrestart does not have sufficient information to restart LXC containers)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1088047: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1088047, regarding needrestart does not have sufficient information to restart LXC containers to be marked as done. This means that you

Bug#1087917: marked as done (needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1088012: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1088012, regarding needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4 to be marked as done. This means that y

Bug#1087918: marked as done (needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1088012: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1088012, regarding needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4 to be marked as done. This means that y

Bug#1087958: marked as done (needrestart reports services need to be restarted after they are restarted)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087957: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087957, regarding needrestart reports services need to be restarted after they are restarted to be marked as done. This means that you

Bug#1087957: marked as done (needrestart reports services need to be restarted after they are restarted)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087918: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087918, regarding needrestart reports services need to be restarted after they are restarted to be marked as done. This means that you

Bug#1087958: marked as done (needrestart reports services need to be restarted after they are restarted)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087958: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087958, regarding needrestart reports services need to be restarted after they are restarted to be marked as done. This means that you

Bug#1087918: marked as done (needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087958: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087958, regarding needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4 to be marked as done. This means that y

Bug#1088047: marked as done (needrestart does not have sufficient information to restart LXC containers)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087957: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087957, regarding needrestart does not have sufficient information to restart LXC containers to be marked as done. This means that you

Bug#1087958: marked as done (needrestart reports services need to be restarted after they are restarted)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087918: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087918, regarding needrestart reports services need to be restarted after they are restarted to be marked as done. This means that you

Bug#1087917: marked as done (needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087958: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087958, regarding needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4 to be marked as done. This means that y

Bug#1088012: marked as done (needrestart: Always restarts all LXC containers)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087918: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087918, regarding needrestart: Always restarts all LXC containers to be marked as done. This means that you claim that the problem has b

Bug#1088012: marked as done (needrestart: Always restarts all LXC containers)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087957: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087957, regarding needrestart: Always restarts all LXC containers to be marked as done. This means that you claim that the problem has b

Bug#1087918: marked as done (needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087918: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087918, regarding needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4 to be marked as done. This means that y

Bug#1087917: marked as done (needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087957: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087957, regarding needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4 to be marked as done. This means that y

Bug#1087918: marked as done (needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087957: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087957, regarding needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4 to be marked as done. This means that y

Bug#1087957: marked as done (needrestart reports services need to be restarted after they are restarted)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087957: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087957, regarding needrestart reports services need to be restarted after they are restarted to be marked as done. This means that you

Bug#1088047: marked as done (needrestart does not have sufficient information to restart LXC containers)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087918: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087918, regarding needrestart does not have sufficient information to restart LXC containers to be marked as done. This means that you

Bug#1011576: marked as done (Updating the chromium-bsu Uploaders list)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:40:56 + with message-id and subject line Bug#1011576: fixed in chromium-bsu 0.9.16.1-4 has caused the Debian Bug report #1011576, regarding Updating the chromium-bsu Uploaders list to be marked as done. This means that you claim that the problem has been

Bug#1087917: marked as done (needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087917: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087917, regarding needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4 to be marked as done. This means that y

Bug#1087917: marked as done (needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087918: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087918, regarding needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4 to be marked as done. This means that y

Bug#1088047: marked as done (needrestart does not have sufficient information to restart LXC containers)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087917: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087917, regarding needrestart does not have sufficient information to restart LXC containers to be marked as done. This means that you

Bug#1088012: marked as done (needrestart: Always restarts all LXC containers)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087917: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087917, regarding needrestart: Always restarts all LXC containers to be marked as done. This means that you claim that the problem has b

Bug#1087918: marked as done (needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087917: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087917, regarding needrestart: False positive containerd.service after upgrade to 3.5-4+deb11u4 to be marked as done. This means that y

Bug#1087957: marked as done (needrestart reports services need to be restarted after they are restarted)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:43:22 + with message-id and subject line Bug#1087917: fixed in needrestart 3.7-3.2 has caused the Debian Bug report #1087917, regarding needrestart reports services need to be restarted after they are restarted to be marked as done. This means that you

Bug#1088354: marked as done (rdkit downloads from the internet during the build)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 19:46:51 + with message-id and subject line Bug#1088354: fixed in rdkit 202409.2-2 has caused the Debian Bug report #1088354, regarding rdkit downloads from the internet during the build to be marked as done. This means that you claim that the problem has b

Bug#1084524: marked as done (lifelines: Lifeline contains a code associated with CVE.)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 20:27:54 +0100 with message-id <4ca4zhudqewwzagkgx5qxsrc5iuvfxqtak77ykaflzl4rjq...@tarta.nabijaczleweli.xyz> and subject line Close: Bug#1084524: lifelines: Lifeline contains a code associated with CVE. has caused the Debian Bug report #1084524, regarding lifel

Bug#998740: marked as done (kde-telepathy: Connection to XMPP is not possible)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 17:47:11 + with message-id and subject line Bug#1088351: Removed package(s) from unstable has caused the Debian Bug report #998740, regarding kde-telepathy: Connection to XMPP is not possible to be marked as done. This means that you claim that the problem

Bug#967818: marked as done (xboard: depends on deprecated GTK 2)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 18:37:44 + with message-id and subject line Bug#967818: fixed in xboard 4.9.1-3 has caused the Debian Bug report #967818, regarding xboard: depends on deprecated GTK 2 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1088377: marked as done (python3-python-multipart has an undeclared file conflict)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 18:36:05 + with message-id and subject line Bug#1088377: fixed in python-multipart 0.0.17-4 has caused the Debian Bug report #1088377, regarding python3-python-multipart has an undeclared file conflict to be marked as done. This means that you claim that th

Bug#1079660: marked as done (calindori: Plasma 6 transition - qqc2-breeze-style)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 18:34:15 + with message-id and subject line Bug#1079660: fixed in calindori 24.08.3-1 has caused the Debian Bug report #1079660, regarding calindori: Plasma 6 transition - qqc2-breeze-style to be marked as done. This means that you claim that the problem ha

Bug#1088114: marked as done (licenserecon: False positives re LGPL-2.1)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 18:35:02 + with message-id and subject line Bug#1088114: fixed in licenserecon 3.2 has caused the Debian Bug report #1088114, regarding licenserecon: False positives re LGPL-2.1 to be marked as done. This means that you claim that the problem has been dealt

Bug#1079480: marked as done (qmlkonsole: FTBFS)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 18:36:24 + with message-id and subject line Bug#1079480: fixed in qmlkonsole 24.08.3-1 has caused the Debian Bug report #1079480, regarding qmlkonsole: FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1087989: marked as done (RM: libhdf5-openmpi-103-1t64 libhdf5-openmpi-cpp-103-1t64 libhdf5-openmpi-dev libhdf5-openmpi-fortran-102t64 libhdf5-openmpi-hl-100t64 libhdf5-openmpi-hl-cpp-100t64 libhdf

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 18:21:14 + with message-id and subject line Bug#1087989: Removed package(s) from unstable has caused the Debian Bug report #1087989, regarding RM: libhdf5-openmpi-103-1t64 libhdf5-openmpi-cpp-103-1t64 libhdf5-openmpi-dev libhdf5-openmpi-fortran-102t64 libhd

Bug#1087996: marked as done (RM: libscalapack-openmpi2.2 libscalapack-openmpi-dev [armel armhf i386] -- NBS; no longer built due to openmpi 32-bit removal)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 18:20:50 + with message-id and subject line Bug#1087996: Removed package(s) from unstable has caused the Debian Bug report #1087996, regarding RM: libscalapack-openmpi2.2 libscalapack-openmpi-dev [armel armhf i386] -- NBS; no longer built due to openmpi 32-

Bug#1077126: marked as done (proofgeneral: needs rebuild against dh-elpa >=2.1.5)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 18:10:12 + with message-id and subject line Bug#1077126: fixed in proofgeneral 4.5-3 has caused the Debian Bug report #1077126, regarding proofgeneral: needs rebuild against dh-elpa >=2.1.5 to be marked as done. This means that you claim that the problem ha

Bug#1088373: marked as done (RM: ignition-transport -- ROM; abandoned upstream, rc-buggy, low popcon, unmaintained)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 18:07:58 + with message-id and subject line Bug#1088373: Removed package(s) from unstable has caused the Debian Bug report #1088373, regarding RM: ignition-transport -- ROM; abandoned upstream, rc-buggy, low popcon, unmaintained to be marked as done. This

Bug#1087854: marked as done (ignition-transport: autopkgtest regression due to new CMake deprecation warning)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 18:08:00 + with message-id and subject line Bug#1088373: Removed package(s) from unstable has caused the Debian Bug report #1087854, regarding ignition-transport: autopkgtest regression due to new CMake deprecation warning to be marked as done. This means

Bug#1088360: marked as done (RM: netpipe-openmpi [armel armhf i386] -- NBS; no longer built due to openmpi 32-bit removal)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 17:46:32 + with message-id and subject line Bug#1088360: Removed package(s) from unstable has caused the Debian Bug report #1088360, regarding RM: netpipe-openmpi [armel armhf i386] -- NBS; no longer built due to openmpi 32-bit removal to be marked as done.

Bug#758690: marked as done (kde-telepathy: cant connect to my accounts (xmpp, icq, gmail))

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 17:47:11 + with message-id and subject line Bug#1088351: Removed package(s) from unstable has caused the Debian Bug report #758690, regarding kde-telepathy: cant connect to my accounts (xmpp, icq, gmail) to be marked as done. This means that you claim that

Bug#1088296: marked as done (RM: plasma-bigscreen -- ROM; Abandoned upstream)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 17:58:29 + with message-id and subject line Bug#1088296: Removed package(s) from unstable has caused the Debian Bug report #1088296, regarding RM: plasma-bigscreen -- ROM; Abandoned upstream to be marked as done. This means that you claim that the problem h

Bug#1088297: marked as done (RM: plasma-remotecontrollers -- ROM; Abandoned upstream)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 17:57:36 + with message-id and subject line Bug#1088297: Removed package(s) from unstable has caused the Debian Bug report #1088297, regarding RM: plasma-remotecontrollers -- ROM; Abandoned upstream to be marked as done. This means that you claim that the p

Bug#1088336: marked as done (RM: telepathy-accounts-signon -- ROM; Abandoned upstream)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 17:57:04 + with message-id and subject line Bug#1088336: Removed package(s) from unstable has caused the Debian Bug report #1088336, regarding RM: telepathy-accounts-signon -- ROM; Abandoned upstream to be marked as done. This means that you claim that the

Bug#1088349: marked as done (RM: ktp-send-file -- ROM; Abandoned upstream)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 17:48:22 + with message-id and subject line Bug#1088349: Removed package(s) from unstable has caused the Debian Bug report #1088349, regarding RM: ktp-send-file -- ROM; Abandoned upstream to be marked as done. This means that you claim that the problem has

Bug#1015464: marked as done (ktp-common-internals: ftbfs with LTO (link time optimization) enabled)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 17:56:34 + with message-id and subject line Bug#1088337: Removed package(s) from unstable has caused the Debian Bug report #1015464, regarding ktp-common-internals: ftbfs with LTO (link time optimization) enabled to be marked as done. This means that you cl

Bug#1088337: marked as done (RM: ktp-common-internals -- ROM; Abandoned upstream)

2024-11-27 Thread Debian Bug Tracking System
Your message dated Wed, 27 Nov 2024 17:56:31 + with message-id and subject line Bug#1088337: Removed package(s) from unstable has caused the Debian Bug report #1088337, regarding RM: ktp-common-internals -- ROM; Abandoned upstream to be marked as done. This means that you claim that the probl

  1   2   >