This really makes no sense to me. Technically this should not even be possible unless you did something strange with your system.
First off, the -386 package is not available from the amd64 repository. There's no way synaptic should have even seen it.
Secondly, even if you did install the -386 kernel on an 64-bit system, it would not boot, simply because the 32-bit -386 kernel would not be able to run the x86_64 binaries.
So my guess is that you somehow manually installed the 64-bit kernel at some point and are now getting hosed by an upgrade that is setting your system back correctly.
What I need from you is the output of the following commands:
dpkg --print-architecture
uname -a
ls -l /boot/.
file -L /lib/libc.so.6
dpkg -l | grep linux
This really makes no sense to me. Technically this should not even be possible unless you did something strange with your system.
First off, the -386 package is not available from the amd64 repository. There's no way synaptic should have even seen it.
Secondly, even if you did install the -386 kernel on an 64-bit system, it would not boot, simply because the 32-bit -386 kernel would not be able to run the x86_64 binaries.
So my guess is that you somehow manually installed the 64-bit kernel at some point and are now getting hosed by an upgrade that is setting your system back correctly.
What I need from you is the output of the following commands:
dpkg --print- architecture
uname -a
ls -l /boot/.
file -L /lib/libc.so.6
dpkg -l | grep linux
Send this in a follow up comment. Thanks.