This is a bit different to verify, since it's kernel scripting and infrastructure rather than doing testing with the proposed kernel itself.
But I tested it on groovy in the past, so the same should apply now with focal ...
This is the same w/o the patch.
Hence I tried to look the patch up:
$ git log --oneline --grep "kernelconfig -- only update/edit configurations on architectures we have compiler support"
6b7b30d9153f UBUNTU: [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support
It seems to be there but untagged and 'ambiguous':
$ git tag --contains 6b7b30d9153f
warning: refname '6b7b30d9153f' is ambiguous.
6b7b30d9153f
6b7b30d9153ffc0cedfb1016b7c86edea1ec468c
Using the full hash I get the following output:
$ git show 6b7b30d9153ffc0cedfb1016b7c86edea1ec468c | head -n 8
warning: refname '6b7b30d9153ffc0cedfb1016b7c86edea1ec468c' is ambiguous.
Git normally never creates a ref that ends with 40 hex characters
because it will be ignored when you just specify 40-hex. These refs
may be created by mistake. For example,
git switch -c $br $(git rev-parse ...)
where "$br" is somehow empty and a 40-hex ref is created. Please
examine these refs and maybe delete them. Turn this message off by
running "git config advice.objectNameWarning false"
commit 6b7b30d9153ffc0cedfb1016b7c86edea1ec468c
Author: Andy Whitcroft <email address hidden>
Date: Wed Aug 12 22:28:28 2020 +0100
UBUNTU: [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support
We can only rebuild, edit, or update a configuration for an architecture
nativly on that architecture or using a compatible cross-compiler for
$
Even if the commit is the refname is marked as ambiguous, it seems to be in...
On groovy updateconfigs (on a non-amd64 system, like s390x) works and seems to be properly tagged:
$ git tag --contains 9705125c876a3268d17562bb8e46f53dfb8e6580
9705125c876a
Ubuntu-5.8.0-20.21
...
Ubuntu-5.8.0-30.32
So I'm setting the tag 'verification-failed-focal' here, even if this is kernel infrastructure, hence it does NOT block the proposed kernel itself.
This is a bit different to verify, since it's kernel scripting and infrastructure rather than doing testing with the proposed kernel itself.
But I tested it on groovy in the past, so the same should apply now with focal ...
I created a fresh focal master-next clone on a s390x system, like this: /git.launchpad. net/~ubuntu- kernel/ ubuntu/ +source/ linux/+ git/focal --branch master-next --single-branch focal-clean
$ git clone https:/
I installed everything needed to build a kernel (in fact I used my already existing build system that is known to work).
$ fakeroot debian/rules clean
succeeds
$ fakeroot debian/rules updateconfigs
fails, with:
... kconfig/ conf --syncconfig Kconfig Kconfig. include: 35: compiler 'x86_64- linux-gnu- gcc' not found kconfig/ Makefile: 73: syncconfig] Error 1 ubuntu/ focal-master- next/Makefile: 617: syncconfig] Error 2 ubuntu/ focal-master- next/build' ubuntu/ focal-master- next' rules.d/ 1-maintainer. mk:48: updateconfigs] Error 2
scripts/
scripts/
make[3]: *** [../scripts/
make[2]: *** [/home/
make[2]: Leaving directory '/home/
make[1]: *** [Makefile:179: sub-make] Error 2
make[1]: Leaving directory '/home/
make: *** [debian/
This is the same w/o the patch.
Hence I tried to look the patch up:
$ git log --oneline --grep "kernelconfig -- only update/edit configurations on architectures we have compiler support"
6b7b30d9153f UBUNTU: [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support
It seems to be there but untagged and 'ambiguous':
$ git tag --contains 6b7b30d9153f cedfb1016b7c86e dea1ec468c
warning: refname '6b7b30d9153f' is ambiguous.
6b7b30d9153f
6b7b30d9153ffc0
Using the full hash I get the following output:
$ git show 6b7b30d9153ffc0 cedfb1016b7c86e dea1ec468c | head -n 8 0cedfb1016b7c86 edea1ec468c' is ambiguous.
warning: refname '6b7b30d9153ffc
Git normally never creates a ref that ends with 40 hex characters
because it will be ignored when you just specify 40-hex. These refs
may be created by mistake. For example,
git switch -c $br $(git rev-parse ...)
where "$br" is somehow empty and a 40-hex ref is created. Please objectNameWarni ng false" cedfb1016b7c86e dea1ec468c
examine these refs and maybe delete them. Turn this message off by
running "git config advice.
commit 6b7b30d9153ffc0
Author: Andy Whitcroft <email address hidden>
Date: Wed Aug 12 22:28:28 2020 +0100
UBUNTU: [Packaging] kernelconfig -- only update/edit configurations on architectures we have compiler support
We can only rebuild, edit, or update a configuration for an architecture
nativly on that architecture or using a compatible cross-compiler for
$
Even if the commit is the refname is marked as ambiguous, it seems to be in...
On groovy updateconfigs (on a non-amd64 system, like s390x) works and seems to be properly tagged: 8d17562bb8e46f5 3dfb8e6580
$ git tag --contains 9705125c876a326
9705125c876a
Ubuntu-5.8.0-20.21
...
Ubuntu-5.8.0-30.32
So I'm setting the tag 'verification- failed- focal' here, even if this is kernel infrastructure, hence it does NOT block the proposed kernel itself.