On 09/27/2012 12:08 AM, intrigeri wrote: > Jeroen Ooms wrote (27 Sep 2012 03:00:43 GMT) : >> On Wed, Sep 26, 2012 at 10:54 PM, John Johansen >> <[email protected]> wrote: >>> Right, the debian maintainers chose not apply the out of tree >>> networking patch opting instead to wait for us to get the >>> networking support upstream. > > I beg to disagree. IIRC nobody asked them to include that patch. > As far as I'm concerned, I focused on getting the core functionality > in for Wheezy. > Sorry I did not mean to imply that you didn't do what you were asked to do, merely provide some facts in an abbreviated form. We are actually quite happy with the work you did, and the feedback we received. I hope this extended explanation clears things up.
The bug asked to fix certain functionality and you did. The networking patches where floated at the same time as they might have been needed to fix the bug. The networking patch was reviewed and some issues where pointed out and those where fixed. It was asked if they where necessary and it was determined that with a patch to the userspace, to fix a bug, there they where not. At which point it was decided not to include the networking patch because it was not needed to fix the bug. As I recall it there was a comment added to the bug asking for the networking patch but it was late in wheezy's cycle and as far as I am aware a separate bug request for the networking patch was not made. The fact that the networking patch is out of tree made it necessary for a bug to be filed for them to be considered being added. Also I noted during the bug report that the network patch was not something that was going to go upstream, as there was working on improving it and fixing it. I could be wrong but I interpreted comments to have a preference for the networking patchset that would be going upstream instead of having to maintain a dead end patch. Of course this could be because of my own bias against the current networking patch, which is one of the reasons I never filed a bug asking for its inclusion to be considered after it was determined that the networking patches where not necessary to fix the bug that was filed. >> Will this most likely be resolved when wheezy gets released? > > No. Wheezy is currently frozen: > http://release.debian.org/wheezy/freeze_policy.html > > Cheers! > -- AppArmor mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/apparmor
