This release fixes a bug for compatibility with the swupd-client v3.8.3
release; the /usr/share/clear/update-ca directory must now be manually
created in the os-core-update bundle before installing the certificate.
Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
Starting with swupd-client v3.8.3, the update-ca directory is no longer
created for the build, so the cert copy is failing. Fix the issue by
creating the directory before the copy operation.
Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
This release enables the build-all option which will generate all content
for a mix; this means: chroots, all update content (manifests, packs, etc),
and auto-increments the mixversion number so it can be run consecutively
without any user intervention between mixes.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
The tools have been converted from many bash scripts into a single binary,
written in Go. This creates a codebase that is much easier to edit and
maintain, and a single tool that provides all the functionality needed. The
interface is more intuitive and easy to use as it provides options and menus
for each subcommand.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
Because Clear version numbers use numeric digits only, it's possible for
the tag names to conflict with the prefix of a git object hash in the
repo. To remove the possibility of conflict, use the refs/tags/ prefix
when querying the tag names.
Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
With the current workflow, the "mix-bundles" repo is used for
mix-specific bundle changes, and the "clr-bundles" repo is treated as
read-only.
So in clr-bundles, the CLRVER_mix branches should always point to the
commit tagged with CLRVER. To make this handling more robust, first
verify that CLRVER exists and is a tag. Then create the CLRVER_mix
branch based on CLRVER, or if the branch already exists, reset it
appropriately.
Since this is the best place to detect invalid CLEAR_VERSION numbers
passed in the builder.conf, I've added that error handling too.
Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
This release makes build-chroots.sh and check_dep() fail on error to properly
quit the build process when an error occurs. The chroot building script
would get passed the chroot install, and then continue to clean up which
would always return success.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
Because 'set -e' is enabled for init-mix.sh, the exit status of 'type'
is not checked, so an error raised by 'type' would exit immediately, not
running the $? conditional logic.
To fix, disable 'set -e' for the dependency check function.
Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
The rest of the mixer-tools scripts (excluding the pack makers) already
set this shell option, so add it to the build-chroots script too.
Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
This release forces a check for the version numbers existence, which are
absolutely needed for the scripts to function properly.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
This release fixes a path error outputting the Manifest.MoM.sig to the wrong
location when using custom STATE_DIR.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
This release fixes a serious path error when mixes are not created in the
current mixer workspace as expected by default. The path for the output
(STATE_DIR) needs to be used to make this work anywhere.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
This release is largely a rewrite of the mixer scripts to reduce complexity
in using them, add a more robust helper library to minimize the code, and
enable certificate generation for Manifest.MoM signing so mixer users can
have signed content.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
When REPO_DIR is set, the actual binary might not exist at that location
(e.g. swupd-server might not have been compiled).
Add an additional dependency check for the REPO_DIR location.
Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
Since create-update supports a custom location for the swupd-server
binaries, if that option is passed, it should be propogated to the
pack-maker, which also calls swupd_make_pack.
Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
The files now call functions defined in the helper script to stay more minimal
and be easier to read. One very significant change to note is that all state
variables and information needed for mixing will now be stored and read in
the builder.conf. No longer will there be various hidden state files, with
the exception of the yum-mix.conf which is autogenerated by the template
still. This change simplifies the scripts calling convention and creates
one centralized point to specify the configuration(s) needed.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
This will do a lot of the ugly work that does not need to be taking up space
in the main scripts, and should be abstracted out so they are easier to read.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
This release adds support for specifying a certificate to insert into the
mix that the client would use to perform signature verification on a signed
Manifest.MoM.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
This release includes a fix to the hardlink call, fixes to the help menus,
script functionality to build a fully bootable image off the intial mix,
renaming the latest.version file to more appropriately match its use, and
adds a rewrite of pack-macker.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
The first aim of this patch is to centralize pack creation for SWUPD,
adding the ability to create zero packs in addition to delta packs.
Secondly, to make delta pack creation more flexible, instead of
considering the last N times a bundle changed, require the user to
specify the "from" version delta packs should be based on. More than one
--from option can be passed if several sets of delta packs need to be
built.
To facilitate these different modes of operation, I added option
parsing, also with --help output and some examples documented in the
script header.
Additionally, GNU Parallel is used to parallelize pack creation, instead
of shell job control facilities.
Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
The content should only be built fully for a full Clear mix, as the user
may want to add and modify bundle definitions further for the first mix.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
Because the intent is to create hardlinks where possible within the
image/MIXVER directory tree, only the toplevel directory name needs to
be given. This avoids arbitrarily long command lines when the glob is
expanded by the shell.
Signed-off-by: Patrick McCarty <patrick.mccarty@intel.com>
This release adds the pack-maker and super-pack-maker scripts to mixer tools,
adds several options to the build scripts, script cleanup, and sanitizes an
important swupdrepo variable.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
For someone simply trying to get a full build of Clear with everything included,
this option makes doing that much easier. Simply passing -a will tell init-mix
to create the first mix with all bundles, instead of creating a minimal build.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
There may be cases where chroots are needed for the next build, such as when one
may want to use the same (or almost the same) content, and copying the previous
build contents would be much more efficient then re-creating it.
Signed-off-by: Tudor Marcu <tudor.marcu@intel.com>
- superpack-maker.sh
Create superpacks for each bundle in an update version. The
superpack replaces oldest pack in that directory (excluding
zero packs) and is a superset of updates needed for all newer
packs. Leaves a defined number of newest delta packs unchanged.
The remaining delta packs are symlinked to the superpack.
- create-update.sh
Define variables for superpack-maker.sh, call pack-maker.sh, and
call superpack-maker.sh
- Makefile.am
Install superpack-maker.sh
Signed-off-by: Matthew Johnson <matthew.johnson@intel.com>
Patrick McCarty