mythvideo/jamu should only run on backends

Bug #507436 reported by Brian J. Murrell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mythplugins (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: mythplugins

Right in the jamu code there is the following check:

if not mythdb.getSetting('BackendServerIP', hostname = localhostname):
  sys.stderr.write(u"\n! Error: Jamu must be run on a MythTV backend. Local host (%s) is not a MythTV backend.\n" % localhostname)
 sys.exit(1)

and yet mythvideo installs a cron job in cron.hourly which executes the script with the above check in it. mythvideo is typically installed on frontends, not backends so /etc/cron.hourly/mythvideo, as it is currently, does not belong in the mythvideo package.

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :

Ahh. There is a cron.daily cron job which is equally invalid.

Revision history for this message
Mario Limonciello (superm1) wrote : Re: [Bug 507436] [NEW] mythvideo/jamu should only run on backends

The problem is that this ships in the myth plugins package not mythtv
package. Not sure there is much we can do about it because of that.

On 01/14/2010, Brian J. Murrell <email address hidden> wrote:
> Ahh. There is a cron.daily cron job which is equally invalid.
>
> --
> mythvideo/jamu should only run on backends
> https://bugs.launchpad.net/bugs/507436
> You received this bug notification because you are a member of Mythbuntu
> Bug Team, which is subscribed to mythplugins in ubuntu.
>

--
Sent from my mobile device

Mario Limonciello
<email address hidden>

Revision history for this message
Brian J. Murrell (brian-interlinx) wrote :

On Thu, 2010-01-14 at 14:00 +0000, Mario Limonciello wrote:
> The problem is that this ships in the myth plugins package not mythtv
> package.

So is the installation of these cron jobs a direct result of "make
install" in the myth package? i.e. is this a myth packaging error or a
{myth,u}buntu packaging error?

> Not sure there is much we can do about it because of that.

Well, at a minimum, the cron script could ask some sort of "am in the
backend" question and bail out if not. But you know, even that I don't
particularly agree with, because this script is packaged with mythvideo,
and (AFAIU) mythvideo {w,sh}ould not be installed on a pure (i.e. no FE)
backend machine.

But then on the hand again, does "Video" metadata belong on the backend
if it's a frontend package?

I think there is a severe personality disorder deep in this Jamu stuff.
That or I am just not understanding it correctly.

Revision history for this message
Mario Limonciello (superm1) wrote :

This bug has been fixed in the -fixes packaging bzr #107. This will be available in the Mythbuntu autobuilds at http://www.mythbuntu.org/auto-builds for any build greater than r23527. This bug will be automatically closed when a build containing this fix is uploaded to an Ubuntu development release (currently Lucid Lynx).

Changed in mythplugins (Ubuntu):
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mythplugins - 0.22.0+fixes23527-0ubuntu1

---------------
mythplugins (0.22.0+fixes23527-0ubuntu1) lucid; urgency=low

  * New snapshot (r23527)
  * debian/control:
    - Recommends for python-imaging (LP: #500313)
  * debian/mythweb.postinst:
    - Check that a 'default' site is available before attempting to
      make a new one. (LP: #462405)
    - Check that the new site to enable exists before enabling.
  * debian/mythvideo.cron.*:
    - Redirect all output on stderr into the log file too (LP: #487880)
    - Check that a frontend is installed to determine if this job should
      be ran. (LP: #507436)
  * debian/mythvideo.logrotate:
    - Supply a logrotate script for jamu.

  [ Nicholas J Kreucher ]
  * debian/mythvideo.cron.*:
    - Use getent instead of grep /etc/passwd (LP: #511858)
 -- Mario Limonciello <email address hidden> Sun, 14 Feb 2010 19:24:14 -0600

Changed in mythplugins (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.