Currently, fedora core development only installs a very minimal system no matter what you do, see bugs 166091 166088. After install, I installed enough RPMs by hand to make it so system-config-packages would work, thinking I might be able to use that to populate up the machine. I did have success with this (in progress). However, I noticed that if the Gnome Software Development group was selected, an error was produced when you click on 'update'. The error says 'Packages Not Found' and lists a whole big list of RPMs in the error box. That box seems to match the output to the terminal from which I launched the program. This seemed different enough that I thought I'd file it. Feel free to kill this bug if it's another symptom of issues you're working on. I just didn't want to lose anything. * using startup-notification-devel-0:0.8-2.ia64 to satisfy startup-notification-devel-0.5 ('pilot-link-devel', '%{pilot-link-version}') ('mozilla-nss-devel', '37:1.7.11-1') ('nspr-devel', '4.6') ('jadetex', None) ('perl-SGMLSpm', '1.03ii') ('libgnomeprint22-devel', '2.10.0') ('libcroco-devel', '0.6.0') ('libgsf-devel', None) ('tetex-latex', None) ('passivetex', '1.11') ('w3m', None) ('jadetex', '2.5') ('perl(HTML::Entities)', None) [snip]
In a newer update of the fedora ia64 development tree, this problem went away. Closing.