Bug 147631 - Allow yum to exclude repos by arch
Summary: Allow yum to exclude repos by arch
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-02-09 22:38 UTC by Ignacio Vazquez-Abrams
Modified: 2014-01-21 22:51 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2005-02-10 07:41:39 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ignacio Vazquez-Abrams 2005-02-09 22:38:11 UTC
Some third-party repos (e.g., livna) don't have repos for all available
"official" archs (i386 and x86_64 for the moment) yet are included in
commonly-available yum config changes/addons. It would be convenient to have an
"excludearch" or "exclusivearch" tag that could be used in these configs to
indicate that certain repos can only be used for certain archs.

Comment 1 Seth Vidal 2005-02-10 07:11:41 UTC
yum only uses archs that are compatible with the platforms its running on - so
if you have a repo with exclusively ppc packages and you're an p4 - it won't use
any of them.

What's the problem that this feature would preclude?

Comment 2 Ignacio Vazquez-Abrams 2005-02-10 07:39:31 UTC
While yum won't allow you to install a ppc package on an i386 platform, if the
repo path contains $basearch it will still attempt to descend into the i386 dir,
even if only a ppc dir exists. It will then of course fail to find the repodata,
and abort the entire operation outright.

While it could be said that your yum config shouldn't contain repos that don't
support your arch, it would also be convenient for .repo distrobution purposes
to have some way to desensitive yum to this sort of problem.

Comment 3 Seth Vidal 2005-02-10 07:41:39 UTC
if your repo is arch specific then just distribute your .repo file in an
arch-specific rpm.

I think adding arch exclusivity in the yum.conf is overkill.


Note You need to log in before you can comment on or make changes to this bug.