Your message dated Thu, 18 Oct 2018 13:26:16 +0000
with message-id <[email protected]>
and subject line [[email protected]: [piuparts] htdocs/news.tpl: confirm
#582630 has been fixed.]
has caused the Debian Bug report #582630,
regarding logrotate fails on missing logfiles even when it shouldn't
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
582630: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582630
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
package: logrotate
version: 3.7.8-6
x-debbugs-cc: [email protected], [email protected]
Hi,
piuparts.debian.org since some time tests for failing logrotate runs of
packages, the results are at
http://piuparts.debian.org/sid/logrotate_error_after_removal_error.html
Looking at http://piuparts.debian.org/sid/fail/munge_0.5.9-2.log the relevant
lines are:
0m10.8s DEBUG: Starting command:
['chroot', '/org/piuparts.debian.org/tmp/tmpk8ojpT', '/usr/sbin/logrotate',
'/etc/logrotate.d/munge']
0m10.8s DUMP:
error: error accessing /var/log/munge: No such file or directory
error: /etc/logrotate.d/munge:1 glob failed for /var/log/munge/*.log
error: found error in /var/log/munge/*.log , skipping
Now let's look at munges logrotate file:
$ cat /etc/logrotate.d/munge
/var/log/munge/*.log {
rotate 12
weekly
compress
missingok
postrotate
/usr/sbin/invoke-rc.d --quiet munge force-reload >/dev/null
endscript
}
So when piuparts tests the package it doesn't run munge (in this example) and
thus /var/log/munge/ never gets created...
I have come to think this is a bug in logrotate as the config file
specifies "missingok" and the log file is missing. Do you agree?
cheers,
Holger
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
--- Begin Message ---
;tl;dr: I can confirm this bug has been fixed.
----- Forwarded message from Holger Levsen <[email protected]> -----
Date: Thu, 18 Oct 2018 13:21:01 +0000
From: Holger Levsen <[email protected]>
To: [email protected]
Subject: [Piuparts-devel] [Git][debian/piuparts][develop] htdocs/news.tpl:
confirm #582630 has been fixed.
List-Id: Piuparts development list <piuparts-devel.alioth-lists.debian.net>
Reply-To: [email protected]
Holger Levsen pushed to branch develop at Debian / piuparts
Commits:
d7793dfd by Holger Levsen at 2018-10-18T13:18:51Z
htdocs/news.tpl: confirm #582630 has been fixed.
Signed-off-by: Holger Levsen <[email protected]>
- - - - -
3 changed files:
- debian/changelog
- htdocs/news.tpl
- known_problems/logrotate_error_after_removal_error.conf
Changes:
=====================================
debian/changelog
=====================================
@@ -44,6 +44,7 @@ piuparts (0.93) UNRELEASED; urgency=medium
branch. Explain to always include a debian/changelog entry with patches.
Explain to always test patches and to explain that testing has happened.
* htdocs/bug_howto.tpl: some improvements, it's been some years.
+ * htdocs/news.tpl: confirm #582630 has been fixed.
-- Holger Levsen <[email protected]> Sat, 22 Sep 2018 15:32:55 +0200
=====================================
htdocs/news.tpl
=====================================
@@ -12,7 +12,7 @@
</tr>
<tr class="normalrow">
<td class="contentcell2">
- <b>2018-08-28</b>: Enable the logrotate test (temporarily) again, to
check whether <a href="https://bugs.debian.org/582630";
target="_blank">#582630</a> really has been fixed...
+ <b>2018-08-28</b>: Enable the logrotate test again to confirm <a
href="https://bugs.debian.org/582630"; target="_blank">#582630</a> has been
fixed.
</td>
</tr>
<tr class="normalrow">
=====================================
known_problems/logrotate_error_after_removal_error.conf
=====================================
@@ -7,6 +7,6 @@ ISSUE=0
HEADER='Packages with failed logs because a logrotate script has output and/or
exits with error after the package has been removed'
HELPTEXT='
<p>
-Most of these packages are probably not buggy but rather affected by <a
href="https://bugs.debian.org/582630"; target=_blank>#582630</a>. It is being
considered to disable this check...
+The logrotate configuration cause output and/or exit with error when the
package has been removed but not purged.
</p>
'
View it on GitLab:
https://salsa.debian.org/debian/piuparts/commit/d7793dfdf187e8d9927512f3c8b88e94192aaaca
--
View it on GitLab:
https://salsa.debian.org/debian/piuparts/commit/d7793dfdf187e8d9927512f3c8b88e94192aaaca
You're receiving this email because of your account on salsa.debian.org.
_______________________________________________
Piuparts-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/piuparts-devel
----- End forwarded message -----
--
cheers,
Holger
-------------------------------------------------------------------------------
holger@(debian|reproducible-builds|layer-acht).org
PGP fingerprint: B8BF 5413 7B09 D35C F026 FE9D 091A B856 069A AA1C
signature.asc
Description: PGP signature
--- End Message ---
