** Package changed: ubuntu => cloud-images
** Changed in: cloud-images
Milestone: ubuntu-14.01 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262951
Title:
cloud-images
This is incompatible with what Debian's ifupdown does: source-directory
/etc/network/interfaces.d/. This includes everything without a suffix,
while this change includes every *.cfg file. This makes it rather hard
to write snippets which work on both (which is e. g. necessary for
autopkgtests).
** Changed in: ubuntu
Status: Fix Committed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262951
Title:
cloud-images /etc/network/interfaces shoud source-directory
** Changed in: ubuntu
Milestone: None = ubuntu-14.01
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1262951
Title:
cloud-images /etc/network/interfaces shoud source-directory
interfaces.d
To
So, some thoughts on this that I'd like to get some feedback on
(slangasek or stgraber).
a.) Should we put 'eth0' configuration into /etc/network/interfaces.d?
my feeling is that we should. This is possible to cause some breakage, but
its fine with me to have to fix things. I'd just rather
So the blurb that ifupdown puts in /etc/network/interfaces when it doesn't
exist is:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d
The loopback interface entry is no longer required as it's assumed
Moved eth0 configuration to /etc/network/interfaces.d and now sourced
via /etc/network/interfaces file.
Marking fix commited pending builds through the Cloud Image build
system.
** Changed in: ubuntu
Status: Triaged = Fix Committed
--
You received this bug notification because you are a
