Bug 550802

Summary:	Python error when first run during cron.daily
Product:	[Fedora] Fedora	Reporter:	Mike Chambers <mike>
Component:	epylog	Assignee:	Konstantin Ryabitsev <icon>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	12	CC:	icon, karl
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	epylog-1.0.3-13.fc13	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-08-05 23:26:41 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mike Chambers 2009-12-27 14:08:55 UTC

Description of problem:program shows a deprecation warning when first ran during cron.daily


Version-Release number of selected component (if applicable):epylog-1.0.3-10.fc12.noarch


How reproducible:Always


Steps to Reproduce:
1.yum install epylog
2.wait for cron.daily to run or manually run /etc/cron.daily/epylog.cron
3.
  
Actual results:/usr/lib/python2.6/site-packages/epylog/publishers.py:268: DeprecationWarning: the MimeWriter module is deprecated; use the email package instead
  import StringIO, MimeWriter


Expected results:No warnings/errors and produce the log(s) as normal.


Additional info:It seems that during the day the any other logs produced by epylog seem to be fine and no errors/warnings.  It's just during the cron.daily log that the warning/error happens.

Comment 1 Konstantin Ryabitsev 2010-02-02 17:44:26 UTC

This has been fixed upstream. The upcoming version 1.0.4 should fix this problem.

Comment 2 Mike Chambers 2010-05-31 13:31:52 UTC

When are we gonna see the .4 version? Have switched to running F14/rawhide currently and still not upgraded.

Comment 3 karl kleinpaste 2010-07-08 11:01:01 UTC

Another echo of "when"?

This was reported at Christmas.  It's been marked "release pending" for 5 months.  Oh?  That's nearly the entire average life cycle of a whole Fedora release (6 months).  For exactly how long does a release have to be pending before we stop having to deal with what amounts to one more piece of useless spam every single day generated by every single system administered?

Comment 4 Konstantin Ryabitsev 2010-07-16 18:22:21 UTC

You are right, this is my fault. I will patch it in the RPM instead of waiting for the next release -- it may have stalled again.

Comment 5 Fedora Update System 2010-07-16 18:47:08 UTC

epylog-1.0.3-13.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/epylog-1.0.3-13.fc13

Comment 6 Fedora Update System 2010-07-16 19:02:24 UTC

epylog-1.0.3-13.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/epylog-1.0.3-13.fc12

Comment 7 karl kleinpaste 2010-07-16 19:20:20 UTC

Very cool.  Thanx much, it is appreciated.

Comment 8 Fedora Update System 2010-08-05 23:26:36 UTC

epylog-1.0.3-13.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2010-08-05 23:41:46 UTC

epylog-1.0.3-13.fc13 has been pushed to the Fedora 13 stable repository.  If problems still persist, please make note of it in this bug report.