Bug#1082087: chkrootkit's autopkg tests fail on amd64, arm64 and riscv64

2024-09-23 Thread Richard Lewis
control: tags -1 pending bug is fixed in the git repos On Sat, 21 Sep 2024, 23:21 Richard Lewis, < richard.lewis.deb...@googlemail.com> wrote: > On Thu, 19 Sept 2024 at 08:57, Matthias Klose wrote: > > > > On 18.09.24 20:03, Richard Lewis wrote: > > > Thanks, t

Bug#1082087: chkrootkit's autopkg tests fail on amd64, arm64 and riscv64

2024-09-21 Thread Richard Lewis
On Thu, 19 Sept 2024 at 08:57, Matthias Klose wrote: > > On 18.09.24 20:03, Richard Lewis wrote: > > Thanks, this is a consequence of the 64 bit time_t transition which has > > replaced the wtmp/utmp/lastlog files > > the 64bit time_t transition affected 32bit architecture

Bug#1082087: chkrootkit's autopkg tests fail on amd64, arm64 and riscv64

2024-09-18 Thread Richard Lewis
Thanks, this is a consequence of the 64 bit time_t transition which has replaced the wtmp/utmp/lastlog files i am a little surprised those running the transition did not file bugs against affected packages when the new packages were uploaded, (especially as i suggested chkrootkit would be affected

Bug#1042049: lintian: FTBFS: 3 tests failed

2023-12-11 Thread Richard Lewis
On Thu, 7 Dec 2023 22:05:29 +1300 Vladimir Petko wrote: > As of today there are more test failures: > Test Summary Report > --- > debian/test-out/eval/checks/documentation/manual/manpage-errors-from-man/generic.t > debian/test-out/eval/checks/documentation/manual/surplus-manpage

Bug#1053898: Hardening rsyslog.service breaks debian/tests/logcheck autopkgtest

2023-10-14 Thread Richard Lewis
On Fri, 13 Oct 2023 at 20:27, Michael Biebl wrote: > It turns out that `PrivateTmp=yes` breaks the logcheck autopkgtest. i think the test tells rsyslog to write to /tmp and then calls logcheck on the output outside the unit. But the PrivateTmp=true means rsyslog is actually writing to [somewhere

Bug#1039591: logcheck: prompting due to modified conffiles which were not modified by the user: /etc/logcheck/header.txt

2023-08-06 Thread Richard Lewis
On Wed, 12 Jul 2023 at 12:20, Mathias Gibbens wrote: > > Andreas, thanks for the report, and Richard, thanks for your work as > well. I think the changes look good, and if there's no other concerns > I'll merge the salsa MR, and upload a new version to unstable. Once > that's done, I'll also fil

Bug#1039591: logcheck: prompting due to modified conffiles which were not modified by the user: /etc/logcheck/header.txt

2023-07-07 Thread Richard Lewis
https://salsa.debian.org/debian/logcheck/-/merge_requests/18 now has the patch for this On Thu, 29 Jun 2023 at 21:36, Richard Lewis wrote: > > I think you might be missing one md5sum - I found 4 versions in the git repos > > # > for x in $(git log debian/h

Bug#1039591: logcheck: prompting due to modified conffiles which were not modified by the user: /etc/logcheck/header.txt

2023-06-29 Thread Richard Lewis
I think you might be missing one md5sum - I found 4 versions in the git repos # for x in $(git log debian/header.txt | awk '/commit/{print $2}'); do git show $x:debian/header.txt | md5sum ; done d9206d89f2f8d85d346a23da90459862 - a32fc12d69628d96756fd3af3f8b3ecd - dbc1e8d136

Bug#1039591: logcheck: prompting due to modified conffiles which were not modified by the user: /etc/logcheck/header.txt

2023-06-29 Thread Richard Lewis
On Tue, 27 Jun 2023, 22:01 Andreas Beckmann, wrote: > Control: tag -1 patch > > On 27/06/2023 19.21, Richard Lewis wrote: > > header.txt has not been modified since 2015. > > I've found three versions (with sightly different spelling): > * lenny > * squeeze, whe

Bug#1039591: logcheck: prompting due to modified conffiles which were not modified by the user: /etc/logcheck/header.txt

2023-06-27 Thread Richard Lewis
header.txt has not been modified since 2015. it is a simple yext file that is installed with debian/logcheck.install the only change is that it used to be installed into /usr/share but got moved to /etc to be a conffile in 2021. This didnt trigger any piuparts issues and there was no change to th

Bug#1031786: logcheck: Filtering not working with entries from journald

2023-02-22 Thread Richard Lewis
On Wed, 22 Feb 2023, 17:51 Helge Kreutzmann, wrote: > Package: logcheck > Version: 1.4.1 > Severity: grave > Justification: renders package unusable > > The change for #1025719 broke logcheck massively. > > I've extensivly tuned logcheck files which nicely filter out lots of > messages (see stati

Bug#1002522: chkrootkit: autopkgtest failure everywhere except amd64

2021-12-24 Thread Richard Lewis
control: fixed -1 0.55-4 thanks On Thu, 23 Dec 2021 21:36:11 +0100 Paul Gevers wrote: > So let's assume the results will be OK, then you can just close this bug > with fixed version 0.55-4 and ignore it further. Thanks, it seems 0.55-4 is indeed testing fine everywhere, according to the latest

Bug#999082: offering to help with checksecurity

2021-12-14 Thread Richard Lewis
Hi, I don't know how much attention this package gets, but i still use it The repository at https://salsa.debian.org/rpil2/checksecurity/ includes a 'modernised' 3-line debian/rules (plus other things) that would, i think, fix this bug. That repository includes all the history that git-buildpac

Bug#948706: Polite ping

2020-06-20 Thread Richard Lewis
Is there a recommended alternative way to implement greylisting with exim? On Wed, 3 Jun 2020 at 14:18, Eugene Berdnikov wrote: > > Hi. > > On Wed, Jun 03, 2020 at 02:01:33PM +0200, Benedikt Spranger wrote: > > Hi, > > > > are there any updates or is more help needed? > > Unfortunately, this pa

Bug#306595: tetex-bin: postinst failure with jadetex and xmltex

2005-04-27 Thread Richard Lewis
"Laurent Bonnaud" <[EMAIL PROTECTED]> writes: > here is the problem: > > Setting up tetex-bin (3.0-3) ... > Merging information from /etc/texmf/texmf.d/ into /etc/texmf/texmf.cnf ... > done > Regenerating /var/lib/texmf/web2c/fmtutil.cnf ... done > Running fmtutil-sys. This may take some time. ..

Bug#294895: dependency problems prevent configuration of a2ps

2005-02-11 Thread Richard Lewis
Package: a2ps Version: 1:4.13b-4.3 Severity: grave Justification: renders package unupgradeable (I hope the severity is appropriate; it's not exactly hard to fix the problem but clearly something needs to be fixed) When doing a "apt-get dist-upgrade" (from version 1:4.13b-4) I got the following e