Bug#1064293: marked as done (less: CVE-2022-48624)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 19:18:13 + with message-id and subject line Bug#1064293: fixed in less 551-2+deb11u2 has caused the Debian Bug report #1064293, regarding less: CVE-2022-48624 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1064293: marked as done (less: CVE-2022-48624)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 19:18:09 + with message-id and subject line Bug#1064293: fixed in less 551-2+deb11u1 has caused the Debian Bug report #1064293, regarding less: CVE-2022-48624 to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1064293: marked as done (less: CVE-2022-48624)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:48:09 + with message-id and subject line Bug#1064293: fixed in less 590-2.1~deb12u2 has caused the Debian Bug report #1064293, regarding less: CVE-2022-48624 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1064293: marked as done (less: CVE-2022-48624)

2024-05-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 May 2024 18:48:05 + with message-id and subject line Bug#1064293: fixed in less 590-2.1~deb12u1 has caused the Debian Bug report #1064293, regarding less: CVE-2022-48624 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1064293: marked as done (less: CVE-2022-48624)

2024-04-21 Thread Debian Bug Tracking System
Your message dated Sun, 21 Apr 2024 15:49:35 + with message-id and subject line Bug#1064293: fixed in less 590-2.1 has caused the Debian Bug report #1064293, regarding less: CVE-2022-48624 to be marked as done. This means that you claim that the problem has been dealt with. If this is not