summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorRaptor Engineering Development Team <support@raptorengineering.com>2018-04-12 17:19:02 -0500
committerRaptor Engineering Development Team <support@raptorengineering.com>2018-04-13 04:30:02 -0500
commit22a1def1be010efe99466b4854fc27b34eed95a3 (patch)
tree8bc6a6868d4a0a4a006d1119442f1f42298acc73
parent25194a99873a856183be8cc280313136d183a820 (diff)
downloadtalos-openbmc-22a1def1be010efe99466b4854fc27b34eed95a3.tar.gz
talos-openbmc-22a1def1be010efe99466b4854fc27b34eed95a3.zip
Use proper distro name on Talos builds to pull in OpenPOWER-related packages
-rw-r--r--meta-openbmc-machines/meta-openpower/meta-rcs/meta-talos/conf/local.conf.sample2
1 files changed, 1 insertions, 1 deletions
diff --git a/meta-openbmc-machines/meta-openpower/meta-rcs/meta-talos/conf/local.conf.sample b/meta-openbmc-machines/meta-openpower/meta-rcs/meta-talos/conf/local.conf.sample
index 77399ab01..b3eb50d17 100644
--- a/meta-openbmc-machines/meta-openpower/meta-rcs/meta-talos/conf/local.conf.sample
+++ b/meta-openbmc-machines/meta-openpower/meta-rcs/meta-talos/conf/local.conf.sample
@@ -63,7 +63,7 @@ MACHINE ??= "talos"
# Ultimately when creating custom policy, people will likely end up subclassing
# these defaults.
#
-DISTRO ?= "openbmc-phosphor"
+DISTRO ?= "openbmc-openpower"
# As an example of a subclass there is a "bleeding" edge policy configuration
# where many versions are set to the absolute latest code from the upstream
# source control systems. This is just mentioned here as an example, its not
OpenPOWER on IntegriCloud