[mythtv-users] Ticket #3031: Recording will not commence until a PMT is

Nick Morrott knowledgejunkie at gmail.com
Thu Mar 15 13:51:37 UTC 2007

On 15/03/07, Peter Abplanalp <pta-myth at psaconsultants.com> wrote:
> ----- "Axel Thimm" <Axel.Thimm at ATrpms.net> wrote:
> > > *bleeding edge* install.  Dangerous for a newbie like myself, I
> > > agree, and frustrating for all that listen to me carp.
> >
> > What makes you think this is "bleeding edge"? There are bleeding edge
> > 0.21 mythtv packages at ATrpms' bleeding repo, but the above is not
> > that.
> the op was merely responding to what a previous poster had told him, namely that he was running a "bleeding edge" package.  turns out he isn't but he doesn't know the difference being a self proclaimed newbie.  it seems the op is having a problem and thinks/thought the problem had to do with a particular bug.  a respondent then told him that particular bug was for a particular svn version and made the assumption that the op was running that "bleeding edge" package.

It does not appear from what I can see that 12619 - if this is the
culprit - was back-ported to 0.20-fixes

i) Does the atrpms.net stable mythtv build still use the 0.20-fixes
branch? Builds after 0.20-147 had their version bumped to 0.21-xxx -
does this indicate a departure from building from 0.20-fixes and using
trunk instead? (http://atrpms.net/dist/fc6/mythtv/mythtv-suite.spec.html)

ii) atrpms.net mythtv-trunk builds have exactly the same spec update
log (http://atrpms.net/dist/fc6/mythtv-trunk/mythtv-suite.spec.html).
Is this intentional?

MythTV Official wiki:
MythTV users list archive:

"An investment in knowledge always pays the best interest." - Benjamin Franklin

More information about the mythtv-users mailing list