[mythtv-users] Backend log - Possible SSDP reflection attempt

[Rich Freeman]

On Mon, Apr 6, 2015 at 12:01 PM, Karl Newman <newmank1 at asme.org> wrote:
> On Mon, Apr 6, 2015 at 8:42 AM, Michael T. Dean <mtdean at thirdcontact.com>
> wrote:
>> On 04/06/2015 11:22 AM, Phil Bridges wrote:
>>>
>>> Thanks.  I'm updating now to the latest in Portage -  0.27.4_p20150124
>>>
>>> Interestingly enough, after updating / restarting mythbackend, my version
>>> info still shows:
>>>
>>> MythTV Version : e4f65c8
>>> MythTV Branch : tag: v0.27.4
>>> Network Protocol : 77
>>> Library API : 0.27.20141016-1
>>> QT Version : 4.8.5
>>
>> Chances are you didn't actually start the new version (unless the version
>> in portage is actually e4f65c8, in which case you didn't update).  Easiest
>> solution (that will always work) to ensure you're starting the new version
>> after an update is to actually reboot the machine.  Otherwise, you'll need
>> to keep futzing with your shutdown/start scripts until you get the new
>> version reported.
>>
>
> This is Gentoo, which doesn't (by default) live in systemd hell. A simple
> `/etc/init.d/mythbackend restart` should do it.

systemctl restart mythbackend will restart the backend.  It should
actually be more reliable than doing it with openrc (I've found that I
often have to do a killall -u mythtv with openrc just to get rid of
logservers and such).  Either way it isn't a big deal to use the
latest code on Gentoo.

> I have noticed, though, that
> the mythtv ebuild may not be compiling in the most up-to-date git commit
> version information. My info shows the same as Phil's above, but the build
> selected for the 0.27.4_p20150124 is "3b4390396bf..." There's probably
> something that needs to be done to the source to get that git commit into
> the version info (looping in the maintainer Rich Freeman for his input).

0.27.4_p20150124 is indeed git commit 3b4390396bf...

It looks like the ebuild sets the version in VERSION, but not in
EXPORTED_VERSION.  Adding these two lines to the ebuild src_prepare()
fixes this:
        echo "SOURCE_VERSION=\"${BACKPORTS}\"" > "${S}"/EXPORTED_VERSION
        echo "BRANCH=\"${MYTHTV_BRANCH}\"" >> "${S}"/EXPORTED_VERSION

$ cat EXPORTED_VERSION
SOURCE_VERSION="3b4390396bf09dfe3741508ecf7fc71a004abd01"
BRANCH="fixes/0.27"

I'll include this in the next revision.  We're about due for one
anyway.  I'll fix the auto-rebuild anytime mysql changes as well.

--
Rich