From: "Enrico Jörns" <ejo@pengutronix.de>
To: Martin Hollingsworth <Martin.Hollingsworth@itk-engineering.de>,
"meta-rauc@pengutronix.de" <meta-rauc@pengutronix.de>
Subject: Re: [meta-rauc] Rauc 1.4 with Yocto Zeus
Date: Wed, 18 Nov 2020 13:33:52 +0100 [thread overview]
Message-ID: <6701663d7bad1cb1cbe5611400f41fd5fe75f6a7.camel@pengutronix.de> (raw)
In-Reply-To: <a9d049bc6732462494aaf7ce007dff2a@itk-engineering.de>
Hi Martin,
Am Dienstag, den 17.11.2020, 13:26 +0000 schrieb Martin Hollingsworth:
> Hello community,
> I would like to use the latest RAUC release (v1.4) with my project, which is stuck on Yocto Zeus 3.0.x. However meta-rauc branch “zeus” integrates only Rauc v1.2.
If this project is still in development I would encourage to move at
least to the dunfell LTS as zeus is already out of support.
> Has anyone tried to update to the latest RAUC version? Any pitfalls with Zeus?
Updating to RAUC 1.4 should be possible without any issues. There were
no major changes that would affect compatibility. Simply copy the RAUC
recipes from current master as there were some recipe-internal reworks
that you should take with.
Best regards
Enrico
> Thanks and regards,
> Martin Hollingsworth
> _______________________________________________
> meta-rauc mailing list
--
Pengutronix e.K. | Enrico Jörns |
Embedded Linux Consulting & Support | https://www.pengutronix.de/ |
Steuerwalder Str. 21 | Phone: +49-5121-206917-180 |
31137 Hildesheim, Germany | Fax: +49-5121-206917-9 |
_______________________________________________
meta-rauc mailing list
next prev parent reply other threads:[~2020-11-18 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 13:26 Martin Hollingsworth
2020-11-18 12:33 ` Enrico Jörns [this message]
2020-12-02 18:10 ` Martin Hollingsworth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6701663d7bad1cb1cbe5611400f41fd5fe75f6a7.camel@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=Martin.Hollingsworth@itk-engineering.de \
--cc=meta-rauc@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox