[Touch-packages] [Bug 1550539] Re: VMWare network interface name change with wily → xenial upgrade

2017-02-10 Thread Amos Hayes
I just encountered this bug today when upgrading from a fully updated 14.04 server to 16.04 using do-release-upgrade. My static IP configured in /etc/network/interfaces was configured to come up on eth0. Logging in on the console and replacing eth0 with ens32 in that interfaces file and rebooting

[Touch-packages] [Bug 1550539] Re: VMWare network interface name change with wily → xenial upgrade

2016-03-22 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 229-3ubuntu1 --- systemd (229-3ubuntu1) xenial; urgency=medium * Merge with Debian unstable. Remaining Ubuntu changes: - Hack to support system-image read-only /etc, and modify files in /etc/writable/ instead. Upgrade

[Touch-packages] [Bug 1550539] Re: VMWare network interface name change with wily → xenial upgrade

2016-03-22 Thread Simon Déziel
@Martin, correct, the postinst succeeds, sorry for the confusion. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1550539 Title: VMWare network interface name change with

[Touch-packages] [Bug 1550539] Re: VMWare network interface name change with wily → xenial upgrade

2016-03-22 Thread Martin Pitt
@Simon: The postinst certainly writes that error message, but it does not actually fail, right? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1550539 Title: VMWare

[Touch-packages] [Bug 1550539] Re: VMWare network interface name change with wily → xenial upgrade

2016-03-22 Thread Martin Pitt
@Simon: This is tracked in bug 1560112 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1550539 Title: VMWare network interface name change with wily → xenial upgrade

[Touch-packages] [Bug 1550539] Re: VMWare network interface name change with wily → xenial upgrade

2016-03-21 Thread Simon Déziel
@pitti, this new code [*] causes the postinst to fail when no eno* device exist: /var/lib/dpkg/info/udev.postinst: 109: [: Illegal number: * *: https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=ubuntu=47584521cd23ab3490b40b8d95a1748d86ad7f25 -- You received this bug

[Touch-packages] [Bug 1550539] Re: VMWare network interface name change with wily → xenial upgrade

2016-03-01 Thread Herb McNew
The old name was eno1628 and it was a wily install, not upgraded from a previous release. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1550539 Title: VMWare network

[Touch-packages] [Bug 1550539] Re: VMWare network interface name change with wily → xenial upgrade

2016-03-01 Thread Martin Pitt
I added some migration postinst code: http://anonscm.debian.org/cgit /pkg-systemd/systemd.git/commit/?h=ubuntu=e4cad ** Changed in: systemd (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which

[Touch-packages] [Bug 1550539] Re: VMWare network interface name change with wily → xenial upgrade

2016-03-01 Thread Martin Pitt
** Changed in: systemd (Ubuntu) Status: Triaged => In Progress ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.