Ahh, I see where the kteam tools stuff is supposed to come from. It's not clear if I'm supposed to go down that route and use the mainline-build-one script or not when trying to build the kernel in this case. If I use the mainline-build-one tool:
$ mainline-build-one afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc xenial *** BUILDING: commit:afd2ff9b7e1b367172f18ba7f693dfb62bdcb2dc series:xenial abinum: ... full_version<4.4.0> version<4.4.0> long<v4.4> abinum<040400> fatal: 'xenial' does not appear to be a git repository fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. error: pathspec 'xenial/master' did not match any file(s) known to git. error: Cannot delete the branch 'BUILD.040400' which you are currently on. fatal: A branch named 'BUILD.040400' already exists. The only way this tool works with that syntax is to switch to the master branch, and run it from there. I'm not sure how that's supposed to work with git bisect, given bisect is setting your checked out position. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1652348 Title: initrd dhcp fails / ignores valid response To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1652348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
