[elrepo-devel] kmod-fglrx.el6

[Phil Perry]

On 10/02/11 18:33, Steve Cleveland wrote:
>
>
> On 02/10/11 10:28, Fabian Arrotin wrote:
>> Steve Cleveland wrote:
>>> Was just going to try out the kmod-fglrx package in the test repository
>>> for el6.  Ran into a quick problem:
>>>
>>> # yum --enablerepo=elrepotest install kmod-fglrx
>>> Loaded plugins: refresh-packagekit, rhnplugin
>>> This system is not registered with RHN.
>>> RHN support will be disabled.
>>> Setting up Install Process
>>> Resolving Dependencies
>>> -->   Running transaction check
>>> --->   Package kmod-fglrx.x86_64 0:10.12-1.el6.elrepo set to be updated
>>> -->   Processing Dependency: fglrx-x11-drv = 10.12-1.el6.elrepo for
>>> package: kmod-fglrx-10.12-1.el6.elrepo.x86_64
>>> -->   Finished Dependency Resolution
>>> Error: Package: kmod-fglrx-10.12-1.el6.elrepo.x86_64 (elrepotest)
>>>               Requires: fglrx-x11-drv = 10.12-1.el6.elrepo
>>>               Available: fglrx-x11-drv-10.12-1.1.el6.elrepo.x86_64
>>> (elrepotest)
>>>                   fglrx-x11-drv = 10.12-1.1.el6.elrepo
>>>     You could try using --skip-broken to work around the problem
>>>     You could try running: rpm -Va --nofiles --nodigest
>>>
>>> The packages listed in the repo are:
>>>
>>> fglrx-x11-drv-10.12-1.1.el6.elrepo.x86_64.rpm
>>> kmod-fglrx-10.12-1.el6.elrepo.x86_64.rpm
>>>
>>> So one is 10.12-1, the other is 10.12-1.1.
>>>
>>> Thanks,
>>>     - Steve
>>
>> The reason (and it's still in testing) was mentioned by Phil here :
>> http://elrepo.org/bugs/view.php?id=104
>> I've myself not that laptop with fglrx anymore : i've just received my
>> new Thinkpad which has Nvidia so i'll test the nvidia kmod on el6 :-)
>
> Great thanks.  I swear I searched for a bug report.  I don't see it when
> going to the View Issues page.  Oh, I see, I have the project set to
> el6.  I get it. :)  Never mind.  I'll get it installed and report back
> in the bug report.
>

Yes, sorry about that - I ran out of time to rebuild the matching kmod 
package for testing (although the earlier release will "work" just fine 
with --nodeps).

Lets see if we can make some progress on this over the next few days :-)