I agree; this is a particularly severe bug because it renders the entire apt-get facility useless.
For what it's worth, even though the last command is the command that "fixes" the issue, I believe it to be desirable to execute the previous two commands, too, because those packages are part of the problematic dependency-chain.
In other words, even though it may be possible to remove only the "libc6-dev-x32" package and "fix" the problem, that approach seems more likely to introduce problems in the future (i.e., once Canonical fixes this package).
@Karthik
I agree; this is a particularly severe bug because it renders the entire apt-get facility useless.
For what it's worth, even though the last command is the command that "fixes" the issue, I believe it to be desirable to execute the previous two commands, too, because those packages are part of the problematic dependency-chain.
In other words, even though it may be possible to remove only the "libc6-dev-x32" package and "fix" the problem, that approach seems more likely to introduce problems in the future (i.e., once Canonical fixes this package).