From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Martin Jansa <martin.jansa@gmail.com>,
Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 00/38] Morty Next pull request
Date: Fri, 06 Apr 2018 15:11:49 +0100 [thread overview]
Message-ID: <1523023909.2942.8.camel@linuxfoundation.org> (raw)
In-Reply-To: <CA+chaQf17H2+HKJ6V=+tGnL7xkH_ocPRj7j_hBWSG5e2AKV31w@mail.gmail.com>
On Fri, 2018-04-06 at 16:07 +0200, Martin Jansa wrote:
> > Is it safe to backport to morty, which doesn't have RSS?
>
> It doesn't work well for me, all the builds are now failing with:
>
> ERROR: glibc-2.24-r0 do_stash_locale_setscene: The recipe glibc is
> trying to install files into a shared area when those files already
> exist. Those files and their manifest location are:
> TMPDIR/sysroots-components/aarch64/glibc-stash-locale/SUPPORTED
> Matched in b''
> TMPDIR/sysroots-components/aarch64/glibc-stash-
> locale/lib/libnss_nisplus.so.2
> Matched in b''
> TMPDIR/sysroots-components/aarch64/glibc-stash-locale/lib/ld-
> 2.24.so
> Matched in b''
> ...
I suspect using its own sstate task is ok in morty even if it didn't
have RSS. What may have broken is the existing TMPDIR upgrade path
though :(
If the files are removed, I suspect things will then work out ok. There
were manifest handling changes in later versions which dealt with this
kind of issue better (removals before installations).
Cheers,
Richard
next prev parent reply other threads:[~2018-04-06 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 13:53 [PATCH 00/38] Morty Next pull request Armin Kuster
2018-04-05 14:04 ` akuster808
2018-04-05 21:41 ` Andre McCurdy
2018-04-06 14:07 ` Martin Jansa
2018-04-06 14:11 ` Richard Purdie [this message]
2018-04-06 14:15 ` Martin Jansa
2018-04-11 15:07 ` Martin Jansa
2018-04-11 22:37 ` Richard Purdie
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=1523023909.2942.8.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=armccurdy@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
/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