Yann Dirson

@Soul85 I see you did make progress in https://github.com/microsoft/windows-rs/issues/2040, do you have some updates?

@ohadravid I'm try to get such method calls to work in an iterative manner, first implementing one rust func for each method call, and then we'll see what can be...

We finally decided that for our needs (generating a rootfs) using Mock was not the best way (we went to direct yum usage, and may end up with directly calling...

FWIW, I start getting this error when migrating a yocto build from sumo to warrior, without changing kernel and with minimal meta-rockchip changes.

In my case, if I use the exact same glmark2 version from sumo in my warrior build, use `ltrace -S` on glmark2-es2 and compare the results, what stands out is:...

I'm unlikely to find the time for this, as going this far proved not necessary to get the cause of the glitch I was after. I'll leave this as an...

Trying that last suggestion of letting `package-lock.json` as-is, even `npm install --package-lock-only` does not seem to fit, still yielding: ``` user@perso-dev:www (www|REBASE 1/10)$ npm install --package-lock-only npm WARN old lockfile...

Maybe also the first tutorials could be adjusted not to use webpack, but instead to use a simpler setup with `--target=web`, and introduce the bundler mode later on?

> Do you have any ideas on what the documentation should be? I would be happy to look at any PRs updating the docs I would be happy to reach...

This would be the scope of something like #56, which is likely not to land in `pytest-dependency` itself, but could be implemented as a separate plugin. I've started to think...