This may be a self-inflicted wound, so I didn't want to jump the gun and submit a bug report. I've been running mythtv-trunk packages from the atrpms-bleeding repo for about a month now. Yesterday I noticed that there were new packages available (0.21-154; r12854 versions). I don't have the bleeding repo enabled by default in either my yum or smart configurations, so I have been using 'yum --enablerepo=atrpms...' to get these mythtv updates. After running this command both last night and this morning and not seeing the new myth packages show up I decided to download and install manually. The install went through without a hitch, and the mythbackend started up OK. However, after a few minutes of the back-end process running, I think when it started doing it's normal maintenance stuff, it just died. The following message showed up in the back-end log: /usr/bin/mythbackend: symbol lookup error: /usr/bin/mythbackend: undefined symbol: _ZN8EITCache17ClearChannelLocksEv
I tried starting up the back-end again, but it did the same thing. I have now downgraded to the 0.21-153 packages and everything is running fine. Is this a legitimate bug, or did I just miss something by not letting yum find the updates?
_______________________________________________ atrpms-users mailing list [email protected] http://lists.atrpms.net/mailman/listinfo/atrpms-users
