To better solicit help from others interested in Raspbian, I've been working this evening on scripts that will automate the process of pushing the logs of all package built by the autobuilders into a 'logs' folder that sits parallel to the repository. A URL to where the logs will be found is here:
The directory structure is nearly a mirror of how the packages are placed within the repository pool itself. Logs for specific source packages can be located by indexing on their first letter of the package name in to the directory — or by 'lib' and the next letter for library packages. Hopefully it's fairly self evident how it works.
Also, within a day or so, I'll start posting on a regular basis a page on the Raspbian wiki with a current list of problem packages that can be examined. This list is currently nearly 120 packages long so Plugwash and I could certainly use any help others might provide.
If you have the QEMU image or an actual Raspberry Pi hardware running Raspbian and some knowledge of how Debian packages can be built and modified locally, there should be enough of Raspbian functioning that you'll have everything you need to help us debug packages that aren't autobuilding.
Note that the logs will be missing for packages which we manually built outside the autobuilding system or for packages built more than a week and a half ago. However, for now, the priority is on making sure the logs for packages which didn't build are available.
Let me know if you have any suggestions on improving how things might work.
Also, I realize that it's probably past time to look into a bug base of some kind so that issues with Raspbian can be better identified, prioritized and tracked to a resolution. I'll try to start putting some cycles towards this over the next few days.
I gotta get some sleep now. And I didn't get to yet try to run XFCE within Raspbian .