There is a bug in bodhi's new pre-push sanity checker that causes the
mashing lockfile to get wiped out when a push is resumed and the sanity
check fails.
I would like to push this patch out to releng2 and relepel01 only.
--- a/bodhi/masher.py
+++ b/bodhi/masher.py
@@ -641,7 +641,6 @@ class MashTask(Thread):
if self.resume:
if not self.safe_to_resume():
log.error("safe_to_resume failed! -- aborting")
- self._unlock()
masher.done(self)
return
else:

Right now, the meetbot logs are organized as:
<channel>/<date>/<meetingname>.log
However, that means that someone who (for instance) wants to browse old
FESCo meetings, needs to know:
1) that it's on #fedora-meeting
2) that it's currently on Wednesdays
3) that at points in the past, it's been on Tuedays, and before that Fridays
This can make browsing the meeting logs more difficult than it could be.
How hard would it be to set up an alternate heirarchy that is:
<meetingname>/<date>/<meetingname>.log
without necessarily worrying about what channel that it's on?
Bill

Due to the many reboots it looks like the /var/log/httpd on the fas
servers are in a 'weird' state. Some of the files were compressed and
some were sort of compressed when the box rebooted itself. [In fact it
looks like the reboots seem to occur often during logrotate. Since the
files have not been compressed, the logrotate cleanup hasn't removed
them. I would like to compress and let logrotate remove all the old
ones.
--
Stephen J Smoogen.
“The core skill of innovators is error recovery, not failure avoidance.”
Randy Nelson, President of Pixar University.
"We have a strategic plan. It's called doing things.""
— Herb Kelleher, founder Southwest Airlines