broken packages question

[Toby Kelsey]

This is probably a trivial question, but I'm not used to apt-based systems.

I'm trying to fix a GNOME problem, and when I look in Synaptic:Custom/Broken
it's empty, and fix broken packages/mark upgrades/apply does nothing.

But when I run
  aptitude search '~b'
from the command-line, I get this list:

iB  evolution                                  - The groupware suite
iB  evolution-data-server                      - evolution database backend server
iB  evolution-exchange                         - Exchange plugin for the Evolution groupware suite
iB  gnome-pilot                                - A GNOME applet for management of your Palm PDA
iB  gnome-pilot-conduits                       - conduits for gnome-pilot
iB  gnomemeeting                               - The GnomeMeeting Voice Over IP Suite
iB  gstreamer0.8-dv                            - DV plugin for GStreamer
iB  gstreamer0.8-gsm                           - GSM plugin for GStreamer
iB  gstreamer0.8-theora                        - Theora plugin for GStreamer
iB  gstreamer0.8-vorbis                        - Vorbis plugin for GStreamer
iB  libcamel1.2-3                              - Generic messaging library for evolution data servers
iB  libegroupwise1.2-5                         - Client library for accessing groupwise POA through SO
iB  nautilus-sendto                            - provide integration between nautilus, evolution, and
iB  rhythmbox                                  - music player and organizer for GNOME
iB  sound-juicer                               - GNOME 2 CD Ripper
iB  totem-gstreamer                            - A simple media player for the Gnome desktop based on
iB  ubuntu-desktop                             - The Ubuntu desktop system

which seems to mean they are broken. So my question is what is the canonical way of determining
broken packages and the unmet dependencies?

Also while I'm here, what's the apt equivalent of 'rpm -qf file'?

Thanks,
Toby