Bug 926549

Summary: anaconda dependency problems when selecting KDE Plasma Workspaces (no addons)
Product: [Fedora] Fedora Reporter: Reartes Guillermo <rtguille>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 19CC: anaconda-maint-list, awilliam, g.kaviyarasu, jonathan, mkolman, robatino, sbueno, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-25 14:06:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 834084    
Attachments:
Description Flags
first screenshot
none
second screenshot none

Description Reartes Guillermo 2013-03-23 16:20:31 UTC
Created attachment 715148 [details]
first screenshot

Description of problem:

anaconda fails to resolve dependencies when selecting KDE Plasma Workspaces, see
first screen-shot. 

But if one re-selects KDE Plasma Workspaces again, there will be no dependency errors.

It is even possible to start installing but it will fail during installation with the error dependencies, see second screenshot.

Failing Packages: enblend, libgpod, upower

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

How reproducible:
always

Steps to Reproduce:

0. reach the welcome screen, leave default
1. enter Software Selection and select KDE Plasma Workspaces, then DONE.
2. after anaconda fails to resolve dependencies, enter Software Selection again.
3. select KDE Plasma Workspaces again, then DONE.
4. anaconda seems to resolve the dependencies this time...
5. select automatic partitioning (or whatever works).
6. Start installing, anaconda will hit the dependency error.
  
Actual results:
one can start installing with known dependency problems

Expected results:
no dependency issues, if there are some, do not let the user start installing.

Additional info:

12:14:49,516 INFO packaging: have _yum_lock for AnaInstallThread
12:14:49,516 INFO packaging: gave up _yum_lock for AnaInstallThread
12:14:49,517 WARN packaging: libgpod-0.8.2-8.fc19.x86_64 requires libimobiledevice.so.3()(64bit)
12:14:49,517 WARN packaging: enblend-4.1.1-1.fc19.x86_64 requires libIlmImf.so.6()(64bit)
12:14:49,517 WARN packaging: upower-0.9.19-2.fc19.x86_64 requires libimobiledevice.so.3()(64bit)
12:14:49,517 INFO packaging: gave up _yum_lock for AnaInstallThread

Comment 1 Reartes Guillermo 2013-03-23 16:21:08 UTC
Created attachment 715149 [details]
second screenshot

Comment 2 Andre Robatino 2013-03-23 16:56:24 UTC
Probably a dupe of repoclosure bugs

https://bugzilla.redhat.com/show_bug.cgi?id=924255 (libgpod)
https://bugzilla.redhat.com/show_bug.cgi?id=924248 (enblend)
https://bugzilla.redhat.com/show_bug.cgi?id=924260 (upower)

Comment 3 Adam Williamson 2013-03-23 17:37:24 UTC
It's not exactly a dupe as it's about how anaconda handles broken deps rather than the deps themselves, but I'm -1 blocker since we won't release Alpha with broken deps on the images anyway.

Comment 4 Chris Lumens 2013-03-25 14:06:59 UTC

*** This bug has been marked as a duplicate of bug 924162 ***