Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Buster kernel built numbers screwed up #1158

Closed
MrEngman opened this issue Jun 25, 2019 · 7 comments
Closed

Buster kernel built numbers screwed up #1158

MrEngman opened this issue Jun 25, 2019 · 7 comments

Comments

@MrEngman
Copy link

No description provided.

@pelwell
Copy link
Contributor

pelwell commented Jun 25, 2019

Can you spare a few words to explain the title?

@MrEngman
Copy link
Author

MrEngman commented Jun 25, 2019

What has happened to the kernel build numbers for the kernel updates since Buster appeared? "#896, #902 and #906".

Kernel build numbers for Buster are using values previously used for kernel 4.4.xx, Jessie.

Someone screwed up the kernel compiles?

MrEngman

@pelwell
Copy link
Contributor

pelwell commented Jun 25, 2019

Has something led you to expect a continuity between build numbers for different releases?

@MrEngman
Copy link
Author

Well, it has been like this since kernel 3.2.27+ #6, Aug 18 2012, apart from an odd error, 3.18.6-v7+ #749 and 3.18.6+ #1. although a similar issue occured when moving from kernel 3.1.9 to 3.2.27, when the builds for 3.1.9 went from #21-#278 and then kernel 3.2.27 reverted to build #6.

MrEngman

@Ferroin
Copy link

Ferroin commented Jun 25, 2019

Kernel build numbers aren't guaranteed unique to begin with. All they represent is that it's the nth kernel built since the last time someone completely cleaned out the build directory, so it takes effort to keep them increasing for a given project. In fact, most distros reset the build number every time the kernel version changes.

@pelwell
Copy link
Contributor

pelwell commented Jun 25, 2019

Thanks - that was my thinking, but a bit of validation is always welcome.

@MrEngman
Copy link
Author

Latest update uses build #1241 so looks like things are back to normal, AFAIK.

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants