Matt, can you please provide the details about the upgrade failure you
experience?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/929552
Title:
Upgrade of resolvconf from 1.63ubuntu* to 1.63ubuntu7
This appears to make a "apt-get upgrade" fail on a precise debootstrap
chroot (on powerpc, at least).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/929552
Title:
Upgrade of resolvconf from 1.63ubunt
[Expired for resolvconf (Ubuntu) because there has been no activity for
60 days.]
** Changed in: resolvconf (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
Kosmonaut, asbenicio: Do you get this failure with resolvconf
1.63ubuntu8?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/929552
Title:
Upgrade of resolvconf from 1.63ubuntu* to 1.63ubuntu7 fails: st
Once #936835 is fixed, the likelihood of the resolvconf Upstart job
failing to start will be reduced and the installation failures reported
here (#929552, #929641) might disappear --- without the underlying
cause(s) being eliminated.
Once #936835 is fixed, that is, the resolvconf Upstart job will
So the answer to my question (#16) was that the resolvconf Upstart job
was failing to start at boot time because of #927803.
The misbehavior reported here (#929552) occurs post-boot so I am
doubtful that it has the same cause.
--
You received this bug notification because you are a member of Ubu
