staging/nbd/scripts/getver.sh, branch master

build: parsing "git log" breaks with gpg signature verification

2025-09-23T19:49:54Z

Parsing "git log" is fragile. The actual output depends on both global and local configuration files. Enabling "log.showSignature" makes "git log" prefix signed commits with multiple lines of gpg verify output, regardless of the configured log format. Add "--no-show-signature" to "git log" commands to work around this particular issue. Signed-off-by: Bjørn Mork Link: https://github.com/openwrt/openwrt/pull/20127 Signed-off-by: Robert Marko

scripts: getver.sh: approximate version from date

2025-06-26T08:29:50Z

When doing package support and management it is often the case that knowing the corresponding openwrt repo's release version is useful. For example, when adding package changes to the ASU server, the openwrt revision is used as the cutoff for applying those changes. Knowing a package change's hash in its remote feed repo allows us to look up its change date, which we can now use with getver.sh to approximate the revision in openwrt at which it was made. Signed-off-by: Eric Fahlgren Link: https://github.com/openwrt/openwrt/pull/17817 Signed-off-by: Robert Marko

scripts: fix revision calculation using new "main" branch

2024-05-21T15:53:33Z

Fix revision calculation when local branch is rebased on new "main" branch instead of "master". Signed-off-by: Marius Dinu Link: https://github.com/openwrt/openwrt/pull/15538 Signed-off-by: Christian Marangi

scripts/getver.sh: prevent asking for negative rev-parse

2023-11-12T15:19:04Z

With the case of asking an invalid version that is too big, getver.sh might return an invalid output in the form of HEAD~-2260475641. This is caused by BASE_REV - GET_REV using a negative number. Prevent this by checking if BASE_REV - GET_REV actually return 0 or a positive number and set REV variable accordingly. With the following change, invalid revision number will result in unknown printed instead of the invalid HEAD~-NUMBERS output. Signed-off-by: Christian Marangi

scripts/getver.sh: silence rev-list errors

2020-11-02T07:39:49Z

Shallow copies are quite common on CI platforms nowadays, making REBOOT tag unavailable, thus producing following confusing errors in the build logs: fatal: Invalid revision range ee53a240ac902dc83209008a2671e7fdcf55957a..HEAD fatal: Invalid revision range ee53a240ac902dc83209008a2671e7fdcf55957a..0493d57e04774d47921a7d2014b567455d5dc16b Signed-off-by: Petr Štetiar

scripts/getver.sh: append short git hash based on upstream commit

2017-02-01T16:48:45Z

The short git hash suffix printed by getver.sh is taken from the latest local commit, change this to use the hash from latest upstream commit if available. This is considered the intended behavior based on commit message a642a11faca87e2a7bddc1fadb54253e2fc26e84, introducing getver.sh. Signed-off-by: Magnus Kroken Signed-off-by: Felix Fietkau

scripts: getver.sh: append Git short hash to revision

2016-12-02T15:38:55Z

Change getver.sh to append a short Git commit hash to the end of the artifical revision number. This way we still have order- and comparable commit numbers but also a direct relation to the Git commit. The new output format will look like "r2400+2-882472e" for dirty trees or like "r2402-882472e" for clean ones. Signed-off-by: Jo-Philipp Wich

scripts/getver.sh: treat all commits as local if can't find upstream

2016-11-21T13:36:04Z

If something goes wrong and script can't find upstream revision it will return something like: r2220 which looks like a valid upstream revision 2220. We cant' distinguish it from e.g. 2200 upstream commits and 20 local ones. The new format still provides revision number but also points clearly that is may be not the upstream one: r0+2220 Signed-off-by: Rafał Miłecki Acked-by: John Crispin < john@phrozen.org>

scripts/getver.sh: fix older git versions from printing stuff to stdout

2016-07-16T18:50:56Z

Older git versions seem output the original argument to stdout if there is no upstream, presumably because they try to do things with it internally. This can be prevented by passing --verify to it, which should be safe on newer git versions. Signed-off-by: Jonas Gorski

scripts/getver.sh: stop relying on the reboot tag

2016-07-14T11:37:58Z

It may not be present when cloning a staging tree or another fork Signed-off-by: Felix Fietkau