This PR seems still current - as I do not see reference to emulator 29 in master.

(I am having a quick look at the androidenv-related PRs - hence this comment.)

I understand this PR is meant to be a short term solution for getting emulator 29 until the script for automatic generation of the related config is fixed and re-run.

The bash script to automatically generate the packages derivation seems to be broken ...

I understand the script in question is generate.sh, whose usage is documented.

I wonder if the project has a way (CI cron weekly job?) for periodically checking for these kinds of semi-automatically generated configurations:

• Whether the invocation of generate.sh still succeeds.
• Whether the invocation of generate.sh still generates the same output - so if some body has to call it manually it still works predictably.
• Whether new version are available (and ideally automatically prepare a PR).

@lucafavatella Thanks for your comment. Yes, this was a quick fix to get emulator v29.

Like you said the long term solution should be to get generate.sh t run and run regularly and auto updates the generated files.

I'm not a Nix expert, but I'm not sure why the generated files are part of this package. If it can be built by the user, then we won't need to maintain this package for every version upgrade.. I guess it's something to do with determinism.

@fmnxl Thanks for coming back to me! Your changes saved me a lot of time while trying to get a recent emulator to run. I am trying to propose this in (still draft) PR #82118 so you are welcome to have a look to that so we get your changes (hopefully) merged soon.

Hello, I'm a bot and I thank you in the name of the community for your contributions.

Nixpkgs is a busy repository, and unfortunately sometimes PRs get left behind for too long. Nevertheless, we'd like to help committers reach the PRs that are still important. This PR has had no activity for 180 days, and so I marked it as stale, but you can rest assured it will never be closed by a non-human.

If this is still important to you and you'd like to remove the stale label, we ask that you leave a comment. Your comment can be as simple as "still important to me". But there's a bit more you can do:

If you received an approval by an unprivileged maintainer and you are just waiting for a merge, you can @ mention someone with merge permissions and ask them to help. You might be able to find someone relevant by using Git blame on the relevant files, or via GitHub's web interface. You can see if someone's a member of the nixpkgs-committers team, by hovering with the mouse over their username on the web interface, or by searching them directly on the list.

If your PR wasn't reviewed at all, it might help to find someone who's perhaps a user of the package or module you are changing, or alternatively, ask once more for a review by the maintainer of the package/module this is about. If you don't know any, you can use Git blame on the relevant files, or GitHub's web interface to find someone who touched the relevant files in the past.

If your PR has had reviews and nevertheless got stale, make sure you've responded to all of the reviewer's requests / questions. Usually when PR authors show responsibility and dedication, reviewers (privileged or not) show dedication as well. If you've pushed a change, it's possible the reviewer wasn't notified about your push via email, so you can always officially request them for a review, or just @ mention them and say you've addressed their comments.

Lastly, you can always ask for help at our Discourse Forum, or more specifically, at this thread or at #nixos' IRC channel.

Possibly superseded by #89775