using dpkg is a nogo. does not do dependency tracking at all.
Use gdebi instead, if you install packages. Gdebi tracks depencencies, and installs them with the package.
gdebi can be used on commandline (gdebi packagename.deb) and gui (e.g. gdebi-gtk)
btw,
debian wheezy by default is a nogo, too.
Problem is: it has no multiarch support, activated by default. hence it does not support i386 and amd64 packages side by side out of the box.
dpkg --add-architecture i386 fixes that.
@anders" best thing to circumvent that all would be to make a debian repository, which is absolutely a nobrainer, if you do not need to have signed packages. It obviously also removes the burden of installing two packages by hand, in the right oder.
In your vm, make a folder called debian, put the debs into a new folder e.g called om inside of debian. Make sure you have dpkg-dev installed, then, in commandline, issue this command inside of the debian folder: dpkg-scanpackages om /dev/null | gzip -9c > om/Packages.gz
And that’s it. This generates a Packages.gz file in om folder. now upload the whole debian folder to your webspace.
People who want to use om repository then just have to add the debian repository like this:
echo “deb http://yourhost.com/debian om/” | sudo tee /etc/apt/sources.list.d/om.list
and then issue a sudo apt-get update && sudo apt-get install openmusic
You could make this process even more easy if you make a debian package which adds the repository automatically (I could provide a blueprint package for that if whished). People then just have to download the deb file, and this one would also work with dpkg 
Only thing which happens here is that packages are not signed ( single debs downloaded from sourceforge are also not signed btw…), thus the package manager tells you so with a warning that you install unsigned packages. If you want to get this right, I can also help, though it’s a bit more work.
Cheapest way would be for now to add the info in the readme of sourceforge why the 64bit package does not exist, and that you still can install the 32bit package on 64bit, but some systems do not have multiarch support (enabled and how to do that) and adding the info that installing packages with gdebi (in the right order) is a good idea.