kbuild: Restore .version auto-increment behaviour for Debian packages
PATCH 1/1 kbuild: Restore .version auto-increment behaviour for Debian packages
Since 2df8220cc511 ("kbuild: build init/built-in.a just once"), generating Debian packages using 'make bindeb-pkg' results in packages that are stuck to the same .version, leading to unexpected behaviours (multiple packages with the same version).
That's because the mkdebian script samples the build version before building the kernel, and forces the use of that version number for the actual build.
Restore the previous behaviour by calling init/build-version instead of reading the .version file. This is likely to result in too many .version bumps, but this is what was happening before (although the bump was affecting builds made after the current one).
Eventually, this script should be turned into something that is a bit less counter-intuitive (building the kernel first and only then generating the packaging artefacts).
---
Notes:
v2: Drop the RPM version which was wrong, and make the path
relative to $srctree.
scripts/package/mkdebian | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
scripts/package/mkdebian +1 -1
@@ -90,7 +90,7 @@ if [ -n "$KDEB_PKGVERSION" ]; then packageversion=$KDEB_PKGVERSION revision=${packageversion##*-} else - revision=$(cat .version 2>/dev/null||echo 1) + revision=$($srctree/init/build-version) packageversion=$version-$revision fi sourcename=$KDEB_SOURCENAME
Signature · 1 line
2.34.1
Quoted 6 lines · Marc Zyngier
Since
2df8220cc511("kbuild: buildinit/built-in.ajust once"), generating Debian packages using 'make bindeb-pkg' results in packages that are stuck to the same .version, leading to unexpected behaviours (multiple packages with the same version).
Quoted 8 lines
That's because the mkdebian script samples the build version before building the kernel, and forces the use of that version number for the actual build.
Restore the previous behaviour by calling
init/build-versioninstead of reading the .version file. This is likely to result in too many .version bumps, but this is what was happening before (although the bump was affecting builds made after the current one).
What do you mean by "too many .version bumps"?
Every "make bindeb-pkg" increments the version by one.
Is there any case where it increases more?
Quoted 3 lines
Eventually, this script should be turned into something that is a bit less counter-intuitive (building the kernel first and only then generating the packaging artefacts).
How to achieve this?
The version is recorded in debian/chanegelog.
Without it, dpkg-buildpackage fails.
In my understanding, the version must be fixed before building the kernel.
Quoted 29 lines
Fixes 2df8220cc511 ("kbuild: build init/built-in.a just once")Signed-off-by Marc Zyngier <[email protected]>Cc Masahiro Yamada <[email protected]>Cc Michal Marek <[email protected]>Cc Nick Desaulniers <[email protected]>---
Notes:
v2: Drop the RPM version which was wrong, and make the path
relative to $srctree.scripts/package/mkdebian | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)scripts/package/mkdebian +1
-2@@ -90,7 +90,7 @@ if [ -n "$KDEB_PKGVERSION" ]; then packageversion=$KDEB_PKGVERSION revision=${packageversion##*-} else - revision=$(cat .version 2>/dev/null||echo 1) + revision=$($srctree/init/build-version) packageversion=$version-$revision fi sourcename=$KDEB_SOURCENAME --
Quoted 2 lines
2.34.1
--
Best Regards
Masahiro Yamada
Quoted 18 lines · Masahiro Yamada
Quoted 6 lines · Marc Zyngier
Since
2df8220cc511("kbuild: buildinit/built-in.ajust once"), generating Debian packages using 'make bindeb-pkg' results in packages that are stuck to the same .version, leading to unexpected behaviours (multiple packages with the same version).Quoted 8 lines
That's because the mkdebian script samples the build version before building the kernel, and forces the use of that version number for the actual build.
Restore the previous behaviour by calling
init/build-versioninstead of reading the .version file. This is likely to result in too many .version bumps, but this is what was happening before (although the bump was affecting builds made after the current one).
Quoted 3 lines
What do you mean by "too many .version bumps"?
Every "make bindeb-pkg" increments the version by one.
And isn't that a problem? We increase the build number pointlessly, even if there is *nothing* to change.
Quoted 2 lines
Is there any case where it increases more?
No, but that's bad enough IMHO.
Quoted 6 lines
Quoted 3 lines
Eventually, this script should be turned into something that is a bit less counter-intuitive (building the kernel first and only then generating the packaging artefacts).
How to achieve this?
By building the kernel *before* sampling the version number, just like RPM does.
Quoted 3 lines
The version is recorded in debian/chanegelog.
Without it, dpkg-buildpackage fails.
And again, nothing forces us to do it in that order.
Quoted 1 line
In my understanding, the version must be fixed before building the kernel.
Can't immediately see what mandates it, but I'm sure you know better.
Anyway, the current situation needs fixing. If you're unhappy with the patch, feel free to replace it with something that you consider more appropriate.
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Quoted 21 lines · Marc Zyngier
Quoted 18 lines · Masahiro Yamada
Quoted 14 lines · Marc Zyngier
Since
2df8220cc511("kbuild: buildinit/built-in.ajust once"), generating Debian packages using 'make bindeb-pkg' results in packages that are stuck to the same .version, leading to unexpected behaviours (multiple packages with the same version).That's because the mkdebian script samples the build version before building the kernel, and forces the use of that version number for the actual build.
Restore the previous behaviour by calling
init/build-versioninstead of reading the .version file. This is likely to result in too many .version bumps, but this is what was happening before (although the bump was affecting builds made after the current one).
Quoted 6 lines
Quoted 3 lines
What do you mean by "too many .version bumps"?
Every "make bindeb-pkg" increments the version by one.
And isn't that a problem? We increase the build number pointlessly, even if there is *nothing* to change.
I think "make *-pkg" should increment the version every time.
The .version is incremented only when vmlinux is updated.
When you change module code, only *.ko is relinked. The .version stays because it is embedded in vmlinux.
Even if you build the kernel first, and .version has no change, the package contents may have some changes.
Quoted 34 lines
Quoted 2 lines
Is there any case where it increases more?
No, but that's bad enough IMHO.
Quoted 6 lines
Quoted 3 lines
Eventually, this script should be turned into something that is a bit less counter-intuitive (building the kernel first and only then generating the packaging artefacts).
How to achieve this?
By building the kernel *before* sampling the version number, just like RPM does.
Quoted 3 lines
The version is recorded in debian/chanegelog.
Without it, dpkg-buildpackage fails.And again, nothing forces us to do it in that order.
Quoted 1 line
In my understanding, the version must be fixed before building the kernel.
Can't immediately see what mandates it, but I'm sure you know better.
Anyway, the current situation needs fixing. If you're unhappy with the patch, feel free to replace it with something that you consider more appropriate.
M.--
Without deviation from the norm, progress is not possible.
Signature · 2 lines
Best Regards Masahiro Yamada
Quoted 25 lines · Masahiro Yamada
Quoted 23 lines · Marc Zyngier
Quoted 20 lines · Masahiro Yamada
Quoted 6 lines · Marc Zyngier
Since
2df8220cc511("kbuild: buildinit/built-in.ajust once"), generating Debian packages using 'make bindeb-pkg' results in packages that are stuck to the same .version, leading to unexpected behaviours (multiple packages with the same version).Quoted 8 lines
That's because the mkdebian script samples the build version before building the kernel, and forces the use of that version number for the actual build.
Restore the previous behaviour by calling
init/build-versioninstead of reading the .version file. This is likely to result in too many .version bumps, but this is what was happening before (although the bump was affecting builds made after the current one).What do you mean by "too many .version bumps"?
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
Every "make bindeb-pkg" increments the version by one.
And isn't that a problem? We increase the build number pointlessly, even if there is *nothing* to change.
I think "make *-pkg" should increment the version every time.
But that's not what the rpm package builder does.
Quoted 10 lines
The .version is incremented only when vmlinux is updated.
When you change module code, only *.ko is relinked. The .version stays because it is embedded in vmlinux.
Even if you build the kernel first, and .version has no change, the package contents may have some changes.
And again, isn't that an inconsistency?
Anyway, enough idle arguing. What do want me to do about this bug?
M.
Signature · 1 line
Without deviation from the norm, progress is not possible.
Quoted 42 lines · Marc Zyngier
Quoted 25 lines · Masahiro Yamada
Quoted 23 lines · Marc Zyngier
Quoted 20 lines · Masahiro Yamada
Quoted 6 lines · Marc Zyngier
Since
2df8220cc511("kbuild: buildinit/built-in.ajust once"), generating Debian packages using 'make bindeb-pkg' results in packages that are stuck to the same .version, leading to unexpected behaviours (multiple packages with the same version).Quoted 8 lines
That's because the mkdebian script samples the build version before building the kernel, and forces the use of that version number for the actual build.
Restore the previous behaviour by calling
init/build-versioninstead of reading the .version file. This is likely to result in too many .version bumps, but this is what was happening before (although the bump was affecting builds made after the current one).What do you mean by "too many .version bumps"?
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
Every "make bindeb-pkg" increments the version by one.
And isn't that a problem? We increase the build number pointlessly, even if there is *nothing* to change.
I think "make *-pkg" should increment the version every time.
But that's not what the rpm package builder does.
Quoted 4 lines
The .version is incremented only when vmlinux is updated.
Quoted 8 lines
Quoted 6 lines
When you change module code, only *.ko is relinked. The .version stays because it is embedded in vmlinux.
Even if you build the kernel first, and .version has no change, the package contents may have some changes.
And again, isn't that an inconsistency?
Yes, it is inconsistent.
Basically, I want all *-pkg targets working in the same way. Changing binrpm-pkg is easy (Bump the version first), but the opposite way is impossible (at least, I cannot come up with a good solution).
Quoted 7 lines
Anyway, enough idle arguing. What do want me to do about this bug?
M.--
Without deviation from the norm, progress is not possible.
I dropped the last paragraph, and applied. Thanks.
Signature · 2 lines
Best Regards Masahiro Yamada