Bug 555585

Summary: modifying repo doesn't clear group data
Product: [Fedora] Fedora Reporter: Bill Nottingham <notting>
Component: anacondaAssignee: Radek Vykydal <rvykydal>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: jonathan, rvokal, vanmeeuwen+fedora
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: anaconda-14.2-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 574761 (view as bug list) Environment:
Last Closed: 2010-12-04 00:24:22 UTC Type: ---
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: 574761    

Description Bill Nottingham 2010-01-14 20:45:53 UTC
Description of problem:

Modifying the base installation repo doesn't clear the group cache, leading to package selection weirdness.

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

F12 GA

How reproducible:

100%

Steps to Reproduce:
1. Examine F12 GA comps file. Note 'slim' as a default package in LXDE, 'lxdm' package not included.
2. Examine F13 comps file. Note 'lxdm' is a default package, but 'slim' is not listed.
3. Boot F12 GA installer. It defaults to F12 GA as 'installation repo'.
4. Modify the 'installation repo' to point to rawhide
5. Go to 'customize', and look at the LXDE group.
  
Actual results:

It has merged the groups. Both 'lxdm' and 'slim' are on by default. If you look in some other groups, you'll see packages listed twice due to the merging.

Expected results:

It only uses the rawhide groups, as that's the only 'installation' repo.

Additional info:

Comment 1 Radek Vykydal 2010-03-17 14:52:02 UTC
This should be fixed in version 14.2-1 of anaconda.

Comment 2 Bug Zapper 2010-11-04 00:58:07 UTC
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Bug Zapper 2010-12-04 00:24:22 UTC
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.