On Mon, Dec 28, 2015 at 07:49:09AM +0100, Martin Pitt wrote:
> > I can do this in the next release of ifupdown (0.8.5). I'll need to
> > know which version of the udev package to sync with.
>
> How about this: When you upload this, you add a Breaks:/Replaces: udev
> (<< current version + 1~) and
On Wed, Dec 30, 2015 at 12:36:04PM +0100, Martin Pitt wrote:
> > How about this: When you upload this, you add a Breaks:/Replaces: udev
> > (<< current version + 1~) and notify me on this bug
>
> Sorry, this was imprecise: the file conflict is on "systemd" (as that
> ships ifup@.service), the
Hello again,
Martin Pitt [2015-12-28 7:49 +0100]:
> How about this: When you upload this, you add a Breaks:/Replaces: udev
> (<< current version + 1~) and notify me on this bug
Sorry, this was imprecise: the file conflict is on "systemd" (as that
ships ifup@.service), the "logical" breakage is
Package: ifupdown
Severity: wishlist
Version: 0.8.4
Hello,
for historical reasons the udev package has shipped the functionality
for handling network device hotplug events. However, it's a bit weird
to ship the coldplugging parts (/etc/init.d/networking and
networking.service) in ifupdown, but
On Sun, Dec 27, 2015 at 08:58:32PM +0100, Martin Pitt wrote:
> for historical reasons the udev package has shipped the functionality
> for handling network device hotplug events. However, it's a bit weird
> to ship the coldplugging parts (/etc/init.d/networking and
> networking.service) in
Hello Guus,
Guus Sliepen [2015-12-27 23:11 +0100]:
> > * An udev rule which reacts to adding or removing network devices.
> >This is currently shipped as /lib/udev/rules.d/80-networking.rules
> >but I propose that ifupdown ships it as
> >/lib/udev/rules.d/80-ifupdown.rules to avoid a
6 matches
Mail list logo
