taking ownership

The impact of this is high enough to carry forward the request to the next
Update. In addition it is not unlikely that there will be other requests for
this component possibly justifying a QA slot. 

Moving to the next Update, clearing all ACKs.

Quality Engineering Management has reviewed and declined this request.  You may appeal this decision by reopening this request.

This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release.  Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products.  This request is not yet committed for inclusion in an Update
release.

To recap what I have learned so far:

1) oo is 32bit, and needs the 32bit at-spi, gail and libgail-gnome packages
   for a11y to work

2) installing the 64bit libbonobo breaks the desktop on ppc64

3) the first attempt at doing this was to add these packages to the "multilib
   list", this had the side-effect of causing the 64bit libbonobo to get
   installed

What is not clear to me is 

a) how the side-effect in 3) happens. Why do we even ship a 64bit libbonobo
   if installing it breaks the desktop ?

b) "Someone needs to fix the packages so that they play nice together" - it
   is not clear to me what packages are meant here. If anything, it seems we 
   need to find a way to get certain 32bit packages installed (at-spi, gail,
   libgail-gnome) without installing other 64bit packages (libbonobo) as
   a side-effect.

To answer a):
The compose expands the multiarch list to satisfy deps. The compat-arch [*]
libbonobo gets pulled in because some other compat-arch package needs it.
Leaving these dependencies out is likely to breaks things just as badly.

[*] - By compat-arch I mean the extra architecture in the compose for which we
include a basic subset of packages (mostly libraries). The compat-arch is not
always the smaller-bit-size arch. For x86_64 we have i386 as a compat-arch, but
on ppc we have ppc64 as the compat-arch.

What is slightly unclear to me is why bug#175533 only seems to crop up on ppc
(probably something to do with the asymmetry, sure, but what exactly).

This request was previously evaluated by Red Hat Product Management
for inclusion in the current Red Hat Enterprise Linux release, but
Red Hat was unable to resolve it in time.  This request will be
reviewed for a future Red Hat Enterprise Linux release.

This is not being fixed at this point in RHEL 4.