mboudet

There seems to be an issue on the bioconda side of things. The PR was merged, but the conda package was not built. https://github.com/bioconda/bioconda-recipes/pull/43684 https://anaconda.org/bioconda/vamb As soon as the package...

No problem. You may wish to create a new issue on the bioconda repository to make sure the problem is known.

> I believe biocontainers would automatically make a PR to bump the version (via dependabot) everytime there would be a new pypi release. I don't believe there is a dependabot...

Hmm, it seems to build fine on our end without the --ulimit. (Which is great, because there are not easy way to include those in the build process). Not sure...

Well, I feel like it would be cleaner to link to the main repo. If the maintainer does not wish to incorporate the modifications, we can proceed as it is.

Sorry, I seem to have missed this issue... @bgruening Should this be done with a mulled containers, since both packages are in conda? (I'm fine with having a dedicated container...

Hi. You can skip the biotools part, since it's a different container, but it would be great to add the license (same as before, GPL-3.0 I think?) Another issue is...

Hello, So, there are two main sources of docker images: * This repository, which build the images on https://hub.docker.com/orgs/biocontainers/repositories * The [bioconda channel recipes](https://github.com/bioconda/bioconda-recipes), where every conda package built has...

You can just switch about.license to 'Custom License' and the tests should pass. Did you check if the built image is working for you?

Ok, my question was more regarding the functionalities of the built images. Did you manage to use the software as intended using the container?