mythbuntu-bugs team mailing list archive

[Thomas Mashos <thomas@xxxxxxxxxx>]

On Sat, Jun 25, 2011 at 12:28 PM, Brian J. Murrell <brian@xxxxxxxxxxxxxxx>wrote:

> 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.
>
>
Mine are. Thanks for editing my quote that clearly stated when the issue
popped up and when it was fixed. Classy.


>  > 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.
>

And yet that wasn't the point of that experiment. It was to prove that the
cron jobs do not exist in the packaging. Since you didn't believe me when I
told you that I thought I'd show you.


> > 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.
>

That's how it works for most things, but we are talking about things in
/etc/. Things in that directory don't get removed usually unless a purge is
done on the package. Things in that directory are handled differently that
other files on the system. For instance, had you edited the file would you
really want some package to remove it upon  upgrade?

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

Super.

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?
>

We've talked about it. The issue is how we should handle this to adhere to
proper Ubuntu packaging policy. It was a short window where the issue popped
up before it was fixed and having the files there do not hurt anything. If I
see a large number of people reporting this issue I might think of doing
that, but until then we'll probably just leave it.


> 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
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mythbuntu-bugs
> Post to     : mythbuntu-bugs@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~mythbuntu-bugs
> More help   : https://help.launchpad.net/ListHelp
>