mamba-org / micromamba-releases Goto Github PK

xref mamba-org/mamba#2536

Who can do this?

In the current version of install.ps1 (946ea16), although the installation script asks the user if they want to initialize using a custom prefix, this variable is not used during the actual initialization process. This can lead to results that are inconsistent with the user's expectations after installation.

See https://github.com/mamba-org/micromamba-releases/blame/946ea168f610f3d8f7cdb25c12561ba286a59d75/install.ps1#L41 and below.

As of: https://github.com/mamba-org/micromamba-releases/releases/tag/1.5.3-0

Windows artifacts:

• micromamba-win-64 (missing .exe extension)
• micromamba-win-64.sha256
• micromamba-win-64.tar.bz2
• micromamba-win-64.tar.bz2.sha256

Right now https://micro.mamba.pm/install.sh is an old version of https://micromamba.pfx.dev/install.sh. Can we redirect to the new place? @wolfv

#17 (comment)

There was a problem with the Test micro.mamba.pm workflow, please investigate.

There was a problem with the Test micro.mamba.pm workflow, please investigate.

Here is my environment.yml file:

name:
channels:
  - conda-forge
  - pytorch
  - nvidia
dependencies:
  - python >= 3.8, <3.9
  - pytorch
  - pytorch-cuda=11.8
  - torchvision
  - pip
  - pip:
      - ultralytics
      - pillow
      - numpy
      - pandas
      - git+https://github.com/openai/CLIP.git

When running the following command:

micromamba env create -f environment.yml -p ./.conda

it fails with

Installing pip packages: ultralytics, pillow, numpy, pandas, git+https://github.com/openai/CLIP.git
critical libmamba Cannot activate, prefix does not exist at: '{ SNIP }\micromambaenv\envs.conda'
critical libmamba pip failed to install packages

It seems to be trying to find an environment called .conda instead of using the environment I have locally in my project.

I'm using micromamba version 1.5.6 on windows.

There was a problem with the Test micro.mamba.pm workflow, please investigate.

We recently started having build failures after 1.5.1-1 was released because we use https://github.com/mamba-org/setup-micromamba with version set to the default latest and linux-aarch64 runners. The errors are 404s like:

Install micromamba
  Error: Error installing micromamba: Unexpected HTTP response: 404
Error: Unexpected HTTP response: 404

They seem to be caused by there being no linux-aarch64 files in the 1.5.1-1 assets list. Could you please add the linux-aarch64 files to the release?

install.sh prints [Y/n], which mean Y is default value, but it uses CONDA_FORGE_YES="${CONDA_FORGE_YES:-no}"

From readme:

On Windows, the executable micromamba.exe is installed into $Env:LocalAppData\micromamba\micromamba.exe.

Shouldn't it honour MAMBA_ROOT_PREFIX env variable if it's defined?

critical libmamba The package "/tmp/linux-64/xxxx.tar.bz3" is not available for the specified platform

Failing back to 1.4.9 it all works, but some change at 1.5.0 caused this.

I install a package from conda-forge and then install locally built plugins for that package using micromamba. But cannot install the local package since the latest release

There was a problem with the Test micro.mamba.pm workflow, please investigate.

The workflow file is invalid as described in #12 (comment)

@AntoinePrv

There was a problem with the Test micro.mamba.pm workflow, please investigate.

There was a problem with the Test micro.mamba.pm workflow, please investigate.

There was a problem with the Test micro.mamba.pm workflow, please investigate.

There was a problem with the Test micro.mamba.pm workflow, please investigate.

Invoke-Expression ((Invoke-WebRequest -Uri https://micro.mamba.pm/install.ps1).Content) can be simplified to
irm https://micro.mamba.pm/install.ps1 | iex, where irm -> Invoke-RestMethod and iex -> Invoke-Expression are built-in aliases.

The provided .sha256 files are always hashes of micromamba binaries and never the archives. In other words, micromamba-linux-64.tar.bz2.sha256 is not the sha256sum of micromamba-linux-64.tar.bz2. Relatedly, micromamba-linux-64.sha256 and micromamba-linux-64.tar.bz2.sha256 are identical. Assuming this isn't an artifact of how anaconda.org operates, I think these should be the hashes of the archive files instead of the binaries they contain.

Troubleshooting docs

• My problem is not solved in the Troubleshooting docs

How did you install Mamba?

Micromamba

Search tried in issue tracker

ps unknown option

Latest version of Mamba

• My problem is not solved with the latest version

Tried in Conda?

Not applicable

Describe your issue

Error using recommended micromamba install script on Windows Git Bash:

"${SHELL}" <(curl -L micro.mamba.pm/install.sh)
ps: unknown option -- o

Indeed, the ps installed in my Git Bash does not have -o:

The installation continues and appears to work though.

$ ps -h
Usage: ps [-aefls] [-u UID] [-p PID]

Report process status

 -a, --all       show processes of all users
 -e, --everyone  show processes of all users
 -f, --full      show process uids, ppids
 -h, --help      output usage information and exit
 -l, --long      show process uids, ppids, pgids, winpids
 -p, --process   show information for specified PID
 -s, --summary   show process summary
 -u, --user      list processes owned by UID
 -V, --version   output version information and exit
 -W, --windows   show windows as well as cygwin processes

With no options, ps outputs the long format by default

mamba info / micromamba info

No response

Logs

No response

environment.yml

No response

~/.condarc

No response