Bug#891806: marked as done (busybox: Please include stty in busybox-udeb)

Your message dated Mon, 06 Jun 2022 18:48:58 + with message-id and subject line Bug#891806: fixed in busybox 1:1.35.0-1 has caused the Debian Bug report #891806, regarding busybox: Please include stty in busybox-udeb to be marked as done. This means that you claim that the problem has been de

Bug#1002663: marked as done (busybox: new upstream version)

Your message dated Mon, 06 Jun 2022 18:48:58 + with message-id and subject line Bug#1002663: fixed in busybox 1:1.35.0-1 has caused the Debian Bug report #1002663, regarding busybox: new upstream version to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#891857: marked as done (busybox: Special case for /32 subnets not working as expected)

Your message dated Mon, 06 Jun 2022 18:48:58 + with message-id and subject line Bug#891857: fixed in busybox 1:1.35.0-1 has caused the Debian Bug report #891857, regarding busybox: Special case for /32 subnets not working as expected to be marked as done. This means that you claim that the pr

Bug#985674: marked as done (CVE-2021-28831)

Your message dated Mon, 06 Jun 2022 18:48:58 + with message-id and subject line Bug#985674: fixed in busybox 1:1.35.0-1 has caused the Debian Bug report #985674, regarding CVE-2021-28831 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Bug#995833: marked as done (busybox: uudecode doesn't recognise the special decode_pathname /dev/stdout)

Your message dated Mon, 06 Jun 2022 18:48:58 + with message-id and subject line Bug#995833: fixed in busybox 1:1.35.0-1 has caused the Debian Bug report #995833, regarding busybox: uudecode doesn't recognise the special decode_pathname /dev/stdout to be marked as done. This means that you cl

Bug#949626: marked as done (busybox-static: Please include less and ftpput in busybox-udeb)

Your message dated Mon, 06 Jun 2022 18:48:58 + with message-id and subject line Bug#949626: fixed in busybox 1:1.35.0-1 has caused the Debian Bug report #949626, regarding busybox-static: Please include less and ftpput in busybox-udeb to be marked as done. This means that you claim that the p

Bug#998803: marked as done (busybox: Debian’s busybox’ tr violates POSIX)

Your message dated Mon, 06 Jun 2022 18:48:58 + with message-id and subject line Bug#998803: fixed in busybox 1:1.35.0-1 has caused the Debian Bug report #998803, regarding busybox: Debian’s busybox’ tr violates POSIX to be marked as done. This means that you claim that the problem has been de

Bug#999567: marked as done (busybox: CVE-2021-42373 through CVE-2021-42386 (fixed in 1.34))

Your message dated Mon, 06 Jun 2022 18:48:58 + with message-id and subject line Bug#999567: fixed in busybox 1:1.35.0-1 has caused the Debian Bug report #999567, regarding busybox: CVE-2021-42373 through CVE-2021-42386 (fixed in 1.34) to be marked as done. This means that you claim that the p

Bug#998804: marked as done (busybox: please enable bas64)

Your message dated Mon, 06 Jun 2022 18:48:58 + with message-id and subject line Bug#998804: fixed in busybox 1:1.35.0-1 has caused the Debian Bug report #998804, regarding busybox: please enable bas64 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Processing of busybox_1.35.0-1_source.changes

busybox_1.35.0-1_source.changes uploaded successfully to localhost along with the files: busybox_1.35.0-1.dsc busybox_1.35.0.orig.tar.bz2 busybox_1.35.0-1.debian.tar.xz busybox_1.35.0-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

busybox_1.35.0-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 06 Jun 2022 21:25:41 +0300 Source: busybox Architecture: source Version: 1:1.35.0-1 Distribution: unstable Urgency: medium Maintainer: Debian Install System Team Changed-By: Michael Tokarev Closes: 891806 891857