New comment by cmspam on void-packages repository

https://github.com/void-linux/void-packages/pull/49265#issuecomment-2019280204

Comment:
> We could do with fewer breathless protestations about packages falling behind when the version in the repo is only two months old and the version you're updating to was released last month. If you want bleeding-edge packages, there are other distributions to fulfill that desire.

There is an important void-specific fix implemented by this update, hence the breathless protestations. Initially I submitted this PR because Incus was out of date. I then saw an issue with void specifically, that was fixed with this update, and thought that because of the void-specificity of the issue/fix this might want to be merged sooner than later, and attention needed to be drawn to it.

This is not an issue of wanting bleeding edge features. It's an issue of wanting void-specific functionality added upstream to cover for a lack thereof, to be available in void before it's too late for people to have an easy migration path. There is a cut-off date for linuxcontainers image support for LXD, and many other reasons that migrations to incus need to be made quickly, and this particular version of incus is instrumental in enabling that for void users, because the migration tool was included, but not working for void specifically up until this version, which specifically enables it for void via https://github.com/lxc/incus/pull/511/commits

That said, I'm more than happy not to try to push fixes or updates along in a community where my help is not wanted.  I don't run incus on void personally, and any urgency behind this PR was simply to help others who do. I'll fix this commit message, and let others deal with any other void/incus issues in the future.