Please stabilize pyudev on arm64, this is required to move forward with libblockdev stabilization.
arm64 done all arches done
(In reply to Piotr Karbowski from comment #0) > Please stabilize pyudev on arm64, this is required to move forward with > libblockdev stabilization. Hi. No issues this time (especially from me, as I have no issues with others helping in my packages), but this might do bad things in other places. Note that you manually added arm64@g.o to CC, which is equal to automatically CC-ARCHES manually and overwriting nattka. Next time, please don't add arches and let nattka add them (after the maintainer adds CC-ARCHES to keywords). Once again, nothing happened here, just caution to next time :)
This is interesting thing you bring up. There are two reasons why I did so. - I assumed here nattka would add arm64 only if there ever was other ebuild of pyudev that had stable arm64, which in this case it did not. - Whenever I got assigned a stabilization bug made by others for package I maintain, I noticed CC-ARCHES being added there not by maintainers, like in bug 854135, this was not always the case though. Perhaps blueness gave green light there. I am all into aligning with process, and until this very moment I was sure I do. Now looking at https://devmanual.gentoo.org/keywording/index.html#moving-from-arch-to-arch I see that it's indeed the case. Will pay more attention to it, thanks for bringing it up to my attention.
