I was asked about the createrepo_c patch in private. Replying here for closure.

I had reported the issue upstream at 
https://github.com/rpm-software-management/createrepo_c/issues/266 and it has 
been fixed. Poky kirkstone and mainline should have the fix.

Kind Regards,
Devendra

> On 28 Apr 2021, at 20:02, Devendra Tewari <[email protected]> wrote:
> 
> Understood - carrying patches is a burden for sure. I’ll maintain patches for 
> my own narrow use cases at my end, and perhaps submit them upstream.
> 
> Thanks,
> Devendra
> 
>> On 28 Apr 2021, at 18:42, Richard Purdie 
>> <[email protected]> wrote:
>> 
>> On Wed, 2021-04-28 at 07:00 -0300, Devendra Tewari wrote:
>>> The gist of it is that Docker uses the overlay2 storage driver by default, 
>>> previously it used aufs. Both drivers have the same limitation in rename, 
>>> where file rename across layers is handled by moving, but directory rename
>>> across layers results in error EXDEV. It is up to user space to handle the 
>>> error.
>> 
>> I'm still struggling to see how you're going to patch all the various pieces 
>> of
>> software out there used during a build to handle EXDEV correctly.
>> 
>> We have handled some cases of this for a long time where we're moving files
>> over to different parts of a filesystem, e.g. /tmp/ to WORKDIR or vice versa.
>> 
>> This new docker case triggers for renames even within a directory, e.g. 
>> /some/path/a -> /some/path/b which is not something that would often trigger
>> this.
>> 
>> I need to say clearly now that we are not carrying/taking patches to patch
>> every bit of other software to try and avoid this.
>> 
>> Cheers,
>> 
>> Richard
>> 
>> 
>> 
> 
> 
> 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#169671): 
https://lists.openembedded.org/g/openembedded-core/message/169671
Mute This Topic: https://lists.openembedded.org/mt/81698791/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to