Closed michaelweinold closed 6 months ago
There is a handful of recipes which I did not manage to build right away when we switched from an old emscripten compiler to 3.1.45
(at the same time we also switched from python 3.10 to 3.11 ).
To give some context:
When changing the emscripten compiler every package needs to be recompiled. I tried to do this by myself for every package, but had to stop when about 95% of the packages were done, because at some point we had to transition to the new emscripten / python versions and this update already took weeks of fulltime work :/
Also, we renamed the platform from emscripten-32
to emscripten-wasm32
when making this change.
So if you want to see which packages are "actually" available you can have a look at the actual repodata.
So if a package is missing repodata but there is already a recipe, it might be enough to just bump the build number and cross the fingers and hope that it still builds.
Sorry for the inconvenience, and I hope I can help with bringing the missing packages back to life.
Greetings Thorsten
so for peewee
I see 3.16.3
, so we probably just need to update the version, but If I remember correctly I had some problems compiling lxml
which is currently missing
Ah, I see - this is helpful to know, thank you! I will try to bump the build number for peewee
. I didn't see an issue for lxml
. Do you know what the blocker is in this case?
Now that peewee
has been updated in https://github.com/emscripten-forge/recipes/pull/990 and lxml
has been updated in https://github.com/emscripten-forge/recipes/pull/955, I think I can close this.
Thank you for your support!
...now that I was able to resolve https://github.com/emscripten-forge/recipes/issues/695, I can't seem to install certain packages from the emscripten-forge channel:
returns