Yes, I've tested the one from proposed, and the ubiquity side of the bug does not show up in the tests I've ran.
On 11/30/2009, Brian Murray <[email protected]> wrote: > Mario you mentioned the following in comment 9: > > "b) If Network Manager calls update_etc_hosts at the exact same time > that oem-config was changing the hostname, you can run into this > scenario. OEM-config shouldn't be changing the hostname at all in the > first place though as there is no place in the UI to set it." > > and the changelog indicates: > > "* Do not try to configure networking in oem-config (LP: #471498)." > > Shouldn't the fix in ubiquity avoid this particular situation? Has > anybody tested with the version of ubiquity in lucid or karmic-proposed? > > -- > oem-config incorrectly setting up /etc/hosts > https://bugs.launchpad.net/bugs/471498 > You received this bug notification because you are a member of Ubuntu > Installer Team, which is subscribed to ubiquity in ubuntu. > -- Sent from my mobile device Mario Limonciello [email protected] -- oem-config incorrectly setting up /etc/hosts https://bugs.launchpad.net/bugs/471498 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
