I'm not saying it isn't a headache. I'm saying its exactly like the situation was back in 2005 that everyone prior to the formation of Ubuntu was dealing with already with Java.
It'll be interesting to see what Debian decides to do with the sun-java6-jre package in nonfree which ironically were derived from Canonical's partner repository packages.
And really you shouldn't be too upset that Oracle isn't building debs. Even for those of us who use rpm based distributions, the rpm packages provided by Oracle (and by Sun back in the day) aren't particularly stellar. There's a reason why the jpackage project exists and encourages people to rebuild rpms using their nosrc approach instead of the Sun/Oracle packages to build well formed rpm packages.
And we've already seen examples of Debian doing this sort of workaround when redistribution of the code is not allowed by the license. I'm pretty sure the standard debian and Ubuntu flash-plugin package has historically had to work around a lack of redistribution rights and pull the flash-plugin payload at package install in what is essentially a fake package wrapper that sets up the dependencies correctly and what not. I'm sure a similar deb packaging technical workaround can be found for the oracle jre6 bin if there is enough desire to do it.