This is a hack:
:apt-get source package
cd package-version
dpkg-buildpackage -us -uc -rfakeroot
This is prohibitive in terms of development...
So is a "force" option.
Are there any config solutions for say alien-arena:amd64 showing alien-arena-data (all) as incompatible??
(assuming it is compatible...)
Have had similar issues with other amd64 installs using generic dependencies, not to mention dependency issues with other non-tagged (amd64 compatible?) packages.
Anyone else have this or similar issues?
Any non-hackish solutions?
(also the i386 alien install simply returns "Killed" on an x86-64 system)
--
Hoping I'm way off and there's a simple config fix to make x86 and x86-64 play nice together--esp. for development (e.g. elf 32/elf 64, x_x)
--
Is it the tagging and apt-get being too strict (not that it would know to begin with, without being told--supercow powers and all) or are they simply incompatible and need to be recompiled? Not looking forward to recompiling 500mb of graphic/game data... Esp. if I don't need to. Is it a similar issue of debian unwilling to store the excess/identical tagged data when the generic package is equally compatible. What happened to dummy packages? Too much of a crutch? Could suffice for the interim...