`noarch` with dep(s) not built on all systems
See original GitHub issueWhat is the policy on noarch
builds which have dependencies that are not built for all systems? Are these valid noarch
recipes?
Attn: @scopatz
@conda-forge/staged-recipes
Issue Analytics
- State:
- Created 6 years ago
- Comments:16 (16 by maintainers)
Top Results From Across the Web
RHEL 8.6 to RHEL 9 LEAPP Failing install leapp-upgrade -y
Updating Subscription Management repositories. Dependencies resolved. Package Architecture Version Repository Size. Removing: leapp noarch 0.14.
Read more >noarch packages are incompatible with pinned Python versions
When you specify the Python version in the meta.yaml file, this causes noarch packages to fail to build. ... Possible workaround is to...
Read more >centos - How do I install an rpm that complains about rpmlib ...
In this case, it is referring to particular features of the rpm library. error: Failed dependencies: rpmlib(FileDigests) <= 4.6.0-1 is needed by epel-release-6- ......
Read more >check_noarch — Bioconda documentation
The recipe should be noarch and not use python based skipping ... deps – Dictionary mapping requirements occurring in the recipe to their...
Read more >Fedora Packaging Guidelines
Architecture Build Failures; Noarch with Unported Dependencies ... If the arched package that your package deps on isn't available on all architectures ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If you make a
noarch
package depending on a package only available on a different python version, where herestupid-dummy-dep
is anoarch
package depending onenum34
but trying to be installed on python 3.6:If you make a
noarch
package with a dependency only available on a different architecture, where herestupid-dummy-maconly
is anoarch
package,stupid-dummy
is a package only available on Mac (sorry for bad names, they should probably be swapped), and I’m trying to install it on Linux:Pretty informative error messages, IMO, which makes me 👍 for allowing this.
Closing as this is now documented thanks to PR ( https://github.com/conda-forge/conda-forge.github.io/pull/567 ).
Thanks everyone 😃