However, base-files 6.3ubuntu3 got uploaded prematurely, thus beginning the transition before other packages were updated to follow suit.
Guessing the guilty commit to be this one:
base-files (6.3ubuntu3) oneiric; urgency=low
* debian/1777-dirs: remove /var/lock (replaced by /run/lock on tmpfs)
* debian/directory-list: remove /var/run and /var/lock, add /run
* debian/postinst.in: replace references to /var/run with /run
-- Scott James Remnant <email address hidden> Thu, 07 Jul 2011 13:33:06 -0400
Presumably downgrading your base-files to version 6.3ubuntu2 or other version prior to this commit will restore your system to working behavior.
Ok, nevermind my post #22. A bit more digging has revealed the problem is this:
upgrade base-files 2011-07-08 01:23:13 6.3ubuntu2 6.3ubuntu4
There is a plan to transition from /var/run to /run, according to this plan:
http:// wiki.debian. org/ReleaseGoal s/RunDirectory
However, base-files 6.3ubuntu3 got uploaded prematurely, thus beginning the transition before other packages were updated to follow suit.
Guessing the guilty commit to be this one:
base-files (6.3ubuntu3) oneiric; urgency=low
* debian/1777-dirs: remove /var/lock (replaced by /run/lock on tmpfs) directory- list: remove /var/run and /var/lock, add /run
* debian/
* debian/postinst.in: replace references to /var/run with /run
-- Scott James Remnant <email address hidden> Thu, 07 Jul 2011 13:33:06 -0400
Presumably downgrading your base-files to version 6.3ubuntu2 or other version prior to this commit will restore your system to working behavior.