[mythtv-users] recent mythbackend crashing
Eyal Lebedinsky
eyal at eyal.emu.id.au
Wed Jun 8 05:03:38 UTC 2022
On 08/06/2022 00.06, Eyal Lebedinsky wrote:
>
>
> On 07/06/2022 21.32, Klaas de Waal wrote:
>>
>>
>> On Tue, 7 Jun 2022 at 04:39, Gary Buhrmaster <gary.buhrmaster at gmail.com <mailto:gary.buhrmaster at gmail.com>> wrote:
>>
>> On Mon, Jun 6, 2022 at 11:29 PM Eyal Lebedinsky <eyal at eyal.emu.id.au <mailto:eyal at eyal.emu.id.au>> wrote:
>>
>> > Now we really need a fix, or is there a workaround?
>>
>> The fix was backported. Have you updated to the
>> latest 32/fixes? You may need to build your own
>> as some packagers will not update their package(s)
>> automatically (you will need to contact your
>> packager to see if, and when, they might upgrade).
>>
>>
>>
>> From this:
>>
>> and on f36 it is
>> mythtv-backend-32.0-1.30.20220510git26079f815a.fc36.x86_64
>>
>> I understand that your package is created on 10 May 2022 from which I conclude that your package provider does update the package regularly.
>> The bug fix commit was on 5 June, so If, after updating, the date in the package name is after 20220605 it should contain the fix.
>
> The packages comes from rpmfusion and there the latest version is
> https://koji.rpmfusion.org/koji/packageinfo?packageID=162
> mythtv-backend-32.0-1.30.20220510git26079f815a.fc3{4,6}.x86_64
> So I need to wait, even after I upgrade to f36. I do not know how rpmfusion decides when to update a package.
>
> Maybe I should ping their admin and ask.
Now registered
https://bugzilla.rpmfusion.org/show_bug.cgi?id=6327
with a link to the discussion here.
BTW, while I was having a walk just now there were 26 aborts in about 30m.
Eyal
>> Klaas.
--
Eyal Lebedinsky (eyal at eyal.emu.id.au)
More information about the mythtv-users
mailing list