01:39 <_whitenotifier> [symbiflow-arch-defs] Zambito1 opened issue #1957: make env fails on Arch Linux - https://git.io/Jtqsf

06:43 <_whitenotifier> [sv-tests] caryr opened issue #1287: yosys is listed as a runner for all tests - https://git.io/Jtqwr

08:55 <lambda> litghost: I installed conda using pacman - as far as I can tell conda is basically a generic package manager, so I don't really see why I'd have to install it in a symbiflow-specific prefix

11:50 <_whitenotifier> [symbiflow-arch-defs] the-centry opened issue #1959: How to add IOB18 into symbiflow? - https://git.io/Jtmf4

16:57 <litghost> lambda: You don't need to install conda to a symbiflow-specific prefix. Howeer conda does need write access to the conda prefix path to create new environments (which are roughly equiv to python venv's). If you install conda via pacman, presumably it installed conda with a prefix that requires root permissions to write into. The instructions provides a recommended install method so that root permissions are not

16:57 <litghost> required to setup the conda environment.

16:58 <litghost> lambda: So to answer your original question about why the instructions were trying to write to /usr/pkgs/urls.txt is because you installed conda via pacman, instead of using a conda that is installed to a user writable path.