Marked conda-build 3.28 as broken

[JohanMabille]

conda-build 3.28 now requires package/version to be found in the meta.yaml, see this diff (If that link doesn't open to the right lines: Files Changed -> search "package/version").

However, this was not required for split packages before, and thus this change is potentially breaking a lot of feedstocks (it is breaking mamba-feedstock for instance).

[jezdez]

Le sigh, just wanted to mention that we've seen this and work on a fix..

[mbargull]

FWIW, a local build (with slightly different set of packages, but including conda-build=3.28) of conda-forge/mamba-feedstock@eabfae2 (with all scripts replaced by calls to true) did not trigger the issue for me. 🤷

[mbargull]

Upstream is working on fixing the issue -- so let's wait for that until we use conda-build>=3.28.0 in production on conda-forge.
As always, thanks everyone for looking into this!

[wolfv]

I guess this is also something new from the last release? mamba-org/boa#388

[jezdez]

I guess this is also something new from the last release? mamba-org/boa#388

I don't think it's the same issue, this sounds like a possible other issue related how metadata is used. I wasn't aware that boa is passing around their own classes.