mythbuntu-bugs team mailing list archive

["Brian J. Murrell" <brian@xxxxxxxxxxxxxxx>]

On 11-06-25 02:08 PM, Thomas Mashos wrote:
> thomas@ares:~$ dpkg -S /etc/cron.hourly/*
> mythvideo: /etc/cron.hourly/mythvideo
> thomas@ares:~$
> 
> mythtv-frontend and mythtv-backend are 2:0.24.1+fixes.20110531.3657f31

Who's mythtv-{front,back}end are 2:0.24.1+fixes.20110531.3657f31?  I
clearly demonstrated above that mine are currently
2:0.24.1+fixes.20110625.30993d6-0ubuntu0mythbuntu3.

> Download both
> mythtv-backend_0.24.1+fixes.20110625.30993d6-0ubuntu0mythbuntu3_amd64.deb
> mythtv-frontend_0.24.1+fixes.20110625.30993d6-0ubuntu0mythbuntu3_amd64.deb

I don't need to.  I have them already since I have them installed.

> Run 'dpkg --contents to see what files are inside the deb file. Filter by
> cron if you deem necessary'
> thomas@poseidon:~/Downloads$ dpkg --contents
> mythtv-backend_0.24.1+fixes.20110625.30993d6-0ubuntu0mythbuntu3_amd64.deb |
> grep cron
> thomas@poseidon:~/Downloads$ dpkg --contents
> mythtv-frontend_0.24.1+fixes.20110625.30993d6-0ubuntu0mythbuntu3_amd64.deb |
> grep cron
> thomas@poseidon:~/Downloads$
> 
> See, not in the packages. You however still have them because as I said,
> they are left over from old packages and not removed because they exist in
> /etc/

That's just stupid behavior on dpkg's part.  Seriously.  If a package
includes a file in a given release and the file is removed from the
package in a subsequent release, the file should be removed when the
subsequent package is installed.

Clearly those cron jobs should not be there so I will remove them.

Given that dpkg is clearly broken in this regard, why not have removing
those jobs in the postinstall script of subsequent packages so that
everyone does not fall into this trap?

b.

-- 
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to mythtv in Ubuntu.
https://bugs.launchpad.net/bugs/799663

Title:
  run-parts: /etc/cron.hourly/mythvideo exited with return code 1

Status in “mythtv” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: mythtv

  Once again, mythvideo's hourly cron job in the 0.24-fixes stream is
  exiting with an error:

  run-parts: /etc/cron.hourly/mythvideo exited with return code 1

  The tail end of my /var/log/mythtv/jamu.log reads:

  ! Error: Jamu must be run on a MythTV backend. Local host (pvr) is not
  a MythTV backend.

  With any -M option Jamu must be run on a MythTV backend
  ! Warning - Unexpected response to ANN on 10.75.22.2:6543 - 

  ! Error: Jamu must be run on a MythTV backend. Local host (pvr) is not
  a MythTV backend.

  With any -M option Jamu must be run on a MythTV backend
  ! Warning - Unexpected response to ANN on 10.75.22.2:6543 - 

  ! Error: Jamu must be run on a MythTV backend. Local host (pvr) is not
  a MythTV backend.

  With any -M option Jamu must be run on a MythTV backend
  ! Warning - Unexpected response to ANN on 10.75.22.2:6543 - 

  ! Error: Jamu must be run on a MythTV backend. Local host (pvr) is not
  a MythTV backend.

  With any -M option Jamu must be run on a MythTV backend
  ! Warning - Unexpected response to ANN on 10.75.22.2:6543 - 

  The host "pvr" is in fact a MythTV backend so something is obviously
  wrong.

  On a slave backend machine (slave not actually running at this point)
  I am seeing:

  run-parts: /etc/cron.hourly/mythtv-backend exited with return code 2
  run-parts: /etc/cron.hourly/mythtv-frontend exited with return code 1

  When the mythtv-backend hourly cron job runs and exits with an error,
  the /var/log/mythtv/jamu.log on this host reports:

  /usr/bin/python: can't open file '/usr/share/doc/mythtv-
  backend/contrib/metadata/jamu.py': [Errno 2] No such file or directory

  When the mythtv-frontend hourly cron job runs and exits with an error,
  the /var/log/mythtv/jamu.log on this host reports:

  ! Error: Jamu must be run on a MythTV backend. Local host (pc) is not
  a MythTV backend.

  With any -M option Jamu must be run on a MythTV backend
  ! Warning - Failed to connect to backend at 10.75.22.1:6543

  Which is correct.  So why is this job expecting the machine to be a
  backend when it's being run from the mythtv-frontend hourly cron job.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/799663/+subscriptions