os-release: disable 'pseudo' for git

bitbake recipes are run under a process monitor called 'pseudo'.
We are observing cases where these are triggering a "Pseudo Abort" due
to inode reuse (https://wiki.yoctoproject.org/wiki/Pseudo_Abort) of
some sort.  'pseudo' is used for running operations which may require
higher levels of privledge and recording them so they can be re-applied
when building a file system.  The `git` calls we are doing are to
determine the revision of the repository and therefore do not need
'pseudo' support.  Disable it with the PSEUDO_DISABLED=1 env var.

Also, add a bb.warn call of any exception that is caused by the `git`
call for future debugging.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: Ie1b1f3b1ae0b66f850f9f3cdf5146db8b2e68466
1 file changed
tree: 1bf9f99cc01ed770495d24e9596665c9be646f2e
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. raspberrypi/
  6. recipes-connectivity/
  7. recipes-core/
  8. recipes-devtools/
  9. recipes-extended/
  10. recipes-graphics/
  11. recipes-phosphor/
  12. recipes-protocols/
  13. recipes-support/
  14. recipes-textproc/
  15. recipes-x86/
  16. COPYING.apache-2.0
  17. COPYING.MIT
  18. LICENSE
  19. MAINTAINERS
  20. README.md
  21. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.