Hi,

We are maintaining the ASE (Atomic Simulation Environment) and GPAW (a Density 
Functional Theory code).  GPAW depends on ASE, and the development of the two 
packages is tightly integrated.  In addition, a few other packages depend on 
ASE.

We would like to release new versions of ASE + GPAW, also on the 2018b 
toolchain (which is the one we use ourselves).  That does, however, create a 
version conflict according to the Travis CI on github, see 
https://github.com/easybuilders/easybuild-easyconfigs/pull/8751

The problem is that one version of GPAW (and a few other packages) depend on 
ASE 3.17.0 and this new GPAW depends on ASE 3.18.0.  It was my impression that 
this could be solved by changing the package suffix, i.e. call the new version 
of GPAW GPAW/19.8.1-foss-2018b-ASE-3.18.0-Python-3.6.6 instead of 
GPAW/19.8.1-foss-2018b-Python-3.6.6 .  However, that does not work and the 
Travis CI self test still complains.

Have I misunderstood what I should do, or is this just not possible?

Jakob


--
Jakob Schiøtz, professor, Ph.D.
Department of Physics
Technical University of Denmark
DK-2800 Kongens Lyngby, Denmark
http://www.fysik.dtu.dk/~schiotz/



Reply via email to