Open curtisma opened 1 year ago
curtisma
commented
1 year ago Do any of the maintainers have a comment on the status of this package? Do you mind merging the latest version at least?
ocefpaf
commented
1 year ago I don't recall the reasons we gave up on this package but I don't think any of our tests/checks are using it. If you want to maintain it please add yourself as a maintainer and I'll be happy to merge that.
maddenp
commented
2 months ago FWIW (not much probably, as @ocefpaf's post above, with its invitation to potential maintainers, suggests that this is a human-resource issue), but the latest conda-forge conda-verify package will not install into the latest released Miniforge (output elided):
~ $ wget https://github.com/conda-forge/miniforge/releases/download/24.7.1-0/Miniforge3-Linux-aarch64.sh
~ $ bash Miniforge3-Linux-aarch64.sh -bfp conda
~ $ . conda/etc/profile.d/conda.sh
~ $ conda activate
(base) ~ $ conda install conda-verify
Channels:
- conda-forge
Platform: linux-aarch64
Collecting package metadata (repodata.json): done
Solving environment: | warning libmamba Added empty dependency for problem type SOLVER_RULE_UPDATE
failed
LibMambaUnsatisfiableError: Encountered problems while solving:
- nothing provides openssl >=1.0.2p,<1.0.3a needed by python-2.7.15-h938d71a_1006
Could not solve for environment specs
The following packages are incompatible
├─ conda-verify is installable with the potential options
│ ├─ conda-verify 3.1.1 would require
│ │ └─ python >=2.7,<2.8.0a0 with the potential options
│ │ ├─ python 2.7.15, which can be installed;
│ │ └─ python [2.7.15|3.6.7|3.7.1] would require
│ │ └─ openssl >=1.0.2p,<1.0.3a , which does not exist (perhaps a missing channel);
│ ├─ conda-verify 3.1.1 would require
│ │ └─ python >=3.10,<3.11.0a0 , which can be installed;
│ ├─ conda-verify 3.1.1 would require
│ │ └─ python >=3.11,<3.12.0a0 , which can be installed;
│ ├─ conda-verify 3.1.1 would require
│ │ └─ python >=3.6,<3.7.0a0 with the potential options
│ │ ├─ python [2.7.15|3.6.7|3.7.1], which cannot be installed (as previously explained);
│ │ └─ python [3.6.10|3.6.11|...|3.6.9], which can be installed;
│ ├─ conda-verify 3.1.1 would require
│ │ └─ python >=3.7,<3.8.0a0 with the potential options
│ │ ├─ python [2.7.15|3.6.7|3.7.1], which cannot be installed (as previously explained);
│ │ └─ python [3.7.1|3.7.10|...|3.7.9], which can be installed;
│ ├─ conda-verify 3.1.1 would require
│ │ └─ python >=3.8,<3.9.0a0 , which can be installed;
│ └─ conda-verify 3.1.1 would require
│ └─ python >=3.9,<3.10.0a0 , which can be installed;
└─ pin-1 is not installable because it requires
└─ python 3.12.* , which conflicts with any installable versions previously reported.I don't know how valuable the checks provided by conda-verify are, but when it's not available this slightly alarming message appears in conda-build's output:
WARNING: Importing conda-verify failed. Please be sure to test your packages. conda install conda-verify to make this message go away.I would prefer not to see this, as it is confusing when debugging. By now I know what it means and can ignore it, but newer conda users may be misled about the source of their problems, and now will not even be able to follow the warning's advice.
That said, I cannot offer to be a maintainer at the moment, but will see if I can make that change.
Comment:
The latest version available is v3.1.1 but v3.4.2 is the latest version Can any of the 8 open feed-stock PRs including v3.4.2 be merged so the latest version is available on the conda-forge channel?