/srv/irclogs.ubuntu.com/2017/07/07/#ubuntu-kernel.txt

=== klebers_ is now known as klebers
=== mms is now known as shabgard
wileiHi! Should there be (in the mainline-crack GIT repository) tags for 4.11.8 and 4.11.9 kernels? I'm trying to build custom kernel from mainline-crack and after "git fetch" the command "git checkout -b `cat COMMIT`" I get error: 'fatal: reference is not a tree: f82a53b87594f460f2dd9983eeb851a5840e8df8' and that's for 4.11.9. And the command "git tag" doesn't return 4.11.9 nor 4.11.8...07:56
apwwilei, what does COMMIT contain ?08:25
apwwilei, the master repo for that has 4.11.9 in it08:27
wileiapw, COMMIT is copy of http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11.9/COMMIT08:29
apwdoes the instructions tell you to git checkout -b `cat COMMIT`08:30
apwthat sounds wrong to me08:30
apwgit checkout -b test `head -1 COMMIT`08:30
apwwilei, does that work ?08:30
wileiI'll try that08:31
apwwilei, where are the instructions you are following08:32
wileithat worked. but wierdly that `cat COMMIT´ worked for v.4.10.17... :) 08:32
apwas i suspect we have enhanced the content of COMMIT at some point, perhaps our instructions are wrong08:33
wileiapw, I'm mixing these instructions: https://wiki.ubuntu.com/Kernel/MainlineBuilds and https://wiki.ubuntu.com/KernelTeam/GitKernelBuild08:33
apw(and if they say that command they are)08:33
apwwilei, ok the only reference on that page to COMMIT is not related to the contents of the COMMIT file in a mainline build08:34
wileifiles http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.10.17/COMMIT and http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.11.9/COMMIT doesn't differ that much 08:34
apwwilei, perhaps so but you are asking it to interpolate those two lines on the end08:35
apwof the git ceckout -b08:35
apwso you get:08:35
wileiyeah08:35
apwgit checkout -b v4.10.17 17a4d48033813f2ba893d6918fa2931afcd9af0208:35
apwwhich is asking ot make a local branch under the name of a likely existing tag08:35
apwthat is just asking for trouble08:35
apwthe first line is the tag name in that repo which you want, the second line is a check08:36
apwso we can tell if the tag changes, which it never should08:36
wileitrue :) thanks!08:36
apwgit checkout -b <useful branch name> `head -1 COMMIT`08:37
apwmakes sense08:37
wileibut actually not :) 08:43
wileigit checkout -b v4.11.9 `head -1 ../v4.11.9/COMMIT` returns fatal: Cannot update paths and switch to branch 'v4.11.9' at the same time.08:43
wileiand if I run command "git checkout -b dev f82a53b87594f460f2dd9983eeb851a5840e8df8" I still get error "fatal: reference is not a tree: f82a53b87594f460f2dd9983eeb851a5840e8df8"08:44
wileithe f82a53b87594f460f2dd9983eeb851a5840e8df8 is reference for tag v4.11.9 which is missing from mainline-crack08:45
wileimainline-crack as git://git.launchpad.net/~ubuntu-kernel-test/ubuntu/+source/linux/+git/mainline-crack08:46
wileibut it exists in git://kernel.ubuntu.com/virgin/testing/crack.git08:46
wilei"git tag | grep v4.11" doesn't return v4.11.8 nor v4.11.9 when done in clone of mainline-crack, so the tags are missing :)  08:47
apwwilei, no you already have a branch08:49
apwyou made it when it went wrong before08:49
apwdon't use tag names for your branch08:49
apwand use a "new" branch name with using -b08:49
wileionly branches I've in my clone are master and v4.10.1708:50
wileiand v4.10.17 is checkouted just like I was trying to checkout v4.11.9 08:51
apwwilei | git checkout -b v4.11.9 `head -1 ../v4.11.9/COMMIT` returns fatal: Cannot update paths and switch to branch 'v4.11.9' at the 08:51
apwif it is saying that, you already have a v4.11.9 _thing_ in your repo08:51
wileiand I tried this too: "git checkout -b wdev f82a53b87594f460f2dd9983eeb851a5840e8df8" resulting "fatal: reference is not a tree: f82a53b87594f460f2dd9983eeb851a5840e8df8"08:51
apwyou cannot trivially name a branch the same as a tag08:51
apwyeah use the tag name08:52
apwgit checkout -b wdev v4.11.908:52
wileiapw, that gives: "fatal: Cannot update paths and switch to branch 'wdev' at the same time."08:52
wileinow I got it working, there was some problem with git fetch so I had to clone repo again08:58
apwwilei, sounds odd, as that error is nothing to do with fetching, but hey, if it is working life is good09:47
lucasrangitWhat is the reason for having debian.master and debian.hwe-edge in https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial/tree/?h=hwe-edge ?22:13

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!