I thought i’d use git tags to determine the version for my rpm packages, but that seems broken. According to https://sailfishos.org/wiki/Application_SDK_Packaging_Apps#Version_.28required.29, setting
0 should result in a version determined by the git tag. In particular, when the current HEAD is the same as the last tag, and the working directory is clean, this should give me version
0.4. However, it gets me something like
So since that is broken, I changed the
Version field in the yaml file back to
0.4. This is picked up by the build in qtcreater, but sfdk builds keep setting version to something with the suffix appended. Before I changed it to
0, it would correctly use the version as specified in the yaml file. How can I go back to the old behaviour that correctly uses the version specified in yaml? Also, why doesn’t setting it to
0 work as advertised?
gmc@coltrane:~/src/sailfish/tasks/build$ grep Version ../tasks/rpm/harbour-tasks.* ../tasks/rpm/harbour-tasks.spec:Version: 0.4 ../tasks/rpm/harbour-tasks.yaml:Version: 0.4 gmc@coltrane:~/src/sailfish/tasks/build$ sfdk build ../tasks/ NOTICE: Appending changelog entries to the .spec file… Setting version: 0.4+master.20201106191949.ef2bef8 Building target platforms: i486-meego-linux-gnu ...
Note: when I ssh into the build vm, and execute mb2 myself, things work as expected. So what is sfdk caching that should not be cached?