The 'rmdir' call should be enough, and just because there is an
empty dir in the boot part, does not mean that it exists in
rootfs/boot, so just remove this.
Changelog: Fix error when removing empty directories in rootfs/boot
Signed-off-by: Mirza Krak <mirza.krak@northern.tech>
(cherry picked from commit 17b92ddfe0)
The current checks will not work when multiple options are used. Ignore
the '-O ' and check only for the option values.
Changelog: Title
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
(cherry picked from commit 57053296b7)
This is needed for MacOS compatibility as the default chown version there does
not understand the user.group syntax.
Changelog: Title
Signed-off-by: Drew Moseley <drew.moseley@northern.tech>
(cherry picked from commit d8531dd154)
This keeps the tests looking like they did prior to the submodule refactoring on
master.
Changelog: None
Signed-off-by: Ole Petter <ole.orhagen@northern.tech>
Following recent changes in mender-qa and the GitLab master runner.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
(cherry picked from commit 84589ee74e)
This new keyword of GitLab allows for jobs in further stages start as
soon as their dependencies are done.
This should speed-up this pipeline, starting most of the acceptance
testing without finishing to the raspberrypi conversions.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
(cherry picked from commit 5fff844e23)
The latest package does not have the Debian version suffixed.
Therefore, simply remove it in the case where it is needed.
Changelog: None
Signed-off-by: Ole Petter <ole.orhagen@northern.tech>
(cherry picked from commit 70350d608c)
The 'latest' tag is always pointing to the latest released Mender-client.
Therefore it is no longer necessary to update the client version on release.
Changelog: Package latest released Mender-client by default
Signed-off-by: Ole Petter <ole.orhagen@northern.tech>
(cherry picked from commit b5caf4b07f)
It is already manual, so really no need for the 'only' tag.
Changelog: None
Signed-off-by: Ole Petter <ole.orhagen@northern.tech>
(cherry picked from commit 23d169a4b2)
As probe_initrd_in_boot_and_root indicates, this is not always required.
Adding the check for the ln not to throw an error.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
(cherry picked from commit 850e40490a)
Remove all the logic for the special handling of this submodule, and
treat it instead a regular Git submodule.
This commit updates the submodule to latest, removes the --no-pull
functionality, and removes the ignore of the submodule to make
developers aware
To ease maintenance, add also dependabot to pay attention to the future
updates of the submodule.
Changelog: None
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
(cherry picked from commit 721b9f3ce2)
Originally the intention was to fix the U-Boot integration for
Beaglebone, but this seems to have been broken for a long time, almost
a year, and no one has complained about it. The problem appears to be
connected to this commit [1], but it's not entirely clear to me what
the fix should be, and there are a lot of patches for our U-Boot fork.
However, since the U-Boot integration is supposed to be the backup
solution, rather than dig into U-Boot I decided to just fix the UEFI
path instead. This method doesn't require any patching, but there is
a problem with the specific image which is available for download at
the time of writing. So just grab the boot loader and kernel pieces
from a later, yet unbuilt, image, and it all works again.
Changelog: Title
Changelog: beaglebone: Remove U-Boot integration, which has not worked
for a long time. U-Boot will still be used for booting, but GRUB will
be used for integration with Mender, by chainloading via UEFI.
[1] e88d5dbf01
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
(cherry picked from commit ce2b1f46cf)
Sounds scary, but it happens at build time, not runtime, so it cannot
brick devices. However, it was a frustrating exercise to uncover it,
as it is not entirely deterministic. This has been there for quite a
long time and I honestly cannot tell why it happened to me now.
Perhaps the exact location of the sparse holes on the filesystem makes
a difference. Or perhaps some versions of mkfs can handle it, others
not. All I know for sure, is that with `sparse` enabled I got massive
filesystem corruption (though sane enough to be somewhat readable) on
the rootfs. Without it, it's clean.
Changelog: Title
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
(cherry picked from commit 2ce70456e6)
... not just for EFI configuration. This doesn't fix any immediate
problems, but some U-Boot configurations seem to make a reference to
this, so this is just being proactive.
Changelog: None
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
(cherry picked from commit 1862363ca4)
Because we hardcode the name in the boot loader script, you can never
upgrade to a kernel with a different version string. Fix by using a
generic name and symlinking instead.
Changelog: Title
Signed-off-by: Kristian Amlie <kristian.amlie@northern.tech>
(cherry picked from commit b258f2f901)
Changelog: Warn user when converting read-only file systems that would
result in unstable checksums, making the image incompatible with Mender
Delta updates.
Signed-off-by: Lluis Campos <lluis.campos@northern.tech>
Kristian Amlie
Lluis Campos
Mirza Krak
Kristian Amlie
Drew Moseley
oleorhagen