[mythtv-users] Upgrade surprise

Stephen Worthington stephen_agent at jsw.gen.nz
Sat Oct 18 11:50:17 UTC 2014


On Fri, 17 Oct 2014 23:15:16 -0700, you wrote:

>
>On 10/17/2014 07:00 AM, Michael Watson wrote:
>> On 17/10/2014 4:53 PM, Mike Carron wrote:
>>>
>>> On 10/16/2014 04:15 PM, Thomas Mashos wrote:
>>>>
>>>>
>>>> On Oct 16, 2014 3:26 PM, "Mike Carron" <jmcarron at starstream.net 
>>>> <mailto:jmcarron at starstream.net>> wrote:
>>>> >
>>>> > I installed Mythbuntu 12.04.1 on a new MBE, set the repository in 
>>>> MCC to 0.27 and did sudo apt-get update && sudo apt-get upgrade in 
>>>> order to get the MythTV version from 0.25 to 0.27. These are the 
>>>> final lines from that process.
>>>> >
>>>> >    Preparing to replace php-mythtv
>>>> >    2:0.25.2+fixes.20120802.46cab93-0ubuntu1 (using
>>>> > 
>>>>  .../php-mythtv_2%3a0.27.4+fixes.20141015.e4f65c8-0ubuntu0mythbuntu1_all.deb)
>>>> >    ...
>>>> >    Unpacking replacement php-mythtv ...
>>>> >    Setting up libmyth-python
>>>> >    (2:0.27.4+fixes.20141015.e4f65c8-0ubuntu0mythbuntu1) ...
>>>> >    Setting up libmythtv-perl
>>>> >    (2:0.27.4+fixes.20141015.e4f65c8-0ubuntu0mythbuntu1) ...
>>>> >    Setting up mythtv-database
>>>> >    (2:0.27.4+fixes.20141015.e4f65c8-0ubuntu0mythbuntu1) ...
>>>> >    Setting up mythtv-backend-master
>>>> >    (2:0.27.4+fixes.20141015.e4f65c8-0ubuntu0mythbuntu1) ...
>>>> >    Setting up mythtv-theme-mythbuntu
>>>> >    (2:0.27.4+fixes.20141015.e4f65c8-0ubuntu0mythbuntu1) ...
>>>> >    Setting up php-mythtv
>>>> >    (2:0.27.4+fixes.20141015.e4f65c8-0ubuntu0mythbuntu1) ...
>>>> >
>>>> >
>>>> > I then did mythbackend -- version in order to confirm that MythTV 
>>>> had been upgraded to 0.27.4. The result is:
>>>> >
>>>> >    Please attach all output as a file in bug reports.
>>>> >    MythTV Version : v0.25.2-15-g46cab93
>>>> >    MythTV Branch : fixes/0.25
>>>> >    Network Protocol : 72
>>>> >    Library API : 0.25.20120506-1
>>>> >    QT Version : 4.8.1
>>>> >    Options compiled in:
>>>> >      linux profile use_hidesyms using_alsa using_oss using_pulse
>>>> >    using_pulseoutput using_backend using_bindings_perl
>>>> >    using_bindings_python using_bindings_php using_crystalhd using_dvb
>>>> >    using_firewire using_frontend using_hdhomerun using_ceton
>>>> >    using_hdpvr using_iptv using_ivtv using_joystick_menu using_libcec
>>>> >    using_libcrypto using_libdns_sd using_libxml2 using_lirc 
>>>> using_mheg
>>>> >    using_opengl_video using_qtwebkit using_qtscript using_qtdbus
>>>> >    using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl
>>>> >    using_bindings_python using_bindings_php using_mythtranscode
>>>> >    using_opengl using_vaapi using_vdpau using_ffmpeg_threads 
>>>> using_live
>>>> >    using_mheg using_libass using_libxml2
>>>> >
>>>> > Should I assume the upgrade to 0.27.4 did not actually happen?
>>>> >
>>>> > --
>>>> > mike
>>>> >
>>>> > _______________________________________________
>>>> > mythtv-users mailing list
>>>> > mythtv-users at mythtv.org <mailto:mythtv-users at mythtv.org>
>>>> > http://www.mythtv.org/mailman/listinfo/mythtv-users
>>>> > http://wiki.mythtv.org/Mailing_List_etiquette
>>>> > MythTV Forums: https://forum.mythtv.org
>>>>
>>>> When upgrading major MythTV versions, you want "apt-get 
>>>> dist-upgrade", not just "apt-get upgrade"
>>>>
>>> ***
>>> That's understandable and it answers why the upgrade did not actually 
>>> happen. Why is it then that the original upgrade log seemed to 
>>> indicate that the upgrade to 0.27.4 did happen when it clearly did not?
>>>
>>> mike
>>>
>> The upgrade did happen, but because you didn't use *apt-get 
>> dist-upgrade* it didnt upgrade libmyth and possibly some others.
>***
>Ok, if the upgrade did happen, why did a version test indicate 
>otherwise? I'm not disputing my evident use of the wrong upgrade 
>sequence but is that the reason I received conflicting reports of what 
>actually happened?
>
>mike

Most of the MythTV packages were upgraded, but not libmythtv-0.25 to
libmythtv-0.27.  That only happens with dist-upgrade.  And the version
information must have been coming from libmythtv-0.25, not the other
upgraded packages.


More information about the mythtv-users mailing list