On Thu, Apr 10, 2014 at 8:43 AM, Shridatt Sugrim <ssugrim@xxxxxxxxxxxxxxxxxx> wrote: > Thanks Luis, and Backports :) > > I'm pretty sure I've cloned that repo because I was reading the docs from > back ports wiki. I guess I should build the 3.2.y that's in the similarly > branch instead of trying to keep my tree? I'm under the impression you have a backports on a linux-3.2.y branch (maybe we should rename these branches to backports-3.2.y for emphasis and to distinguish from Linux names), if so my objective was to try to convince you that that branch is only for backporting 3.2 kernel code. In other words it would produce a backports-3.2 sort of release, and that release can be used for *any* supported kernel below 3.2, it *is not* mean to be used when you are on the 3.2 kernel on your Debian box. You want the latest and greatest backports releases, either the latest stable release or one based on linux-next. We've struggled with trying to educate a bit better on this buts its unclear what we can do to help with this mild but very important difference. > I'll give the update manager a > shot and see what happens, if not I'll try to build what is in the 3.2.y > branch with my running config, and hope that it works. You don't want to use the 3.2.y branch on either linux or backports, you want to use the 3.14.y branch on both, or if daring try the master branch on backports and a respective linux-next tag. That or you can wait for a public backports-3.14.y release or a new linux-next based release. Luis -- To unsubscribe from this list: send the line "unsubscribe backports" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
