I just did that. Did the checksum change again?
Are they constantly re-tagging this release or what?
| Git Clone URL: | https://aur.archlinux.org/python-conda.git (read-only, click to copy) |
|---|---|
| Package Base: | python-conda |
| Description: | OS-agnostic, system-level binary package manager and ecosystem https://conda.io |
| Upstream URL: | https://github.com/conda/conda |
| Licenses: | BSD-3-Clause |
| Conflicts: | python-conda-git |
| Provides: | python-conda-env |
| Submitter: | cyrevolt |
| Maintainer: | flying-sheep |
| Last Packager: | flying-sheep |
| Votes: | 36 |
| Popularity: | 0.94 |
| First Submitted: | 2016-04-08 07:41 (UTC) |
| Last Updated: | 2026-02-07 17:14 (UTC) |
« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 12 Next › Last »
I just did that. Did the checksum change again?
Are they constantly re-tagging this release or what?
Well, that kinda foils the entire purpose of the checksum ;) @flyingsheep, could you please update the PKGBUILD with the correct checksum? Thanks!
To resolve the issue:
Pull the package contents:
yay -G python-conda
cd python-conda
Regenerate the Correct Checksum:
makepkg -g >> PKGBUILD
This appends the new checksum to the PKGBUILD file, replacing the incorrect one.
Rebuild and Reinstall:
makepkg -si
Have a nice day, I failed to install python-conda using yay, can you help me? the error is listed as:
==> 错误: 一个或多个文件没有通过有效性检查! -> 下载源文件时出错: /home/lizhao/.cache/yay/python-conda context: exit status 1
:: (1/1) 正在解析 SRCINFO: python-conda ==> 正在创建软件包:python-conda 24.9.2-1 (2024年10月31日 星期四 08时47分11秒) ==> 正在检查运行时依赖关系... ==> 正在检查编译时依赖关系 ==> 获取源代码... -> 找到 conda-24.9.2.tar.gz ==> 正在验证 source 文件,使用sha512sums... conda-24.9.2.tar.gz ... 失败 ==> 错误: 一个或多个文件没有通过有效性检查! -> 生成时出错: python-conda-exit status 1 -> 无法安装以下软件包, 需要手动介入处理: python-conda - exit status 1
OK, here we go, it all actually works, without any workarounds relying on the dog-slow classic solver. Have fun everyone.
As said, in the future, my python-libmamba package will probably be replaced by micromamba at some point
this package is currently waiting for the scikit-build maintainers’ help in building python-libmamba/micromamba.
in the future python-libmamba will probably be replaced with micromamba since with a few tweaks, it can provide everything provide everything python-conda-libmamba-solver needs.
Then the dependency chain will be python-conda->python-conda-libmamba-solver->micromamba
Any attempt to install this package has failed miserably for me, because of borked python-libmamba dependency. Any attempt to patch python-libmamba has also failed miserably for me.
Here's how I managed to install it: First, clone this repo Second, remove python-libmamba as a dependency in the PKGBUILD file.
Once conda is installed, run this command in conda:
conda config --set solver classic
This will tell conda to use the classic solver instead of libmamba. You will get an annoying message about missing libmamba every time you run the conda command. Also, you won't be able to use libmamba unless you manually move your base environment and manually install it:
conda install -n base conda-libmamba-solver
awesome, your new version works perfectly!
You forgot to push your .SRCINFO file though.
Also FYI: conda changed their build setup away from setuptools:
makedepends=(
'python-build'
'python-installer'
'python-hatchling'
'python-hatch-vcs'
'python-wheel'
)
build() {
cd $srcdir/${_name}-$pkgver
python -m build --no-isolation
}
but since you didn’t use `--no-isolation`, it continued working
For python-conda here, it just crashed when I tried to run conda create with an error message saying that that package can’t be found.
For binary packages like python-libmamba I build them using something like
extra-x86_64-build -- -I ~/.cache/paru/clone/reproc/reproc-14.2.5-2-x86_64.pkg.tar.zst
Which will then tell you which dependencies aren’t satisfied. I added them one by one with the most high level ones first, because a lot of dependencies (like zstd) are implicitly satisfied by other, more high-level dependencies also depending on them.
Uploaded a new version with a patched conda binary and python-archspec as a dep.
Patch:
# BEGIN Patch conda binary
sed -i 's/ import/.main import/' conda/shell/bin/conda
sed -i 's/path.main/path/' conda/shell/bin/conda
sed -i 's/from conda.deprecations/# from conda.deprecations/' conda/shell/bin/conda
sed -i 's/deprecated.module/# deprecated.module/' conda/shell/bin/conda
sed -i 's/"24/# "24/g' conda/shell/bin/conda
sed -i 's/addendum/# addendum/g' conda/shell/bin/conda
sed -i 's/ )/# )/' conda/shell/bin/conda
# END
# BEGIN Install patched conda binary
rm -f $pkgdir/usr/bin/conda
install -Dm 755 conda/shell/bin/conda $pkgdir/usr/bin/conda
# END
Pinned Comments
flying-sheep commented on 2025-01-06 13:01 (UTC)
You forgot to rebuild all your AUR python packages after that update. That's a necessary step and has nothing to do with our conda package.
See e.g. https://www.reddit.com/r/archlinux/comments/1hk2wii/comment/m3g11xz/
Please ask in the Arch BBS or on e.g. Reddit if you have further questions!