'queue fetch' safety catch is slightly too stiff

lp_archive@drescher:/tmp/cjwatson/queue$ q -Q unapproved fetch banshee
Initialising connection to queue unapproved
Running: "fetch banshee"
Fetching ubuntu/None (UNAPPROVED) 4/33
---------------------------------------------------------------------------
Constructing banshee_0.11.1-0ubuntu1_source.changes
Constructing banshee_0.11.1-0ubuntu1.dsc
Constructing banshee_0.11.1-0ubuntu1.diff.gz
Constructing banshee_0.11.1.orig.tar.gz
Constructing banshee-official-plugins_0.11.1-0ubuntu1_source.changes
Constructing banshee-official-plugins_0.11.1-0ubuntu1.dsc
Constructing banshee-official-plugins_0.11.1-0ubuntu1.diff.gz
Constructing banshee-official-plugins_0.11.1.orig.tar.gz
Constructing banshee-official-plugins_0.11.1-0ubuntu2_source.changes
Constructing banshee-official-plugins_0.11.1-0ubuntu2.dsc
Constructing banshee-official-plugins_0.11.1-0ubuntu2.diff.gz
Constructing banshee-official-plugins_0.11.1.orig.tar.gz
banshee-official-plugins_0.11.1.orig.tar.gz already present on disk
Aborting current transaction

But the two banshee-official-plugins_0.11.1.orig.tar.gz files are the same. It would make my life a bit easier if 'queue fetch' only aborted if the file it's trying to fetch was different from the one already present on disk.