Bug 994940 - regression: '--excludepkgs' statement ignored in kickstart file
Summary: regression: '--excludepkgs' statement ignored in kickstart file
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 995526 997116 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-08-08 09:32 UTC by Enrico Scholz
Modified: 2014-02-21 19:17 UTC (History)
10 users (show)

Fixed In Version: anaconda-20.8-1
Clone Of:
Environment:
Last Closed: 2014-02-21 19:17:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Enrico Scholz 2013-08-08 09:32:43 UTC 
Description of problem:

The '--excludepkgs' switch of the 'repo' option seems to be ignored by recent anaconda.  It worked fine with previous versions.

E.g. I have

| repo --name=fedora-core ... --excludepkgs=cfengine
| repo --name=local ...

where the 'local' repository provides 'cfengine-2.2.10'. After installation, cfengine-3.3.0 from the 'fedora-core' repository is installed.


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

Fedora 19 installer
Comment 1 Chris Lumens 2013-08-21 19:25:52 UTC 
Can you please attach /tmp/packaging.log and /tmp/yum.repos.d/fedora-core.* to this bug report?  For that matter, where is fedora-core configured to install from?  Is that your own local repo?
Comment 2 Chris Lumens 2013-08-21 19:33:43 UTC 
*** Bug 995526 has been marked as a duplicate of this bug. ***
Comment 3 Chris Lumens 2013-08-21 19:34:57 UTC 
I'm guessing your repo config file simply will not contain an exclude= line.  Can you confirm that suspicion?  I do not need the log files attached, turns out.
Comment 4 Chris Lumens 2013-08-21 20:11:41 UTC 
*** Bug 997116 has been marked as a duplicate of this bug. ***
Comment 5 Chris Lumens 2013-08-21 20:15:17 UTC 
All kickstart repo problems appear to be somehow related to the repo getting removed in source.py:_update_payload_repos.
Note You need to log in before you can comment on or make changes to this bug.