Source: scanlogd Version: 2.2.5-3.3 Severity: serious Control: submitter -1 <so...@openwall.com>
[ Turning the private messages into a public bug report with submitters consent. ] [ RC severity for DFSG violations (wrong copyright file) ] -------- Forwarded Message -------- Subject: Debian scanlogd package Date: Mon, 25 Nov 2019 16:04:15 +0100 From: Solar Designer <so...@openwall.com> To: Michael Vogt <m...@debian.org>, Scott Kitterman <sc...@kitterman.com>, Andreas Beckmann <a...@debian.org>, Joao Eriberto Mota Filho <eribe...@debian.org> Hi, Can one of you please update the scanlogd package in Debian to current upstream version 2.2.7, and drop the patching of CLK_TCK to CLOCKS_PER_SEC, which is a subtly wrong workaround previously applied in the Debian package. The actual correct value can only be reliably determined at runtime (which version 2.2.7 does), and besides CLOCKS_PER_SEC is for clock(3) whereas we use times(2). As upstream author, I am getting occasional problem reports about the Debian package, and I wonder whether issues are introduced by effects of the above change on some systems (in particular, non-x86, where these constants in the kernel are more likely to differ). Debian's patching of the historical Phrack article is especially weird, and is a misattribution of your newer changes to me. Please revert those edits (e.g. take the original article off the scanlogd homepage). While at it, please update "copyright" to reflect scanlogd's current license (it's changed since someone copied the old one into that file). Thanks, Alexander
