Enrico
October 16, 2025, 12:18am
1
Hello everyone,
I am having a critical and recurring problem trying to install either the full Anaconda or the smaller Miniconda distribution on my Ubuntu system. The installation consistently fails during the “Unpacking payload” stage.
The failure is always preceded by a warning about a checksum mismatch for an internal archive:
Installer Attempted
Version
Internal Warning
Final Crash
Anaconda 2025.06-0/1WARNING: md5sum mismatch of tar archiveLookupError: didn't find info-python-3.13.5... component
Miniconda py313_25.7.0-2WARNING: md5sum mismatch of tar archiveBrokenProcessPool: A process in the process pool was terminated abruptly
I have taken the extraordinary step of checking the integrity of the downloaded file against the published checksums on multiple machines (Ubuntu 25.10 and 24.04 LTS), and here is what I found:
External Integrity Passes: The SHA256 checksum of the entire downloaded installer file (.sh) matches the expected value published by Anaconda perfectly. This confirms my downloaded file is not corrupted by my network.
Internal Integrity Fails: The installation breaks because the MD5 sum of the internal package archive, calculated during execution, does not match the MD5 value that is hardcoded inside the installer script itself.
This strongly suggests the issue is a bug within the installer script itself for the 2025.06 release, where an incorrect MD5 hash was accidentally hardcoded for the core Python 3.13.5 package.
I’ve cleared everything multiple times to ensure a clean install environment:
Redownloaded the .sh file multiple times.
Removed all previous directories: ~/anaconda3, ~/miniconda3.
Removed all Conda configuration: ~/.condarc, ~/.conda, ~/.continuum.
Has anyone else experienced this specific internal MD5 failure with the 2025.06 installers?
Since I am confident the file I downloaded is correct (based on the external SHA256 match), is there a known flag I can pass to the bash command to force the installation to ignore the internal MD5 mismatch and just proceed with the extraction?
Any help or confirmation of this potential installer bug would be greatly appreciated!
P.S. This post was produced with the assistance of the Gemini AI model for clarity and comprehensive detailing of technical steps. I’m stating this for clarity and transparency.
Enrico
October 16, 2025, 8:30am
2
This was apparently it’s an issue with Ubuntu 25.10 core-uutils (which include the new Rust components).
Workaround
Reverting to the older core-utils solved the issue for me. In Ubuntu terminal write:
sudo apt install coreutils-from-gnu coreutils-from-uutils- --allow-remove-essential
Then 2025.06 installation goes forward with no additional errors.
2 Likes
Esteve
October 19, 2025, 8:54am
3
You saved my day, I confirm the issue and the workaround worked for me.
I have experienced exactly the same issue with https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh for the past week and Enrico’s solution solved it today. You saved my second day hitting my head against this wall ^^’
Thanks Enrico you saved my day
Enrico
October 23, 2025, 9:47am
6
Here to report the issues raised on conda and anaconda github pages:
aperto 02:12AM - 17 Oct 25 UTC
type::support
source::community
### Checklist
- [x] I added a descriptive title
- [x] I searched open reports a… nd couldn't find a duplicate
### What happened?
```
Traceback (most recent call last):
File "concurrent/futures/process.py", line 264, in _process_worker
File "conda_package_handling/api.py", line 77, in extract
File "conda_package_handling/conda_fmt.py", line 51, in extract
File "conda_package_handling/streaming.py", line 52, in _extract
File "conda_package_handling/streaming.py", line 32, in _stream_components
File "conda_package_streaming/package_streaming.py", line 142, in stream_conda_component
LookupError: didn't find info-python-3.13.5-h4612cfd_100_cp313 component in /home/agent/anaconda3/pkgs/python-3.13.5-h4612cfd_100_cp313.conda
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "entry_point.py", line 244, in _constructor_extract_conda_pkgs
File "concurrent/futures/_base.py", line 449, in result
File "concurrent/futures/_base.py", line 401, in __get_result
LookupError: didn't find info-python-3.13.5-h4612cfd_100_cp313 component in /home/agent/anaconda3/pkgs/python-3.13.5-h4612cfd_100_cp313.conda
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "entry_point.py", line 691, in <module>
File "entry_point.py", line 681, in main
File "entry_point.py", line 582, in _constructor_subcommand
File "entry_point.py", line 246, in _constructor_extract_conda_pkgs
RuntimeError: Failed to extract /home/agent/anaconda3/pkgs/python-3.13.5-h4612cfd_100_cp313.conda: didn't find info-python-3.13.5-h4612cfd_100_cp313 component in /home/agent/anaconda3/pkgs/python-3.13.5-h4612cfd_100_cp313.conda
```
### Conda Info
```shell
```
### Conda Config
```shell
```
### Conda list
```shell
```
### Additional Context
_No response_
aperto 10:14AM - 14 Oct 25 UTC
type-bug
### Checklist
- [x] I added a descriptive title.
- [x] I searched through [exis… ting issues](https://github.com/ContinuumIO/anaconda-issues/issues) and couldn't find a solution or duplicate issue.
- [x] I searched on the web (e.g. Google) and didn't find any helpful information.
- [x] I searched the [Anaconda documentation](https://docs.anaconda.com/) and didn't find any helpful information.
### Impacted product
- [ ] A conda package (built by Anaconda)
- [ ] Anaconda Distribution (formerly Anaconda Individual Edition)
- [ ] Miniconda
- [ ] Anaconda.org
### What happened?
PREFIX=/home/n00b/miniconda3
WARNING: md5sum mismatch of tar archive
expected: cb28419f6cd1ada49cb72c393d6154b7
got: 9876f2812348c87cd397c3ee6c93da4b -
Unpacking bootstrapper...
Unpacking payload...
concurrent.futures.process._RemoteTraceback:
'''
Traceback (most recent call last):
File "concurrent/futures/process.py", line 423, in wait_result_broken_or_wakeup
File "multiprocessing/connection.py", line 251, in recv
TypeError: InvalidArchiveError.__init__() missing 1 required positional argument: 'msg'
'''
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "entry_point.py", line 234, in _constructor_extract_conda_pkgs
File "concurrent/futures/_base.py", line 449, in result
File "concurrent/futures/_base.py", line 401, in __get_result
concurrent.futures.process.BrokenProcessPool: A process in the process pool was terminated abruptly while the future was running or pending.
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "entry_point.py", line 684, in <module>
File "entry_point.py", line 673, in main
File "entry_point.py", line 567, in _constructor_subcommand
File "entry_point.py", line 236, in _constructor_extract_conda_pkgs
RuntimeError: Failed to extract /home/n00b/miniconda3/pkgs/python-3.13.5-h4612cfd_100_cp313.conda: A process in the process pool was terminated abruptly while the future was running or pending.
[PYI-155344:ERROR] Failed to execute script 'entry_point' due to unhandled exception!
### Expected behavior or outcome
There might be an issue with the Conda version or its handling of the package
### Conda info
```shell
```
### Conda config
```shell
```
### Conda list
```shell
```
### Additional information
_No response_
No definitive solution yet
Enrico
October 23, 2025, 11:49am
7
I also created an issue on coreuutils github:
aperto 11:46AM - 23 Oct 25 UTC
## Description
The `md5sum` utility in uutils/coreutils version 0.2.2 produces … different checksums than GNU coreutils' `md5sum` for the same input, causing installation failures for Anaconda and Miniconda on Ubuntu 25.10.
## Environment
- **OS:** Ubuntu 25.10 (Questing Quokka)
- **Architecture:** x86_64
- **uutils coreutils version:** 0.2.2-0ubuntu2 (from rust-coreutils package)
- **GNU coreutils version (working):** 9.5-1ubuntu4
- **Package:** rust-coreutils 0.2.2-0ubuntu2
## Reproduction
1. Install Ubuntu 25.10 (which uses Rust-based coreutils by default)
2. Download Miniconda installer:
```bash
wget https://repo.anaconda.com/miniconda/Miniconda3-py313_25.7.0-2-Linux-x86_64.sh
```
3. Verify external integrity (this passes):
```bash
sha256sum Miniconda3-py313_25.7.0-2-Linux-x86_64.sh
```
4. Run installer:
```bash
bash Miniconda3-py313_25.7.0-2-Linux-x86_64.sh
```
5. Observe failure during "Unpacking payload" with:
```
WARNING: md5sum mismatch of tar archive
BrokenProcessPool: A process in the process pool was terminated abruptly
```
The same installer file works correctly after switching to GNU coreutils:
```bash
sudo apt install coreutils-from-gnu coreutils-from-uutils- --allow-remove-essential
bash Miniconda3-py313_25.7.0-2-Linux-x86_64.sh # Now succeeds
```
## Version Comparison
**uutils (problematic):**
```
$ /usr/lib/cargo/bin/coreutils/md5sum --version
/usr/lib/cargo/bin/coreutils/md5sum (uutils coreutils) 0.2.2
```
**GNU coreutils (working):**
```
$ /usr/bin/gnumd5sum --version
md5sum (GNU coreutils) 9.5
```
## Expected Behavior
`md5sum` should produce identical checksums to GNU coreutils' `md5sum` for the same input.
## Actual Behavior
The installer's internal MD5 checksum verification fails because the calculated checksum doesn't match the expected value (which is correct for GNU coreutils).
## Additional Context
- External file integrity check (SHA256) passes on multiple systems (Ubuntu 25.10 and 24.04 LTS)
- Issue occurs with both Anaconda 2025.06-0/1 and Miniconda py313_25.7.0-2
- The installers are self-extracting shell scripts that verify internal tar archive checksums during unpacking
- The issue is reproducible consistently on fresh Ubuntu 25.10 installations
- Original report: https://forum.anaconda.com/t/critical-installation-failure-persistent-internal-md5-mismatch-anaconda-miniconda-2025-06-on-ubuntu-25-10/107525
## Impact
This is a critical compatibility issue. Ubuntu 25.10 users cannot install Anaconda/Miniconda (widely-used scientific computing platforms) without manually reverting to GNU coreutils, which undermines the goal of being a drop-in replacement.
## Questions
1. Are there known differences in how uutils `md5sum` handles piped input or processes data from tar archives?
2. What diagnostic information would help narrow down the root cause?
3. Is there a way to extract a minimal test case from the installer to debug this further?
---
**Disclaimer:** This report was created with the assistance of Google Gemini 3.5 Pro and GitHub Copilot with Claude Sonnet 4.5 for clarity, comprehensive detailing of technical steps, and proper formatting according to the project's contributing guidelines. This disclaimer is included at my request for transparency reasons. Also, this issue has been created from my machine after the workaround (reverting to older coreutils) had already been applied and Anaconda successfully installed.