Red Hat Bugzilla – Bug 124343
noarch packages incorrectly distributed to s390/s390x channels
Last modified: 2007-04-18 13:08:04 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 > #
rhelU2 packages were distributed according to rel-eng population of the trees. Were the trees done wrong in this case?
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.
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.
Chris: what needs to happen is for someone from RHN to just remove the firtboot packages from the s390* channels. Back to you.
This requires some custom work to disassociate the packages with the channel(s) in question.
packages removed from webqa. If all looks good let me know (set this to prod_ready) and I'll have them removed from production.
verified fixed on webqa ... setting status to PROD_READY ... thanks! :)