| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
To enable simultaneous bitbaking of two images with the same branch name, create
a new ref in the OSTree repo using the basename of the image.
As @OYTIS has pointed out, this probably won't solve every problem that might
come up with simultaneous bitbaking, such as if the two images use different
bootloaders. However, it does solve the immediate problem that comes up with our
primary-image + secondary-image example.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|
|
|
|
|
|
| |
Search made with the following regex: getVar ?\((.*), True\), this is
to be consistent with OE.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
|
|
|
|
| |
type -> size.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
|
|
|
|
|
|
| |
Just trying to be careful and consistent. I didn't change every variable in
places where it seemed like it was obvious that we were dealing with purely
local variables.
Signed-off-by: Patrick Vacek <patrickvacek@gmail.com>
|
|
|
|
|
|
| |
Curly braces are necessary around bitbake variables
Signed-off-by: Anton Gerasimov <anton.gerasimov@here.com>
|
|
|
|
|
|
|
| |
Move the dependency do_image_wic -> do_image_ota_ext4 from sota.bbclass
to image_types_ota.bbclass, since it's a image specific dependency.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There are several flaws with ostree tasks, as follows:
- ${IMAGE_NAME}.rootfs.ostree.tar.bz2 is generated, but it's not being
used during ostree commit, so it should be removed if it's just a
intermittent artifact. Or if we intend to deploy this tar.bz2 file,
it should be tracked by sstate cache, that is to day, it should be
generated in ${IMGDEPLOYDIR} rather than in ${DEPLOY_DIR_IMAGE}.
- There are quite a few redundant code like mktemp/cd/rm a directory,
which can be replaced by setting 'dirs', 'cleandirs' varflags.
- There are some redundant variable check logic in image_types_ostree
and image_types_ota bbclass.
To fix the above, we make the following changes:
- Introduce a new conversion image type 'tar', it could convert ostree
and ota to ostree.tar, ota.tar, hence we can drop the code generating
ostree.tar.bz2 in image_types_ostree.bbclass, and also drop the
do_image_ota-tar task. To let this conversion type take effect, the
otasetup task needs to be changed to ota.
- Introduce BUILD_OSTREE_TARBALL variable, when being set to 1, a
ostree.tar.bz2 tarball would be built, BUILD_OSTREE_TARBALL defaults
to be 1, to be consistent with original behavior.
- Replace 'ota-tar ota-tar.xz' with ota.tar.xz in IMAGE_FSTYPES.
- Add a sanity check bbclass sota_sanity.bbclass, to ensure ostree or
ota is not in OVERRIDES, this is to prevent potential naming
pollution with other meta layers, and also check the required
variables are not empty. This sota_sanity.bbclass is a common class
that could be extended easily in furture, and one of its most
advantages is that all the check are done in bb.event.SanityCheck
event handler, so the end users could get the error message at very
beginning of the recipe parsing time.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
| |
There are quite a few 'export' syntax, they are either not necessary or
being redundant. Actually only the variables being referred in ostree
or aktualizr need to be exported, we can move them into sota.bbclass so
they can be exported once only for all other classes referring to them.
And drop all other unnecessary exports.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
|
|
|
|
|
|
|
| |
When calling bbfatal, it reports error message and exit 1, it should be
used to replace of 'bberror && exit 1' to avoid being redundant.
Also fixed some incorrect bberror usages and typos.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Do not write directly to the IMAGE_DEPLOY_DIR but to the new
deploy directory IMGDEPLOYDIR.
Also change the image ending to match the image type name (from
otaimg to ota-ext4). This allows to use the automatic symlinking
and output artefact management too.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
|
|
|
|
|
|
| |
Do not write directly to the IMAGE_DEPLOY_DIR but to the new
deploy directory IMGDEPLOYDIR. This allows to use the automatic
symlinking too.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
|
|
|
|
|
|
| |
Almost all code in create_ota is either tar or ext4 specific. Move
the code directly into the respective IMAGE_CMD_ functions. This
gets rid of unnecessary work for the tar image and simplifies code.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
|
|
|
|
|
|
| |
OpenEmbedded makes sure that IMAGE_CMD_type gets only called if the
type is in IMAGE_FSTYPE. There is no need to explicitly check for it.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Make sure to use the custom target version when creating
installed_versions if defined by the user.
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
|
|
|
|
|
|
|
| |
/boot/grub2/grub.cfg should reflect the grub.cfg used by the boot process
instead of being an empty file.
Signed-off-by: Ricardo Salveti <ricardo@opensourcefoundries.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
RAMDISK_EXT and IMAGE_FSTYPES of initramfs-ostree-image should not be
defined separately, because they are representing the same fstype of
a same initramfs image, or else, they turn out to be inconsistent if
the users change one of them.
So we use INITRAMFS_FSTYPES already defined in bitbake.conf, to be able
to set fstype for initramfs. And it should default to ext4.gz.u-boot or
ext4.gz depending on what OSTREE_BOOTLOADER is being set.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
|
|
|
|
|
| |
As a image_types_* bbclass, it does not have to inherit image class, it
is sort of redundant code.
Signed-off-by: Ming Liu <liu.ming50@gmail.com>
|
|
|
|
| |
We should also do this in the recipes
|
|
|
| |
calculate_size had a typo that made one of the cases fail. This patch fixes it.
|
|\ |
|
| | |
|
|\|
| |
| |
| | |
Bring over fixes from the last couple months from pyro in rocko.
|
| | |
|
|/ |
|
|
|
|
| |
Fixes SPEC-761 in AGL
|
| |
|
|\
| |
| | |
Remove unneeded image types
|
| | |
|
|/
|
|
|
|
|
|
|
| |
Aktualizr currently supports OSTree updates in non-autoprovisioned mode. Add a
systemd service to run it in that mode. It uses the same location for the
config file as rvi-sota-client (/sysroot/boot/sota.toml)
Also, the aktualizr recipe is reformatted according to
meta-openembedded/contrib/oe-stylize.py (which follows the OE styleguide)
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
by live image recipe
Bug-AGL: SPEC-296
Change-Id: Idbb00f33fd04b2a2d9fa8c615347f9b85d917d4a
Signed-off-by: Anton Gerasimov <anton@advancedtelematic.com>
|
|
|
|
|
|
|
|
|
| |
bootable as an OSTree deployment
Bug-AGL: SPEC-253
Change-Id: If636a282d51a64c73c46ce70a361518c1f70cdd6
Signed-off-by: Anton Gerasimov <anton@advancedtelematic.com>
|
|
|
|
|
|
|
| |
Bug-AGL: SPEC-249
Change-Id: Ib5d725f203c0b0545b7c6b3196afb149ac8015c2
Signed-off-by: Anton Gerasimov <anton@advancedtelematic.com>
|
|
|
|
|
|
|
|
|
| |
build with otaimg
Bug-AGL: SPEC-236
Change-Id: I60f5b535467819cd03a591a12b725f2d7fc2cd31
Signed-off-by: Anton Gerasimov <anton@advancedtelematic.com>
|
|
|
|
|
|
|
|
|
| |
otaimg is now a live image.
Bug-AGL: SPEC-236
Change-Id: I5a56ffbdb098c1b4eb33fceeae32e28611b83fb7
Signed-off-by: Anton Gerasimov <anton@advancedtelematic.com>
|
|
u-boot that can be used as BIOS, machine that uses both and fork of poky
runqemu supporting the new live image.
Bug-AGL: SPEC-236
Change-Id: Id99d122c05a00eb94902e8f6907455a1e681f2a3
Signed-off-by: Anton Gerasimov <anton@advancedtelematic.com>
|