<div dir="ltr">In this build I was starting with empty TMPDIR, there shouldn't be any old files, but will retry manually in different builds.</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 6, 2018 at 4:11 PM, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, 2018-04-06 at 16:07 +0200, Martin Jansa wrote:<br>
> > Is it safe to backport to morty, which doesn't have RSS?<br>
><br>
> It doesn't work well for me, all the builds are now failing with:<br>
><br>
> ERROR: glibc-2.24-r0 do_stash_locale_setscene: The recipe glibc is<br>
> trying to install files into a shared area when those files already<br>
> exist. Those files and their manifest location are:<br>
> TMPDIR/sysroots-components/<wbr>aarch64/glibc-stash-locale/<wbr>SUPPORTED<br>
> Matched in b''<br>
> TMPDIR/sysroots-components/<wbr>aarch64/glibc-stash-<br>
> locale/lib/libnss_nisplus.so.2<br>
> Matched in b''<br>
> TMPDIR/sysroots-components/<wbr>aarch64/glibc-stash-locale/<wbr>lib/ld-<br>
> <a href="http://2.24.so" rel="noreferrer" target="_blank">2.24.so</a><br>
> Matched in b''<br>
> ...<br>
<br>
</span>I suspect using its own sstate task is ok in morty even if it didn't<br>
have RSS. What may have broken is the existing TMPDIR upgrade path<br>
though :(<br>
<br>
If the files are removed, I suspect things will then work out ok. There<br>
were manifest handling changes in later versions which dealt with this<br>
kind of issue better (removals before installations).<br>
<br>
Cheers,<br>
<br>
Richard<br>
</blockquote></div><br></div>