** Package changed: mythvideo (Ubuntu) = mythplugins (Ubuntu)
--
run-parts: /etc/cron.hourly/mythvideo exited with return code 1
https://bugs.launchpad.net/bugs/502051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
So after talking this over with the Jamu author, he suspects this is
caused by prolonged outtages of tvdb. When a second instance of jamu
spawns for the hourly cron job, it sees another running instance and
causes an exit(1) code.
He will make this change upstream so that it will exit(0) instead
This is an upstream problem. The code uses sys.exit(True) where is
should be using False and vice vera.
eg
# Check if this is a Scheduled and Recorded graphics download
request
if self.config['mythtv_watched']:
This has been fixed upstream http://svn.mythtv.org/trac/ticket/7560
--
run-parts: /etc/cron.hourly/mythvideo exited with return code 1
https://bugs.launchpad.net/bugs/502051
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
That change was committed 7 weeks ago. This build that the reporter is
running is quite fresh. He's also provided a last functional build to
base a comparison on from his broken one.
On Sat, Jan 2, 2010 at 22:00, John Ferlito jo...@inodes.org wrote:
This has been fixed upstream
Running the cronjob manually doesn't give more.
[..]
sudo run-parts --report /etc/cron.hourly
run-parts: /etc/cron.hourly/mythvideo exited with return code 1
[..]
Running /etc/cron.hourly/mythvideo manually doesn't give anything.
[..]
sudo /etc/cron.hourly/mythvideo
[..]
Looking at
The last functional version was 0.22.0+fixes22564-0ubuntu1 (karmic) I
think.
At some point I can find this in the jamu.log. This could be a hint.
[..]
! Error: An instance of Jamu (-MW) is already running only one instance can run
at a time.
One of the meta data sources may be off-line or very
