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.
This has been fixed upstream. The upcoming version 1.0.4 should fix this problem.
When are we gonna see the .4 version? Have switched to running F14/rawhide currently and still not upgraded.
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?
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.
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
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
Very cool. Thanx much, it is appreciated.
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.
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.