-------- Forwarded Message -------- Subject: Re: Debian scanlogd package Date: Mon, 25 Nov 2019 16:07:46 +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>
On Mon, Nov 25, 2019 at 04:04:15PM +0100, Solar Designer wrote: > 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). More on this issue: https://www.openwall.com/lists/xvendor/2006/04/17/1 Debian's wrong fix made instead of simply updating to new upstream version at the time (would be 2.2.6): scanlogd (2.2.5-2.1) unstable; urgency=medium * Non-maintainer upload during BSP. * Substitute CLK_TCK with CLOCKS_PER_SEC in scanlogd.c and P53-13 to avoid FTBFS with new glibc. (Closes: #421085). * Use now dh_installman instead of dh_installmanpages -- Mario Iseli <ad...@marioiseli.com> Thu, 17 May 2007 20:30:11 +0200 > 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
