Bug 170986

ls -l dist/fc4/{glibc,gcc,binutils,coreutils,bash}/*/ppc64/*debuginfo*
-rw-r--r--    1 root     root      1323632 May 20 13:13
dist/fc4/bash/3.0-31/ppc64/bash-debuginfo-3.0-31.ppc64.rpm
-rw-r--r--    1 root     root      4761790 May 25 15:11
dist/fc4/binutils/2.15.94.0.2.2-2/ppc64/binutils-debuginfo-2.15.94.0.2.2-2.ppc64.rpm
-rw-r--r--    1 root     root      2645897 May 25 15:12
dist/fc4/coreutils/5.2.1-48/ppc64/coreutils-debuginfo-5.2.1-48.ppc64.rpm-rw-r--r--    1 root     root     57529743 May 20 13:19
dist/fc4/gcc/4.0.0-8/ppc64/gcc-debuginfo-4.0.0-8.ppc64.rpm
-rw-r--r--    1 root     root     20753528 May 30 17:17
dist/fc4/glibc/2.3.5-10/ppc64/glibc-debuginfo-2.3.5-10.ppc64.rpm

I certainly see them in FC4 (on porkchop and likewise in FC5).
And in rawhide too:
http://download.fedora.redhat.com/pub/fedora/linux/core/development/ppc64/debug/

So, are you not seeing them when you build new ppc64.rpm's, or are you just
missing them on ftp in fedora/linux/core/4/ppc/debug/
(where they clearly are missing, guess the compose scripts would need tweaking)?

I meant the later, ftp in fedora/linux/core/4/ppc/debug/.  I didn't think to
look on our internal servers; I hadn't considered that we might be building
these and forgetting to copy them over.

We aren't copying i386 debuginfo rpms either in the x86_64 composes, etc.
But the difference that matters here is that unlike x86_64 where there is
x86_64 distro and i386 distro, on ppc there is no ppc64 distro.

Anyway, reassigning to distribution, this is a releng issue.

Is this going to be fixed in FC5?
Should it be on a blocker list?

 I can put it on the target list. Note that this is a mess, as the ppc/pp64 or
x86/x86_64 debuginfo RPMS will conflict with each other.

Eeew, yes this is a major mess, especially since yum if asked to install a
package, will attempt to install all the arches available for said package.

yum install foo-debug 

will try to install

foo-debug.ppc
foo-debug.ppc64

This is particularly bad on say pure ppc systems.  Even non-pure ppc systems, if
you don't already have the 64bit version of an application, when you ask for a
debug package, by nature of bringing in both arches, it'll try to depsolve the
64bit package and pull even more 64bit stuff in.

I'm not sure there is a clean way to fix this, given the broken nature of how we
publish ppc(64). :/

Hrm, I just looked at FC6 and we're doing exactly what I was afraid of, both ppc
and ppc64 debug info packages are in the ppc/debug/ dir.  We'll see if this
causes problems.

I'm not sure if we'd want to do anything in FC5 land for this.

I'm not comfortable with changing anything for Fc5.  This is resolved in FC6.