Bugs fixes in "resolvconf"
Origin | Bug number | Title | Date fixed |
---|---|---|---|
Launchpad | 989585 | resolvconf failed to install/upgrade because /etc/r... | 2012-05-03 |
Launchpad | 953257 | resolvconf.8 manpage points to /etc/dhcp3 instead o... | 2012-03-18 |
Launchpad | 949473 | resolvconf is unaware of biosdevname NIC names | 2012-03-18 |
Launchpad | 932275 | Bogus or no nameserver information written to /etc/network/interfaces | 2012-02-25 |
Launchpad | 933723 | resolvconf creating bogus resolv.conf file | 2012-02-20 |
Launchpad | 923685 | Installing resolvconf causes loss of manually entered nameserver information in resolv.conf | 2012-02-20 |
Launchpad | 933566 | Stopping resolvconf doesn't disable updates | 2012-02-20 |
Launchpad | 924836 | network-manager does not tell plymouth it has started | 2012-02-02 |
Launchpad | 922491 | lucid to precise server upgrade: resolvconf failed to upgrade: cp cannot create regular file `/run/resolvconf/resolv.conf': No such file or directory | 2012-01-28 |
Launchpad | 922578 | please remove 'resolvconf' from ubuntu-minimal Depends | 2012-01-27 |
Launchpad | 366967 | ifupdown-udev integration should be thought-out more thoroghly | 2011-12-20 |
Launchpad | 797339 | apparmor profile for bind. resolvconf error | 2011-12-20 |
Ubuntu | 386822 | resolvconf: "Jaunty: Does not create run directory in /var/run" | 2011-12-19 |
About
-
Send Feedback to @ubuntu_updates