[mythtv-users] Time between ticket closed & patched version showing up in the daily build?

Raymond Wagner raymond at wagnerrp.com
Wed Aug 4 05:10:56 UTC 2010


  On 8/4/2010 01:07, Douglas Peale wrote:
> On 08/03/2010 09:46 PM, Jarod Wilson wrote:
>> On Wed, Aug 4, 2010 at 12:37 AM, Douglas Peale
>> <Douglas_Peale at comcast.net>  wrote:
>>> On 08/03/2010 08:49 PM, Robert McNamara wrote:
>>>> On Tue, Aug 3, 2010 at 8:47 PM, Douglas Peale<Douglas_Peale at comcast.net>  wrote:
>>>>> These tickets:
>>>>> http://svn.mythtv.org/trac/ticket/8614
>>>>> http://svn.mythtv.org/trac/ticket/8616
>>>>> claim to have been fixed six days ago.
>>>>>
>>>>> How long does it usually take for this kind of fix to get into the daily build?
>>>> Those are trunk fixes.  If you are running trunk, just svn up and
>>>> compile.  These changes were not made to .23-fixes.
>>>>
>>>> Robert
>>> I'm not running 0.23-fixes, I'm running the daily builds for 0.24 trunk via http://ppa.launchpad.net/mythbuntu/0.24/ubuntu
>>>
>>> My attempts to compile MythTV myself failed miserably.
>>>
>>> So, I'm back to my original question, how long does it usually take for a bug fix to propagate to the daily builds?
>> Um. The tickets were closed when the code was committed. It says so in
>> the tickets themselves. That would be the "(In [xyz])" part. If the
>> "daily" builds are truly daily, it should show up in them within a
>> day. But the mythtv developers have no control over mythbuntu "daily"
>> builds whatsoever.
>>
>>
> Yes, I got that the code was committed, but they did not say what version (build number?) the code got committed to

It says that right in the message that closed the ticket.  25468.  There 
is even a link to the commit log for that revision.


More information about the mythtv-users mailing list