That's what I did. Yesterday I edited my atrpms.repo and changed
bleeding to enable=0. Did a yum clean all; yum update and everything
went smooth.
Mike
Brian Long wrote:
> I'm currently running 0.21 build 179 from atrpms-bleeding. Assuming I
> would like to stabilize on 0.21 for a while inste
Axel Thimm wrote:
> On Fri, Nov 09, 2007 at 09:55:44AM -0600, Mike LaPlante wrote:
>
>> Just wondering if there are plans to rebuild the kmdls for 1394 on the
>> new F7 2.6.23 kernel? Package doesn't seem to be updated it. I may try
>> to compile my ow
Just wondering if there are plans to rebuild the kmdls for 1394 on the
new F7 2.6.23 kernel? Package doesn't seem to be updated it. I may try
to compile my own but the rpms sure are handy.
Thanks
Mike
___
atrpms-users mailing list
atrpms-users@atrpms.
[EMAIL PROTECTED] wrote:
> Uhm, yeah. Sorry.
>
> Remove livna versions of ffmpeg*, lame* and faad*, disable livna and try
> again. Will try that tonight.
>
> Google is my friend.
>
:-)
For what its worth on my myth boxen I try not to use livna at all. Or
any repo except atrpms. If I need some
Mike LaPlante wrote:
> I can't seem to install the madwifi drivers on FC6 because I'm running
> kernel 2.6.22.4-45 and there are no kmdls for that kernel.
>
>
>
Well I got it working by forcing the downgraded kernel. Works for me, no
side effects yet. Maybe 2.6.22.4
I can't seem to install the madwifi drivers on FC6 because I'm running
kernel 2.6.22.4-45 and there are no kmdls for that kernel.
"yum install madwifi" is trying to install an older kernel
Installing:
madwifi i386 1:0.9.4-38_r2512.fc6
atrpms 46 k
Installing f
Not sure if this is a bug or a configuration error on my part. But I've
never run into this before and it stumped me for a few minutes.
I did an update this weekend and yum installed the wrong architecture
nvidia package, I saw this in my logs when probing the module.
kernel: nvidia: version m
Axel Thimm wrote:
> Maybe I should make that the default. There are two camps that say
> "have the list do that", or "let the user have the choice". Until now
> I went with the max-freedom variant, which also means more config by
> user side.
>
> Anyway there are pros and cons and I have also grown
I have a tendency to just click 'Reply' in Thunderbird when responding
to the various mailing lists I subscribe to. On all of them except
ATrpms this is usually not a problem because the headers have the
ReplyTo set to the list not the Sender.
Is there anything I can do client side to make this
(Bah, sorry Tom sent that last email went direct to you, for some reason when I
hit Reply in Thunderbird for this list its not using the list address)
http://www.gossamer-threads.com/lists/mythtv/users/285096
Daniel K says that myth-20.2 should be out tomorrow, after that its just
a matter of ti
Tom Bishop wrote:
> I also use the atrpms mythtv-suite (.20) and would like to know what
> the forward path is for going to schedules direct, I would like to
> sign up but it is not clear as to what needs to be done to get there.
>
I'm assuming that once there is a new MythTV release on mythtv.or
Just noticed a new build of myth is in atrpms bleeding. However, when I
do a yum update I get this error:
Transaction Check Error:
file /usr/lib/perl5/site_perl/5.8.8/MythTV.pm from install of
perl-MythTV-0.21-162_trunk_r13726.fc7 conflicts with file from package
libmyth-0.21-159_trunk_r13460.
12 matches
Mail list logo
