gcc-3.4_3.4.0-2_powerpc.changes REJECTED
Rejected: no source found for gcc-3.4 3.4.0-2 (cpp-3.4_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (libstdc++6-dev_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (gnat-3.4_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (g++-3.4_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (libstdc++6-dbg_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (gobjc-3.4_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (gpc-2.1-3.4_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (fixincludes_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (g77-3.4_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (libgcc1_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (gij-3.4_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (libffi2-dev_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (libffi2_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (gcj-3.4_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (protoize_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (libstdc++6_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (libstdc++6-pic_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (libgcj5-dev_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (gcc-3.4_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (libgcj5_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (libg2c0_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (gcc-3.4-base_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (libobjc1_3.4.0-2_powerpc.deb).
Rejected: no source found for gcc-3.4 3.4.0-2 (fastjar_3.4.0-2_powerpc.deb).
===
If you don't understand why your files were rejected, or if the
override file requires editing, reply to this email.
Reply to: