Bug #34041
closed
Restrict to Architecture setting in yum type repos has no effect
Added by Marcel Kühlhorn about 3 years ago.
Updated almost 3 years ago.
Description
I want to sync a particular architecture from a upstream repo that contains multiple architectures, my assumption is that the Restrict to Architecture setting in yum type repos would achieve that.
Example Upstream: https://download.opensuse.org/repositories/home:/orcharhino:/sles_15/SLES15SP3/
Despite setting the Restrict to Architecture setting to e.g. aarch64, after syncing the Repo will contain all packages available upstream regardless of the packages architecture.
My expectation is that instead only the packages of the specified architecture and noarch packages are synced.
The UI here is extremely misleading.
Restrict to architecture doesn't have anything to do with restricting the packages that are synced. Instead it restricts which clients will have this repository 'enabled' when subscribed to the product.
We need to move this option to another category such as 'deployment options' or 'publishing options' or something like that
- Triaged changed from No to Yes
- Status changed from New to Ready For Testing
- Assignee set to Ryan Verdile
- Pull request https://github.com/Katello/katello/pull/9900 added
- Fixed in Releases Katello 4.5.0 added
- Status changed from Ready For Testing to Closed
- Pull request deleted (
https://github.com/Katello/katello/pull/9900)
- Fixed in Releases Katello 4.4.0 added
- Fixed in Releases deleted (
Katello 4.5.0)
- Pull request https://github.com/Katello/katello/pull/9900 added
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by