Processing of apr_1.7.0-5_source.changes

2020-12-27 Thread Debian FTP Masters
apr_1.7.0-5.dsc has incorrect size; deleting it apr_1.7.0-5.debian.tar.xz has incorrect size; deleting it apr_1.7.0-5_source.buildinfo has incorrect size; deleting it Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processing of apr_1.7.0-5_source.changes

2020-12-27 Thread Debian FTP Masters
apr_1.7.0-5_source.changes uploaded successfully to localhost along with the files: apr_1.7.0-5.dsc apr_1.7.0-5.debian.tar.xz apr_1.7.0-5_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processing of apr_1.7.0-6_source.changes

2020-12-27 Thread Debian FTP Masters
apr_1.7.0-6_source.changes uploaded successfully to localhost along with the files: apr_1.7.0-6.dsc apr_1.7.0-6.debian.tar.xz apr_1.7.0-6_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

apr_1.7.0-6_source.changes ACCEPTED into unstable

2020-12-27 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 27 Dec 2020 17:28:47 +0100 Source: apr Architecture: source Version: 1.7.0-6 Distribution: unstable Urgency: medium Maintainer: Debian Apache Maintainers Changed-By: Stefan Fritsch Closes: 978018 Changes: apr

Bug#978045: apache2-bin: Immediate exit with "AH00141: Could not initialize random number generator"

2020-12-27 Thread Stefan Fritsch
Am 27.12.20 um 12:24 schrieb David W: I think a perfectly valid fix would be to document (in the changelog or elsewhere) that this hard requirement was added, in particular because (IIUC) using getrandom() instead of one of the other codepaths is the choice of the package maintainer. (I.e.

Bug#978018: marked as done (libapr1: Please add 64-bit atomics workaround for m68k and sh4)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 17:18:27 + with message-id and subject line Bug#978018: fixed in apr 1.7.0-6 has caused the Debian Bug report #978018, regarding libapr1: Please add 64-bit atomics workaround for m68k and sh4 to be marked as done. This means that you claim that the problem

Bug#978018: marked as done (libapr1: Please add 64-bit atomics workaround for m68k and sh4)

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 17:18:21 + with message-id and subject line Bug#978018: fixed in apr 1.7.0-5 has caused the Debian Bug report #978018, regarding libapr1: Please add 64-bit atomics workaround for m68k and sh4 to be marked as done. This means that you claim that the problem

Bug#978045: apache2-bin: Immediate exit with "AH00141: Could not initialize random number generator"

2020-12-27 Thread David W
On Sat, Dec 26, 2020 at 10:37 PM Ondřej Surý wrote: > I believe it’s a reasonable assumption that the kernel matches the Debian > release. If anybody is running with old kernel or disables getrandom I > would say they are on their own - also other stuff will break, not only > apache2. > Yes,

Processed: tagging 978045

2020-12-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 978045 + wontfix Bug #978045 [libapr1] apache2-bin: Immediate exit with "AH00141: Could not initialize random number generator" Added tag(s) wontfix. > thanks Stopping processing here. Please contact me if you need assistance. -- 978045:

Bug#978045: marked as done (apache2-bin: Immediate exit with "AH00141: Could not initialize random number generator")

2020-12-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Dec 2020 11:16:25 +0100 (CET) with message-id and subject line Re: Bug#978045: apache2-bin: Immediate exit with "AH00141: Could not initialize random number generator" has caused the Debian Bug report #978045, regarding apache2-bin: Immediate exit with "AH00141: Could