From: Ladislav Michl <ladis@linux-mips.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC] casync: new package
Date: Thu, 29 Aug 2019 14:35:11 +0200 [thread overview]
Message-ID: <20190829123511.GA19758@lenoch> (raw)
In-Reply-To: <20190517143210.gn54u2mvfb4vk5wy@pengutronix.de>
On Fri, May 17, 2019 at 04:32:10PM +0200, Michael Olbrich wrote:
> On Wed, May 15, 2019 at 09:00:45AM +0200, Ladislav Michl wrote:
> > Signed-off-by: Ladislav Michl <ladis@linux-mips.org>
> > ---
> > Hi there,
> >
> > this is just an attempt to find you how (if at all) are people using
> > rauc with casync support. Packages here are good enough to run
> > $ PATH=$ROOT/sysroot-host/bin:$ROOT/sysroot-host/sbin:$PATH
> > $ rauc convert --cerrt=<config>/rauc/rauc.cert.pem --key=<config>/rauc/rauc.key.pem --keyring=<prjdir>/projectroot/etc/rauc/ca.cert.pem <imgdir>/update.raucb casync-bundle.raucb
> > after rauc bundle is built. Resulting index and chunk store can
> > be then used to update target system.
> >
> > Do we want it as another image target? Anyone is using any other
> > scenario?
Gentle ping. Are there any casync users out there?
> > Also, to make host-casync built we need host-xz with f9b48616ef47
> > ("host-xz: Don't build with shared libs") reverted. That commit log
> > says:
> > We don't need shared librarys of host-xz. When they are enabled,
> > building host-gettext may fail because of mixed shared library versions.
> > Is that still an issue?
>
> Probably not. If I remember correctly, then host-gettext was built with
> system libxz (if found) at the time. If libxz was then built afterwards and
> was an older version, then executing some gettext tool would fail because
> it used the wrong libxz.
> We build host-gettext with --without-xz now, so I hope, this is no longer
> an issue.
> You can test this by installing xz devel files and then build host-gettext
> and see if it uses libxz.
For the record, this is indeed not an issue any longer, so patch enabling
shared liblzma will be part of next version patch set.
ladis
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2019-08-29 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 7:00 Ladislav Michl
2019-05-17 14:32 ` Michael Olbrich
2019-08-29 12:35 ` Ladislav Michl [this message]
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=20190829123511.GA19758@lenoch \
--to=ladis@linux-mips.org \
--cc=ptxdist@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