Are there any news regarding this problem? >From my point of view, the problem should be clear. The upstream (Debian) changes, that were introduced in the 1.69ubuntu1.1 version, don't work together with the (Ubuntu) postinst script, which causes the empty /etc/resolv.conf during installation, and then subsequent installation steps fail.
So the postinst script needs to be fixed, so network installations are possible again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1392297 Title: resolvconf 1.69ubuntu1.1 breaks network install Status in resolvconf package in Ubuntu: New Bug description: We are experiencing problems with Ubuntu 14.04 network installations, when using the 1.69ubuntu1.1 version of resolvconf. With this version the file /etc/resolv.conf gets reset to an empty file (does only include just the standard resolvconf comments) during the installation of the resolvconf package. After that the name resolution doesn't work anymore and the subsequent installation steps fail. If we use the 1.69ubuntu1 version, everything works fine. If I make a diff of both package contents, the most significant change seems to be the inclusion of a new Sys-V init script, which (besides other things) removes the contents of the resolvconf runtime directories when called with the option "start", and the postinst script calls "invoke-rc.d resolvconf start" at the end (included by dh_installinit), which I think should do nothing during the installation because of policy-rc.d (right?), but I wonder if it actually get's called and removes the resolv.conf file that got migrated to the runtime directories earlier in the postinst script. At least that would explain our problems, because I don't really see anything else, that could cause this problem. I see that the inclusion of the new init script is coming from debian, and they call the dh_installinit with the option "--no-start" in debian/rules, while the Ubuntu package calls the dh_installinit only with the option "-r". And debian inserts the debhelper code a lot earlier in the postinst script. Could this be what's causing the problem? As soon I have more time, I will try to debug this further and provide more information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1392297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
