Bug 1289939
Summary: | Preupgrade-assistant package should be NOARCH | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Petr Hracek <phracek> |
Component: | preupgrade-assistant | Assignee: | Petr Hracek <phracek> |
Status: | CLOSED ERRATA | QA Contact: | Tereza Cerna <tcerna> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.8 | CC: | fkluknav, mflitter, ovasik, phracek, pstodulk, tcerna, ttomecek |
Target Milestone: | rc | Keywords: | Extras |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | preupgrade-assistant-2.1.3-1.el6 | Doc Type: | Bug Fix |
Doc Text: |
The preupgrade-assistant tool is now .noarch
Previously, preupgrade-assistant was distributed as set of architecture-specific RPM packages. As this is no longer required, it will be distributed as single cross-architecture (noarch) package.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-11 08:26:38 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: | |
Embargoed: |
Description
Petr Hracek
2015-12-09 11:49:43 UTC
(In reply to Alois Mahdal from comment #1) [...] > One way is look at TPS tab as see if the tests have been scheduled at > expected arch/variant combinations (same as ER#21377, ie. ppc64m, s390x, > x86_64 but *not* i386). this can be done more easily by using `rqkit-anydiff`, new tool announced on qe-baseos-demons mtg and list: rqkit anydiff er/tps 21377 22151 or rqkit anydiff -r 3 er/tps 21377 22151 to hide gory details such as times and hostnames. (still has same disadvantages as mentioned, but it's better than just looking at HTML) Verified. Packages are noarch. Builds, spec file, rpmdiff and rqkit was checked and everything is OK. Verified in: preupgrade-assistant-2.1.5-4.el6 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-1022.html |