Skip to content
This repository was archived by the owner on Feb 24, 2020. It is now read-only.

Conversation

@brianredbeard
Copy link
Contributor

Currently there is a combination where both xattr data cannot be
transferred from a squashfs image to the filesystem combined with the
fact that it's not there. This at least enables the transfer in the
future, and silences some of the warnings in the build process.

If it is decided that xattrs should not be explicitly transferred in the
future this should be changed to -no-xattrs.

Currently there is a combination where both xattr data cannot be
transferred from a squashfs image to the filesystem combined with the
fact that it's not there.  This at least enables the transfer in the
future, and silences some of the warnings in the build process.

If it is decided that xattrs should not be explicitly transferred in the
future this should be changed to -no-xattrs.
@squeed
Copy link
Contributor

squeed commented May 2, 2017

Yeah, this error message always bugged me too.

Copy link
Member

@lucab lucab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@lucab lucab added this to the v1.26.0 milestone May 8, 2017
@lucab lucab changed the title build / stage1: Transfer xattr data build/stage1: Transfer xattr data May 8, 2017
@lucab lucab changed the title build/stage1: Transfer xattr data build/stage1: transfer user xattr data May 8, 2017
@lucab lucab merged commit 18a9342 into rkt:master May 8, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants