Add QEMU with execve intercept - WIP: __glibc 2.28 fail

[MementoRC]

Checklist

• [x] Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• [x] License file is packaged (see here for an example).
• [x] Source is from official source.
• [x] Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• [ ] If static libraries are linked in, the license of the static library is packaged.
• [x] Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• [x] Build number is 0.
• [x] A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• [x] GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• [x] When in trouble, please check our knowledge base documentation before pinging a team.

[github-actions[bot]]

Hi! This is the staged-recipes linter and your PR looks excellent! :rocket:

[github-actions[bot]]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/qemu-execve/meta.yaml) and found some lint.

Here's what I've got...

For recipes/qemu-execve/meta.yaml:

• Selectors are suggested to take a <two spaces>#<one space>[<expression>] form. See lines [118]

[MementoRC]

@xhochy Please, when you have some time, can you look at this proposal? It fails locally with:

The following package could not be installed
└─ qemu-execve-aarch64 9.1.0.* ha1f11d0_0 is not installable because it requires
   └─ __glibc >=2.28,<3.0.a0 , which is missing on the system.

and I can't evaluate the tests to see if it will even work as intended

[github-actions[bot]]

Hi! This is the staged-recipes linter and I found some lint.

It looks like some changes were made outside the recipes/ directory. To ensure everything runs smoothly, please make sure that recipes are only added to the recipes/ directory and no other files are changed.

If these changes are intentional (and you aren't submitting a recipe), please add a maintenance label to the PR.

File-specific lints and/or hints:

• .ci_support/linux64.yaml:
  • lints:
  • Do not edit files outside of the recipes/ directory.

[github-actions[bot]]

Hi! This is the staged-recipes linter and your PR looks excellent! :rocket:

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/qemu-execve/meta.yaml) and found it was in an excellent condition.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/qemu-execve/meta.yaml, recipes/python-qemu-qmp/meta.yaml) and found some lint.

Here's what I've got...

For recipes/python-qemu-qmp/meta.yaml:

• noarch: python recipes are required to have a lower bound on the python version. Typically this means putting python >=3.6 in both host and run but you should check upstream for the package's Python compatibility.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/qemu-execve/meta.yaml, recipes/python-qemu-qmp/meta.yaml) and found it was in an excellent condition.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/python-qemu-qmp/meta.yaml, recipes/qemu-execve/meta.yaml) and found some lint.

Here's what I've got...

For recipes/python-qemu-qmp/meta.yaml:

• Non noarch packages should have python requirement without any version constraints.
• Non noarch packages should have python requirement without any version constraints.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/qemu-execve/meta.yaml, recipes/python-qemu-qmp/meta.yaml) and found it was in an excellent condition.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipes/python-qemu-qmp/meta.yaml, recipes/qemu-execve/meta.yaml) and found some lint.

Here's what I've got...

For recipes/python-qemu-qmp/meta.yaml:

• ❌ noarch packages can't have skips with selectors. If the selectors are necessary, please remove noarch: python.

For recipes/python-qemu-qmp/meta.yaml:

• ℹ️ noarch: python recipes should usually follow the syntax in our documentation for specifying the Python version.
  • For the run section of the recipe, you should usually use python >={{ python_min }} for the python entry.
  • If the package requires a newer Python version than the currently supported minimum version on conda-forge, you can override the python_min variable by adding a Jinja2 set statement at the top of your recipe (or using an equivalent context variable for v1 recipes).

[MementoRC]

@xhochy I am trying to build a local windows test/debug framework. I saw a discussion and your original docker proposal, as well as a few people saying that they were able to build package locally using that solution. I have tried based upon my poor understanding of it and failed. Updating the build-locally.py and win64.yaml does not seem to be the way. I turned to a complicated docker/vagrant solution (found online) and wanted to see if you could not provide me with a bit of guidance on how to proceed. Currently the 20G location that I am using is too small, so before starting to change things around, it'd be great if you could point me in the right direction - win work is way too frustrating (I know, it's likely my ignorance that is too frustrating)