Bug#855598: src:ifupdown2: allow-hotplug behaves differently, not UPing interfaces

2017-02-20 Thread Roopa Prabhu
Thanks for reporting the issue Bernhard. I see the difference, we will make it similar to ifupdown and submit a fix in the next update as soon as we can. ifupdown: === ifup_hotplug () { if [ -d /sys/class/net ] then ifaces=$(for iface in $(ifquery --list --allow=hotplug)

Bug#855401: ifupdown2 [1.0~git20170114-1~bpo8+1/jessie-backports] missing python-pkg-resources dependency

2017-02-19 Thread Roopa Prabhu
Thanks for reporting the issue. pkg_resources is only used to get the package version today. We will most likely fix it by removing the use of pkg_resources given so little value it adds. we will post a fix soon. thanks.

Bug#854325: ifupdown2: missing Conflicts: ifupdown

2017-02-12 Thread Roopa Prabhu
On 2/12/17, 2:10 PM, Andreas Beckmann wrote: > On 2017-02-12 19:46, Roopa Prabhu wrote: >> On 2/12/17, 1:29 AM, Andreas Beckmann wrote: >>> On 2017-02-12 07:01, Roopa Prabhu wrote: >>>> Andreas, Thanks for reporting the issue. We can add 'Conflicts: ifupdown

Bug#854325: ifupdown2: missing Conflicts: ifupdown

2017-02-12 Thread Roopa Prabhu
On 2/12/17, 1:29 AM, Andreas Beckmann wrote: > On 2017-02-12 07:01, Roopa Prabhu wrote: >> Andreas, Thanks for reporting the issue. We can add 'Conflicts: ifupdown'. >> Infact earlier versions of ifupdown2 >> did have the "Conflicts: ifupdown"...but in ord

Bug#854325: ifupdown2: missing Conflicts: ifupdown

2017-02-11 Thread Roopa Prabhu
Andreas, Thanks for reporting the issue. We can add 'Conflicts: ifupdown'. Infact earlier versions of ifupdown2 did have the "Conflicts: ifupdown"...but in order to have both ifupdown and ifupdown2 co-exist, we removed the "Conflicts: ifupdown" in the recent versions of ifupdown2. We did this pri

Bug#843565: ifupdown2: Unsupported keyword (wpa-ssid) (wpa-psk) after upgrade to 1.0~git20161101-1

2016-11-07 Thread Roopa Prabhu
It appears we have enabled a config that should have been off by default for debian ifupdown scripts. Please set the attribute addon_syntax_check=0 in ifupdown2.conf to disable syntax checking. /etc/network/ifupdown2/ifupdown2.conf # enable addon module syntax check: # Python addon modules regis

Bug#813046: ifupdown2: No network connection on startup

2016-01-31 Thread roopa
Thanks for the report. We were able to reproduce it. working on a fix. On 1/28/16, 12:43 PM, Thomas Mayer wrote: > Package: ifupdown2 > Version: 1.0~git20151029-1 > Severity: important > > Dear Maintainer, > > after migration from ifupdown to ifupdown2, network connections are not > available aut

Bug#810844: ifupdown2: Unlisted dependencies

2016-01-12 Thread roopa
Thanks for the report. agreed. I will submit a fix with appropriate dependencies. ifupdown2 is running today on a distribution with latest networking tools on linux mainly iproute2. You may see warnings related to ip and other commands if not available. will fix it. On 1/12/16, 11:38 AM, Alex

Bug#801915: ifupdown2: unowned directory after purge: /etc/network/interfaces.d/

2015-10-17 Thread roopa
On 10/15/15, 8:14 PM, Andreas Beckmann wrote: > Package: ifupdown2 > Version: 1.0~git20150917-1 > Severity: important > User: debian...@lists.debian.org > Usertags: piuparts > > Hi, > > during a test with piuparts I noticed your package left unowned > directories on the system after purge, which is

Bug#786902: (no subject)

2015-05-27 Thread roopa
We would love to keep ifupdown alive and very interested in submitting ifupdown2 as an alternative to ifupdown. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#600723: Attached patch supports bridge_pathcost and bridge_portprios to set pathcost and priority on multiple bridge ports

2013-03-18 Thread Roopa Prabhu
--- /etc/network/if-pre-up.d/bridge.orig2013-03-15 19:04:33.0 + +++ /etc/network/if-pre-up.d/bridge 2013-03-15 18:58:07.0 + @@ -55,9 +55,11 @@ ifconfig $IFACE down || exit 1 fi +BRIDGE_PORTS=$(bridge_parse_ports $INTERFACES | tr '\n' ' ') + all_interfac

Bug#600723: bridge-utils: multiple bridge_pathcost options are not supported

2013-03-12 Thread Roopa Prabhu
The error " vpnbox-f2-en1:/etc/network# ifup mybridge /etc/network/interfaces:39: duplicate option ifup: couldn't read interfaces file "/etc/network/interfaces" is not seen in 1.5-6. However there is another error in 1.5-6. Multiple bridge_pathcost lines in in /etc/network/interfaces for m