Bug 124343 - noarch packages incorrectly distributed to s390/s390x channels
noarch packages incorrectly distributed to s390/s390x channels
Status: CLOSED CURRENTRELEASE
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Channels (Show other bugs)
RHN Stable
s390x Linux
medium Severity low
: ---
: ---
Assigned To: Chris MacLeod
Fanny Augustin
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-05-25 15:41 EDT by Brock Organ
Modified: 2007-04-18 13:08 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-06-03 16:54:32 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Brock Organ 2004-05-25 15:41:24 EDT
* RHEL3 U2 s390/s390x AS
* Erratum: RHBA-2004:149-03 - Updated firstboot package clarifies
wording in the additional CDs scree
* packages selected in file list are all noarch

the errata file listing is:

> 3AS/SRPMS/firstboot-1.1.19-2.src.rpm
> 3AS/noarch/firstboot-1.1.19-2.noarch.rpm
> 3ES/SRPMS/firstboot-1.1.19-2.src.rpm
> 3ES/noarch/firstboot-1.1.19-2.noarch.rpm
> 3WS/SRPMS/firstboot-1.1.19-2.src.rpm
> 3WS/noarch/firstboot-1.1.19-2.noarch.rpm

which is correct; however, the s390/s390x arches should be excluded
from receiving this package, but up2date --showall on s390/s390x
incorrectly lists the package:

> # up2date --showall | grep firstboot
> firstboot-1.1.19-2.noarch
> #
Comment 1 Chris MacLeod 2004-05-26 12:58:23 EDT
rhelU2 packages were distributed according to rel-eng population of
the trees.  Were the trees done wrong in this case?
Comment 2 Tim Powers 2004-05-26 13:31:41 EDT
Um, no they weren't. Remember, I'm not supposed to use rhnpush for those, so they 
shouldn't be there in the s390* channels unless the erratum included it for the s390* 
channels.
Comment 3 Tim Powers 2004-05-26 16:51:08 EDT
Why is this assigned to me? Someone screwed up the errata and it needs to be re-issued. 
It has absolutely _nothing_ to do with my trees.
Comment 4 Tim Powers 2004-05-26 16:54:34 EDT
Chris: what needs to happen is for someone from RHN to just remove the firtboot 
packages from the s390* channels. Back to you.
Comment 5 Chris MacLeod 2004-05-26 17:26:55 EDT
This requires some custom work to disassociate the packages with the
channel(s) in question.
Comment 6 Chris MacLeod 2004-06-03 14:53:16 EDT
packages removed from webqa.  If all looks good let me know (set this
to prod_ready) and I'll have them removed from production.
Comment 7 Brock Organ 2004-06-03 16:18:02 EDT
verified fixed on webqa ... setting status to PROD_READY ... thanks! :)

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