Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix tar transfer: use GNU tar format instead of UStar for copy operations #82

Merged
merged 2 commits into from
Oct 27, 2021

Conversation

TheLortex
Copy link
Contributor

Currently it's not possible to use the copy operation when src contains a file whose name is more than 100 characters.
It's because the UStar format is used. Because of that, the following exception is raised: Failure "file_name can't be split"

If we use the GNU tar format then the limit is lifted.

@TheLortex
Copy link
Contributor Author

TheLortex commented Oct 20, 2021

(rebased on top of #80)

When a file name in the source is too long (>100 chars)
This enables copying from sources containing long file names
(more than 100 characters)
@MisterDA
Copy link
Contributor

Posix seems to be a better choice anyway, from POSIX.1-2001. It will become the default in GNU tar.
https://www.gnu.org/software/tar/manual/tar.html#Formats

@dra27
Copy link
Contributor

dra27 commented Nov 12, 2021

IIRC the Posix support isn't implemented in ocaml-tar, though?

@MisterDA
Copy link
Contributor

MisterDA commented Nov 12, 2021

It has the header definition but no support for the format? 😮
I'll think about it later, if needed.

tmcgilchrist added a commit to tmcgilchrist/opam-repository that referenced this pull request Jun 17, 2022
CHANGES:

- Use GNU tar format instead of UStar for `copy` operations (@TheLortex ocurrent/obuilder#82, reviewed @dra27).
  This enables copying from sources containing long file names (>100 characters).

- Add support for secrets (@TheLortex ocurrent/obuilder#63, reviewed by @talex5).
  The obuilder spec's `run` command supports a new `secrets` fields, which allows to temporarily
  mount secret files in an user-specified location. The sandbox build context has an additional
  `secrets` parameter to provide values for the requested keys.

- Limit permissions on temporary directories (@talex5 ocurrent/obuilder#67)

- Check Linux kernel version support for btrfs (@kit-ty-kate ocurrent/obuilder#68)

- Generalise obuilder sandbox, removing runc/linux specifc pieces and
  making the S.SANDBOX interface more general
  (@patricoferris ocurrent/obuilder#58, reviewed by @talex5, @avsm, @MisterDA)

- Convert --fast-sync back to a flag (@talex5 ocurrent/obuilder#72)

- Support Fmt.cli and Logs.cli flags. (@MisterDA ocurrent/obuilder#74, reviewed by @talex5)
  For Fmt the new options are --color=always|never|auto
  For Log the new options are:
    -v, --verbose Increase verbosity
    --verbosity=LEVEL (absent=warning)
        Be more or less verbose. LEVEL must be one of quiet, error,
        warning, info or debug. Takes over -v.

- Minor cleanup changes (@talex5 ocurrent/obuilder#76)

- Fix deprecations in Fmt 0.8.10 (@tmcgilchrist ocurrent/obuilder#80)

- Remove travis-ci and replace with Github Actions (@MisterDA ocurrent/obuilder#84)

- Add RSync store backend for obuilder to support macOS builders (@patricoferris ocurrent/obuilder#88, reviewed @talex5)

- Fixes for ZFS tests in CI (@patricoferris ocurrent/obuilder#91)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants