summaryrefslogtreecommitdiff
path: root/meta-phosphor/classes/image_version.bbclass
AgeCommit message (Collapse)AuthorFilesLines
2021-11-10image_types: Add BUILD_ID to MANIFESTAdriana Kobylak1-0/+18
Add the BUILD_ID value to the MANIFEST so that it can be used alongside the VERSION value to generate a version id during firmware updates. Add a function to read BUILD_ID from the os-release file instead of reading it from a variable because the BUILD_ID value could be set via a os_release.bbappend file instead of a .conf file. Tested: Verified the BUILD_ID value was added to the MANIFEST by default, and when BUILD_ID was specified in a .conf file, and on a os-release.bbappend. Ex: $ cat MANIFEST purpose=xyz.openbmc_project.Software.Version.VersionPurpose.BMC version=2.11.0-dev-566-g263df7f852 BuildId=20211025151654 ExtendedVersion= KeyType=OpenBMC HashType=RSA-SHA256 MachineName=p10bmc Change-Id: I3b7beaccbbd47d8820d499180ccdf021b004cf85 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
2021-10-15meta-phosphor: image: update ConfigParser class namePatrick Williams1-1/+1
As a follow up to 400d9dab03e25d992429f94296caa4938c281fbd, fix the deprecated SafeConfigParser to ConfigParser across the tree. Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: Iabf941889eed97a996b739d77c8107f1f35ce5bf
2021-08-11meta-phosphor: prep for new override syntaxPatrick Williams1-1/+1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I588025b614416c43aa2d053765ab53bacf890cb5
2018-02-23image_version: Add missing os-release dependencyBrad Bishop1-1/+3
Any recipe inheriting image_version must have a dependency on os-release to ensure the sysroot is populated before attempting to get the version out of it. Also read the version out of the target sysroot rather than the host sysroot. os-release does not have a native variant. Tested: Built image and verified in witherspoon qemu Change-Id: I8d79280a75577eff48314f0f57c0015e1d6738ef Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2017-11-16Calculate the version ID of BMC UBI volumes during build time.Saqib Khan1-0/+26
- When the new ubi layout is flashed onto the BMC, the volumes were named kernel-0 and rofs-0 by default. This tends to be misleading as we can't differentiate between two different BMC versions. - Now the ubi volumes will be named kernel-<versionID> and rofs-<versionID> calculated by getting the hash(SHA-512) of the version and taking the first 8 characters. - The Uboot env needs to be updated to point to the correct kernelname which has now changed from kernel-0 to kernel-<versionID> calculated by getting the HASH(SHA-512) of the version and taking the first 8 characters. Resolves openbmc/openbmc#2323 Change-Id: I258d165b399d1ff59ea86f410006f6d03fe13a2e Signed-off-by: Saqib Khan <khansa@us.ibm.com>