The latest version is 10-14, but the latest released version on conda-forge is v20241017-0
Beside for the obvious issue of misrepresenting the version, this makes it tough for people like me who are reporting issues to tell if the latest version is synchronized/installed/etc.
Just today I thought a bug still persisted, but in reality my bmad installation was just held behind for (confusing) reasons:
Ugh...
```
$ conda install bmad=20241017 python=3.12
Channels:
- conda-forge
Platform: osx-arm64
Collecting package metadata (repodata.json): done
Solving environment: failed
LibMambaUnsatisfiableError: Encountered problems while solving:
- nothing provides _python_rc needed by python-3.12.0rc3-rc3_h47c9636_1_cpython
Could not solve for environment specs
The following packages are incompatible
├─ bmad 20241017** is not installable because it requires
│ ├─ hdf5 >=1.14.4,<1.14.5.0a0 with the potential options
│ │ ├─ hdf5 1.14.4 would require
│ │ │ └─ mpich >=4.2.3,<5.0a0 , which requires
│ │ │ └─ mpi 1.0.* mpich, which can be installed;
│ │ ├─ hdf5 1.14.4 would require
│ │ │ └─ openmpi >=5.0.5,<6.0a0 , which requires
│ │ │ └─ mpi 1.0 openmpi, which conflicts with any installable versions previously reported;
│ │ └─ hdf5 1.14.4, which can be installed;
│ └─ openmpi >=5.0.5,<6.0a0 , which cannot be installed (as previously explained);
├─ h5py is installable with the potential options
│ ├─ h5py [2.10.0|3.1.0|...|3.9.0] would require
│ │ └─ python_abi 3.8.* *_cp38, which can be installed;
│ ├─ h5py 3.12.1 would require
│ │ └─ python_abi 3.13.* *_cp313, which can be installed;
│ ├─ h5py [2.10.0|3.1.0|...|3.9.0] would require
│ │ └─ python_abi 3.9.* *_cp39, which can be installed;
│ ├─ h5py [3.10.0|3.11.0|...|3.9.0] would require
│ │ └─ python_abi 3.10.* *_cp310, which can be installed;
│ ├─ h5py [3.10.0|3.11.0|...|3.9.0] would require
│ │ └─ python_abi 3.11.* *_cp311, which can be installed;
│ ├─ h5py [3.10.0|3.11.0|3.12.1|3.9.0] would require
│ │ ├─ hdf5 [>=1.14.2,<1.14.4.0a0 mpi_mpich_*|>=1.14.3,<1.14.4.0a0 mpi_mpich_*], which requires
│ │ │ └─ mpich [>=4.1.2,<5.0a0 |>=4.2.1,<5.0a0 ] with the potential options
│ │ │ ├─ mpich [4.1.2|4.2.0|4.2.1|4.2.2] would require
│ │ │ │ └─ mpi 1.0 mpich, which can be installed;
│ │ │ └─ mpich 4.2.3, which can be installed (as previously explained);
│ │ └─ mpich [>=4.1.2,<5.0a0 |>=4.2.0,<5.0a0 |>=4.2.1,<5.0a0 |>=4.2.3,<5.0a0 ], which can be installed (as previously explained);
│ ├─ h5py [3.10.0|3.11.0|3.12.1|3.9.0] would require
│ │ ├─ hdf5 [>=1.14.2,<1.14.4.0a0 mpi_openmpi_*|>=1.14.3,<1.14.4.0a0 mpi_openmpi_*] but there are no viable options
│ │ │ ├─ hdf5 1.14.3 conflicts with any installable versions previously reported;
│ │ │ └─ hdf5 [1.14.2|1.14.3] would require
│ │ │ └─ openmpi [>=4.1.5,<5.0a0 |>=4.1.6,<5.0a0 ], which requires
│ │ │ └─ mpi 1.0 openmpi, which conflicts with any installable versions previously reported;
│ │ └─ openmpi [>=4.1.5,<5.0a0 |>=4.1.6,<5.0a0 |>=5.0.3,<6.0a0 |>=5.0.5,<6.0a0 ], which cannot be installed (as previously explained);
│ ├─ h5py [3.10.0|3.9.0] would require
│ │ └─ hdf5 >=1.14.2,<1.14.4.0a0 but there are no viable options
│ │ ├─ hdf5 [1.14.2|1.14.3], which cannot be installed (as previously explained);
│ │ ├─ hdf5 1.14.3 conflicts with any installable versions previously reported;
│ │ ├─ hdf5 [1.14.2|1.14.3], which cannot be installed (as previously explained);
│ │ ├─ hdf5 1.14.2 conflicts with any installable versions previously reported;
│ │ └─ hdf5 1.14.3 conflicts with any installable versions previously reported;
│ ├─ h5py [3.10.0|3.11.0|3.12.1] would require
│ │ └─ hdf5 >=1.14.3,<1.14.4.0a0 but there are no viable options
│ │ ├─ hdf5 [1.14.2|1.14.3], which cannot be installed (as previously explained);
│ │ ├─ hdf5 1.14.3 conflicts with any installable versions previously reported;
│ │ ├─ hdf5 [1.14.2|1.14.3], which cannot be installed (as previously explained);
│ │ └─ hdf5 1.14.3 conflicts with any installable versions previously reported;
│ ├─ h5py 3.9.0 would require
│ │ └─ hdf5 >=1.14.1,<1.14.2.0a0 mpi_mpich_*, which conflicts with any installable versions previously reported;
│ └─ h5py 3.9.0 would require
│ └─ hdf5 >=1.14.1,<1.14.2.0a0 mpi_openmpi_*, which conflicts with any installable versions previously reported;
└─ python 3.12** is not installable because there are no viable options
├─ python [3.12.0|3.12.1|...|3.12.7] would require
│ └─ python_abi 3.12.* *_cp312, which conflicts with any installable versions previously reported;
└─ python 3.12.0rc3 would require
└─ _python_rc, which does not exist (perhaps a missing channel).
```
Comment:
In
tao/version/tao_version_mod.f90: https://github.com/bmad-sim/bmad-ecosystem/blob/main/tao/version/tao_version_mod.f90#L9The latest version is 10-14, but the latest released version on conda-forge is
v20241017-0Beside for the obvious issue of misrepresenting the version, this makes it tough for people like me who are reporting issues to tell if the latest version is synchronized/installed/etc.
Just today I thought a bug still persisted, but in reality my
bmadinstallation was just held behind for (confusing) reasons:Ugh...
``` $ conda install bmad=20241017 python=3.12 Channels: - conda-forge Platform: osx-arm64 Collecting package metadata (repodata.json): done Solving environment: failed LibMambaUnsatisfiableError: Encountered problems while solving: - nothing provides _python_rc needed by python-3.12.0rc3-rc3_h47c9636_1_cpython Could not solve for environment specs The following packages are incompatible ├─ bmad 20241017** is not installable because it requires │ ├─ hdf5 >=1.14.4,<1.14.5.0a0 with the potential options │ │ ├─ hdf5 1.14.4 would require │ │ │ └─ mpich >=4.2.3,<5.0a0 , which requires │ │ │ └─ mpi 1.0.* mpich, which can be installed; │ │ ├─ hdf5 1.14.4 would require │ │ │ └─ openmpi >=5.0.5,<6.0a0 , which requires │ │ │ └─ mpi 1.0 openmpi, which conflicts with any installable versions previously reported; │ │ └─ hdf5 1.14.4, which can be installed; │ └─ openmpi >=5.0.5,<6.0a0 , which cannot be installed (as previously explained); ├─ h5py is installable with the potential options │ ├─ h5py [2.10.0|3.1.0|...|3.9.0] would require │ │ └─ python_abi 3.8.* *_cp38, which can be installed; │ ├─ h5py 3.12.1 would require │ │ └─ python_abi 3.13.* *_cp313, which can be installed; │ ├─ h5py [2.10.0|3.1.0|...|3.9.0] would require │ │ └─ python_abi 3.9.* *_cp39, which can be installed; │ ├─ h5py [3.10.0|3.11.0|...|3.9.0] would require │ │ └─ python_abi 3.10.* *_cp310, which can be installed; │ ├─ h5py [3.10.0|3.11.0|...|3.9.0] would require │ │ └─ python_abi 3.11.* *_cp311, which can be installed; │ ├─ h5py [3.10.0|3.11.0|3.12.1|3.9.0] would require │ │ ├─ hdf5 [>=1.14.2,<1.14.4.0a0 mpi_mpich_*|>=1.14.3,<1.14.4.0a0 mpi_mpich_*], which requires │ │ │ └─ mpich [>=4.1.2,<5.0a0 |>=4.2.1,<5.0a0 ] with the potential options │ │ │ ├─ mpich [4.1.2|4.2.0|4.2.1|4.2.2] would require │ │ │ │ └─ mpi 1.0 mpich, which can be installed; │ │ │ └─ mpich 4.2.3, which can be installed (as previously explained); │ │ └─ mpich [>=4.1.2,<5.0a0 |>=4.2.0,<5.0a0 |>=4.2.1,<5.0a0 |>=4.2.3,<5.0a0 ], which can be installed (as previously explained); │ ├─ h5py [3.10.0|3.11.0|3.12.1|3.9.0] would require │ │ ├─ hdf5 [>=1.14.2,<1.14.4.0a0 mpi_openmpi_*|>=1.14.3,<1.14.4.0a0 mpi_openmpi_*] but there are no viable options │ │ │ ├─ hdf5 1.14.3 conflicts with any installable versions previously reported; │ │ │ └─ hdf5 [1.14.2|1.14.3] would require │ │ │ └─ openmpi [>=4.1.5,<5.0a0 |>=4.1.6,<5.0a0 ], which requires │ │ │ └─ mpi 1.0 openmpi, which conflicts with any installable versions previously reported; │ │ └─ openmpi [>=4.1.5,<5.0a0 |>=4.1.6,<5.0a0 |>=5.0.3,<6.0a0 |>=5.0.5,<6.0a0 ], which cannot be installed (as previously explained); │ ├─ h5py [3.10.0|3.9.0] would require │ │ └─ hdf5 >=1.14.2,<1.14.4.0a0 but there are no viable options │ │ ├─ hdf5 [1.14.2|1.14.3], which cannot be installed (as previously explained); │ │ ├─ hdf5 1.14.3 conflicts with any installable versions previously reported; │ │ ├─ hdf5 [1.14.2|1.14.3], which cannot be installed (as previously explained); │ │ ├─ hdf5 1.14.2 conflicts with any installable versions previously reported; │ │ └─ hdf5 1.14.3 conflicts with any installable versions previously reported; │ ├─ h5py [3.10.0|3.11.0|3.12.1] would require │ │ └─ hdf5 >=1.14.3,<1.14.4.0a0 but there are no viable options │ │ ├─ hdf5 [1.14.2|1.14.3], which cannot be installed (as previously explained); │ │ ├─ hdf5 1.14.3 conflicts with any installable versions previously reported; │ │ ├─ hdf5 [1.14.2|1.14.3], which cannot be installed (as previously explained); │ │ └─ hdf5 1.14.3 conflicts with any installable versions previously reported; │ ├─ h5py 3.9.0 would require │ │ └─ hdf5 >=1.14.1,<1.14.2.0a0 mpi_mpich_*, which conflicts with any installable versions previously reported; │ └─ h5py 3.9.0 would require │ └─ hdf5 >=1.14.1,<1.14.2.0a0 mpi_openmpi_*, which conflicts with any installable versions previously reported; └─ python 3.12** is not installable because there are no viable options ├─ python [3.12.0|3.12.1|...|3.12.7] would require │ └─ python_abi 3.12.* *_cp312, which conflicts with any installable versions previously reported; └─ python 3.12.0rc3 would require └─ _python_rc, which does not exist (perhaps a missing channel). ```