Mythtv 25 to testing and then stable

Bob Lightfoot <[email protected]>
Newsgroups gmane.linux.redhat.rpm.atrpms.general
Message-ID <[email protected]>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/11/2012 06:00 AM, [email protected] wrote:
> Send atrpms-users mailing list submissions to 
> [email protected]
> 
> To subscribe or unsubscribe via the World Wide Web, visit 
> http://lists.atrpms.net/mailman/listinfo/atrpms-users or, via
> email, send a message with subject or body 'help' to 
> [email protected]
> 
> You can reach the person managing the list at 
> [email protected]
> 
> When replying, please edit your Subject line so it is more
> specific than "Re: Contents of atrpms-users digest..."
> 
> 
> Today's Topics:
> 
> 1. myth 25 beta test results (Bob Lightfoot) 2. Re: myth 25 beta
> test results (Monkey Pet) 3. mythtv 0.25 moving to stable? (Monkey
> Pet) 4. Re: mythtv 0.25 moving to stable? (Axel Thimm)
> 
> 
> ----------------------------------------------------------------------
>
>  Message: 1 Date: Tue, 10 Apr 2012 17:28:02 -0400 From: Bob
> Lightfoot <[email protected]> To: [email protected] Subject:
> [ATrpms-users] myth 25 beta test results Message-ID:
> <[email protected]> Content-Type: text/plain;
> charset=ISO-8859-1
> 
> Dear Atrpms Team: For anyone interested I conducted the following
> test today. Test Notes : 1.	System was a stock HP Pavillion Elite
> M9040N with an additional Hauppage Win-TV HVR 1600. 2. 	Mythtv 24
> was running on Centos 6.2 x86_64 on this machine with no
> significant issues. {note the occasional segfault does occur which
> I have not chased down yet} 3.	A totally fresh Centos 6.2 i686
> Desktop install {1107 packages} was performed from DVD into a VM
> with 2 cpu cores, 1 gig of ram and 12 gb f disk space. 4.	Yum
> update and reboot was done immediately after install. 5. 	For some
> reason even with mythbackend disabled on the host I could not mount
> the pci host tuner hdwe to the guest vm.
> 
> So I'll test mythfrontend v25-beta only on the vm.
> 
> 6. 	Firefox visited atrpms.net and installed atrpms repos. With
> testing and bleeding repos enabled.
> 
> 7.	yum install mythtv-frontend -- successfully installs myth25 
> frontend and associated programs.
> 
> The mythfrontend will not start on i686 however for an error - 
> mythfrontend: symbol lookup error: /usr/lib/libmythbase-0.25.so.0: 
> undefined symbol: ZN9QListData11detach_growEPii
> 
> NOTE : I am getting the same error on my i686 mythv24 system as
> well, but the x86_64 version works.
> 
> Bob Lightfoot
> 
> 
> 
> ------------------------------
> 
> Message: 2 Date: Tue, 10 Apr 2012 16:19:41 -0700 From: Monkey Pet
> <[email protected]> To: "User discussion about ATrpms.net"
> <[email protected]> Subject: Re: [ATrpms-users] myth 25 beta
> test results Message-ID: 
> <CADXZuRyVFUyNTAJY-fJ0oohPnnQZMn7V6sh8Y174=UWQt3e7VQ@mail.gmail.com>
>
> 
Content-Type: text/plain; charset="iso-8859-1"
> 
> Make sure you remove all the mythtv-0.24 rpms.
> 
> rpm -qa |grep myth |grep 0.24
> 
> If you see any 0.24 listed, you are in trouble with both 0.25 and
> 0.24 versions installed.
> 
> 
> You can feed the output of the cmd above into 'rpm --erase
> --nodeps'
> 
> When I did yum update mythtv after changing the repo to bleeding,
> the wrong thing happened and it left 0.24 stuff behind.  I had to
> remove the 0.24 myth stuff first, then do a yum install mythtv
> again.  After that, myth ran fine both the backend and frontend.
> 
> 
> 
> 
> On Tue, Apr 10, 2012 at 2:28 PM, Bob Lightfoot <[email protected]>
> wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
>> 
>> Dear Atrpms Team: For anyone interested I conducted the following
>> test today. Test Notes : 1.      System was a stock HP Pavillion
>> Elite M9040N with an additional Hauppage Win-TV HVR 1600. 2.
>> Mythtv 24 was running on Centos 6.2 x86_64 on this machine with
>> no significant issues. {note the occasional segfault does occur 
>> which I have not chased down yet} 3.      A totally fresh Centos
>> 6.2 i686 Desktop install {1107 packages} was performed from DVD
>> into a VM with 2 cpu cores, 1 gig of ram and 12 gb f disk space. 
>> 4.      Yum update and reboot was done immediately after
>> install. 5.      For some reason even with mythbackend disabled
>> on the host I could not mount the pci host tuner hdwe to the
>> guest vm.
>> 
>> So I'll test mythfrontend v25-beta only on the vm.
>> 
>> 6.      Firefox visited atrpms.net and installed atrpms repos. 
>> With testing and bleeding repos enabled.
>> 
>> 7.      yum install mythtv-frontend -- successfully installs
>> myth25 frontend and associated programs.
>> 
>> The mythfrontend will not start on i686 however for an error - 
>> mythfrontend: symbol lookup error:
>> /usr/lib/libmythbase-0.25.so.0: undefined symbol:
>> ZN9QListData11detach_growEPii
>> 
>> NOTE : I am getting the same error on my i686 mythv24 system as
>> well, but the x86_64 version works.
>> 
>> Bob Lightfoot -----BEGIN PGP SIGNATURE----- Version: GnuPG
>> v2.0.14 (GNU/Linux) Comment: Using GnuPG with Mozilla -
>> http://enigmail.mozdev.org/
>> 
>> iQEcBAEBAgAGBQJPhKXiAAoJEKqgpLIhfz3XnxYIAK8QQJwF/oVg4AsWQPwy9J8y 
>> AAWQ7Q6TMCdlgEIJeP14WH8O+n50Ewdno41Md4YjFXjoZN6MhUvEXYvI264dIseC 
>> IIG9dHBpXXXTdAyfgjaG55GXHKD/RJhgCJQcQOXilValtpLSOksO/QWaNxvx+Xnq 
>> 0+jYffPaROMpxIiMHyOWhbY+Lspki6ChTELdpAiCycigCgzRGhZWv10u3B2vL9Vh 
>> rNarK+wmva+5EX2Xc7XpMHZZNxmQJoNlB7tTMA2GBwRFU3VjPZ+cFqRaMH942e1q 
>> w1ZZNDr9vIfGpstSjGmOi4IwxmEkRXBjYzOMkJhHDu4jwYjiI+4gQPE79JN4tDg= 
>> =WdhN -----END PGP SIGNATURE-----
>> 
>> _______________________________________________ atrpms-users
>> mailing list [email protected] 
>> http://lists.atrpms.net/mailman/listinfo/atrpms-users
>> 
> -------------- next part -------------- An HTML attachment was
> scrubbed... URL:
> <http://lists.atrpms.net/pipermail/atrpms-users/attachments/20120410/47050699/attachment-0001.html>
>
>  ------------------------------
> 
> Message: 3 Date: Tue, 10 Apr 2012 21:33:50 -0700 From: Monkey Pet
> <[email protected]> To: ATrpms user list
> <[email protected]> Subject: [ATrpms-users] mythtv 0.25
> moving to stable? Message-ID: 
> <CADXZuRweZzgu5pToJ=mLPkjK-L+gDtr3mmVC5qFh3AwoMSvhBQ@mail.gmail.com>
>
> 
Content-Type: text/plain; charset="iso-8859-1"
> 
> Hi, is the plan to move the mythtv 0.25 to stable from bleeding? 
> -------------- next part -------------- An HTML attachment was
> scrubbed... URL:
> <http://lists.atrpms.net/pipermail/atrpms-users/attachments/20120410/b5bcf6ab/attachment-0001.html>
>
>  ------------------------------
> 
> Message: 4 Date: Wed, 11 Apr 2012 11:53:46 +0200 From: Axel Thimm
> <[email protected]> To: "User discussion about ATrpms.net"
> <[email protected]> Subject: Re: [ATrpms-users] mythtv 0.25
> moving to stable? Message-ID:
> <[email protected]> Content-Type:
> text/plain; charset=us-ascii
> 
> On Tue, Apr 10, 2012 at 09:33:50PM -0700, Monkey Pet wrote:
>> Hi, is the plan to move the mythtv 0.25 to stable from bleeding?
> 
> The final release is building now, let's move it to testing for a
> day or two and once there are a couple of success reports we can
> go stable.

I hope my testing results in Qemu/KVM with Centos 6.2 up to date and
using myth v25 from bleeding are not what will happen on real bare
metal systems.

Anyone have a suggestion about the symbol lookup error I saw on all
attempts with v25 and on my v24-i686 frontend only install.

Bob
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPhXWeAAoJEKqgpLIhfz3Xn0AH/jof626ebNixxu/naMf2wBEo
e21CfZLkKjIB5bGJ33WN/cmmlYg49z4m1nM6lcfWURmn2MZqDYzByv0vdzgiimK/
4gkXOQbsjXREnb2q0KNsshRYvIQMXbcAm5hwupU09gRWxY2w2no9Qhf1bfTEFwvg
OVfEWtqM8WR0+FXDWdtreRe8qHAyYuwv3ST81ke1KTETmuyLduN/qHrBsiREry/l
56ikPK+qCdq+MRM+kC11PdRbQFHzxUM9DbvDtTpxkzpdL49oir3J193rO3s3DRtW
m4QRBZ9lhDe7mfn5CG1wWyAx12LKg/hYwkr8N1m8xMG4rPsgodpm3fgXFOvNNmk=
=2/yD
-----END PGP SIGNATURE-----
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.