Bug 1121201 - spacewalk-repo-sync needs an arch filter capability
Summary: spacewalk-repo-sync needs an arch filter capability
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Satellite Synchronization
Version: 560
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
Assignee: Michael Mráka
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 260381
TreeView+ depends on / blocked
 
Reported: 2014-07-18 15:50 UTC by Chris Roberts
Modified: 2014-08-08 19:58 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-08-08 19:58:16 UTC


Attachments (Terms of Use)

Description Chris Roberts 2014-07-18 15:50:29 UTC
I am unable to use spacewalk-repo-sync to populate a custom x86_64 Satellite channel with data from a mixed-architecture repo (specifically, oVirt 3.4 - http://resources.ovirt.org/pub/ovirt-3.4/rpm/el6/) because spacewalk-repo-sync has no way of masking out packages with an inappropriate architecture (ppc64 in my case). Consequently all the downloaded rpms remain orphaned because spacewalk-repo-sync fails to link any of them with the channel.  I have not been able to work around the problem using spacewalk-repo-sync's documented "-e" option (is this a regex?  how much of the file/path name is matched?).  I cannot synch arch-specific sub-repos (e.g. http://resources.ovirt.org/pub/ovirt-3.4/rpm/el6/x86_64/) because the subdirectories lack repodata.

Yum handles mixed-architecture repos of this sort just fine.  It seems to me that space-walk-repo-sync needs an option analogous to reposync's "-a" option, so that it can be instructed to ignore architectures that are not relevant to the channel, rather than just consistently failing.


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