On Thu, Jan 21, 2016 at 10:01:57AM -0000, Martin Pitt wrote: > I tried to reproduce this with a 14.04 → 16.04 upgrade in several > scenarios, but I can't yet. Nicolas, do you actually use ifupdown on > this system, i. e. can you please attach your /etc/network/interfaces > and /etc/network/interfaces.d/* ?
> Even if I remove "eth0" from /etc/network/interfaces, 14.04's > resolvconf still creates /run/resolvconf/interfaces/ (it will be empty > then). This happens both in the upstart job (/etc/init/resolvconf.conf) > and in the systemd service (/lib/systemd/system/resolvconf.service). So > it appears to me that resolvconf was never started before you started > the upgrade even. And what happens if resolvconf is upgraded inside a chroot, where services are not started? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1536335 Title: package resolvconf 1.78ubuntu1 failed to install/upgrade: le sous- processus script post-installation installé a retourné une erreur de sortie d'état 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1536335/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
