Wolf Vollprecht
Wolf Vollprecht
Or we change the way we do activation completely (to work like pixi) and add everything to the Jinja context :)
Actually, it's a requirement for the reproducible builds to build the packages in the exact same prefix regardless, so that's not really an issue. A lot of packages ship files...
Hi @EugenePlanteurCS thank you for trying sandboxing with rattler-build! My first thoughts are that it sounds like our sandbox implementation relies on features that were not activated on your Linux...
Hi @EugenePlanteurCS I think unfortunately the missing `MNT_NS` is the issue. It looks like it is needed to control filesystem access and "mount" folders as readonly / readwrite / ......
Hmm in that case you could check whether e.g. bash is accessible, or any of the tools that you are using?
Maybe you can use the link from Gitlab instead? https://gitlab.com/hepcedar/yoda/-/archive/yoda-2.0.3/yoda-yoda-2.0.3.tar.gz I am not sure we can reasonably deduce file names from a query string. It seems pretty brittle. However, the...
The thing is that we don't extract the file when the file name is set explicitly. Sometimes you want an archive as archive eg for testing
I think there is something similar happening in `rattler` right now cc @prsabahrami
Yes, I think that's something we should be able to add to rattler-build. Were you able to workaround this or is this (very) urgent?
Will have to look into this. Thanks for the bug report, and it might indeed be the same issue.