New comment by tsndqst on void-packages repository

https://github.com/void-linux/void-packages/pull/41472#issuecomment-1826200948

Comment:
Thanks for reminding me to look at this again @Vaelatern.  I was waiting for the 2.2.44 release then got distracted by the aiohttp 3.9 release that supports Python 3.12.  I  haven't used GNS3 recently but perhaps it works fine on 3.12 without the latest aiohttp library.

Anyway, I have integrated your suggestions into my local branch and I'm trying to figure out how to manage the busybox binary but I'm not having much luck.  The BUSYBOX_PATH variable you found is a Python variable.  I tried setting it via an environment variable so I can change it based on XBPS variables during build.  I haven't found a combination that works yet.  

Also, it turns out `setup.py` uses that BUSYBOX_PATH variable as a destination.  It is where GNS3 looks for binaries to copy into docker images.  It uses the `shutil.which()` to find the appropriate binary. 

I ended up copying the static busybox file into the location where the GNS3 setup expects to find it.  I think that is cleaner than what I had before.

I also tested it on my aarch64 box and docker images contain the aarch64 static busybox binary.