I was able to reproduce the reported behavior by rebooting in the middle
of the upgrade, after resolvconf has been unpacked and its preinst run,
but before its configuration files have been installed and the package
configured. Then the /run/resolvconf that was created in
resolvconf.preinst gets lost but the resolvconf upstart job has not been
enabled yet (i.e., the file is still called '/etc/init/resolvconf.conf
.dpkg-new') so /run/resolvconf is not created on boot either. Then in
resolvconf.postinst the line
cp -a /etc/resolv.conf /run/resolvconf/resolv.conf
which comes *before*
invoke-rc.d resolvconf start || exit $?
fails with "cp: cannot create regular file
`/run/resolvconf/resolv.conf': No such file or directory".
The installation continues and at the end prints that resolvconf failed
configuration. Then a new apt operation retries the configuration step
resulting in another failure exactly like the one reported here
(#933035).
Whether or not both this report (#933035) and its duplicate (#927300)
were submitted for systems that were rebooted between preinst and
conffile-installation of resolvconf, there is at least one bug.
Resolvconf.postinst should not rely upon the presence of
/run/resolvconf/interface but should create it, because such reboots are
physically possible and the package shouldn't be broken by them. A
mkdir -p /run/resolvconf/interface
command is needed early in the "configure" code in resolvconf.postinst.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/933035
Title:
Upgrade from 11.10 to Precise: resolvconf 1.63ubuntu7 fails to
configure with "cp: cannot create regular file
`/run/resolvconf/resolv.conf': No such file or directory"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/933035/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
