| Summary: | spacewalk-repo-sync fails on mixed repositories | ||
|---|---|---|---|
| Product: | [Community] Spacewalk | Reporter: | Thomas Schweikle <tschweikle> |
| Component: | Server | Assignee: | Tomáš Kašpárek <tkasparek> |
| Status: | CLOSED NOTABUG | QA Contact: | Red Hat Satellite QA List <satqe-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 2.4 | CC: | mmraka |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-10-21 13:09:57 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Thomas Schweikle
2016-11-17 11:26:20 UTC
yum does not have any problem with such a repository. It selects what package is OK and takes *x86_64 for IA-64 and *i686 for IA-32 architectures. This is quite more complicated: Filter: '-*x86_64' makes it work. But: '-*x86_64 +*i686' leads to fail. Looks like it is really looking after files '<anything>x86_64<anything>i686' in this case and tries to exclude them. Parse error while looking at filter string, not breaking it up on spaces? > 2. create channel:
> Channel-Name*: Bareos 15.2 (i386)
> Channel-Label*: bareos152
> Parent-Channel: OL6-Client-Development (i386)
> Architektur: IA-32
i386 channel can't contain x86_64 packages but the other way round is possible (x86_64 channel can contain i686/i386 packages).
|