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

Suspicious file: miniforge3/=2.17 / quoting issue #865

Closed
2 tasks done
sk1p opened this issue Sep 21, 2024 · 1 comment · Fixed by #887
Closed
2 tasks done

Suspicious file: miniforge3/=2.17 / quoting issue #865

sk1p opened this issue Sep 21, 2024 · 1 comment · Fixed by #887
Labels
type::bug describes erroneous operation, use severity::* to classify the type

Comments

@sk1p
Copy link

sk1p commented Sep 21, 2024

Checklist

  • I added a descriptive title
  • I searched open reports and couldn't find a duplicate

What happened?

I hope this is the correct repo to report. After installing Miniforge3-24.7.1-0-Linux-x86_64.sh, there's a suspicious file called =2.17 in the miniforge3 directory. It contains the text:

Checking virtual specs compatibility: __glibc

I think this comes from broken quoting here:

echo 'Checking virtual specs compatibility: __VIRTUAL_SPECS__'

Where __VIRTUAL_SPECS__ is '__glibc>=2.17'. So the rendered script looks like this:

[...]
if [ "'__glibc >=2.17'" != "" ]; then
    echo 'Checking virtual specs compatibility: '__glibc >=2.17''
    CONDA_QUIET="$BATCH" \
    CONDA_SOLVER="classic" \
    CONDA_PKGS_DIRS="$(mktemp -d)" \
    "$CONDA_EXEC" create --dry-run --prefix "$PREFIX/envs/_virtual_specs_checks" --offline '__glibc >=2.17'
fi
[...]

So instead of printing the message to stdout, it gets redirected to a file called =2.17.

Additional Context

No response

@sk1p sk1p added the type::bug describes erroneous operation, use severity::* to classify the type label Sep 21, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Sep 21, 2024
@jaimergp
Copy link
Contributor

jaimergp commented Nov 8, 2024

Thanks, adding a fix in #887

@github-project-automation github-project-automation bot moved this from 🆕 New to 🏁 Done in 🧭 Planning Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::bug describes erroneous operation, use severity::* to classify the type
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants