diff options
| author | Prashanth Swaminathan <prashanthsw@google.com> | 2019-07-29 17:40:36 -0700 |
|---|---|---|
| committer | Prashanth Swaminathan <prashanthsw@google.com> | 2019-07-30 17:53:20 -0700 |
| commit | 95aab59a9e9c5f22eb75346e697ffe0dc5ded91c (patch) | |
| tree | fbda7c5fd3f1e6fb6540bd87279c2a2d741a5f2b | |
| parent | 10f28c1f873070c28eb28ec1f59798015e72edb0 (diff) | |
| download | mediatek-95aab59a9e9c5f22eb75346e697ffe0dc5ded91c.tar.gz | |
Fix the SCM version of the repository
The kernel's version is based off the output of the setlocalversion
script, which takes into account CONFIG_LOCALVERSION_AUTO (which we do
not set) and LOCALVERSION (which we also do not set). Based on these
empty defaults, the script relies on the git history to determine
whether or not to append a '+' symbol to indicate that this is a kernel
with patches (e.g. '4.4.95+').
We rely on this '+' symbol as other proprietary code hard-codes these
paths. However, buildbots make no guarantees about the state of the .git
history (b/138144743#comment6), leading to scenarios where runs
conducted on different buildbots lead to the kernel being built with or
without the '+'. While this doesn't break the kernel, it does break
other binaries relying on the /sys/module/kernel path.
Separately, we should look into removing this dependency. For the short
term, we short-circuit this path by creating an .scmversion file. This
identifies the kernel as having been built with modified sources.
Bug: 138144743
Test: Verified that repeated builds result in the proper version string.
Change-Id: I997b705a45a3c3c5c255c9b58da346e83d65a36e
| -rw-r--r-- | .scmversion | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/.scmversion b/.scmversion new file mode 100644 index 000000000000..924cb07136d6 --- /dev/null +++ b/.scmversion @@ -0,0 +1 @@ +4.4.95 |