Hi Jernej, I faced similar issue some time all, I don't remember all the details but in some special cases the script get the wrong information. I think it happens when we do git reset --hard to some commit from old release.
I cloned again and it got fixed. BR, Alan On Wednesday, January 4, 2023, Jernej Turnsek <jernej.turn...@gmail.com> wrote: > Hi, > > I have done the prune and prune-tags option again and now it seems to work > ok. The .version file gets the proper version, although git describe > command still gives me 8.2 version. > > On Tue, Jan 3, 2023 at 2:50 PM Gregory Nutt <spudan...@gmail.com> wrote: > > > Look at the hidden file .version. You will need to modify that file as > > you see fit. It is not controlled under GIT (but is provided with each > > new release package). > > > > On 1/3/2023 2:38 AM, Jernej Turnsek wrote: > > > Hi All, > > > > > > when building the latest NuttX OS from git, I am having problems with > > > .version file, where wrong version is used. Running the git describe, I > > > get nuttx-8.2-12100-g56c6943311, although I have the latest code. I > have > > > updated the local repo from upstream with --prune and --prune- tags > > option > > > to get the latest tagging, but all the tags after 8.2 are on releases > and > > > not the master branch, thus describe command is not seeing them. I was > > also > > > trying to manually run the version.sh script, but make command is > always > > > overriding the version. How to get around the problem, without using > the > > > release? > > > > > > Thanks, Jernej > > > > > > > >
