Petter Reinholdtsen <p...@hungry.com> writes: > Very good that you did this, and thank you for bringing it to our > attention. It is though not very useful to file it against insserv, as > the problem is likely to be in some other package.
Well, yes, but I didn't know which package. That was part of the "probably unhelpful" part of the bug report, I'm afraid. > Usertagging it to put it on the list of dependency based boot sequencing > issues, and reassign to wicd to get input from the wicd maintainer. It seems unlikely to me that this is a specific wicd problem, since all DHCP methods were affected, including things that had nothing to do with wicd (such as straight network configuration in /etc/network/interfaces followed by ifdown and ifup). It looked more like wicd was affected by a general networking problem. But I could be wrong; maybe something odd was interacting in a way that interfered. > Can you provide the output from /usr/share/insserv/make-testsuite, the > content of /etc/network/interfaces and the version numbers for dhclient, > ifupdown and wicd? Yeah, I can try to reproduce the problem at home this weekend and get you the additional information. That's definitely the next step. > Could this be a variation of #508289? wicd was involved there too. > Reassigning there to see if the maintainer of wicd have input. Hm, maybe. It seems like a similar problem. I can try uninstalling wicd and see if that makes the problem go away, assuming I can reproduce it. More information coming this weekend. Thanks! -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
