yocto-ktn issueshttps://git.kontron-electronics.de/sw/yocto/yocto-ktn/-/issues2021-10-01T08:20:18Zhttps://git.kontron-electronics.de/sw/yocto/yocto-ktn/-/issues/6No revision values when checking out not yet existing layers2021-10-01T08:20:18ZEberhard StollNo revision values when checking out not yet existing layersWhen `init-env` is called the first time without a pre-populated `layers` directory, the output of `init-env` prints `Revision: <None>`, although the checkout is done correctly.
```
user@ubuntu:~/cust/ked/mp1/dunfell/yk$ source init-env...When `init-env` is called the first time without a pre-populated `layers` directory, the output of `init-env` prints `Revision: <None>`, although the checkout is done correctly.
```
user@ubuntu:~/cust/ked/mp1/dunfell/yk$ source init-env build-stm32mp -u -r thud
Passing option: -u to meta-update
Passing option: -r thud to meta-update
Updating core repos...
* yk Branch: master Revision: <None>
* Using build repo URI git@git.kontron-electronics.de:stm32mp/build-stm32mp.git
Cloning/Updating build repos...
Cloning ...
* build-stm32mp Branch: thud Revision: <a0aa17b> (HEAD)
Updating meta layers...
* meta-ktn Branch: thud Revision: <None>
Cloning ...
* meta-ktn-stm32mp Branch: thud Revision: <None>
Cloning ...
* meta-openembedded Branch: master Revision: <None>
Cloning ...
* meta-qt5 Branch: master Revision: <None>
Cloning ...
* meta-st-openstlinux Branch: thud Revision: <None>
Cloning ...
* meta-st-stm32mp Branch: thud Revision: <None>
Cloning ...
* meta-swupdate Branch: thud Revision: <None>
Cloning ...
* openembedded-core Branch: master Revision: <None>
Cloning ...
* bitbake Branch: master Revision: <None>
Cloning ...
```
The expected behaviour would be to print the branch and revision which will be checked out and which are configured in `repo.conf`.
When the checkout is done a second time with an already populated `layers` directory, the revisions are shown!