Bug 14124 - 5a2: unsatisfied libatiuki.so.1 for x11-driver-video-fglrx-14.201-0.2.mga5.nonfree.x86_64
Summary: 5a2: unsatisfied libatiuki.so.1 for x11-driver-video-fglrx-14.201-0.2.mga5.no...
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-19 04:12 CEST by Bit Twister
Modified: 2014-09-21 05:45 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bit Twister 2014-09-19 04:12:00 CEST 
Description of problem:

Some requested packages cannot be installed:
x11-driver-video-fglrx-14.201-0.2.mga5.nonfree.x86_64 (due to unsatisfied libatiuki.so.1)

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. urpmi --downloader wget --auto --auto-update

Update wiped out usage of fglrx driver. Had to revert to vesa driver.
No fglrx driver prevents wireless modules from loading. :(


Reproducible: 

Steps to Reproduce:
Comment 1 Thierry Vignaud 2014-09-19 12:28:15 CEST 
The following should fixes it:
 %global __requires_exclude libati

CC: (none) => thierry.vignaud

Comment 2 Thierry Vignaud 2014-09-19 12:29:54 CEST 
Humm the real issue is "\\+"
One needs to replace "\\+" by "+"
Comment 3 Thierry Vignaud 2014-09-19 19:19:55 CEST 
Fixed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Comment 4 Bit Twister 2014-09-20 17:26:00 CEST 
(In reply to Thierry Vignaud from comment #3)
> Fixed.

I'll close this when I can get the fglrx package installed. Still getting

Some requested packages cannot be installed:
x11-driver-video-fglrx-14.201-0.3.mga5.nonfree.x86_64 (due to unsatisfied libatiuki.so.1()(64bit))
Continue installation anyway?

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Comment 5 Bit Twister 2014-09-21 05:45:48 CEST 
no longer getting the error.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.