Page MenuHomeVyOS Platform
Create Task
Maniphest T6158

Linux kernel version did not matched then caused LTS version building failed
Closed, WontfixPublicBUG
Actions

Description

In few days ago, I built 1.4.0-epa2 successful.

Today, I tried to build it again but it failed.
I noticed that a new commit on github when I trace the error message.
https://github.com/vyos/vyos-build/commit/19039d6622f45dab5b85303ebb504d09e2ce07df

and the error message is

E: there is more than one kernel image file installed!
E: please make sure that kernel_version in data/defaults.toml is up to date
E: if your repository is up to date, then there is a bug
I: Executing update-initramfs -c -k 6.6.21-amd64-vyos
6.6.22-amd64-vyos
Extra argument '6.6.22-amd64-vyos'


Usage: update-initramfs {-c|-d|-u} [-k version] [-v] [-b directory]

Options:
 -k version     Specify kernel version or 'all'
 -c             Create a new initramfs
 -u             Update an existing initramfs
 -d             Remove an existing initramfs
 -b directory   Set alternate boot directory
 -v             Be verbose

See update-initramfs(8) for further details.

In this situation, how should I build a specific LTS version with the github tag?
Please help me, thanks !

Details

Version
1.4.0-epa2
Is it a breaking change?
Unspecified (possibly destroys the router)
Issue type
Unspecified (please specify)

Event Timeline

chesskuo created this task.Mar 22 2024, 3:35 PM
pasik subscribed.Mar 22 2024, 3:51 PM
Viacheslav closed this task as Wontfix.Mar 22 2024, 7:53 PM
Viacheslav claimed this task.
Viacheslav subscribed.

Tags show the code base at the step where the tag was added.
But binary can be changed since this time. For the same reason, you will not be able to build 1.1.8 or 1.2.1, etc. exactly with those binary that were on the step of tagging.
Close it as wonfix.

chesskuo added a comment.Mar 23 2024, 4:30 AM

Hello @Viacheslav ,

Thanks for your reply.
But I have some questions about this situation.
Because it is something different with I knew "version meaning".

For now, the building method seems that I always need to build the lastest commit wherever it is LTS branch or rolling branch.

If LTS is for stable purpose, the version tag means it is stable enough and has a bundle of patch to release this time, right ?

If I always need to build the lastest commit, how should I understand the new commit after the release tag?
This situation still like rolling branch that has "no version".

Thanks