Dominique Dumont, I don't think it is sufficient that the dependancy be resolved. I just upgraded two hosts on my network, as a result dnet-common got installed on both. I was aked "configure, don't configure, or leave it alone". I chose "leave it alone", and guess what -- both hosts on my network were given the same mac address.
There was absolutely no indication of this. Not only did my hosts lose their assigned IP's, the entire network broke because this package got installed. Changing mac addresses is kind of a big deal. You can't just do it when somebody picks a default configuration option of "not right now". The dnet-common package needs to be fixed to never, EVER change somebody's MAC address unless they explicitly consent to this action.