<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Tue, Apr 17, 2018 at 12:24 PM Stephen Worthington <<a href="mailto:stephen_agent@jsw.gen.nz">stephen_agent@jsw.gen.nz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Tue, 17 Apr 2018 14:51:25 +0000, you wrote:<br>
<br>
>On Tue, Apr 17, 2018 at 3:04 AM John Pilkington <<a href="mailto:johnpilk222@gmail.com" target="_blank">johnpilk222@gmail.com</a>><br>
>wrote:<br>
><br>
>> On 17/04/18 02:36, Stephen Worthington wrote:<br>
>> > On Mon, 16 Apr 2018 23:35:02 +0000, you wrote:<br>
>> ><br>
>> ><br>
>> >> Is there a way that I can make a frontend match a particular version of<br>
>> a<br>
>> >> backend? I had created a backend a few months back but never got around<br>
>> >> making a frontend. SO - if I were to do this - I am thinking why not<br>
>> just<br>
>> >> make a frontend on an already made backend?<br>
>> >><br>
>> >> It's a few months old, so I may need to do a complete refresh but<br>
>> wanted to<br>
>> >> see if I should go that way or should I make a brand new install?<br>
>> >><br>
>> >> I have always used centos so that's where I would be going unless<br>
>> someone<br>
>> >> tells me otherwise.<br>
>> ><br>
>> > I do not do Centos, but if it has packages for MythTV, just install<br>
>> > the frontend packages. MythTV packages come as a set with matching<br>
>> > frontend and backend. And mythfrontend will tell you if it tries to<br>
>> > connect to an incompatible backend. Both the database and the<br>
>> > communications protocols are versioned and the versions are checked on<br>
>> > startup.<br>
>><br>
>> Look at the rpmfusion repo<br>
>><br>
>><br>
>> <a href="http://download1.rpmfusion.org/free/el/updates/6/x86_64/mythtv-0.26.1-5.el6.x86_64.rpm" rel="noreferrer" target="_blank">http://download1.rpmfusion.org/free/el/updates/6/x86_64/mythtv-0.26.1-5.el6.x86_64.rpm</a></blockquote><div><br></div><div>I tried going to the link but it only has 0.29 - went up to
<a href="http://download1.rpmfusion.org/free/el/updates/7/x86_64/m/mythtv-29.1-15.20180228.8.g925ceea0fb.el7.x86_64.rpm" rel="noreferrer" target="_blank" style="color:rgb(17,85,204);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255)">http://download1.rpmfusion.org/free/el/updates/7/x86_64/m/</a><span style="font-size:12.8px"> but it only has current ones</span></div><div><br></div><div>Am I looking at the wrong place? </div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
>><br>
>> is the metapackage that should bring in the 'current' build for Centos<br>
>> 6. For Centos 7:<br>
>><br>
><br>
>the version I have (created 8/17) is:<br>
><br>
> mythbackend --version<br>
>Please attach all output as a file in bug reports.<br>
>MythTV Version : v28.0-104-g3930f5d<br>
>MythTV Branch : fixes/0.28<br>
>Network Protocol : 88<br>
>Library API : 0.28.20161120-1<br>
>QT Version : 5.6.1<br>
>Options compiled in:<br>
> linux release use_hidesyms using_alsa using_oss using_pulse<br>
>using_pulseoutput using_backend using_bindings_perl using_bindings_python<br>
>using_bindings_php using_crystalhd using_dvb using_firewire using_frontend<br>
>using_hdhomerun using_vbox using_ceton using_hdpvr using_ivtv<br>
>using_joystick_menu using_libcrypto using_libdns_sd using_libfftw3<br>
>using_libxml2 using_lirc using_mheg using_opengl using_opengl_video<br>
>using_opengl_themepainter using_qtwebkit using_qtscript using_qtdbus<br>
>using_taglib using_v4l2 using_x11 using_xrandr using_xv<br>
>using_systemd_notify using_bindings_perl using_bindings_python<br>
>using_bindings_php using_freetype2 using_mythtranscode using_opengl<br>
>using_vaapi using_vdpau using_ffmpeg_threads using_mheg using_libass<br>
>using_libxml2<br>
><br>
>Here's the hardware config of my backend - someone mentioned the need for<br>
>newer box.<br>
><br>
>#lscpu<br>
><br>
>Architecture: x86_64<br>
>CPU op-mode(s): 32-bit, 64-bit<br>
>Byte Order: Little Endian<br>
>CPU(s): 4<br>
>On-line CPU(s) list: 0-3<br>
>Thread(s) per core: 1<br>
>Core(s) per socket: 4<br>
>Socket(s): 1<br>
>NUMA node(s): 1<br>
>Vendor ID: GenuineIntel<br>
>CPU family: 6<br>
>Model: 94<br>
>Model name: Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz<br>
>Stepping: 3<br>
>CPU MHz: 3311.994<br>
>BogoMIPS: 6623.98<br>
>Hypervisor vendor: KVM<br>
>Virtualization type: full<br>
>L1d cache: 32K<br>
>L1i cache: 32K<br>
>L2 cache: 256K<br>
>L3 cache: 8192K<br>
>NUMA node0 CPU(s): 0-3<br>
<br>
That looks fine for a backend box, as long as it has enough RAM.<br>
<br>
><br>
><br>
>><br>
>><br>
>> <a href="http://download1.rpmfusion.org/free/el/updates/7/x86_64/m/mythtv-29.1-15.20180228.8.g925ceea0fb.el7.x86_64.rpm" rel="noreferrer" target="_blank">http://download1.rpmfusion.org/free/el/updates/7/x86_64/m/mythtv-29.1-15.20180228.8.g925ceea0fb.el7.x86_64.rpm</a><br>
><br>
><br>
>I need the same 0.28/fixes correct (for the frontend)?<br>
<br>
Yes, although any 0.28 frontend version should be able to talk to any<br>
0.28 backend. But it is best to use exactly the same versions for the<br>
frontend and backend.<br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://lists.mythtv.org/mailman/listinfo/mythtv-users" rel="noreferrer" target="_blank">http://lists.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<a href="http://wiki.mythtv.org/Mailing_List_etiquette" rel="noreferrer" target="_blank">http://wiki.mythtv.org/Mailing_List_etiquette</a><br>
MythTV Forums: <a href="https://forum.mythtv.org" rel="noreferrer" target="_blank">https://forum.mythtv.org</a><br>
</blockquote></div><br clear="all"><div><br></div><br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"></div></div>