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

Miniconda breaks for old versions (or an old version?) of tail #272

Closed
willirath opened this issue Aug 16, 2019 · 5 comments · Fixed by #279
Closed

Miniconda breaks for old versions (or an old version?) of tail #272

willirath opened this issue Aug 16, 2019 · 5 comments · Fixed by #279
Labels
locked [bot] locked due to inactivity type::bug describes erroneous operation, use severity::* to classify the type

Comments

@willirath
Copy link

Based on https://repo.continuum.io/miniconda/Miniconda3-latest-Linux-x86_64.sh at v4.7.10.

On an old Linux that has tail from GNU coreutils 8.12 / April 2015.

The file contains

[...]
printf "Unpacking payload ...\n"
if ! tail -c +000000000000018891 "$THIS_PATH" | tail -c +9231072 | tail -c +2 | "$CONDA_EXEC" constructor --extract-tar --prefix "$PREFIX"; then
    printf "ERROR: could not extract tar starting at offset 000000000000018891+9231072+2\\n" >&2
    exit 1
fi
[...]

Here, the tails later in the pipe are supposed to read from stdin but have no explicit -. For more recent GNU coreutils, tail -c seems to default to stdin:

$ man -P cat tail | tail -n1
GNU coreutils 8.25                         February 2017                                    TAIL(1)
$ seq 1 9 | tail -c 2
9

For GNU coreutils 8.12, this is not true:

$ man -P cat 1 tail | tail -n 1
GNU coreutils 8.12                April 2015                           TAIL(1)
$ seq 1 9 | tail -c 2
tail: cannot open `2' for reading: No such file or directory
@willirath
Copy link
Author

cc @kgetzlaff

@jjhelmus
Copy link
Contributor

This looks like a bug in constructor, the software which creates the installer. I'm moving this issue to that project.

@jjhelmus jjhelmus transferred this issue from conda/conda Aug 21, 2019
@nehaljwani
Copy link
Collaborator

@willirath Which Linux distro are you using?

@willirath
Copy link
Author

I'm not sure. This is on an HPC frontend that runs some stable Redhat. I can try and find out more tomorrow.

@willirath
Copy link
Author

It's a SUSE Linux Enterprise Server 11 SP3.

@kenodegard kenodegard added type::bug describes erroneous operation, use severity::* to classify the type and removed type-bug labels Jan 25, 2022
@github-actions github-actions bot added the locked [bot] locked due to inactivity label Jan 26, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity type::bug describes erroneous operation, use severity::* to classify the type
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants