[mythtv-users] [mythtv-commits] Ticket #2484: Mythweb Recording Schedule Category is Broken

[Michael T. Dean]

On 10/03/06 09:50, Chris Rouch wrote:

>On 9/30/06, Michael T. Dean <mtdean at thirdcontact.com> wrote:
>  
>
>>On 09/30/06 10:42, MythTV wrote:
>>
>>>#2484: Mythweb Recording Schedule Category is Broken
>>>
>>>Changes (by dhighley):
>>>
>>> * status:  closed => reopened
>>> * resolution:  worksforme =>
>>>
>>>Comment:
>>>
>>>You know works for me is about as useless as can be. So if it works for
>>>you am I to understand that I need to rip the code apart to figure out why
>>>it is broken on my system? It worked uptil about 3 weeks ago. So under
>>>lying blocks of code might be effecting this.
>>>
>>No, actually it means you need to send an e-mail to the -users mailing
>>list to ask if anyone else sees the behavior.
>>    
>>
><snip>
>
>FWIW I'm seeing this too. I usually only use atrpms for myth, and this
>happened after I installed 0.20.
>
I'm guessing this should be fixed in recent packages from ATrpms 
(sometime on or after Oct 1).

>  However looking at the bug report,
>it seems xris has found and fixed the bug in the meantime.
>
Yes, since the original bugreport didn't fully describe the problem, 
Chris was unable to reproduce the problem.  Some sphery guy explained 
what the ticket was trying to say because he figured no one would send 
an e-mail to the -users list asking about the issue.

However, he was wrong--you actually followed through appropriately.  You 
asked about the issue on the -users list instead of:
    a) reopening the ticket with no further information
    b) reopening the ticket and arguing with the dev about why it's not 
invalid but without providing additional information
    c) reopening the ticket and telling the dev it's not your 
responsibility to track down the bugs
    d) not reopening the ticket but putting a snide comment in the 
already closed ticket
    e) ...

So, I--I mean sphery--stands corrected.  :)

> The fix as
>shown in the bug report is broken (gives php errors)
>
There was a typo fix like 2 commits later that removed the extra comma.

>, but the latest
>recording_schedules.php now seems to work as expected.
>
Which is why, when trying to fix a fixed problem (or any problem for 
that matter), you should be updating to 0.20-fixes head rather than 
trying to manually patch in selected changes (or, in this case, updating 
to the most recent ATrpms version).  After all, think of all the other 
bugs you haven't found that you'd be fixing at the same time.

In this case, the change is still new enough that ATrpms may not have 
had it when you tried to update.  So, in that case, the right thing to 
do is to ask on the -users list--which is exactly what you did.  If Axel 
doesn't yet have the updated MythWeb in a package, I'm sure he will 
soon.  :)

Thanks for doing things the right way, and I hope this information is 
helpful.  Also, I'm glad you were able to get it working--even without 
all the pieces of the puzzle.  :)

Mike