Bug#738909: More on this "Problem"
This was the second time apt-get upgrade placed packages from
experimental (when I am using Sid). The first time, I noticed in time
and stopped it (always run -s first!). This time, I did not notice.
So it placed several experimental packages include libc6-2.18.
System was bootable with this. A terminal session had "3.5.4" instead of
"machine name/path" but worked fine. KDE konsole sessions functioned
normally.
Network was not working, suspected this package, attempted to force
downgrade an accidentally installed the lib6-2.17-udeb (normal packages
was on lintian or something). This killed any bash or sh. The 2.18
package had nothing to do with the network. System was now unbootable.
Went to rescue CD, removed the udeb files from /lib/. Pointed
the /lib/ld-linux.so.2 to the 2.18 package on i386-gnu folder (this is
shown as on file list for the package but is not actually in its .gz!).
Results are the same, with or without this:
Attempt to chroot to the "target" could not run /bin/sh-->bash
Reboot attempt could not run /sbin/init and oopsed out.
As everything appears in order, I am at whits end on how to restore my
system. Any help (email off list) would be greatly appreciated.
Title of the bug might be changed to "Sporadic Update Attempted to
Experimental, Should be Sid."
Happened twice but no consistent way to reproduce. This was sent from
the live CD, no way to really test anything else.
Reply to: