|
Bugzilla – Full Text Bug Listing |
| Summary: | Conflict between ial and fnfx | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Arnaud Delobel <arnaud.delobel> |
| Component: | Installation | Assignee: | Jiri Srain <jsrain> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | blade2445, exigentsky, forgotten_VqcLmSAkg-, yast2-maintainers |
| Version: | Beta 3 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Yast2 log of installation | ||
|
Description
Arnaud Delobel
2005-08-25 11:55:06 UTC
The package ial is not in any selection. fnfx is in the laptop selection. So right now I do not see why both could be installed. Please provide the YaST2 logs of the installation, see: http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST Created attachment 47551 [details]
Yast2 log of installation
Jiri, please have a look. @comment #1: ial is in selection, fnfx is not. According to PDB descriptions, both packages are for the same purpose, fnfx is toshiba-specific, ial is generic. fnfx is selected via .probe.system. Since I know abuot the conflict, I will hack it into Packages.ycp so that if fnfx is selected, ila is automatically deselected (although I will hate this hack). Done in SVN, please, test Beta4 when it is out. *** Bug 113892 has been marked as a duplicate of this bug. *** Still happens on Beta 4 here (Toshiba M30-344). In addition, ial is set to "taboo" which leads to another dependency conflict needing manual intervention. *** Bug 113714 has been marked as a duplicate of this bug. *** does this still happen? If it does, please reopen! Works fine with RC1: fnfx wasn't automatically selected, but ial and initial. I can adjust screen brightness out of the box, which was my main concern. Good job. I cannot start initial any longer, but I guess I'd better check if there's already a bug. |