Chris Sewell

although actually the packages are not upgraded, as noted here: https://github.com/marvel-nccr/quantum-mobile/issues/127#issuecomment-661838576

I would maybe leave it there, but basically remove all of its contents and add a "redirect" note to look at `quantum-mobile/docs/releases/`

As I think I've mentioned before, the changelog here is a bit non-standard, because mostly the changes between releases are dictated by the versions of the roles used and the...

Heya, the seem to remember an issue opened on aiida-core about this as well maybe also you?) So with it up and running after this error message, can you submit/run...

I think I've solved this in the aiida role: https://github.com/marvel-nccr/ansible-role-aiida/pull/48#issuecomment-713277036 😄 Just need to do something similar for the aiidalab role

As suggested by @webknjaz in marvel-nccr/ansible-role-aiida#48, we may want to consider using pip-tools and "lock" files, to keep the virtualenv reproducible

Also, as I was just saying to @csadorf with quantum mobile, we in essence have two competing goals: - in one sense it is a tool for building VMs, in...

note the full build is now tested on pushes to master or tag/release creation: https://github.com/marvel-nccr/quantum-mobile/actions/runs/308356597 😄 This kind of closes this issue, although we should probably decide (and document) a...

I guess my main concern is if you can truly say/assume that: because these tests pass when installing the role into an empty docker container (i.e. the role's molecule testing),...

Heya, yeh no worries thanks; do you know at what step it hangs, i.e. do you have the ansible output?