Conda forge no longer works through Artifactory

[oriyafe]

conda-forge started to return the field track_features as list and not String which broke to contract between conda and Artifactory.

Two days ago https://gitlab.com/petsc/petsc added a new package: petsc-3.22.3-cuda11_complex_he184e62_101.conda to conda forge with list of track_features ("track_features" : "petsc-p-0, petsc-p-1"):
https://conda.anaconda.org/conda-forge/linux-64/current_repodata.json

Please change the track_features field to String or remove this package.

[beckermr]

This issue needs to be opened on the conda/conda-build issue tracker I think.

cc @conda-forge/core this looks potentially breaking?

[oriyafe]

Im not sure you are right. In the metadata file it looks like the track_features field was always List.
But in the repodata scheme it is String concat by spaces

[beckermr]

conda-forge doesn't itself make any changes or maintain the tooling that builds packages. So any incompatibilities or changes in metadata formats by definition are changes in conda, conda-build, or some other tool. Thus a conda-forge issue tracker is not the correct spot for this issue.

The best way to understand this is to note that both links you included in your previous message are to repos in the conda github org. Please reopen this issue there.

[hmaarrfk]

@oriyafe do you work for Artifactory or are you a user? It helps build context.

I notice that
https://github.com/conda-forge/petsc-feedstock/pull/227/files#diff-ad6aed43f0cf479348ccccec8e7185c4b70582192329f11908dd22a731771702R42-R47

moved to a v1 recipe that may have caused issues.

[oriyafe]

I'm working in Artifactory and this change impacted significantly many Conda users within our community.

[hmaarrfk]

I'm working in Artifactory

I take this to mean that you have an environment in their CI pipeline???

[oriyafe]

Yes, exactly. Many Conda pipelines are failing because of this change

[beckermr]

Xref: conda/conda-build#5608

[beckermr]

This issue can be closed in favor of the issue above on the correct issue tracker. Please follow along there for updates.