Mismatch (armel/armhf) between debs and dpkg
I'm trying to understand where/why/how [the target] dpkg is setting it's default architecture. I'm building for BeagleBoneBlack, which is compiling for hardware floating point. The .deb packages created are suffixed armhf (correctly picked up through package_deb.class), yet the dpkg binary itself reports the architecture as armel.
Hence, other than forcing/overriding this, dpkg complains about the architecture mismatch.
Is there something in there somewhere which will correct dpkg's behaviour?