Chris Burr

Maybe it is caused by the removal of `setuptools_scm` from the environment that is used for deploying the tarballs? Else I'm not sure.

Ah the other segfault is "harmless": https://github.com/conda-incubator/conda-docker/blob/154a6851a249cb2da55b495ed81539a5b31a6224/conda_docker/conda.py#L462-L463

> One trick that might help would be to have a separate CI job which unpacked the contents of the just-built package and called tree on it. With GitHub Actions...

Two things: - XRootD is now [available from conda-forge](https://github.com/conda-forge/xrootd-feedstock) - The minimal firewall configuration required to get it to work is (tested in a docker container): ```bash iptables --flush #...

What was the reason for https://github.com/conda-forge/myproxyclient-feedstock/pull/18?

Sorry I wasn't clear enough in my question, what was the original reason for trying to remove noarch and then add it back again? (Mostly asking for my own curiosity...

I'd only searched issues before opening this but now I see https://github.com/owenthereal/upterm/pull/213 which I think might be the same question.

To summarise some of the thingsI just said in person: * For strings represeting the architecture I really think we should follow: https://github.com/opencontainers/image-spec/blob/main/image-index.md#platform-variants * In `${CVMFS_locations}/container/${technology}/${operating_system}/${platform}/` * `/container/` really restricts...

What is meant by "at indexing time" here? Is the idea to switch to index templates? If so, the wiki should be updated as I don't see any automatic creation...

Won't creating the template also be needed for existing installations as well?