See tracker bug 471488 for details. /usr/share/mythtv/mytharchive/scripts/mythburn.py:import Image /usr/share/mythtv/mytharchive/scripts/mythburn.py:import ImageDraw /usr/share/mythtv/mytharchive/scripts/mythburn.py:import ImageFont /usr/share/mythtv/mytharchive/scripts/mythburn.py:import ImageColor
Submitted patch upstream. Unless somebody tells me that this is going to cause some imminent problem I'll give them some time to kick this around before I patch it. Upstream ticket: http://code.mythtv.org/trac/ticket/11561
Upstream has merged the fix into master/0.27. I suspect this will work its way back into fixes/0.26. I'll wait a few more days before doing my monthly update of the fixes branch (now based on 0.26.1). If it isn't there I'll probably just incorporate the patch anyway and close this.
Any update on this?
(In reply to Mike Gilbert from comment #3) > Any update on this? This is indeed fixed in 0.27, which will be the next stable target (actually, I probably should get a STABLEREQ out on that and put out another monthly fixes). If this is causing you issues we can give some thought to what to do about 0.26. They never did backport it upstream, but there has been very little activity on 0.26 since the version in portage already.
Just following up on bugs blocking the tracker. I'm in no particular rush.
We will probably mask/remove dev-python/imaging for security bug 507982. Can you stabilize 0.27 shortly?
(In reply to Mike Gilbert from comment #6) > We will probably mask/remove dev-python/imaging for security bug 507982. Can > you stabilize 0.27 shortly? I will do so. The last patch set is nearly 30 days old, and the only thing that might give users trouble when upgrading is the logging (worse things can go wrong).
Ok amd64 stable. I put in a stable request for x86, stable masked the mythweather plugin, and put in a stable request for >dev-perl/DateTime-1 to get that stable mask removed.
Looks like this one is resolved.